On 3/9/16, Andy Furniss wrote:
> Sreenath BH wrote:
>> On 3/8/16, Moritz Barsnick wrote:
>
>>> If you want the same profiles and levels, you will need to request them
>>> explicitly.
>>>
>>> The same thing goes for the quality: libx264 defaults to crf=23, I
>>> don't know about nvenc. Furthermore
Sreenath BH wrote:
On 3/8/16, Moritz Barsnick wrote:
If you want the same profiles and levels, you will need to request them
explicitly.
The same thing goes for the quality: libx264 defaults to crf=23, I
don't know about nvenc. Furthermore, encoders can trade off quality (or
size) for conver
On Tue, Mar 08, 2016 at 22:24:16 +0530, Sreenath BH wrote:
> I wanted to know if there was a way to achieve the results I wanted
> with the codec we prefer to use (nvidia) because it have significant
> speed increase.
You didn't say what you wanted to achieve (not directly), you reported
differenc
On 08 Mar 2016, at 17:54, Sreenath BH wrote:
> On 3/8/16, Moritz Barsnick wrote:
>> Hi Sreenath,
>>
>> On Mon, Mar 07, 2016 at 22:28:32 +0530, Sreenath BH wrote:
>>> As can be seen the two outputs differ in the H264 profile(High vs
>>> Main), bitrate, the pixel format and of course the file si
On 3/8/16, Moritz Barsnick wrote:
> Hi Sreenath,
>
> On Mon, Mar 07, 2016 at 22:28:32 +0530, Sreenath BH wrote:
>> As can be seen the two outputs differ in the H264 profile(High vs
>> Main), bitrate, the pixel format and of course the file sizes.
>
> Different encoders can have different defaults.
Hi Sreenath,
On Mon, Mar 07, 2016 at 22:28:32 +0530, Sreenath BH wrote:
> As can be seen the two outputs differ in the H264 profile(High vs
> Main), bitrate, the pixel format and of course the file sizes.
Different encoders can have different defaults. It appears that nvenc
defaults to "Main", wh
On 3/7/16, Carl Eugen Hoyos wrote:
> Sreenath BH gmail.com> writes:
>
>> Should I rerun the ffmprg command without the "loglevel quiet"
>> and report the output?
>
> Yes, please.
>
>> Please suggest. The input file is rather large, and ffmpeg
> < console output is likely to be very long.
>
> Then
Sreenath BH gmail.com> writes:
> Should I rerun the ffmprg command without the "loglevel quiet"
> and report the output?
Yes, please.
> Please suggest. The input file is rather large, and ffmpeg
< console output is likely to be very long.
Then cut the repeating lines in the middle of the con
Hi Carl,
Should I rerun the ffmprg command without the "loglevel quiet" and
report the output?
Please suggest. The input file is rather large, and ffmpeg console
output is likely to be very long.
thanks,
Sreenath
On 3/7/16, Carl Eugen Hoyos wrote:
> Carl Eugen Hoyos ag.or.at> writes:
>
>> Sre
Carl Eugen Hoyos ag.or.at> writes:
> Sreenath BH gmail.com> writes:
>
> > ffmpeg -i large.mp4 -loglevel quiet -c:a aac -c:v nvenc
> > -pix_fmt yuv420p -movflags +faststart out.mp4
>
> Always provide the complete, uncut console output when
> asking for support here.
Sorry, I forgot: Never us
Sorry.
Here is the unedited output from ffprobe.
--
Original file (source file)
root@ip-172-21-13-223:/tmp# ffprobe large.mp4
ffprobe version 3.0.git Copyright (c) 2007-2016 the FFmpeg developers
built with gcc 4.8.5 (GCC) 20150623 (Red Hat 4.8.5-4)
configuration: --prefix=/opt/mediase
Sreenath BH gmail.com> writes:
> ffmpeg -i large.mp4 -loglevel quiet -c:a aac -c:v nvenc
> -pix_fmt yuv420p -movflags +faststart out.mp4
Always provide the complete, uncut console output when
asking for support here.
Carl Eugen
___
ffmpeg-user mail
12 matches
Mail list logo
