[opuswerk]

I indeed tried to go the route Superlewing described, but not all parameters behave in such a smart way. Ie being multiples of 32 for example.

So to make things easy to manage, I built the Lua routines instead, which are all similar. I have an excel sheet somewhere with all the possible values of all the parameters that I used to keep track of the whole thing 🙂 .

@Possemo: I’m curious how well your upgrade will go. 🙂

http://opuswerk.tumblr.com
www.soundcloud.com/opuswerk
www.facebook.com/opuswerk

[opuswerk]

Hello Possemo,

I suppose I could try out and plan the panel for the PWM mod, but as I’m not 100% sure of how the patch dumps work with it, i’d rather not yet venture in developping this.

I just read that Fred’s out of PWM kits, so my upgrade will need to wait. But i’m on the looout for a EPROM burner, as I need to update my ROMs in my MKS 🙂 Do you have one to recommend?

http://opuswerk.tumblr.com
www.soundcloud.com/opuswerk
www.facebook.com/opuswerk

[opuswerk]

Hello Possemo,

Thanks for the links. I wish I had found those when I was programming the panel… Most of the parameters sysex I had to find myself by trial and error, which was VERY long….

So you know, the panel already works by using the data sent by the synth on PATCH and TONE dumps. This data is used to update the whole panel. This bit of code could definitely be optimised though.

Basically, to extend the panel, you will have to extend the sysex capabilities. I do not know how the PATCH and TONE dumps are handled on the Vecoven 4.0 OS. So you’ll need to ask him about those so that the synth will update correctly when data is sent from the MKS70/JX10.
I’m hoping I will have time to add the extra functionalities myself, as it shouldn’t be too long, but i’ll have no way of testing it at all.

Maybe it’s worth having a button the user can engage that extends the UI if he/she has the PWM mod installed. That would be nifty 🙂

http://opuswerk.tumblr.com
www.soundcloud.com/opuswerk
www.facebook.com/opuswerk

[opuswerk]

Yes, I should’ve said that I usually record the master out of my mixer, and don’t do much multi-tracking.
Also, like this I can directly compensate the latencies and thus apply fxs and the likes on the signal and have this directly in the monitors too. When needed, I usually then fire another channel that records the MKS70 directly, or any other hardware synth that I use.

http://opuswerk.tumblr.com
www.soundcloud.com/opuswerk
www.facebook.com/opuswerk

[opuswerk]

Glad to see my panel is getting used outside of my studio. Didn’t expect it could be worth that much cash. I’m always open for donations 🙂

That is indeed a LOT of new parameters, which deserve a re-thinking of the GUI. Especially with all the power brought by the looping enveloppes. This would need some graphical ADSR visualisation. Which would be really cool to implement on the current enveloppes too. I find the sliders are a bit hard to use, as you currently have no way of knowing how long your attack or decay will really be.

About the CTRLR setup. The way I go about it, is couple (rack) it in Ableton Live with an external instrument device. That way, the CTRLR only takes care of sending the SYSEX and controlling the synth parameters, while the external instrument sends the MIDI notes and receives the Audio directly in the same channel.

http://opuswerk.tumblr.com
www.soundcloud.com/opuswerk
www.facebook.com/opuswerk

[opuswerk]

@possemo:

The panel can update the patch on the MKS70/JX10, but it doesn’t currently update its value on patch dumps. I do however now know how to go about this. So I will update it ASAP.

Thanks for your patch dump. It seems all works as expected on mine too. Although, I still can’t explain why the synths sends the patch twice. It’s almost as if it’s receiving and sending the PRGM change on patch load, forcing the synth to load twice…

Is there a way in CTRLR to prevent the panel from sending ANY midi information until the panel has finished updating? Any Lua trick to do?

@AnalogJunkie:
Please keep me posted on how things go with your synth.

xx edit xx

Updated the latest version, which reflects the KeyMode properly!

• This reply was modified 9 years ago by opuswerk.

Attachments:

You must be logged in to view attached files.

