Forum Replies Created
-
Posts
-
Hi zeoka,
yes I asked Atom about the Menu hiding and how to export a restricted instance while the Menu is hidden and he is working on a solution for that.
A demo panel showcasing the midi devices access will follow too.
Cheers!Dude, was it sarcasm or something?
Please keep it to yourself, Atom is doing all this hard work developing CTRLR for 3 platforms all for free and in his own free time!
Show the man some respect or switch to PC if you are in such need to select multiple files for funk’s sake!
Instead of “I need…” you should ask “Haw could I help and contribute?”.
——
Sorry for letting some steam out!
Usually I sit still but somehow I needed to speak up this time.
——
Don’t take it too personal, this is a general remark to all the users out there forgetting sometimes how hard it is to maintain a project like this over few years and doing all that just for a pure satisfaction.
Atom – you rule!
Peace!Thank You so much Atom,
Hiding the Menu is something I was waiting for!
Have a nice day!Yes, this is all true and I had it already all working alright but not anymore – that’s the mystery.
I’m using loopMIDI to connect virtual midi cable between Ctrlr and Cubase and since I have created 2 ports – No.1 for CtrlOut>>CubaseIN and No.2 for CubaseOut>>CtrlrIn I never had problems with MIDI loops / MIDI feedbacks.What I do here is for ex. assign a CC#100 to a slider in Ctrlr and use it to drive the Volume slider of a chosen track inside Cubase. All I need is a visual feedback on my Ctrlr slider when I play back my session with all the automation lanes in Cubase. I checked with Midi Quest and I see Cubase sending CC#100 back to Ctrlr on the right MIDI port etc. It is just not showing up in Ctrlr anymore.
Same goes for other buttons, leds and sliders that need to change state or value if deselected or changed inside Cubase.
Tomorrow I’ll try on my laptop with some older builds and see if that changes anything.
Thanks for your feedback Puppeteer!
Cheers!OK so I did few tests with Midi and also assigning a VST controller and it is still no luck on the way back into Ctrlr using Ctrlr as a standalone BUT it is working properly if I do the same with an exported VST instance of Ctrlr inside Cubase. The In/Out midi connection is the same in both cases but only the VST version of my panel is reacting to the incoming data (and that makes me at least a bit happier since VST will be the goal for me here).
However I’m still wondering what can be the cause here, I’m sure it was working with the standalone too and I could get direct feedback while working on my panel.
Thanx!Thank You das, works like a charm!
I appreciate it very much!
Have a great day.Oh, yes sure,
I’m copy – pasting here on my iPad from the top of my head but your version looks much better i was totally missing the “function timer Callback0” and Callback1 in my script as I can recall!
Thank You das, I’ll try it as soon as I get home!
Cheers!yes, something like this:
— Called when a modulator value changes
— @mod http://ctrlr.org/api/class_ctrlr_modulator.html
— @value new numeric value of the modulator
Trigger = function(–[[ CtrlrModulator –]] mod, –[[ number –]] value)
ret1 = panel:getModulatorByName(“pB001”)
ret1:setValue (1, true)
———————————————–
— /// timer:setCallback (0, timerCallback)
— /// timer:startTimer(0,100)
— /// timer:setCallback (0, timerCallback)
———————————————-
ret2 = panel:getModulatorByName(“pB002”)
ret2:setValue (1, true)— // timer:stopTimer(0)
————————————————–
— /// timer:setCallback (1, timerCallback)
— /// timer:startTimer(1,200)
— /// timer:setCallback (1, timerCallback)
————————————————–ret3 = panel:getModulatorByName(“pB003”)
ret3:setValue (1, true)— // timer:stopTimer(1)
end
Yes, it must be something wrong with your .panel
Crashes on opening.
Cheers!Thanks das,
but all I get doing so is some text formatted properly mixed with some gibberish characters (notepad, wordpad, word) so I can’t really see it as a code that will work in the panel.
Andy ideas what to use to open it or how to import it directly into the panel?
Thanx!Hi Puppeteer,
I think I am that person who asked Atom to introduce the option to block the resizing in VST. The main reason for that is simple – I don’t want my clients to play with the size. I’m sorry to hear this is messing stuff on your end and I hope we will find a solution for that.
Cheers!
