Author Topic: Will ModPlugin ever be resurrected?  (Read 1668 times)

Offline Kitsune_Phoenix

  • Active artist
  • *
  • Posts: 43
  • Gender: Female
  • Free Hugs? I don't bite... much.
    • My Profile.
  • Operating System: Windows 7 Enterprise SP1 32-Bit
Will ModPlugin ever be resurrected?
« on: March 14, 2015, 01:33:21 »
Will development of ModPlugin ever be restarted, not only to be compatible with modern browsers (such as Firefox, Chrome and IE11), but also to take advantage of all of the format support and playback fixes of OpenMPT?

I personally think that bringing back ModPlugin in a more modern format would be an amazing idea. Obviously, the actual OpenMPT will take priority over this, but it definitely seems like it is worth looking into.

- - - - -

For the record, I have read this thread: http://forum.openmpt.org/index.php?topic=1911.0
« Last Edit: March 14, 2015, 01:40:20 by Kitsune_Phoenix »

Offline Rakib

  • Crazy artist
  • ****
  • Posts: 880
  • Operating System: win7x64
Re: Will ModPlugin ever be resurrected?
« Reply #1 on: March 14, 2015, 07:49:18 »
Modplugin is not open source. There are other javascript-based alternatives you can use.
http://deskjet.github.io/chiptune.js/
^^

Offline Kitsune_Phoenix

  • Active artist
  • *
  • Posts: 43
  • Gender: Female
  • Free Hugs? I don't bite... much.
    • My Profile.
  • Operating System: Windows 7 Enterprise SP1 32-Bit
Re: Will ModPlugin ever be resurrected?
« Reply #2 on: March 14, 2015, 08:17:06 »
The problem though is that those have to be coded per-website, and Java has many of problems of which I presently do not have the stamina to go into detail.

Besides, OpenMPT was built on the original ModPlug Tracker, which itself was built on ModPlug Player, which itself was built on ModPlugin. With some reverse engineering and the new code, ModPlugin could be back up and running.

Offline manx

  • OpenMPT Developers
  • *****
  • Posts: 105
Re: Will ModPlugin ever be resurrected?
« Reply #3 on: March 14, 2015, 09:49:42 »
Will development of ModPlugin ever be restarted, not only to be compatible with modern browsers (such as Firefox, Chrome and IE11), but also to take advantage of all of the format support and playback fixes of OpenMPT?
I personally think that bringing back ModPlugin in a more modern format would be an amazing idea. Obviously, the actual OpenMPT will take priority over this, but it definitely seems like it is worth looking into.

We have no intent to resurrect ModPlugin at all.
All browser vendors are currently phasing out native plugin support in their browsers in favour of more modern and secure technologies like asm.js or NativeClient. Mobile browser tend to not even support native plugins at all.

libopenmpt can already be compiled to asm.js via emscripten since quite some time now, and works just fine.
There is the already mentioned chiptune.js https://github.com/deskjet/chiptune.js (based on libxmp and not OpenMPT/libopenmpt) and its successor, chiptune2.js (which uses an emscripten compiled libopenmpt) https://github.com/deskjet/chiptune2.js (demo here: https://deskjet.github.io/chiptune2.js/) which are both JavaScript based solutions based on current module playback libraries.

There are some other, native JavaScript, MOD-only, players around that I do not have links to ready at hand.

The problem though is that those have to be coded per-website, and Java has many of problems of which I presently do not have the stamina to go into detail.

These all are NOT Java-based and require no browser plugin at all. They all require a somewhat recent JavaScript engine with WebAudio API support in the browser, which all major browsers provide by now.

Besides, OpenMPT was built on the original ModPlug Tracker, which itself was built on ModPlug Player, which itself was built on ModPlugin. With some reverse engineering and the new code, ModPlugin could be back up and running.

This would be beating a dead horse as all browser are phasing out native plugin support. Even leaving that aside, supporting n different broser APIs on m different desktop and mobile platforms and their actual audio APIs appears like some major effort compared to just targetting JavaScript which every browser supports anyway. Brower incompatibilities (maily the audio output itself) are better handled at the JavaScript level.