Recent posts

#21

Development Corner / Re: How long did libopenmpt ta...

Last post by manx - November 26, 2024, 09:49:34

I've been constantly talking to cs127 about how OpenMPT should "fix" it's UI as in not use MFC so that it can be ported to run natively on Linux without Wine.

Can you please move such discussion to a/(any) public forum? We already have an issue tracker issue (https://bugs.openmpt.org/view.php?id=783) that tries to track everything roughly related to that (this includes all transitively linked issues). It would be great if you could just either start new issues or amend existing ones if the topic fits with summeries of your discussions.

I know that the playback was "fixed" in I think 2013 (every time I check, it turns out it was released a year earlier than I thought) with libopenmpt, but I don't know a lot about libopenmpt's development, so I want to know a few things. First off, when did it start development? I know that it stated work on with the current developers, but I don't know if it was started a year or two prior or if it was started immediately in the late 2000s.

libopenmpt development effectively began when I joined OpenMPT, which, according to https://github.com/OpenMPT/openmpt/blob/f57280eee841ac2bf1f817914ff40f9086bab718/common/version.cpp#L603-L623 and https://github.com/OpenMPT/openmpt/blob/f57280eee841ac2bf1f817914ff40f9086bab718/packageTemplate/History.txt#L13-L21 was sometime in 2012. Saga Musix and I had been talking about the module playback situation on non-Windows systems before that at Demoparties for about 1 or 2 years I guess.

I also want to know how much the code base being less windows reliant and libopenmpt being was developed, was it sort of a backburner task while other features were being worked on, or was it the main priority and nothing else was being added to OpenMPT at the time? Was the development all a conceited effort through and through, or were there massive ebbs and flows in how much it was being worked on?

I would say, it was an integrated approach for the most part. I mainly had joined OpenMPT with the intention of moving it towards a cross-platform playback library. I never felt it was the right approach to only work solely on that though, thus I also worked on tasks only related to OpenMPT itself.

We converted the playback code to be usable alone basically while still keeping the whole code base working and releasable as OpenMPT. This was frankly one of the main goals, and still is, because we very much wanted to avoid divergence between libopenmpt and OpenMPT like it had happened before between libmodplug and OpenMPT, see https://openmpt.org/legacy_software, https://lib.openmpt.org/libopenmpt/faq/, and https://buildbot.openmpt.org/history/ for more context on that history.

There were various things to clean up (in no specific order, and probably not a complete list):

• MSVC-specific language extensions
• global state (inappropriate for a thread-safe library)
• entanglement of UI code and playback code that had creeped in over the years (note that originally, ModPlugTracker and ModPlugPlayer had a shared code base)
• build system and dependency handling
• x86-specific assembler code
• Windows-specific API usage and assumptions
• portable character set handling

The details of that process and everything related to that could likely fill multiple long blog posts.

As the API facade on top of the shared code base (which libopenmpt still is and should remain), libopenmpt was implemented in probably a week or so, once the foundation was set. Porting to non-MSVC/non-Windows really only started after that, because before that there was not really anything that could sensibly be ported and (compile-)tested because of the MFC dependency.

With the release of libopenmpt 0.3 (2017), OpenMPT switched from a trunk-only development model to using release-branches, which was somewhat necessary to be able to sensibly maintain older versions (of both, OpenMPT and libopenmpt) with bug fixes while shielding them from major refactoring or development work on a shared trunk. This is probably also the main reason why we use SVN instead of GIT. GIT is awful at that development model without additional tools that track cherry-picking (in git-speak) / selective-merging (in svn-speak).

Was the getting off windows a priority from the start, or was that decided later on?

That was a goal from the start, and still is.

Also if months/dates could be provided that'd be nice as it's annoying to say "2013" or "2008" without any reference on where in the year that was.

Well, everything is in the SVN repository at https://source.openmpt.org/svn/openmpt/ (not sure how good the development-branches that we used early on are mapped to GIT (https://github.com/OpenMPT/openmpt/), but in theory the commits should also all be there).

#22

Development Corner / How long did libopenmpt take t...

Last post by minebrandon - November 26, 2024, 08:27:06

I've been constantly talking to cs127 about how OpenMPT should "fix" it's UI as in not use MFC so that it can be ported to run natively on Linux without Wine. I know that the playback was "fixed" in I think 2013(every time I check, it turns out it was released a year earlier than I thought) with libopenmpt, but I don't know a lot about libopenmpt's development, so I want to know a few things. First off, when did it start development? I know that it stated work on with the current developers, but I don't know if it was started a year or two prior or if it was started immediately in the late 2000s. I also want to know how much the code base being less windows reliant and libopenmpt being was developed, was it sort of a backburner task while other features were being worked on, or was it the main priority and nothing else was being added to OpenMPT at the time? Was the development all a conceited effort through and through, or were there massive ebbs and flows in how much it was being worked on? Was the getting off windows a priority from the start, or was that decided later on? Also if months/dates could be provided that'd be nice as it's annoying to say "2013" or "2008" without any reference on where in the year that was.

#23

Development Corner / Re: Open ModPlug Player

Last post by sunshine - November 25, 2024, 10:02:42

PlayList Editor demonstration of ModPlug Player 2 Alpha 4 version: https://youtu.be/2pgCnw1SQcg

#24

Development Corner / Re: Open ModPlug Player

Last post by sunshine - November 24, 2024, 15:52:04

Hello everybody. Before new year, I am planning to release Alpha 4 version of ModPlug Player 2. I started working on this project full dedicated this month. This release will have the following features:
* All the spectrum analyzer settings will be functional.
* Playlist editor window (it is completely functional but its integration may be completed on the next Alpha release).
* Resizable main window (all the components are resizable now, but this feature may be completed on the next Alpha release).
* Interpolation mode and reverb features will be functional.
Since I actively full dedicated working on this project, we will have new releases more frequently (probably every 1-2 month). I am planning to have first full functional beta release next year.
Web page of ModPlug Player 2 is http://www.modplugplayer.org and I am planning to develop a modern web site for it before the beta release. Currently this address is redirected to SourceForge project page.
For spectrum analyzer settings, you can see this video: https://youtu.be/hCk4EMbA4BA
For color settings of spectrum analyzer, you can see this video: https://youtu.be/EttvI3wWDfY

#25

Development Corner / Re: Open ModPlug Player

Last post by sunshine - November 24, 2024, 15:40:56

Hi sunshine, I hope you are still ok and working on this project... I was thinking I might offer to lend a hand in the ways I can by offering to make skins for it.
It has been so long since you were working on this lovely little project, and I really hope you are still ok. If you have had life get in the way, maybe an offer for some graphical assistance might get you enthused on the project again, but if you dont reply I will try my very best to fork the project and add skins that way and maybe when you come back I will have skins to offer you.

EDIT : WARNING! WARNING!
do not drag and drop your tracks into any of the windows versions of this... it deletes the file! Fortunately I tested the drag and drop on a tune I had already uploaded to the modplug forums, but when I went to go drag and drop it again it wasnt there... YOU HAVE BEEN WARNED!

I added a warning on the git for other people too.

Hello Exhale,
I actively develop this project, and I explained you this bug on your bug report of your project. I am a software engineer, and I develop this application on my spare times. This year I decided to dedicate most of my time to the development of this application. I resigned my daily job, and as I wrote, I decided most of  my time to develop this project full dedicated.
On Alpha 2 version, there was file deletion bug, but I fixed it on Alpha 3 version. When you noticed that bug, there was Alpha 3 version but I accidentally removed Alpha 3 on GitHub. When you opened bug report ticket, I explained it to you and reuploaded Alpha3 version to GitHub.
I have skin support on my development calendar, but it is very early to add skin support. I am planning to add skin support next year, and it will be similar to Winamp's modern skin support. You can share your skin designs here, and I will be happy to use your skins, too.

Here is his GitHub page https://github.com/ModPlugPlayer/ModPlugPlayer
It looks like he hasn't done anything on Github since Oct 26 2022. I hope he is okay.

Thanks newbie. My brother died previous year.
This project was in my mind since 2004, and it is not a short-term project. I want to continue to its development until the end of my life.

#26

Help and Questions / Re: Surge XT vst3

Last post by nycos62 - November 17, 2024, 08:13:29

thank you for your answer, well, let's wait v33/25 or v1+1/(3+1/8) 

#27

Help and Questions / Re: Surge XT vst3

Last post by Saga Musix - November 16, 2024, 20:48:03

OpenMPT does not support VST3 plugins, and probably isn't going to anytime soon due to Steinberg's unfortunate decision to release the VST SDK under either a proprietary or GPL license. However, the upcoming OpenMPT 1.32 will support VST shell plugins, which means that you can use polac's vst3shell plugin in OpenMPT.

If you would like to give it a try at this point in time, you can download OpenMPT 1.32 test builds from https://builds.openmpt.org/builds/ - Just load vst3shell and vsti3shell into OpenMPT and they will automatically add all installed VST3 plugins to OpenMPT's plugin list.

Alternatively, here's the last Surge version that was distributed as VST2: https://github.com/surge-synthesizer/releases/releases/tag/1.6.6
It's possible that later versions that were only distributed as VST3 could still load in OpenMPT, because some older VST3 plugins contain a built-in VST2 wrapper. Might be worth a try to see if e.g. v1.9 still loads in OpenMPT.

#28

Help and Questions / Surge XT vst3

Last post by nycos62 - November 16, 2024, 19:36:34

Hello, any idea why Surge XT vst3 drop the message "File is not a valid plugin" into the plugin manager ? ( https://surge-synthesizer.github.io/ )

#29

Free Music Downloads / Re: [Chiptune] Massive Hamburg...

Last post by Saga Musix - November 16, 2024, 18:32:28

That's a good start indeed. Keep going!

#30

Free Music Downloads / [Chiptune] Massive Hamburger (...

Last post by south - November 16, 2024, 17:41:38

still learning openmpt, but i'd say i did a somewhat decent job on this for my first time