Quoting Niklas Haas (2024-04-24 12:51:55)
> Incidentally, I think it would be nice if lavfi could *automatically*
> split filter links referenced multiple times, so we could just write
> e.g. [i][ri]scale=rw:rh[o]; [ri][o]overlay[out] and have it work. Maybe
> I'll try getting that to work, next.
On Wed, 24 Apr 2024 12:51:55 +0200 Niklas Haas wrote:
> As discussed in my previous series for fixing scale2ref[1], this filter
> is fundamentally broken, and the only real fix would be to switch to
> activate(), or ideally FFFrameSync.
>
> [1] https://ffmpeg.org//pipermail/ffmpeg-devel/2024-Marc
On Wed, 24 Apr 2024 16:48:54 +0530 Gyan Doshi wrote:
>
>
> On 2024-04-24 04:21 pm, Niklas Haas wrote:
> > As discussed in my previous series for fixing scale2ref[1], this filter
> > is fundamentally broken, and the only real fix would be to switch to
> > activate(), or ideally FFFrameSync.
> >
>
On 24/04/2024 13:18, Gyan Doshi wrote:
On 2024-04-24 04:21 pm, Niklas Haas wrote:
As discussed in my previous series for fixing scale2ref[1], this filter
is fundamentally broken, and the only real fix would be to switch to
activate(), or ideally FFFrameSync.
[1] https://ffmpeg.org//pipermail/
On 2024-04-24 04:21 pm, Niklas Haas wrote:
As discussed in my previous series for fixing scale2ref[1], this filter
is fundamentally broken, and the only real fix would be to switch to
activate(), or ideally FFFrameSync.
[1] https://ffmpeg.org//pipermail/ffmpeg-devel/2024-March/323382.html
Th
As discussed in my previous series for fixing scale2ref[1], this filter
is fundamentally broken, and the only real fix would be to switch to
activate(), or ideally FFFrameSync.
[1] https://ffmpeg.org//pipermail/ffmpeg-devel/2024-March/323382.html
The main thing making this difficult is the fact t