http://opuswerk.tumblr.com
www.soundcloud.com/opuswerk
www.facebook.com/opuswerk

[opuswerk]

From now, the panel updates the KeyMode, but its state is not reflected by the patch dump, as I can’t find which byte has that information. I will get in touch directly with Fred to check this issue.

Let me know if I can be of some help to get the panel working with your JX. CTRLR is a bit strange to setup the first time, but once you wrap your head around it, it’s very easy.

http://opuswerk.tumblr.com
www.soundcloud.com/opuswerk
www.facebook.com/opuswerk

[opuswerk]

Will check your panel in the morning. I did start a D50 panel at some point, but it was a bit too much as a starting panel.
You might want to check the D20 panel that is in the forum, as it dealt in avery nice way with the envelopes and the UI.

http://opuswerk.tumblr.com
www.soundcloud.com/opuswerk
www.facebook.com/opuswerk

[opuswerk]

Thanks for you dump Possemo.

Could you please send a dump that starts with a program change you’d load from the MKS please? Will be a bit easier to compare.

I’ve updated the panel, so that it behaves a bit better. The Lua was relaunching a bit too many things on every midi message received. So Filtered that a bit, in a nasty way though… But heh, it works.
What I’ve couldn’t figure out unfortunately, was how to mute the program change messages that get sent on the panel updates. Those cause the whole panel to reload everything twice, and send sysex twice as well. Which is far less than optimal. If someone a bit more knowledgeable can pitch in here, i’d love some help.

All the present parameters update to reflect the status of the synth now. If I missed something please let me know.

My OS version doesn’t seem to be sending the KEY MODE value in the Patch APR. So I can’t get the correct values to finish the lua there. The code to update starts at line 14 of the assignPatchParamValues function.

Attachments:

You must be logged in to view attached files.

http://opuswerk.tumblr.com
www.soundcloud.com/opuswerk
www.facebook.com/opuswerk

[opuswerk]

Trying to figure how this one works as well.

I aim to filter normal messages from patches dump, as the mks70/JX10 sends a bit too much stuff, and triggers function unnecessarily with the midiMessageReceived function.

http://opuswerk.tumblr.com
www.soundcloud.com/opuswerk
www.facebook.com/opuswerk

[opuswerk]

@AnalogJunkie:
I’m using Vecoven’s Beta 3750 on my MKS70. I believe the unit number is also 24 for the JX10 ? If so the panel should work. Have you set the MIDI out in CTRLR correctly?

I’m currently trying to figure out why I get so much sysex on patch dumps.
Could anyone load a patch and paste the content of the sysex patch dump? You can easily do this by using the built-in MIDI monitor in CTRLR.

For some reason I seem to be getting the Patch program data twice…

Here’s a sample of a message I receive:

