questions

[zeoka]

Hi
i’ve seen “Added Lua callbacks to store custom user data in programs and Ctrlr states (DAW programs when in plugin mode). Custom data is stored as a ValueTree to simplified access.” in the changelog
this could helps for texts because even if i type in them i save in the daw , i reload the preset the modulator states are saved but not texts
How to use Callbacks ? Do i need to specify the cusom data ?
—
i notice that:
i would have 105 params exported so i have MyPlug.dll and MyPlug.overrides
where the max exported param is set to 105
but i see in daw few other params at the end
Why ?
—–
Is it possible to export fixedslider or combo contents to daw?
Ctrlr does that some long ago.

i use the 5.3.0 version

Thank you

[atom]

1. There are 2 new panel callbacks (panel properties) that are triggered when the DAW loads and saves a project, so just override them and place your data in the parameter of the call, you should get it back when the project later loads.

2. I have no idea what are the extra ones, i’d need to see an example panel

3. What do you mean “export” ?

[zeoka]

-thank you Atom i try them 🙂

-i can send you the panel via mail you can see in other hosts
tried reaper, maschine2, kore2(hum there is a problem with plugs tags , i don’t have the words to explain correctly and quickly ), bloxpander.

-i would mean displaying comboContent or fixed sliderContent in the DAW

if you look at my panel and load a syx or read in a daw the midifle that send patchs you will see some combos send midi messages without any special reason.

[zeoka]

Hi Atom

Please Can you confirm that values in string form (ex :Saw,Tri,etc..) can or not be exposed to the host
in actual Ctrlr version ?

If yes how is it possible ?
Is it bad in term of performance or bug the host “see” them?

There is a Maschine update that render the GUI really secondary now because it
displays “real” values instead of percents..

[atom]

This is a problem due to threading issues, some hosts query those parameters on the Audio thread, that means that i need to lock the GUI to access the string values and pass them to the audio thread, that might mean that the audio thread will be waiting to get the lock… this might cause bad stuff to happen in the host.

I’ll try to figure out a way to avoid that, but it’s hard.

[zeoka]

Ah ok

I remember old Ctrlr displayed well in kore or bloxpander
without visible/audible performance decrease
Not remember for ableton and don’t know for cubase or others
but worked bad with reaper( looked like intensive thing as you describe happens)

All the best

[Author]

Posts