I made retuning of neopan’s Yamaha TX81Z definition
i have got rid of breathcontrol parameters (for space economy)
global transpose and operators detune parameters become bipolar
more readable labels
added Delay and Pan effects controls (can’t figure out how to add Chord effect though)
more useful defaults for envelopes and operators (OP1 is audible by default, rest are muted; every OP has Ratio 1.00 displayed as 4)
I have few feature requests:
Meta modifier — has to be, in some extent, Hydra for Guru framework. You can bind, with specified ranges, group of already declared parameters (or only one) to newly created control. Corresponding controls for this parameters should update their states with meta modifier. Meta modifiers could be grouped.
Rotary knobs. I believe they can be composed into something like this:
And GURU is still simple
Sweeeeet! It works perfectly with the Xiosynth using the A-Station preset! This is great, it is so hard to program this synth from the board, but this extension makes it an easy cake.
Nice to see lots of activity. I’ve been away doing other stuff.
So, Trash80, just go a head make what you think would work fine for you and other definitions. When I started this I knew alsmotst nothing about MIDI, so what’s there is pretty much what’s there, no thought out bit handling and stuff.
The “nn” stuff for the sysex template is just hard-coded placeholders, so if you think other definitions can use the things you’re adding just go ahead add your placeholders and add handling in send_sysex in the midi class maybe? Or if you have a better idea…
Hi there! Great tool. I’m trying to write a definition for the Korg Radias, and maybe, if I succeed for som other synths.
I have A bit trouble figuring out how my Sysex template should look like.
I found this in the Radias Manual:
System exclusive messages
RADIAS format
F0: Exclusive status
42: Korg ID
3n: [n=0–F] global MIDI channel
72: RADIAS model ID
ff: function ID (type of message)
| |
F7: End of exclusive
Universal system exclusive
Certain types of system exclusive messages are defined
for public use, and these are called Universal System Exclusive
messages.
Of these universal system exclusive messages, the RADIAS
responds to master volume and master fine tuning.
Master volume [F0, 7F, nn, 04, 01, vv, mm, F7]
(vv: lower byte of value, mm: upper byte of value. Volume
at maximum when mm,vv=7F, 7F. Volume at zero
when mm, vv=00,00)
The overall volume of the entire RADIAS is adjusted
when this master volume message is received.
3 Post in a row />/>
Since I had a MS2000R laying around I figured I would make a def for that one too. So here it is. view grymmjack’s post some further down the road. He got it covered even better.
Can someone help me? with this? should be quite simple, but I can’t get my head around it.
I now have this:
sysex_message_template = {0xf0, 0x43, 0x11, 0x00, “nn”, “vv”, 0xf7},
I was wondering is it even worth attempting a kawai k5000s? If someone could have a glance at the sysex implementation and tell me if it’s possible I’d appreciate it.
Maybe there could be a “learn” function implemented? I have a various different sysex software editors for my hardware that work, but some are on obsolete operation systems and it’d just be nice to have them all in one place with a nice GUI.
i’ve noticed weird behavior when GURU sends data to tx81z:
when i turn on my tx81z it starts with last used patch. then i start GURU and GURU sends patch data to tx81z. but! some parameters are updated correctly, and some are simply not updated: for example GURU shows that OP1’s attack rate is fast, but i hear that sound has long attack, like in previous patch exactly. all my saved patches sound really different every time
maybe i should specify sysex_message_template for every parameter?
Hmm, i made a hasty conclusion about proper functioning. It works way better than previous versions, but it still has quirks when i switch from one patch to another.
Hi xrxs, since you are the only one alive in this topic. Have you any Idea how my midi template should be?
I discribed it in the post before your posts.
do you have a full sysex implementation specs for KORG Radias?
Then, why do you specified 42: Korg ID as 43 here: sysex_message_template = {0xf0, 0x43, 0x11, 0x00, “nn”, “vv”, 0xf7} ?
That’s right, I didn’t figure that out,yet.(hence my earlier posts)
It only covers the hardware knobs and buttons ATM.
So if you like to expand on it, be my guest
I could use it to complete the sysex parameters on my Korg Radias which is also quite similar.
/>/>
/>
/>
/>.