Forum Replies Created
-
AuthorPosts
-
I figured it out.
Just had to find the include images and re-include them again.
Looks like the ubutton has a unlatched mode now..
I’ve been messing around with it and it looks like it works as I requested except there is a little “General” window that pops up next to the mouse when I Right Click the button. It wont go away until click the panel somewhere a few times.
Any idea on removing it?
was there a change to the nightly for the pads?
I tried a recent nightly, but when I tried to load my panels, it was all efff’d up!
Knobs were missing, shifted around… seems the includes were all gone, wouldnt load.
So I reverted to what I was using and it returned to normal.
I have 5.1.0 1137.
Is the latest revision incompatible with the one I’m using now?
can you make it so that a right click will cause it to latch and a left click will be a momentary switch like a keyboard ?
and right clicking again while it is latched will cause it to unlatchThanks Atom.. I was going nuts trying to get the uiButton to work like that and it always acted like a latching switch everytime…
OK.. making a little headway.
I just tried to make a trigger pad. How do I make a uiButton act like a key on a keyboard? So it’s like a momentary switch.
This could be real helpful for making a Phrase Sampler out of the S2k and make the GUI have an MPC appearance.
Thanks atom that information looks very helpful.
I got to messin around with the Akai last night a little more and have begun to start figuring out more SysEx coding.
I managed to get it to send dumps for key groups and for programs.
I also think I found a dump message for the raw sample itselfHecticcc,
Here’s what I got when I did filter changes in Program 1, Program 2 and Keygroups in various numbers.
Program 1
KeyG. 1 Filter value 96
065C57C0 1 2 F0 Buffer: 15 Bytes System Exclusive
SYSX: F0 47 00 2A 48 00 00 00 07 00 01 00 00 06 F7KeyG. 2 Filter value 97
065E4CE7 1 2 F0 Buffer: 15 Bytes System Exclusive
SYSX: F0 47 00 2A 48 00 00 01 07 00 01 00 01 06 F7KeyG. 3 Filter value 98
065F16EF 1 2 F0 Buffer: 15 Bytes System Exclusive
SYSX: F0 47 00 2A 48 00 00 02 07 00 01 00 02 06 F7Keygroup 36 Filter value 99
065FD4B9 1 2 F0 Buffer: 15 Bytes System Exclusive
SYSX: F0 47 00 2A 48 00 00 23 07 00 01 00 03 06 F7Program 2
KeyG. 1 Filter Val. 91
SYSX: F0 47 00 2A 48 01 00 00 07 00 01 00 0B 05 F7KeyG. 2 Filter Value 92
SYSX: F0 47 00 2A 48 01 00 01 07 00 01 00 0C 05 F7KeyG. 27 Filter Value 93
SYSX: F0 47 00 2A 48 01 00 1A 07 00 01 00 0D 05 F7Here’s a snippet from the info on sysex from here-
http://lakai.sourceforge.net/docs/s2800_sysex.html“Receive Keygroup Header bytes
0xF0 MIDI System Exclusive identifier
0x47 Akai Manufacturer code
cc MIDI Exclusive channel
0x2A Operation code
0x48 S1000 Model identity
pp,PP Program number
kk Keygroup (0x7f indicates all keygroups in program)
oo,oo Byte offset into header
nn,nn Number of bytes of data
ln,hn First byte (nibbled)
..,.. further data
0xF7 End of Exclusive message”with that info above, you can follow the bytes.
It looks like it is mixed in areas that are nibblized/4bits and lsb is first, msb 2nd.
I think Program # is nibbled, as is “byte offset into header” , “Number of bytes”, and finally the Value bytes themeselves at the end.
Other bytes, like Keygroup # are normal bytes.When you go down to “Accessing Keygroup Header bytes”
you will find the “Offset” byte values that correspond to the parameter/edit
Like Filter Cutoff Freq. is,
“FILFRQ” and it’s Offset # is 7 bytes.By changing that 7 to a “C” (Offset of 12), I was able to dial in the Prog.1/KG1 Env. 1 Attack Value and it immediately began to work.
Look at that page really close.. I think I see ways to access the hard/ZIP drives for directories/volumes.
Atom- I need to learn on how to use Global variables.. I’ve heard them being used many times before.. How I got this far w/out using them yet is beyond me, but I never could catch on how to set them up and use them.
a sample wave and loop editor panel would be awesome
hectic, I’ll get a good look at those strings tonight and post them in here
It was exciting to see and hear it working for the 1st time.
Hecticc, how does that script apply to a slider? Right now I’m hardset on KeyG. 1/Prog.1
Is there some kind of way to make it look your script msg. code?
I was thinking…. and I’ve done this before with a lot of time put into it.. I’d like to make a script that will fetch a program or keyg. dump.. well any dump it can use and update all the sliders to the selected prog./keyg. every time you switch over to a different one.
Making a panel that could emulate the sample edit functions might prove difficult, I imagine. It’d be nice if I could at least reverse the sample.. I’m guessing wave edits is a bit out of scope for Ctrlr?
I’d be happy if I could numerically loop/end/start/loop point, Reverse, attenuate volume.. just about everything that could be edited from the S2k’s tiny LCD.
I’ll have to sniff out those commands too, if they are even there in the 1st place.
Exciting stuff.. head is already turning on how to do the GUI.
-Blaine
Well I kept at it and figured out how to make the slider work.
I used this formula and the ls/ms variables in place…-
F0 47 00 2A 48 00 00 00 07 00 01 00 ls ms F7
In moments I had a Filter Cutoff/LFO Depth and LFO Rate sliders functioning and adjusting the S2k in real time!
Woohoo!! Gentlemen, I do believe I’ve got a good start going here!
Ok.. I hooked up the S2k to MidiOX and this is what I get when I have Program 1, Keygroup ‘s “FILTER Freq Reso” page on the LCD showing.
A zero Freq gives me this-
SYSX: F0 47 00 2A 48 00 00 00 07 00 01 00 00 00 F7
0002C49D 1 2 F0 Buffer: 7 Bytes System Exclusive
SYSX: F0 47 00 16 48 00 F7A “1” gives me this..
SYSX: F0 47 00 2A 48 00 00 00 07 00 01 00 00 01 F7
0002C49D 1 2 F0 Buffer: 7 Bytes System Exclusive
SYSX: F0 47 00 16 48 00 F7Freq set to “15”..
SYSX: F0 47 00 2A 48 00 00 00 07 00 01 00 0F 00 F7
0002C49D 1 2 F0 Buffer: 7 Bytes System Exclusive
SYSX: F0 47 00 16 48 00 F7And finally we have Freq. set at “99”
SYSX: F0 47 00 2A 48 00 00 00 07 00 01 00 03 06 F7
0002C49D 1 2 F0 Buffer: 7 Bytes System Exclusive
SYSX: F0 47 00 16 48 00 F7I’m not sure what that second message is, I think OX is resending the message back to the Akai and that is a confirmation msg.. seems to get that msg no matter what parameter I edit.
here’s another.. Program1 Keygroup 1, LFO1 rate set to “0”
00037B80 1 2 F0 Buffer: 15 Bytes System Exclusive
SYSX: F0 47 00 28 48 00 00 00 21 00 01 00 00 00 F7
00037B8F 1 2 F0 Buffer: 7 Bytes System Exclusive
SYSX: F0 47 00 16 48 00 F7
00037B93 1 2 F0 Buffer: 7 Bytes System Exclusive
SYSX: F0 47 00 16 48 00 F7that one gives me two extra messages at the end..
Anyone know if there’s a midi thru to switch on/off in OX?
Here’s the same LFO1 parameter, set to “99”
00054E73 1 2 F0 Buffer: 15 Bytes System Exclusive
SYSX: F0 47 00 28 48 00 00 00 21 00 01 00 03 06 F7
00054E82 1 2 F0 Buffer: 7 Bytes System Exclusive
SYSX: F0 47 00 16 48 00 F7
00054E86 1 2 F0 Buffer: 7 Bytes System Exclusive
SYSX: F0 47 00 16 48 00 F7I tried to make a slider out of the sysex info, but I cludged it all up somehow and it doesnt like it.
Any pointers on how to do it? Thanks all for your help and comments.. I think once I figure out how to do one, I can figure out most the rest of it.
- This reply was modified 11 years ago by Synthetech.
Uhhh.. I think recycle uses scuzzy as well, not MIDI.
I have searched all over for a MIDI based controller app for the Akai s2000 and have come up nil.
that’s why I think it’s worth the trouble to create a new panel for it. and it will also work for all the S Series samplers.
they are backward compatible but not forward.
that is why you have to look at the S 1000 sysex documentation to find the code format for parameters then the additional sysex documentations just have the update information.it is in the S 1000 doc that I think I saw the offset byte info that is the key to locating all the basic parameters, instead of monitoring every single jogwheell edit.
This is promising then if we can extract the sysex format from monitoring the MIDI data..
I’m betting some of the sysex docs I’ve found will spell out how to use that “offset byte” information to dial in the parameter to assign to a slider.
I’ll give it a go tonight and see if I cant evoke a response out of it.
And if we ever get this done, I have a Roland D2 to figure out eventually too..
I’ve heard you can use most of a MC-505 editor.. but the only one I found so far sucks just as bad as MESA II. There is not realtime control over something as simple as the filter.. again it is like it is rewriting the entire patch dump again instead of changing just the one parameter.
I see the knob adjust, but hear no changes.. but when I let the knob go, I finally hear it change to the value where I released the knob at.
Thanks so much for the quick replies/support.
I found this site to help figure out the sysex/parameters
http://lakai.sourceforge.net/documentation.shtml
Something about offset bytes is how you locate a parameter to change it’s value.
I took a look at Ctrlr and found you can reverse the MSB/LSB.. what is “Value Mapping” and “Number Mapping”? Is this where the MSB/LSB nibble bytes go?
I can tell this is going to take some time to understand.. but I’m guessing once we figure out how to crack the Akai open, then it’ll just be a matter of tedious entries for each slider/parameter.
Thanks for the replies.
Atom, I will definately refresh myself by reading your guide.
Hecticc, cool you made a Emu panel… which sampler?
I’ve done a panel before. It was for a custom Korg Poly 800 (new firmware).
But I did that about a year ago. I used both straight panel editing and a little bit of LUA/scripting so it could fetch a patch dump and set all the knobs/sliders/switches each time you selected a new patch via the panel.It was a pretty in depth script.. so I’ve gotten my feet a little wet in the fancy stuff.
I tried to do a simple filter control via sysex command for the S2K. I used a imageSlider and dialed in the Sysex format using a formula… I faltered with the LSB/MSB implimentation, evidently.
This machine seems to use the LSB first, then MSB.. so say 1C, 0A pairs of bytes would be LSB, MSB.
I appreciate any help/pointers I can get.. maybe if we collaborate we can get a decent panel once and for all for this machine..
Atom, don’t you think it would be a good idea to mention on the download page that the “stable” version may not work correctly with some of the example panels you can download from the database?
That they will need to try and use the latest “nightly” version instead?
Also, I suggest that the file that is downloaded have the version # in it somewhere.. I have two files, Ctrlr.exe and Ctrlr.exe. One is the stable version, the other is the nightly version.. I cant tell which is which at a glance.
If I get help on my question on how to script a line that will output a sysex hex code out, with variable #’s in it, I could probably figure up something.
I prev. managed to call a patch dump from my Korg, then set every single knob to the correct value.. one by one.
Youll need a control knob that is set to call a LUA script up every time they activate/change in value. In the script we piece the code together by calling the values for each “modulator”/control knob, inserting their values into the code and transmit it to the synth.
question- the 1 bit variable in there.. is it a byte of it’s own, or shared in one of the other two bytes? Do you have an example of a full F0-F7 of this sysex message to look at?
I still need help in how to send a sysex/hex code message with a variable hex value number in it….
…..I can SEND the patches, but not get them from the virus, so every patches sent are basically “all the knob down”, and what I’m sending it’s just the classic saw sound preset (another issue is that then every time I open a song after closing the program, ctrlr sends this presets. Any ways to avoid this? thank you!
If you know how to request a single patch dump from the virus.. then you can create a script that will set all the controls for you when you ask for the patch from the panel.
-
AuthorPosts