So far, this version is free from crashes since I made the build. Previous builds had a week of stability and no crashes. I'm not discounting the possibility of multiple bugs to fix, but I haven't had a crash since I've been building them.

If anyone cares to have a listen, I'm streaming continuously (sans outages due to crashes) at http://radio.psylight.ca/listen.m3u. Random electronic music, with an emphasis on stuff you can dance to and acid/electro/idm influences. May contain objectionable content from time-to-time. Some of this stuff I haven't even listened to yet! Just tracks that I tend to like to listen to. Streamed continuously with very few repeats for 3 months.

If there's any complaint about aoTuV 5.5, I'm open to discussion. I just don't see any reason not to support the latest and greatest aoTuV. His releases have been continuously excellent so far. I intend to support the best Vorbis tuning, not all Vorbis tunings.

Thanks a lot man! Now the difficult part... would you mind making a brief tutorial on how to make this thing work?As far as I know, you put the dll on the components folder, add to DSP window... but after adding an encoder and hitting connect, it does not do it (keeps retrying every 10 seconds but to no avail).Any idea?

You have an Icecast2 server somewhere I imagine? This component does not work on its own, it requires a working installation of Icecast2 to stream to. Icecast2 then allows for relaying and connecting to the stream.

After searching a bit, it seems it happens only when the crossfader is in the DSP chain.Usually the only DSP i use are:-crossfader-edcast Vorbis Streamer (or original Edcast plugin)

So i don't know if the problem is with the crossfader or edcast or the combination of the 2 of them.

Another little bug (that was also present in the original plugin) :If I close the edcast Vorbis Streamer window, it goes in the tray. Fine.But once in the tray, if i close foobar, the edcast Vorbis Streamer icon stays in the tray until my mouse cursor hovers it which make it disappear.

The bug regarding the icon in the notification area will go away once I make the component use proper DSP presets for storing configuration, which is on my todo list.

Edit: Is there any reproducible way to trigger the Crossfader bug? I've been trying for a couple hours and all I've found so far is an integer overflow problem with the resampler, which is irrelevant to fix anyhow, because I'll be transitioning to using PPHS sometime in the future.

v0.9.5.6b has been released, which just might fix your bug Hamallainen. Download link is at the same location.

Other changes include removal of the "Advanced Settings" tab, changing the logging options to be foobar2000 Advanced Preferences instead. Also, changed logging to output to the console instead of a log file. Removed various other pieces of useless cruft. Refactored the component interface.

It's funny you say that because Crossfade works as expected here. Obviously it's going to have to come before the streaming component if you want to hear it in the stream, but other than that blatantly obvious tidbit, it's working okay.

v0.9.5.6b has been released, which just might fix your bug Hamallainen. Download link is at the same location.

Yes ! with this version no more crash with crossfader enabled. Thanks.While testing i had found 2 songs, if played with the crossfader and edcast, it crashed (with 0.9.5.6a not 0.9.5.6b) while 'crossfading'.The first song was 48000Hz (never noticed before, i didn't encode it) and the second was 44100Hz. Don't know if it helps.Thanks again, now i can test it on long term.

Version 0.9.6a has been released. I had a crash, so I fixed a bug. Also, this new version should handle dynamic metadata properly. For example, if you're listening to a FLAC stream (and if you are, I'd love to get a URL, as I've yet to be able to find any FLAC streaming that works properly) and it has proper metadata, you can transcode it to Vorbis using this component and no metadata will be lost!

v0.9.7 is released. It fixes a bug where edcast crashes if there are more than 30 fields of metadata and also fixes UTF-8 support. I've only tested the UTF-8 support on a foobar2000 -> Icecast2 -> foobar2000 pathway, so YMMV. If there are problems in other configurations, please report them here and I'll do my best to solve the problem.

edit: ouch , crashed right after start, do i have to reset the config before upgrading ?

edit2 : ok now, i had to remove it from the dsp chain before before upgradingthe poping window is gone ? to configure more than 1 stream we need to upgrade to 0.9.6.4b1 to add the vorbisstream to the dsp chain as many time as we want ?

"Known to cause the host audio to skip if upload bandwidth is insufficient for the stream."

That can be fixed by "overhauling" the network out buffers to auto-size based on incoming data, and catches up as fast as it can until it's back to 1-2 buffers. don't forget to put a check on it to start reconnect function if no data has been sent at all in [n] seconds.

the poping window is gone ? to configure more than 1 stream we need to upgrade to 0.9.6.4b1 to add the vorbisstream to the dsp chain as many time as we want ?

Yes, it's configured like a normal DSP component now. And yes, you'll need to upgrade to 0.9.6.4b1 to have multiple concurrent streams. That change actually inspired me to get the latest batch of work done.

Hello,Here is something to think about.When the plugin is added into the DSP chain more than once, each occurence does transcoding to ogg vorbis. Would it be possible to add an ability to send a stream to more than one icecast in the future?I know the proper setup is setting master / slave icecast configurations in this case but there may be need to do this on the client side when the actual broadcaster does not have full control over the hosting server.

odyssey, please upgrade to the new version. You're using a very old build.

--pv--, I don't really understand what you're requesting. You want to be able to use multiple vorbis streams? Just grab the latest foobar2000 beta and give it a try. The component is designed to allow multiple DSP instances at once to stream to several different Icecast servers, or to serve several streams on one, or whatever.

Edit: --pv--, if what you desired was to send a single transcode to multiple servers, the smartest way to do that could be to run a local Icecast server that relays to others. Your request would involve too much additional complexity.