r486 warning

[atom]

there is a new component uiLCDLabel, witch is what it says a LCD like label
but it won’t work on the MAC, there is a bug in JUCE (i think) that breaks custom fonts (LCD fonts are built into Ctrlr)
so MAC users please don’t try to use it, it will crash Ctrlr

there was a bug that cause VST/AU versions to crash on the MAC, i worked around it (maybe fixed it). you will notice a slight
delay (hang) when Ctrlr is loading or is beeing scanned by the host, that’s ok it has to be this way (there is a "feature" on this devilish
OS that tries to deliver messages to a plugin instance that doesn’t exist anymore, witch not only is weird but also causes crashes).

[minimalist]

"atom":c115xgxl wrote:

so MAC users please don’t try to use it, it will crash Ctrlr[/quote:c115xgxl]
That’s really sadly! Not because I need this LCDLable (for me it’s just a graphical "nice to have")… No, it’s sadly because it seems to me that on PC created panels (which have this LCDLable) are not compatible to Mac anymore!?
This seems to be a big step backward in terms of compatibility.

"atom":c115xgxl wrote:

you will notice a slight delay (hang) when Ctrlr is loading or is beeing scanned by the host[/quote:c115xgxl]
Yes, there is a slight hang when Ctrlr is loaded – but because it’s really slight it’s OK. But: there is a very huge delay when Ctrlr plugins get removed from the host (at least on Maschine).
In older Ctrlr releases when I wanted to close a Maschine project which e.g. contains 15 Ctrlr plugins… the needed time for this was about 2-3 seconds.
Since 486 the needed time for closing the same project is about ONE minute! To wait such a long time just for close a project (or quit Maschine) is a bit… too much?

[atom]

yes it is too long, i’d need to know what panels do you have loaded to see what takes so long.

if the mac/windows lcd issue won’t get fix, i will remove that component, but i hope to fix that.

[minimalist]

I’ve tested it with completely blank/empty Ctrlr plugins in Maschine.
Load this project: 1-2 seconds
Close the project: 50 seconds

[atom]

well that’s weird, i’ll have a look at that. maybe you have some resources in the Ctrlr settings folder ?

[minimalist]

Do you mean that I maybe have some images (for panel background, sliders, buttons, ect) in the common "resources" folder? Yes, I do (of course).
I’ve tested it with with completely fresh & empty Ctrlr plugins – I assume that they don’t grab to this folder in this case?
For further tests I’ve deleted now all images (pngs) in that folder… Closing Maschine still needs such a long time.

[atom]

allright i’ll definetly look at that @home

[minimalist]

Great!

[minimalist]

I’m not sure if this should be fixed (in 496)… If yes: I can’t see any difference to the build before.

[atom]

i uploaded a new build for the MAC using the old JUCE that should at least fix the no-click bug.

[minimalist]

Many thanks! ” title=”Smile” />
(this long time when removing plugins issue still exists (in Maschine), but I assume that you know about)[/size:218gl9je]

[minimalist]

"atom":157x7ypp wrote:

allright i’ll definetly look at that @home[/quote:157x7ypp]
Do you already have some news about this? I’m still on 475 because of that (nerving) bug.

[atom]

i double checked this, i loaded the Tetra panel you’ve sent in the VST ctrlr in maschine, everything seems to work fine in terms of exiting. I can’t see a problem here. I’ll try to fix the cpu usage and re-check, i had a lot of work and didn’t have a lot of time for Ctrlr. Once i get some time i’ll get back to this.

[minimalist]

OK, no problem. As I told you don’t have to take the Tetra panel – even with an empty/complete fresh panel/Ctrlr this problem should appear. Did you try to load some more Ctrlr plugins (instead of one) in the Maschine project? In my case each(!) loaded Ctrlr VST/AU needs about ~ 4 seconds to close it (12 VSTs/AUs: ~ 50 sec). In older releases 12 plugins needed about 2 seconds to close. Maybe you should test this issue with some more Ctrlr plugins to notice the delay better?

[atom]

multiple ctrlrs loaded, no i haven’t tried that, i have to say multiple copies of Ctrlr loaded in one host means trouble and i don’t think this will ever change. but i’ll see what i can do.

[minimalist]

Sorry, I don’t think that "multible copies of Ctrlr loaded in one host" is the problem (at least not on Mac). As I wrote: in ALL versions before 486 it worked well (just a short time to close the project/host).
… and as I also told: Even just ONE single Ctrlr plugin loaded in Maschine causes a "big" delay when it get removed (486: 4 seconds… in older releases (<486) ONE single plugin just needs: ~ 0.2 seconds).
The amount of "50 seconds" I was talking about before is just the multiplier of 12*1 Ctrlr plugin (ok, actually it’s exactly 48). An other reason why it doesn’t depend on "multible Ctrlrs": In Ableton everything works as before (removing 1 plugin: ~0.2 sec – removing 12 plugins: ~ 2 sec).

[atom]

well removing any instance of Ctrlr will take at least 2secs, and yes for each instance you lad it’s another 2 seconds (each instance has it’s own timer) and it is necessary so that the host does not crash after unloading Ctrlr, and that is the Hosts fault not Ctrlr.

[minimalist]

OK – I can’t anymore. It costs me often a way too much energy (like now), that you’ll exept a bug as a bug.
Fault by the host? – No! … on PC I can load 1.000 Ctrlr plugins in Maschine – needed time to close: ONE second
Fault by Mac? – No! … on Mac I can load 10.000 other plugins (not Ctrlr) in Maschine – needed time to close: ONE second
"Fault" by the way Ctrlr works? – No! Before 485 everything worked well. EVEN 485 works on PC (Maschine, Ableton, whatever); on Mac: Just not with Maschine!
Fault by the Lord? – Maybe

Sorry I’ve the feeling I can write what I want – you’ll never exept it. If this bug (yes: bug) will not be solved… I’ll try to get happy with 475 (this nasty CPU monster) – and I’m out.

[atom]

yes but before r485 there was no 2 second delay on Ctrlr close, i know it’s there because i added it i understand that you consider this a bug, i consider this a feature that has to be there.

[minimalist]

But for WHAT is that great feature??? In all release before 485 everything work well! Why to change this?? And why it’s just in Maschine on MAC (EVERYWHERE Ctrlr 485 works PERFECTLY… But not in the combination Mac/Maschine!)?
No – i really don’t need the answer: "because Maschine is a bad host – and Mac is a bad OS".

[Author]

Posts