MAC builds with v5

[atom]

Well i fixed the plugin bug in v5 that caused Ctrlr v5 to crash the host but this is only valid for VST, i can’t figure out why the AU is still crashing, i’m a bit tired of working with that AU stuff.
I have decided to spend one more day trying to figure out what’s wrong but if i won’t be able to, i’ll drop AU support for now (AU does not support MIDI I/O anyway). It’s an awful format
forged by a very bad company.

However the new build should work on MAC in the VST version.

[minimalist]

Yeah, I don’t like the AU format aswell – it’s incompatible and useless in compare to VST. The hosts I’m using can handle both formats (VST & AU), so I don’t care a lot… But for Logic users this could be very bad news.
But maybe this idea could help some AU addicted ” title=”Very Happy” /> users: You could use a AU plugin inside your host which can hosts other plugins inside itself. Something like NI Kore 2. Load this in Logic as an AU and load Ctrlr v5 inside (i.g.) Kore2 as a VST. So you’re still able to load [b:3310eob1]any[/b:3310eob1] VST, though your host normally couldn’t handle them…

On the other hand I’ve tried out the latest Mac version (VST and Standalone build 320)…. And the crashing problem still stays! Now [b:3310eob1]both[/b:3310eob1] versions (Standalone and VST) are crashing immediately when you want to open them. So, until now the most "stable" version for Mac was build 301. Sorry for the moment it seems that the Mac versions are more unstable than ever. I’ll make a bug report (with crashlog) soon.

I know it seems that the Mac builds are not easy to get stable… But please don’t give up the hope with Mac at all!

[atom]

allright, well i tried to get it working, my advice is try to delete the Ctrlr directory in your home folder in the Library/Preferences folder, this can be causing Ctrlr to crash, if that won’t help… i’ll sit to the damn OSX tomorrow after work and see what else i can cook up.

i hate that os, really.

[minimalist]

Hmm, don’t know if I’ve deleted the right folder. But I did it here: Home/Library/Preferences/Ctrlr <- this folder I’ve deleted (and other stuff which was related to Ctrlr (even the v4 folders). But it didn’t help anything.

I know these days Mac politics aren’t very acceptable, but in the past the Mac did become a very stable and solid equipment in many studios. So it would be very sadly if this users from the past couldn’t get the very great enjoyment from v5!

If you need any help (don’t know which kind of for a non programmer like me) please tell!

[atom]

i’ll work on it, just need to change the CPU in my hackintosh and get some decent remote desktop server running. it’s hard to work on two computers and my hackintosh is only a core2duo 2.13ghz. Ctrlr v4 currently builds a few minutes so it’s annoying. I’m doing a revision 323 maybe it will be better, no promises.

[Coil]

"atom":yd46avpo wrote:

i’m a bit tired of working with that AU stuff.
I have decided to spend one more day trying to figure out what’s wrong but if i won’t be able to, i’ll drop AU support for now [/quote:yd46avpo]

sad news

[minimalist]

I’ve tried out the new build (325) and it works more stable than before! It’s possible again to open the standalone version without crashes.

But the VST is still crashing Ableton if I want to open it (the crash needs some seconds). When hosting b325 in NI Maschine there are no crashes until… I want to control Ctrlr’s parameters by the hardware (or make automations) – b325 is also crashing this host. I think the last Mac fix was in the right direction.

Coil, I can feel with you!

[atom]

please try the latest build, i hope that the bugs are removed and Ctrlr should load and run in both VST/AU and Standalone. Let me know if it doesn’t. I changed the binary type to Universal.

[minimalist]

Thanks for your effort atom! I tried out all versions and no one is crashing anymore when you want to open them, so it’s much better than before. But the VST/AU version is still crashing the DAW when the host wants to control Ctrlr v5. I eperienced some more details and made some crashlogs, I’l do that in the bugreport. Nice that you’re on to this issue – v5 really rocks!

[atom]

i’ll try to crunch the automation stuff tomorrow.

[soatteprorp]

+1

[Author]

Posts