modplug player source code - is it available ?

fabricius · July 20, 2007, 14:05:16

Hi !
I'm a long time module listener, and a new modplug tracker user (in fact I used MPT a long time ago, but never really used it seriously).

Now I'd like to track again and for once *finish* something.

Today I downloaded modplug player and used it to listen to various modules. MPP was my favourite mod player. But now I must admit that I prefer XMplay or dekibulle. I like XMplay because it is really mod-oriented (unlike dekibulle) but I like dekibulle because it runs in tray and can be controlled from global shortcuts (ie no need to leave current app).

I think modplug player misses a lot to be a modern module player: configurable keyboard shortcuts, some user-friendlyness stuff, may be skinable interface (I dont need it, personnally).
For instance: you click on playlist button, you have the playlist. cool. You click it again, it does not disappear. Not cool.
Another example: an internal volume controller. I know it has one, but on a laptop it's not as convenient as the dekibulle one, or XMplay. The MPP volume controller has too narrow range i think.

So I thought: where is the modplug player source code ? I could try to dig it by myself... I'm a software designer, so I could do something...

LPChip · July 20, 2007, 15:08:27

Unfortunatelly, Olivier Lapique, the original author, never released the sourcecode for the player.

And although I suggested to create a player from OpenMPT, it is not gonna happen soon, if at all.

KrazyKatz · July 20, 2007, 15:12:35

Why dont you ask Mr. Lapique? Dont ask, dont get..

LPChip · July 20, 2007, 16:34:27

I guess you can always ask, but I still remember last time when Modplug Tracker went open source. It took quite a while before it actually was realised. But indeed, those who don't ask won't receive.

fabricius · July 20, 2007, 20:52:10

ok, I'll ask him.

maleek · July 20, 2007, 22:50:07

That sounds sweet fabricius. Just on a egoistical note

I would like to add that Open Modplug Tracker that could use a 24/7 kind of guy.

Just joking, the best of luck in your contact with Olivier.

Relabsoluness · July 21, 2007, 17:29:06

Am I the only one who thinks it would be nice to have the (mod)player and the tracker in a single app - like one tab for tracker and one for player. For example if there was a nice part in some tune one could just switch to tracker view and see the pattern structure. But then again, maybe there's a good reason why they were separate in the first place, yet I can't think of a good reason why they should be separate - if someone knows better please enlighten me

LPChip · July 21, 2007, 17:56:29

Quote from: "Relabsoluness"Am I the only one who thinks it would be nice to have the (mod)player and the tracker in a single app - like one tab for tracker and one for player. For example if there was a nice part in some tune one could just switch to tracker view and see the pattern structure. But then again, maybe there's a good reason why they were separate in the first place, yet I can't think of a good reason why they should be separate - if someone knows better please enlighten me

I agree, but differently.

The player part should have a completelly different GUI than the tracker, but ofcource switching between would be great! I actually suggested this long ago.

Its kind of like: add a playlist thingy as first start, and later on top of that, you can make a gui that you can switch to which only shows like the playlist (optional window) and some controls for play/pause/stop/next song/previous song shows progress info.

Sam_Zen · July 22, 2007, 00:01:10

I still have MPP462 associated with the tracker-extensions, for a quick look of a file.
The GUI indeed could fancy some improvements. Things are quite hidden. But a playlist is there, export to WAV, the same
player options as with the editor, song-info, etc.

It already has a link with the editor because in the Details/Song properties dialog there is a button 'Edit in MPT'.
Of course that button doesn't work anymore.

Snu · July 22, 2007, 04:24:48

Quote from: "Relabsoluness"Am I the only one who thinks it would be nice to have the (mod)player and the tracker in a single app - like one tab for tracker and one for player. For example if there was a nice part in some tune one could just switch to tracker view and see the pattern structure. But then again, maybe there's a good reason why they were separate in the first place, yet I can't think of a good reason why they should be separate - if someone knows better please enlighten me :)

but, for writing music you dont want any of the effects added (ie, surround, reverb, bass expansion), but in a player those should be enabled... also, who uses a player in full screen? usually with a player the smaller the better.
i agree that it would be cool to be able to just switch and see the patterns of a playing song tho... but, the player had an 'open in modplug tracker' button which would be good for that.

bvanoudtshoorn · July 22, 2007, 11:45:41

I think that the reason they were separate is because the player can use playlists etc., and also should have a smaller footprint. However, with vst(i)s and what not, lumping them together could be mildly useful... But I must admit that if I do use mpt as a player, I like to see what's happening. I stopped using the player long before it stopped getting worked on. =)

Relabsoluness · July 22, 2007, 14:38:00

.

LPChip · July 22, 2007, 15:11:50

I've taken this discussion to a next level. See here:

http://forum.openmpt.org/index.php?msg=13873.0#msg13873

Sam_Zen · July 23, 2007, 01:16:23

I would like to stay on this level as well.
This is about developing a new stage of module-player.

Apart from standard playlist things, another aspect comes around the corner : Realtime manipulating of the playback.
This has been developed in the meantime in OMPT, with options like 'change mode at transition'.

So such things should be integrated in the Player as well, perhaps also the Channel Manager dialog.
So the player not only can integrate the ole source code of the player, but also the source code of the real-time options
made in the meantime.
This facility would make a difference with other media-players, because it not only can reproduce some song, but
the Player actually can be used by a musician, who is playing it like an instrument.

LPChip · July 23, 2007, 07:24:19

Quote from: "Sam_Zen"I would like to stay on this level as well.
This is about developing a new stage of module-player.

Apart from standard playlist things, another aspect comes around the corner : Realtime manipulating of the playback.
This has been developed in the meantime in OMPT, with options like 'change mode at transition'.

So such things should be integrated in the Player as well, perhaps also the Channel Manager dialog.
So the player not only can integrate the ole source code of the player, but also the source code of the real-time options
made in the meantime.
This facility would make a difference with other media-players, because it not only can reproduce some song, but
the Player actually can be used by a musician, who is playing it like an instrument.

I disagree with you here.

If you want to play around with a song, it should be done in the tracker interface instead of the player, simply because such control would lead to an enormous GUI. A player should be small. In fact, the smaller the better in most cases. A player should be a tool that you activate and can work on the background. It should allow you to listen to your music like it was broadcasted on a radio station (playlist?), with the ability to stop and play, in case you need to interrupt the sound for other sound events, like a telephone that needs answering.

Having the ability to do those life transitions are nice, but IMHO not required for the player interface. True, if the player would be a seperate program, it could have the option to switch to a bigger GUI, but even though, I still think that these options are best for the tracker interface only.