Forum Replies Created
-
Posts
-
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?)
@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 😉
For instance?
panel:getModulatorByName(“ModeSelect”):setModulatorValue(ModeSelect, false, false, false)
often there are false and true values but i don’t know what they are used for.
or
timer:setCallback (2,RestMidCallback)
timer:startTimer(2,1000)where can i find docs about the timer object?
sorry for my stupid questions but my humble opinion is that CTRL would need a better documentation or at least some source for it.
Maybe is somwhere hidden in CTRLR sources?
thanks
Many thanks @dasfaker.
Anyway i see a lot of LUA functions that are not documented in Juce.
Am I wrong?Many thanks @Possemo! But where can i find the docs for all the LUA functions as ‘midiMessageReceived’?
Yeah the TG77 sysex is fairly big. In the present TG77 panel there is the Bulk Request and the sysex sequence is correct (i took a look at the TG77 SysEx manual and check with MidiOX).
Where can i find the docs on how to post the received MIDI bytes in the LUA console?thanks!
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.Hi 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.I’ve just solved tuning the .override files to more VST parameters.
Are the 4AFM and Drum Mode modes gonna be implemented?
bestOk. 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?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?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.
