On Dec 08, 2012, at 19:55, Carl Eugen Hoyos wrote:
> Carl Eugen Hoyos writes:
>
>>> You may not agree, but it my experience that material
>>> that has already been compressed with a lossy codec is
>>> often hard to compress further
>>
>> This is true for material that has been compressed with
Carl Eugen Hoyos writes:
> > You may not agree, but it my experience that material
> > that has already been compressed with a lossy codec is
> > often hard to compress further
>
> This is true for material that has been compressed with
> maximum quantiser but this does not seem like a typical
René J.V. Bertin writes:
> On Dec 08, 2012, at 00:06, Carl Eugen Hoyos wrote:
> > My guess now is that you argue that for two given codecs (no
> > matter if mjpeg, mpeg-4 asp, mpeg2video, flv1 or snow), the
> > following command line always produces files of nearly identical
> > size:
> > $ ff
On Dec 08, 2012, at 00:06, Carl Eugen Hoyos wrote:
> My guess now is that you argue that for two given codecs (no
> matter if mjpeg, mpeg-4 asp, mpeg2video, flv1 or snow), the
> following command line always produces files of nearly identical
> size:
> $ ffmpeg -i input -vcodec xxx out.avi
No,
René J.V. Bertin writes:
> >> What I mean is the size of the files I get on my sample videos.
> >> Guess I should have made that clearer. And of course I never
> >> meant to say it depends on the framerate only, evidently it
> >> depends on how much the images vary between frames.
("Guess" is
Top-hi :P
On Dec 07, 2012, at 18:42, Carl Eugen Hoyos wrote:
>> What I mean is the size of the files I get on my sample videos. Guess I
>> should have made that clearer. And of course I never meant to say it depends
>> on the framerate only, evidently it depends on how much the images vary
>> b
René J.V. Bertin writes:
> NB: at 12Hz there isn't much gain of mpeg4 encoding over
> mjpeg encoding
Depending on what you mean with "gain", this is not correct.
(Your sentence is equivalent to "intra-only codecs have
no real disadvantage over using P and B-frames for
sufficiently small fps."
René J.V. Bertin writes:
> Are we really speaking about the same thing, generating
> multiple tracks in a QuickTime movie, and not a
> track with 4 overlays or a multi-channel (audio) track?
> May I ask what the name of the filter is that merges
> the crop filter outputs in 4 tracks in a single
Are we really speaking about the same thing, generating multiple tracks in a
QuickTime movie, and not a track with 4 overlays or a multi-channel (audio)
track? May I ask what the name of the filter is that merges the crop filter
outputs in 4 tracks in a single output (not overlay, not amerge ...
René J.V. Bertin writes:
> I discovered yesterday that it's possible to split an input
> movie (a raw m4v stream) into 4 separate output movies (.mov)
> each containing a quarter of the original image (obtained with
> -vf crop=w/2:h/2:x:y), using a single invocation of ffmpeg.
> Is it possible
I discovered yesterday that it's possible to split an input movie (a raw m4v
stream) into 4 separate output movies (.mov) each containing a quarter of the
original image (obtained with -vf crop=w/2:h/2:x:y), using a single invocation
of ffmpeg.
Is it possible to generate a single output movie wi
11 matches
Mail list logo
