I was working on a rackspace that contains multiple instances of ARP 2600 V to accomodate my favorite factory Bass Presets.
Most of the ARP 2600 V save their state (presets) properly - meaning when I reopen the gig file I can un-bypass to hear the sound via variations. The exception are 4 of the presets which don’t save their state (preset resets to STATE - no sound). I can reopen the plugin editor and select the preset, but it will only stay for the duration of the session. Once I save and close the gig file, same behavior when I open back up.
Those culprit presets are:
Acid Baby
Atom Pusher
Flattering Eric
Silver Line
I guess I could give up on those presets if that’s the way it is.
I am just wondering why would it work on most but not on some.
I have also tried to save the preset as a GP user preset but that renders the same problematic behavior.
I must say though - if this somehow is related to Arturia ARP 2600 V, then this would be a pretty cool way for gig performer to identify broken presets. Although it does not show anything in red like a warning or something. A user must just discover such broken presets by bypassing and un-bypassing presets via variations to look for the ones that are silent.
How cool would it be if GP showed some warning to let the user know that plugin preset was not actually recalled correctly by the rackspace/variation.
Any thoughts on how one would go about solving such a strange issue?
by storing the name of the preset that was saved with the plugin block. then checking if it was changed or became blank (initialized).
When the gig file opens - any presets that did not retain their stored names would cause the blocks to go red (for instance).
we are most likely sure the issue is related to Arturia - because I tried VST2, VST3, saving preset in GP, also tried saving the preset and/or project in Ableton - and same behavior.
I guess no sound is enough of an indication the preset did not save - and that works well when checking each one of the 57 instances in my rack.
Just another thought: I have been struggling with Arturia (and other) plugins a long time ago. Arturia has a lot of MIDI CC mappings. If you have unmapped controllers (i.e. not mapped to GP widgets) and you have a lot of active controllers on your MIDI controller, they can go staright through to the plugins. I had this, because in a rackspace change I also did a preset change on an external board, which sent back a ton of controllers indicating the current state…
E.g. the old Arturia Piano V2 has been detuned and vibrating on my side all the time after a rackspace or variation change
What you could try: just put a very restictive MIDI filter in front of the affected plugin, which only lets pass note on/off, pich-bend, modwhell e.g. and test if you still have this behaviour
Arturia V Collection 9.
I don’t have any MIDI CC mappings - meaning I don’t twist any knobs or move any sliders.
My widgets are simply assigned to the bypass of plugin instances to turn them off when not active.
and I save those states in variations.
so I know what you mean, but this is not the case here.
I discovered today another handful of presets from the same synth that also don’t save their state, or simply (even worse) recall the wrong preset.
I downloaded the gig file Version 1.
And I can reproduce that Acid Bass does not produce any sound.
I loaded Acid Bass again in the 1. rackspace, saved the gig as a new gig and loaded the new gig again.
Now sound could be heard.
that’s what I have been trying with numerous presets perhaps 5-10 times each.
Result always the same - when I open gig file, all those culprit presets act the same (either no sound like Acid Bass, or some of them change to other presets). Mac (Monterey) and Pc (Windows 10) the same.
the only thing I didn’t do - was saving as a NEW gig file. Rather I saved over the existing gig file.
I am on Windows 10
Yes it was created with ARP 2600 V3 from V collection 9.
Yes I only used VST3 for all ARP 2600 V3 instances
Yes the dead variations are the problem of my post
The red text label was my way of marking which presets didn’t save state.
Although I missed some in V1, I removed all dead (or misbehaving) ones in V2 of the gig file
Yes some show STATE, others nothing, others select a totally different preset (see PAD Rackspace where some presets go to the Bass category choosing some random preset)
I do have a new Mac Mini M4 I can try this on.
But I am pretty sure the problem is with Arturia, because those presets act the same way if I try to save them in Ableton 10. Other presets work correctly, but those ones don’t seem to want to save their state.
I did email Arturia support with this ticket, but haven’t heard back yet.
Another guess I have is maybe the difference is that I removed presets from factory folder, and I moved from Synthopedia and Patchworks into the Factory folder.
But given ARP 2600 V3 sees the presets well, as well as Analog Lab V, I wouldn’t assume that would be an issue.
Hm, drilling deeper: the plugin state for the Android Steroids in your gig file is ~5.633 bytes, in my reloaded and saved as new ~10.707 bytes
I’m not familiar with plugin states, however it looks like there’s something missing… either not sent or received the full package?!
Once a (simple) preset is loaded, it’s not referred by a plugin state anymore AFAIK. You even don’t need to have user preset as a file or db entry, it’s in the state and you can save it as an ‘own’ preset.
ok i heard “saved as” new gig file a few times - and forgot to try that.
i will try it now.
downloading V1 of the gig file
placing back Acid Baby preset
Opening ARP 2600 V3 to ensure that preset is recognized in the standalone.
Then opening the V1 gig file
Replacing the Acid Baby preset
Saving as a NEW gig file. Closing GP.
Opening the NEW gig file
and…
oh forgot i have to wait for gp to release memory
opening the resource monitor…
waiting for gig performer to disappear from the RAM section…
ok it’s gone. try this again…
Opening the NEW gig file
drum roll…
loading about 1 min 40 sec…
and…
Acid Baby is lost
Opening that block shows no text in the preset title.
Update:
I posted V3 of the article and gig files - for those interested to try.
In short - I have identified 15 more culprit presets, removed them, and added Red LEDs for opening/closing the plugin editors.
Now the project is down to 141 presets.
It takes about 1 minute to load/open.
All 141 presets save their state/their name and behave properly.
I prefer less presets and stability vs more presets that I can’t rely on.
No word from Arturia yet - as it’s the weekend.
My guess is that they will reply with something early next week.
issue remains unsolved after talking to Arturia.
See update here.
If it’s not GP related.
If it’s not Arturia related.
not sure what to say - but I am pretty sure it has to be Arturia related - because the same thing happens on every computer i tried it - mac and pc.
can’t be related to Ableton 10 because although Ableton 10 behaves the same way when it comes to those culprit presets - I am not using Ableton 10 for those presets.
I just gave up on those presets and this issue.
Now I know that certain presets can exhibit this behavior, and need to be on the lookout for such cases.