next »

[Ian @ un4seen]

The stop button can also be used to cancel opening a track, eg. if a stream is taking a while to open. That possibility would be lost if the button was changed to just signal the new track to begin in a stopped state.

Regarding the original request of staying paused when opening the next track, here's an update with an XMPLAY.INI setting for that...

   www.un4seen.com/stuff/xmplay.exe

Add a "NoResumeNext=1" line to your XMPLAY.INI file (under "[XMPlay]") to prevent the next/previous options starting playback when it's currently paused/stopped.

[Jimmy Neutron]

Ian, gotta make the "con" into "com"

www.un4seen.com/stuff/xmplay.exe

[saga]

XMPlay doesn't exit sustain loops correctly if the sustain loop is bidi and the normal loop is not. Check the attached example...

[Ian @ un4seen]

Ian, gotta make the "con" into "com"

Oops! I've updated the post.

XMPlay doesn't exit sustain loops correctly if the sustain loop is bidi and the normal loop is not. Check the attached example...

There was indeed a problem with exiting sustain loops in sample-only IT files. Here's an update to fix that...

   www.un4seen.com/stuff/xmplay.exe

[saga]

That fixes it, thanks. Could you please shed any light on how playback is resumed after exiting the sustain loop? When the Note Off is encountered, I set the sample pointer to the beginning of the loop, but that is obviously not what IT and XMPlay are doing - they seem to start somewhere in the loop, but I cannot determine where this offset comes from.

[Ian @ un4seen]

I think the sample position should be left as it is unless it is beyond the loop end, in which case, it's set according to how far beyond the end it is, eg. if it's 10 samples past the end then set it to 10 samples past the start.

[saga]

Ah, that wasn't very obvious. I'll try that, thanks!

[Cosworth]

The problem is, when I play in some games, XMPlay stops playing. This is an old problem, but here is new PC and I forget how to solve it

[Dotpitch]

On the Playlist page of Options and stuff, are 'Stop at dead track' and 'Stop at end of queue' unticked? Is 'Loop' ticked?

[Cosworth]

On the Playlist page of Options and stuff, are 'Stop at dead track' and 'Stop at end of queue' unticked? Is 'Loop' ticked?

Nope, everything is ok.

I apologise, actually xmplay stops playing about 2-3 seconds, than play is continues. This happens very often. Other players don't have this trouble

[Dotpitch]

What output device are you using? WASAPI?

[Dotpitch]

Changelog for XMPlay 3.6:
XMPlay 3.6 - Stuff version changelog on the Support Site.

[Cosworth]

What output device are you using? WASAPI?

No, RealteK AC97

[Dotpitch]

Does your new PC have Windows 7 (or Vista)? Then get the WASAPI output plugin and use the WASAPI driver. Still with XP? Try the DirectSound output plugin (same page).

[Cosworth]

Still with XP? Try the DirectSound output plugin (same page).

Thank you, tha problem is solved   But, now sound is like stuck 1-3 sec   Maybe something need to do with Buffer?

[moriez]

Regarding the original request of staying paused when opening the next track, here's an update with an XMPLAY.INI setting for that...

   www.un4seen.com/stuff/xmplay.exe

Add a "NoResumeNext=1" line to your XMPLAY.INI file (under "[XMPlay]") to prevent the next/previous options starting playback when it's currently paused/stopped.

You're still the man 

Thanks a wild bunch!

[Ian @ un4seen]

I apologise, actually xmplay stops playing about 2-3 seconds, than play is continues. This happens very often. Other players don't have this trouble

That sounds like XMPlay possibly isn't getting any CPU, so it can't generate any output, resulting in a gap in the output (or repeated sound with DirectSound output). I'm not sure why that would only happen with XMPlay and not other players. One possibility is that other players generally default to using a larger output buffer than XMPlay does, so you could try increasing the buffer length in the "Output" options and see if that helps. You could also try adding a "Boost=1" line in your XMPLAY.INI file (under "[XMPlay]") to give XMPlay higher priority.

Does the problem happen with everything that you try to play, including local files (in archives and not) and internet streams?

[Cosworth]

I apologise, actually xmplay stops playing about 2-3 seconds, than play is continues. This happens very often. Other players don't have this trouble

That sounds like XMPlay possibly isn't getting any CPU, so it can't generate any output, resulting in a gap in the output (or repeated sound with DirectSound output). I'm not sure why that would only happen with XMPlay and not other players. One possibility is that other players generally default to using a larger output buffer than XMPlay does, so you could try increasing the buffer length in the "Output" options and see if that helps. You could also try adding a "Boost=1" line in your XMPLAY.INI file (under "[XMPlay]") to give XMPlay higher priority.

Does the problem happen with everything that you try to play, including local files (in archives and not) and internet streams?

I noticed, problem was only when I played. But with Boost=1, problem is gone I think fully

[saga]

Here's a new riddle for you The 900 effect is somehow executed wrong in XMPlay, it starts from an apparently arbitrary offset in FT2 (as it can be heard on the second channel of the XM), which does not depend on the 979 earlier in the pattern (which is not executed anyway). Maybe you know where the offset comes from...? I have no idea...

[SmartOne]

XMPlay couldn't open a TTA file when the directory name was "イース Ⅰ&Ⅱクロニクルズ オリジナルサウンドトラックmini."  It played fine with a CUE sheet after I renamed the folder to "blah."