> I tried both versions (included ffmpeg / external ffmpeg) with mpeg2 and > AVCHD footage from my camcorder. With mpeg2 no problem, and I had also > partial success loading and editing directly AVCHD files (the "original" > cinelerra-cv crashed when I tried to load them, so your patched version is > much better) : > - cinelerra can now open and edit AVCHD files, > - but some frames at the beginning and at the end of these clips are not > displayed correctly in the viewer/compositor, and also not rendered correctly. > It seems that cinelerra with included ffmpeg processes AVCHD slightly better > than with external ffmpeg.
The included ffmpeg has a beginning-of-file fix where stock ffmpeg accidentally advances itself past the first keyframe before beginning decode. > In both cases the terminal is full of messages like : > [swscaler @ 0x7f3657abd590]No accelerated colorspace conversion found from > yuv420p to rgb24. This one means the build had assembly disabled for the scaling function. > [h264 @ 0x7f3625ce6c40]number of reference frames exceeds max (probably > corrupt input), discarding one This appears to be harmless, though it does indicate that ffmpeg is seriously confused. > [h264 @ 0x7f3625ce6c40]Cannot parallelize deblocking type 1, decoding such > frames in sequential order This is ffmpeg being overly chatty. I'll find a way to shut it up :-) > With external ffmpeg, the first and last frames of a clip are black or look > like video noise when they're rendered. Yep; dropping keyframes. I have a spot-fix for it. > With internal ffmpeg, same problem but more frames are displayed/rendered > properly. Right. > I know AVCHD is not a good format for editing, so problems with it are not > really relevant. I just report them as testing results. If the internal ffmpeg misbehaves in a way that actually causes misrender, I want to know about it. Monty _______________________________________________ Cinelerra mailing list [email protected] https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
