Forum Replies Created
-
Posts
-
OK, thanks! I already wrote it, but I like to repeat myself – because I think it could be interessting. The Ableton issue: In build 342 the v5 AU version already behave like I wrote in my last post… BUT the VST version didn’t. In build 347 BOTH versions (AU and VST) set the "focus"/priority to session view. So this priority issue is something like new in the VST version.
With the "fucus" stuff it would be helpful to know if you’re experienced in Ableton. Ableton Live offers 2 different ways to produce music – the standard linear way: "arrangement view", and the non-linear way: "session view". You’re only able to play ONE of these methods at the same time per track. If you have have a sequence in the arrangement AND the session (in the SAME track), Ableton need to know which of them has priority and set the "focus" to one of these methods. If the sequence in session view is playing – the button "back to arrangement" (transport field) is enabled, to indicate that the arrangement is disabled and the "focus" (priority) is on session view.
… Because it’s only possible to make automations in the arrangement, of course I did automate Ctrlr v5 there. I don’t know why… but if I playback the track with the automation, Ableton sets the priority ("focus")of this track to session view – and the "focus" button (called "back to arrangement") is enabled. So the automation is disabled, because the arrangement is disabled, too.The Maschine issue: If I playback the already recorded automation (of course Ctrlr is automated) and tweak/control at the SAME time (via Maschine) this automated parameter with the mouse or Maschine hardware, Maschine is crashing immediately.
Did you get it what I mean? It’s really not easy for me to explain it better (at least for the moment).
Yeah atom! 347 is a HUGE Mac update again – it feels 10 times more stable than 342 (also more stable than v4), and seems VERY close to become rock solid!
I’ve controlled/automated all versions (VST/AU) in 2 hosts – NI Maschine and Ableton. In ALL versions/combinations the CPU peaks are gone (1-2% constantly!!), no crashes anymore when deleting a plugin or close the hosts – and no problems anymore with disable/enable MIDI ports in the global MIDI device manager! GREAT work! Though there are just a few problems left.Maschine:
The VST/AU versions seems to be identical in terms of automation and crashes. I managed to automate both versions for many minutes (in build 342 this wasn’t possible), but after 10-30 minutes Maschine crashed. Sometimes it needs longer, sometimes not – but this crash appears VERY rarely!
On the other hand when Maschine is automating the VST/AU and I additional control the automated parameter by the mouse – Maschine needs 2-3 seconds and crash immediately. I know it’s a extremely situation, but maybe this could be interessting/help.Ableton:
Also here the VST/AU versions behave same in all terms I’ve tested. In both versions I experienced a strange issue which I already experienced in AU build 342. Do you have Ableton? I remember that I’ve read (a long time ago) that you use an other host/DAW. In Ableton there is a red button in the transport field called something like "back to arrangement". If this button is enabled (red) the "arrangement view" is something like disabled and the main focus is on the "session view". Because the most of automations are only available in "arrangement view" you need to do it there.
OK, this I experienced: I’ve recorded an automation in "arrangement view", it works fine. But if I want to play the recorded automation, the red button enables itself when the automation is played. This means that you’re not able to play the automation, because the main focus is always on the "session view"! Looong explanation of a little thing, but for someone who maybe don’t know Ableton it’s not easy to explain.Summary: It seems for me (as a non programmer) that there are just 2-3 problems left – and Ctrlr v5 is rock solid on the Mac! You can’t imagine how excited I am!
From now on I’m creating my Ctrlr pannels only when it’s hosted.nrhyan, if I understood you right you didn’t tested the "automation bug" with the current version? Or why you don’t have any problems?
Nice, I’m glad to test it with the "gr8" platform!
But I’m not able to unzip the file, an error is appearing.I also thought that it’s a shame about the previous work of v4 (though I ever dreamed about a "modular" tool like v5). BUT on the other hand: Ctrlr v5 is able to deliver almost every tool you need to create your individual plugin – and you absolutely don’t need any programming skills. The potential is endless! Only think how the future could look like: If v5 will offer all planned features and become rock solid on every host and operating software, very soon many musicans will join this project… Think about what will be available in 1-2 years! I think there is no synth without it’s own plugin anymore! The potential from Ctrlr v4, soundtower, sounddiver, rekon, etc.. was depending on the wishes of the developers. Ctrlr v5 is a never ending story!
Hmm, maybe it seems that this are a lot of crashes. But it’s a fact that 342 is the most "stable" v5 version until now (at least when hosted on Mac). As I told Ableton was automating v5 about 20 minutes without a crash. For me 342 succeeded this test – so I was the one who closed Ableton (this time it wasn’t v5
” title=”Wink” /> )What’s about your hackingtosh? It’s still not working, or do you need an original Mac for fixing?
No, also if I disable all MIDI devices there are sometimes CPU peaks about 70%. If I "just" control Ctrlr v5 via Ableton with the mouse – the peaks are not sooo high (about 40%), but if I record/play the automation the peaks are much higher.
In my other host NI Maschine (it’s my goal to host v5 some day there) there aren’t so huge peaks (about 20%) when I control v5 via Maschine just with the mouse. But when I want to record/play the automation Maschine crashes immediately.
The hosts also crashing sometimes when I want to enable/disable MIDI ports in the Ctrlr global MIDI device manager. And they also crash sometimes when I want to delete the Ctrlr VST, or if I quit/close the hosts.In my case it happens on Mac (I think nrhyan, too?). So is it unnecessary to give you closer informations about the crashes – would a bug report help?
Coil, I’m not sure if I understood your problem. Is it that your TX802 doesn’t respond to your keyboard? I’ve tested it aswell (but just 1 minute )and maybe v5 can’t send MIDI note messages (at the moment)? But you can also create a second MIDI track in Logic for MIDI notes.
If you’re a bit experienced in MIDI stuff – v5 isn’t that complicated. Until now I didn’t need the LUA (honestly I also don’t know what this is) and most opperations already work.
– create a new pannel
– by rigtht mouse click choose a component (slider/knob/whatever)
– choose the MIDI channels/ports of your hardware
– type in the right MIDI message which responds to the parameter you want to control… have fun!
” title=”Wink” />"v5 does not support multiple instances"
Really? As I understood it’s not working for Windows – how is it with Mac? And how is it if I use different MIDI ports?
The support of multible v5 instances is also for me very important. There are many reasons why I prefer to have one instance of v5 for each MIDI channel.OK. Does it mean that a bugreport is unnecessary at the moment? Short info: when v5 342 is controlled/automated by the host there are heavy CPU peaks (70-80%) appearing.
Yes, atom! The last update is MUCH more stable than ever! Though there are still some crashes (Mac VST/AU) I’m verry glad to tell you: In a simple testproject I managed to let Ableton automate v5 for about 20 minutes without any crash!!
” title=”Very Happy” /> ” title=”Very Happy” />
As I told 342 is still not 100% stable, but for closer informations I will use the bugtracker. Btw: Because the headline of the bugreport doesn’t fit anymore, maybe it’s better to create a completely new bug report for a better overview?Many thanks!
Thanks atom, Sysex works! From day to day I love v5 more and more. Hope that I can host and automate my Ctrlr projects without crashes soon.
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!
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!
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!
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!
Yes, I already created a bug report about this issue (and I think you’ve made a comment?). The Ctrlr v5 Mac version is only a few days available, so I think there will be some updates from atom soon.
My music computer don’t have internet connection, so I don’t care about the updater. The latest versions you can find here: http://sourceforge.net/projects/ctrlrv4/files/
I think 307 is the latest, but wait a bit I’m sure that there are comming more.
” title=”Razz” /> !