BogProg AterKast is now available!!!

[jhbmusic]

Cool, thanks for the suggestions.

[thinktink]

Version 1.1.5.18 now available.

Download

Changes:

• Fixed crash issue when turning off the DSP (from within a stacker or by selecting a different DSP from Winamp preferences) while one or more EndPoints were in the middle of trying to establish a connection to the distributer (aka DNAS, Icecast Server, etc...).
• Fixed a crash issue on plugin quit.
• Fixed multiple crash issues on plugin unload (whether by shutting down Winamp or unloading the plugin in a stacker).

None of the above crashes affected normal streaming, just during shutdown/quit/de-init.

[thinktink]

Version 1.2.7.40 now available.

Download

Changes:

• Added ability to enable JNetLib for SSL support for versions of Winamp 5.8 or older. 5.9+ versions just crash, so don't do it if you're on 5.9 or above unless I say.
• Fixed colors of about box and added supporting code references to it.
• There were more changes but I forgot what they were. [EDIT/] Remembered what the third one was, LOGGING! Check config window for details.

There's going to be another update very soon that will include manual metadata and potentially automatic external metadata (posting to a TCP/IP port, reading from a file when it changes, etc...)

[thinktink]

Version 1.3.8.52 now available.

Download

Changes:

• Added manual metadata both local (per EndPoint) and shared (used on multiple EndPoints.)
• Added external shared flat file metadata.
• Updated DSP main window to accommodate the new features.
• Added more logging in places where it was missing.
• Removed extremely repetitive logging from the DirectSound device source handler.

The external metadata flat file format is the same that was used from the experimental BogProg LiveIn plugin. The flat file can accept Unicode character sets if converted to UTF-8 MBCS. The following is the current list of (protocol independently) supported metadata values in the flat file(without the double quotes):

{
"title"    *  **
"artist"   *  **
"album"    *
"year"     *
"comment"  *
"genre"    *
"albumartist"
"composer"
"disc"
"track"
"bpm"
"director"
"producer"
<<!
Entries that have a (*) next to them are read by the SCv2 Protocol.
Entries that have a (**) next to them are read by the SCv1 and Icecast Protocols.
>>
}​

[thinktink]

Version 1.4.9.56 now available.

Download

Changes:

• Fixed logic error on streams disconnected at certain stages. Hopefully this fixes errors with streams no longer connected but still showing a valid stream status.
• Updated logging for file transcodes on SCv2 streams. No longer logs transcodes for files pulled from cache.

[rlevis]

Have you considered switching to FFMpeg for encoding? It supports Fraunhoffer's HE-AAC, Opus, and so many other useful streaming codecs.

[thinktink]

Have you considered switching to FFMpeg for encoding? It supports Fraunhoffer's HE-AAC, Opus, and so many other useful streaming codecs.

It did occur to me but as I currently understand it the licensing requirements for ffmpeg integration is incompatible with closed source software.

[rlevis]

I may be wrong but I think it's fine if you distribute ffmpeg as a DLL and just call it.

[thinktink]

I may be wrong but I think it's fine if you distribute ffmpeg as a DLL and just call it.

I would have to research that first. From my previous experience with "Secret Rabit Code" it may be the same issue, whether it's a separate DLL or compiled in with the plugin source. Though the only reason why I would use ffmpeg libraries would be just for HE-AAC+ support since the other codecs are running fine the way they are.

[rlevis]

Fair enough. You could always implement it and the user forced to download the ffmpeg DLL separately if necessary. It would be a game changer as it's very commonly used for internet streaming.

[thinktink]

Fair enough. You could always implement it and the user forced to download the ffmpeg DLL separately if necessary. It would be a game changer as it's very commonly used for internet streaming.

At the moment it looks like I can't even do that if I wanted to use HE-AAC+ from FFmpeg:

https://www.ffmpeg.org/legal.html

https://trac.ffmpeg.org/wiki/Encode/AAC

[rlevis]

It is definitely legal for you to write code to call a DLL you are not distributing. It is commonly done. The user may need to compile their own ffmpeg DLL from source code to get HE-AAC support legally.