Hydrogenaudio Forums

Hosted Forums => foobar2000 => 3rd Party Plugins - (fb2k) => Topic started by: R1CH on 2006-03-26 00:58:29

Title: foo_winamp_spam 0.9 beta
Post by: R1CH on 2006-03-26 00:58:29
Winamp API emulator is designed to create a fake Winamp 1.x window which will act as a wrapper between applications written to use the Winamp API and foobar2000. Only a small subset of the Winamp API is implemented, but most of the useful functionality is there.

I've updated my Winamp API emulator to support foobar2000 0.9. Unfortunately I don't have any applications installed to test a number of features such as remote control of "Winamp" (pause/play/stop/next/prev/etc), I've only tested the "query" commands such as the ones provided by r1dll (http://r1ch.net/r1dll).

Beta3 is here, please post feedback.
http://r-1.ch/foo_winamp_spam-0.9beta3.7z (http://r-1.ch/foo_winamp_spam-0.9beta3.7z)
Title: foo_winamp_spam 0.9 beta
Post by: Seldaek on 2006-03-26 02:15:19
It's working here with my mIRC script, well I can get the filename but not the current playtime & total file length nor the Kbps of the file, for the rest I'm not sure. All of these worked with 0.8.3 so it should be possible, good luck and thank you already
Title: foo_winamp_spam 0.9 beta
Post by: R1CH on 2006-03-26 02:34:16
Quote
It's working here with my mIRC script, well I can get the filename but not the current playtime & total file length nor the Kbps of the file, for the rest I'm not sure. All of these worked with 0.8.3 so it should be possible, good luck and thank you already
[a href="index.php?act=findpost&pid=375278"][{POST_SNAPBACK}][/a]

How are you trying to get those values? I've tested it with R1DLL which uses the Winamp API and it seems to work fine.
Title: foo_winamp_spam 0.9 beta
Post by: crono cloud on 2006-03-26 03:16:08
i use winamp cd case (http://www.closetosoftware.com/wcc.html) to view album art... and it worked in foobar 0.8.3 but its not working now in v 0.9

Evillyrics is now working though, i just dont know why winamp cd case isn't
also, some scripts that worked in samurize with foobar v0.8.3 are not working either

but thanks so much for updating, at least evillyrics is working now =)

edit** also, controls on the winamp cd case work to control foobar, for example clicking next track in winamp cd case changes the track in foobar, but still it's not recieving the information or something

**edit again
heres some pics that might help solve the problem

