I'm not sure if it is a problem with bmpx or gstreamer, but it sucks. ;) When I enable the stream useflag of media-sound/bmpx and try to play radio streams I get following error message for example. ERROR [Element: src] (E202) Couldn't open the stream/track Current URI: http://64.62.252.130:8070 Detailed debugging information: gstgnomevfssrc.c(839): gst_gnome_vfs_src_start (): /pipeline_http/src: Could not open vfs file "http://64.62.252.130:8070/" for reading: Generic error If I disable the stream useflag, does it work at least with a few radio streams.
gst-plugins-neon-0.10.3 in portage (and upstream) is too old for BMPx, i'm glad it works for you. USE="stream" switches default stream plugin to gst-plugins-gnomevfs because it worked for me (and majority of people I've heard). So we are waiting for new -neon release.. ..unless you have time to create a patch from gstreamer CVS for neon plugin upgrade (all changes effecting stability without forgetting new neon support which I have allready patched). *wink*
I don't understand, what for should I create a patch? Can I not use the cvs version of gst-plugins-neon with bmpx, yet? I rembered that I did it in the past with a former version of gst-plugins-neon. Another question; if gst-plugins-gnomevfs is working so well, why didn't you decide to keep it instead of planning to go back to gst-plugins-neon? If it would be more reasonable to keep gst-plugins-gnomevfs, I would prefer to fix the bug, I had to note with it, instead of make gst-plugins-neon (which btw already works for me) work, like you proposed.
