next »

[pyc]

It just freezes when you click play. Playlist works. This happens after I reinstalled my motherboard drivers (Nforce 400 chipset, integrated Realtek Audio). That wouldn't be so strange to me, but every other program works: Reason, Buzz, Media Player Classic... Really I don't know how to fix it.... I already reinstalled my sound card driver. Some suggestions?

[raina]

Sounds a little like messing with the drivers would have shuffled your audio device list and XMPlay is now using the WAV Writer instead. You can check whether this is the case in Options and stuff > Output.

[pyc]

I already checked it

[Dotpitch]

And what about a clean XMPlay, no plugins and no settings (copy xmplay.exe to a different folder)? If even that doesn't work, you're probably the first one to have that problem! You could also try using the DirectSound or ASIO output plugin.

[pyc]

will try that, and i can tell you there's no direct-x output (but the direct-x is installed (working in reason)) or asio outputs on configuration screen...

[Dotpitch]

That's because you have to download the plugins seperately (Directsound plugin), then they'll show up. But the standard WaveOut should work nonetheless.

[pyc]

This is too crazy, the same is happening with DS plugin..... And the other multimedia is working... (( I don't want to reinstall my whole system because of this.... and there's really no decent player except XMPlay

[pyc]

My xmplay.ini was fucked up... I isolated xmplay.exe to make new .ini and now it works... if someone's interested, I can post xmplay.ini that was causing the problem.

[Ian @ un4seen]

Yes, please upload the dodgy XMPLAY.INI file here...

   ftp.un4seen.com/incoming/

[pyc]

You just got it...

[Ian @ un4seen]

For some reason, there doesn't seem to be any problem playing stuff with your XMPLAY.INI file here. Just to be sure, if you replace your current XMPLAY.INI with it, do the problems occur again? Also, does the problem happen with all files that you try to play?

[Tsorovan]

I've had some really weird .ini corruption myself. An .ini that works splendidly on one computer will ignore some secret settings (usually NoExt and NoTenths and NoWheelVol (coincidentally, options I myself requested)) sometimes, when moved to another computer. When this happens there's nothing I can do to fix it except for deleting the .ini and redoing all the changes.

I sadly don't have a copy of such an .ini still here, but the next time it happens I'll be sure to post it.