Displaying 3 results from an estimated 3 matches for "icy200ok".
2013 Oct 03
1
understanding icecast decoding from a listener client perspective
...can
asynchronously connect read the continuous bytes from the stream using
some basic C# code. When I look at the bytes (interpreted as ASCII) I
don't understand what it is that I need to be using before passing the
Ogg to libogg. I see some artist information, and I know that there is
an ICY200OK type of message. I also see the word Oggs at the beginning.
But, what do I really need to do to decode the stream and the header?
What parts of the header are actually necessary for libogg to start
pulling the packets?
Ideally, my client would connect to the stream and read the header as
well...
2013 Oct 04
2
understanding icecast decoding from a listener client perspective
...d the continuous bytes from the stream
> using some basic C# code. When I look at the bytes (interpreted as
> ASCII) I don't understand what it is that I need to be using
> before passing the Ogg to libogg. I see some artist information,
> and I know that there is an ICY200OK type of message. I also see
> the word Oggs at the beginning. But, what do I really need to do
> to decode the stream and the header? What parts of the header are
> actually necessary for libogg to start pulling the packets?
>
> Ideally, my client would connect to the...
2013 Oct 04
0
understanding icecast decoding from a listener client perspective
...bytes from the
>> stream using some basic C# code. When I look at the bytes
>> (interpreted as ASCII) I don't understand what it is that I need
>> to be using before passing the Ogg to libogg. I see some artist
>> information, and I know that there is an ICY200OK type of
>> message. I also see the word Oggs at the beginning. But, what do
>> I really need to do to decode the stream and the header? What
>> parts of the header are actually necessary for libogg to start
>> pulling the packets?
>>
>> Ideall...