Announcement: ActiveWinamp

[shaneh]

The source code and development tracking of ActiveWinamp is now available at sourceforge:

http://sourceforge.net/projects/activewinamp/

Please direct bug reports and feature requests to the trackers for more efficient handling.

[CaboWaboAddict]

Cool! Many thanks.

[SilverbackNet]

Since this project is no longer maintained, and I really wanted it back, I forked it today:

https://bitbucket.org/silverbacknet/activewinamp

Source->Release to get the latest dll.

Changes:

Accepts .js and .ps1 (PowerShell) files
Upgraded to full Unicode support
Unicode support also fixed the rating, playcount, lastplay, etc bugs.

Regarding the last, it looks like some 5.x changed the way extended_info was written, and obviously this plugin was never updated to fix that, so most of the info would only randomly work at best.

To use PowerShell, you have to open an admin command prompt and run:

code:
%windir%\syswow64\windowspowershell\v1.0\powershell Set-ExecutionPolicy RemoteSigned

Otherwise PS scripts can't run outside of the PS sandbox.

I'm going to upload some sample scripts, but to use it in a PS script, start with:

code:
$aw = New-Object -ComObject ActiveWinamp.Application

at the top; from there, you can access $aw.playlist, $aw.medialibrary, etc, as you would in VBS. The plugin automatically executes the x86 PS, since Winamp will never be x64. You can call them from the command line, like:

code:
powershell -file "AnyScript.ps1"

If you do, I really recommend adding an x64 guard at the top, like so:

code:
if ($env:Processor_Architecture -ne "x86") {

write-warning 'Switching to x86 mode...'

&"$env:windir\syswow64\windowspowershell\v1.0\powershell.exe" -noninteractive -noprofile -file $myinvocation.Mycommand.path -executionpolicy bypass

exit

}

I'm going to be adding all of the library fields that aren't available yet next.

[ryerman]

Originally Posted by SilverbackNet

Since this project is no longer maintained, and I really wanted it back, I forked it today:

I'm a big fan of ActiveWinamp too, so I was excited to see somebody trying to make improvements.
Unfortunately, when using your new .dll, my scripts written in VBScript do not execute.

Is that expected?

[SilverbackNet]

My apologies, of course it's meant to work! That was me being so excited by my new scripts that I didn't sufficiently test the old -- I forgot to switch the vbscript loader to Unicode as well. Fixed.

There might be other mistakes, I'm going to start testing on some more complex vbscripts today and see what happens.

[ryerman]

Originally Posted by SilverbackNet

There might be other mistakes, I'm going to start testing on some more complex vbscripts today and see what happens.

Good luck.
My vbscripts now open but do not execute properly.
I suspect "GetSendToItems" in ActiveWinamp is failing somehow.

I hope you can fix it so existing scripts work from the "Send to" menu without executing twice, as they do in the original.

[SilverbackNet]

I found a few other problems, I really jumped the gun on this announcement. Sorry about that. I'll post back when it's in more respectable shape.

[silversilver]

Looks great, is there any links or documentation on the function names and methods?