Topic: Having difficulty with sample Loop points

[Amaroq_Dricaldari]

I tried converting some ImpulseTracker modules to MO3s, and while I am pleased with the sound quality and compression ratios I am not so pleased by the lack of loop points. It doesn't remember the loop points I set for each sample in ModPlug tracker, just deleting everything in the sample after the Loop End and going right back to the beginning, ignoring the Loop Start point. Could you do a fix regarding this, such as a modified Vorbis codec (it should be Open-Source IIRC)?

EDIT: Nevermind, it seems to be cooperating now. Mostly... the loop points are off because the sample was encoded at 44100 Hz, and the sample that came out was 44092. Is there a way to fix it to 44100 Hz while keeping the Ogg Codec, or have it automatically re-adjust the sample loop points to fit the new sample rates?

[Ian @ un4seen]

That's strange, as loop points should be retained in a MO3 conversion. Are you having the problem with a particular IT file? If so, please upload it to have a look at here...

   ftp.un4seen.com/incoming/

[Amaroq_Dricaldari]

I attached a RAR archive containing both files. Sorry, I overwrote the one without loop points before I received your reply, but this one was encoded at 44092 instead of 44100, and as such the IT version and MO3 version are now looping slightly off-sync. I could adjust the loop points on the MO3 version manually, but ModPlug would turn it back into an IT.

I am trying to port the Unreal Tournament 3 soundtrack to Unreal Engine 1, and ImpulseTracker modules are way too big (I am using a special OpenAL plugin that lets me use MO3s.)

[Ian @ un4seen]

The encoding rate won't affect the sample's playback rate, so it shouldn't really matter if they are different. The only issue could be if the encoder strongly filters the sample data (to remove less audible frequencies), but if there's only 8 Hz difference between the rates then that shouldn't be much of an issue. The encoding rate also won't affect the loop point positions, but note that lossy encoding will change the waveform slightly, which could result in imperfect looping, eg. a "click" sound. Is that what you're hearing? Ogg Vorbis is usually pretty good at keeping the waveform shape close to the original. To confirm whether the problem you're hearing is due to the lossy encoding, you could try using the MO3 encoder's built-in lossless encoding option and compare the result.

[saga]

the loop points are off because the sample was encoded at 44100 Hz, and the sample that came out was 44092.

That sounds like you worked with an XM file rather than IT. 44092 is the closest you get to 44100 in XM, but in IT the frequency is not restricted, so you should be able to use a sample at 44100 Hz perfectly fine.

[Amaroq_Dricaldari]

Well, the song I used was put directly in an ImpulseTracker module. And the sample rate was 44100 Hz.

When I converted it to an MO3, the song got downsampled to 44092 Hz, which desynced the loop.
Edit: I got it working now.


@un4seen Also, you should check this out for future versions of MO3: http://en.wikipedia.org/wiki/Opus_(audio_codec)