Re: [FFmpeg-user] libaom - first frame not lossless when > 7 frames in source
Am Sa., 6. Juni 2020 um 21:05 Uhr schrieb Kieran O Leary : > I was doing some tests with libaom and lossness encoding and with synthetic > files and some real world files, I kept finding that the framemd5s for the > first frame was different than the source, but every other libaom encoded > frame produced matching framemd5s for source and output. > I then tried with smaller frame counts, and with synthetic files, I found > that all frames would produce matching framemd5s when there was between 1 > and 7 frames in the input. Once you went to 8 frames and above, the first > frame would produce a framemd5 mismatch. Should be fixed, work-around was to set qmax to 0. Carl Eugen ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
[FFmpeg-user] Determine timecode of errors
Hey ffmpeg-user, when ffmpeg reports errors it looks like this: Error while decoding stream #0:0: Invalid data found when processing input [h264 @ 01d8c0fe9cc0] Invalid NAL unit size (0 > 7208). [h264 @ 01d8c0fe9cc0] Error splitting the input into NAL units. How can I find out what is the timecode for the reported error(s) in streams (audio/video)? Thanks ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] Recorded Frame Timestamps are Inconsistent! How to Fix it?
So I have modified to recording resolution and applied the offset to
capture only the area of interest. It speeds up the capturing of timestamps
and I am getting a timestamp on each frame at an interval of (14ms to
18ms). Which is close to ideal 16.6msec for 60 FPS recording, yet not
accurate enough. Following is the command.
ffmpeg -f gdigrab -framerate 60 -offset_x 550 -offset_y 350 -video_size
640x480 -thread_queue_size 1024 -i desktop -vf "settb=AVTB,
setpts='trunc(PTS/1K)*1K+st(1,trunc(RTCTIME/1K))-1K*trunc(ld(1)/1K)',
drawtext=fontfile=ArialBold.ttf:fontsize=30:fontcolor=white:text='%{localtime}.%{eif\:1M*t-1K*trunc(t*1K)\:d\:3}.%{n}:fontsize=30:r=60:x=(w-tw)/2:
y=h-(2*lh):box=1:boxborderw=20:boxcolor=black@1.0:x=10:y=10'" -c:v
libx264rgb -crf 0 -preset ultrafast ./test_SD_1.mkv
@Marton: Could you please see the above command and let me know how to add
-copyts opinion? Also, when you mentioned the use of '%{pts\:localtime}'
variable expansion, it gives an error of Unterminated %{} near '{pts'. Can
you please help fix the above command?
@Mark: I have tried to modify the setts and setpts options. Below is the
command:
ffmpeg -f gdigrab -framerate 60 -offset_x 550 -offset_y 350 -video_size
640x480 -thread_queue_size 1024 -i desktop -vf "settb=expr=1/72,
setpts=N*12000,fps=60,
drawtext=fontfile=ArialBold.ttf:fontsize=40:fontcolor=white:text='%{localtime}.%{eif\:1M*t-1K*trunc(t*1K)\:d}:box=1:boxborderw=20:boxcolor=black@1.0:x=10:y=10'"
-c:v libx264rgb -crf 0 -preset ultrafast ./test_SD_1.mkv
However, the seconds never increment and the milliseconds loop in three
values 0,333,666. Have a set anything incorrect in the command?.
I have another challenge. I want to record at FPs higher than 60 FPS, i.e.,
120 FPS. For that, i set -framerate 120 and in -vf, I set r=120. However,
the recording that I get is just 60 FPS. Is it because my LCD has a refresh
rate of 60hz? Or FFmpeg is not concerned about LCD hardware? How can I
record at 120 FPS?
Another question is regarding the working of FFmpeg. Suppose, I am
capturing a video from a desktop that is playing at 60 FPS. My frame rate
for capturing is also set at 60 FPS. Is it likely that a frame of video
appears on LCD and the ffmpeg captures it at a delta of almost a full
frame, i.e., ~16. mec ? If so, then isn't recording a 60 FPS video with
-framerate 60 an incorrect choice?
On Mon, Mar 15, 2021 at 10:52 PM Mark Filipak (ffmpeg)
wrote:
> On 2021-03-15 13:43, Hassan wrote:
> > Hello,
> >
> > I am using ffmpeg on a Windows 10 machine and I want to record the
> desktop
> > at a high frame rate while appending accurate timestamps to each frame.
> > I am recording my desktop using the following command:
> >
> > ffmpeg -f gdigrab -framerate 60 -i desktop -vf "settb=AVTB,
> > setpts='trunc(PTS/1K)*1K+st(1,trunc(RTCTIME/1K))-1K*trunc(ld(1)/1K)',
> >
> drawtext=fontfile=ArialBold.ttf:fontsize=40:fontcolor=white:text='%{localtime}.%{eif\:1M*t-1K*trunc(t*1K)\:d}:box=1:boxborderw=20:boxcolor=black@1.0
> :x=10:y=10'"
> > -c:v libx264rgb -crf 0 -preset ultrafast output.mkv
> >
> > The long text next to -vf flag is used to append timestamp (date and
> > current time in milliseconds) on the top left corner of the frame with
> > black background.
> >
> > The issue is that, ideally, when I am recording at 60 FPS, each
> subsequent
> > frame should have a timestamp with an increment of 16.66 msec. However,
> the
> > timestamp is not incremented as such. Instead, it stays the same on a lot
> > of frames and then changes.
> >
> > For example, when I break the video into frames, the frame titled
> > "img0428.png" has the timestamp 18:44:16.828 (hh:mm:ss.millisec)
> > [image: image.png].
> > Then until "next 40 frames, it says the same. On file "img0469.png", the
> > timestamp changes and becomes 18:44:17.510.
> > [image: image.png]
> > So, the timestamp changed after 41 frames and the time difference is 682
> > milliseconds. Ideally, each of the 40 frames between these two frames
> > should carry an incremental timestamp by a step size of 16.66 msec but
> this
> > is not happening.
>
> Hello Hassan,
>
> I don't know anything about 'gdigrab' but I have a lot of experience with
> frame rate manipulation.
>
> "I am recording at 60 FPS..."
> A little higher than 60 fps. Look:
>
> (468 - 428 + 1 frames)/(17510[+/-0.5...] - 16828[+/-0.5...] ms)(1000 ms/s)
> = 60.029 to 60.206 frames/s.
>
> "...with an increment of 16.66 msec."
> The 'gdigrab' timing resolution may not be +/-0.01 ms. For example, it may
> be +/-0.1 ms or even +/-1 ms.
>
> If you can tolerate setting fps to exactly 60 (you're saving video to
> disk, you're not streaming to
> the Internet), put this:
>
> settb=expr=1/72,setpts=N*12000,fps=60,
>
> at the beginning of the filter chain. It will set frame rate to exactly
> 60fps and will also preserve
> excellent timing resolution (0.013[8..] ms) in any succeeding processing
> (without affecting the
> final encoder).
>
> Regards,
> Mark.
>
Re: [FFmpeg-user] Recorded Frame Timestamps are Inconsistent! How to Fix it?
Please do not top-post on this list.
On 3/21/2021 10:31 AM, Hassan wrote:
... Following is the command.
ffmpeg -f gdigrab -framerate 60 -offset_x 550 -offset_y 350 -video_size
640x480 -thread_queue_size 1024 -i desktop -vf "settb=AVTB,
setpts='trunc(PTS/1K)*1K+st(1,trunc(RTCTIME/1K))-1K*trunc(ld(1)/1K)',
drawtext=fontfile=ArialBold.ttf:fontsize=30:fontcolor=white:text='%{localtime}.%{eif\:1M*t-1K*trunc(t*1K)\:d\:3}.%{n}:fontsize=30:r=60:x=(w-tw)/2:
y=h-(2*lh):box=1:boxborderw=20:boxcolor=black@1.0:x=10:y=10'" -c:v
libx264rgb -crf 0 -preset ultrafast ./test_SD_1.mkv
You always need to show the output of the command.
it gives an error of Unterminated %{} near '{pts'. Can
you please help fix the above command?
But it looks like there's a quote nesting error in the drawtext, there's a
end " but not a start.
I have another challenge. I want to record at FPs higher than 60 FPS, i.e.,
120 FPS. For that, i set -framerate 120 and in -vf, I set r=120. However,
the recording that I get is just 60 FPS. Is it because my LCD has a refresh
rate of 60hz? Or FFmpeg is not concerned about LCD hardware? How can I
record at 120 FPS?
Please don't add new questions to a topic, it's better to start a new one.
However, ffmpeg doesn't know about the display hardware, and certainly not
when you're using gdi, but yes, if the HW is a 60fps rate, the display
driver isn't going to render more often since it doesn't need to.
If you _really_ want to capture with accurate timing and at faster than
60fps, use a hardware device like a Blackmagic Decklink or Intensity card
and get the actual output of the graphics card. You will need a second
system to hold the card.
z!
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user
To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] Recorded Frame Timestamps are Inconsistent! How to Fix it?
On 2021-03-21 13:31, Hassan wrote:
@Mark: I have tried to modify the setts and setpts options. Below is the
command:
ffmpeg -f gdigrab -framerate 60 -offset_x 550 -offset_y 350 -video_size
640x480 -thread_queue_size 1024 -i desktop -vf "settb=expr=1/72,
setpts=N*12000,fps=60,
drawtext=fontfile=ArialBold.ttf:fontsize=40:fontcolor=white:text='%{localtime}.%{eif\:1M*t-1K*trunc(t*1K)\:d}:box=1:boxborderw=20:boxcolor=black@1.0:x=10:y=10'"
-c:v libx264rgb -crf 0 -preset ultrafast ./test_SD_1.mkv
However, the seconds never increment and the milliseconds loop in three
values 0,333,666. Have a set anything incorrect in the command?.
Let's get the basics working, eh?
I think '-framerate 60' may not be needed at all.
These: '-offset_x 550 -offset_y 350 -video_size 640x480 -thread_queue_size 1024' can probably be
left out for now.
'drawtext' can be left out for now.
Try this:
ffmpeg -f gdigrab -i desktop -vf "settb=expr=1/72, setpts=N*12000, fps=60" -c:v libx264rgb
-preset ultrafast ./test_SD_1.mkv
See if it works.
I have another challenge. I want to record at FPs higher than 60 FPS, i.e.,
120 FPS. For that, i set -framerate 120 and in -vf, I set r=120. However,
the recording that I get is just 60 FPS. Is it because my LCD has a refresh
rate of 60hz? Or FFmpeg is not concerned about LCD hardware? How can I
record at 120 FPS?
Another question is regarding the working of FFmpeg. Suppose, I am
capturing a video from a desktop that is playing at 60 FPS. My frame rate
for capturing is also set at 60 FPS. Is it likely that a frame of video
appears on LCD and the ffmpeg captures it at a delta of almost a full
frame, i.e., ~16. mec ? If so, then isn't recording a 60 FPS video with
-framerate 60 an incorrect choice?
On Mon, Mar 15, 2021 at 10:52 PM Mark Filipak (ffmpeg)
wrote:
On 2021-03-15 13:43, Hassan wrote:
Hello,
I am using ffmpeg on a Windows 10 machine and I want to record the
desktop
at a high frame rate while appending accurate timestamps to each frame.
I am recording my desktop using the following command:
ffmpeg -f gdigrab -framerate 60 -i desktop -vf "settb=AVTB,
setpts='trunc(PTS/1K)*1K+st(1,trunc(RTCTIME/1K))-1K*trunc(ld(1)/1K)',
drawtext=fontfile=ArialBold.ttf:fontsize=40:fontcolor=white:text='%{localtime}.%{eif\:1M*t-1K*trunc(t*1K)\:d}:box=1:boxborderw=20:boxcolor=black@1.0
:x=10:y=10'"
-c:v libx264rgb -crf 0 -preset ultrafast output.mkv
The long text next to -vf flag is used to append timestamp (date and
current time in milliseconds) on the top left corner of the frame with
black background.
The issue is that, ideally, when I am recording at 60 FPS, each
subsequent
frame should have a timestamp with an increment of 16.66 msec. However,
the
timestamp is not incremented as such. Instead, it stays the same on a lot
of frames and then changes.
For example, when I break the video into frames, the frame titled
"img0428.png" has the timestamp 18:44:16.828 (hh:mm:ss.millisec)
[image: image.png].
Then until "next 40 frames, it says the same. On file "img0469.png", the
timestamp changes and becomes 18:44:17.510.
[image: image.png]
So, the timestamp changed after 41 frames and the time difference is 682
milliseconds. Ideally, each of the 40 frames between these two frames
should carry an incremental timestamp by a step size of 16.66 msec but
this
is not happening.
Hello Hassan,
I don't know anything about 'gdigrab' but I have a lot of experience with
frame rate manipulation.
"I am recording at 60 FPS..."
A little higher than 60 fps. Look:
(468 - 428 + 1 frames)/(17510[+/-0.5...] - 16828[+/-0.5...] ms)(1000 ms/s)
= 60.029 to 60.206 frames/s.
"...with an increment of 16.66 msec."
The 'gdigrab' timing resolution may not be +/-0.01 ms. For example, it may
be +/-0.1 ms or even +/-1 ms.
If you can tolerate setting fps to exactly 60 (you're saving video to
disk, you're not streaming to
the Internet), put this:
settb=expr=1/72,setpts=N*12000,fps=60,
at the beginning of the filter chain. It will set frame rate to exactly
60fps and will also preserve
excellent timing resolution (0.013[8..] ms) in any succeeding processing
(without affecting the
final encoder).
Regards,
Mark.
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user
To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] Recorded Frame Timestamps are Inconsistent! How to Fix it?
Am So., 21. März 2021 um 22:13 Uhr schrieb Mark Filipak (ffmpeg) : > I think '-framerate 60' may not be needed at all. It is only needed if 60fps recording is wanted. As said before, setpts should generally be avoided and this is even more true for settb. If you have to smooth timestamps, use the fps filter or the ffmpeg option -r. Carl Eugen ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
[FFmpeg-user] filter script file
Is the format of a filter script file documented anywhere? I can't find any. Working command is: ffmpeg -i source.mkv -filter_script:v test.filter_script -map 0 -codec:v libx265 -codec:a copy -codec:s copy -dn test.mkv If the test.filter_script file contains this: settb=expr=1/72,setpts=N*24024,fieldmatch,yadif=deint=interlaced,telecine=pattern=4 it works, but if the test.filter_script file contains this: settb=expr=1/72,setpts=N*24024,fieldmatch, \ yadif=deint=interlaced,telecine=pattern=4 the transcode fails. [AVFilterGraph @ 027205e29d80] No such filter: ' yadif' Obviously, the ' \' isn't working. ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] Recorded Frame Timestamps are Inconsistent! How to Fix it?
On 2021-03-21 17:50, Carl Eugen Hoyos wrote: Am So., 21. März 2021 um 22:13 Uhr schrieb Mark Filipak (ffmpeg) : I think '-framerate 60' may not be needed at all. It is only needed if 60fps recording is wanted. As said before, setpts should generally be avoided and this is even more true for settb. Serious questions: 'setpts=N/FR/TB' seems to be reliable, and is the only way I've gotten some of my frame gymnastics to work. What is wrong/dangerous about 'setpts"? Note: I'm aware that frames can be out-of-order for some input streams (e.g. mpeg2video) but they seem to be in-order in the frame pipeline. Is there some reason to *not* take advantage of that? 'settb=expr=1/72' seems to be pretty useful for improving the timing resolution of the filter pipeline. Why do you think it should be avoided? Regards, and Much Thanks, Mark. ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] Recorded Frame Timestamps are Inconsistent! How to Fix it?
Am So., 21. März 2021 um 23:31 Uhr schrieb Mark Filipak (ffmpeg) : > > On 2021-03-21 17:50, Carl Eugen Hoyos wrote: > > Am So., 21. März 2021 um 22:13 Uhr schrieb Mark Filipak (ffmpeg) > > : > > > >> I think '-framerate 60' may not be needed at all. > > > > It is only needed if 60fps recording is wanted. > > As said before, setpts should generally be avoided and > > this is even more true for settb. > > Serious questions: > > 'setpts=N/FR/TB' seems to be reliable, and is the only way > I've gotten some of my frame gymnastics to work. Serious question: What does this tell you? > What is wrong/dangerous about 'setpts"? I can only work for input that is strictly cfr, this is typically not true for screen recordings. Carl Eugen ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] Recorded Frame Timestamps are Inconsistent! How to Fix it?
On 2021-03-21 18:36, Carl Eugen Hoyos wrote: Am So., 21. März 2021 um 23:31 Uhr schrieb Mark Filipak (ffmpeg) : On 2021-03-21 17:50, Carl Eugen Hoyos wrote: Am So., 21. März 2021 um 22:13 Uhr schrieb Mark Filipak (ffmpeg) : I think '-framerate 60' may not be needed at all. It is only needed if 60fps recording is wanted. As said before, setpts should generally be avoided and this is even more true for settb. Serious questions: 'setpts=N/FR/TB' seems to be reliable, and is the only way I've gotten some of my frame gymnastics to work. Serious question: What does this tell you? You are "answering" a question with a question. I don't know what your "answer" means. What is wrong/dangerous about 'setpts"? I can only work for input that is strictly cfr,... Of course, that's true. ...this is typically not true for screen recordings. What are "screen recordings"? ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] Recorded Frame Timestamps are Inconsistent! How to Fix it?
Am So., 21. März 2021 um 23:55 Uhr schrieb Mark Filipak (ffmpeg) : > > On 2021-03-21 18:36, Carl Eugen Hoyos wrote: > > Am So., 21. März 2021 um 23:31 Uhr schrieb Mark Filipak (ffmpeg) > > : > >> > >> On 2021-03-21 17:50, Carl Eugen Hoyos wrote: > >>> Am So., 21. März 2021 um 22:13 Uhr schrieb Mark Filipak (ffmpeg) > >>> : > >>> > I think '-framerate 60' may not be needed at all. > >>> > >>> It is only needed if 60fps recording is wanted. > > > >>> As said before, setpts should generally be avoided and > >>> this is even more true for settb. > >> > >> Serious questions: > >> > >> 'setpts=N/FR/TB' seems to be reliable, and is the only way > >> I've gotten some of my frame gymnastics to work. > > > > Serious question: > > What does this tell you? > > You are "answering" a question with a question. This is clearly a "lie" to quote another contributor ;-) > I don't know what your "answer" means. It was a (too?) subtle way to indicate that what you try to do makes no sense. > >> What is wrong/dangerous about 'setpts"? > > > > I can only work for input that is strictly cfr,... > > Of course, that's true. > > >...this is typically not true for screen recordings. > What are "screen recordings"? The topic of this mailing list thread. Carl Eugen ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] Determine timecode of errors
On 2021-03-21 05:04, Er Win wrote: Hey ffmpeg-user, when ffmpeg reports errors it looks like this: Error while decoding stream #0:0: Invalid data found when processing input [h264 @ 01d8c0fe9cc0] Invalid NAL unit size (0 > 7208). [h264 @ 01d8c0fe9cc0] Error splitting the input into NAL units. How can I find out what is the timecode for the reported error(s) in streams (audio/video)? Have you tried 'verbose' or 'debug' reporting? I don't know whether they would report the timecodes but it's worth a try, eh? -- Mars? We can't live there! Mars is fatal: no magnetosphere to deflect cosmic rays. A tropical sunshade orbiting Earth would work. It's the only way. We need to start construction now. Forget Mars. ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] filter script file
Mark Filipak (ffmpeg) wrote > Is the format of a filter script file documented anywhere? I can't find > any. > > Working command is: > > ffmpeg -i source.mkv -filter_script:v test.filter_script -map 0 -codec:v > libx265 -codec:a copy > -codec:s copy -dn test.mkv > > If the test.filter_script file contains this: > > settb=expr=1/72,setpts=N*24024,fieldmatch,yadif=deint=interlaced,telecine=pattern=4 > > it works, but if the test.filter_script file contains this: > > settb=expr=1/72,setpts=N*24024,fieldmatch, \ > yadif=deint=interlaced,telecine=pattern=4 > > the transcode fails. > > [AVFilterGraph @ 027205e29d80] No such filter: ' > yadif' > > Obviously, the ' \' isn't working. On windows, for a text file, you don't need a carriage return or line break character - just hit enter (remove the "\") -- Sent from: http://ffmpeg-users.933282.n4.nabble.com/ ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] Recorded Frame Timestamps are Inconsistent! How to Fix it?
On 2021-03-21 19:01, Carl Eugen Hoyos wrote: Am So., 21. März 2021 um 23:55 Uhr schrieb Mark Filipak (ffmpeg) : On 2021-03-21 18:36, Carl Eugen Hoyos wrote: Am So., 21. März 2021 um 23:31 Uhr schrieb Mark Filipak (ffmpeg) : On 2021-03-21 17:50, Carl Eugen Hoyos wrote: Am So., 21. März 2021 um 22:13 Uhr schrieb Mark Filipak (ffmpeg) : I think '-framerate 60' may not be needed at all. It is only needed if 60fps recording is wanted. As said before, setpts should generally be avoided and this is even more true for settb. Serious questions: 'setpts=N/FR/TB' seems to be reliable, and is the only way I've gotten some of my frame gymnastics to work. Serious question: What does this tell you? You are "answering" a question with a question. This is clearly a "lie" to quote another contributor ;-) I don't know to what you refer. Are you making a joke? I don't know what your "answer" means. It was a (too?) subtle way to indicate that what you try to do makes no sense. 'setpts' exists. It makes sense to me -- and it works. I'm sure it made sense to the person who wrote the 'setpts' filter. Why does it make no sense to you? What is wrong/dangerous about 'setpts"? I can only work for input that is strictly cfr,... Of course, that's true. ...this is typically not true for screen recordings. What are "screen recordings"? The topic of this mailing list thread. Oh! Thanks. I thought the OP was asking about camera output. My bad. ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
[FFmpeg-user] sytraming AAC+
I am getting... [rtp @ 0x55e52ffe8c00] AAC with no global headers is currently not supported. SDP: with ffmpeg -i http://localhost:8000/wireless.aacp -acodec copy -vn -flags +global_header -f rtp rtp://192.168.1.100:7001 is there support for aac coming? regards Robert ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
[FFmpeg-user] Mystery error initializing complex filters -- bug?
Hi All, A little help, please. Using the latest git source, using '-filter_complex_script', I get a mystery error. I have checked the filter_complex_script: 23fps.ffmpeg.filter.txt, for errors. Especially I've checked that every input pad (especially [AA1]) has one and only one matching output pad, and that every output pad (especially [AA1]) has one and only one matching input pad. Can you suggest any other checks or should I file a bug now? Thanks Much! Mark. Contents: command line debug level report filter_complex_script === command line === ffmpeg -i "THE LAST EMPEROR.excerpt.24fps.mkv" -filter_complex_script 23fps.ffmpeg.filter.txt -map 0 -codec:v libx265 -x265-params crf=16:qcomp=1.00 -codec:a copy -codec:s copy -dn "THE LAST EMPEROR.excerpt.60fps.mkv" === debug level report === ffmpeg started on 2021-03-22 at 01:30:30 Report written to "ffmpeg-20210322-013030.log" Log level: 48 Command line: ffmpeg -i "THE LAST EMPEROR.excerpt.24fps.mkv" -filter_complex_script 23fps.ffmpeg.filter.txt -map 0 -codec:v libx265 -x265-params "crf=16:qcomp=1.00" -codec:a copy -codec:s copy -dn "THE LAST EMPEROR.excerpt.60fps.mkv" ffmpeg version N-101658-g75fd3e1519 Copyright (c) 2000-2021 the FFmpeg developers built with gcc 9.3-win32 (GCC) 20200320 configuration: --prefix=/ffbuild/prefix --pkg-config-flags=--static --pkg-config=pkg-config --cross-prefix=x86_64-w64-mingw32- --arch=x86_64 --target-os=mingw32 --enable-gpl --enable-version3 --disable-debug --disable-w32threads --enable-pthreads --enable-iconv --enable-zlib --enable-libxml2 --enable-libfreetype --enable-libfribidi --enable-gmp --enable-lzma --enable-fontconfig --enable-opencl --enable-libvmaf --enable-vulkan --enable-libvorbis --enable-amf --enable-libaom --enable-avisynth --enable-libdav1d --enable-libdavs2 --enable-ffnvcodec --enable-cuda-llvm --enable-libglslang --enable-libgme --enable-libass --enable-libbluray --enable-libmp3lame --enable-libopus --enable-libtheora --enable-libvpx --enable-libwebp --enable-lv2 --enable-libmfx --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-librav1e --enable-librubberband --enable-schannel --enable-sdl2 --enable-libsoxr --enable-libsrt --enable-libsvtav1 --enable-libtwolame --enable-libuavs3d --enable-libvidstab --e libavutil 56. 71.100 / 56. 71.100 libavcodec 58.135.100 / 58.135.100 libavformat58. 77.100 / 58. 77.100 libavdevice58. 14.100 / 58. 14.100 libavfilter 7.111.100 / 7.111.100 libswscale 5. 10.100 / 5. 10.100 libswresample 3. 10.100 / 3. 10.100 libpostproc55. 10.100 / 55. 10.100 Splitting the commandline. Reading option '-i' ... matched as input url with argument 'THE LAST EMPEROR.excerpt.24fps.mkv'. Reading option '-filter_complex_script' ... matched as option 'filter_complex_script' (read complex filtergraph description from a file) with argument '23fps.ffmpeg.filter.txt'. Reading option '-map' ... matched as option 'map' (set input stream mapping) with argument '0'. Reading option '-codec:v' ... matched as option 'codec' (codec name) with argument 'libx265'. Reading option '-x265-params' ... matched as AVOption 'x265-params' with argument 'crf=16:qcomp=1.00'. Reading option '-codec:a' ... matched as option 'codec' (codec name) with argument 'copy'. Reading option '-codec:s' ... matched as option 'codec' (codec name) with argument 'copy'. Reading option '-dn' ... matched as option 'dn' (disable data) with argument '1'. Reading option 'THE LAST EMPEROR.excerpt.60fps.mkv' ... matched as output url. Finished splitting the commandline. Parsing a group of options: global . Applying option filter_complex_script (read complex filtergraph description from a file) with argument 23fps.ffmpeg.filter.txt. [file @ 020aba1a6440] Setting default whitelist 'file,crypto,data' [AVIOContext @ 020aba1aef40] Statistics: 1952 bytes read, 0 seeks Successfully parsed a group of options. Parsing a group of options: input url THE LAST EMPEROR.excerpt.24fps.mkv. Successfully parsed a group of options. Opening an input file: THE LAST EMPEROR.excerpt.24fps.mkv. [NULL @ 020ab89d9c80] Opening 'THE LAST EMPEROR.excerpt.24fps.mkv' for reading [file @ 020ab89da3c0] Setting default whitelist 'file,crypto,data' [matroska,webm @ 020ab89d9c80] Format matroska,webm probed with size=2048 and score=100 [matroska,webm @ 020ab89d9c80] Unknown entry 0x22B59D at pos. 4397 [matroska,webm @ 020ab89d9c80] Unknown entry 0x22B59D at pos. 4461 [matroska,webm @ 020ab89d9c80] Unknown entry 0x22B59D at pos. 4519 [matroska,webm @ 020ab89d9c80] Unknown entry 0x22B59D at pos. 4573 [matroska,webm @ 020ab89d9c80] Unknown entry 0x447B at pos. 65913312 [matroska,webm @ 020ab89d9c80] Unknown entry 0x447B at pos. 65913358 [matroska,webm @ 020ab89d9c80] Unknown entry 0x447B at pos. 65913397 [matroska,webm @ 020ab89d9c80] Unknown entry 0x447B at pos. 65913440 [matroska,webm @ 020ab89d9c80]
