Main Menu

Recent posts

#1
Help and Questions / Re: Plugin settings not saving
Last post by Saga Musix - Today at 16:58:04
Quote from: crayfish77 on Yesterday at 21:46:17Interestingly 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.
#2
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).
#3
Much better! Has somewhat a Command & Conquer vibe to it
#5
Help and Questions / Re: Plugin settings not saving
Last post by crayfish77 - Yesterday at 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.
#6
Help and Questions / Re: Sending velocities above 6...
Last post by Saga Musix - Yesterday at 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.
#7
Help and Questions / Sending velocities above 64?
Last post by Cartman1337 - Yesterday at 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?
#8
Help and Questions / Re: Plugin settings not saving
Last post by Saga Musix - Yesterday at 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.
#9
Help and Questions / Plugin settings not saving
Last post by crayfish77 - Yesterday at 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?

#10
Free Music Downloads / Re: (Experimental) Quantum X (...
Last post by n0cturn - Yesterday at 15:11:03
Oops! posted the wrong version. Fixed it now. At least anybody that listened will know what I'm working on next because I'd left the start of that on the end!