Print

[themoon_follow]

There is an MO3 of the same track already in the archive, however, it is rendered unplayable via the native libopenmpt player. I've recently had the module file of that track (and yes, it's the same name but in IT format) that is currently in the upload area.

This is the MO3 rendition of the module.

I just wanted to know what had caused this to happen in the first place, and any given feedback on how MO3s will be impacted in the future.

[ASIKWUSpulse]

First of all, have you checked with Hajba if it is ok to upload the IT-module?

That's weird. I think that could be a libopenmpt bug, because I've played the tracks without problem before. See with Saga when he answers, he's one of the OpenMPT developers.

[themoon_follow]

Alright... Admittedly, it was originally on his website where the module was found. I might have to contact him at any time if given the opportunity to do so.

Also, yeah, I might look forward on Saga's thoughts about this MO3 issues...

[themoon_follow]

I actually do forgot about the conjunction in the first part: I also dug into some of his modules and they also match what is included in the Archive. He probably might have uploaded most of his and somebody did the rest, I'm not quite sure.

[Axxy]

I would imagine that someone decompressed the .mo3 and uploaded the .it file, probably because their player might not have supported the .mo3 format..

Tbh, I wouldn't store the .mo3 format myself either, so I would probably do the same as well.

[Saga Musix]

libopenmpt doesn't generally have a problem with that particular MO3 file. It's probably just something that's specific to the WebAssembly version used on ModArchive (the Ogg Vorbis samples fail to decompress). I'll look into it.

In general, please don't upload "fixed" version of songs without notifying me beforehand, because otherwise they might get rejected quickly after uploading.

A general note:
We want modules to be in their original format - which is IT in this case. However, some modules (not this one) are only available as MO3, in which case we don't want the file uncompressed with UNMO3 or OpenMPT. Uncompressing a file suggests that it was never compressed, so it may hide the fact that samples are lower quality, etc...

Edit: Confirmed, the current version of the library used for decoding Vorbis samples, stb_vorbis, has issues with decoding certain Vorbis samples, and there's already a bugfix available for it. The online player will be updated soon.

[Saga Musix]

The online player will now play the MO3 file correctly again (might require a force refresh to clean browser cache).

[themoon_follow]

Alright, word.

I'll be looking into the MO3 fix on my end, as expected by the thread shown.

Also, Saga, I'll should get in contact you by any means of communication should there be more of his lying around. And if in case there would be a further requirement, I'd get to it asap.

[themoon_follow]

Got a little update on the MO3 issue. But first, some little info:

I am using Microsoft Edge (Beta Channel, based on Chromium engine) to browse the internet. And since the browser is multi-account, I can easily start from scratch if there are any problems with the current user.

Now how does that relate to the topic?

Upon garnering the release that the native player's MO3 encoding has been fixed, I tried it again with removed cache (and newer browser cookies) and still doesn't work. I have decided to reset my account and start from scratch, and waited for a few days with intermittent playback of other modules.

It works fine now, and I'm happy with the results so far.

Now how about the IT file that was supposed to overwrite the existing MO3?

Intriguing question, but I should come up with a rather simple answer to wrap up this topic. I'll let Saga and the mods handle it.

Licensing issues and other related modules?

From now on, I'll let them know firsthand before making any move to avoid any potential hurdles in the future.

~~~

That's all I have for now. Keep tracking and stay sane, people.