Hi Brian, I've tested the Fluendo plugins on my OpenSolaris box here with Totem/Rhythmbox/Elisa (removed the FFmpeg one). All of them work great with playing the audio/video streaming.
Need to do a correction for my last post about transcoding of Coherence. Coherence doesn't depend on the FFmpeg plugins of GStreamer. The current Coherence code implements mp4 transcoder, which depends on the qtdemux element of gst-plugins-good and h264parse/mp4mux elements of gst-plugins-bad 0.10.10. The GStremaer pipeline looks like "$file ! qtdemux name=d ! queue ! h264parse ! mp4mux name=mux d. ! queue ! mux.". As we can see, coherence doesn't do decoding/encoding, demux/mux are involved. For audio transcoding, the GStreamer lame element was used. But all the audio transcoding part is disabled in the current code. I've sent email to the upstream community for further information. Is it possible that Fluendo could provide similar codecs as h264parse (Parses raw h264 stream)/mp4mux (should be the part to mux the mp4 audio/video) do? Are there any replacement for them? Thanks for the updates for the one-pager. Best Regards, -Alfred Brian Cameron wrote: > Alfred: > > Please test the Fluendo plugins and verify that programs like totem, > rhythmbox and elisa work well with them. In a separate email, I > provided you information about how to test with Fluendo's plugins. > So, hopefully you can respond with the results after testing. > > Also, make sure to remove FFmpeg from your system. It's better > to use the Fluendo plugins than to use FFmpeg. > >>> I wouldn't think there would be any special relationship between >>> coherence and GStreamer. Aside from the fact that some media >>> programs like totem, rhythmbox and elisa pull data from UPnP >>> servers and play them via a GStreamer pipeline. >> The Coherence transcoder depends on GStreamer as I can tell from the >> source code. And Coherence implements the transcoding via gst-python. >> Guess we'll have to include the ARC case gst-python (PSARC/2008/105) in >> the "Imported Interface" table. > > I added this to the Imported interfaced table, and a comment to the end > of section 4.1 to explain the gst-python dependency. I also updated > the package names in the Exported Interface table to highlight that > we will deliver Python 2.4 bindings in the SUNWpython24-coherence > package and the 2.6 bindings in the SUNWpython26-coherence package, > to be consistent with our normal package naming for Python modules.
