April 18, 2013 at 6:57 pm #8303
This panel is brill.
Mr Mean. I have done another little adaptation so this works with an MKS-70, and I’ve found out how to edit both tones independently as well now, so have created an A and a B panel which I save as a CTRLR state. It is ace. Would you mind if I posted them? (with full credit to you of course) I have no idea how to incorporate the two panels into one panel so I just open them both together and it works a treat
jakeApril 19, 2013 at 7:30 am #8324
Nice to hear you like it!
And no it’s not a problem if you post it but maybe I can have a look first and see if I’m able to make it work with a JX8P/MKS70 and Layer switch.
I don’t have a MKS70 myself so it would be nice if you can test it for me.
Almost all functions are the same as far as I know it, only the sysex header is different.
Please PM for contact.April 19, 2013 at 1:31 pm #8330
PM’d with zipfile of panels..fill your boots 🙂
Happy to test anything..I have a real PG-800 as well, so can verify functionality with all of the hardware – if you can find and afford one, pick up an MKS; they are great little boxes – got mine from Pete Waterman’s studio years ago on eBay! – apparently “at least one Kylie record made with it” LOLMay 4, 2013 at 3:26 pm #8701
Oh cool, I was just gonna sit down and try and port this over! Any chance you guys can send me the panels? I’d love to help out as well.
MicahMay 28, 2013 at 7:06 pm #9337
Sorry, I’ve been mad busy at work.
So, with absolute total credit to Mr. Mean, here is my (very basic) adaptation of his most excellent JX-10 panel.
As we all know, the MKS-70 is basically a JX-10 in a rack, so with a simple deviceID and tone byte byte change, this panel now controls both Tone A and Tone B. I am not clever enough to actually make these panels, as I don’t know LUA (and don’t have time to learn it right now) but I do know sysex, so what I did was just create a seperate panel for each tone and just open them both in an instance of ctrlr. Hey presto, it works!
There are limitations, which Mr. Mean has tried to overcome in a further adaptation of the panel, but I think he hit a brick wall with the aged intransigence of the thing, so this is it (for now at least)
1. It will not send the visible slider settings for the non-visible panel i.e if you are looking at tone B and change patch only the visible sliders will move (the tone window you have foremost in ctrlr)
2. You cannot use the program and tone select functions (though the tone select function sort of works up to a point)
Have fun and again, all credit goes to Mr. Mean for his patience in creating such a damn useful tool,
- This reply was modified 4 years, 8 months ago by quadraspleen. Reason: dumbness
Attachments:You must be logged in to view attached files.August 11, 2013 at 11:02 am #11843
Hi, my MKS70 is still in repairs, but i as i was dying to try this out, i grabbed it. Unfortunately, i get an error when opening it.
Seems like the sliders are there, but they don’t show. It’s as if the graphics where all missing.
Any chance this could be broken by the latest ctrlr update?
www.facebook.com/opuswerkNovember 27, 2013 at 10:54 pm #15907
Due to my synth getting back from repair, I wanted to quickly try those panels. Unfortunately, I still don’t get any slider displaying…
I did however salvage the sysex info and am trying to build a panel on my own next tot he d50 one i’m also working on.
I have one question regarding the MKS70. For some reason, I can send sysex to it, and the value of the corresponding parameter will change on the synth. However, it doesn’t update until I turn the Alpha-Dial, and the screen keeps on blinking until the Alpha-Dial is turned as well. I’m very sure I’m missing something very obvious here, but if some kind soul could give me a hand it’d be awesome 🙂
www.facebook.com/opuswerkDecember 1, 2013 at 1:49 pm #16050
The current version of my version of the MKS70/JX10 panel can be found here
Several things still need to be done on the panel, namely:
- all of Tone B controls (which i can’t test as i’m on 1.05)
a GUI for the enveloppes
making the dropdown menus work (selecting waveforms and ranges don’t work at the moment because of what i suspect is a ctrlr bug)
overall layout design
I am currently stuck with the parameters still not updating until moving the alpha dial, despite showing the correct value on the synth.
I tried applying and not applying the Roland checksum, and looked everywhere I could to find a global parameter to reduce the Sysex transmission speed.
Instead of duplicating the PG800 layout, the idea is to offer a design that allows for an overview of both tones, as well as a new part that will allow for controls of both tones parameters at once.
I hope this will be of interest to someone 🙂
www.facebook.com/opuswerkDecember 5, 2013 at 11:52 am #16237
Thanks opuswerk, this is shaping up nicely!
I’m on 1.08 and happy to help testing tone B.December 5, 2013 at 11:57 am #16238
Glad to see you’re interested. Maybe you can tell me if parameters of Tone A already update with the panel as it is. Currently on my machine, the value update but the changes are not applied. I’m suspecting it’s a problem of the 1.05 OS. It would be great if you could confirm that, as my machine is just out of repair, and if something is wrong, I have to bring it back 🙂
www.facebook.com/opuswerkDecember 5, 2013 at 1:22 pm #16240
I’ll have a look tonight. Yesterday I managed to get a couple knobs affecting tone A but it was patchy at best.December 5, 2013 at 2:11 pm #16246
Cool, please keep me posted.
www.facebook.com/opuswerkDecember 6, 2013 at 12:02 am #16257
It seems like most of the knobs are working. Altering the VCF Q knob always sets it to zero always and there’s a couple others which might do the same. The MKS70 is new to me so it’s hard to tell.
The selectors just set a specific value whatever is selected, VCO shape will always set to noise for example.
The patch selectors do work so I’ve been having fun getting to know this beast a bit. Lemme know if there’s anything I can do to help this along.December 29, 2013 at 6:25 am #17064
Where can I get the latest version of the MKS-70 panel?
The link above isn’t working.
Thanks.December 30, 2013 at 10:11 pm #17149
I was away for a while and didn’t get to work on this more. However, I’ll be finishing this up as fast as possible and will post updated versions of the panel in this thread.
I have also updated my MKS70, so I will be able to test the editing of tone B as well.
I have been struggling with the dropdown lists. It seems they work when I set them up outside of a uiGroup, but only send one value once I drag them in a uiGroup. I still don’t know wether that is a ctrlr bug, or if it’s me doing it in a wrong way.
www.facebook.com/opuswerkDecember 31, 2013 at 1:14 am #17152
Do you mean a combo (dropdown list?)December 31, 2013 at 6:26 am #17158
Yes, it’s happening with uiCombo lists.
I’ve attached the current state of the panel hereunder so you can see what does it wrong.
www.facebook.com/opuswerkJanuary 2, 2014 at 10:52 am #17219
I have worked a bit more on the panel, and I hope the current version will be more useable for everyone. I’ve attached it in the post hereunder
You can now edit both tones from the panel and edit all of the available parameters on the synth. If something isn’t working correctly, or as expected, please let me know so i can test and fix it.
More needs to be done about the UI and look/feel of the panel, but this should allow everyone to test this and try it out with their mks70 or jx10, as the MIDI implementation is fairly similar.
I also still want to get the parameters to update on patch changes, like the great panel for the Matrix1000 does. If time allows that might get done today if it’s possible, as there’s quite a lot of parameters to program…
Attachments:You must be logged in to view attached files.
www.facebook.com/opuswerkJanuary 3, 2014 at 7:59 pm #17316
Will try it tonight. WELL DONE!
(I wouldn’t worry too much about the look and feel; if it works, it works!)
jakeJanuary 3, 2014 at 10:18 pm #17326
I woked some more on it today and fixed a few things. Will post the new version up tomorrow.
There’s some slight layout change and a few bugs correcting. I’d love some help on getting the modulator to reflect the current state of the patch if anyone has some time to spare 🙂
As i’m currently running a beta version of the rewritten OS by vecoven, there might be some things that i can’t test properly. So all extra testing would be really great.
You must be logged in to reply to this topic.