revision 375

[atom]

A lot of bug fixes, i tried to fix the VST/AU automation crashing and Thread locking, for now i was not able to crash any host while automating multiple parameters, at the same time modifying the UI and sending/receiving MIDI. But i’m not sure i have not tested all possibilites, so it’s up 2u.

Some other stuff worth mentioning

– multiple selection of components, you can select as many as you want and all the common values for those selected components can be edited (also the modulator and MIDI parameters)
– expressions for outgoing and incomming MIDI, that is if you want to have components with values different then the actual midi values, you can have them now, but you need to write
simple math formulas that describe that conversion, ex if you have a panning pot that has the range of -127 – 127 your normal expression for that component would be
[code:1arf26k6]
modulatorValue+127
[/code:1arf26k6]
and your reverse expression would be
[code:1arf26k6]
midiValue-127
[/code:1arf26k6]

that’s it, Ctrlr will deal with the rest. Theese expressions allow parentheses simple sin() cos() and some other math functions and other math operations quote from the JUCE manual
[code:1arf26k6]
This class can parse a simple C-style string expression involving floating point numbers, named symbols and functions. The basic arithmetic operations of +, -, *, / are supported, as well as parentheses, and any alphanumeric identifiers are assumed to be named symbols which will be resolved when the expression is evaluated.
[/code:1arf26k6]

– vst parameter fixes, whenever you add or remove components all components (on all panels) will be re-indexed and sorted, each new component will have the next unique index. This is not tested enough on my side, and i know there might be problems when saving/opening the same projects so be careful with that, but this should fix the issue where you move one slider and some others move too

– LUA has been removed for now from the MIDI processing/VST stuff until i get that part stable, then it will be back.

– Sliders and FixedSliders have the same properties and all should work
– a lot more new colours for components
– some stuff i can’t remember ” title=”Smile” /> have a look at the changelog.

[minimalist]

Yeah, all the new features (multible selection & editing!) seems to be very cool! I’ll test it very soon (particulary the VST/ automation thing!). But 1 think I can tell you immediately: the standalone version crashes very often. If you want to open a new pannel (or an already created) Ctrlr crashes. Also it crashes sometimes when you want to close it. – Mac 10.6.6

Many thanks for this huge update – shortly I’ll test the plugin versions! ” title=”Smile” />

[nrhyan]

Definitely sounds pretty big. Thanks atom, I cant wait to check it out..

[nrhyan]

please take a look at my bug report. on the upside, however, the plugin is now responding beutifully to my mopho key’s knob movements! for me this is so huge.

[atom]

well i know about the automation not beeing exported to Live, but i tested it in other hosts and others don’t mind (Reaper, Maschine) only Live has some problems. This is something i think is in JUCE and i already started a thread on the JUCE forum about this, cause it’s affecting not only my code.

For the standalone stuff, my 1st recommandation is always delete the settings directory from your home directory.

[minimalist]

Ok – the standalone version also crashes after a while when you’re doing nothing. Just open build 375 and wait.
Not sure, but is it possible the there is something wrong with the GUI? The VST/AU versions also crashing the host, BUT it seems that this only happens when Ctrlr’s GUI is open. Until now I didn’t tried out the automation problem (without GUI it’s not easy to test).

EDIT: yes, I forgot about it. I’ll delete it and write soon.

[atom]

well the only thing that happens after some time *5 seconds) is the auto update that gets triggered, try to quickly disable this…
Lua/Hook->[manager]->checkForUpdates set to 0, exit
after you start it won’t do any update checking.

[minimalist]

I’ve deleted in Preferences/Ctrlr the ctrlr.settings file – it didn’t help.

I totaly don’t know something about Lua/Hook. When I’m open it there is a "Manager". When I open (press +) it, there is only midiDeviceManager and luaObject. Absolutely don’t know where I can type something nor where this checkForUpdates should be. Please be more precisely, thanks.

EDIT: Sorry, I found it! But on the other hand: In Maschine the AU version needed much longer than 5 seconds to crash. And all versions only crashed when the GUI was open (and I guess this "updateManager" also works in the background – not only when the GUI is open?). Anyway I’ll test it immediately.

[atom]

