[gst-devel] Trouble with giostreamsrc

[W. Michael Petullo]

>>>> That's a different bug, not sure where :) For some reason decodebin
>>>> tries to link a million id3demux elements...
>>>>
>>>> Could you file a bug for this?
>>>
>>> ...if it doesn't work after this change:
>>>
>>> commit b9c79380aa07e3cf2c00a190bbbcb0b0c252df96
>>> Author: Sebastian Dröge <sebastian.droege at collabora.co.uk>
>>> Date:   Thu Jul 9 13:45:13 2009 +0200
>>>
>>>    gio: Make sure that we have the correct stream position when
>>> starting
>>>
>>> Note that your application blocks forever after the pipeline has
>>> finished because of no bus usage, etc :)
>>
>> The above change fixed all of my problems. I misread your note above,
>> so I filed bug. I thought you wanted one filed for the purpose of the
>> release notes (generally Bugzilla is cited in the change log). The
>> following bug exists for Sebastian's review and should be closed after
>> you read it:
>>
>> https://bugzilla.gnome.org/show_bug.cgi?id=588205
>
> That's nice to hear :)
>
> Why exactly are you using the giostreamsrc and a custom GInputStream
> btw?

I just refactored my media server (dmapd / libdmapsharing) and found that
using giostreamsrc instead of giosrc was more convenient. This allows my
media database to provide a GInputStream that libdmapsharing can then
either send directly with libsoup or inject a transcoding pipeline before
sending. In my case, moving the transcoding process from the media
database (that has no itea of what type of client is connecting) to
libdmapsharing (which does) is very beneficial.

Mike