Home › Forums › General › Using Ctrlr › cubase unknown parameters
- This topic has 24 replies, 2 voices, and was last updated 10 years, 7 months ago by spinacem.
-
AuthorPosts
-
August 27, 2013 at 9:57 pm #12534
Hi all!
I have a problem using ctrlr on cubase 7…it doesn’t show the name of the parameters. It calls everything unknown parameter #, instead of filtCutoff, filtResonance etc..
I don’t have this problem on ableton live. Someone else is experiencing the same issue on cubase? Any solution?
thanks in advance
August 27, 2013 at 10:37 pm #12536What OS what Ctrlr build, what panel ?
August 27, 2013 at 11:00 pm #12539Hi atom, i’ve tried with different builds (1535, 1500, 1441).
I am on windows 7 64 bit, and i’ve tried with minitaur panel and little phatty panel.
August 28, 2013 at 12:14 am #12542I just tested the x64 build in Reaper (the only 64bit host i have) and seems to work, can you try Reaper too and see what results you get, i can’t get Cubase (i don’t have it) and i really don’t want a pirated version.
August 28, 2013 at 12:28 am #12545I don’t have reaper, i am using ableton live 9 64 bit and cubase 7 64 bit. On ableton i get properly the name of the parameters, but in cubase i get ‘unknown parameter #”….i don’t know why. It’s only me or it’s cubase?
August 28, 2013 at 12:40 am #12547I’ll try to find a version of Cubase x64 somewhere and see what i can do.
August 28, 2013 at 12:58 am #12549Thank you very much atom!
August 28, 2013 at 7:24 pm #12597Yeah i tried, there is no way to get Cubase 7 to run without the eLicenser, and i don’t have one, so i can’t help, sorry. I’ll look on other hosts if i get the same problem, maybe i’ll be (un)lucky.
August 29, 2013 at 12:09 am #12613Argh! Thanks anyway atom! Maybe someone in this forum use ctrlr on cubase?
August 29, 2013 at 12:14 am #12614Try the new nightly i uploaded today, maybe it will help i made some fixes (i found some issues in Ableton x64).
August 29, 2013 at 12:21 am #12617Thanks i will try. One thing i would ask you: i found that if i save a panel with midi input and midi output device connected, when i re-open the panel it doesn’t remember the midi device (so i need to re-choose it every time) and also the knobs position are not stored. Am i doing something wrong?
August 29, 2013 at 12:24 am #12618The panel state (knobs etc.) are saved with the program in your host (cubase, live) so if you save the project and re-open it, Ctrlr should set the knobs to saved positions, if that doesn’t happen, then it might be a bug, please let me know about that, but please try the latest nightly first.
August 29, 2013 at 12:38 am #12619I am trying it now on ableton. Something strange, i can’t add parameters automation using configure button plugin. Also the knob positions are not stored when re-open the project.
August 29, 2013 at 12:43 am #12620I just opened the latest nightly x64 bit VST in Live x64, new panel, added two sliders, clicked configure, they show up as parameters with names, it looks ok.
I’m using Live 9.0.5Maybe you can give me more details, what Live version are you using, what panel, what OS etc. so i can reproduce the situation.
August 29, 2013 at 12:48 am #12621Also make sure to open Help->About and see all the versions in there.
August 29, 2013 at 12:58 am #12622Yes if i do a new panel i can add parameters. A strange thing: when i add the parameters with configure, using the ableton sliders i get random values at minimum position (like 2,1,5 etc) and random values at maximum position (like 122,125 etc). In the ctrlr panel it gets correctly from 0 to 127.
I am on ableton 9.0.4
August 29, 2013 at 1:02 am #12624This might be a floating point rounding issue. I’ll look into that tomorrow, i already took my sleeping drugs, it’s not a good idea for me to code under influence 🙂
August 29, 2013 at 1:06 am #12625Of course man! See ya!
August 29, 2013 at 10:19 pm #12679build 1543
Tested on fruity loops: working fine.
On ableton works but there are problems on the values displayed by the ableton sliders (configure).
ON cubase there are no names of the parameters (cubase shows them as undefined 0, undefined 1, undefined 3, etc…). Very very annoying. Any chance to get a fix for this issue on cubase?
August 29, 2013 at 11:14 pm #12683Yeah i was doing some work today and found some more stuff within the plugin hosting code. I made some fixes and the new build i hope to post today should take care of that (see the changelog for details)
-
AuthorPosts
- The forum ‘Using Ctrlr’ is closed to new topics and replies.