Hi there,
Is there an easy way of reading an icecast HTTP audio streams in PD?
oggread~ does not accept URLs in the "open" message and when using a named-pipe with curl feeding into it, curl bails out with: curl: (23) Failed writing body (1741 != 8000)
This is pd 0.41.4-extended.
Any help or ideas are appreciated, robin
http://aug.ment.org/readanysf/index.php
D.
On 3/4/10 10:49 AM, Robin Gareus wrote:
Is there an easy way of reading an icecast HTTP audio streams in PD?
oggread~ does not accept URLs in the "open" message and when using a named-pipe with curl feeding into it, curl bails out with: curl: (23) Failed writing body (1741 != 8000)
hi,
[oggamp~] or readanysf hugs :O)
Derek Holzer escribió:
http://aug.ment.org/readanysf/index.php
D.
On 3/4/10 10:49 AM, Robin Gareus wrote:
Is there an easy way of reading an icecast HTTP audio streams in PD?
oggread~ does not accept URLs in the "open" message and when using a named-pipe with curl feeding into it, curl bails out with: curl: (23) Failed writing body (1741 != 8000)
hi, [oggamp~] is the correct "ogg object" for this, i think and yes of course readanysf hugs :O) dani.
Derek Holzer escribió:
http://aug.ment.org/readanysf/index.php
D.
On 3/4/10 10:49 AM, Robin Gareus wrote:
Is there an easy way of reading an icecast HTTP audio streams in PD?
oggread~ does not accept URLs in the "open" message and when using a named-pipe with curl feeding into it, curl bails out with: curl: (23) Failed writing body (1741 != 8000)
Derek Holzer wrote:
Thanks, works like a charm!
Cheers! robin
D.
On 3/4/10 10:49 AM, Robin Gareus wrote:
Is there an easy way of reading an icecast HTTP audio streams in PD?
oggread~ does not accept URLs in the "open" message and when using a named-pipe with curl feeding into it, curl bails out with: curl: (23) Failed writing body (1741 != 8000)