google-code-export / pidgin-musictracker

Automatically exported from code.google.com/p/pidgin-musictracker
GNU General Public License v2.0
1 stars 1 forks source link

foobar support doesn't work #144

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What is the expected output? What do you see instead?
foobar2000 support doesn't work at all

What version of musictracker are you using? What version of pidgin are you
using? On what operating system?
pidgin 2.5.8 
musictracker 0.4.19 
Windows XP

What media player are you using?
foobar2000 0.9.6/7 (latest)
The theme I'm using have changed the name of the window.. I don't know if
it's the cause of the bug

What IM protocol(s) are you using?
MSN or MSN Pecan, both are not working

Please attach or paste output from pidgin's Help/Debug Window (be careful
to remove any protocol usernames you don't want made public)
Log:
(16:42:37) musictracker: trying 'Winamp'
(16:42:37) musictracker: Failed to find winamp window. Assuming player is off
(16:42:37) musictracker: trying 'Windows Media Player'
(16:42:37) musictracker: No WMP core IDispatch (WMP not running?)
(16:42:37) musictracker: trying 'iTunes'
(16:42:37) musictracker: trying 'Messenger compatible interface'
(16:42:37) musictracker: trying 'Foobar2000'
(16:42:37) musictracker: Converted wchar string to 'The Kills | 03. Tape
Song | 2:13 (3:36)'
(16:42:37) musictracker: Got window title: The Kills | 03. Tape Song | 2:13
(3:36)
(16:42:37) musictracker: pcre_compile: regex '(.*) - (?:\[([^#]+)[^\]]+\]
|)(.*) \[foobar2000.*\]'
(16:42:37) musictracker: pcre_exec: returned -1
(16:42:37) musictracker: Foobar2000,,,,2

So the error seems to be that my theme changed the name of the window.. is
there any way to customize it ? 

Original issue reported on code.google.com by baptist...@gmail.com on 1 Jul 2009 at 2:44

Attachments:

GoogleCodeExporter commented 9 years ago
http://code.google.com/p/pidgin-musictracker/wiki/FAQ#8

Original comment by b152fee4...@gmail.com on 1 Jul 2009 at 5:00

GoogleCodeExporter commented 9 years ago

Original comment by b152fee4...@gmail.com on 14 Jul 2009 at 12:10

GoogleCodeExporter commented 9 years ago
Closing on the assumption that the FAQ has resolved the problem.  Please 
re-open this
issue if that is not the case.

Original comment by b152fee4...@gmail.com on 2 Sep 2009 at 7:32