On Di, 2014-08-12 at 11:50 +0300, Martin-Éric Racine wrote: > 2014-08-12 10:52 GMT+03:00 Sebastian Dröge <sl...@coaxion.net>: > > On Di, 2014-08-12 at 10:46 +0300, Martin-Éric Racine wrote: > >> 2014-08-12 10:29 GMT+03:00 Sebastian Dröge <sl...@coaxion.net>: > >> > On Di, 2014-08-12 at 10:13 +0300, Martin-Éric Racine wrote: > >> >> 2014-08-12 10:10 GMT+03:00 Sebastian Dröge <sl...@coaxion.net>: > >> >> > On Di, 2014-08-12 at 09:26 +0300, Martin-Éric Racine wrote: > >> >> >> Package: gstreamer0.10-ffmpeg > >> >> >> Version: 0.10.13-5 > >> >> >> Followup-For: Bug #742037 > >> >> >> > >> >> >> Jessie will ship with Iceweasel (>= 30) which has Gstreamer 1.0 > >> >> >> support. > >> >> >> Thus, would a solution be to concentrate FFMPEG porting efforts on > >> >> >> 1.0, > >> >> >> rather than on 0.10 Gstreamer? Can we produce 1.0 modules with new > >> >> >> AV? > >> >> > > >> >> > Yes, see the gstreamer1.0-libav package. > >> >> > >> >> Is there anything preventing us from building gstreamer1.0-ffmpeg > >> >> packages then? > >> > > >> > You mean building gst-libav against ffmpeg instead of libav? No, unless > >> > ffmpeg has a different API than libav v10 there should be no problem. > >> > >> Not quite what I meant. > >> > >> We currently have a Gstreamer0.10-ffmpeg that is stuck in Sid because > >> it won't build against recent libav. Do we have something to produce a > >> Gstreamer1.0-ffmpeg against current libav? There's hardly any software > >> that explictly needs Gstreamer 0.10 left in Jessie, so we could pretty > >> much let the whole Gstreamer 0.10 stack go, if that's the case. > > > > gstreamer1.0-libav is exactly what you mean then. It's just renamed from > > -ffmpeg to -libav as upstream also switched to libav as default. > > OK. Good to know. > > Is it a drop-in replacement for the older -ffmpeg? i.e. will Iceweasel > be able to play H.264 media content with it?
Yes
signature.asc
Description: This is a digitally signed message part
