gstreamer-1.0.5 & shout2send

[Bill Blue]

On Wednesday 03/06/2013 at 14:42:47, Tim-Philipp Müller  wrote:
> On Wed, 2013-03-06 at 11:37 -0800, Bill Blue wrote:
>
> Hi,
>
>>
>> gst-launch \
>>                  directsoundsrc ! \
>>                  audioconvert ! \
>>                  audioamplify amplification="1" ! \
>>                  vorbisenc bitrate="128000" ! \
>>                  oggmux ! \
>>                  shout2send ip="10.146.162.40" port="4949" 
>> mount="/nor"
>> password="xxxx" username="xx"
>
> I'm a bit confused here. gst-launch usually means 0.10, in 1.0 it's
> always gst-launch-1.0 (the error shows that it's using 1.x though - I
> assume it's a copy'n'paste mistake?).

Hi Tim,

Actually, no.  It's a hard link from gst-launch-1.0 to gst-launch -- 
easier to type.  All of my gst-*'s are set that way.

>
>>
>> ERROR: from element /GstPipeline:pipeline0/GstShout2send:shout2send0:
>> Could not connect to server
>> Additional debug info:
>> C:/sbuild/src/mingw/gst-plugins-good-1.0-1.0.5-1/gst-plugins-good-1.0.5/ext/shout2/gstshout2.c(550):
>> gst_shout2send_connect ():
>> /GstPipeline:pipeline0/GstShout2send:shout2send0:
>> shout_open() failed: err=Login failed
> ...
> Have you looked at the GST_DEBUG=shout*:6 debug log?

I had tried level 4 which didn't reveal anything useful.  Using level 
6 I discovered the problem.  The mount point in my configuration is 
/nor.  Trying it quoted or not, shout2send was expanding it to 
C:/sbuild/src/mingw/nor, which is obviously incorrect.  Entering the 
mount as //nor corrected that problem (it now 'expands' to /nor ) and 
seems to be working correctly.

On the way to that discovery, I found that "--gst-debug-no-color" does 
not work to turn off debug output hi-lighting (or at all, for that 
matter), but setting the environment variable GST_DEBUG_NO_COLOR=1 
does.  Both are referenced in the gstreamer html pages documentation.

Thanks for the suggestion.

--Bill