You should have barsHD.mxf
I attach: barsHDoutMorganFromVirtualDub.avi that is barsHD.mxf loaded in virtualdub and save the .avi file in morgan mjpeg
and
I put barsHDoutMorganFromVirtualDub.avi into the timeline and export it to achieve: barsHDoutFromNLE.avi
If I don't mistake: the 2 avi files have to be the "same"
+ Reply to Thread
Results 31 to 44 of 44
-
-
my cat says: please what is the difference from -level:v 4.1 and -level:v 3?
-
AVC levels place a restriction on data, bandwidth, resolution . They are meant to categorize, so you can make encodes compatible with certain targets and devices and decoding chip hardware
Look at the chart here
http://en.wikipedia.org/wiki/H.264/MPEG-4_AVC#Levels
For example Level 3 is only supposed to support 720x576 . I think you just copy & pasted that from another SD encode, hence the mistake
The good news is your dinosaur NLE wasn't causing those chroma aliasing artifacts, it was Lead mjpeg -
using a .avi mjpeg LEAD file, and using:
v:\automazioneclip\core\ffmpeg.exe -y -i v:\lead_input.avi -pix_fmt yuvj420p -f rawvideo -vcodec rawvideo - | v:\automazioneclip\core\ffmpeg.exe -y -f rawvideo -s 1920x1080 -r 25 -i - -c:v libx264 -profile:v main -level:v 4.1 -g 33 -bf 0 -crf 18 -flags +ildct+ilme -x264opts tff=1:ref=1:colorprim=bt709:transfer=bt709:colorma trix=bt709:vbv-maxrate=40000:vbv-bufsize=30000 -pix_fmt yuv420p -an -aspect 16:9 z:\lead_output.mp4
seems levels are ok
meanwhile using Morgan, but in pipe
v:\automazioneclip\core\ffmpeg.exe -y -i v:\morgan_input.avi -pix_fmt yuvj420p -f rawvideo -vcodec rawvideo - | v:\automazioneclip\core\ffmpeg.exe -y -f rawvideo -s 1920x1080 -r 25 -i - -c:v libx264 -profile:v main -level:v 4.1 -g 33 -bf 0 -crf 18 -flags +ildct+ilme -x264opts tff=1:ref=1:colorprim=bt709:transfer=bt709:colorma trix=bt709:vbv-maxrate=40000:vbv-bufsize=30000 -filter_complex crop=out_h=1080:y=0,scale=interl=1:in_range=tvut_range=tv -pix_fmt yuv420p -pix_fmt yuv420p -an -aspect 16:9 z:\morgan_output.mp4
I get an error
In attachement the lead_output.mp4 -
Post the error message
You don't want to pipe using the old method since the new commandline using vf scale
The reasons why the old one is no good:
1) the 422=>420 scaling is progressive - you will get chroma ghosting artifacts as described earlier. You will see this in motion , not on a static scene
2) ffmpeg pipe to ffmpeg is waste of resources ; you only had to do that before the in_range and out_range were added
The reason why we did that was to get around the yuvj420 issue - the "j" is stripped in the raw pipe because it's no longer "MJPEG". So ffmpeg no longer "thinks" it's "j" or full range, and no longer does a PC=>TV conversion automatically. ie. you're doing that to avoid the levels clamp -
I know but levels are bad, I think, are bad because avoiding pipe I cannot fin the just commanline to have same levels that I get with the pipe
-
I don't know why you think levels are bad ? I already proved to you levels are same as original source mxf
I showed you bad chroma artifacts from progressive 422=>420 downsampling
I think something is wrong with your display setup configuration
Did you download this one to test?
https://forum.videohelp.com/threads/365583-from-mxf-avi-1080-1088-mess-mp4-please-pleas...=1#post2331684 -
If that one looks ok, then nothing is wrong with your display setup
I posted precise commandline, just change the input/output filenames
https://forum.videohelp.com/threads/365583-from-mxf-avi-1080-1088-mess-mp4-please-pleas...=1#post2331628
ffmpeg from June 28,2014 from Zeranoe
http://ffmpeg.zeranoe.com/builds/