You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd be very against merging use of ffmpeg (etc) into core; the idea of supporting that on most systems gives me the shivers. I suspect this is a case where a third-party hosted service or an external plugin could do the gruntwork, and then post into the Known stream via integration or webhook.
Fair point. My understanding of this ticket was that we were talking about spinning out Video into its separate third party plugin (rather than having it as a legacy feature / easter egg in Audio). Since video is still something that requires transcoding (although browser support is getting better) it makes sense to bundle ffmpeg into that video plugin and make that "complete", but to not necessarily support it ourselves.
Video is, of course, much much much harder to implement.
But these two media types have very different needs and should be two different plugins.
The text was updated successfully, but these errors were encountered: