next »

[piovrauz]

Something strange is happening when I play an old module. Repeat always is checked. it play fine the first time, but when it's supposed to repeat, it starts very slow. I suppose there's some speed setting at the end, but shouldn't it be reset when replaying? it's not a looped module, so I suppose the wrong speed is set in the end of it and get carried when replaying the track. any idea? maybe a reset? -"terror 4 ever.it" is on the ftp-

[saga]

Looping modules does not work like looping streamed media like MP3. None of the internal variables are supposed to be reset when looping a module - you can check yourself by playing the file in Impulse Tracker. Whatever tempo the module was at when it reached the last pattern, that tempo is not supposed to change when returning to the first pattern, unless there's an explicit tempo command on the first pattern.

[piovrauz]

I know that saga, but I was thinking differently: I was supposing that looping the module -as a whole-, expecially for non looped module, should be done treating it as it was the first time it played, not just restarting from the first pattern.
In modplug player that module is treated like an mp3 would, so maybe there's something similar to a reset or it's just simply reloaded? maybe it wouldn't hurt putting an option like the midi reset between songs...

After all, a thing is looping a set of pattern, another is repeating a whole song (no loops at the end, obviously).
I suppose this can apply to all -finit lenght- modules that have a tempo change at the end for some reason.

[wrkq]

Erm, saga, while it's a perfectly proper choice when the mod's self-looping with a jump command at end (or with a flag in file header if supported), it then totally breaks cases like this one, i.e. a mod not meant to be looping that you just want to listen in a loop like you'd want to listen to a MP3.
I guess putting it as the only entry in playlist and ticking Loop List instead of Loop Song would be a workaround for now, but IMO a "Reset MOD on non-automatic(forced?) loop" setting (per-file sure would be cooler, but even a global would help) makes some sense.

ED: Ugh, missed the new post warning, sorry.

[saga]

Erm, saga, while it's a perfectly proper choice when the mod's self-looping with a jump command at end (or with a flag in file header if supported), it then totally breaks cases like this one, i.e. a mod not meant to be looping that you just want to listen in a loop like you'd want to listen to a MP3.

That's what ModPlug did for years and it was hated by anyone not using ModPlug to compose their songs. Every other tracker didn't reset the song variables, so the author had to reset them.

[piovrauz]

Mmmm, I wouldn't hate if xmplay were to have an (hidden) option to do the same think. or even not so hidden, in fact it's a lot like a midi reset.
Actually, to achieve my intended result, I'd have to load 2 time the same track on the playlist and repeat the playlist, but in that way I can't really use the playlist...
Is this request feasible?

[Ian @ un4seen]

I think an option can be arranged

I guess it should only apply when the restart position is the 1st order?

[piovrauz]

nice. It should only apply when the restart position is the 1st order, and the song isn't looping itsef using pattern jump commands (so that it doesn't break songs already designed to loop and actually using speed changes, might be pretty uncommon but...).

[Ian @ un4seen]

OK, here's something to try...

   www.un4seen.com/stuff/xmplay.exe

Let me know if it misbehaves with any files.

[piovrauz]

Thanks a lot!
Seems to work perfectly with the specific file I mentioned.
I'll try more looped files when at home and post results.

-edit: sadly, I spotted an issue, xmplay loses the setting upon restart. The module is in a 7zip along with others if it matters.

[saga]

-edit: sadly, I spotted an issue, xmplay loses the setting upon restart. The module is in a 7zip along with others if it matters.

FWIW, it also "forgets" the position of the vis/playlist window since this update... it always defaults to a small windows place in the upper-left corner of the desktop.

[Ian @ un4seen]

sadly, I spotted an issue, xmplay loses the setting upon restart.

I think you must've downloaded the update as soon as I posted it? I also noticed that the setting wasn't saved a few minutes later and put up an updated update

FWIW, it also "forgets" the position of the vis/playlist window since this update... it always defaults to a small windows place in the upper-left corner of the desktop.

Oops! That should be back to normal now...

   www.un4seen.com/stuff/xmplay.exe

[piovrauz]

prrrrfect meow! ehm, works as supposed now. thanks a lot. will test with more modules as soon I get some time.

[saga]

OK, here's something to try...

   www.un4seen.com/stuff/xmplay.exe

Let me know if it misbehaves with any files.

It breaks Seldom Seen.

[Ian @ un4seen]

Yep, it was actually resetting any time the end was reached, regardless of the restart position. But I'm thinking now that it may be better to use the loop detection (rather than the restart position) to determine whether to reset, as there may be songs that are meant to loop (without resetting) from the 1st order? Here's an update with that change...

   www.un4seen.com/stuff/xmplay.exe

Let me know if it causes any problems.

[saga]

I also guess that this is the better option.

[piovrauz]

yup, that's what I meant saying "should only apply when the restart position is the 1st order, and the song isn't looping itsef using pattern jump commands". I'll test later with files that aren't supposed to loop. thaanks for the fix.