Forum Replies Created
-
AuthorPosts
-
Stick to CC for the parameters that are available that way, nrpn is not realtime so you will get ‘erratic’ behaviour like parameters jumping to a value instead of gradually moving towards the desired value. Or in the worst case scenario you flood the buffer of the device’s midi interface and it locks up or chokes until it catches up.
Thanks drsteve!
Yeah i also was thinking about the midi possibilities of html5 and from the docs i have read it is certainly viable, but i know next to no javascript and that will be the way to do it (i think) . Maybe use node.js as framework or something like that…
But that will be a whole other can of worms than Ctrlr!Hi midiquestions,
I have just started again because i finally have time again.
Will be a while for the next ‘release’ but at least its not dead anymore 😉Hi Zeoka, good to see you’re still around 😉
Thanks for confirming it is not my setup.
What version works for you? I cannot have Lua being gutted because the panel i work on heavily relies on it.Fwiw I switched to using git on a headless machine to store all my work, and i spotted that the panels i opened were also modified. Looking into them revealed the same bug – all Lua gone.
But thanks to git i can restore easily -phew 🙂
Btw i strongly recommend all here to use git, besides being a headache most of the time it actually is a lifesaver.That panel was made with a deprecated version of Ctrlr; to make it work with the current Ctrlr architecture the scripts need to be modified.
I have no idea how much of a workover this panel will need, but it is possible.
Do you you mean making a panel without modulators that can transform the input?
This is possible, you can make the midiReceived script catch all incoming data and assign functionality using if-then blocks.As for making it a “simple” Lua script, it depends on what you intend to make it do. Lua syntax & structure in itself is very straightforward and relatively easy to learn, even if you have never scripted/programmed before.
Hang in there Atom!
I’ve been looking into/playing around with this component; i still need to study it further but at first glance it works for me. I have adapted part of the D-20 pitch env and it did what i expected it to do 🙂
I will now try to make a custom env using your framework and see how far i get without hitting a wall.What i found until now (using Ctrlr 1547):
The DW-8000 modulators do not seem to be linking to the env component, changing values with the modulators does not update the component & vice-versa. I tried tracking down what causes this but my (not so thourough) debugging has not yet proved succesful.If/when i find more buggy/unexpected behaviour i will post it here.
Very nice work!
Very cool stuff, i will give it a spin this weekend.
Afaik there is no way to make the alpha juno’s transmit individual patch data, only full dumps that can be initiated from the unit itself.
See http://members.iquest.net/~twilight/mks_tip3.html for a dumping how-to.
- This reply was modified 10 years, 5 months ago by Hecticcc.
Please do Msepsis,
Iirc your implementation has click/drag functionality on the nodes & that is something i would love to study. Mine is only a graphical representation atm, which is also nice but adding click/drag would be awesome.
I see how that can complicate things.
Would it be possible to make a point have it’s x and/or y to be “locked” somehow, and make “unlocked” points’ movement scale to these positions?Easier said than done though….especially if you want to minimize Lua usage to set it up..
If you set the content to “” before assigning the actual values for uiFixedSliderContent it resets the value to the minimum.
You can use a variable to store the value temporarily and use that one to set the modulator’s value correctly.Just my 2 cents but maybe Ctrlr could have two different kinds of envelopes?
-One simple one for the regular ADSR types with fixed amount of control points.
-One for the exotic ones, that has the option to add control points & can add the required parameter property fields for each point to itself.Also, see attachment for more envelope exotism 😉
Attachments:
You must be logged in to view attached files.If i understand correctly you have modulators that need different value mappings for a selected fx type?
You can try resetting the value content of the modulators before assigning new ranges/values.
IE setting the propery to an empty string (so the old values go away) before you assign the actual data it should hold (for the selected fx-type in your case).
This happens very fast, you don’t even see it glitching 😉I don’t know how far Atom is with the program manager but this is what it will be able to do afaik. You can also “roll your own” using Lua, but this is a quite large task, especially if you did not design the panel yourself and/or have no scripting/programming experience.
But absolutely possible if you don’t mind putting some time and effort into it.
Yeah that should work, but for some reason sometimes it fails for me. That’s why i use a custom variable just to be sure.
Read up here for info on this:
ctrlr.org/forums/topic/preventing-script-from-running-at-panel-load/- This reply was modified 10 years, 6 months ago by Hecticcc.
I suggest you take a look at the amt8 panel i made, it is in the panels section.
All switches are used to set specific bits in 16 different bytes, those are then sent to a method that makes and transmits the midimessage.
Thanks Atom 🙂
-
AuthorPosts