- This topic has 14 replies, 5 voices, and was last updated 5 years, 6 months ago by
.
-
Posts
-
HI, i’m a new customer with ctrlr, i’m very happy to find a easy way to program my tg77 but i’m completely lost with the tg77 panel, not about the programmation (i mean operator, filter etc…) but with the patch edition, How can i do modify existing patch, or how can i create a new one ?
Regards
Hi all! Is there any way to automate the operator envelopes levels and rates? all the best
There are a lot of parameters that are not visible in the VST parameter automation list.
Is there any way to deal with this?
thanks
a.There are a lot of parameters that are not visible in the VST parameter automation list.
Is there any way to deal with this?
thanks
a.Hi alfonso,
If I understand correctly, you’re talking about modulators that become visible in your host so you can automate them in your host right?
First, the relevant modulators’ “modulatorVstExported” parameters should be set to enabled. I use Ableton, so click ‘Configure’ on Ableton host device and delete if you have stuff there, then move a modulator, it will be exposed on Ableton host device.
I hope this helps.
There are a lot of parameters that are not visible in the VST parameter automation list.
Is there any way to deal with this?
thanks
a.Hi alfonso,
If I understand correctly, you’re talking about modulators that become visible in your host so you can automate them in your host right?
First, the relevant modulators’ “modulatorVstExported” parameters should be set to enabled. I use Ableton, so click ‘Configure’ on Ableton host device and delete if you have stuff there, then move a modulator, it will be exposed on Ableton host device.
I hope this helps.
Hi Mr.ToR,
Thanks for the info.
Yes is exactly what i need to do. To control my TG77 via VST automation to CTRLR. How can i set the relavant modulators to modulatorVstExported?Ok. I got into Panel Edit and all the parameters are set to be exported to VST already. But neither Ableton Live abd Reaper show those parameters.
Maybe a bug?I’ve just solved tuning the .override files to more VST parameters.
Are the 4AFM and Drum Mode modes gonna be implemented?
bestHi all,
as the developing activity on this panel seems to be ceased (am i wrong?) i would like to help completing it.
I’m just starting studing the all CTRL framework and i do have a certain amount of coding skills (mostly C, C++).
I guess LUA is a pretty simple one to learn having some coding experience.
So i have some general CTRL questions and some other panel specific ones.1. CTRL documentations seems limited to the online section on the CTRL site. Is there any documentation of the CTRL API?
2. I wonder how this TG77 panel implement Bulk Request and how all the relevant modulators receive their values from the date received from TG77.
3. I try now to list all the missing features of the panel.
A) Retrieve Patch Name and write and Send a patch name.
B) AFM3 and AFM4 elements
C) Deal with all Multi, Tuning, Program Change Table, System, Pan, Drum Set data.
D) A more structured integrated Librarian to deal with TG77 memory.
E) Eventually work with sample transfer for the AWM elements.Any help from the panel developer and the community?
Thanks and all the best
a.2. I wonder how this TG77 panel implement Bulk Request and how all the relevant modulators receive their values from the date received from TG77.
On all bidirectional panels there is a Lua script e.g. called “midiMessageReceived” attached to the property “called when a panel receives a MIDI message”.
On all bidirectional panels there is a Lua script e.g. called “midiMessageReceived” attached to the property “called when a panel receives a MIDI message”.
Thanks. The thing is that this panel does not update its modulators when receiving data.
At least it seems to me.I looked into the panel. It should update the modulators, everything is there to do it. It was written for an old Ctrlr build. Mainproblem is probably the use of the deprecated “getLuaData” instead of “getData”. If you do a search and replace on all scripts it may work with newer Ctrlr builds.
Alfonso, I and a few others are really excited to try out your TG77 panel improvements! Hope you’re close to being able to post your work. Looking forward to getting inspired with my TG77.
@ryanpg Sorry for the huge delay 🙂 I actually suspended that project because i’ve got and still get other things to do. But i’ll be back on this after summertime. In the meantime i’m studing the user algorythm problem on TG77 and a little LUA 😉
Woo hoo! That’s exciting to hear. Looking forward to your developments. It’d be awesome if you would post your work so far. Things happen in life, and if you decided never to get back to it, it’d be great if others could benefit from your work!
Thanks for replying; glad to hear from you!
Sorry guys, i have to put this project in stand-by….too much music to compose, rehearse, perform, produce, teach, learn etc…But i’ll need to come back to it because i really want to integrate my old TG77 in my production routine. Thanks for the patience (btw…its seems that CTRL development is kinda slowed down a lot in the last year or more?)
- The forum ‘Panels, Components, Macros’ is closed to new topics and replies.