Forum Replies Created
-
Posts
-
OK, thanks for this update of your present situation! I was indeed wondering if there was something bad going on. Hope you like your new job better then your previous one! To be able to code at work seems to me a very nice “feature” to have 😉 Hope also you will find now some time to test the TX7 (as you promised a while ago) and even (yes I keep asking…) to put me on the right track considering the specific problems I have with the panel. Thanks anyway for developing CTRLR further.
Today (May 20) I uploaded the latest update for this panel (v0.92 beta). Wrong settings for some modulators were corrected and I added a new block: function parameter change. These functions can sometimes be useful.
OK, you’re right! I will change those values. Thanks for noticing and sorry for any inconvenience caused by this 🙂
I think I misunderstood your post. By “panel” you mean the LCD-screen of the TX7 itself, not my TX7 CTRLR panel… But anyway, those values should have a range from 0 to 15, not 0 to 4, according to the manual.
Ah, thanks! I will adjust the low/high value of this modulator. (You can do it yourself also, of course.)
I’m not sure if I understand your question… Initially I thought the numbers 1,2, 3 and 4 (both for rate and level) were the same as ADSR (attack = 1, decay = 2 etc.), but when those modulators were receiving their value, there was some weird behavior, so I took the easy way and labeled them according to the manual. In a way the modulators behave almost like ADSR, but not entirely ;-). Maybe it’s a typical Yamaha thing, I don’t know. Somebody else can shed a light? (I just bought the TX7 a couple of months ago and haven’t spend much time playing with the thing. Like you I still have to learn the ins and outs of FM synthesis.)
If you read the text I have added for the panel in the panel upload section you’ll see that’s what my experience is also. I really don’t know why this happens, because I literally assign each incoming midi parameter value to the appropriate modulator. If what you notice – the settings one can actually adjust from the panel of the TX7 are not getting the right value – is true, then I know where to look. I will dive deeper into this. Thanks and please test this panel some more.
So for all of you eagerly 🙂 awaiting this panel, I have just uploaded a beta version. I hope with the help of all interested forum members this will become a full grown professional editor/controller for the TX7!
@msepsis: I assume you solved this “problem”, but for other forum members with the same problem I will post (what I think is) the solution: setting the right parameters for the setModulatorValue statement. (Of course you have to use Lua.)
The Ctrlr source tells me:
setModulatorValue(const int newValue, bool vst, bool midi, bool ui)
Setting the value for ‘midi’ to false did the trick for me. I assume setting the value for ‘vst’ to false means also not sending the value to vst. The meaning of the value for ‘ui’ is not clear for me, I saw no change in behavior.
Before doing the upload I checked the manual once again and found still a few loose ends which I only can solve with the device connected (and sending sysex messages). So please wait a bit longer. Thanks anyway for the offer to test this panel!
I support this request. Would be also very convenient the other way around: one has developed (quickly) a panel using the standard sliders and knobs and want to replace them all afterwards with knobs and sliders made with Knobman…
The panel is finished (theoretically), but I want to test it extensively with the TX7 connected before releasing it. To do this I must be back home, which is somewhere in the beginning of May. So until then!
I love cats too! What a lovely sight your cat and all this warm gear. Is he/she by any chance a Somali breed? (I wished my sisters came up with such a present, but they have not the faintest idea of what I’m doing with MIDI and music…)
Well, after all not that simple… Is there any restriction on the lenght of the message in the ‘sendMidiMessagNow’ command, because I get irregular behaviour when sending a large message (about 162 bytes). Irregular: I ‘pick out’ one byte (e.g. byte 9) in the receive midi script, but the console output shows sometimes 3 bytes and sometimes a lot more with the value zero when I change the byte number to a higher number…
No need to reply, I figured it out. As usually, very simple ‘sendMidiMessageNow({putheremessagedatainhex})’.
Loopbe1 works like a charm! Thanks again!
So I’m able to send midi (sysex) from one panel to another, BUT now I want to send (using a button on the sending panel) voice data which is a message containing 155 bytes of data. I tried the ‘multi message list’ (copied the data from clipboard), also tried the ‘sysex formule’ property, but got not the desired result. So how do I send this ‘large’ message using a button or, if needed, using Lua?
OK, thanks for the link! MIDI YOKE on my computer was ‘recognized’ by MIDI-OX, showing input and output ports, but I saw no possibility to connect Ctrlr to one of these ports. But maybe I need to dig deeper into this. Anyway, I will try Loopbe first. Thanks again.
