Recent posts

#1

General Chatter / Re: Making my own music commun...

Last post by Soundman - Yesterday at 20:19:52

I have known about and played with OpenMPT since the early 90's when it was called ModPlug Tracker and it was closed source and developed by Olivier Lapicque, he also developed ModPlug Player which I used to like use as well, now I use XMPlay. I think forks are okay, there is an active fork of Audacity called Tenacity and I believe it has real potential. Forks are not a bad thing because those who love the original will most likely stick with the original but those who want something new and fresh will go with a fork. I love Audacity but I also like Tenacity, however for me Tenacity is missing many features that are found in Audacity. Anyone who wants to make a fork or OpenMPT has to realize the amount of work and dedicated time it will take to develop, maintain and bugfix your fork. It is no small task, it will be like a full time job, and you better have a team of people that will help you and also be willing to spend a lot of time developing, maintaining and bug fixing. That being said I would hate to see a fork end up killing OpenMPT, although the Tenacity fork of Audacity has not killed Audacity. Tenacity has given people more options, however there is currently no Mac build of Tenacity, this is not a problem for me because I am a Windows 11 user as well as an Ubuntu Studio user, but it might be a problem for Mac users. i have both Audacity and Tenacity installed in both Windows 11 and Ubuntu Studio, so if someone were to fork OpenMPT I would probably have both OpenMPT and the forked version installed in Windows 11, because both would have their pluses and minuses because different developers would have different ideas and different features, just like Audacity and Tenacity are different from each other.

#2

Help and Questions / Re: Plugin settings not saving

Last post by Saga Musix - Yesterday at 16:58:04

Interestingly I have been using the Drumazon previously in Psycle and it worked fine, the manual also states that it will save all the parameter changes in the song file, but somehow it is not loading them once I reload the song in openMPT. I used a hexeditor to check the actual songfile and I can actually see the correct value in the file (I just maxed out a decay value for the bassdrum). But once I load the song in openMPT it does not interpret it and rest to the factory defaults (which according to the manual of my vsts is the default behavior, IF there is no extra information stored in the song). When I then save the song again (again factory presets) I can see that the decay has changed in the actual file again.

That very much sounds like typical unregistered / trial plugin behaviour, so I would double- and triple-check that the plugin is really properly installed, that the correct plugin DLL is loaded (maybe there are several of them in multiple places?), and that loading the same plugin DLL currently still works as expected in Psycle.

#3

Help and Questions / Re: Sample editor: set one sam...

Last post by Saga Musix - Yesterday at 16:56:04

That seems like a bit of an overkill to draw a straight line in a sample (espeically since it will do more than just that).

#4

Free Music Downloads / Re: (Experimental) Quantum X (...

Last post by Vojvodinosaurus - Yesterday at 16:02:26

Much better! Has somewhat a Command & Conquer vibe to it

#5

Help and Questions / Re: Sample editor: set one sam...

Last post by Rakib - Yesterday at 12:21:44

https://www.izotope.com/en/learn/an-introduction-to-limiters-and-how-to-use-them.html

#6

Help and Questions / Re: Plugin settings not saving

Last post by crayfish77 - May 14, 2024, 21:46:17

thanks for the pointers! I have recently reinstalled my windows partition but have not reinstalled all of my vsts again, I just used the old directories. After reinstall it is partially fixed. Meaning, for some plugins it does save bank selectors and parameter changes, and will reload them when opening a song.

Interestingly I have been using the Drumazon previously in Psycle and it worked fine, the manual also states that it will save all the parameter changes in the song file, but somehow it is not loading them once I reload the song in openMPT. I used a hexeditor to check the actual songfile and I can actually see the correct value in the file (I just maxed out a decay value for the bassdrum). But once I load the song in openMPT it does not interpret it and rest to the factory defaults (which according to the manual of my vsts is the default behavior, IF there is no extra information stored in the song). When I then save the song again (again factory presets) I can see that the decay has changed in the actual file again.

Not sure what I can from here as the VST clearly pushes values into the song file but does not read them back correctly. There is no other MIDI banks or presets active that I can tell, everything is pretty much default. I even checked all options and settings that I would have active in the same VST in psycle and there it works as you'd expect.

#7

Help and Questions / Re: Sending velocities above 6...

Last post by Saga Musix - May 14, 2024, 19:57:16

OpenMPT's 0-64 volume range is translated to MIDI velocity 0-127. You get the full range but every second value is missing.

#8

Help and Questions / Sending velocities above 64?

Last post by Cartman1337 - May 14, 2024, 19:06:00

Ok, so some VSTs can take use of the volume column to send velocities instead of volume, but it's limited to 0-64. Some VSTs do other things with the notes if given velocities in the range of 65-127, though. Is there a way to send such velocities through using OpenMPT?

#9

Help and Questions / Re: Plugin settings not saving

Last post by Saga Musix - May 14, 2024, 18:44:31

In general there isn't much that could be going wrong on OpenMPT's side. It is asking the plugin to provide the data, so most of the job is on the plugin's side. I don't have access to either of the two plugins you mentioned, but just to make sure - both are commercial plugins, so have you verified that they are properly registered? Many plugins with a trial mode will simply not load/save user data when requested to do so.

Another thing to check is if the instruments you have associated with those plugins have a MIDI bank or MIDI program set up - if that is the case, it may cause the plugin to reset all its user data when switching to that specific bank and program.

#10

Help and Questions / Plugin settings not saving

Last post by crayfish77 - May 14, 2024, 18:15:54

Hi,

new to openMPT and loving it. I was still on the Psycle train but got off as it is no longer maintained. As I'm getting to grips with the workflow in openMPT, I was wondering is I missed something regarding the settings of the plugins I use.

For example, I'm using redominator vst and I select a specific bank, or Drumazon vst and I change some parameters. This doesn't appear to get saved with the openMPT songfile. Am I missing something as to why these settings are not persistent? I can save bank presets in the vsts, but then I'd still need to reload them every time I open the file.

Also, certain vst settings don't seem to get saved in the bank as they are generic settings (e.g. internal sequencer on or off and those kind of things).

Any idea how to troubleshoot this?