2017-03-27 12:19 GMT+02:00 Moritz Barsnick :
> On Mon, Mar 27, 2017 at 10:08:02 +0200, Carl Eugen Hoyos wrote:
>> Doesn't "-profile:v 3" increase the quality?
>> Please remove qscale from your command line, it has no effect on prores
>> encoding.
>
> From the Wiki:
> https://trac.ffmpeg.org/wiki/En
On Mon, Mar 27, 2017 at 10:08:02 +0200, Carl Eugen Hoyos wrote:
> Doesn't "-profile:v 3" increase the quality?
> Please remove qscale from your command line, it has no effect on prores
> encoding.
From the Wiki:
https://trac.ffmpeg.org/wiki/Encode/VFX#Prores
From empirical testing we've found t
>
>
> Do you see the blurring only using the Adobe decoder or also when decoding
> with FFmpeg?
>
> Doesn't "-profile:v 3" increase the quality?
> Please remove qscale from your command line, it has no effect on prores
> encoding.
>
IIRC the quality of AME was described to be better than ffmpeg's
2017-03-23 12:43 GMT+01:00 Dave :
> ffmpeg -y -i in.mxf -r 25 -vf settb=1/25 -flags +ilme+ildct -timecode
> 00:00:00:00
> -acodec pcm_s16le -filter_complex "[:1:a][:2:a]amerge=inputs=2[aout]"
> -map "[aout]" -map 0:0 -qscale:v 6 -vcodec prores_ks -profile:v 1
> -video_track_timescale 25 -copytb -
Dave wrote:
The full ffmpeg output is:
$ ./ffmpeg -y -i in.mp4 -acodec pcm_s16le -vcodec prores_ks -profile:v 1 -vf
scale=interl=1 -sws_flags full_chroma_inp+full_chroma_int -copytb -1 out.mov
FWIW I tested a bit the format conversion + various flags and the
only ones that made the ssim/psnr
I think reason why you can not get the same result is simple, ame using
apple prores, apple codec is closed and patented, ffmpeg prores is
opensource community implementation and creates non standard prores
files, try increase bitrate (-bits_per_mb 1200) and check if it get good
result, if resu
Hi Lou,
Sorry I wasn’t trying to top post, just respond to everyone’s questions. I
thought it would be easier to read if I responded to them individually.
I realise that ffmpeg can be downloaded there. I was referring to Erik’s post
where he said that he was using "zeranoe builds” and saw on
On Sat, 25 Mar 2017 10:57:19 +1100
Dave wrote:
> Seranoe seems to be windows only? I am testing on a Mac at the
> moment but the final install will be on a Linux box.
See http://ffmpeg.org/download.html for links to builds for macOS and
Linux.
Please try to avoid top-posting on this mailing li
Seranoe seems to be windows only? I am testing on a Mac at the moment but the
final install will be on a Linux box.
> On 25 Mar 2017, at 1:08 am, Erik Dobberkau wrote:
>
>> W dniu 2017-03-24 o 12:04, Dave pisze:
>>
>>> To answer your suggestions Chronek:
>>>
>>> I tried encoding with your su
Hi,
The AME encode of the sample is 209.3MB. Media Info reports the bitrate as
81.3Mbps for the video and 546Kbps for the audio.
> On 24 Mar 2017, at 11:53 pm, chronek wrote:
>
> Hello,
>
> Thanks for sample, nah i do not have prores codec and could not encode it
> with AME, could you tell m
Erik Dobberkau wrote:
W dniu 2017-03-24 o 12:04, Dave pisze:
To answer your suggestions Chronek:
I tried encoding with your suggested command line it was still pretty
much the same.
1) I downloaded a fresh copy of ffmpeg and compiled it and still had the
same results
2) I am not really in a p
2017-03-23 12:43 GMT+01:00 Dave :
> ffmpeg -y -i in.mp4 -acodec pcm_s16le -vcodec prores_ks -profile:v 1 -vf
> scale=interl=1
> -sws_flags full_chroma_inp+full_chroma_int -copytb -1 out.mov
Complete, uncut console output missing.
Do you see the blurring only with prores_ks or also with the defa
> W dniu 2017-03-24 o 12:04, Dave pisze:
>
>> To answer your suggestions Chronek:
>>
>> I tried encoding with your suggested command line it was still pretty
>> much the same.
>>
>> 1) I downloaded a fresh copy of ffmpeg and compiled it and still had the
>> same results
>> 2) I am not really in a p
Hello,
Thanks for sample, nah i do not have prores codec and could not encode
it with AME, could you tell me what filesize or bitrate you get with AME
and that sample?
Yes it is somehow blurry that why i want compare bitrate, now was
trying: ffmpeg -y -i in.mp4 -acodec pcm_s16le -vcodec pror
To answer your suggestions Chronek:
I tried encoding with your suggested command line it was still pretty much the
same.
1) I downloaded a fresh copy of ffmpeg and compiled it and still had the same
results
2) I am not really in a position to comment on
3) I assure you AME is using the same set
If "ffmpeg -i in.mp4 -acodec pcm_s16le -sws_flags
full_chroma_inp+full_chroma_int+accurate_rnd+bitexact -sws_dither none
-vcodec prores_ks -profile:v 1 -copytb -1 out.mov" not work as should
then there are posibilities (1) you are using old ffmpeg (2) there is
bug in ffmpeg decoder what debloc
> On 24 Mar 2017, at 4:12 am, Erik Dobberkau wrote:
>
>>
>> ffmpeg -y -i in.mxf -r 25 -vf settb=1/25 -flags +ilme+ildct -timecode
>> 00:00:00:00 -acodec pcm_s16le -filter_complex
>> "[:1:a][:2:a]amerge=inputs=2[aout]"
>> -map "[aout]" -map 0:0 -qscale:v 6 -vcodec prores_ks -profile:v 1
>> -vid
ProRes is required because it is going into Final Cut Pro 7.
> On 24 Mar 2017, at 2:20 am, chronek wrote:
>
> Are you really need prores codec? If you concern quality then use some
> loseless codec like utvideo...
>
> W dniu 2017-03-23 o 12:43, Dave pisze:
>> Hi guys,
>>
>> I am having a pro
I do not know what for he need prores codec, maybe he not need it I
did not see previous posts or screenshots...
so what is source file container/codec/colorspace/is interlaced? and
what is desired container/codec/colorspace and for what he need it?
(maybe can be used something else)
D
chronek :
> We still do not know what is his colorspace of input video, if it is only
> yuv420p then conversion to prores_ks profile:v 1 (yuv422p10) will be losy,
> not to mention that prores is itself losy, why not use native yuv420p? If
> you really need change codec why not use utvideo it can
2017-03-23 18:12 GMT+01:00 Erik Dobberkau :
> ffmpeg -y -i in.mxf -r 25 -vf settb=1/25 -flags +ilme+ildct -timecode
>> 00:00:00:00 -acodec pcm_s16le -filter_complex
>> "[:1:a][:2:a]amerge=inputs=2[aout]"
>> -map "[aout]" -map 0:0 -qscale:v 6 -vcodec prores_ks -profile:v 1
>> -video_track_timescal
We still do not know what is his colorspace of input video, if it is
only yuv420p then conversion to prores_ks profile:v 1 (yuv422p10) will
be losy, not to mention that prores is itself losy, why not use native
yuv420p? If you really need change codec why not use utvideo it can
loseless yuv420,
>
> ffmpeg -y -i in.mxf -r 25 -vf settb=1/25 -flags +ilme+ildct -timecode
> 00:00:00:00 -acodec pcm_s16le -filter_complex
> "[:1:a][:2:a]amerge=inputs=2[aout]"
> -map "[aout]" -map 0:0 -qscale:v 6 -vcodec prores_ks -profile:v 1
> -video_track_timescale 25 -copytb -1 out.mov
>
>
This will give you
Are you really need prores codec? If you concern quality then use some
loseless codec like utvideo...
W dniu 2017-03-23 o 12:43, Dave pisze:
Hi guys,
I am having a problem where there is a slight blur on converted videos. I am
trying to automate a couple of workflows where Adobe Media Encode
Hi guys,
I am having a problem where there is a slight blur on converted videos. I am
trying to automate a couple of workflows where Adobe Media Encoder is currently
used.
Here are the commands that I am running:
MXF Conversion:
ffmpeg -y -i in.mxf -r 25 -vf settb=1/25 -flags +ilme+ildct -ti
25 matches
Mail list logo
