Details please, there does not seem to be adequate documentation that I can find on this.mirkosp wrote:??.even when L-Smash Works is out there, free for all, and better?
mirkosp wrote:Also, I will have to say that FFMS2 is a brad idea for direct BD AVC (and not just that), and remuxing isn't a solution to fix the problem, since it's not related to the container, hence why I suggest L-Smash Works now; here's a more indepth explanation (keep in mind that ffms2 relies directly on libav)? For progressive content, L-Smash Works is a safe option, for interlaced content, only DGDecNV is truly safe.
For instance, H.264 allows IDR-picture without SPS/PPS.
For such IDR-pictures in TS, we can't treat as keyframe (random access point) but libavfomrat returns them as keyframe.
So, the result will be broken when the current SPS/PPS in extradata doesn't match (and libavcodec shall not update AVCodecContext.extradata)?
This case is frequently present in BD m2ts.
LWLibavVideoSource can handle correctly this case.
I seemed to have overlooked the link in your first post. Well this is rather new and I have not heard of it before, thank you for the links and information. Also, this would have been nice information to quote the first time around rather than a side note and a link the first post, helps it to not get overlooked as easilymirkosp wrote:I already linked it before:mirkosp wrote:Also, I will have to say that FFMS2 is a brad idea for direct BD AVC (and not just that), and remuxing isn't a solution to fix the problem, since it's not related to the container, hence why I suggest L-Smash Works now; here's a more indepth explanation (keep in mind that ffms2 relies directly on libav)? For progressive content, L-Smash Works is a safe option, for interlaced content, only DGDecNV is truly safe.For instance, H.264 allows IDR-picture without SPS/PPS.
For such IDR-pictures in TS, we can't treat as keyframe (random access point) but libavfomrat returns them as keyframe.
So, the result will be broken when the current SPS/PPS in extradata doesn't match (and libavcodec shall not update AVCodecContext.extradata)?
This case is frequently present in BD m2ts.
LWLibavVideoSource can handle correctly this case.
L-Smash Works has its own internal workarounds to make this all work correctly, whereas ffms2 depends entirely on libav, which doesn't handle this properly. As this is a common occurrance in AVC BDs (yes, progressive ones as well), it makes L-Smash Works the preferrable suggestion now that it exists, if a free solution is desired.
Users browsing this forum: No registered users and 0 guests