Quoting Marton Balint (2024-02-04 11:11:12) > > The 'pipe:' output can be used with a real video player such as mpv, vlc, or > > even ffplay. For cases where the user was an application using the API they > > should supply their own renderer. > > Yeah, but I never liked when people piped uncompressed data... Not > everything that the devices support can be serialized,
For instance? What do these devices support that e.g. NUT does not? > it is extra CPU, latency of the receiving app reading from pipe is a > question... People keep saying this in defence of these devices, but never support such claims with any data. I have doubts this is an actual problem in practice. > I'd be a lot more happy with this if we'd offer some replacement which has > no issues. Maybe a libplacebo based outdev. I don't think it's possible to have such a replacement, neither should we try. Muxer API is simply the wrong abstraction for playback. -- Anton Khirnov _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
