Quantcast

Issue in vorbisdec

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Issue in vorbisdec

Puneeth
Hi All,

         I m facing some problem when i  m using vorbis decoder with gstrtpbin with the below pipeline.
Client
       sudo gst-launch gstrtpbin name=rtpbin udpsrc caps="application/x-rtp,channels=1,media=(string)audio,clock-rate=(int)44100,encoding-name=(string)VORBIS,payload=(int)96,encoding-params=(string)1" port=5002 ! rtpbin.recv_rtp_sink_0 rtpbin. ! rtpvorbisdepay ! vorbisdec ! audioconvert ! volume volume=10 ! audioresample quality=10 ! alsasink udpsrc port=5003 ! rtpbin.recv_rtcp_sink_0 rtpbin.send_rtcp_src_0 ! udpsink port=5007 host=127.0.0.1 sync=false async=false

WARNING: from element /GstPipeline:pipeline0/GstRtpVorbisDepay:rtpvorbisdepay0: Could not decode stream.
Additional debug info:
gstrtpvorbisdepay.c(584): gst_rtp_vorbis_depay_process (): /GstPipeline:pipeline0/GstRtpVorbisDepay:rtpvorbisdepay0:
Could not switch codebooks

Server

sudo gst-launch gstrtpbin name=rtpbin alsasrc ! audioconvert ! audioresample ! vorbisenc ! rtpvorbispay ! rtpbin.send_rtp_sink_0 rtpbin.send_rtp_src_0 ! udpsink port=5002 host=172.16.10.71 rtpbin.send_rtcp_src_0 ! udpsink port=5003 host=172.16.10.71 sync=false async=false udpsrc port=5007 ! rtpbin.recv_rtcp_sink_0

Please kindly anyone help me to resolve this issue. But i m able to listen with the below pipeline.

gst-launch alsasrc ! audioconvert ! vorbisenc ! rtpvorbispay ! rtpvorbisdepay ! vorbisdec ! audioconvert ! alsasink

Thank u in advance.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Issue in vorbisdec

Wim Taymans
On 02/10/2011 02:02 PM, Puneeth wrote:

>
> Hi All,
>
>           I m facing some problem when i  m using vorbis decoder with
> gstrtpbin with the below pipeline.
> Client
>         sudo gst-launch gstrtpbin name=rtpbin udpsrc
> caps="application/x-rtp,channels=1,media=(string)audio,clock-rate=(int)44100,encoding-name=(string)VORBIS,payload=(int)96,encoding-params=(string)1"
> port=5002 ! rtpbin.recv_rtp_sink_0 rtpbin. ! rtpvorbisdepay ! vorbisdec !
> audioconvert ! volume volume=10 ! audioresample quality=10 ! alsasink udpsrc
> port=5003 ! rtpbin.recv_rtcp_sink_0 rtpbin.send_rtcp_src_0 ! udpsink
> port=5007 host=127.0.0.1 sync=false async=false
>

You are missing the configuration string in the RTP caps.

Wim


> WARNING: from element
> /GstPipeline:pipeline0/GstRtpVorbisDepay:rtpvorbisdepay0: Could not decode
> stream.
> Additional debug info:
> gstrtpvorbisdepay.c(584): gst_rtp_vorbis_depay_process ():
> /GstPipeline:pipeline0/GstRtpVorbisDepay:rtpvorbisdepay0:
> Could not switch codebooks
>
> Server
>
> sudo gst-launch gstrtpbin name=rtpbin alsasrc ! audioconvert ! audioresample
> ! vorbisenc ! rtpvorbispay ! rtpbin.send_rtp_sink_0 rtpbin.send_rtp_src_0 !
> udpsink port=5002 host=172.16.10.71 rtpbin.send_rtcp_src_0 ! udpsink
> port=5003 host=172.16.10.71 sync=false async=false udpsrc port=5007 !
> rtpbin.recv_rtcp_sink_0
>
> Please kindly anyone help me to resolve this issue. But i m able to listen
> with the below pipeline.
>
> gst-launch alsasrc ! audioconvert ! vorbisenc ! rtpvorbispay !
> rtpvorbisdepay ! vorbisdec ! audioconvert ! alsasink
>
> Thank u in advance.


