September 28th, 2003, 02:41 AM
foobar2000 w/ girder
I'm having a bit of trouble getting girder to work with foobar2000 (http://www.foobar2000.org) fully. I've narrowed down the problem to this...
when i close foobar2000 and restart it, girder is able to send the commands, but foobar2000 doesn't respond. That is, until I click one of the menu (Foobar2000, Playback, Playlist, or Components) or play a song by 2x clicking on one. All of the keys I assigned in girder works after that. It's weird. The keys will work, only, and only if I click one of the menus or play a song by 2x clicking on it. The keys work until I close foobar2000 again and start it up again. Then, I have to do the menu-clicking part again to make the keys work again.
Can anybody help?[/url]
September 28th, 2003, 03:16 PM
It sounds to me that however you defined FooBar as a target in Girder to send commands to doesn't actually occur until you click on something in FooBar2000 (or whatever, as you mentioned). E.g., if you used the Target button in Girder to "define" FooBar (i.e., tell Girder how to look for FooBar), it seems that something may be different in FooBar when it's initially run and when you've pressed something.
What I would suggest is opening FooBar, and don't press and commands, menus, etc., in FooBar. Then, press the Target buton in Girder for your commands, and see if the window for FooBar as you defined it actually exists at that point. That should be a good starting point. A quick workaround (although kludgy) would be to then have Girder, after executing FooBar, automatically access a menu item just so that the other commands will work.
September 29th, 2003, 05:46 PM
yeah..the first suggestion doesn't work.. i'll try the second one. thanks for the suggestions!