this is foobar v0.8.3, in the 'fake' or whatever window it shows the playlist number
(http://img111.imageshack.us/img111/2888/clip26bl.th.jpg) (http://img111.imageshack.us/my.php?image=clip26bl.jpg)

foobar v0.9, the playlist number in the winamp window is 0, so im guessing thats the key to the problem
(http://img111.imageshack.us/img111/1139/clip2xr.th.jpg) (http://img111.imageshack.us/my.php?image=clip2xr.jpg)
Title: foo_winamp_spam 0.9 beta
Post by: Spi on 2006-03-26 03:48:22
I'd never use it again cause sometime ago i had it in my fb2k 0.8.3 config, and my fb ate about 50 mb ram only cause of this plugin, sry ... never again

i could give some more clues y it did that, but not in my actual state
Title: foo_winamp_spam 0.9 beta
Post by: R1CH on 2006-03-26 04:47:48
Ok, it should be compatible with Winamp CD case now. Unfortunately I still can't get the playlist number to work, it seems the API call fails.

Code: [Select]
  t_size plIndex, trackIndex;
 if (static_api_ptr_t<playlist_manager>()->get_playing_item_location (&plIndex, &trackIndex))
...

I have that in my on_playback_new_track and it always returns false. Perhaps the playing item isn't updated until after on_playback_new_track returns? Where should I be using this...

Beta2:
http://r-1.ch/foo_winamp_spam-0.9beta2.7z (http://r-1.ch/foo_winamp_spam-0.9beta2.7z)
Title: foo_winamp_spam 0.9 beta
Post by: crono cloud on 2006-03-26 05:10:23
thanks! that was really quick! works great!

thanks again soo much
Title: foo_winamp_spam 0.9 beta
Post by: Seldaek on 2006-03-26 05:34:10
I can get all the infos with beta2 BUT there seem to be a problem, requests take between 3 and 4 seconds to get returned. I think with beta1 it was instantaneously returned. And with 0.8.3 version I'm sure it is. (Edit: I just tried; doing a loop request for data I get 1every answer 3seconds with 0.9 and 5-6 per second with 0.8.3)
Title: foo_winamp_spam 0.9 beta
Post by: R1CH on 2006-03-26 05:56:26
I can't seem to replicate this, all my IPC_ requests are fulfilled nearly instantly. What messages are you sending?
Title: foo_winamp_spam 0.9 beta
Post by: Seldaek on 2006-03-26 06:29:04
Well it's strange, if I try to individually requesting the filename through r1dll or tracklenght & trackposition through another dll I use everything is returned very quickly, but when I use the mirc script it takes several seconds.. but it can't be the script part as it's very fast with the old foobar.. I just don't get it, it's 7.30am here and I have to go to bed. I'll see tomorrow.
Title: foo_winamp_spam 0.9 beta
Post by: Costa666 on 2006-03-26 19:59:45
Hello. I'm using your plugin for sending songs name into Evil Lyrics. It is working perfect in foobar 0.8.3 but this new version changes few letters we use in Croatian language. Character encoding is ISO-8859-2:
(http://www.slibe.com/images/1fb0a167-winampspam_png.png)
Title: foo_winamp_spam 0.9 beta
Post by: zoidbergslo on 2006-03-26 20:42:18
It works well with mir.dll plugin for mirc to show what I am listening to

[span style='font-size:8pt;line-height:100%'][edit] I guess that Advanced Media Player Info for samurize has nothing to do with foo_winamp_spam[/span]
Title: foo_winamp_spam 0.9 beta
Post by: R1CH on 2006-03-26 23:25:21
Quote
Hello. I'm using your plugin for sending songs name into Evil Lyrics. It is working perfect in foobar 0.8.3 but this new version changes few letters we use in Croatian language. Character encoding is ISO-8859-2:
(http://www.slibe.com/images/1fb0a167-winampspam_png.png)
[{POST_SNAPBACK}][/a] (http://index.php?act=findpost&pid=375481")

Ok, I think I fixed this. The main problem though is the Winamp API has no unicode support so everything has to be converted to multibyte which greatly limits support of international characters.

With Advanced Media Player Info, try opening the foobar2000 console and checking for any foo_winamp_api warnings.

[a href="http://r-1.ch/foo_winamp_spam-0.9beta3.7z]http://r-1.ch/foo_winamp_spam-0.9beta3.7z[/url]
Title: foo_winamp_spam 0.9 beta
Post by: amonrei on 2006-03-26 23:52:38
Thanks. Been waiting for this. Works well so far.
Title: foo_winamp_spam 0.9 beta
Post by: ilikedirtthe2nd on 2006-03-27 00:04:54
Shouldn't the API emulator settings appear in "tools"? I think "display" is ment for settings that change the visible appearance of the player.

EDIT: another note, foo_winamp_spam seems to "spam" my console. Happens when I launch Evillyrics

Code: [Select]
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1242024.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1242024.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1242024.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1242024.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1242024.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1242024.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1242024.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1242024.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1242024.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1242024.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1242024.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1242024.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1242024.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1242024.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1242024.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1242024.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1242024.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1242024.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1242024.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1242024.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1242024.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1242024.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1242024.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1242024.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1242024.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1242024.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1242024.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1242024.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1242024.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1242024.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1242024.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1242024.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1242024.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1242024.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1242024.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1242024.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1242024.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1242024.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1242024.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1242024.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1242024.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1242024.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1242024.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1242024.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1242024.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1242024.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1242024.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1242024.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1242024.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1242024.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1242024.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1242024.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1242024.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1242024.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1242024.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1242024.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1242024.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1242024.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243292.
Title: foo_winamp_spam 0.9 beta
Post by: R1CH on 2006-03-27 00:39:27
Odd. I get the same thing too. None of those message ids appear in the Winamp SDK so I've no idea what EvilLyrics is trying to do.
Title: foo_winamp_spam 0.9 beta
Post by: wortels on 2006-03-27 01:12:39
increased cpu usage in latest version...definitely cause of winamp_spam

EDIT:

Just needed a new profile...working ok now
Title: foo_winamp_spam 0.9 beta
Post by: Gord on 2006-03-27 04:45:48
Someone couldn't mirror this could they? I can't connect to r-1.ch ... it just times out all the time no matter the browser I try.
Title: foo_winamp_spam 0.9 beta
Post by: Costa666 on 2006-03-27 14:01:53
It works well but I get these "Unsupported WM_USER" messages also. They don't appear when using beta 1 version, only in beta 2 and 3.
Title: foo_winamp_spam 0.9 beta
Post by: iZu on 2006-03-27 15:08:32
great, evillyrics is working!

thank you very much!
Title: foo_winamp_spam 0.9 beta
Post by: crono cloud on 2006-03-28 04:26:25
Quote
increased cpu usage in latest version...definitely cause of winamp_spam

EDIT:

Just needed a new profile...working ok now
[a href="index.php?act=findpost&pid=375600"][{POST_SNAPBACK}][/a]


what do you mean you needed a new profile?
bc im having this problem and i need a fix
Title: foo_winamp_spam 0.9 beta
Post by: wortels on 2006-03-28 12:08:36
Quote
Quote
increased cpu usage in latest version...definitely cause of winamp_spam

EDIT:

Just needed a new profile...working ok now
[a href="index.php?act=findpost&pid=375600"][{POST_SNAPBACK}][/a]


what do you mean you needed a new profile?
bc im having this problem and i need a fix
[a href="index.php?act=findpost&pid=376069"][{POST_SNAPBACK}][/a]



delete the foobar2000.cfg file from your folder
Title: foo_winamp_spam 0.9 beta
Post by: Rogue` on 2006-03-28 19:54:13
Cant express how happy i am this has been ported to 0.9

mIRC now playing script (gtsdll) and Winamp CD Case are working again \o/

Thanks allot r1ch.
Title: foo_winamp_spam 0.9 beta
Post by: crono cloud on 2006-03-28 22:06:28
Quote
delete the foobar2000.cfg file from your folder
[a href="index.php?act=findpost&pid=376153"][{POST_SNAPBACK}][/a]


i did that and foobar v0.9 still remains at 10%+
but without the plugin its rarely above 0%
Title: foo_winamp_spam 0.9 beta
Post by: Niko on 2006-03-29 03:13:04
I'm getting the same console spam here.

Also, quick question.  Anyone have any ideas why my keyboard would only be able to control foobar when it's in the foreground? I get my LCD information just fine, but none of the buttons work unless foobar is in focus.
Title: foo_winamp_spam 0.9 beta
Post by: R1CH on 2006-03-29 06:17:09
Quote
Quote
delete the foobar2000.cfg file from your folder
[a href="index.php?act=findpost&pid=376153"][{POST_SNAPBACK}][/a]


i did that and foobar v0.9 still remains at 10%+
but without the plugin its rarely above 0%
[a href="index.php?act=findpost&pid=376393"][{POST_SNAPBACK}][/a]

Do you have anything querying the window during the high CPU usage? I've had foobar2000 running all day with just 15 secs CPU time, there's nothing obvious I can see that would cause constant CPU usage. The only time the plugin does stuff is when something queries the fake winamp window.
Title: foo_winamp_spam 0.9 beta
Post by: crono cloud on 2006-03-29 06:49:46
Quote
Do you have anything querying the window during the high CPU usage? I've had foobar2000 running all day with just 15 secs CPU time, there's nothing obvious I can see that would cause constant CPU usage. The only time the plugin does stuff is when something queries the fake winamp window.
[a href="index.php?act=findpost&pid=376535"][{POST_SNAPBACK}][/a]


i guess its the constant querying by winamp cd case or evillyrics.. i really dont know...
but apparently its only happening to me so its nothing wrong with the plugin...

edit** i closed winamp cd case, and foobar's cpu usage remained high, then i closed evillyrics, and the cpu usage almost immediately went back down to 0, so its something to do with evillyrics, i just dont know what
Title: foo_winamp_spam 0.9 beta
Post by: BelleAndZEK on 2006-03-29 21:36:42
Samurize displays all tags correctly (lenght, title, artist, year, birtare) but doesnt display the album cover.
and im getting a shitload of this:
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 124.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 124.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 124.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 124.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 124.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 124.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 124.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 124.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 124.

i mean, a SHITLOAD.
Title: foo_winamp_spam 0.9 beta
Post by: R1CH on 2006-03-30 02:50:02
Quote
Samurize displays all tags correctly (lenght, title, artist, year, birtare) but doesnt display the album cover.
and im getting a shitload of this:

WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 124.

i mean, a SHITLOAD.
[a href="index.php?act=findpost&pid=376834"][{POST_SNAPBACK}][/a]

It looks like it's trying to query your playlist, right now playlist functions aren't working too well as either I'm using the API incorrectly or it's broken.
Title: foo_winamp_spam 0.9 beta
Post by: Jayphen on 2006-03-30 12:00:03
I'm getting the same console spam when evillyrics is open. It stops as soon as I close it.
Title: foo_winamp_spam 0.9 beta
Post by: AsILayDying on 2006-03-30 22:18:22
thanks for the update
Title: foo_winamp_spam 0.9 beta
Post by: R1CH on 2006-04-01 03:46:54
If no other issues come up I'll consider it ready for release .
Title: foo_winamp_spam 0.9 beta
Post by: JzE on 2006-04-01 14:37:19
Thanks R1CH this plugin is great, but I have a high CPU usage problem too. When I take a look at console it says this:

Code: [Select]
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 610.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 610.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 610.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 610.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 610.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 610.


What does this mean?

~JzE
Title: foo_winamp_spam 0.9 beta
Post by: Gurney on 2006-04-01 16:23:31
Quote
If no other issues come up I'll consider it ready for release .
[a href="index.php?act=findpost&pid=377692"][{POST_SNAPBACK}][/a]



Well, I've one

While the b2 works perfectly for me (I use it to spam the OSD of the Logitech DiNovo's Mediapad), the b3 just doesn't work anymore.

Did you change anything ?

While I'm at it, I don't know if it will be of any use for you, but with the logitech driver, I've to rename foobar.exe to winamp.exe to make it work. I don't know if you can do anything about it or if it is on the Logitech side ?

Thanks any way for this really useful plugins !
Title: foo_winamp_spam 0.9 beta
Post by: Ran Sagy on 2006-04-01 20:50:41
Just wanted to say thanks alot for updating this. If you remember, I once emailed you about the sourcecode of this plugin and a possible update for v0.9 when it comes out. Well, I'm happy to say i figured out some kind of foobar plugin to do this myself (via foosion's COM Server), But im very happy you kept updating this plugin. It does superbly for alot of people (I can notice that, like rogue`, as a fellow #GTSdll helper).

Two thumbs up, r1ch :]
Title: foo_winamp_spam 0.9 beta
Post by: Seldaek on 2006-04-03 03:11:57
It would be cool if the plugin returned no file playing when foobar's paused. My mIRC script reads current playing file from BSPlayer when foobar returns nothing so it's pretty annoying as I'm used to only pause and not stop, but if you don't want to change it I guess I'll get used to it someday...
Title: foo_winamp_spam 0.9 beta
Post by: R1CH on 2006-04-03 05:15:36
Quote
It would be cool if the plugin returned no file playing when foobar's paused. My mIRC script reads current playing file from BSPlayer when foobar returns nothing so it's pretty annoying as I'm used to only pause and not stop, but if you don't want to change it I guess I'll get used to it someday...
[a href="index.php?act=findpost&pid=378407"][{POST_SNAPBACK}][/a]

The Winamp API code that returns paused/playing/stopped state should work for this purpose. I don't believe winamp stops returning the info when the song is paused so this component shouldn't either.
Title: foo_winamp_spam 0.9 beta
Post by: Seldaek on 2006-04-03 12:31:07
Ok no problem but could you give me the command to request playing state? I found some stuff like IPC_ISPLAYING in the SDK but it doesn't work so I guess you renamed it. Anyway if you would have a full list of commands supported by r1dll it would be great.
Title: foo_winamp_spam 0.9 beta
Post by: Sneltrekker on 2006-04-03 16:03:35
Works great for me, though I also have the console spam.

Using it for Samurize, which queries: song time, passed time, title, artist.
Title: foo_winamp_spam 0.9 beta
Post by: 2Pacalypse on 2006-04-13 13:30:55
ive got a logitech mx5000 keyboard with a lcd is there anyway to make this work with foobar (display tack info) like it does with winamp
Title: foo_winamp_spam 0.9 beta
Post by: R1CH on 2006-04-16 15:17:46
Ok no problem but could you give me the command to request playing state? I found some stuff like IPC_ISPLAYING in the SDK but it doesn't work so I guess you renamed it. Anyway if you would have a full list of commands supported by r1dll it would be great.

That's supported and (should) work fine.

ive got a logitech mx5000 keyboard with a lcd is there anyway to make this work with foobar (display tack info) like it does with winamp

If it doesn't work "out of the box" with foo_winamp_spam, open up the console and paste which messages types are shown as unsupported.
Title: foo_winamp_spam 0.9 beta
Post by: DeathWolf on 2006-04-16 18:42:12
any hope of seeing the playlist size/current number working or is it a functional limitation of the new .9?
Title: foo_winamp_spam 0.9 beta
Post by: Seldaek on 2006-04-17 01:40:39

Ok no problem but could you give me the command to request playing state? I found some stuff like IPC_ISPLAYING in the SDK but it doesn't work so I guess you renamed it. Anyway if you would have a full list of commands supported by r1dll it would be great.

That's supported and (should) work fine.

I would like to believe you but as I said I couldn't get it to work so could you please tell me what's the exact command? $dll(r1dll.dll,IPC_ISPLAYING,) doesn't work, but it should be something close.. and may I rerequest the full list of available commands ?
Thanks
Title: foo_winamp_spam 0.9 beta
Post by: R1CH on 2006-04-17 04:45:22


Ok no problem but could you give me the command to request playing state? I found some stuff like IPC_ISPLAYING in the SDK but it doesn't work so I guess you renamed it. Anyway if you would have a full list of commands supported by r1dll it would be great.

That's supported and (should) work fine.

I would like to believe you but as I said I couldn't get it to work so could you please tell me what's the exact command? $dll(r1dll.dll,IPC_ISPLAYING,) doesn't work, but it should be something close.. and may I rerequest the full list of available commands ?
Thanks

Oh sorry I didn't read you were using R1DLL. At present R1DLL doesn't have an export for checking whether a song is playing or not. I may add it to a future version.
Title: foo_winamp_spam 0.9 beta
Post by: Seldaek on 2006-04-17 05:44:15
Well.. is there any other way to achieve that ? Through mIRC so I need a dll to query that will query winamp_spam.. I tried using another dll made for winamp, and when I check the state of "winamp" it says either playing or stopped, and when in pause it's still playing..
Title: foo_winamp_spam 0.9 beta
Post by: 2Pacalypse on 2006-04-17 19:14:54

Ok no problem but could you give me the command to request playing state? I found some stuff like IPC_ISPLAYING in the SDK but it doesn't work so I guess you renamed it. Anyway if you would have a full list of commands supported by r1dll it would be great.

That's supported and (should) work fine.

ive got a logitech mx5000 keyboard with a lcd is there anyway to make this work with foobar (display tack info) like it does with winamp

If it doesn't work "out of the box" with foo_winamp_spam, open up the console and paste which messages types are shown as unsupported.


can you help me out here.  it doesnt work out of the box, but i dont know what you want me to paste into the console.  there is no unsupported messages
Title: foo_winamp_spam 0.9 beta
Post by: cynos on 2006-04-18 13:27:17
I just wanted to add something regarding the Logitech keyboard. I own a Logitech G15 with LCD and there is a small program (LCDMedia.exe) to display some information from players like Winamp. It works "out-of-the-box" by using this plugin, but I get a lot of
Code: [Select]
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 610.

Fortunatly I use my own program (and the ComServer) and not Logitech's ugly one.
Title: foo_winamp_spam 0.9 beta
Post by: Olliver Sloppytongs on 2006-04-21 02:06:32
Feature Request: Is it possible to add a variable that returns only the directory path of the file?  This way we could setup an external program like Samurize to display %Path%\folder.jpg for album art that's not embedded in the tag?
Title: foo_winamp_spam 0.9 beta
Post by: Mangix on 2006-04-30 01:21:54
i keep getting the error "WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 640." in the console everytime i change the song.

the only way that this can happen is if i click "Next", "Random" or if the song changes by itself(the previous song finished). so it has to do with changing the info. however, when i click "Previous", the error doesn't seem to appear which i found to be weird.

edit: also, i keep getting a messagebox saying "metadb_handle leaks: # objects". the # is always random and foobar nearly crashes when i try to exit it. although that could be the cause of audioscribbler although i really doubt it.

edit2: just checked, it also does the error with Previous. so the error happens everytime the song changes.

edit3: also, on any file other than mp3, the info isn't correctly shown. it doesn't show the tracknumber(always 0 or a random number) and it also doesn't show the album info.
Title: foo_winamp_spam 0.9 beta
Post by: krazy on 2006-05-08 04:29:20
Been using this just recently to feed now-playing info to Miranda IM, and noticed that when scanning replaygain, the song being scanned is the one sent by foo_winamp_spam instead of the one being played.
Title: foo_winamp_spam 0.9 beta
Post by: Duble0Syx on 2006-05-09 04:21:46
Wow.  Thanks to this I can use my ATI remote with foobar 0.9.x!  Few minor issue though.  The ATI Remote Wonder has a plugin for controlling winamp, I am using a modified version that allows you to control it even when it's minimized.  The remote functions with foobar using this, however the play button on the remote just gives a Unsupported WM_USER error.  The pause button functions as Play/Pause.  Also seeking track doesn't not, same error, differen number at the end.  I can confirm these button function as they should with winamp.  Even if this is not resolved I'd like to say thank you for allowing to finally switch to the new foobar.
Title: foo_winamp_spam 0.9 beta
Post by: Mindflux on 2006-05-11 04:11:39
I know this is going to sound odd, but since i added foo_winamp_spam my foo_audioscrobbler program quit reporting songs to last.fm.

If I remove the foo_winamp_spam.dll and restart foobar the audioscrobbler works again.
Title: foo_winamp_spam 0.9 beta
Post by: Ran Sagy on 2006-05-11 18:50:05
I always get these two in the console while working:

   WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 124.
   WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 120.

I suppose it has to do with the mIRC addon im using to display info, GTSdll. It probably requests some sort of info not implemented in the dll yet? Not sure.
Title: foo_winamp_spam 0.9 beta
Post by: R1CH on 2006-05-16 04:02:04
Wow.  Thanks to this I can use my ATI remote with foobar 0.9.x!  Few minor issue though.  The ATI Remote Wonder has a plugin for controlling winamp, I am using a modified version that allows you to control it even when it's minimized.  The remote functions with foobar using this, however the play button on the remote just gives a Unsupported WM_USER error.  The pause button functions as Play/Pause.  Also seeking track doesn't not, same error, differen number at the end.  I can confirm these button function as they should with winamp.  Even if this is not resolved I'd like to say thank you for allowing to finally switch to the new foobar.

Can you post the numbers it gives?
Title: foo_winamp_spam 0.9 beta
Post by: germanjulian on 2006-05-26 12:38:50
hey works great with my G15 keyboard (songs display correctly on LCD and buttons work)

thanks

UPSSS: doesnt work when the program is minimized

Duble0Syx can you tell me how you setup this plugin that you can control foobar minimized?
thanks
Title: foo_winamp_spam 0.9 beta
Post by: Ran Sagy on 2006-05-27 19:32:47
R1CH, I was wondering if it could be possible to also return dynamic info in the string. Things like %playback_time% and the playlist index\length.
Title: foo_winamp_spam 0.9 beta
Post by: crono cloud on 2006-06-02 04:17:29
anyone ever find a solution to the high cpu usage when evillyrics is running

and was there ever a fix so that the track number was not '0'?
Title: foo_winamp_spam 0.9 beta
Post by: Sphix on 2006-06-02 04:36:48
My Philips Remote Control works with Winamp but it doesn't w/ foobar2k even with this plugin
Why this happens?!
Title: foo_winamp_spam 0.9 beta
Post by: amonrei on 2006-06-03 12:17:52
R1CH, I was wondering if it could be possible to also return dynamic info in the string. Things like %playback_time% and the playlist index\length.

I second that. 
Title: foo_winamp_spam 0.9 beta
Post by: alphaex32 on 2006-06-04 08:24:15
I have media buttons on my laptop keyboard that only work with the winamp API, however they will not work  with this plugin. When I used foobar 0.83, the plugin worked correctly, but now only the prev/skip buttons work and only when the foobar window is in focus.
Title: foo_winamp_spam 0.9 beta
Post by: krazy on 2006-06-04 08:36:04
I have media buttons on my laptop keyboard that only work with the winamp API, however they will not work  with this plugin. When I used foobar 0.83, the plugin worked correctly, but now only the prev/skip buttons work and only when the foobar window is in focus.

Try binding the buttons to functions in the 'Keyboard Shortcuts' section of preferences. Works well with my lappy media buttons!
Title: foo_winamp_spam 0.9 beta
Post by: alphaex32 on 2006-06-04 08:43:51

I have media buttons on my laptop keyboard that only work with the winamp API, however they will not work  with this plugin. When I used foobar 0.83, the plugin worked correctly, but now only the prev/skip buttons work and only when the foobar window is in focus.

Try binding the buttons to functions in the 'Keyboard Shortcuts' section of preferences. Works well with my lappy media buttons!


Unfortunately the media buttons aren't standard keyboard buttons, and don't get detected if I try to use them for shortcuts. They are hardwired to the BIOS or something. I just went back and tried the version in .83, and it definitely works, so it must be something that's been changed for the 0.9 version.
Title: foo_winamp_spam 0.9 beta
Post by: ftboomer on 2006-06-06 23:09:40
OK,  got this working and it's great. Now,  how do I get this into a foobar panel?
Title: foo_winamp_spam 0.9 beta
Post by: abwh on 2006-06-13 19:07:38
Got it working with the bemused server, and a j2me client!!!   

although... no playlist, and the volume is not sent either... 

what info do you need to support these options????



Gerardo
Title: foo_winamp_spam 0.9 beta
Post by: seethru on 2006-06-14 22:06:34
I too am experiencing the high cpu usage when running this plugin. Does anyone have any suggestions?
Title: foo_winamp_spam 0.9 beta
Post by: davitof on 2006-06-23 18:15:11
FWIW tested on the following system:
- Windows XP Home SP2 up to date
- foobar2000 0.9.0.0
- the modified version of HControl (http://power4gear.bk-kicks.com/forum/index.php?topic=7.msg44#msg44)
All seems to run smoothly, the four hardware buttons (previous, next, stop, play/pause) act as expected.

--
Frederic
Title: foo_winamp_spam 0.9 beta
Post by: ZephiriS on 2006-07-06 16:10:57
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 610.

Shitload of that.
Title: foo_winamp_spam 0.9 beta
Post by: alphaex32 on 2006-07-06 16:43:34
FWIW tested on the following system:
- Windows XP Home SP2 up to date
- foobar2000 0.9.0.0
- the modified version of HControl (http://power4gear.bk-kicks.com/forum/index.php?topic=7.msg44#msg44)
All seems to run smoothly, the four hardware buttons (previous, next, stop, play/pause) act as expected.

--
Frederic

I'm using and Asus laptop with the modified HControl also, and for some reason only my play and stop buttons are working with the latest foobar v0.9.2. Has there been a change recently that could have causes this, because it worked with the v0.9.1?
Title: foo_winamp_spam 0.9 beta
Post by: joeblow1102 on 2006-07-06 19:04:47
i think i read above that winamp doesn't send paused/playing/stopped info, but could this plugin do so?  so that it'll maybe send a blank string when foobar is stopped.  thanks for the great plugin.
Title: foo_winamp_spam 0.9 beta
Post by: tzamal on 2006-07-09 01:04:15
great, evillyrics is working!

thank you very much!

THe same thanks
Title: foo_winamp_spam 0.9 beta
Post by: KouZ on 2006-07-18 22:53:10
Hi. get at least the following errors while EvilLyrics is running. As usual for this problem I get them at machingun-repeat-rate and at the cost of at lest 10% CPU-Consumption

I am using EvilLyrics 0.1.7 Build 141 with WinAmp_Spam v0.90 on foobar0.9.3b1. The Bug doesn't occur for my old foobar0.8.3 with Winamp_Spam v0.82.

Would be nice if you could fix this. That would be the last step to finally substitute my old foobar by the 0.9-version

Code: [Select]
[23:28:06] WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1241704.
[23:28:07] WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243188.
[23:28:09] WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1236740.
Title: foo_winamp_spam 0.9 beta
Post by: ASk on 2006-07-20 18:36:36
my shell's plugin (BBMuse, for BB4Win) stopped getting 'paused' state from the plugin. In 0.8.3, the plugin worked fine.

This is the code that the plugin is using (relevant parts only):

Code: [Select]
#define WINAMP_PLAYBACK_STATUS 104
#define WINAMP_PLAYBACK_PLAYING 1
#define WINAMP_PLAYBACK_PAUSED 3

/////////////////////////////////////////////
playback = getWinampData(WINAMP_PLAYBACK_STATUS, WM_USER);
if(playback == WINAMP_PLAYBACK_PAUSED){

// do paused stuff
}
else {
// do something else, etc
}

/////////////////////////////////////

int getWinampData(int id, UINT type){
    if(hwndWinamp == NULL)return -1;
    
    return SendMessage(hwndWinamp, type, 0, id);
}


Well, apparently in the latest version of foo_winamp_spam this doesn't work. It used to work in 0.8.3. Any ideas?
Title: foo_winamp_spam 0.9 beta
Post by: Andrea on 2006-07-31 15:21:40
Is there any chance that this plugin starts working with the new gtalk music track display (http://www.hydrogenaudio.org/forums/index.php?showtopic=46956&st=0&gopid=416853&#entry416853)?
Title: foo_winamp_spam 0.9 beta
Post by: iamdanielj on 2006-08-09 17:17:55
Trying to get Beta3 working with aMSN's music plugin. It detects theirs a winamp, and puts the Music logo and the seperator in the personal comment area. However it doesn't pull any of the title or artist information. Code in console as follows:

Code: [Select]
Startup time : 0:01.078692
Handshaking: Client up to date.
Submit interval set to 1 seconds.
Handshake successful.
Submitting track to Audioscrobbler...
Submission succeeded.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 290.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 290.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 290.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 290.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 290.
....
....
....
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 290.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 290.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 290.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 290.


As you can see im getting littered with "WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 290.", I'm guessing every 15seconds as aMSN checks "winamp". Anyhelp would be much obliged.
Title: foo_winamp_spam 0.9 beta
Post by: cartman(2vd) on 2006-08-10 12:00:24
answer lays in winamp SDK:

Code: [Select]
#define IPC_GET_EXTENDED_FILE_INFO 290 //pass a pointer to the following struct in wParam
#define IPC_GET_EXTENDED_FILE_INFO_HOOKABLE 296
/* (requires Winamp 2.9+)
** to use, create an extendedFileInfoStruct, point the values filename and metadata to the
** filename and metadata field you wish to query, and ret to a buffer, with retlen to the
** length of that buffer, and then SendMessage(hwnd_winamp,WM_WA_IPC,&struct,IPC_GET_EXTENDED_FILE_INFO);
** the results should be in the buffer pointed to by ret.
** returns 1 if the decoder supports a getExtendedFileInfo method
*/
typedef struct {
  char *filename;
  char *metadata;
  char *ret;
  int retlen;
} extendedFileInfoStruct;


obviously not supported command by component (maybe there is problem in implementing this in foobar, maybe it was overlooked)
Title: foo_winamp_spam 0.9 beta
Post by: bojo on 2006-08-10 15:18:21
hey guys..

is it possible to use this thing to emulate a winamp window and use bemused with it?.

i have the bemused server thing, but it dies (no winamp directory to select).

what do i do? to set it up
Title: foo_winamp_spam 0.9 beta
Post by: jhoff80 on 2006-08-16 00:30:02
I also have an MX5000 keyboard and was hoping this would make the LCD work with foobar, but that doesn't seem to be the case.  Logitech hasn't been very forthcoming with info on how to get other programs to use this LCD either.
Title: foo_winamp_spam 0.9 beta
Post by: informale on 2006-08-17 14:10:21
jhoff80
Here (http://www.hydrogenaudio.org/forums/index.php?showtopic=43143&hl=logitech) may be a solution for you. It works for me.

R1CH
Could you please think of the way to "fool" apps and make them think that foobar's executable is "winamp.exe". Cause at the moment the only way to make Logitech diNovo LCDs work with fb2k is to rename the executable to winamp.exe (
Title: foo_winamp_spam 0.9 beta
Post by: kockroach on 2006-09-02 13:39:08
Just wanted to include myself in the group experiencing high CPU usage with this plugin.  My usage was as high as 50% even when the install of fb2k 0.9.3.1 was fresh, unaltered and just sitting open not playing.  The usage would only drop back down when this plugin was removed.
Title: foo_winamp_spam 0.9 beta
Post by: Rekoil on 2006-09-03 11:26:30
jhoff80
Here (http://www.hydrogenaudio.org/forums/index.php?showtopic=43143&hl=logitech) may be a solution for you. It works for me.

R1CH
Could you please think of the way to "fool" apps and make them think that foobar's executable is "winamp.exe". Cause at the moment the only way to make Logitech diNovo LCDs work with fb2k is to rename the executable to winamp.exe (

so rename it winamp.exe, it wont make foobar act any different
Title: foo_winamp_spam 0.9 beta
Post by: ghost_zero5 on 2006-09-06 10:36:27
Might be a stupid question:
But how do I get this component to work...?
I inputed it into the v0.9.3.1 component folder and in the preferences a page for configuration shows up...
There is only the possibility to change the title bar format string and that's it...

No other windows or options possible...
How can I connect it to a Winamp-Plugin..?

e.g.: The in_midi.dll ? I found a thread here where this was done through the foo_winamp_spam.dll (although I don't know how)...?
Title: foo_winamp_spam 0.9 beta
Post by: cartman(2vd) on 2006-09-06 17:51:07
Might be a stupid question:
But how do I get this component to work...?
I inputed it into the v0.9.3.1 component folder and in the preferences a page for configuration shows up...
There is only the possibility to change the title bar format string and that's it...

No other windows or options possible...
How can I connect it to a Winamp-Plugin..?

e.g.: The in_midi.dll ? I found a thread here where this was done through the foo_winamp_spam.dll (although I don't know how)...?


this component translate winamp API calls to foobars... it does not provide any "use winamp plugin in foobar" service... it never said it would
Title: foo_winamp_spam 0.9 beta
Post by: ghost_zero5 on 2006-09-06 19:47:39
Well I would say that plugins use the Winamp API? At least that is the only think I could say would use Winamp API... (OK, I never used Winamp never like it)
But OK
Title: foo_winamp_spam 0.9 beta
Post by: Andrea on 2006-09-12 15:34:40
I'm getting the :
Quote
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 120.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 120.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 120.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 120.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 120.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 120.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 120.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 120.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 120.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 120.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 120.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 120.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 120.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 120.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 120.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 120.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 120.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 120.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 120.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 120.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 120.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 120.


:/
Title: foo_winamp_spam 0.9 beta
Post by: cartman(2vd) on 2006-09-12 18:22:19
I'm getting the :
Quote

WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 120.


:/


from winamp sdk:

Code: [Select]
#define IPC_WRITEPLAYLIST 120
/* (requires Winamp 1.666+)
** SendMessage(hwnd_winamp,WM_WA_IPC,0,IPC_WRITEPLAYLIST);
**
** IPC_WRITEPLAYLIST writes the current playlist to <winampdir>\\Winamp.m3u,
** and returns the current playlist position.
** Kinda obsoleted by some of the 2.x new stuff, but still good for when
** using a front-end (instead of a plug-in)
*/


acording to this, the utility you are using sending this msg... its obviously not possible to convert this function in foobar.

maybe author can implement some sort of null point for this ipc calls so this console spaming stops... we will see if there ever be some new version.
Title: foo_winamp_spam 0.9 beta
Post by: Chronial on 2006-09-12 21:27:50
Maybe it would also make sense to implement this - since foobar can write m3u files I don't see why it shouldn't be possible. But I have never seen anything using this, so implementing it may be questionable.

After All it shouldn't be very difficult to fix most of the problems reported (and very easy to switch off the console message). But since the author didn't provide any sourcecode there's not much we can do but to wait.
Title: foo_winamp_spam 0.9 beta
Post by: cartman(2vd) on 2006-09-13 15:57:23
Maybe it would also make sense to implement this - since foobar can write m3u files I don't see why it shouldn't be possible. But I have never seen anything using this, so implementing it may be questionable.

After All it shouldn't be very difficult to fix most of the problems reported (and very easy to switch off the console message). But since the author didn't provide any sourcecode there's not much we can do but to wait.


first) the winampdir property could be a pain the a** because its most of time restored from registry (it could be but dont have to be possible to retrieve this from some ipc call... i dont know this sry  )
second) problem could be that foobar use absolutely different way of maintaining playlists than winamp so there alway will be some compromise.

the main reson of creating this component was to give ppl some translator from winamp api to foobars not to turn foobar virtualy in winamp. of course there are issues but basics works really great. i can retrieve curently playing songs from almost any program primarly written for winamp. i could also use some api calls for minimizing, opening, closing and so on...
Title: foo_winamp_spam 0.9 beta
Post by: Chronial on 2006-09-13 17:02:30
The path should be rather simple: When someone calls this, we store the playlist in the winamp path (per registry) and the foobar path (in case a program checks per executable). If winamp is not installed we can give the user the option to write a fake winamp path to registry.

The use of this call is pretty obvious: This way programs can display the whole playlist+current position. I can't see any problems for an implementation - write the currenty playing playlist, give the current position. There should be no problem at all.

Quote
the main reson of creating this component was to give ppl some translator from winamp api to foobars not to turn foobar virtualy in winamp. of course there are issues but basics works really great. i can retrieve curently playing songs from almost any program primarly written for winamp. i could also use some api calls for minimizing, opening, closing and so on...

People are posting about problems with programms trying to display the playlist. Implementing this would no way turn anything into winamp - it would just complete the simulation of the winamp IPC interface.
Title: foo_winamp_spam 0.9 beta
Post by: cartman(2vd) on 2006-09-13 19:20:38
The path should be rather simple: When someone calls this, we store the playlist in the winamp path (per registry) and the foobar path (in case a program checks per executable). If winamp is not installed we can give the user the option to write a fake winamp path to registry.

The use of this call is pretty obvious: This way programs can display the whole playlist+current position. I can't see any problems for an implementation - write the currenty playing playlist, give the current position. There should be no problem at all.


i see your point... well of course its also the way... how should component check to erase the path if its uninstalled from foobar??? or you prefer to have your registry prety corupted?  (no sory im just teasing you of course this is the way to achive this)...but there is a catch. it all depends on possibility to force foobar to save playlist in non-default format (default is fpl i presume) in non-default folder and silently and to do it repetedly (maybe even really fast but it depends on software which do this ipc 120 call)... if it is possible it could be done but dont forget that we are talking still only about one api call there is much much more... but this one at least looks like it is useable by someone. we should wait for authors opinion if he is still interested in this component (last post by r1ch in this topic May 16 2006)...
Title: foo_winamp_spam 0.9 beta
Post by: Chronial on 2006-09-13 20:17:17
Quote
we should wait for authors opinion if he is still interested in this component (last post by r1ch in this topic May 16 2006)...

We'll have to do after all... he has the sourcecode.

A lot of "winamp-compatible" stuff writes the winamp path and does no care for it - winamp itself left my registration info in the registry after beeing uninstalled.

Foobar can write playlists in m3u format - just do file->save playlist. I didn't check, but I'm quite sure there is an api-call for that. If winamp can do this repeatedly, foobar can do it, too...

Quote
it is possible it could be done but dont forget that we are talking still only about one api call there is much much more

Actually not
The component already supports most api calls. I checked the posts in this topic - the unsported api calls are mostly not valid - the others are very easy to implement.
Title: foo_winamp_spam 0.9 beta
Post by: Hall on 2006-11-06 07:37:09
URL broken! :-( Does anyone have a copy?
Title: foo_winamp_spam 0.9 beta
Post by: Morfeus on 2006-12-03 13:57:11
Is possile of implementing this (setting position of current playing song)?

Code: [Select]
#define IPC_JUMPTOTIME 106
/* (requires Winamp 1.60+)
** SendMessage(hwnd_winamp,WM_WA_IPC,ms,IPC_JUMPTOTIME);
** IPC_JUMPTOTIME sets the position in milliseconds of the
** current song (approximately).
** Returns -1 if not playing, 1 on eof, or 0 if successful
*/
Title: foo_winamp_spam 0.9 beta
Post by: Morfeus on 2006-12-03 19:45:09
and will you implement right version of IPC_GETOUTPUTTIME when mode is 0? it returns time in seconds with three ending zeros (e.g. the time in foobar is 00:09.5 and foo_winamp_spam will return 9000 not 9500 or something like that). Or can I get it from other IPC message?
Title: foo_winamp_spam 0.9 beta
Post by: R1CH on 2006-12-03 21:46:43
Regrettably I do not have time to continue working on this plugin, so I am releasing the source for anyone interested in taking over development.

http://r-1.ch/foo_r1dll_serve-src.zip (http://r-1.ch/foo_r1dll_serve-src.zip) (you can see by the name what this plugin was intended for )

The code isn't very pretty, it's been through 3 API changes I believe, but it's quite simple underneath it all. I will gladly host any updated versions on my main site at http://www.r1ch.net/stuff/foobar/ (http://www.r1ch.net/stuff/foobar/) if needed. The project file might contain several hard coded paths, so please check it before compiling.
Title: foo_winamp_spam 0.9 beta
Post by: JazzBrew on 2006-12-03 21:51:33
R1CH,

Works great on my Win2K system. I'm using foobar2000 v0.9.4.2, foo_winamp_spam v0.9 beta, and foo_xm 1.03. Artist & Title information from XM outputs just fine.

Good work. Thanks.
Title: foo_winamp_spam 0.9 beta
Post by: Chronial on 2006-12-03 21:58:24
Thanks for the source

As we now have access to the source I can implement missing features, if they are still requested.
So if you get Unsupported WM_USER messages, post again and I'll see what I can do.
Title: foo_winamp_spam 0.9 beta
Post by: Morfeus on 2006-12-04 14:09:21
Jumping in time

Code: [Select]
#define IPC_JUMPTOTIME 106
/* (requires Winamp 1.60+)
** SendMessage(hwnd_winamp,WM_WA_IPC,ms,IPC_JUMPTOTIME);
** IPC_JUMPTOTIME sets the position in milliseconds of the
** current song (approximately).
** Returns -1 if not playing, 1 on eof, or 0 if successful
*/



re-implement IPC_GETOUTPUTTIME for mode 0, to return right value (not only seconds with three ending zeros, e.g. SECONDS * 1000)

Maybe I'll help with something... in which compiler I'll have to compile it? Visual C++ 6 or just Dev-Cpp (MinGW)?

edit: I can now see in source, that in handling IPC_GETOUTPUTTIME is the time from foobar in seconds. Why? There's no way to get time in ms, even in seconds like 49.5 or 139.2?
Title: foo_winamp_spam 0.9 beta
Post by: Chronial on 2006-12-06 00:47:44
Version 0.91 is here

http://chron.visiondesigns.de/foobar2000/f..._spam_v0.91.zip (http://chron.visiondesigns.de/foobar2000/foo_winamp_spam_v0.91.zip)

Changes:
Quote
I can now see in source, that in handling IPC_GETOUTPUTTIME is the time from foobar in seconds. Why? There's no way to get time in ms, even in seconds like 49.5 or 139.2?

Have a look at the return type of playback_get_position() - it's double
Should work now, but I don't know of any software using this call.
Title: foo_winamp_spam 0.9 beta
Post by: mazy on 2006-12-06 12:41:39
i'm getting this when using EvilLyrics:

Code: [Select]
[13:40:25] WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1241704.
[13:40:25] WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1237188.
Title: foo_winamp_spam 0.9 beta
Post by: Chronial on 2006-12-06 12:57:18
These lParams are invalid.
I made the component ignore them, so they won't spam you console anymore.
Title: foo_winamp_spam 0.9 beta
Post by: Chronial on 2006-12-06 13:27:37
Here goes Version 0.92
http://chron.visiondesigns.de/foobar2000/f..._spam_v0.92.zip (http://chron.visiondesigns.de/foobar2000/foo_winamp_spam_v0.92.zip)

Changes
Made a hp for my components
http://chron.visiondesigns.de/foobar2000/ (http://chron.visiondesigns.de/foobar2000/)
Title: foo_winamp_spam 0.9 beta
Post by: mazy on 2006-12-07 01:31:10
thanks for the update! no more evillyric's spam
Title: foo_winamp_spam 0.9 beta
Post by: Ran Sagy on 2006-12-07 20:45:26
Thanks to r1ch and Chronial for keeping up with this. Can't say i'm using it anymore (switched to foosion's COM Server and a COM client of my own) but kudos are definitely deserved here. Good job
Title: foo_winamp_spam 0.9 beta
Post by: slinger1182 on 2006-12-08 00:07:46
Hey Chronial,

I use this plugin primarily for Gtalk's Now Playing mode. My console gets spammed with "Warning: foo_winamp_spam. lParam 120 not supported". Would you be able to fix that? Thanks.
Title: foo_winamp_spam 0.9 beta
Post by: Chronial on 2006-12-08 14:46:02
How did you get it to work with Gtalk?
Gtalk neither shows my current track nor causes console spam. The now playing feature just does not work at all.
Title: foo_winamp_spam 0.9 beta
Post by: slinger1182 on 2006-12-09 10:11:35
If you dont have Winamp installed, follow the instruction given by MEK on the following link.
http://www.hydrogenaudio.org/forums/index....55&hl=gtalk (http://www.hydrogenaudio.org/forums/index.php?showtopic=47155&hl=gtalk)

I have Winamp installed (for transferring music into my Sony portable player) and the Now Playing feature of Gtalk works for me and should work for anyone else too.
Title: foo_winamp_spam 0.9 beta
Post by: Chronial on 2006-12-09 22:42:22
So we are at v0.93
http://chron.visiondesigns.de/foobar2000/f..._spam_v0.93.zip (http://chron.visiondesigns.de/foobar2000/foo_winamp_spam_v0.93.zip)

Changes:
Implemented IPC_WRITEPLAYLIST (lParam 120) - If there is no winamp path set in registry, foobar sets it to its settings path during startup and deletes in on shutdown. Playlist is written into this path, so foobar will overwrite your winamp playlist, if this feature is activated and winamp installed.
Title: foo_winamp_spam 0.9 beta
Post by: slinger1182 on 2006-12-10 08:21:35
Works like a charm. Thanks!
Title: foo_winamp_spam 0.9 beta
Post by: Morfeus on 2006-12-10 14:22:55
Is there any chance implementing something like checking if user is seeking (in foobar, not through IPC_JUMPTOTIME)?
Title: foo_winamp_spam 0.9 beta
Post by: Chronial on 2006-12-10 16:35:29
I'm sorry, but this component should emulate the winamp api, and I will not implement any other functionality than that.

Or did I get you wrong?
Title: foo_winamp_spam 0.9 beta
Post by: Morfeus on 2006-12-10 20:31:02
No, I didn't, but I just hope you can implement it, but if not, it doesn't matter. I'll try to do it on my own. Anyway thanks!
Title: foo_winamp_spam 0.9 beta
Post by: ilikedirtthe2nd on 2006-12-14 18:33:17
Hi, just found out that there is an updated Version. Evillyrics (build 142) still spams my console. I have the following version of the plugin:

foo_winamp_spam.dll (2006-12-09 23:36:08)
    Winamp API Emulator 0.93

The message is: WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1235828.
Title: foo_winamp_spam 0.9 beta
Post by: Andrea on 2006-12-14 18:53:23
So we are at v0.93
http://chron.visiondesigns.de/foobar2000/f..._spam_v0.93.zip (http://chron.visiondesigns.de/foobar2000/foo_winamp_spam_v0.93.zip)

Changes:
Implemented IPC_WRITEPLAYLIST (lParam 120) - If there is no winamp path set in registry, foobar sets it to its settings path during startup and deletes in on shutdown. Playlist is written into this path, so foobar will overwrite your winamp playlist, if this feature is activated and winamp installed.



Hi! Thank you so much for taking over the development! Works like a charm
Title: foo_winamp_spam 0.9 beta
Post by: Sphix on 2006-12-14 19:07:12
Thanks for the update ;D
Title: foo_winamp_spam 0.9 beta
Post by: Chronial on 2006-12-14 21:13:19
Hi, just found out that there is an updated Version. Evillyrics (build 142) still spams my console. I have the following version of the plugin:

foo_winamp_spam.dll (2006-12-09 23:36:08)
    Winamp API Emulator 0.93

The message is: WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1235828.


Evillyrics must generate these numbers at random ^^.
Will be fixed in the next release
Title: foo_winamp_spam 0.9 beta
Post by: amonrei on 2006-12-15 03:54:09
Thanks for the update but i have a request. 

R1CH, I was wondering if it could be possible to also return dynamic info in the string. Things like %playback_time% and the playlist index\length.
I second that. 
Title: foo_winamp_spam 0.9 beta
Post by: Costa666 on 2006-12-15 11:35:56
Thanks for the update. Here is the error I still get:
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243188.
Title: foo_winamp_spam 0.9 beta
Post by: Chronial on 2006-12-16 01:47:06
R1CH, I was wondering if it could be possible to also return dynamic info in the string. Things like %playback_time% and the playlist index\length.

I don't quite know if I understood this request correctly, but did you have a look at cwb_hooks?

Well, did a release for all the poor evillyrics haunted people out there
Get it here (http://chron.visiondesigns.de/foobar2000/#foo_winamp_spam)

Changes:
Fixed the Evillyrics spam - all lParam > 1200000 are ignored (they don't have any meaning after all)
Title: foo_winamp_spam 0.9 beta
Post by: aNTropocentrio on 2006-12-16 02:11:14
Is it posible to use this plugin to control Winamp visualisations. That would be awesome.
Title: foo_winamp_spam 0.9 beta
Post by: Ran Sagy on 2006-12-16 11:43:12
Frankly, Even i don't remember why i asked that

Probably had to do with the plugin not returning info for winamp API calls that involve dynamic info, especially playlist position\length.
Title: foo_winamp_spam 0.9 beta
Post by: Chronial on 2006-12-16 15:47:41
Is it posible to use this plugin to control Winamp visualisations. That would be awesome.

Once and for all:
The aim of this component is to imitate winamp's behavior towards other applications (like your mIRC plugin, google talk etc.). I am not going to add any feature to this component that is not present in winamp or is part of winamp's internal behavior (like winamp's communication with it's visualizations).

I hope this makes it clear.
(No, I'm not pissed or something alike - just wanted to make that clear )
Title: foo_winamp_spam 0.9 beta
Post by: pIv on 2006-12-21 14:08:54
It is possible add playlist-number of playing track?

When i use current version of plugin i see next:

I use PowerOff program and it have option - shutdown after "n" winamp tracks are played (not work!).
Also it have option - show track name in header of active window (work!)
Title: foo_winamp_spam 0.9 beta
Post by: Chronial on 2006-12-21 14:54:48
Sry, I didn't quite understand your problem.

Can you give me the exact name or a download link of the program that is not working?
Title: foo_winamp_spam 0.9 beta
Post by: pIv on 2006-12-21 16:20:46
I place link to program site

http://www.videozona.ru/software/PowerOff/PowerOff.asp (http://www.videozona.ru/software/PowerOff/PowerOff.asp)

Only restriction - language is russian.
Title: foo_winamp_spam 0.9 beta
Post by: Yotsuya on 2007-01-05 04:04:47
First off thank you for developing this compenent, I primarily use it for my playback info on google talk. There are however a couple issues I'd like to bring up and hopefully have resolved.

1) Is there any way to reduce the frequency which this program rewrites the winamp playlist? Under the current version it appears the playlist gets rewritten nearly every second which can cause a race condition resulting in sharing errors when other programs are trying to read the playlist. Maybe have it only update when the track changes and/or playback state changes?

2) Real winamp writes meta information as a comment on a line between the filename lines. While I generally dislike using comments as code, many 3rd party programs for winamp process this information. Specifically I am trying to get X-Winamp for XChat working.. it is able to report the currently playing track however unable to discover the filename based on the playlist for the fileserver options.
Title: foo_winamp_spam 0.9 beta
Post by: Chronial on 2007-01-07 23:17:02
First off thank you for developing this compenent, I primarily use it for my playback info on google talk. There are however a couple issues I'd like to bring up and hopefully have resolved.

1) Is there any way to reduce the frequency which this program rewrites the winamp playlist? Under the current version it appears the playlist gets rewritten nearly every second which can cause a race condition resulting in sharing errors when other programs are trying to read the playlist. Maybe have it only update when the track changes and/or playback state changes?

Quote Winamp API:
Code: [Select]
#define IPC_WRITEPLAYLIST 120
/* (requires Winamp 1.666+)
** SendMessage(hwnd_winamp,WM_WA_IPC,0,IPC_WRITEPLAYLIST);
**
** IPC_WRITEPLAYLIST writes the current playlist to <winampdir>\\Winamp.m3u,
** and returns the current playlist position.
** Kinda obsoleted by some of the 2.x new stuff, but still good for when
** using a front-end (instead of a plug-in)
*/

The playlist gets written every time "winamp" is asked to do so (which gtalk does once per second) - just like it should. Did you actually get any errors or do you just fear them? If you get errors, I wonder how gtalk works with winamp. If you close gtalk, the playlist won't get written after all (as long as no other app asks "winamp" to do so).

Quote
2) Real winamp writes meta information as a comment on a line between the filename lines. While I generally dislike using comments as code, many 3rd party programs for winamp process this information. Specifically I am trying to get X-Winamp for XChat working.. it is able to report the currently playing track however unable to discover the filename based on the playlist for the fileserver options.

Sry, but writing this comments is quite a lot of work, since I'm using the foobar playlist writing functionality right now. I'm not going to implement this, but you could ask for it to get implemented into the foobar core playlist writer (since that's where it belongs anyway).


PS: pIv, I'm sorry, but I can't help you - don't understand anything of this program. But you can do this with foo_scheduler.
Title: foo_winamp_spam 0.9 beta
Post by: OddbOd on 2007-01-08 14:39:48
Thanks Chronial/R1CH, I've been using this with ezQuake (http://ezquake.sourceforge.net/) and it works a treat. A few minor things like playlist display and volume adjustment from within the game don't work but I don't consider those important.
Title: foo_winamp_spam 0.9 beta
Post by: Chronial on 2007-01-08 17:25:17
Do you get any "Unsupported WM_USER, lParam ..." Messages in your foobar console?
Maybe I could implement the missing features.
Title: foo_winamp_spam 0.9 beta
Post by: Yotsuya on 2007-01-08 18:58:23
The playlist gets written every time "winamp" is asked to do so (which gtalk does once per second) - just like it should. Did you actually get any errors or do you just fear them? If you get errors, I wonder how gtalk works with winamp. If you close gtalk, the playlist won't get written after all (as long as no other app asks "winamp" to do so).


My foobar is randomly crashing with sharing violation errors. I tracked it down to the fake winamp playlist. I did some more experimentation following your feedback and this behavior goes away when gtalk is not running (Google Talk, XChat, and Foobar are accessing the playlist). I also noticed that my Google Talk process jumps in CPU consumption whenever foobar dies with the sharing violation so there must be something fishy going on in the way google talk handles the playlist, I wonder why it hammers it so much.
Title: foo_winamp_spam 0.9 beta
Post by: Morfeus on 2007-01-08 20:11:43
Can you implement these?

wParam 40144
wParam 40148

I think these are for forward, backward buttons (quick seeking, e.g. 5-sec forward or backward). Thanks!
Title: foo_winamp_spam 0.9 beta
Post by: TheStupidOne on 2007-01-09 03:28:09
Getting the following unsupported errors when trying to use the TwinsMediaPlayer addon for KVIRC.  The media buttons work, but the track display info doesn't, except for length and bitrate, and only on the first song played.

Code: [Select]
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 122.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 13123.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 10000.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 13123.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 10000.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 13123.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 10000.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 13123.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 5000.

It cycles this list of unsupported lParams about every second.
Title: foo_winamp_spam 0.9 beta
Post by: OddbOd on 2007-01-09 06:29:38
Actually now that you mention it I am getting:

Code: [Select]
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 122.

It happens once at startup and then spams the console if you enter the game's MP3 Player menu.
Title: foo_winamp_spam 0.9 beta
Post by: cartman(2vd) on 2007-01-09 16:54:57
word from winamp SDK:

Code: [Select]
#define IPC_SETVOLUME 122
/* (requires Winamp 2.0+)
** SendMessage(hwnd_winamp,WM_WA_IPC,volume,IPC_SETVOLUME);
** IPC_SETVOLUME sets the volume of Winamp (from 0-255).
*/


for all others. all important ipc calls (those lparams thing) are usualy lower then 300 (there are calls with higher number but these are winamp specific like "open popup", "return skin file" and so on)... but even those are all bellow 1000 (from fast look in SDK) so anything up from this number is just rubish from utility you use. pls dont ask anyone to implement it these calls are not in SDK and are not documented.

i had fast thought that these insane calls can come up from joinin lparam string and wparam together but it doesnt look like that.

problem is that some software use really brute force on winamp and hope that noone in winamp will use xGB playlist and just spam conponent with stupid calls.

ps: that 122 ipc call could be implemented it depends on Chonical

Can you implement these?

wParam 40144
wParam 40148

I think these are for forward, backward buttons (quick seeking, e.g. 5-sec forward or backward). Thanks!


Chronical:

Code: [Select]
/*
** Finally there are some WM_COMMAND messages that you can use to send
** Winamp misc commands.
**
** To send these, use:
**
** SendMessage(hwnd_winamp, WM_COMMAND,command_name,0);
*/

#define WINAMP_OPTIONS_EQ               40036 // toggles the EQ window
#define WINAMP_OPTIONS_PLEDIT           40040 // toggles the playlist window
#define WINAMP_VOLUMEUP                 40058 // turns the volume up a little
#define WINAMP_VOLUMEDOWN               40059 // turns the volume down a little
#define WINAMP_FFWD5S                   40060 // fast forwards 5 seconds
#define WINAMP_REW5S                    40061 // rewinds 5 seconds

// the following are the five main control buttons, with optionally shift
// or control pressed
// (for the exact functions of each, just try it out)
#define WINAMP_BUTTON1                  40044
#define WINAMP_BUTTON2                  40045
#define WINAMP_BUTTON3                  40046
#define WINAMP_BUTTON4                  40047
#define WINAMP_BUTTON5                  40048
#define WINAMP_BUTTON1_SHIFT            40144
#define WINAMP_BUTTON2_SHIFT            40145
#define WINAMP_BUTTON3_SHIFT            40146
#define WINAMP_BUTTON4_SHIFT            40147
#define WINAMP_BUTTON5_SHIFT            40148
#define WINAMP_BUTTON1_CTRL             40154
#define WINAMP_BUTTON2_CTRL             40155
#define WINAMP_BUTTON3_CTRL             40156
#define WINAMP_BUTTON4_CTRL             40157
#define WINAMP_BUTTON5_CTRL             40158

#define WINAMP_FILE_PLAY                40029 // pops up the load file(s) box
#define WINAMP_FILE_DIR                 40187 // pops up the load directory box
#define WINAMP_OPTIONS_PREFS            40012 // pops up the preferences
#define WINAMP_OPTIONS_AOT              40019 // toggles always on top
#define WINAMP_HELP_ABOUT               40041 // pops up the about box :)

#define ID_MAIN_PLAY_AUDIOCD1           40323 // starts playing the audio CD in the first CD reader
#define ID_MAIN_PLAY_AUDIOCD2           40323 // plays the 2nd
#define ID_MAIN_PLAY_AUDIOCD3           40323 // plays the 3nd
#define ID_MAIN_PLAY_AUDIOCD4           40323 // plays the 4nd


maybe not all but some of these could be implemented imho
Title: foo_winamp_spam 0.9 beta
Post by: Chronial on 2007-01-09 17:03:56
Thanks, but I've got the winamp api myself - and my nick is chronial (no second c )

But if you've got winamp installed you could help me by telling me what these buttons actually do
WINAMP_BUTTON1_SHIFT            40144
WINAMP_BUTTON5_SHIFT            40148

If they actually do seek, I'd need to now by how far they seek.

*edit*
Well, I could actually need this info for all five buttons (these are prev, play, pause, stop and next) - with shift and ctrl pressed.
Title: foo_winamp_spam 0.9 beta
Post by: cartman(2vd) on 2007-01-09 19:16:59
Thanks, but I've got the winamp api myself - and my nick is chronial (no second c )

But if you've got winamp installed you could help me by telling me what these buttons actually do
WINAMP_BUTTON1_SHIFT            40144
WINAMP_BUTTON5_SHIFT            40148

If they actually do seek, I'd need to now by how far they seek.

*edit*
Well, I could actually need this info for all five buttons (these are prev, play, pause, stop and next) - with shift and ctrl pressed.


humbly sory for nick misspell  i was just tryin to help and express something that some ppl obviously still didnt get. hope it will be clear now but maybe not.

ps: sry dont have winamp installed nor have any of these ("send one gvantzilion of ipc calls in one pikosec ") utilities
Title: foo_winamp_spam 0.9 beta
Post by: DrO on 2007-01-09 19:53:00
for buttons 1 and 5::

the 'shift' actions do rewind and fastforward appropriately with the jump time generally being 5seconds

the 'ctrl' actions will jump to the first or last entries in the playlist (if winamp's shuffle is disabled and to the first or last entries in the shuffle list if shuffle is enabled

for button 2::
normal action is play/restart playback of currently playing track
shift does the open file dialog
ctrl does the open url dialog

for button 3::
normal action is pause
shift and ctrl do not have any defined actions

for button 4::
normal action is to stop
shift does stop with fadeout (can't remember the duration on the fade)
ctrl does stop after current

-daz
Title: foo_winamp_spam 0.9 beta
Post by: Chronial on 2007-01-09 20:40:13
Thanks a lot for the info
Title: foo_winamp_spam 0.9 beta
Post by: DrO on 2007-01-09 21:30:23
not a problem, anything else then don't hesitate to ask

-daz
Title: foo_winamp_spam 0.9 beta
Post by: Chronial on 2007-01-10 15:08:24
Well, it's all implemented now, but I could need something that tries to set winamp's volume so I can test this.
Title: foo_winamp_spam 0.9 beta
Post by: Morfeus on 2007-01-10 16:48:40
Here's volume changer (http://program.php5.cz/volume.zip), which changes volume by steps (WINAMP_VOLUMEUP, WINAMP_VOLUMEDOWN) or with slider (IPC_SETVOLUME). Steps works fine with Winamp and foobar, but slider only for Winamp.

btw. would you release src?
Title: foo_winamp_spam 0.9 beta
Post by: Garfield4 on 2007-01-12 10:45:46
For those of you using Yahoo's Widget Engine, I downloaded Winamp Remote v.1 and all simple functions work, which suits me fine (e.g. play, pause, next track, skin colour change). Features that dont work are volume control, seek bar, open / quit foobar and of course ratings).

Here's a link for those interested.

(http://img407.imageshack.us/img407/1428/winampremotekn4.jpg) (http://imageshack.us)

http://www.widgetgallery.com/view.php?widget=36544 (http://www.widgetgallery.com/view.php?widget=36544)
Title: foo_winamp_spam 0.9 beta
Post by: Morfeus on 2007-01-12 16:15:16
Chronial: Will you implement VBR updating (lParam = IPC_GETINFO, wParam = 1)? Thanks!
Title: foo_winamp_spam 0.9 beta
Post by: Chronial on 2007-01-12 16:33:39
I don't think this command is meant to report current bitrate - the current implementation seems correct to me.
Title: foo_winamp_spam 0.9 beta
Post by: Morfeus on 2007-01-14 11:34:52
No sorry, you are wrong! Now I tried it with Winamp 5.3 and it changes bitrate as playback goes on. So, will you implement it or not (I'm just asking)? Your goal is to emulate Winamp API, and Winamp IPC API is doing that, so...
Title: foo_winamp_spam 0.9 beta
Post by: zuk4u on 2007-01-16 08:44:31
I've installed Vista and this plugin causes 30-35% cpu usage (sempron 3000+), any ideas how to fix it?
Title: foo_winamp_spam 0.9 beta
Post by: hotzenpl0tz on 2007-01-22 11:31:27
For me, under Vista this plugin seems to be the cause of "Unhandled Exception: Bad Allocation" errors. I have been playing around for some hours now and with the removing of this component my foobar has stopped crashing. It would frequently crash on song changes before, and when I clicked around in the playlist and changed songs too often/fast. These symptoms are now totally gone (running stable for more than 6 hours now and frantic clicking doesn't cause a crash).
Title: foo_winamp_spam 0.9 beta
Post by: Chronial on 2007-01-22 15:44:36
I'm sorry, but I haven't got any vista testing machine at hand, and I think I won't use vista until microsoft forces me to do so.
Maybe the implementation of VBR updating will fix this. But I don't have a lot of time at the moment.
Title: foo_winamp_spam 0.9 beta
Post by: thegeek on 2007-01-22 22:50:39
Could you please add track seeking?
Title: foo_winamp_spam 0.9 beta
Post by: Ran Sagy on 2007-01-23 16:18:36
Building the component against the latest Foobar SDK should solve any Vista problems. At least, It solved that specific error for the other components.
Title: foo_winamp_spam 0.9 beta
Post by: thegeek on 2007-02-01 21:14:03
A bump here, track seeking would really be appreciated (lparam 106).
If you don't have time or don't want to do it, please consider releasing source (I'll try to add it).
Title: foo_winamp_spam 0.9 beta
Post by: Morfeus on 2007-02-03 14:23:43
thegeek: lParam = 106, seeking is already implemented, download the latest version of foo_winamp_spam plugin. If you don't belive me, use this program (http://program.php5.cz/NowPlaying.zip), which works with both foobar (foo_winamp_spam) and winamp. Of course with foobar doesn't work volume chaning, as Chronial hasn't implemented it yet.

Things which I found out that aren't implemented:
- volume setting - lParam = 122, wParam = volume
- VBR bitrate updating - lParam = 125, wParam = 1

You said you want to EMULATE Winamp API, and Winamp supports everything above. So, it's your move now. Implement it, or release source code, if you don't want to implement it. Thanks!

btw. I have found that foo_winamp_spam and Winamp 5.32 (latest) returns bits per sample differently. Winamp returns 44 and foo_winamp_spam returns 44100. foo_winamp_spam does it right.
Title: foo_winamp_spam 0.9 beta
Post by: thegeek on 2007-02-05 18:51:15
No, track seeking does _not_ work.
The program you linked shows the track progress, but you can NOT _seek_.
I did however use the wrong lparam;P
It's not 106, I have this in my code:
PostMessage(hwndFoobar2000,TRACKSET, 1, Round (  (Wparam/100) * SendMessage(hwndFoobar2000,TRACKLENGTH, 0, 0) ));
and
TRACKSET =  WM_USER + 13 ;

Sorry about the mistake;P
However, to get on topic: _Please_ release source code.
Title: foo_winamp_spam 0.9 beta
Post by: Morfeus on 2007-02-05 19:32:29
No, YOU are wrong... don't make me blind, cause I'm not blind!

Code: [Select]
WM_USER = 1024; //(0x400)
IPC_JUMPTOTIME = 106; //(0x6A)

ret = SendMessage(hWnd, WM_USER, ms, IPC_JUMPTOTIME);


Here's my prove! You are using bad Message for foo_winamp_spam. Sorry, you are using Winamp IPC API WRONG way.

Code: [Select]
#define IPC_JUMPTOTIME 106
/* (requires Winamp 1.60+)
** SendMessage(hwnd_winamp,WM_WA_IPC,ms,IPC_JUMPTOTIME);
** IPC_JUMPTOTIME sets the position in milliseconds of the
** current song (approximately).
** Returns -1 if not playing, 1 on eof, or 0 if successful
*/


Can you see that? You have to use SendMessage, NOT PostPessage. I have question: do you get something right from Winamp (foo_winamp_spam)? I don't think so.

Code: [Select]
/* message used to sent many messages to winamp's main window. 
** most all of the IPC_* messages involve sending the message in the form of:
**   result = SendMessage(hwnd_winamp,WM_WA_IPC,(parameter),IPC_*);
*/
#define WM_WA_IPC WM_USER


And if you now still think you are right, start thinking about it. Think about all code sheets I've posted above.

And at last (for making things clear): foo_winamp_spam SUPPORTS seeking!!!
Title: foo_winamp_spam 0.9 beta
Post by: DrO on 2007-02-05 20:37:21
Quote
Can you see that? You have to use SendMessage, NOT PostPessage. I have question: do you get something right from Winamp (foo_winamp_spam)? I don't think so.
using PostMessage(..) is a valid way of using some of the apis (basically those which you don't need to get the return value) and is used both by myself, others and internally in some instances - as long as the wndproc receives a valid message irrespective of it being done straight away (SendMessage(..) style) or delayed until the message pump gets to the message (PostMessage(..) style) and fits with how the api is implemented ie if you need the return value or not, then it doesn't matter.

with the case of IPC_JUMPTOTIME, it can be happily used with PostMessage(..) - i've got a few plugin's which do it so SendMessage(..) is not a fixed requirement for that api.

also your tone in your post comes across aggressively to an extent (is just how it seems to me).

-daz
Title: foo_winamp_spam 0.9 beta
Post by: Morfeus on 2007-02-06 18:11:26
Yes, I knew about PostMessage, but I didn't use it.

btw. i was angry when thegeek repeately wrote about that foo_winamp_spam doesn't support seeking. I have to prove the opposite (as that is right)... that's why the post was aggressive

btw. I think he won't get from Winamp (or foo_winamp_spam) anything NOT because of using PostMessage. That's ok. But he is using BAD messages and he mixed up lParam and wParam params
Title: foo_winamp_spam 0.9 beta
Post by: thegeek on 2007-02-06 23:08:41
Well, if seeking actually works that would be great.
So far I used the app you posted with a completely fresh reinstall of foobar and with foo_winamp_spam from the link in the first post of this thread. Is there a newer version?
I have a song playing and the app you linked to does show the track progress, however if I change position on the slider it just "snaps" back. Exactly like the program I'm working on.
As for the code I posted I know it works, since it works with both winamp and foobar 0.8.

This is the code from another project I'm working on (this one c++) :
case MODE_AMP:
   PostMessage(g_hwndWinamp, WM_USER, ((SendMessage(g_hwndWinamp,WM_USER, 1, 105)*1000)/100)*wParam, 106);
   break;

This code _works_ with the latest winamp.

The reason I use postmessage instead of sendmessage is because this is used directly in the message processing-function of a gui element, sendmessage will block and that means the gui element might not respond. I also fail to see why my messages are "bad", when they work with winamp.
If you say that track seeking works I'll believe you, but it's _NOT_ working for me.

EDIT:
Ok, I'm very sorry, I missed the updated version, as soon as I updated the component everything worked;P
It might be a good idea to edit the wiki to point to the homepage and edit the first post of this thread so that new arrivals will get the latest version. *feels stupid*
Title: foo_winamp_spam 0.9 beta
Post by: Morfeus on 2007-02-07 17:38:11
thegeek: Doesn't matter. And, I'm sorry that I shouted at you (I was sure that you are using an old version).

Back to the point: Chronial we NEED you to implement those features OR release source code
Title: foo_winamp_spam 0.9 beta
Post by: MrMincho on 2007-02-09 06:24:33
Works great with foobar .9.4.2, collunms ui and music info for gaim!  http://www.ews.uiuc.edu/~rbalik2/musicinfo/index.html (http://www.ews.uiuc.edu/~rbalik2/musicinfo/index.html)
Thanks for this
Title: foo_winamp_spam 0.9 beta
Post by: Chronial on 2007-02-10 00:09:57
Well, there it is: foo_winamp_spam v 0.95 (http://chron.visiondesigns.de/foobar2000/foo_winamp_spam_v0.95.zip)

Changelog available at my foobar page (http://chron.visiondesigns.de/foobar2000/#foo_winamp_spam)

Enjoy

(If anyone knows the volume formula used by winamp, i'd be happy to implement it)

Sourcecode requests will be answered if sent by mail - see my foobar page (http://chron.visiondesigns.de/foobar2000/)
Title: foo_winamp_spam 0.9 beta
Post by: Mangix on 2007-02-10 02:38:37
while using one program, i encountered an error called "foo_winamp_spam: Unsupported WM_USER, lParam 640.". can anyone tell me what lParam 640 is? the SDK doesn't mention it...
Title: foo_winamp_spam 0.9 beta
Post by: Morfeus on 2007-02-10 12:06:13
Chronial: THANKS! You rocks!
My question is: can you implement lParam = IPC_GETOUTPUTTIME wParam = 1 to return length in miliseconds? I'm just asking, because I know Winamp hasn't implemented this, it's your choice. Thanks

btw. Winamp isn't using dB for volume, it just use percents (from main window) to calculate volume from 0 to 255. As fb2k is using dB, I think your formula is good as it is.
Title: foo_winamp_spam 0.9 beta
Post by: Chronial on 2007-02-10 12:56:10
My question is: can you implement lParam = IPC_GETOUTPUTTIME wParam = 1 to return length in miliseconds? I'm just asking, because I know Winamp hasn't implemented this, it's your choice. Thanks

No, of course not. This would break the component. An application using this param awaits the length in seconds, returning milliseconds would break such an application.

Quote
btw. Winamp isn't using dB for volume, it just use percents (from main window) to calculate volume from 0 to 255. As fb2k is using dB, I think your formula is good as it is.

This doesn't matter - if you are calling it db or percent, you can always convert from the one unit to the other (if you know the correct formula). But as far as I remember, you can set different formulas in winamp's settings (linear, logarithmic and something else I believe).
Title: foo_winamp_spam 0.9 beta
Post by: DrO on 2007-02-10 13:52:30
i encountered an error called "foo_winamp_spam: Unsupported WM_USER, lParam 640.". can anyone tell me what lParam 640 is? the SDK doesn't mention it...

it's IPC_GETRATING and has been in the sdk for a few years (was done 5.04 so you're using an old one i bet)

Quote
But as far as I remember, you can set different formulas in winamp's settings (linear, logarithmic and something else I believe).

that'd be down to the relevant output plugin and what's reported by the IPC_SETVOLUME api is just whatever the value is set in the main window. i wouldn't worry about things and looks like how you've done it will be fine from the foobar to winamp mapping. winamp plugin's querying that api never have an idea.

also not sure but you might want to look at implementing the -666 wparam option for IPC_SETVOLUME to return the current volume (just to get the implementation of the api completed)

-daz
Title: foo_winamp_spam 0.9 beta
Post by: Morfeus on 2007-02-10 16:25:43
Chronial: and what about considering new mode=2 for length of song in miliseconds?
Title: foo_winamp_spam 0.9 beta
Post by: DrO on 2007-02-10 18:04:55
for what's intended for this component to be a winamp api emulation layer, adding in parts which have nothing to do with the winamp api implementations doesn't seem right and really if extras are required, native implementations of the plugins being used would be the better option to go for. well that's how i see it especially if this one is just to replicate the winamp api

-daz
Title: foo_winamp_spam 0.9 beta
Post by: Chronial on 2007-02-10 18:29:42
That's just how I see it.

Thanks for the notes on the new SDK version (the volume thing is also not mentioned in the old version).
Maybe you should tell the guys from nullsoft to update their Website (http://www.winamp.com/nsdn/winamp/sdk/)
Title: foo_winamp_spam 0.9 beta
Post by: DrO on 2007-02-10 19:33:48
no one bothers with nsdn anymore, is all in the dev forum for all of the latest sdk bits (nsdn is basically dead from all view points on it)

-daz
Title: foo_winamp_spam 0.9 beta
Post by: Yotsuya on 2007-02-26 19:13:57
Would anyone be so kind as to modify the wiki for this component (http://wiki.hydrogenaudio.org/index.php?title=Foobar2000:Components_0.9/Winamp_API_Emulator_%28foo_winamp_spam%29) to include either a download link for the latest version or a link to Chronial's Foobar Components (http://chron.visiondesigns.de/foobar2000/#foo_winamp_spam) page? The first post in this thread is outdated and it's a bit troublesome to scroll back through the thread history and find the link.

Edit: I attempted to do this myself however the wiki is locked.
Title: foo_winamp_spam 0.9 beta
Post by: bastya_elvtars on 2007-03-07 12:42:32
Hello,
I just got the time to update the plugin from the latest r1ch version, and found that with 0.95 my volume gets set to -100dB and it gets reset all the time I am trying to increase it. With 0.94 it' all fine. I have winamp 5.33 an foobar2000 0.9.4.2. I am happy to help with tracking this down.
Title: foo_winamp_spam 0.9 beta
Post by: Chronial on 2007-03-07 12:55:58
There's only one thing that could cause such a behaviour: something tells foobar to set the volume to -100db. Just try to close everything else that's running and kill every non-windows proccess.
Title: foo_winamp_spam 0.9 beta
Post by: bastya_elvtars on 2007-03-07 13:48:15
OK, it must have been foxytunes for firefox, I haven't used that anyway, just occupied loads of place on my sidebar. ;-) Sorry for the noise.
Oh, and looks like the title of the 'fake window' does not get reset when I stop the player, or is it just me?
Title: foo_winamp_spam 0.9 beta
Post by: Chronial on 2007-03-26 16:46:09
There we go - foo_winamp_spam 0.96 (http://chron.visiondesigns.de/foobar2000/#foo_winamp_spam) is out.

changes:
*  Implemented IPC_SETVOLUME (lParam 122), wParam=-666 to return current volume level
* Implemented IPC_GETRATING (lParam 640)
* Implemented IPC_SETRATING (lParam 639) - setting the rating to 0 removes the tag
Title: foo_winamp_spam 0.9 beta
Post by: Ran Sagy on 2007-03-26 20:28:37
The title of the fake window is always 'Winamp 1.x', If I'm not mistaken.
Title: foo_winamp_spam 0.9 beta
Post by: Chronial on 2007-03-26 20:33:15
Didn't change anything there in this version
can someone confirm that?
Title: foo_winamp_spam 0.9 beta
Post by: Ran Sagy on 2007-03-26 20:57:03
Actually, I wrote that as an answer to bastya_elvtars.
I thought its supposed to always be that? afaik, That's what Winamp does.
Title: foo_winamp_spam 0.9 beta
Post by: Chronial on 2007-03-26 20:59:31
Oh, thought that was a bug report ^^. But this is indeed the desired behavior.
Title: foo_winamp_spam 0.9 beta
Post by: bastya_elvtars on 2007-03-26 21:13:20
I thought its supposed to always be that? afaik, That's what Winamp does.


I meant it should remove the _track_ _title_ in the titlebar of the fake window when I press Stop, shouldn't it?
Sorry.
Title: foo_winamp_spam 0.9 beta
Post by: Ran Sagy on 2007-03-26 21:38:43
Perhaps it should, It's been a really long time since i have used Winamp. But i guess thats for Chronial to find out ;p
Title: foo_winamp_spam 0.9 beta
Post by: Mangix on 2007-03-27 03:37:05
i have a tiny question about the plugin.

right now, i am using a program called CD Art Display which relies on this plugin to do the playback and title grabbing. one of the problems that i have with this plugin that i didn't have with R1CH's version was that when i clicked pause on CD Art Display, it paused. if i click it again, it doesn't resume the playback. R1CH's version didn't cause that.

so were there any changes that dealt with the pause button?
Title: foo_winamp_spam 0.9 beta
Post by: Chronial on 2007-03-27 08:33:41
Yes, there were. I made the pause button behave like in winamp. the Winamp pause button does not resume playback if it is paused.
Title: foo_winamp_spam 0.9 beta
Post by: gren on 2007-03-27 16:29:17
I use foo_winamp_spam so that Gtalk can display what I'm playing in foobar.  I was using 0.9beta3 until I looked at the console saw that it was spamming that error and upgraded to 0.96.  When I did that my Foobar started lagging and using 20-50% CPU.  I removed it and it was back to normal.  I downgraded to 0.95 to see if it did the same on that... and, it did, but I looked at the options and when I turn off "enable Winamp playlist writing" it stops eating my CPU (and it still shows what I'm playing on Gtalk).  Is there a reason for this that you know of?

Edit: Is there something that reacts poorly to really large playlists?  Because I have 68,000 songs in browser... and that could be the issue?  and, if so, is there a way to avoid that since it didn't do it earlier?
Title: foo_winamp_spam 0.9 beta
Post by: Chronial on 2007-03-27 18:22:30
that's very easy: Gtalk requests "winamp" (->foobar) to save the playlist once a second. I consider this quite evil, but that's the way gtalk does it. This will of course cause some cpu load with 70k songs in the list.
Title: foo_winamp_spam 0.9 beta
Post by: Ran Sagy on 2007-03-27 21:51:27
Thats a really bad thing to do. Someone could over to google's forum\newsgroup\whatever-they-have and poke them about it.
Title: foo_winamp_spam 0.9 beta
Post by: gren on 2007-03-27 22:36:36
Wow, that is horrible.  Now I know why about the time gtalk upgraded to showing music my winamp (I was still using it some then) began to lag like hell.  Granted, most people don't have playlists as large as mine but, still, that's incredibly stupid implementation.
Title: foo_winamp_spam 0.9 beta
Post by: cartman(2vd) on 2007-03-27 22:43:31
Wow, that is horrible.  Now I know why about the time gtalk upgraded to showing music my winamp (I was still using it some then) began to lag like hell.  Granted, most people don't have playlists as large as mine but, still, that's incredibly stupid implementation.


well as far as i know about winamp api there is no way to get $path in winamp co maybe they use playlistindex and saved playlist (winamp saves it in predefined possition with predefined name) to get to the physical file that is playing right now... stupid yes but quite effective with short playlist that most of people use in winamp i also had to use this procedure in one of my app because i didnt find more accurate way to get the file id3s.

edit: typo
Title: foo_winamp_spam 0.9 beta
Post by: Mangix on 2007-03-28 04:24:26
Yes, there were. I made the pause button behave like in winamp. the Winamp pause button does not resume playback if it is paused.

could you add an option in the preferences section so that i can toggle the old behavior on and off? It would make my life a bit more convenient since i downloaded a widget which does the same thing as CD Art Display and it really becomes annoying(not being able to play the song when it's paused).
Title: foo_winamp_spam 0.9 beta
Post by: gren on 2007-04-07 20:11:08
This is a little off topic (although not entirely).  Foreign characters (Japanese in this case) don't properly work with Winamp or foo_winamp_spam while displaying in GTalk.  I figure this is a problem with the winamp API?  Here are the questions:

1) Is there a way to bypass that? or would it be completely removed from the scope of this problem?
2) This plugin is used by most for a lot more than just Gtalk music display, I think, so, my question is what is the best option to allow for unicode characters from foobar to display properly in GTalk?

EDIT: I just installed Winamp 5.34 beta and once I did a reinstall removing all old plugins it corrects the problem and displays foreign character sets in GTalk.  This may be at at least a good sign that it's possible to do under foobar.

EDIT2: And I might as well ask... why does 0.9 beta3 change my song in GTalk automatically and not lag?  If in the newest version I don't write the playlist every second it won't change tracks unless I click to make it do it manually in GTalk and it lags severely if I have playlist writing on.  In the old version neither of those problems exist?  Is there a reason for this?
Title: foo_winamp_spam 0.9 beta
Post by: Lukaszek on 2007-04-29 18:31:07
Hi. Great plugin. I don't have any problems to use this. But I have one proposition to this plugin.

I need one option - If I listening music more than 20 seconds then plugin refresh "winamp title bar" information, not early. Why I need this? Sometime I listening track short, and I skip to next track. I don't need to show many changes tracks to my friends on GTalk.

I think You understanding this. This is possible to create and add this option on preferences menu? Thanks for help.
Title: foo_winamp_spam 0.9 beta
Post by: Tein on 2007-05-06 03:50:43
Is there any way to customize the output of this plugin? For example, whenever I list what I'm listening to, it lists the track information, then says "Winamp 2.93". Is there any way I can remove the "Winamp 2.93"?

Thanks.
Title: foo_winamp_spam 0.9 beta
Post by: cartman(2vd) on 2007-05-06 21:32:02
Is there any way to customize the output of this plugin? For example, whenever I list what I'm listening to, it lists the track information, then says "Winamp 2.93". Is there any way I can remove the "Winamp 2.93"?

Thanks.


AFAIK this commponent really dont have any output... it just response to API calls. apparently tool you use for this "I list what I'm listening to" just somehow include winamp version in output so you should look in its settings... for second chance you can look in prefferences / winamp API emulator there is TAGZ for title bar of "fake" winamp window and look if that string isnt contained there... maybe it will also be helpfull to tell us what tool you use for "I list what I'm listening to"
Title: foo_winamp_spam 0.9 beta
Post by: Tein on 2007-05-07 18:02:19
[quote author=cartman(2vd) link=msg=490582 date=1178483522]AFAIK this commponent really dont have any output... it just response to API calls. apparently tool you use for this "I list what I'm listening to" just somehow include winamp version in output so you should look in its settings... for second chance you can look in prefferences / winamp API emulator there is TAGZ for title bar of "fake" winamp window and look if that string isnt contained there... maybe it will also be helpfull to tell us what tool you use for "I list what I'm listening to" ;)[/quote]
Well, I just use foobar2000 v0.9.4.3. The newest version. I was just wondering if I could change the message it displays when I show what I'm listening to.
Title: foo_winamp_spam 0.9 beta
Post by: servimo on 2007-05-14 14:07:20
Which is the latest foo_winamp_spam?

This: (0.9beta3) http://r-1.ch/foo_winamp_spam-0.9beta3.7z (http://r-1.ch/foo_winamp_spam-0.9beta3.7z)
Or this: (0.96) http://chron.visiondesigns.de/foobar2000/f..._spam_v0.96.zip (http://chron.visiondesigns.de/foobar2000/foo_winamp_spam_v0.96.zip)
Title: foo_winamp_spam 0.9 beta
Post by: Keikonium on 2007-05-15 00:26:01
Well I had beta 4 (I think thats what it was) and that was 0.94, so I'd say 0.96 is newer. It seems to work fine, so I'm gonna say the second link.

If you want to be sure, just put one in, and check out the version in foobar. Then put the other one in (after removing the previous version) and check it out. Whichever one has the highest version number is probably the newest one.
Title: foo_winamp_spam 0.9 beta
Post by: Chronial on 2007-05-15 16:46:07
The first link is Version 0.9 - beta 3, the second link is Version 0.96 - that's a lot newer.
But as long as all your winamp-software works without, it doesn't actually matter which version you are using.
Title: foo_winamp_spam 0.9 beta
Post by: ThePhoEniX on 2007-05-21 19:31:19
updated evillyrics still spam your plugin, Chronial
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1241664.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243168.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1240928.
Title: foo_winamp_spam 0.9 beta
Post by: cartman(2vd) on 2007-05-21 23:01:27
updated evillyrics still spam your plugin, Chronial
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1241664.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1243168.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 1240928.


none of these lparams realy exists it looks like evillyrics try to post lparam124 but somehow messed up the string (didnot close it with chr(0) dont know)... any way chronial was afaik inplementing some sort of spam filter which should disable these callings with stupid and incorrect lparmas... are you sure you are using the newest version od winamp_spam?
Title: foo_winamp_spam 0.9 beta
Post by: Anandamid on 2007-06-09 02:04:15
Evillyrics spam problem's gone here with the new v096, thank you very much!
Title: foo_winamp_spam 0.9 beta
Post by: per on 2007-06-14 04:17:01
Any chances that this component could get back to being compatible with CD Art Display (http://www.closetosoftware.com/?s=cdartdisplay)? 

I really liked how I configured CDAD to be pinned on my desktop and all the transparency features of it gave it a clean look that could suit frequent wallpaper changes. Now that I've discovered Foobar2000, I don't want to go back to Winamp!


If that doesn't happen, well still, thanks Chronial for keeping the updates coming on this great component. 
Title: foo_winamp_spam 0.9 beta
Post by: cartman(2vd) on 2007-06-14 18:00:16
Any chances that this component could get back to being compatible with CD Art Display (http://www.closetosoftware.com/?s=cdartdisplay)? 

I really liked how I configured CDAD to be pinned on my desktop and all the transparency features of it gave it a clean look that could suit frequent wallpaper changes. Now that I've discovered Foobar2000, I don't want to go back to Winamp!


If that doesn't happen, well still, thanks Chronial for keeping the updates coming on this great component. 


if you report lparam which coused any problem or is unsupported chronial will possibly looks into this but dont ask him to install this software and test what doesnt work
Title: foo_winamp_spam 0.9 beta
Post by: per on 2007-06-15 17:43:08
[quote author=cartman(2vd) link=msg=498626 date=1181840416]

Any chances that this component could get back to being compatible with CD Art Display (http://www.closetosoftware.com/?s=cdartdisplay)? 

I really liked how I configured CDAD to be pinned on my desktop and all the transparency features of it gave it a clean look that could suit frequent wallpaper changes. Now that I've discovered Foobar2000, I don't want to go back to Winamp!


If that doesn't happen, well still, thanks Chronial for keeping the updates coming on this great component. 


if you report lparam which coused any problem or is unsupported chronial will possibly looks into this but dont ask him to install this software and test what doesnt work
[/quote]

I dont know what you refer to by "lparam" or how to find such information .
With CD Art Display, I can switch tracks (Previous, Next) in foobar2000 but the Start/Pause functions don't work. It also doesn't read the ID3v2 tags of the song being played so it doesn't display any of the information of the track. That application also refers to this Winamp Emulator and actually tries to copy a foo_winamp_spam.dll (by looking at the date, i would say it's 0.96) into the components folder of foobar2000.
Title: foo_winamp_spam 0.9 beta
Post by: Ran Sagy on 2007-06-15 18:42:49
Upon attempting to use the plugin, If any invalid or unimplemented Winamp API features are called, You should have messages in foobar's console window that relate to those, Usually with the format of 'Unrecognized lparam 1243234' or something like that. If you paste those, It can help. Especially if you can map each to an action you tried performing in CD Art Display.
Title: foo_winamp_spam 0.9 beta
Post by: Mangix on 2007-06-16 06:41:26
With CD Art Display, I can switch tracks (Previous, Next) in foobar2000 but the Start/Pause functions don't work.

It also doesn't read the ID3v2 tags of the song being played so it doesn't display any of the information of the track.

Chronial broke it. see my post on the previous page.

it reads mp3 files that have ID3v2 tags but it doesn't work with all formats. keep in mind that CAD reads the info from the file. the plugin tells nothing about the file being played(well except in the title bar...)
Title: foo_winamp_spam 0.9 beta
Post by: Chronial on 2007-06-17 11:31:32

Yes, there were. I made the pause button behave like in winamp. the Winamp pause button does not resume playback if it is paused.

could you add an option in the preferences section so that i can toggle the old behavior on and off? It would make my life a bit more convenient since i downloaded a widget which does the same thing as CD Art Display and it really becomes annoying(not being able to play the song when it's paused).


I'm sorry, but I don't have much time at hand to look after my foobar components at the moment.
But of course you can play a song when it's paused - that's just what the play button does.
Title: foo_winamp_spam 0.9 beta
Post by: Mangix on 2007-06-22 23:34:13
when the pause button is clicked in Winamp while a song is playing, it pauses. when the pause button is clicked again while the track is paused, the song resumes. some applications don't offer a play button and only offer a pause which is the reason why it's a hassle to have to raise foobar2000 from the tray and click play.
Title: foo_winamp_spam 0.9 beta
Post by: odyssey on 2007-06-23 09:58:56
Great plugin!  Now I have my diNovo Mediapad displaying song information, just like Winamp.
Title: foo_winamp_spam 0.9 beta
Post by: cartman(2vd) on 2007-06-23 14:05:21
when the pause button is clicked in Winamp while a song is playing, it pauses. when the pause button is clicked again while the track is paused, the song resumes. some applications don't offer a play button and only offer a pause which is the reason why it's a hassle to have to raise foobar2000 from the tray and click play.


this was discused before pls read the thread or search it i dont remember what conclusion comes from it
Title: foo_winamp_spam 0.9 beta
Post by: Morfeus on 2007-06-26 15:32:01
Bad implementation of IPC_ISPLAYING. Returns 1 for playing and paused (for paused is 3, not according to documentation (in which it is 3) but according Winamp latest version).
Title: foo_winamp_spam 0.9 beta
Post by: radorn on 2007-07-27 01:49:12
Hi

Sorry if the question is stupid, but it is not quite clear to me.

I actually have been tinkering with this a long time because I didn't want to ask anything obvious, but (long story short) for some reason I came to believe this component allowed the use of winamp plugins (at least input ones, wich is what I'm interested in) on foobar. I think that there was something like that some years ago when I first aproached foobar (0.7.x I believe) but, being a perfectionist, I was overwhelmed by all the options I didn't yet understand so I gave up and continued using winamp until some months ago.
Now I'm back and using foobar, I would like to use some winamp plugins (mainly chiptune input plugins for formats not available or not so well supported on foobar, like USF) on it, and researching the matter I came by foo_winamp_spam but I can't seem to get it to do the trick no matter how hard I try, and start to believe that maybe it is not even meant to do that...

Could someone help me with this?
Does foo_winamp_spam really do what I want it to or am I completelly wrong?
If it does, how do I make it work?
or if it does not, is there something else that does?
Title: foo_winamp_spam 0.9 beta
Post by: cartman(2vd) on 2007-07-27 11:31:34
Could someone help me with this?
Does foo_winamp_spam really do what I want it to or am I completelly wrong?
If it does, how do I make it work?
or if it does not, is there something else that does?


No it doesnt its simply translator. when some program want to use some winamp function or information it sends so called api call which is recieved by winamp and winamp act accordingly. This component just translate winamp api calls to foobars so many many programs using winamp api can be used with foobar now.
as for the seccond question. ive never heard of such component. only two i was hearing about is one that allow use of winamp visualisation plugins somehow (i know that milkdrop was runin on fb2k somehow with it) and seccond which somehow enables using of winamp dps plugins. sory dont use any of it so dont know the exact name of it
Title: foo_winamp_spam 0.9 beta
Post by: radorn on 2007-07-27 21:47:46
[quote author=cartman(2vd) link=msg=507055 date=1185532294]... only two i was hearing about is one that allow use of winamp visualisation plugins somehow (i know that milkdrop was runin on fb2k somehow with it) and seccond which somehow enables using of winamp dps plugins. sory dont use any of it so dont know the exact name of it [/quote]

Yeah, yeah, I saw those too (and neither I remember their names), but I'm interested in input plugins only. I don't even use visualizations or dsp's on winamp so those components are of no use to me.
Thanks for the explanation, though. I already understood spam could do that (mainly from the mention of those "now playing" programs for mirc and so), but since it said "API emulation" I thought it may give support for plugins too, wich is not even actively denied. I just got confussed over the possibility of finally getting rid of winamp, cause I now feel forced to use it for those plugins. I also tried xmplayer as it supports winamp inputs but I don't really like it at all.

I guess I'm stuck with it for now.

Thanks and sorry for filling the thread with unrelated stuff. ;)
Title: foo_winamp_spam 0.9 beta
Post by: Trif0n on 2007-08-22 21:05:42
http://chron.visiondesigns.de/foobar2000/f..._spam_v0.96.zip (http://chron.visiondesigns.de/foobar2000/foo_winamp_spam_v0.96.zip)



i had v0.95 and i had probs with CAD , it seems that the french characters (and probably others) in id3 aren't supported in this version
v0.96 fixed that ^^

Thank you !
Title: foo_winamp_spam 0.9 beta
Post by: boundless on 2007-09-17 09:41:58
Thanks for this. It worked good with the latest Google Talk and foobar.
Title: foo_winamp_spam 0.9 beta
Post by: geekmaster1 on 2007-12-08 00:54:42
Which is the latest foo_winamp_spam?

This: (0.9beta3) http://r-1.ch/foo_winamp_spam-0.9beta3.7z (http://r-1.ch/foo_winamp_spam-0.9beta3.7z)
Or this: (0.96) http://chron.visiondesigns.de/foobar2000/f..._spam_v0.96.zip (http://chron.visiondesigns.de/foobar2000/foo_winamp_spam_v0.96.zip)

this thing crashes gtalk
Title: foo_winamp_spam 0.9 beta
Post by: Vernier on 2008-08-07 15:31:01
Quote
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 214.
WARNING : foo_winamp_spam: Unsupported WM_USER, lParam 3026.


These are IPC_GET_EXTENDED_FILE_INFOW. IPC_GETPLAYLISTFILEW

Would be nice to support the wide-character versions of these messages, this is needed to work properly when the filename or tags contain east-asian characters
Title: foo_winamp_spam 0.9 beta
Post by: Zulithe on 2008-08-31 10:32:24
Hi all. Is there a way for foo_winamp_spam + r1dll to find the album name and report it in your winamp script? I can't seem to find a way!
Title: foo_winamp_spam 0.9 beta
Post by: dannymichel on 2008-08-31 13:11:28
thanks for the new version.
runs smooth
Title: foo_winamp_spam 0.9 beta
Post by: satorippoi on 2008-11-08 16:09:35
I can't make my Gtalk display the song name...

I have tried various workarounds including creating a blank winamp.m3u file, modifying registry...
but it seems that nothing works...

I use the latest fb2k and gtalk...can anyone help me?..

edit: ok, problem solved...it is just that i used the russian version of gtalk where the option "show current track" is missing...((
Title: foo_winamp_spam 0.9 beta
Post by: leavingharvard on 2008-11-08 20:36:45
I can't make my Gtalk display the song name...

I have tried various workarounds including creating a blank winamp.m3u file, modifying registry...
but it seems that nothing works...

I use the latest fb2k and gtalk...can anyone help me?..

edit: ok, problem solved...it is just that i used the russian version of gtalk where the option "show current track" is missing...((


When using the API to trick Pidgin into thinking that you're using Winamp, the track name will display correctly but the album and artist fields are blank.

If I knew square one about coding I would fix it myself. Thanks very much and I appreciate the effort if you can fix it.
Title: foo_winamp_spam 0.9 beta
Post by: acmodeu on 2008-11-24 23:40:30
Thanks for the plugin. I'm so glad that it works with FB2k@0.9.6b5 under Vista x64!
Title: foo_winamp_spam 0.9 beta
Post by: Kvanto on 2009-04-06 03:51:03
It is possible to make a plugin, that makes gracenote database thinking that it works with winamp but not foobar and allows using it for tagging?
I don't know how it works in winamp but it looks similar for me as API emulation...
Title: foo_winamp_spam 0.9 beta
Post by: Rumbah on 2009-05-17 16:47:06
Is there any alternative now that Foobar 0.9.6.6 seems to blacklist this plugin? I just installed 0.9.6.6 it and it is not loaded anymore.
Title: foo_winamp_spam 0.9 beta
Post by: Yirkha on 2009-05-17 19:18:56
See the post I wrote to the other foo_winamp_spam's thread (http://www.hydrogenaudio.org/forums/index.php?s=&showtopic=61516&view=findpost&p=632127) two weeks ago.
Title: foo_winamp_spam 0.9 beta
Post by: manudevil on 2009-09-08 08:31:52
Hello,

Using Foobar2000 0.9.6.9, I can't make foo_winamp_spam work. I've tried 0.96, 0.90fix... With 0.90, I got an error message, I must upgrade foo_winamp_spam, and with 0.96, nothing works. I don't see the component in the foobar option window.
I want to use Foobar with rainmeter. So what can I do ?

Thanks.
Title: foo_winamp_spam 0.9 beta
Post by: kode54 on 2009-09-08 09:13:41
Hello,

Hello, read the post above yours.
Title: foo_winamp_spam 0.9 beta
Post by: manudevil on 2009-09-08 18:29:53
Of course, I have read. Maybe not the best way. But I must precise I have tried foo_winamp_ipc too. It works with rainmeter but... the commands doesn't seem to fit well. For example, pause button doesn't seem to work well. It stop the track, which is beginning to the start... What can be done?
I have posted this question on the Raimneter forum, but no one told me which version of foo_winamp_spam to use, just that I must use it instead of anything else...
Title: foo_winamp_spam 0.9 beta
Post by: kode54 on 2009-09-09 02:38:04
Maybe not the best way.

Have you tried Shpeck? It has a pretty thorough Winamp API emulator built-in, you can ignore the visualization functionality.
Title: foo_winamp_spam 0.9 beta
Post by: manudevil on 2009-09-09 20:36:08
It's alright! I've found a way. Using foo_winamp_ipc and modifying the rainmeter plugin, it works now almost the way I want.
Thank you!
Title: foo_winamp_spam 0.9 beta
Post by: R1CH on 2010-01-19 20:43:48
Rebuilt for 1.0, http://r-1.ch/foo_winamp_spam-1.0.zip (http://r-1.ch/foo_winamp_spam-1.0.zip)
Title: foo_winamp_spam 0.9 beta
Post by: pyrotechnician on 2010-01-20 23:56:30
thanks
however, this version is not working with windows live messenger. not for me..
i'm quite positive that the last version did work with live messenger.
edit: or was that some other component? 
Title: foo_winamp_spam 0.9 beta
Post by: neuromancer on 2010-01-23 01:29:12
I really like this component, this was my only solution for FoxyTunes to display correctly Asian characters, but after I updated FoxyTunes on this week, I got the message: "your Winamp is idle" instead of the song information. And when I switch to foobar no matter which character encoding I choose, I have only question marks instead of the Japanese or Korean text.
(http://img25.imageshack.us/img25/9595/foxytunesproblem.th.jpg) (http://img25.imageshack.us/img25/9595/foxytunesproblem.jpg)

So I updated both foobar and winamp_spam component but it didn't solve the problem.

On my other PC I have older version of FoxyTunes, I didn't dare updating it:
(http://img46.imageshack.us/img46/3900/foxytunesolder.th.jpg) (http://img46.imageshack.us/img46/3900/foxytunesolder.jpg)

Why doesn't work any more?








Title: foo_winamp_spam 0.9 beta
Post by: pyrotechnician on 2010-02-02 00:34:32
i had a problem with spamming google talk when I updated foobar to version 1.0. Had to completely uninstall foobar, then do a fresh install. now it works fine.
Title: foo_winamp_spam 0.9 beta
Post by: Nol888 on 2010-04-26 23:58:54
Is there source available for this plugin? If not, I would like to request UTF-8 support for the fake WinAmp window. Taking for example a Japanese-titled song, the correct title will show up in the foobar2000 window class title, but is displayed as ?'s in the fake WinAmp window class. (Viewed via Spy++)

If I got the source I would be more than happy to submit a patch to add foreign character support. Unfortunately until then it looks like the foobar<-->winamp bridge is still not fully crossed.
Title: foo_winamp_spam 0.9 beta
Post by: cartman(2vd) on 2010-04-27 00:31:59
Is there source available for this plugin? If not, I would like to request UTF-8 support for the fake WinAmp window. Taking for example a Japanese-titled song, the correct title will show up in the foobar2000 window class title, but is displayed as ?'s in the fake WinAmp window class. (Viewed via Spy++)

If I got the source I would be more than happy to submit a patch to add foreign character support. Unfortunately until then it looks like the foobar<-->winamp bridge is still not fully crossed.


have you tried vis_spcheck? it kind of assimilates function of this plugin... maybe it does solve your problem and it can play winamp visualisation if you want it to ... but i use it just as winamp ipc gateway to foobar
Title: foo_winamp_spam 0.9 beta
Post by: viriato_iceview51 on 2010-05-31 13:59:25
Also tried version 1.0 and it's not working, but then I found this version (http://chron.visiondesigns.de/foobar2000/#foo_winamp_spam) which works.
Title: foo_winamp_spam 0.9 beta
Post by: Haf on 2011-09-06 22:26:55
Hi again folks

I re-installed Windows 7 Ultimate with 64bit version.
Now I have installed Foobar2000 again, but the foo_spam isn`t working. I need foo_spam to get the player in Rainmeter to work.

Info
System: Windows 7 Ultimate 64bit (Bought and registred legally. All updates installed)
Foobar2000 version: v1.1.8 beta 6
Foo_spam version:  foo winamp spam 0.90fix

Hope someone can help me out
Title: foo_winamp_spam 0.9 beta
Post by: _Matt_ on 2011-09-07 03:57:17
@ Haf
foo_winamp_spam is no longer needed. Since April 2011 the Rainmeter 2.1 betas have included poiru's awesome NowPlaying plugin. You can read more about it here (http://rainmeter.net/RainCMS/?q=NowPlaying_beta), and be sure to look at the Supported Players:foobar2000 section for the link to the foo_rainmeter plugin.
Title: foo_winamp_spam 0.9 beta
Post by: Haf on 2011-09-07 05:32:53
Thanks! I got the skin working. Good that they have a skin for this great musicplayer  Here is what my desktop with the NowPlaying skin looks like:

(http://a2.sphotos.ak.fbcdn.net/hphotos-ak-ash4/s720x720/317399_254813914559395_100000923641319_781902_132946062_n.jpg)
Title: foo_winamp_spam 0.9 beta
Post by: Chronial on 2012-01-11 18:16:16
Released the source code of my last version (v0.96) on github: https://github.com/Chronial/foo_winamp_spam (https://github.com/Chronial/foo_winamp_spam).
SimplePortal 1.0.0 RC1 © 2008-2018