On 2025-03-01 11:28, BloodMan wrote:
I suspect colorspace, so try explicitly set on input (or convert)
colorspace maybe... There is a lot of options -vf, -pix_fmt, -sws_flags
etc. you can test - find them on ffmpeg wiki here
https://trac.ffmpeg.org/wiki/colorspace
Finally, managed to get
Hi Vlad,
W dniu 2025-03-01 o 08:35, Vladimir Mishonov via ffmpeg-user pisze:
On 2025-03-01 00:36, Vladimir Mishonov via ffmpeg-user wrote:
On 2025-02-28 23:26, BloodMan wrote:
Hi Vladimir,
I see on previous posts that resolutions are different, but also
frame rates are different and colour s
On 2025-03-01 00:36, Vladimir Mishonov via ffmpeg-user wrote:
On 2025-02-28 23:26, BloodMan wrote:
Hi Vladimir,
I see on previous posts that resolutions are different, but also frame
rates are different and colour spaces (bt709 vs "") are different.
Are you really sure the problem is the res
Hi Vladimir,
W dniu 2025-02-28 o 20:21, Vladimir Mishonov via ffmpeg-user pisze:
ffmpeg \
-hwaccel vaapi -hwaccel_output_format vaapi -i rtmp://localhost/stream1 \
-hwaccel vaapi -hwaccel_output_format vaapi -i rtmp://localhost/stream2 \
-filter_complex "[0:v][1:v]overlay_vaapi=w=500" \
On 2025-02-28 23:26, BloodMan wrote:
Hi Vladimir,
W dniu 2025-02-28 o 20:21, Vladimir Mishonov via ffmpeg-user pisze:
ffmpeg \
-hwaccel vaapi -hwaccel_output_format vaapi -i
rtmp://localhost/stream1 \
-hwaccel vaapi -hwaccel_output_format vaapi -i
rtmp://localhost/stream2 \
-filter_com
On 2025-02-28 22:00, Dragan Randjelovic wrote:
Hi Vladimir,
I have noticed that you were strugling, try using the following:
scale_vaapi=w=-1:h=-1 ensures hardware scaling before overlay (source
resolution is kept with -1)
Thank you for your reply. I'm verry sorry to say, however, that it
On 2025-02-28 19:53, Greg Oliver wrote:
On Thu, Feb 27, 2025 at 11:49 PM Vladimir Mishonov via ffmpeg-user <
ffmpeg-user@ffmpeg.org> wrote:
Sorry - that link I referenced actually did not have the whole thread.
The
piece I intended to be included was:
https://lists.ffmpeg.org/pipermail/ffmp
On Thu, Feb 27, 2025 at 11:49 PM Vladimir Mishonov via ffmpeg-user <
ffmpeg-user@ffmpeg.org> wrote:
> On 2025-02-28 02:36, Greg Oliver wrote:
>
> > On Thu, Feb 27, 2025 at 11:25 AM Vladimir Mishonov via ffmpeg-user <
> > ffmpeg-user@ffmpeg.org> wrote:
> >
> >
> > https://ffmpeg.org/pipermail/ffmpe
On 2025-02-28 02:36, Greg Oliver wrote:
On Thu, Feb 27, 2025 at 11:25 AM Vladimir Mishonov via ffmpeg-user <
ffmpeg-user@ffmpeg.org> wrote:
https://ffmpeg.org/pipermail/ffmpeg-user/2024-August/058638.html
Thanks for the link. Unfortunately, that seems to be only tangentially
related to my
On Thu, Feb 27, 2025 at 11:25 AM Vladimir Mishonov via ffmpeg-user <
ffmpeg-user@ffmpeg.org> wrote:
> So, I've managed to figure out that this may be related to input streams
> having different resolutions.
>
https://ffmpeg.org/pipermail/ffmpeg-user/2024-August/058638.html
> In the meantime, I
On Feb 27, 2025, at 11:25 AM, Vladimir Mishonov via ffmpeg-user
wrote:
>
> Mea Culpa, this was not intended for the list of course.
>
>
> Bouke
>
Ua culpa, huh? I don't know which the list aficionados consider more offensive,
posting by accident or top-posting in the accidental posts.
Your
So, I've managed to figure out that this may be related to input streams
having different resolutions.
In the meantime, I've also switched to VA-API because it seems more
stable on my system, and uses less CPU. (No idea why it uses CPU at all,
shouldn't it use GPU? The gputop utility does conf
Greetings everyone.
I am attempting to overlay 2 video streams in real-time with QuickSync
hardware acceleration. I want to use both hardware decode and encode to
make the most use out of the GPU and avoid excessive CPU usage.
I've found an example command-line here:
https://github.com/intel
13 matches
Mail list logo
