Mattijs

It would be great to be able to recall a plugin preset by sending "recall x" to pluginconfig while a pluggo is loaded in Logic. Is it correct that this currently doesn't work?

recall-message-from-within-plugin-doesnt-work

Quote: mattijs@samplemadness.nl wrote on Tue, 17 October 2006 04:27

----------------------------------------------------

> It would be great to be able to recall a plugin preset by sending "recall x" to pluginconfig while a pluggo is loaded in Logic. Is it correct that this currently doesn't work?

if this is not a new bug ... it normally works.

just dont exspect that it changes the preset# in the

Quote: mattijs@samplemadness.nl wrote on Tue, 17 October 2006 04:27
----------------------------------------------------
> It would be great to be able to recall a plugin preset by sending "recall x" to pluginconfig while a pluggo is loaded in Logic. Is it correct that this currently doesn't work?

just dont exspect that it changes the preset# in the
host?s preset system


Thanks for your reply. I tried the patch below. I build it to a plugin and load it in logic, change the values of the pp's and press 'recall 1'. Nothing happens..

So I guess we have to file a new bug then. I am not sure if the bug is with cycling though, I am having other problems recalling presets in logic..

Maybe someone from cycling 74 could check this?

Same here on pluggo 3.6/powerbook & G5 dual/OSX 10.4.7

The recall message don't work anymore, and some recall weirdness that I'm trying to get to a reproducible scheme.

Same here on pluggo 3.6/powerbook & G5 dual/OSX 10.4.7
The recall message don't work anymore, and some recall weirdness that I'm trying to get to a reproducible scheme.

The problem I am facing is that Logic -sometimes- (?!) doesn't load saved param values back to a plugin correctly. When I open multiple songs at the same time, for 1 of 4 plugins all params that were not automated are set to their minimal value.

We do a live performance friday where we open 6 songs in logic at the same time, leafing through the songs during the performance. Right now, whenever I open the songs I have to go through all instances of my plugins (12+ per song) and manually choose the init preset to set all non-automated parameters to their correct value..

I hoped I could send all of them an udp message, link that to 'recall 1' and be done.

I can reproduce here in MaxMSP and Live. I notice also in Live that if you hit the recall 1 message in this plug it actually updates the init preset in that instance of the plug - kinda weird. We'll look at it all for sure.

In the case of Logic not loading up all params, Are you able to tell us a little more about this? What happens if you load the songs one by one?

I can reproduce here in MaxMSP and Live. I notice also in Live that  if you hit the recall 1 message in this plug it actually updates the init preset in that instance of the plug - kinda weird. We'll look at it all for sure.

Plugconfig has never accepted commands from inside a plug-in context. And it never will.

There may be a host specific way you could arrange to have the data "resent" to the plug if it is not getting loaded correctly. But we would prefer to get a better idea of why the plug is not loading correctly in the first place.

Some more info: I found out that when I set the initial program to 0, the problem disappears. So that solves the pluggo problem for now. A more accurate description of what happens if initprogram is set to 1: all parameters of some plugins (differs every time) that are not explicitly automated are set to their minimum value (not to the value of the initprogram!). When loading the songs one by one the problem still occurs but it feels like it occurs less. Only about 6 plugins of the 12x6 total were not initialized against say 24 when all songs are loaded at the same time (which means you press "don't close" 5 times in a row). The numbers are inaccurate.

But, even more interesting: we found out that a similar problem occurs with logic native plugins! So I make a song, make a nice mix using native eq's, limiters and compressors on several tracks, save the song. Then when I open the song together with other songs, Logic randomly forgets to load back non-automated parameters of -some- of the plugins. Each time these are different plugins. A native plugin that doesn't get its parameters loaded always has all parameters set to default, except for the ones that are explicitly automated.

Sorry I can't be more specific, we are in the middle of rehearsals now and we try to work around it. A solution is to save presets of all plugins and restore them all after loading all songs. It's not a nice job though but we probably have enough sound checking time at the gig (which btw is the Eboman performance at the VAD festival in Girona, Spain. It's gonna be legendary. In a good or in a bad way, I don't know yet. Anyone wants to be on the guest list? ;)

Ps. This mixing thing was very nasty to figure this out because when you open your song and it sounds slightly different, first things you start to doubt about are your mixing skills..

Sounds like there may be a small possibility that Logic has some kind of problem.......

One way you could potentially get around this in your own plugs would be to create a parallel state saving mechanism with pattr, and trigger the slot name as a param or message or whatever. It might be a slightly ambitious task to attempt during sound check though.

Heh, we just got at the gig, they tell us the G5 Quad they would reserve for us is broken. Much apologies.. We planned to install our cards and hd's in their G5 about.. now. Tomorrow is the show.. hmm, they're buying a new one right now in Barcelona, they say it'll arrive tomorrow. There goes our sound-check..

Anyways. Yes, Logic has a problem. More than one, but this one is specifically annoying. For the pluggo's the problem is already 'solved' by setting initprogram 0. No need for a parallel preset system. It's hard to set initprogram 0 to the logic native plugins though :p.

Recall message from within plugin doesn't work