[gst-devel] Problems when using osssink in ARM

[John Faith]

Hi Trimurthulu,
Thanks for the suggestion.

With the 'sync=false', I still get mostly zeros for the data buffer, but 
now about every 2.5 seconds, I get a short (~.2s) burst of noise and the 
data buffer for the burst is mostly 0xFFs.


I assume I need the audioresample, since without it, I get:
ERROR: from element /pipeline0/filesrc0: Internal data flow error.
Additional debug info:
gstbasesrc.c(1642): gst_base_src_loop (): /pipeline0/filesrc0:
streaming task paused, reason not-negotiated (-4)
ERROR: pipeline doesn't want to preroll."
Setting pipeline to NULL ...
FREEING pipeline ...


Thanks,
John


trimurthulu amaradhi wrote:
>  Hi,
> 
>  can you just try with the following
> 
>  gst-launch -v filesrc location=file.mp3 ! mad ! audioconvert
> ! osssink sync=false
> 
>  Trimurthulu
> 
> 
> On 9/29/07, John Faith <jfaith at freescale.com> wrote:
>> Hello,
>> I am seeing the same problem as is described earlier in this thread.
>> When I use 'gst-launch -v filesrc location=file.mp3 ! mad ! audioconvert
>> ! osssink', I get silence like the original poster.
>>
>> I have verified that madplay works on my ARM board, and I have heard the
>> short sample tone using 'gst-launch audiotestsrc ! audioconvert !
>> audioresample ! osssink', so I assume the hardware, OSS driver, and
>> gstreamer are mostly working.
>>
>> As an experiemnt, I used filesink instead of osssink, and used an OSS
>> utility to play the raw audio data.  This also produced sound.
>>
>> Then I put printf()s in gst-plugins-good-0.10.5/sys/oss/gstosssink.c to
>> print out the first 10 bytes of the data passed to gst_oss_sink_write()
>> and saw only zeros, which explains the silence.
>>
>> Has anyone been able to solve this problem or could advise on other
>> debug methods?  I have used --gst-debug-level, but I am not sure what to
>> look for.
>>
>> If I replace filesink with osssink, what might cause the data to be all
>> zeros?
>>
>> Thanks!,
>> John