I might be the only one who still uses this, but....
As mentioned in the announcement thread, I forked the project today to get it working for what I needed:
https://bitbucket.org/silverbacknet/activewinamp
Source->Release to get the latest dll.
Changes:
Quote:
Accepts .js and .ps1 (PowerShell) files
Upgraded to full Unicode support
Unicode support also fixed the rating, playcount, lastplay, etc bugs.
|
To use PowerShell at all, 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. Scripts are named and located the same as before, only with a .ps1 ext.
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.