Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion.

Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules.

 

Go Back   Doom9's Forum > Search Forums

Showing results 1 to 15 of 15
Search took 0.01 seconds.
Search: Posts Made By: feisty2
Forum: VapourSynth 29th January 2017, 14:46
Replies: 105
Views: 116,326
Posted By feisty2
the out of range pixels will only NOT be an issue...

the out of range pixels will only NOT be an issue using floating point.
Forum: VapourSynth 29th January 2017, 14:29
Replies: 105
Views: 116,326
Posted By feisty2
it's supposed to keep out of range pixels like...

it's supposed to keep out of range pixels like that with floating point samples.
the only exception would be a floating point mask clip, which should be clamped to [0.0, 1.0]
Forum: VapourSynth 18th December 2016, 07:54
Replies: 105
Views: 116,326
Posted By feisty2
Actually it's much simpler than that Just use...

Actually it's much simpler than that
Just use the buggy plugin as if it works
And sure vsedit will crash
And then the OS(at least under windows 10) will pop out a "vsedit has stopped working"...
Forum: VapourSynth 17th December 2016, 06:40
Replies: 105
Views: 116,326
Posted By feisty2
since you PMed me, some debug info from vs2015 ...

since you PMed me, some debug info from vs2015

http://i.imgur.com/hwjxNlp.png
http://i.imgur.com/AvPFyo9.png

no offense but, ur code is way too cryptic and pretty much machine code to me..
Forum: VapourSynth 17th December 2016, 02:39
Replies: 105
Views: 116,326
Posted By feisty2
Plus it's "delete[]" for arrays... not sure if...

Plus it's "delete[]" for arrays...
not sure if "delete array" will still lead to memory leak (only the first element got deleted)

Edit: just googled about that and "delete" works in your case...
Forum: VapourSynth 17th December 2016, 02:35
Replies: 105
Views: 116,326
Posted By feisty2
Fix that memory leak and ur done.

Fix that memory leak and ur done.
Forum: VapourSynth 16th December 2016, 18:12
Replies: 105
Views: 116,326
Posted By feisty2
and @captaiŋadamo it's almost 2017 now, not...

and @captaiŋadamo
it's almost 2017 now, not 1997, time to shake the obsolete ideas off, C++ has always been EVOLVING! (C++17 is just around the corner :))
Forum: VapourSynth 16th December 2016, 17:51
Replies: 105
Views: 116,326
Posted By feisty2
LUTTable(const LUTTable &) // copy constructor ...

LUTTable(const LUTTable &) // copy constructor
LUTTable(LUTTable &&) // MOVE constructor (since C++11)

https://msdn.microsoft.com/en-us/library/dd293665.aspx
Forum: VapourSynth 16th December 2016, 17:39
Replies: 105
Views: 116,326
Posted By feisty2
it works, test code, compiled and executed...

it works, test code, compiled and executed smoothly under vs2015

#include <cstdint>
#include <cstdlib>
#include <iostream>

auto operator""ElementsLUTTable(size_t length) {
struct LUTTable...
Forum: VapourSynth 16th December 2016, 14:58
Replies: 105
Views: 116,326
Posted By feisty2
or a bit more organized with C++ 14.. ...

or a bit more organized with C++ 14..

#include <cstdint>

auto operator""ElementsLUTTable(size_t length) {
struct LUTTable final {
int32_t *RGBToLab = nullptr;
int32_t *LabToRGB =...
Forum: VapourSynth 16th December 2016, 14:21
Replies: 105
Views: 116,326
Posted By feisty2
rgblab = new long[16777216]; labrgb = new...

rgblab = new long[16777216];
labrgb = new long[16777216];

and no delete[] for both arrays, basic memory leak..
use smart pointers if you want some kind of automatic GC for C++ like in Java or...
Forum: VapourSynth 12th December 2016, 19:56
Replies: 105
Views: 116,326
Posted By feisty2
I certainly CAN read that kind of code, but that...

I certainly CAN read that kind of code, but that was way too assembly style and kinda makes me feel gross whenever reading such crap
Forum: VapourSynth 12th December 2016, 19:47
Replies: 105
Views: 116,326
Posted By feisty2
Using the pointer as an array is much saner and...

Using the pointer as an array is much saner and easier for programmers to read than doing it with the raw pointer arithmetic style.

"Along with bunch of bit wise operations", I was referring to...
Forum: VapourSynth 12th December 2016, 04:35
Replies: 105
Views: 116,326
Posted By feisty2
old_pixel = src[w] // also legitimate C code, and...

old_pixel = src[w] // also legitimate C code, and much more readable, and faster than *src++ cuz u got one less "add src, sizeof(pixel type)" operation


Right, we should definitely talk more...
Forum: VapourSynth 11th December 2016, 14:18
Replies: 105
Views: 116,326
Posted By feisty2
Tell me how is *src++ any better than src[w]? ...

Tell me how is *src++ any better than src[w]?
Sometimes I just fail to understand why would anyone write such unreadable stuff along with whole bunch of pointless, again, unreadable bit wise...
Showing results 1 to 15 of 15

 
Forum Jump

All times are GMT +1. The time now is 18:56.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2024, vBulletin Solutions Inc.