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
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
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
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
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
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
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
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
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
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:
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
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,
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,
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
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
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
16 matches
Mail list logo