Hi,
Right now I am capturing the web cam through ffmpeg using RTSP port.
Hereby command involved: $ffmpeg -f rtsp -i
rtsp://192.168.1.99/axis-media/media.amp
-pix_fmt yuvj420p -y 0001.mov
Every time I start recording I would be needing a 2/3/4gb size file output. Is
this possible?
Thanks a
Werner, can you please shortly explain the no-scenecut issue.
Without scenecut detection, if such event occurs in the middle of the GOP,
as it usually does, the video quality till the end of the GOP will be
rather compromised. It appears as a 'breathing effect'.
It is mostly stands out when a high
(Did this one not top post? Trying to figure out how to avoid that on Gmail)
Thanks for the advice. Now I guess I should encode a video using
double pass and CFR and compare them. There seems to be a hot debate
about which is best.
The settings below are what the apple.com recommends for 4:3.
Thanks for the advice. Now I guess I should encode a video using
double pass and CFR and compare them. There seems to be a hot debate
about which is best.
The settings below are what the apple.com recommends for 4:3. Forgive
my slowness but I'm having a tough time converting what sites
recommen
> > To: ffmpeg-user@ffmpeg.org
> > From: ceho...@ag.or.at
> > Date: Sun, 10 May 2015 14:27:29 +
> > Subject: Re: [FFmpeg-user] HD > SD Down-Convert Prores Color
> >
> > Kevin Wells hotmail.co.uk> writes:
> >
> > > if I emit the format=uyvy422 then the output file
> > > contains tiny green a
On 12 May 2015, at 16:32, Henk D. Schoneveld wrote:
>
> On 12 May 2015, at 15:50, Werner Robitza wrote:
>
>> On Tue, May 12, 2015 at 3:16 PM, Henk D. Schoneveld
>> wrote:
>>>
On 12 May 2015, at 13:50, Werner Robitza wrote:
On Tue, May 12, 2015 at 11:47 AM, Henk D. Schoneve
On Tue, May 12, 2015 at 18:08:59 +0200, Moritz Barsnick wrote:
> Furthermore, please show us your command line, and why you think the
> result is incorrect.
I'm sorry, I now see why it is incorrect. I failed to see the "6.1" in
ffmpeg's output.
I can reproduce with:
$ ffmpeg -f lavfi -i sine -fi
On Tue, May 12, 2015 at 21:32:32 +0530, Rashed wrote:
> I am trying to create 7.1 ALAC using 8 channel wav file as input. But
> output is always 6.1 instead of 7.1.
>
> Need help in fixing this issue.
>
> stdout:
>
> ffmpeg version N-69146-g90c9899 Copyright (c) 2000-2015 the FFmpeg developers
>
Hi,
I am trying to create 7.1 ALAC using 8 channel wav file as input. But
output is always 6.1 instead of 7.1.
Need help in fixing this issue.
stdout:
ffmpeg version N-69146-g90c9899 Copyright (c) 2000-2015 the FFmpeg
developers
built on Jan 19 2015 01:28:38 with gcc 4.9.2 (GCC)
configurati
On 12 May 2015, at 15:50, Werner Robitza wrote:
> On Tue, May 12, 2015 at 3:16 PM, Henk D. Schoneveld
> wrote:
>>
>>> On 12 May 2015, at 13:50, Werner Robitza wrote:
>>>
>>> On Tue, May 12, 2015 at 11:47 AM, Henk D. Schoneveld
>>> wrote:
Would you be so kind to explain why to NOT use
* Werner Robitza on Tuesday, May 12, 2015 at 15:10:07 +0200
> On Tue, May 12, 2015 at 2:45 PM, Christian Ebert wrote:
>> * Nicolas George on Tuesday, May 05, 2015 at 17:28:33 +0200
>>> As an additional note, the second solution if by far preferable, because
>>> forcing the frame type too frequentl
On Tue, May 12, 2015 at 3:16 PM, Henk D. Schoneveld wrote:
>
>> On 12 May 2015, at 13:50, Werner Robitza wrote:
>>
>> On Tue, May 12, 2015 at 11:47 AM, Henk D. Schoneveld
>> wrote:
>>> Would you be so kind to explain why to NOT use the crf option?
>>
>> CRF is essentially a constant quality mod
Hello,
ffmpeg is able to generate a start timecode for MXF or MOV files by using
" -timecode XX:XX:xxSEPxx"
When making a MOV file ffmpeg generates a starttimecode value in the
header and a seperate timecode stream. But not so for MXF.
But what can I do if I need a second timecode for MXF in
> On 12 May 2015, at 13:50, Werner Robitza wrote:
>
> On Tue, May 12, 2015 at 11:47 AM, Henk D. Schoneveld
> wrote:
>> Would you be so kind to explain why to NOT use the crf option?
>
> CRF is essentially a constant quality mode, which results in variable
> bitrate depending on the spatiotemp
On Tue, May 12, 2015 at 2:45 PM, Christian Ebert wrote:
> * Nicolas George on Tuesday, May 05, 2015 at 17:28:33 +0200
>> As an additional note, the second solution if by far preferable, because
>> forcing the frame type too frequently ruins x264's bit allocation
>> algorithms.
>
> As per this thre
* Nicolas George on Tuesday, May 05, 2015 at 17:28:33 +0200
> As an additional note, the second solution if by far preferable, because
> forcing the frame type too frequently ruins x264's bit allocation
> algorithms.
As per this thread elsewhere there are different opinions on
that. Others say tha
Hi
Many thanks Carl and Moritz.
I'll go and recompile ffmpeg and have a think about the command line
construction.
I will return - no doubt with a new set of questions.
Best regards for now
Chip
On 12 May 2015 at 12:32, Moritz Barsnick wrote:
> Hi Chip,
>
> On Tue, May 12, 2015 at 12:02:54 +
Large gop value is good enough for disabling it.
On Tue, May 12, 2015 at 2:25 PM, Werner Robitza
wrote:
> > Make sure to disable '-g' option, occasionally x264 generates both forced
> > and '-g', increasing the bitrate, reducing the quality and causing some
> > other mess.
>
> There's no way to
On Tue, May 12, 2015 at 11:47 AM, Henk D. Schoneveld wrote:
> Would you be so kind to explain why to NOT use the crf option?
CRF is essentially a constant quality mode, which results in variable
bitrate depending on the spatiotemporal complexity of the scenes. For
streaming purposes, this is not
Hi Chip,
On Tue, May 12, 2015 at 12:02:54 +0100, Chip wrote:
> ffmpeg version 1.0.10 Copyright (c) 2000-2014 the FFmpeg developers
> built on Jul 25 2014 07:50:40 with gcc 4.7 (Debian 4.7.2-5)
Apart from Carl Eugen's comment that this version is way too old to try
to analyze and fix any issues
> Make sure to disable '-g' option, occasionally x264 generates both forced
> and '-g', increasing the bitrate, reducing the quality and causing some
> other mess.
There's no way to "disable" the -g option. If you don't use it, x264
will stick to the default values of keyint=250 and min-keyint=25.
Chip aktivix.org> writes:
> ffmpeg version 1.0.10 Copyright (c) 2000-2014 the FFmpeg developers
This is old (2012) and unsupported, please build your
own FFmpeg binary with --enable-libfdk-aac (this is
the best available aac encoder) from current git head.
Carl Eugen
Hi
First time posting.
I'm currently using liquidsoap to transcode a live MP3 stream to a
lower bitrate AAC+ stream. However the AAC+ stream is not suitable
because it is VBR and we require CBR. There appears to be no way to
set CBR within liquidsoap. The input MP3 stream is CBR.
I am therefore
You don't have to disable scene cut detection. Without scencut the video
quality is dramatically lower than when it is used.
'force_key_frames' and 'scenecut' work just fine together. Such videos
passes Apple AppStore validation and Akamai does not complain about it
either.
Make sure to disable '-g
Verstuurd vanaf mijn iPhone
> Op 12 mei 2015 om 11:31 heeft Werner Robitza het
> volgende geschreven:
>
>> On Tue, May 12, 2015 at 1:25 AM, Joel Lopez wrote:
>> Can I add a few lower versions to the mix and a higher one?
>
> Yes, you should do that.
>
>> Can I realign the keyframes of the
On Tue, May 12, 2015 at 1:25 AM, Joel Lopez wrote:
> Can I add a few lower versions to the mix and a higher one?
Yes, you should do that.
> Can I realign the keyframes of the existing files?
That's going to be hard. You're better off re-encoding from scratch
with a fixed interval.
> I'm not so
On Mon, May 11, 2015 at 10:49 PM, Joel Lopez wrote:
> Could I just run my unaligned files through ffmpeg again with a set
> keyframe interval and disabled scene cut detection?
>
> Or do I need to scrap them and re-encode the source file and generate
> new files that are properly aligned? We have
Hi bigshot,
why are you screaming?
On Mon, May 11, 2015 at 16:53:32 -0700, bigshot wrote:
> Hello,
>
> I have noticed that /libfdk_aac/ in VBR mode spits out CBR audio encodes,
> ONLY, or at least is flagged as CBR in MediaInfo. While encoding there is a
> warning as you can see in the log below.
28 matches
Mail list logo
