> hi, out of curiosity, why one would need to probe (with crazy 100M
probesize) x11 capture and why to use 5.1 on 1080p@24 when 4.2 would be
enough ?
Because this is a generic script not limited to 1080p. That way I can
use it for 4k as well what is not possible with level 4.2.
Furthermore, with
I don't have vulkan here but that's what I use with QSV. Maybe it is
an inspiration to you:
ffmpeg -video_size "$resolution"\
¦ ¦ -loglevel warning \
¦ ¦ -probesize 100M \
¦ ¦ -framerate 25 \
¦ ¦ -thread_queue_size 1024 \
¦ ¦ -init_hw_device
fer -flags low_delay rtmp://localhost/live`
reacts almost instantly I suspect the issue not to be with nginx but
the time-stamp handling of ffmpeg.
Any suggestions are warmly welcomed!
Thanks a lot!
Stephan
Am So., 8. Nov. 2020 um 21:46 Uhr schrieb Stephan Monecke
:
>
> Good evening t
Good evening together,
I have another audio-sync question where we're out of ideas.
We get an rtsp-Stream and mix it together with line-in over pulseaudio.
This looks something like:
ffmpeg \
-use_wallclock_as_timestamps 1 -fflags +genpts \
-max_delay 200 -thread_queue_size 1024
Hi,
does anyone know where I can find a complete command argument
reference for the h264_qsv encoder?
E.g. `-global_quality` as one of the main parameters is not present in
`fmpeg -h encoder=h264_qsv`.
Thanks a lot!
Cheers,
Stephan
___
ffmpeg-user
Good morning,
yesterday evening, the following command crashed (allways but once!) with
[Parsed_vpp_qsv_2 @ 0x563c3523f780] Can't allocate a surface
as long as the vpp_qsv filter was present:
ffmpeg -init_hw_device qsv=hw -filter_hw_device hw -i 'rtsp://url'
-vf
\
-f flv
outfile.flv
Thanks a lot!
Am Do., 4. Juni 2020 um 17:11 Uhr schrieb Stephan Monecke
:
>
> Hi together,
>
>
> I have a weak computer (i3 something) connected to a HDMI-grabber
> (Magewell USB Capture HDMI PLUS, acts like a webcam) and audio via
> line o
Hi together,
I have a weak computer (i3 something) connected to a HDMI-grabber
(Magewell USB Capture HDMI PLUS, acts like a webcam) and audio via
line over the microphone port.
I want to merge those two streams together with as little audio-video
offset as possible and as light as possible on
Have a look at the "-itsoffset" parameter for constant delays.
Also you might want to drop the "-re" [1].
[1] https://trac.ffmpeg.org/wiki/StreamingGuide#The-reflag
Best regards,
Stephan Monecke
--
Sent from my mobile device. Please excuse my brevity.
Am 9. Mai 2020 09:14
ly segfaults for me with
a freshly compiled ffmpeg.
Am Mo., 27. Apr. 2020 um 20:50 Uhr schrieb Stephan Monecke
:
>
> That looks really interesting! Thanks a lot, I'll have a look at it!
>
> Besides daily checking, I managed to overlook ALL the replies ... sorry for
> my late answer a
).
They are present in abundance at the institute and the setup is practically
free of cpu usage even on this weak machine.
That way, the lecturer can switch between blackboards / cameras and fully
control the procedure just via the presenter.
Best regards,
Stephan Monecke
--
Sent from my mobile
Hey!
I have two identical rtsp video-sources stream1, stream2 and an audio
source. I currently merge stream1 with the audio for a rtmp-server
using:
stream1="rtsp://streamurl1"
/usr/bin/ffmpeg\
[...]
-i "$stream1" \
[...]
-itsoffset
12 matches
Mail list logo