Forum Replies Created
-
Posts
-
If you are not already getting paid as a computer graphics designer, look into it, seriously.
nice work!hello, making this work with the TG may require some changes to the sysex header code. I’ll see what i can do about making a TG version. hang tight
ahhh, thanks Msep… yet another tidbit for the ever elusive CTRLR manual lol
i think the biggest mystery for new users is how to manipulate the hex code in the midi messages using the xx variable.
then learning the fixed expressions in the value boxes also the system K0 – KF variables. one can achieve alot
just knowing those things. perhaps a quick start guide describing usage of those things included in the zip file would
help many newbs.AWWW come on fozzy, half the fun of using CTRLR is trying to figure out how to use it!!!!
use the force young Jedi!oh wow, another AN1X owner! i’m getting ready to tackle that one too. except im not sure if i want to
fuss with the arpeggeator and step sequencer since i have software plugins that handle those
tasks fine. i’m looking to just create a CTRLR to shape the tone.http://www.retrevo.com/support/Yamaha-D … ag710/t/2/
thats a link to the yamaha dx7ii the keyboard version of the tx802 that shares the same sysex codes.
hehee very cool, was gonna do the same thing with tabs, but well, tabs are kinda crashy still. i hope you dont mind if i use that LUA code someday, could come in handy!
bahhaa sorry filch, i wish i jumped on this sooner….i delt with the same bank/program change mystery with a few of my controllers! good job figuring it out!
Just updated the TX802 panels, they are growing up!…. didnt catch an issue with parameters being reset in the uitogglebuttons with the update to the latest CTRLR.
you can get the 4.0 version of the TX81z here:
FOr the performance panel, you synth needs to be set to DEVICE ID = ALL accessed via
the system setup button on the synth. And Glogal channel 13, try that.Hi, Thanks for the nice comments about my efforts on this project.
Atom has since fixed the problems with the missing image files with
the latest CTRLR version. i still need to update these TX802 panels.
watch for them when i announce them in a new topic. and yes…
the time/rate system yamaha uses for FM synthesis does seem reverse
more is less less is more….. go figure i got used to it.
there is no save function on the panel. you must still use
the store/compare button on the synth to save you edits sorry.
perhaps when CTRLR has a built in librarian.i run into this scenario with the "voice mute" buttons on controllers that require reading the on/off state of the
other voices. the issue at hand is that CTRLR doesnt do realtime midi-in reading for modulator values. someday maybe.buttons now reload as requested in 573! thanks so much for this Sir!!!!
@atom: oh ok…. I did the test you did with a clean "new" panel made in Rev. 557 and it did indeed work right after close/open… i think the problem is with using code from a panel made with 526 is where the problem is. oh well… no problem, i will finish this last panel with the workarounds i made in the absence of working mulit messages.
keep up the fine work Mr. Atom!
i don’t think so, what you are describing would be for the sliders to "memorize" the last
positions they are in when you switch back and forth with the combo select button. Ctrlr does not support
this kind of behavior in the modulators at this time, correct me if im wrong Atom.if the memorizing is not important, you might use a global variable, like k0
make a combo button, assign 0 to it in the "modulator attached to global variable" field, that assigns the xx value to the global variable k0
in the values box, put something like:
ENV1 = 50
ENV2 = 51
ENV3 = 52the values 50 – 51 being the byte in the sysex string that distinguishes the envelopes.
next, make the sliders for the ADSR like so:
attack slider: F0 40 01 33 k0 xx F7
this is just an example message, you would of course use the message that your synth responds to.
good luck!
i’m noticing on this latest update that when you close/open a ctrlr, the buttons now come up with "button" on them.
I’d rather they came up with the first expression in the value box. for example: "on" in the line "on = 1"also, doing a simple test of dropping a slider on an empty panel and making it a multi componenet
still doesnt work right. closing/opening the ctrlr turns the slider to a regular sysex control.midi monitor shows F0 00 F7 being sent instead of the values in the multi list.
