Modartt user forum - Organteq VST plugin, current settings are not saved with the project

Re: Organteq VST plugin, current settings are not saved with the project

null@example.com (Stephen_Doonan) — Sun, 11 Aug 2024 15:34:41 +0000

rolandcahen wrote:

Thanks for sharing these issues.
Could there be any good reason why there is no pin icon for MIDI mappings on ORGANTECH VST?
Is there any other way to select default mapping though MIDI or VST parameters ?
I haven't yet found any solution to recall the correct MIDI mapping at project startup using the VST version, even in Max MSP. Consequently, my sound installation cannot work until i find a solution. In addition I am using 8 instances of the plug-in and changing manually each one is a nogo.
Annoying !

I believe that there is a fairly high probability that you can accomplish (in some way) what you are trying to accomplish.
Which DAW(s) do you use? (I use Ardour or Mixbus in a Linux operating system.)

What is a "pin icon"? What does or should a "pin icon" do?
Exactly what MIDI mapping are you trying to create, save and recall? (Which MIDI data are you trying to map to which Organteq parameters?)
How would you want this MIDI mapping to change for each instance of Organteq you are using within the DAW?
Why are you using 8 instances of the plugin? (I'm simply curious about this question. Why are so many instances necessary in your case?)

Best--

Re: Organteq VST plugin, current settings are not saved with the project

null@example.com (rolandcahen) — Sun, 11 Aug 2024 10:35:19 +0000

fakemaxwell wrote:

Hi Roman,
Thank you for the response. I understand now that this is by design, but my question is- why? I don't know any other plugin that works like this. It's not even per project, it's per instance that the MIDI mapping can and does change.
Is there some breaking reason that Organteq works differently than other VST instruments in this regard?

Thanks for sharing these issues.
Could there be any good reason why there is no pin icon for MIDI mappings on ORGANTECH VST?
Is there any other way to select default mapping though MIDI or VST parameters ?
I haven't yet found any solution to recall the correct MIDI mapping at project startup using the VST version, even in Max MSP. Consequently, my sound installation cannot work until i find a solution. In addition I am using 8 instances of the plug-in and changing manually each one is a nogo.
Annoying !

Re: Organteq VST plugin, current settings are not saved with the project

null@example.com (fakemaxwell) — Mon, 17 Jan 2022 02:36:51 +0000

Hi Roman,

Thank you for the response. I understand now that this is by design, but my question is- why? I don't know any other plugin that works like this. It's not even per project, it's per instance that the MIDI mapping can and does change.

Is there some breaking reason that Organteq works differently than other VST instruments in this regard?

Re: Organteq VST plugin, current settings are not saved with the project

null@example.com (Roman) — Wed, 22 Dec 2021 14:52:09 +0000

Hi fakemaxwell,

There was a bug regarding the live state (stop switches, couplers switches, etc...) which was sometimes not saved when saving the whole project. I believe version 1.6.4 fixed it. If you still encounter the problem, please contact support@modartt.com with a detailed procedure to reproduce it.

Regarding the MIDI mapping, it is not saved with the project on design.

If a global MIDI mapping for all your project is sufficient, I suggest to set it as the default MIDI mapping from the menu. You have to save it after editing it.
If each project deserves its own MIDI mapping, I suggest to attach it to the preset of the project. You have to save it after editing it.

Roman

Re: Organteq VST plugin, current settings are not saved with the project

null@example.com (fakemaxwell) — Wed, 22 Dec 2021 05:19:39 +0000

There's been one minor update to Organteq since this issue was posted, and it hasn't been addressed. Is there anybody from Modartt paying attention to these forums? Is Organteq dead already?

Re: Organteq VST plugin, current settings are not saved with the project

null@example.com (Dust) — Thu, 21 Oct 2021 22:45:42 +0000

Blae wrote:

I'm having the same issue in FL Studio 20

I'm using FL Studio 20 as well and experiencing this issue.

Re: Organteq VST plugin, current settings are not saved with the project

null@example.com (Blae) — Sat, 02 Oct 2021 14:56:52 +0000

I'm having the same issue in FL Studio 20

Re: Organteq VST plugin, current settings are not saved with the project

null@example.com (lewisalexander2020) — Sat, 28 Aug 2021 08:06:19 +0000

Noticed this in Logic Pro x, drives me mad constantly. that's the only downside. This does need looking in to.

Re: Organteq VST plugin, current settings are not saved with the project

null@example.com (Pat) — Sun, 01 Aug 2021 12:05:57 +0000

@fakemaxwell, Thanks for confirming the problem. I hope that Modartt will recognize this as a bug and fix it.
A supplementary note on the behavior in Cubase: It is not sufficient to save the preset as a VST3 preset (in the Cubase Mediabay).
You have to use Organteq's own preset management and make sure that the MIDI settings are saved with the preset.

Re: Organteq VST plugin, current settings are not saved with the project

null@example.com (fakemaxwell) — Sat, 31 Jul 2021 00:46:27 +0000

I'm having the same problem. In Reaper, VST3. It seems I can get the stops to be remembered sometimes (but not always), but the MIDI mapping always reverts. I only have one keyboard so I usually have the different registers on different tracks, if I put a track each on Recit, Grand Orgue, Positif, and Pedale, when I close and reopen the project they are all reset to Grand Orgue. Even after saving the MIDI mapping it still reverts.

The only way to get everything to save correctly is to save a preset every time, attaching the MIDI mapping to the preset. This is a big ole pain, since every time you adjust you have to resave. Pianoteq doesn't do this. Possible for a fix?

Organteq VST plugin, current settings are not saved with the project

null@example.com (Pat) — Thu, 29 Jul 2021 10:12:19 +0000

When I use Organteq as a VST3 plugin in Cubase 11 pro (Windows 10), I have the following problem:
In contrast to all other plugins that I know, Cubase does not save the current status of the Organteq plugin settings.
For example, if I made changes to a combination (selected other drawknobs), but did not save these changes as a new snapshot, these changes will be lost after closing and reloading the Cubase project.
Instead, the combination is loaded in the unchanged original state.
This behavior irritates me a little, you have to make sure that all current settings are first saved in Organteq before you save the Cubase project.

The problem also affects the MIDI mapping settings. Unfortunately, Cubase forgets such changes when saving, so that you have to make the appropriate settings manually after loading the Cubase project.