On Sat, Mar 27, 2021 at 05:18:18PM +0100, Bo Berglund wrote:
> On Sat, 27 Mar 2021 10:06:03 +0100, Peter White
> wrote:
>
> >> But it all looks the same with the time incrementing at exactly 5
> >> seconds...
> >
> >Looks like someone took extra care to
On Sat, Mar 27, 2021 at 08:15:23AM +0100, Bo Berglund wrote:
> I am using ffmpeg in scripts to download from a live stream TV channel nightly
> so I can view the shows in the morning.
>
> To remove the commercials I have written a video editing program with which I
> can scan through a video and p
On Sat, Mar 27, 2021 at 09:13:10AM +0100, Bo Berglund wrote:
> On Sat, 27 Mar 2021 02:50:13 +0100, Peter White
> wrote:
>
> >> I tested your command ona typical video file and found that the output
> >> looks
> >> basically like this:
> >>
On Sat, Mar 27, 2021 at 09:39:38AM +0100, Cecil Westerhof via ffmpeg-user wrote:
> Bo Berglund writes:
>
> > Worth a check of your computer.
> > It should be able to run at 100% CPU for quite a while in normal
> > surroundings
> > (if the air flow is not obstructed, please check the inlets on th
On Sat, Mar 27, 2021 at 08:29:26AM +0100, Cecil Westerhof via ffmpeg-user wrote:
> Peter White writes:
>
> > On Sat, Mar 27, 2021 at 06:18:59AM +0100, Cecil Westerhof via ffmpeg-user
> > wrote:
> >> Peter White writes:
> >>
> >> > On Fri, Mar 2
On Sat, Mar 27, 2021 at 05:53:56AM +0100, Cecil Westerhof via ffmpeg-user wrote:
> Peter White writes:
>
> > You can compile it yourself as well. It is not that difficult. Might
> > need to hunt down some libraries, but that is basically just looking at
> > the error m
On Sat, Mar 27, 2021 at 06:18:59AM +0100, Cecil Westerhof via ffmpeg-user wrote:
> Peter White writes:
>
> > On Fri, Mar 26, 2021 at 05:28:40PM +0100, Cecil Westerhof via ffmpeg-user
> > wrote:
> >> Peter White writes:
> >>
> >> > On Fri, Mar 2
On Sat, Mar 27, 2021 at 05:53:56AM +0100, Cecil Westerhof via ffmpeg-user wrote:
> Peter White writes:
>
> > On Fri, Mar 26, 2021 at 07:02:13PM +0100, Cecil Westerhof via ffmpeg-user
> > wrote:
> >> Carl Zwanzig writes:
> >>
> >> > On 3/26/202
On Fri, Mar 26, 2021 at 05:28:40PM +0100, Cecil Westerhof via ffmpeg-user wrote:
> Peter White writes:
>
> > On Fri, Mar 26, 2021 at 09:55:21AM +0100, Cecil Westerhof via ffmpeg-user
> > wrote:
> >> I want to publish a speech I gave during a Zoom meeting. But cuttin
On Fri, Mar 26, 2021 at 07:02:13PM +0100, Cecil Westerhof via ffmpeg-user wrote:
> Carl Zwanzig writes:
>
> > On 3/26/2021 9:28 AM, Cecil Westerhof via ffmpeg-user wrote:
> >> There is only one problem. The video is 7:21 long, but both mpv and
> >> vlc think it is 7:30 long.
> >
> > IME, the meta
On Fri, Mar 26, 2021 at 04:40:26PM +0100, Bo Berglund wrote:
> On Fri, 26 Mar 2021 10:59:23 +0100, Peter White
> wrote:
>
> >You can use ffprobe to find the keyframe timestamps:
> >
> >ffprobe -select_streams V:0 -show_frames -skip_frame nokey -show_entries
> >
On Fri, Mar 26, 2021 at 10:59:23AM +0100, Peter White wrote:
> If you can live with further quality loss in the video, you can
> transcode it, i.e. -c:v libx264.
Forgot one thing. You can, and maybe should, use -ss as an input option.
This way ffmpeg does not decode the whole file un
On Fri, Mar 26, 2021 at 09:55:21AM +0100, Cecil Westerhof via ffmpeg-user wrote:
> I want to publish a speech I gave during a Zoom meeting. But cutting
> it out does not work.
>
> When I use:
> ffmpeg -y -i 2021-03-25ToastmastersClubAvond.mp4 -ss 1190 -to 1631
> -acodec copy -vcodec copy -asy
On Fri, Mar 26, 2021 at 10:07:14AM +0100, Michael Koch wrote:
> Am 26.03.2021 um 09:55 schrieb Cecil Westerhof via ffmpeg-user:
> > I want to publish a speech I gave during a Zoom meeting. But cutting
> > it out does not work.
> >
> > When I use:
> > ffmpeg -y -i 2021-03-25ToastmastersClubAvo
On Wed, Mar 24, 2021 at 05:00:09AM -0400, Mark Filipak (ffmpeg) wrote:
> ...contrary to https://ffmpeg.org/ffmpeg-filters.html#mix
>
> [Parsed_mix_29 @ 025771c709c0] Option 'nb_inputs' *not found*
> [AVFilterGraph @ 025772b53dc0] Error initializing filter 'mix' with args
> 'nb_inputs=2:we
On Fri, Mar 12, 2021 at 03:51:11PM +0100, Nicolas George wrote:
> Peter White (12021-03-12):
> > but that is because a packet needs to be decoded first to get the frame.
>
> Please be complete in your statements:
>
> ... with some obscure codecs or if libavcodec happens to
First off, please do not top-post here.
On Fri, Mar 12, 2021 at 10:50:51AM +0200, imalkev...@gmail.com wrote:
> Hi,
>
> Here are the three commands used:
> ffmpeg -threads 0 -loglevel repeat+level+verbose -f lavfi -i
> testsrc2=s=1920x1080:r=30 -f lavfi -i sine -c:a aac -ar 48000 -b:a 64k -c:v
On Fri, Mar 12, 2021 at 02:11:14AM -0500, Mark Filipak (ffmpeg) wrote:
> On 2021-03-11 18:37, Reino Wijnsma wrote:
> > On 2021-03-09T20:43:21+0100, Mark Filipak (ffmpeg)
> > wrote:
> > > On 2021-03-09 03:58, Michael Koch wrote:
> > > > These links might help:
> > > > https://stackoverflow.com/que
On Wed, Mar 10, 2021 at 09:30:20PM -0500, Barry Smith wrote:
> There is absolutely NOTHING about putting all of the package together
> where a PATH could find the files correctly
That is because *you* need to set up the PATH accordingly. Windows by
design is rather stupid in that regard since there
On Tue, Mar 09, 2021 at 04:27:14PM +0100, Peter White wrote:
> Hi all,
>
> as a follow-up to this discussion:
> https://ffmpeg.org/pipermail/ffmpeg-user/2021-March/052358.html
>
> I would like to ask, if frame counting with ffprobe can be made faster.
> The way it don
ied, definition of "frame" in avcodec.h
terms?:
A frame is what the decoder returns in avcodec_receive_frame().
If that is true, then I cannot see, how to work around that without
breaking something.
Or am I looking at it wrong?
> On Tue, Mar 9, 2021 at 4:27 PM Peter White wrot
On Tue, Mar 09, 2021 at 08:13:03PM +, Phil Rhodes via ffmpeg-user wrote:
> One of the other issues with this is that nobody ever seems to bother
> enforcing any rule whatsoever on this list in any case, so I view the entire
> discussion as pointless.
You are one of those meant by the OP. m(
Hi all,
as a follow-up to this discussion:
https://ffmpeg.org/pipermail/ffmpeg-user/2021-March/052358.html
I would like to ask, if frame counting with ffprobe can be made faster.
The way it done now is obviously by decoding every single frame and
afterwards incrementing the counter. See how slow
On Tue, Mar 09, 2021 at 11:26:49PM +1030, Rodney Baker wrote:
> On Tuesday, 9 March 2021 23:17:34 ACDT Peter White wrote:
> > On Tue, Mar 09, 2021 at 01:07:41PM +0100, Nicolas George wrote:
> > > Peter White (12021-03-09):
> > > > ffmpeg -i input.mkv -an -sn -c copy
On Tue, Mar 09, 2021 at 01:50:20PM +0100, Nicolas George wrote:
> Peter White (12021-03-09):
> > I have now, but it returns 'N/A'. Now that I see that, I might have
> > tried it way back when, even, and have forgotten about it.
> >
> > ffprobe -count_pack
On Tue, Mar 09, 2021 at 01:41:38PM +0100, Nicolas George wrote:
> Peter White (12021-03-09):
> > Is there a meaningful difference in this context?
>
> The fact that you need to ask is proof enough that it is needed.
I understand that a packet is what the demuxer sends to the d
On Tue, Mar 09, 2021 at 01:07:41PM +0100, Nicolas George wrote:
> Peter White (12021-03-09):
> > ffmpeg -i input.mkv -an -sn -c copy -f null -
>
> -c copy tells ffmpeg to dispense with the decoder, which means it does
> not count frames but packets. Have you tried tellin
On Tue, Mar 09, 2021 at 01:07:41PM +0100, Nicolas George wrote:
> Peter White (12021-03-09):
> > Would you mind answering the OP's question with a command line example,
> > then?
>
> I help people who help themselves, thus avoiding Russel's paradox.
Sorry, I don&#
On Tue, Mar 09, 2021 at 12:39:09PM +0100, Nicolas George wrote:
> Peter White (12021-03-09):
> > Sorry, I didn't mean to offend.
>
> I was not offended, I was amused.
>
> > Is there a proper universal way to do this with ffprobe that does not
> > take ages to
On Tue, Mar 09, 2021 at 12:13:53PM +0100, Nicolas George wrote:
> Peter White (12021-03-09):
> > Unless it happens to be one of those special cases that don't have that
> > info in their metadata, like matroska:
>
> Did I suggest to limit to the output of -show_format o
On Tue, Mar 09, 2021 at 12:20:32PM +0100, Michael Koch wrote:
> Am 09.03.2021 um 12:05 schrieb Reindl Harald:
> >
> > look at that bunch of idiots which repleatly ignore the "don't top post"
> > and how do you imagine would a list-footer with the sentence change that
>
> That's because many peopl
Let me throw in my very humble two cents.
On Tue, Mar 09, 2021 at 12:05:05PM +0100, Reindl Harald wrote:
>
>
> Am 09.03.21 um 11:48 schrieb mX:
> > Can someone with list admin access (admins at foot of this email) please
> > update the footer for this mailing list to assist new posters - becaus
On Tue, Mar 09, 2021 at 10:41:41AM +0100, Nicolas George wrote:
> Peter White (12021-03-09):
> > If anybody on this list knows a better one, step up, please.
>
> ffprobe, of course.
Unless it happens to be one of those special cases that don't have that
info in their met
On Tue, Mar 09, 2021 at 11:07:21AM +0100, Ulf Zibis wrote:
>
> Am 09.03.21 um 10:43 schrieb Ulf Zibis:
> >
> > Am 09.03.21 um 09:57 schrieb Peter White:
> > > The frame count *is* exact. The way to get there is just not that
> > > pretty. If anybody on t
On Tue, Mar 09, 2021 at 09:46:43AM +0100, Ulf Zibis wrote:
>
> Am 09.03.21 um 09:26 schrieb Peter White:
> > On Tue, Mar 09, 2021 at 09:13:14AM +0100, Ulf Zibis wrote:
> > > Hi,,
> > >
> > > can one please tell me, how I can get the total number of frames
On Tue, Mar 09, 2021 at 09:13:14AM +0100, Ulf Zibis wrote:
> Hi,,
>
> can one please tell me, how I can get the total number of frames of a video?
ffmpeg -i input -an -sn -c copy -f null -
This basically copies all frames into the void but you get the total
count this way in the stats line.
Pe
On Tue, Mar 09, 2021 at 07:38:09AM +0100, Anders Degerberg wrote:
> On Tue, Mar 9, 2021 at 4:52 AM Peter White wrote:
>
> > Just an aside, you need to specifiy the -sws_flags like this:
> > -sws_flags bilinear+print_info
>
> Thanks Peter,
> unfortunately it does
On Mon, Mar 08, 2021 at 09:46:22PM +0100, Anders Degerberg wrote:
> Hi, see output below:
> $ ffmpeg -loglevel verbose -f decklink -raw_format rgb10 -i "DeckLink
> 8K Pro (1)" -sws_flags bilinear -sws_flags print_info -c:v hevc_nvenc
> -an -b:v 30M -f null -
Just an aside, you need to specifiy the
On Mon, Mar 08, 2021 at 07:58:44PM +0100, Anders Degerberg wrote:
> Hi Peter,
>
> On Mon, 8 Mar 2021 at 19:18, Peter White wrote:
> > Try:
> >
> > ffmpeg -i input_file -sws_flags show_info ... output_file
> '-sws_flags print_info' gives:
> [swscaler @
On Mon, Mar 08, 2021 at 03:19:46PM +0100, Anders Degerberg wrote:
> Hi,
>
> I've come across a problem I really can't figure out when trying to stream
> realtime a RGB 10-bit Decklink input, as YUV444 10-bit HEVC in 25fps.
> In a 1920x1080 resolution on the Decklink input, it all works very well,
On Fri, Mar 05, 2021 at 11:07:32PM +0100, Paul B Mahol wrote:
> On Fri, Mar 5, 2021 at 10:54 PM Peter White wrote:
>
> > On Fri, Mar 05, 2021 at 11:33:10AM -0800, Steven Kan wrote:
> > >
> > > >>>
> > > >>> I’d like to assemble
On Fri, Mar 05, 2021 at 11:33:10AM -0800, Steven Kan wrote:
>
> >>>
> >>> I’d like to assemble these videos, side-by-side, but synced in time, which
> >>> means the TrailDown video needs to start 50 seconds after the TrailUp
> >>> video. The TrailDown side can be black/blank, or it can be stuck o
On 04.03.21 22:56, Peter White wrote:
Something like this:
ffmpeg -f lavfi -i ffmpeg -f lavfi -i
color=size=960x720:rate=60:color=black -c libvpx-vp9 -t 50 offset.ts
Sorry, there is a mistake here. This is what I actually meant:
ffmpeg -f lavfi -i
color=size=960x720:rate=60:color=black -c
On 04.03.21 21:36, Steven Kan wrote:
I have captured some nice footage of 3 coyotes traipsing through my yard, from
two IP cameras facing opposite directions. Recording was initiated by in-camera
motion triggers, so the recordings start about 50 seconds apart, as you can
tell from the burned-i
On 04.03.21 17:17, Laura Smith via ffmpeg-user wrote:
-minrate 6000k -maxrate 6000k -bufsize 6000k -b:v 6000k
I know this is off topic and you are free to ignore this but I cannot
stand having to look at badly encoded videos on the interweb. Why do you
force a constant bitrate? I see that tho
On 04.03.21 18:21, Laura Smith via ffmpeg-user wrote:
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'Transcodings/file.mp4':
That looks like a different file, judging by your original post:
> "${OUTDIR}/1080/${OUTPFX}_1080.mp4"
There should be a file ending with _1080.mp4 in ${OUTDIR}/1080/,
similar
On 04.03.21 17:38, Laura Smith via ffmpeg-user wrote:
Stream #0:1(eng): Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, stereo,
fltp, 317 kb/s (default)
Metadata:
creation_time : 2021-03-04T10:22:01.00Z
handler_name : #Mainconcept MP4 Sound Media Handler
vend
On 03.03.21 23:57, Mark Filipak (ffmpeg) wrote:
On 2021-03-03 11:30, Mark Filipak (ffmpeg) wrote:
I've tried transcoding a 2:21:19 movie via this script:
SET codecs=-codec:v libx265 -x265-params crf=16:qcomp=1.00 -codec:a copy
-codec:s copy -dn
FWIW I could not help but notice that you effec
05.09.2016 12:00, Sven C. Dack:
On 05/09/16 10:21, Peter White wrote:
What now? One LOL and I am not serious? You made the joke.
So you have no real interest in being here. Have it your way. I will put
you on an ignore list. Fine by me.
What is this, kindergarten? Fine, do that, if you
05.09.2016 08:34, Sven C. Dack:
On 05/09/16 00:55, Peter White wrote:
...
LOL, never said otherwise.
Actually you did. You have asked "What effects?"
And I gave the "answer" straight away, that there is no answer with
your methodology. And I did expressly acknowle
05.09.2016 00:58, Sven C. Dack:
On 04/09/16 22:52, Peter White wrote:
...
So you showed that they have an effect. Acknowledged. My question had
a follow-up, though. Your conclusions are not correct. The best scaler
is the one producing the best visual quality *before* compression. ...
I am
04.09.2016 23:09, Sven C. Dack:
> On 04/09/16 21:13, Peter White wrote:
>> Hi,
>>
>> 04.09.2016 20:40, Sven C. Dack:
>> ...
>> > *** Please note that this is _NOT_ a comparison of encoders, but it is
>> > meant to show the effect of the (down-)scal
Hi,
04.09.2016 20:40, Sven C. Dack:
> On 02/09/16 17:28, Sven C. Dack wrote:
>
> There are a few things I need to note first... The Nvidia hardware
> encoder NVENC doesn't accept a "-crf" value
Why do you have to use it then for this? I get that you use it in your
day to day encoding but since t
04.09.2016 14:31, Reindl Harald:
Am 04.09.2016 um 14:24 schrieb Peter White:
04.09.2016 14:00, Reindl Harald:
Am 04.09.2016 um 13:57 schrieb Peter White:
But I never saw the point of running two passes to improve the quality
of a file encoded with CRF mode. The quality improvement must be
04.09.2016 14:00, Reindl Harald:
Am 04.09.2016 um 13:57 schrieb Peter White:
But I never saw the point of running two passes to improve the quality
of a file encoded with CRF mode. The quality improvement must be very
small, I reckon. But the encoding time doubles--not worth it
with smart
04.09.2016 13:01, Carl Eugen Hoyos:
> 2016-09-04 12:52 GMT+02:00 Peter White :
>> 04.09.2016 12:21, Carl Eugen Hoyos:
>
>>>> i am trying to encode with a variable bitrate, 2 pass encoding
>>>
>>> How is this supposed to work (in a general sense, unr
04.09.2016 12:21, Carl Eugen Hoyos:
> Hi!
>
> 2016-09-04 10:56 GMT+02:00 Marco Diletti
:
>>
>> i am trying to encode with a variable bitrate, 2 pass encoding
>
> How is this supposed to work (in a general sense, unrelated
> to a codec or an implementation)?
> Two-pass encoding indicates constant
02.09.2016, 08:50, Sven C. Dack:
> Hello,
>
> On the subject... I've been doing just that. Transcoding H.264
> videos into H.265, scaling these down to 480p and reducing the
> bitrate to about 1mbit/s.
Well, the size reduction is obviously due to the smaller image
dimensions and not because
Hi!
20.08.2016 16:43, Moritz Barsnick:
Hi Jens,
On Fri, Aug 19, 2016 at 17:23:03 +0200, Jens Kallup wrote:
What is VLS?
That'd be the VideoLAN Server, I guess. It used to be kind of the
counterpart of VLC, the client. Maybe it still is, but its use seems to
be discouraged:
https://www.videol
19.08.2016 10:41, schrieb Glorin Li:
Hi all,
Hi,
have you really cross-posted this to the devel list? You might want to
think again about that. I am not a developer, so not described to that
one but it certainly is not meant for questions like this. Plus, cross-
posting in general is frowned u
16.08.2016 23:25, Nomis101 🐝:
Am 16.08.16 um 22:26 schrieb Carl Eugen Hoyos:
Thank you for the confirmation!
Are you sure the quality is satisfying?
> The songs are also average 8 % longer.
Just an idea, the original sample rate of DTS is most likely 48kHz. The
target rate is 44.1kHz. These
12.08.2016 10:34, Mikołaj Machowski:
>> 11.08.2016 14:23, Mikołaj Machowski:
>>> I have video with four streams: 0:0 video, 0:1 audio, 0:2 sub1, 0:3
sub2
>
>>> Result of normal settings is that both subtitle streams are default
>
>> Which container or file type is this? I know for certain that m
nothing here
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user
To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Hi!
11.08.2016 14:23, Mikołaj Machowski:
I have video with four streams: 0:0 video, 0:1 audio, 0:2 sub1, 0:3 sub2
> Result of normal settings is that both subtitle streams are default
Which container or file type is this? I know for certain that multiple
default streams of the same kind are n
10.08.2016 20:05, Moritz Barsnick:
On Wed, Aug 10, 2016 at 19:31:28 +0200, Peter White wrote:
That does not make much sense, since the final file is supposed to be
fltp, which is 32 bit, anyway.
This may be a misconception. I believe the "fltp" ffmpeg prints for its
inputs is the
1680d800] Specified sample format fltp is invalid or not supported
This is the problem. fltp seems not to be supported (yet) by this
codec. I get the same with the git master from today (N-81311-g75e7f20).
Am 10.08.16 um 16:09 schrieb Peter White:
Is there a reason you did this in two steps? ffmpe
Hi!
10.08.2016 11:40 Nomis101:
> I found out, that I can listen to 5.1 surround music over iTunes /
> Airplay if the music is an dts-encoded WAV file (44.1 kHz, 16 Bit). This
> means I have to convert all my surround music, mostly *.dts, *.flac or
> *.ac3, into this format.
>
> The format that I
Last try. Really!
10.08.2016 01:31 juan carlos Rebate:
2016-08-10 0:05 GMT+02:00 Peter White :
I if I try to cooperate, but you are wrong, I read all the documentation says
about the http protocol and there is nothing that serves as support for this
error solvetar
You know what, you spend
juan carlos Rebate:
No, nothing is missing
> I wrote already, and others, too:
>> Oh, there is plenty missing. The actual output which contains a hint of
>> what goes wrong.
As I said, PEBCAK. Oh no, that was my crystal ball saying that.
Hint: If you really are here for help or a fix, it is
Am 09.08.2016 um 22:47 schrieb juan carlos Rebate:
2016-08-09 22:04 GMT+02:00 Reindl Harald :
Am 09.08.2016 um 21:09 schrieb juan carlos Rebate:
what *exactly* did you not understand *multiple* times when epople
explained you how to compose a email so it is readable for others?
ignoring doz
09.08.2016 21:09 juan carlos Rebate:
2016-08-09 20:32 GMT+02:00 Peter White :
And if you reply by quoting everything, again, I am done responding!
Have a look at this mail and get an idea what inline reply means and
how to cut the quotation to the relevant part you are responding to
Hi,
Subject "new error" is a rather ambiguous title. You really should
make that more specific. How are people supposed to know what this is
about when browsing the mailing archive?
09.08.2016 19:47 juan carlos Rebate:
> New error found, according to the documentation to indicate the mime
> type
Hi!
09.08.2016 17:31 William van Gelder:
> I am looking for a way to read the input of the command line from
> memory instead of ingesting a file or URL.
I am not certain I understand, what you want to achieve. Maybe
elaborate a bit more?
Do you want to avoid intermediary files or have you got s
Carl Eugen Hoyos wrote:
2016-08-08 15:26 GMT+02:00 Peter White :
Carl Eugen Hoyos wrote:
WMP does not support lossless h264.
LOL, another "surprise". ;)
Not really: I forgot to mention that nothing except x264 and FFmpeg
supports lossless h264 afaik, especially no hardware deco
Carl Eugen Hoyos wrote:
2016-08-08 13:43 GMT+02:00 Peter White :
Kieran O Leary wrote:
WMP 12 does not.
What a huge surprise! ;) Of course, WMP won't respect this. It only
tolerates mp4 and other formats with the least amount of effort, so
users don't go running away in masses
Carl Eugen Hoyos wrote:
Hi!
2016-08-08 10:34 GMT+02:00 Peter White :
But for completeness' sake, a command that rotates and compresses the
video losslessly:
$ ffmpeg -i input.mp4 -vf "transpose=2" -c:v libx264 -crf 0 target.mp4
WMP does not support lossless h264.
LOL, an
Kieran O Leary wrote:
On Mon, Aug 8, 2016 at 10:07 AM, Peter White wrote:
$ ffmpeg -i input.mp4 -c copy -metadata:s:v rotate=270 target.mp4
But this obviously needs to be respected by the playback application, so
YMMV. VLC does work with this.
WMP 12 does not.
What a huge surprise! ;) Of
Peter White wrote:
Elie Grouchko wrote:
I have been trying to rotate an mp4 video file on Windows, without
affecting the quality, encoding, etc. ...
I believe that is not possible. At least I cannot think of a way of
doing it without re-encoding.
Huh, apparently it is possible to do this
Elie Grouchko wrote:
> I have been trying to rotate an mp4 video file on Windows, without
> affecting the quality, encoding, etc. ...
I believe that is not possible. At least I cannot think of a way of
doing it without re-encoding.
> ... but the output file is not compatible with WMP.
Yikes! Th
Peter White wrote:
Apparently the -mapping_family option for the libopus encoder ...
Oops, I just now realized that bug reports are supposed to be submitted
to the bug tracker. Sorry about that. I will open a report there.
___
ffmpeg-user mailing
94187 and 81fcd91. But I wouldn't know how to easily find it by
bisecting or any other means, since I could only find two "bad" commits.
I have attached the full output of the two ffmpeg commands above with
-v 9 -loglevel 99 added. I think this way the mail stays reasonably
readable witho
juan carlos Rebate wrote:
2016-08-06 23:21 GMT+02:00 Moritz Barsnick :
On Sat, Aug 06, 2016 at 03:45:04 +0200, juan carlos Rebate wrote:
[libx264 @ 0253a860] kb/s:1030.90
That is less than one percent off your target. And it is to be
expected. That is definetly no bug. Have a read a
Again with the full quote?!
juan carlos Rebate wrote:
2016-08-05 23:07 GMT+02:00 Peter White :
Am 05.08.2016 um 22:29 schrieb juan carlos Rebate:
2016-08-05 21:29 GMT+02:00 Peter White :
juan carlos Rebate wrote:
2016-08-05 19:46 GMT+02:00 Paul B Mahol :
On Friday, August 5, 2016, juan
Am 05.08.2016 um 22:29 schrieb juan carlos Rebate:
2016-08-05 21:29 GMT+02:00 Peter White :
juan carlos Rebate wrote:
2016-08-05 19:46 GMT+02:00 Paul B Mahol :
On Friday, August 5, 2016, juan carlos Rebate wrote:
[...]
Full uncut ffmpeg output missing.
no text in the mail
Oh
, more than 1000 commits
behind current git master. The bug(s) that may be there could well be
fixed in the meantime. So, please try the latest release and, if the
problem persists, the latest git master version.
Peter White
___
ffmpeg-user mailing list
JULIAN GARDNER wrote:
Well I have managed to copy a .ts which has the problem, had to record over 8
hours of tv just for this.
Since you just mentioned it, how do yoou record the files in question,
because to me it looks like the error could just as well happen at that
stage already.
Judging
Alfredo Di Napoli wrote:
> Hey guys,
>
> Suppose I have a media file composed by 1 video stream and 2 audio
> streams (both AAC).
> Is it possible to add metadata at the stream level, for each of the
> two audio?
It most certainly is. But maybe the answer is that it depends.
Apparently the file f
Am 24.07.2016 um 17:16 schrieb Moritz Barsnick:
On Sun, Jul 24, 2016 at 16:49:30 +0200, Peter White wrote:
<(for f in ./*.MOV; do echo "file '$PWD/$f'"; done)
is a very fancy way of saying *.MOV. ;) Essentially that is what
happens there:
ffmpeg -i *.MOV
No, it isn&#x
Mark Strecker wrote:
> Here is the command line we tried originally (this is the one we
intend to
> use and works on Windows ... except the file input of course):
>
> *ffmpeg -safe 0 -analyzeduration 40 -probesize 40 -i
<(for
> f in ./*.MOV; do echo "file '$PWD/$f'"; done) -ma
Jens Kallup wrote:
Hello,
I want to crop down my desktop stream under Linux
ATM: It is 1200x1000x24.
Please open a new topic for this. You just replied to a totally
unrealted message. That's called hijacking and is rather frowned upon.
Also, this is not the first time you did this.
https://ff
André Luís Duarte wrote:
> Hi guys
>
> I am involved with another project in computer forensic where I have
> to prove that several video files are intact (was not added or
> removed content). I thought it would be easy but I'm a little
> difficulty.
I am pretty certain you cannot prove anything
Am 22.07.2016 um 01:58 schrieb davidjesse:
> But I get the following errors when I change the x and y params
>
> drawbox="x=(w-text_w)/2:y=(h-text_h):w=3000:h=10:color=black@1:t=max"
That's because the drawbox filter does not know anything about
text_w or text_h. Also w and h are the desired
Am 21.07.2016 um 18:00 schrieb Konrad Reiche:
> Hi,
>
> the -progress [URI] options allows to post progress metadata to an
> endpoint. The output roughly correlates with the one printed to
> stderr in verbose mode of ffmpeg:
>
I haven't found any documentation either. But here is what I have
gath
Am 21.07.2016 um 04:48 schrieb davidjesse:
> ffmpeg -i myvideo.flv -vf
> drawtext="fontfile=/root/video/Bristol.otf:
> text='Stack Overflow': fontcolor=white: fontsize=24: box=1:
> boxcolor=black@1: x=(w-text_w)/2: y=(h-text_h)/2" -codec:a copy
> output.flv
>
> I want to have a full black backgro
Am 18.07.2016 um 18:51 schrieb Carl Eugen Hoyos:
> Peter White posteo.net> writes:
>
>> So both programs autoselect 320 kbit/s as the nominal
>> bitrate, yet opusenc produces a considerably smaller file.
>
> So you are reporting a bug in opusenc on our mailing list
Am 18.07.2016 um 18:56 schrieb Carl Eugen Hoyos:
> Peter White posteo.net> writes:
>
>> For 6-channel audio the "target" bitrate is 320 kbit/s
>> in both applications.
>
> From a (very) quick look at the source, I don't think this
> is corre
Am 18.07.2016 14:40 schrieb Carl Eugen Hoyos:
> Peter White posteo.net> writes:
>
>> And as far as I can tell, not providing any options should
>> result in the same default setting and hence the same bitrate.
>
> No, this not correct.
>
> If you don't
Dear list,
I have found a curious issue with encoding 6-channel audio using
ffmpeg's libopus encoder. The bitrate is considerably higher than that
produced by opusenc. Please see below.
Both ffmpeg and opusenc use the latest stable release of libopus
1.1.3. And as far as I can tell, not providing
98 matches
Mail list logo