------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gstreamer-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Issue in vorbisdec

Puneeth
I thought of set that configuration string but how could i set that, that is huge data it started with AAAAX..... should i set with environment variable and then set that or include whole thing in pipeline, i m confused please help. Thank you.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Issue in vorbisdec

garrett
Hello, I have come across the same issue as the OP of this message. I'm giving it a bump in the hopes that the problem can be resolved.

After doing some research: I found that running the server script in verbose mode '-v' would return the caps value that you would need to copy and paste into udpsrc. Unfortunately: this proved unsuccessful, it returned Syntax error: "(" unexpected and when the string is enclosed in quotes, it returns erroneous pipeline: could not set property "caps" in element "udpsrc0"

Is there something additional that must be done to the string to make the receiving script function beyond surrounding it in quotes?
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Issue in vorbisdec

Tim-Philipp Müller-2
On Sat, 2012-03-24 at 03:46 -0700, garrett wrote:

> Hello, I have come across the same issue as the OP of this message. I'm
> giving it a bump in the hopes that the problem can be resolved.
>
> After doing some research: I found that running the server script in verbose
> mode '-v' would return the caps value that you would need to copy and paste
> into udpsrc. Unfortunately: this proved unsuccessful, it returned Syntax
> error: "(" unexpected and when the string is enclosed in quotes, it returns
> erroneous pipeline: could not set property "caps" in element "udpsrc0"
>
> Is there something additional that must be done to the string to make the
> receiving script function beyond surrounding it in quotes?

Could you post the exact command line that caused these problems? You
can also try single quotes 'foo' vs. normal quotes ("foo"), or escape
brackets like \(buffer\)1234

Cheers
 -Tim

_______________________________________________
gstreamer-devel mailing list
[hidden email]
http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Issue in vorbisdec

garrett
Thank you for getting back to me. What I was trying to do was run this audio UDP transmission script using the vorbis codec:

gst-launch-0.10 pulsesrc device=alsa_input.usb-046d_0809_B11D4DC2-02-U0x46d0x809.analog-mono ! audioconvert ! vorbisenc ! rtpvorbispay ! udpsink host=224.1.1.1 port=3000 auto-multicast=true

This worked fine. The receiver script did not.

gst-launch-0.10 udpsrc multicast-group=224.1.1.1 auto-multicast=true port=3000 caps=application/x-rtp ! gstrtpjitterbuffer drop-on-latency=false latency=100 ! rtpvorbisdepay ! vorbisdec ! pulsesink

Which reported that it "Could not decode stream" and "Could not switch code books"

I found, from other resources, that adding '-v' to the transmission script would reveal the correct, but lengthy, caps output but plugging that directly into the receive script did not work saying that erroneous pipeline: could not set property "caps" in element "udpsrc0".

However, putting it between single quotes, which is something that I didn't think to do: worked. Thank you.

On Sat, Mar 24, 2012 at 5:01 AM, Tim-Philipp Müller <[hidden email]> wrote:
On Sat, 2012-03-24 at 03:46 -0700, garrett wrote:

> Hello, I have come across the same issue as the OP of this message. I'm
> giving it a bump in the hopes that the problem can be resolved.
>
> After doing some research: I found that running the server script in verbose
> mode '-v' would return the caps value that you would need to copy and paste
> into udpsrc. Unfortunately: this proved unsuccessful, it returned Syntax
> error: "(" unexpected and when the string is enclosed in quotes, it returns
> erroneous pipeline: could not set property "caps" in element "udpsrc0"
>
> Is there something additional that must be done to the string to make the
> receiving script function beyond surrounding it in quotes?

Could you post the exact command line that caused these problems? You
can also try single quotes 'foo' vs. normal quotes ("foo"), or escape
brackets like \(buffer\)1234

Cheers
 -Tim

_______________________________________________
gstreamer-devel mailing list
[hidden email]
http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel



--
W.A. Garrett Weaver 


_______________________________________________
gstreamer-devel mailing list
[hidden email]
http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel
Loading...