- This topic has 20 replies, 3 voices, and was last updated 13 years ago by
.
-
Posts
-
I just uploaded this build, could those of you with MACs give it a try and let me know if it behaves better, there are some new features too for windows
– global variables as SysEx modifiers (k0-kf)
– FixedSlider UI component (behaves like a combo but is a slider with a displayed value)
– some other fixesFor my first time I was able to load the VST in Live without it crashing! I was even able to open a panel and send values to my Tetr4. That felt fucking great.. Most of the components were already in the VST track. The buttons and lists/combos? werent and upon trying to bring them into the VST track in configure mode, Live froze. Just thought I’d drop this note, I’m gonna get back to do some more testing and I’ll probably return here with some logs. This is a HUGE improvement tho. fun fun
” title=”Razz” />after loading the second time everything seemed to be functioning well and I had no crashes in the fifteen or so minutes testing my panel. I had trouble adding your NRPN preset to a Multi slider, so right now I’m going to go back to standalone to create a panel for Tetr4’s sequencer. Us Tetr4 and Mopho users could really help each other save time and have fun by sharing any work we’ve done on panels. So.. if someone has a panel for Tetr4’s sequencer, now would be a good time to share
” title=”Smile” /> . I will happily do the share the easy but somewhat time consuming panels I am able to do(these would include things like panels complete with all of Tetra’s NRPN program parameters). ” title=”Razz” /> Things like sysex parameter dumps I have not tried setting up components for and could probably use some help.Some time yesterday I tried but could not log on to DeviceDB. I’ll try to give it another shot
deviceDB does not work yet, have a look at the Todo list, it’s all there
awesome. this thing that is going on between panels is really getting in the way for me. I reassigned the VST index for all the components on these two panels I am trying to successfully use in Live, but that isnt solving it. The problem is when I switch from one panel to the other in the VST window, there is no corresponding change or response in the plugin track viewer in ableton. So, no additional controls are able to be "configured" in ableton’s plugin viewer. What happens is each control is mapped to components in BOTH panels.
In v4 I was able to "configure" a seemingly unlimited amount of controls in abletons plug in window(well prob 128), but tonight AI keep on hitting a dead end. This happened to me Reaktor and I’d always have to change/compress the device ID’s. That’s why my first thought was to change the VST index, to no avail however.
I’m sure there are more important things youre trying to tackle with v5 right now. I can try and take a break from bombing you with bug reports. All in all, v5 for Mac has seen so much improvement in the last 48 hours. I’ll try downloading 343. currently the upgrade link/button in standalone doesnt seem to do anything.
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!
well i know there might be some automation problems, i’m still working on that.
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.
I just notices when a ctrlr v5 VST track is opened in Ableton it already has 32 controls, with or without a panel opened. I thought this was odd. 32 is the max amount of configured controls ive been able to add into a vst track so far, and in my experience using other vsts there arent any controls the plugin track viewer if no device is open in the vst. hmph.
” title=”Neutral” />"minimalist":3ft9sitv wrote:Short info: when v5 342 is controlled/automated by the host there are heavy CPU peaks (70-80%) appearing.[/quote:3ft9sitv]yup.
yes the 32 limit is hard-coded, but i will change that, however i need to make it stable enough to change it.
You have to understand that VST and AU do not support changing the number of parameters exported to the host, i went around that limitation by exporting a fixed number of parameters and managing them internaly (i did 32 cause it was simpler to debug). Ofcourse i can export much more, but this will cause other problems. It’s not possible to determine how many parameters a Ctrlr instance will have, it’s a bit complicated. I will increase this number and fix the VST parameter handling (there is a bug report about this and multiple panels). Please remember v5 is still alpha and i need to fix a lot of stuff before it’s ready for production use, i’m aware of that.
"nrhyan":2dkutz5x wrote:"minimalist":2dkutz5x wrote:Short info: when v5 342 is controlled/automated by the host there are heavy CPU peaks (70-80%) appearing.[/quote:2dkutz5x]yup.[/quote:2dkutz5x]
is this on the Mac Windows or Linux ?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?
for now no, i need to sit down to the actual mac (not via RDP) and tweak this around, my tests were just not enough i think. On windows the max peak i got is 7% when i was going crazy on the mouse.
However could you tell me if the parameter you are changing is sending out MIDI messages to the hardware port in the Ctrlr (does the panel have a MIDI Output device set), and if the peak is there
if you disable the MIDI device for the panel.(osx 10.6.7)
The paramter being changed is sending MIDI to the hardware port. When I disabled the device I still saw CPU spikes. Mine aren;t quite as bad as Minimalist’s. Typically 13-28%
Let me know if you want any more info.
"atom":xkbxwsam wrote:yes the 32 limit is hard-coded, but i will change that, however i need to make it stable enough to change it.You have to understand that VST and AU do not support changing the number of parameters exported to the host, i went around that limitation by exporting a fixed number of parameters and managing them internaly (i did 32 cause it was simpler to debug). Ofcourse i can export much more, but this will cause other problems. It’s not possible to determine how many parameters a Ctrlr instance will have, it’s a bit complicated. I will increase this number and fix the VST parameter handling (there is a bug report about this and multiple panels). Please remember v5 is still alpha and i need to fix a lot of stuff before it’s ready for production use, i’m aware of that.[/quote:xkbxwsam]
I do, I do! Atom, you are the shit! I’m just along for the ride, having fun and trying to help. I don’t know how many DSI owner’s there are out there, but once v5 is up and running, which I have faith will happen, it’s gonna help a lot of them out and likely help create a lot more of them. its da trufth
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.That’s a lot of crashes … 20% is a giant cpu usage for Ctrlr, anything above 5% is too much, i’ll have a look but like i wrote i need to sit on the real mac to do that. I’m fixing some VST parameter automation now, maybe i’ll find some more problems while doing that.
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?
- The forum ‘News and releases’ is closed to new topics and replies.