Forum Replies Created
Hi Atom, now you have fixed the verification/activation for the forums again, we can log on again, thank you and warm thought to you for the detox period.
OK, I am working on voice editor panel only. There is another guy, Josef/Seppmeile, who working on registrations and to simplify programming on the HS. You find him in the yahoo group Hsowners.
Hi, yes, I have one under development, what do you use your HS8 for?
You are welcone, it feels good to be able to help 🙂
Thanks Possemo, the Yamaha Electone instruments use channel 16 for all control data, I didn’t think of that.
Yes, you just use an uislider, select the midiMessageType to be “pitchWheel” and do not write anything in the midiMessageMultiList box.
This is what it transmits on my system:
[22:07:34:000795]: RAW:[ef 0f 2b] [22:07:34:000819]: RAW:[ef 60 26] [22:07:34:000836]: RAW:[ef 49 24] [22:07:34:000851]: RAW:[ef 31 22] [22:07:34:000871]: RAW:[ef 1a 20] [22:07:34:000891]: RAW:[ef 02 1e] [22:07:34:000932]: RAW:[ef 6b 1b] [22:07:34:000962]: RAW:[ef 54 19] [22:07:34:000993]: RAW:[ef 3c 17] [22:07:35:000005]: RAW:[ef 25 15] [22:07:35:000017]: RAW:[ef 0d 13] [22:07:35:000033]: RAW:[ef 5e 0e] [22:07:35:000045]: RAW:[ef 2f 0a] [22:07:35:000063]: RAW:[ef 00 06] [22:07:35:000075]: RAW:[ef 69 03] [22:07:35:000088]: RAW:[ef 52 01] [22:07:35:000100]: RAW:[ef 00 00] [22:07:36:000425]: RAW:[ef 7f 3f]
getBitRange is working again, Ctrlr -5.3.86, thanks for fast fix!
Thank you Atom, I will wait for that patch, rather than making a workaround in the code, I believe using getBitRange and MemoryBlock is the cleanest way to get data from a .syx file.
I just changed all my o’s and p’s to l and m and started testing, l and m’s were overwriting again, only k worked, then I tried going higher up on the k’s, global k10, and global k3f and these worked perfectly, based on this I assume the entire range of 64 globals is working in the k range, it is easier to handle too, since the global.kx number is just the hex format of the decimal number, very nice and clean in my opinion. Now I will go ahead and apply these all over the panel, thank you for implementing this into the midi message box, it opens for a lot of possibilities.
Great, k,l,m,n! that explains a lot! I was using k,o,p,n that idea I got from the edit sysexformula selection way back and it stuck to my mind.
I spent some more time experimenting and strangely, there is some inconsistency, sometimes the getBitRangeAsInt gets value, sometimes nothing, once when I was trying to use ka it consistently returned me the value of k0, maybe I am making it worse when experimenting giving the variables different names?
Are we talking naming them like this?
0 1 2 3... 9 10 11 12.. ..15 16 17 18.... k0 k1 k2 k3.. k9 ka kb kc.. ..ke kf o0 o1.....
or continuing counting on k´s:
k0 k1… .. k29 k30 k31… ?
I was trying both of these but soon it started doing strange behavior, the first clue that it is going bad is the uiLabel box stops responding to the changes.
Go to start, type %appdata% it will take you to the appdata folder, there you find ctrlr configuration settings which you can try to delete, it helped me once my installation got corrupt.
I just tried this out in the 5.3.82 nightly, now it is only the first variable (k0) that behaves correctly and consequent, the other (k1 and up) do not.
Well i did a small fix, now anything k23 will be interpreted correctly. Just remember that the number after k is a hex number so 23 is decimal 35 f is 16 etc.
Excellent, I will test it on the next nightly win build, no hurry. Thank you for the fast response.
Thank you atom, I have allocated 53 global variables so far, one per each byte that shares modulators.
the above solves this case I posted with setting a single bit, unfortunately it does not work with range of bits, which I do like this and it works fine:
setGlobal (7, setBitRangeAsInt (global.k7, 4, 3, modulatorValue))
what the global.k7 does is get the actual value of the variable, and then does the bit set job. This is equivalent to:
setGlobal (7, setBitRangeAsInt (getBitRangeAsInt(global.k7, 0, 8), 4, 3, modulatorValue))
(I verified this to give exactly the same results)
Again this is limited to the range k0 to k9, if I do a getBitRangeAsInt on anything higher (ka, kb, o0, o1, etc., apparently it does not return the value correctly.
See the attached panel for demonstration.
Thanks for the reply dasfaker, let me make myself more clear:
k0, k1.. up to k9 are working fine, but then how do we continue counting on through the 64 global variables of the panel? ka? kA? k10? none of these are seem to work correctly.
Thank you for clarifying Zeoka, I will check this out, sorry for revoking an old thread, but I was just hoping I could use this for a quick experiment.
Is this still valid?
I get this error message:
attempt to index global ‘midi’ (a nil value)
Giving the first free VST index is a great idea, I remember this causing me headaches for a while until I found out that the copy got the same VST index as the original.