Forum Replies Created
-
Posts
-
I’m also looking for 5.3.163 for OSX
The only OSX version in the downloads section is 5.3.198
Looks like AU is crashing with Logic. I’m trying to install logic but it needs hardware accelerated graphics, witch i don’t have at the moment (my hackint0sh uses framebuffer only). I’m working this out but it might take awhile so be patient.
I have some contacts at Apple and I sent them my latest crash report (Logic Pro 10.5.1 crashing on load if any Ctrlr plugin is in the session.
They looked at it and said:
“It is a crash in a static constructor of CtrlrMethodEditorTabCloseButton.cpp . Simple AU crash. Please talk to the developer!”
However, I started seeing random validation errors – for example I have completed a plugin and it’s validated and working perfectly, then I change some insignificant aspect (such as the color of the background) and it will FAIL the validation citing parameter values not retaining default values:
“WARNING: retrievedValue = nan (was 0.000000), Parameter did not retain default value when set”
Even if I revert to a previous version it will also fail validation. It’s weird and frustrating.
If I select “use” in the plugin manager, the plugin will work perfectly in Logic, despite this “failed” validation.
I tried renaming the panel as you suggested but it did not make any difference, however I discovered something peculiar in the non working panel.
There were 4 toggle buttons that had some different settings, but I cannot understand how or why..
The first thing was that in the “Link to what type of MODULATOR property” field these read “MIDI Message” and in every other control it simply had the word “Modulator” but it was greyyed out and could not be changed..
Also the field for component position would be in a different order in the editor window for these buttons.
I have uploaded the repaired “GOOD” panel and the latest “BAD” panel(which is simply renamed as you suggested)
Somehow the differences between these two panels is causing the AU validation crash…
Not sure it’s specifically a Logic issue
How fascinating.
Are we sure?
I “fixed” one of my other panels recently and because I wanted to keep an earlier version in there as well I added my initials to the name. It works fine but then so does the earlier version with only one name…
I tried to insert the
panel:getPanelEditor():setProperty(“uiPanelZoom”, 1.0, false)
into a method, but I’m not sure I understand the usage.
My panel opens as an audio Unit with the window covering the full screen, but only on this one panel
I also think the issue is with the AU export function.
This is a very simple panel, only CC data, no programming at all.
It works fine as a stand alone, but not as an AU.
Have you come any closer to understanding what the Meta Parameter flag is?
Also, of course I save versions, I’ve got hundreds for each panel I make, but if the problem is happening during the export, and not due to any real panel error, then this is a bit more serious. The OSX version hasn’t been updated in a very long time..
Well, I asked about “Meta param” as this was the title of this thread and your initial question
But OK, we forget that one then.
I’ll see what happen with the AU on my side.
At this stage, I’m not using the VSTindex at all and don’t see why you should do that for 10 controls…
On your Mac, you can also test your AU panel in Reaper. Then you have at least 2 DAWs for testing.You can create a method PanelLoaded() that is called at panel load (property “Called when the panel has finished loading” of your panel).
In that method you can place the following code to set the initial zoom factorpanel:getPanelEditor():setProperty("uiPanelZoom", 1.0, false)1.0 means 100%
VST index is the order in which the parameters appear in the DAW, both in the control surfaces and when selecting automation parameters.
Thanks for the tip about the PanelLoaded() command, I’ll try that..!
Thx. That I knew and will tell you what I get on my side.
I was speaking about how to reproduce your error “Meta Param Flag is NOT set on a parameter that will change values of other parameters”…Something else: by checking different things on your panel, I saw that the ModulatorValue property is not updated when you change a modulator. Doesn’t sound good but I don’t know what the reason can be.
When selecting another mod then coming back on the first one then the property is updated though.Now, as your panel is very simple without any coding, I can also re-create it from scratch.
Will do it and we can also check that.Not sure what you are asking, the “Meta Param Flag” error indicated is a complete mystery to me, I’ve googled and it seems to be not uncommon. These errors here seem arbitrary, as if there is a bug in the AU export section of the ctrlr app, when I added additional parameters to an known good version of a panel one by one I managed to get it to work, but the “bad” version was created in exactly the same way, so I am confused.. 🙁
There are weird and arbitrary issues in this version of Ctrlr, for example some of my panels open as AUs with a fullscreen window around them , some take the size of the panel’s surface graphic. Yesterday I tried to re-order the modulator list VST index on one panel and it couldn’t be found during an AU scan, while I had done the exact same thing to another panel the day before with no oddness. I hope you can see something there that I can’t..!
Can you please guide me a bit on how you get that error?
You seem to say that you have that with other panels. Maybe you are doing something wrong with all of them?
I’ll try to make a Logic version.Thanks..
All of my other Panels work fine. All of them except the Thermae panel above.
Open the panel in the “CTRLR AU” Instrument plugin in logic. (create an instrument track for this)
Select “Export Instance” this will create an AU component in the components folder.
Save and quit Logic.
Re-boot the mac.
Launch Logic, this will scan the new AU plugin.
I usually get an error message here, so I open the “Plugin Manager” in Logic (under the preferences submenu) and search for the plugin.
If it says “Couldn’t be opened” or “failed validation” then select it and press “Rescan selected”.
Logic will open another window and detail the scanning process, and in my case show the warnings I included in the first post of this thread.
I managed to fix one of my other panels by adding the additional controls to a known good earlier version, but I still have one that is causing trouble for me. It works fine as a standalone but fails validation in Logic
Do you think you might be able to diagnose my error?
I have not solved this. It is frustrating..!
“Meta Param Flag is NOT set on a parameter that will change values of other parameters”
I have no interdependent controls in my panel.. what could this mean?
It’s inexplicable..
I copied and pasted my controls to a new project and everything worked fine, even though I could fine no differences between the two panels.. very confusing.
I’ve been going through every parameter and cannot locate what “flag” is being set here.. confused!
haven’t used fixed slider yet; regular modulator sliders come up
with a default setting on those ‘evaluate’ entries. maybe do a test
with one of those and see what you get in your host.I think I’m just using the basic UI slider..
Here I have selected the fader on the top row at the right, labeled “HC”
It has 31 possible values from 497 to 527, and I use the mapping I posted earlier to get the slider to display the cutoff frequency in Hz:
On the AU the HC parameter value passed to the DAW reads between 0 and 1, shown here in Logic’s “controls” mode while in the normal mode the GUI shows the values as expected.
The issue is how can I get the displayed values to be passed to the DAW instead of the 0-1 values?
looks like float values? ie: you are getting decimal points between
0 and 1 ?
‘expression to evaluate’ should have ‘modulator value’ (by default,
unless it’s a centred -/+ control, and offset +24,+48 etc.) for the
MIDI message to send, and for receiving should say ‘ midi value’,
unless that needs to be offset.soz can’t think of anything else right now. you are using an
image slider with a fixed values list? maybe that needs something.Right. It’s not dissimilar to several other Plugin authoring programs I have and dozens of commercial plugins that only display values between 0 and 1, in several UAD plugins if you go to “controls” mode — where you see the parameters only, no GUI if you double click a value, even if it’s displayed as 300 hz you might have to type in “0.65” to get a value 65% up in the available range.
Each slider is sending a sysex value of some arbitrary value in the hundreds.
I’d like the displayed “MIDI” value to duplicate the slider’s displayed value.
Is that possible?