RAW:[f0 41 34 00 24 30 01 3d 00 f7]
RAW:[f0 41 35 00 24 30 01 20 20 4d 41 59 2e 53 20 50 41 44 20 20 20 20 20 20 20 47 51 27 26 00 00 00 75 11 7f 00 5a 74 00 4d 01 05 00 01 00 42 00 00 4c 01 15 00 01 00 5a 01 1a 00 00 00 f7]
RAW:[f0 41 34 00 24 20 01 5a 00 f7]
RAW:[f0 41 35 00 24 20 01 4d 41 59 2e 53 20 57 49 4e 44 20 40 20 00 00 23 40 20 00 02 30 05 00 7f 7f 7f 60 60 6d 6d 3a 20 20 20 45 00 00 46 63 20 40 70 60 00 40 5e 63 00 15 00 5b 00 20 48 2a 21 20 7f 40 f7]
RAW:[f0 41 34 00 24 20 02 42 00 f7]
RAW:[f0 41 35 00 24 20 02 53 4f 55 4e 44 54 52 41 43 4b 20 20 60 00 00 00 20 60 00 02 30 00 00 7f 7f 7f 60 20 6d 6d 3a 20 20 00 34 00 00 3c 58 20 60 68 40 20 40 4e 67 7f 53 36 5b 00 50 6d 39 4d 20 7f 40 f7]
RAW:[c0 3d]
RAW:[f0 41 34 00 24 20 01 5a 00 f7]
RAW:[f0 41 35 00 24 20 01 4d 41 59 2e 53 20 57 49 4e 44 20 40 20 00 00 23 40 20 00 02 30 05 00 7f 7f 7f 60 60 6d 6d 3a 20 20 20 45 00 00 46 63 20 40 70 60 00 40 5e 63 00 15 00 5b 00 20 48 2a 21 20 7f 40 f7]
RAW:[f0 41 34 00 24 20 02 42 00 f7]
RAW:[f0 41 35 00 24 20 02 53 4f 55 4e 44 54 52 41 43 4b 20 20 60 00 00 00 20 60 00 02 30 00 00 7f 7f 7f 60 20 6d 6d 3a 20 20 00 34 00 00 3c 58 20 60 68 40 20 40 4e 67 7f 53 36 5b 00 50 6d 39 4d 20 7f 40 f7]
RAW:[f0 41 34 00 24 30 01 3d 00 f7]
RAW:[f0 41 35 00 24 30 01 20 20 4d 41 59 2e 53 20 50 41 44 20 20 20 20 20 20 20 47 51 27 26 00 00 00 75 11 7f 00 5a 74 00 4d 01 05 00 01 00 42 00 00 4c 01 15 00 01 00 5a 01 1a 00 00 00 f7]
RAW:[f0 41 34 00 24 20 01 5a 00 f7]
RAW:[f0 41 35 00 24 20 01 4d 41 59 2e 53 20 57 49 4e 44 20 40 20 00 00 23 40 20 00 02 30 05 00 7f 7f 7f 60 60 6d 6d 3a 20 20 20 45 00 00 46 63 20 40 70 60 00 40 5e 63 00 15 00 5b 00 20 48 2a 21 20 7f 40 f7]
RAW:[f0 41 34 00 24 20 02 42 00 f7]
RAW:[f0 41 35 00 24 20 02 53 4f 55 4e 44 54 52 41 43 4b 20 20 60 00 00 00 20 60 00 02 30 00 00 7f 7f 7f 60 20 6d 6d 3a 20 20 00 34 00 00 3c 58 20 60 68 40 20 40 4e 67 7f 53 36 5b 00 50 6d

and here again with some explanations:

PATCH NUMBER
RAW:[f0 41 34 00 24 30 01 3d 00 f7]
PATCH NAME + PARAMETERS
RAW:[f0 41 35 00 24 30 01 20 20 4d 41 59 2e 53 20 50 41 44 20 20 20 20 20 20 20 47 51 27 26 00 00 00 75 11 7f 00 5a 74 00 4d 01 05 00 01 00 42 00 00 4c 01 15 00 01 00 5a 01 1a 00 00 00 f7]

TONE A NUMBER
RAW:[f0 41 34 00 24 20 01 5a 00 f7]
TONE A NAME + PARAMETERS
RAW:[f0 41 35 00 24 20 01 4d 41 59 2e 53 20 57 49 4e 44 20 40 20 00 00 23 40 20 00 02 30 05 00 7f 7f 7f 60 60 6d 6d 3a 20 20 20 45 00 00 46 63 20 40 70 60 00 40 5e 63 00 15 00 5b 00 20 48 2a 21 20 7f 40 f7]

TONE B NUMBER
RAW:[f0 41 34 00 24 20 02 42 00 f7]
TONE B NAME + PARAMETERS
RAW:[f0 41 35 00 24 20 02 53 4f 55 4e 44 54 52 41 43 4b 20 20 60 00 00 00 20 60 00 02 30 00 00 7f 7f 7f 60 20 6d 6d 3a 20 20 00 34 00 00 3c 58 20 60 68 40 20 40 4e 67 7f 53 36 5b 00 50 6d 39 4d 20 7f 40 f7]

BREAK ?
RAW:[c0 3d]

TONE A NUMBER
RAW:[f0 41 34 00 24 20 01 5a 00 f7]
TONE A NAME + PARAMETERS
RAW:[f0 41 35 00 24 20 01 4d 41 59 2e 53 20 57 49 4e 44 20 40 20 00 00 23 40 20 00 02 30 05 00 7f 7f 7f 60 60 6d 6d 3a 20 20 20 45 00 00 46 63 20 40 70 60 00 40 5e 63 00 15 00 5b 00 20 48 2a 21 20 7f 40 f7]

TONE B NUMBER
RAW:[f0 41 34 00 24 20 02 42 00 f7]
TONE B NAME + PARAMETERS
RAW:[f0 41 35 00 24 20 02 53 4f 55 4e 44 54 52 41 43 4b 20 20 60 00 00 00 20 60 00 02 30 00 00 7f 7f 7f 60 20 6d 6d 3a 20 20 00 34 00 00 3c 58 20 60 68 40 20 40 4e 67 7f 53 36 5b 00 50 6d 39 4d 20 7f 40 f7]

PATCH NUMBER
RAW:[f0 41 34 00 24 30 01 3d 00 f7]
PATCH NAME + PARAMETERS
RAW:[f0 41 35 00 24 30 01 20 20 4d 41 59 2e 53 20 50 41 44 20 20 20 20 20 20 20 47 51 27 26 00 00 00 75 11 7f 00 5a 74 00 4d 01 05 00 01 00 42 00 00 4c 01 15 00 01 00 5a 01 1a 00 00 00 f7]

TONE A NUMBER
RAW:[f0 41 34 00 24 20 01 5a 00 f7]
TONE A NAME + PARAMETERS
RAW:[f0 41 35 00 24 20 01 4d 41 59 2e 53 20 57 49 4e 44 20 40 20 00 00 23 40 20 00 02 30 05 00 7f 7f 7f 60 60 6d 6d 3a 20 20 20 45 00 00 46 63 20 40 70 60 00 40 5e 63 00 15 00 5b 00 20 48 2a 21 20 7f 40 f7]

TONE B NUMBER
RAW:[f0 41 34 00 24 20 02 42 00 f7]
TONE B NAME + PARAMETERS
RAW:[f0 41 35 00 24 20 02 53 4f 55 4e 44 54 52 41 43 4b 20 20 60 00 00 00 20 60 00 02 30 00 00 7f 7f 7f 60 20 6d 6d 3a 20 20 00 34 00 00 3c 58 20 60 68 40 20 40 4e 67 7f 53 36 5b 00 50 6d

This could be due to my beta OS. But i’d love someone to confirm this.

http://opuswerk.tumblr.com
www.soundcloud.com/opuswerk
www.facebook.com/opuswerk

[opuswerk]

Hello Superlewing,

Great little update. Makes me think it’d be great to have a way to link Tone A with Tone B and keep the differences of the slaved Tone. In that way it’d become possible to to detune one patch against the other and keep that detuning when automating the master tone. I hope that makes sense.

I’ll try it out with Push tonight when I get home. Very eager to get it on. My history with my MKS70 made it so I never really had the chance to learn it properly, but I’m betting a lot on this panel to get me out of this.

I also want to delve in the LookAndFeel of CTRLR, so might try to change the colors when the link is activated. I’ve updated the panel, so that the Patch Key Mode gets updated on patch dumps.
Not ALL parameters get updated now. Also, the After Touch control are missing of the panel, and some more. Shouldn’t take long once I’m with my MKS70. So i’ll get to those. I might be missing some sysex details here as not all params are shown in the latest manual.

Btw, if someone can help on the GUI, it’d be great. Although I think the panel has become more useable as it is now. It could be more compact still…

@Possemo: I’ll be in Bern next Tuesday. How did the PWM mod go? I want to order from Fred, but it seems he’s finished the batch already?

xx edit xx
Forgot to add the updated panel.

• This reply was modified 9 years ago by opuswerk.
• This reply was modified 9 years ago by opuswerk.

Attachments:

You must be logged in to view attached files.

http://opuswerk.tumblr.com
www.soundcloud.com/opuswerk
www.facebook.com/opuswerk

[opuswerk]

Then we’re closer than I thought we were. I’m in Geneva, so not so far and most believe it’s the capital 😉

http://opuswerk.tumblr.com
www.soundcloud.com/opuswerk
www.facebook.com/opuswerk

[opuswerk]

Now we’re talking! 😉

Keep me posted about your mod successes and we’ll see what we can do.
Where are you based?

http://opuswerk.tumblr.com
www.soundcloud.com/opuswerk
www.facebook.com/opuswerk

[opuswerk]

I’d actually love to do the PWM mod one day. But I believe i’ll need a good tech on this one. As my soldering skills are at a 0 level at the moment.

The issue with updating the panel comes from the fact that I won’t be able to test it at all. But if you send me the layout and the sysex data, it shouldn’t be too difficult to implement roughly and let you edit it in a better way.

Also, You can freely take the panel and update it yourself. Do not hesitate, but share the result with us afterwards 😉

http://opuswerk.tumblr.com
www.soundcloud.com/opuswerk
www.facebook.com/opuswerk

[opuswerk]

Hello guys,

Sorry for not replying earlier. I’ve become a father for the second time since starting this panel project, and I must say it’s taking a toll on my free time.

The VST index is sorted, thanks to your script, but they’re not really bundled together. At least they start from 0 🙂

I currently don’t have the PWM mod, and I won’t be installing it before a while. I believe the sysex controls are already well implemented, and might be complex and long to change. It would be much easier to script some Lua to replace the Hex strings in case the panel is connected to a JX10 instead of a MKS70. Hex is actually very easy to use with CTRLR, and I’d recommend sticking to it. It will also prevent you from re-writing all the Lua which uses the sent patch data to set all the sliders to their correct positions.

I’ve re-organised the panel to something more compact and easier to use. See attached screenshot. I was thinking of maybe doing 2 panels for each voiceboard, which would make the panel even more compact, but I reckon I like having an overview of both boards at the same time.

The latest version is attached hereunder. Please let me know how it goes for you.

Attachments:

You must be logged in to view attached files.

http://opuswerk.tumblr.com
www.soundcloud.com/opuswerk
www.facebook.com/opuswerk

[opuswerk]

I see. Will try and write the routine so that it bundles modulators according to their groups. That should already be of some help to set it up in push.

I’ve worked quite a bit on the layout, and I find what’s currently there to be working pretty well, so would like to keep this grouping in push too.

Will experiment with the sliders too.

Thanks!

http://opuswerk.tumblr.com
www.soundcloud.com/opuswerk
www.facebook.com/opuswerk

[opuswerk]

Quite a smart little function here indeed. Could be integrate to the CTRLR core I reckon.

Will see how one could rename all param names in a smart way. As i understand, they should all be a max of 8 chars?

So at the moment, how are the param numbered? and how do they show up in Push? Are they grouped somehow? Would be smart to have DCO1 params next to one another.

I’ve been trying to get some nice thing out of Knobman. Do you know a method of some-sort to change all the sliders to a specific image slider? What I’m hoping to do is to replace and resize all sliders in one go…

http://opuswerk.tumblr.com
www.soundcloud.com/opuswerk
www.facebook.com/opuswerk

[opuswerk]

I also acquired Push recently, but didn’t think of changing the vst indexes and parameters names yet. Would be a great thing to do indeed. I dont believe many people have used the panel in projects yet. So we could change it without much impact.

How do you think we should go about it? Should be easy and fast to fix. I’ve come to realise for such things, it’s much easier to open the panels in a text editor and replace the text directly. Been using Sublime Text to do so and it’s pretty handy.

http://opuswerk.tumblr.com
www.soundcloud.com/opuswerk
www.facebook.com/opuswerk

[opuswerk]

Any luck using the panel ?

http://opuswerk.tumblr.com
www.soundcloud.com/opuswerk
www.facebook.com/opuswerk

[Author]

Posts