UAD Console Recall plugin - seems not working

VST Live
1
  • Inserting to SONG-CH insert
  • Activating SYNC (UAD Cons Recall)
  • Modding UAD console setting

But seems magic is not happening at song change. Is it the proper way to use that plugin with VSTLive @musicullum ?

2

This case I need SOS workaround today if there is any :thinking:
@Spork , any idea maybe? :slight_smile:

3

Dear @musicullum @Spork any idea for UAD Console Recall plugin placement in VSTL to be able recall? Would appreciate woraround very much :smiling_face:

4

Sorry, no idea and no time so soon.

1 Like
5

maybe change and change back, don’t know that plug yet.

6

Tested today with studio-mac and not working either.
As a possible workaround, tried to put in a VST container (AudioGridder (based on Juice)), but AudioGridderVST3 is crashing VSTLive.

7

It crashes at the first call to process audio, no idea why.

1 Like
8

Thank u for checking. AudioGridder (VST host) was a backup idea from @CliveJ that could be a workaround, but most important is the console recall VST that could recall console setting (eg bypass/enable Marshall amp unison) if I need clean sound on that UADinput.

So AG not a big deal, but UADConsoleRecall VST3plug might help me instead

1 Like
9

Not quite - my intention was that you use a VST wrapper to host your plugin OUTSIDE of VSTL, assuming you could feed MIDI to it to change settings. My bad, should have been more specific. Surely hosting a plugin within a plugin wrapper inside VSTL would be problematic?

10

Hi @fkalmus,

Sorry for that one. It’s been fixed and will be included in the next Pre-Release (2.2.73).
Please give it a try once it’s available and let us know if it works for you.

… I guess it’s working in Cubase. Can you please do a check?

  1. Start Cubase
  2. Start a new Project_A
  3. Insert the “UAD Console Recall plugin”
  4. Create another Project_B. Now Project_A will be “unloaded”
  5. Insert the “UAD Console Recall plugin”
  6. Switch between Project_A and Project_B a few times

Does it work as expected?

My feeling is that these kinds of “remote plug-ins” only disconnect from the device once they’re fully unloaded.

See you,
Michael.

11

Hi Michael! Thank you for checking :slight_smile: and will feedback then.

… skipped C14 test above and did the same with VSTLive:
NewProj-OneSongOnly-A
NewProj-OneSongOnly-B

Having just one instance, one song, UADConsoleRecall does the job, but if two songs contains the UADConsoleRecall they completely confuse (zeroing) each others. So you might absolutely be right or close to the problem. Is there anything to do?

12

Ah - now you mention it - Korg Wavestation doesn’t seem to like existing more than once in a project. Related maybe?

13

Use just one instance (global maybe). Some plugins are not prepared for multiple instanciation.

1 Like
14

Thank you, I thought song instances are destroyed, so plugin will think being loaded alone.

will try something… (QC via GBL instance)

1 Like
15

Thank you for everyone! feedback and solution:

Seems this plugin won’t work for now (it seems, destroyed-instances are not doing the job at song changes). Also - and thank you - AudioGridderVST container works now as plugin, but can’t make ConsoleRecall working either.

However
For anyone is interested, using UAD:
I found, that for certain parameters UAD introduced Snapshots and they can be recalled via external MIDI#CC (these are different from “saved presets”, that I was using in recent years). Snapshots are storing just a segment of Console states, but for e.g. Unison Insert Bypass it works. I finally can Bypass my MarshallAmp Unison Insert from VSTL via PC#no.
:slight_smile: