Fredrik Mellbin comments

Results 145 comments of


                                            Fredrik Mellbin

PC scale color range doesn't seem to work as expected

What? I always assumed YUVRGB_Scale was ignored (since no RGB conversion is ever done by d2vsource) and the range was flagged according to the mpeg stream. Insanity.

PC scale color range doesn't seem to work as expected

Now the scale is simply ignored and _ColorRange is unset. I'll leave this open for a bit in case someone has a better idea later but it's a lot less...

PC scale color range doesn't seem to work as expected

It may be possible to get the range from FFmpeg and properly set things but once again I'm missing a relevant sample to actually test things.

PC scale color range doesn't seem to work as expected

Never mind. I'm not going to try to implement range parsing.

Bug: Duplicate and out-of-sync frames if first GOP starts with B pictures

Sample still required for testing or no progress can be made

Bug: Duplicate and out-of-sync frames if first GOP starts with B pictures

A small sample is very welcome if you have one. I'm not sure exactly what the behavior is after my changes in the newffmpeg branch.

Bug: Duplicate and out-of-sync frames if first GOP starts with B pictures

This is definitely completely broken and I'm not sure if the seeking is closer to one or the other behavior

LWLibavSource crashes with specific file with VapourSynth

Try again with the latest lsmashsource. It should at least return a proper error now instead of crashing.

LWLibavSource crashes with specific file with VapourSynth

And the other obvious question that will probably help me and/or the author. Does it work in avisynth?

LWLibavSource crashes with specific file with VapourSynth

Yes, it is. In avisynth it simply returns an uninitialized frame for many of the possible errors. So you get random memory which is usually a recycled previous frame. Definitely...