Well i’ll re-test it, but i was launching it on my mac and i didn’t get a single crash, i was automating parameters in Maschine for a while no problems…

weird i’ll get back to it tomorrow.

[minimalist]

YES! It was this automated updater, so forget about what I was writing before. Btw: it was absolutely not easy to disable this function in less than 5 seconds. ” title=”Wink” /> Buuut they work… Until now the VST/AU versions never crashed!! Very good work, atom! I’ve to test it more but it seems to be very stable.

Is it possible that Ctrlr doesn’t send it’s messages to the host anymore, only to the other direction – from the host to Ctrlr? Another issue I experienced only with the VST version (not AU): When I want to close a pannel the appearing message "Are you sure you want to close…" is not reacting to "ok" or "cancel" anymore, and it doesn’t disappear anymore. So you have to close the host (in this case Maschine) and it crashes. BUT: this isn’t the most important thing, because usally I don’t need to close pannels (not while music producing).

An other REALLY great thing: Do you remember our discussion about Ctrlr’s parameter names are not showing in some hosts (ig Logic & MAschine), because this hosts refreshing the parameter names only when a plugin is started the first time? => I’ve hosted the AU version… created some sliders with names… saved the project in Maschine… and reloaded it again. Maschine recognised the parameter names perfectly!! ” title=”Smile” /> With the VST version this isn’t possible. Is there a possibility that the VST version could behave same like the AU already does? Would be GREAT!

Build v375 was the very best update ever!!

[aksoni]

Cool. Here’s some bugs, so you’ll have something to do:

– VST Indexing seems broken, made simple patch with 2 knobs and I can’t change order of them. If I’ve understood correctly that VST Index 0 should show up as first in your DAW, 1 second, and so on. I can change those values, but they won’t affect anything and reloading patch will return them as original.

– Exit edit mode, make menu dissapear & close panel => you can’t do anything ” title=”Smile” />

– Still can’t find a way for DAW to display name of the knobs, I have tried on Renoise, Maschine & Logic.

[atom]

well you can’t RE-INDEX VST, i added a [RO] to the tags, you don’t change them, theyre suppose to be untouchable by the user, please don’t change them manually (that’s a bad idead)

– i know ” title=”Smile” /> i cought myself on that, i’ll fix that

– like i wrote this is beyond something i can do, it’s up to the hosts to ask for parameter names, if they don’t ask Ctrlr won’t tell.

[aksoni]

"atom":ezc7w0sq wrote:

well you can’t RE-INDEX VST, i added a [RO] to the tags, you don’t change them, theyre suppose to be untouchable by the user, please don’t change them manually (that’s a bad idead)[/quote:ezc7w0sq]
So no way to make knobs in logical order afterward? Re-arrenging <modulator>…..</modulator> in .panel -file manually?

"atom":ezc7w0sq wrote:

like i wrote this is beyond something i can do, it’s up to the hosts to ask for parameter names, if they don’t ask Ctrlr won’t tell.[/quote:ezc7w0sq]
Those DAWs still show you parameter names with basic plugins, maybe while scanning the plugin for the first time or everytime you load it, so could it help if ctrlr would load last used panel on startup or something like exporting completely different .vst/.au for one panel, which would be cool otherwise too, also more efficient if it ran "player version" of the ctrlr without edit mode, midi monitor, etc.?

+1 tiny bug, no way to name button as =
” title=”Smile” />

[minimalist]

Build 381 seems to be very stable (relating to automations) and everything I’ve tested works as it should! I’ve tried out the VST/AU versions in Maschine and couldn’t find a possiblity (of sending/receiving messages) to get Ctrlr to crash.
One thing I recognised: When one parameter of Ctrlr is controlled (with mouse or automation) the CPU usage increases up to +10-15%. When 2 parameters are controlled: 20-30% (3: 30-45%, and so on). It’s strange that you can’t see this increment inside the host (Maschine, Ableton), but you can see it in Mac’s "Activity Monitor".

As I already wrote the AU version is my preferred version, because the host (Maschine) is recognising the parameternames on startup – even if I re-assign the parameters in the host (Ctrlr VST can’t do this).

One wish: Is it possible that the GUI/window size (and zoom settings) of Ctrlr are saved in the host’s projects?

[Author]

Posts