similar to: understanding icecast decoding from a listener client perspective

Hi, On 10/04/2013 06:27 PM, Andy Martin wrote: > I looked at these requests and started trying to interpret the data of > the header and the stream. I receive a header, and even when I added > the parameter to the request to try and get meta-data, it seems that > it is not being included. Namely, the number that is supposed to tell > the distance between each meta-data section that

I want to write an icecast listener client using C# and C++. I 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

Thanks for this information, but the two connections do not die out when using my player in the Android browser. In fact they even stay when the Audio.src is set to some invalid string. You can observe this here: http://concertzender.nl/wp-content/themes/cz-theme/App/test/ , by clicking one of the large icons - and then monitor the corresponding stream here: http://streams.greenhost.nl:8080/

On 05/03/2014 04:40 PM, Brad Isbell wrote: > I have built a web-based source client using the Web Audio API and > getUserMedia, called the AudioPump Web Encoder. It uses the SHOUTcast > source protocol for now, but I have the code nearly ready for the > Icecast source protocol for when someone needs it. > > You can see a demo here: http://demo.audiopump.co:3000/ That's

Brad Isbell: > I have built a web-based source client using the Web Audio API and > You can see a demo here: http://demo.audiopump.co:3000/ oh my, that looks great!!! > Let me know if there is interest. I can easily add the native Icecast > compatibility. definitely! i've only an icecast server available... thx, uno

I’m setting up my system on a Mac, and have successfully gotten Ladiocast to feed Icecast and can access it on my server Mac at localhost:8000/stream. If I try to access it at the IP of the Mac at 192.168.0.5:8000 or port forwarded from the internet, I CAN successfully access the admin page. However, if I try to access the stream from either the local IP or port forwarded from the internet, I

hello, now that html5 audio becomes usable in some browsers, for example http://webaudiodemos.appspot.com/AudioRecorder/index.html ... has anybody thought about to implement a web based source client for icecast? that's for now beyond my coding skills, unfortunately... thx, uno

Dear all, The problem I am facing, is that one of my clients is concerned about data usage. My client monitors the current number of listeners in the Mount Point list streams.greenhost.nl:8080. The case is, when I start a stream from an HTML app on an Android device, I can see two listeners being added to "Current Listeners". This peculiar behaviour only occurs on Android, not on

2014-05-03 18:40 GMT+02:00 Brad Isbell <brad at musatcha.com>: > The general idea was to make a really simple source client that could be > launched with a single click (such as from a hosting provider's admin > panel). The client accepts parameters on the query-string for configuring > so that in a real-world environment, the user would not have to configure > anything.

I would like to program a basic OGG decoder that takes in an array of bytes (unsigned char *) and return an array of floats. Presumably I could then pass these floats to be read as PCM data which can be immediately interpreted as audio (by Unity3D). The starting point would be the header of an icecast stream (I know I'm not in the icecast mailing-list, but that is only the basic starting

Thanks everyone! I will answer your questions regarding the AudioPump Web Encoder (http://demo.audiopump.co:3000/): *> Can you please explain the process exactly? what is the encoding server?* There is a server built on Node.js that receives audio data, control data, and metadata from the client over a binary websocket. All of these are multiplexed down the same connection. When the server

html5/js source client? (Xabier Oneca -- xOneca) 2014-05-04 21:00 GMT+02:00 <icecast-request at xiph.org>: > Send Icecast mailing list submissions to > icecast at xiph.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.xiph.org/mailman/listinfo/icecast > or, via email, send a message with subject or body 'help' to

Hello I always have had best results encoding the stream .mp3 it works on all devices. I also suggest the source to be the same or better than your stream.. this saves in many areas. it sounds like you are possibly debugging a time lapsed source/ stream.. i did not read all so if this is not so i apologize On May 5, 2015 3:11 AM, "Klaas van der Linden" < vanderlinden at

I have built a web-based source client using the Web Audio API and getUserMedia, called the AudioPump Web Encoder. It uses the SHOUTcast source protocol for now, but I have the code nearly ready for the Icecast source protocol for when someone needs it. You can see a demo here: http://demo.audiopump.co:3000/ The Web Encoder is built with a jQuery Mobile UI optimized for mobile devices at the

Klaas, You will find that there often are multiple connections, particularly for HTML5 audio elements in WebKit browsers as they probe to see if the media is seekable or not. The multiple connections die out soon after starting though, leaving you one connection for actually streaming the audio. You can verify this yourself with a packet sniffer such as Wireshark. It wouldn't hurt to double

You're likely seeing the browser's built-in handling of your stream, and not actually a page. It's unlikely that the issue has anything to do with connectivity. If you can provide a URL to your actual stream, we might be able to help diagnose the issue. *Brad Isbell // AudioPump, Inc.* brad at audiopump.co Skype: bradisbell Phone: +1 312-488-4680 On Wed, Jul 18, 2018 at 2:50 PM,

I have been developing some directshow filters for ogg, and vorbis and speex... currently i have an ogg demux filter and a speex/vorbis decoding filter. In this pre-release only vorbis is operational... but the speex decoder is pretty much done... i jsut need to tweak the demux filter so that it can negotiate a speex connection with the other filter. Just though some people might find them useful

I'm having an issue with URL-based authentication on Windows Server that is being aggravated by a separate logging issue. In the server's error log: [2020-03-13 16:59:46] DBUG connection/connection.c alias has made /player/ > into /player/index.html > [2020-03-13 16:59:46] INFO auth/auth.c adding client for authentication > [2020-03-13 16:59:46] DBUG auth/auth.c ...refcount

Hi all, Xiph aims at developing open-standards media formats. Though xiph.org tells about vorbis/theora/flac/speex, nothing is mentioned about container to use (that is ogg/ogm). I have a few questions Is there a difference between ogg and ogm? I guess its only the extension that is different and everything else is same. Some tools (like ogmtools) are available to create ogm files. What is

Hey i've recently written some directshow filters for ogg vorbis and speex (www.illiminable.com/ogg/) and i thought i might add flac too... i've had a quick look at the C++ api and it appears that the decoding works by having a read callback to get it's data. In directshow everything is pushed into the decoder it can't ask for data when it wants... i'm just wondering if there