[opuswerk]

Hello,

I did get a bit further with the panel, including a total re-organisation of the layout. But I still haven’t had the chance to work on the GUI. At the moment the interface is very big, although it’s now much easier to work with.

You can find the current version attached. I’m not sure all the Lua is included, as I’m not quite clear with all the exporting in CTRLR.

It should update all patch and tone parameters on every patch load, update tone and patch name, as well as allow both tone editing if you have Vecoven’s OS. It currently does not work with a JX10, as the starting sysex string is different than the MKS70’s one.

Here’s what it currently looks like:

https://s3.amazonaws.com/f.cl.ly/items/3R2P1w3X172A213Q132q/Image%202015-03-11%20at%207.28.01%20am.png

Attachments:

You must be logged in to view attached files.

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

[opuswerk]

The Mks70 is known to have an issue with Tone B and sysex.

The only way to solve this is to update it to the latest OS made by Vecoven. All infos about it can be found here: http://www.vecoven.com/superjx/superjx.html

The panel is working as expected when used with this OS. IE it allows to edit both Tones independently.

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

[opuswerk]

Most of what you need is already found in this tutorial by Atom:

Getting started

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

[opuswerk]

It depends on your soldering skills i’d say. The PWM mod needs you to do some soldering, while the OS update is a simple ROM swap. So it’s up to you 🙂

On my side, I’m gonna stick with the OS updates for now. Need to get the 3.05 version though, as I’m still on a beta one, close to RC, but still with some little bugs if i remember correctly.

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

[opuswerk]

Hello,

No defect here at all.
This means you have an old version of the MKS70 firmware. Most certainly version 1.08. This was unfortunately not solvable until very recently. There really was no way around it. However, thanks to Frederic Vecoven, who re-wrote the entire MKS70 and JX10 OS from scratch to fix such bugs, and add some functionalities, now it’s not an issue anymore!

You should get his ROMs and exchange them with the one you have in your synth. It’s a pretty painless exercise, and comes with great benefits, which include Tone A and B editing. I’m currently running an older beta version of his OS, but will soon upgrade to his latest. Here’s some info about his project: http://www.vecoven.com/superjx/superjx.html
The upgrade is very much worth it. Basically he made it a new synth and a great analog poly at that!
If you want more info, there’s a big thread on the Gearslutz forum too.

Best regards,

H.

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

[opuswerk]

Hello Upeter,

The synth section should definitely update as well. Your machine is an MSK70 right?

I did some extra work on it, and it’s closer to being complete. I’ll send it to you via PM, so check your inbox.

Cheers,

H.

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

[opuswerk]

Hello m.tarenskeen,

I currently use a beta version of Vecoven’s MKS70/JX10 OS. I still need to upgrade my ROMs to the latest ones, but haven’t had time yet. It really works wonders, and does much more than fix the mks70. It basically allows it to be integrated in a present studio in a much more fluid way.

I highly recommend grabbing this OS if you own a JX10 or an MKS70. It’s that good!

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

[opuswerk]

Hello Superlewing,

Cool to see you took over part of the project. I had very little time to pursue it and somehow, it was working decently enough for me to use it as is. I hope it wasn’t to messy to work with…
I’m very curious about the link mode, as it’s something I really wanted to get done as well.

It seems like a lot of the lua I had written never got exported.
I had done lua for all dropdowns, as the values were not the same that the MKS70 was expecting. Namely, for the chorus, the enveloppes, etc… They don’t all expect the 0-127 values divided by the amount of object in the list.
Are they all working correctly in your version?
What do the top right buttons do?

Are the filters editing correctly? for both Tones? I noticed in my setup that sometimes, the MKS would hang until i got to the parameter on the synth and edited it myself. then it would catch up.

Also don’t you want the panel to update depending on the status of the MKS? Did you get rid of this part too? What went wrong with yours?

Will definitely try your panel when time allows, which is hopefully soon.

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

[opuswerk]

Hello,

I have indeed a new version of the panel, but some things are still not 100% functional, and I unfortunately didn’t have time to finish it. But I wouldn’t mind a helping hand.

I’m not sure I managed to export everything with the Lua included etc, so please let me know if that works.

Here’s what it currently looks like:

• This reply was modified 9 years, 6 months 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]

Don’t have a pulse, but your panel looks tasty 🙂

I wish I could make the UI of mine look the same. Great job!

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

[opuswerk]

Using the PG1000 layout would be an option, but it would involve a complex tabbing system, which if possible I would like to avoid.

I’d much rather have 1 slider per function in the GUI if possible. As there’s 4 partials + the fx channels, that becomes quite a lot to cram in one interface. So i’d love to find a solution, but haven’t had time to sit and start drawing it properly.
I just re-wired my whole studio, which led me to really wanting to have a better way to edit the D50. So I might get back at it, seeing I seem to have more free time.

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

[opuswerk]

Hello Husc,

Unfortunately time has become very scarce, and I couldn’t find enough to get this Panel done. The D50 has about twice the amount of parameters the D20 has, and needs a very well thought out GUI, which I couldn’t figure out yet.

If you’re interested in building a mockup, with no functions or sysex, I could maybe find the time to implement the functions for the panel.

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

[opuswerk]

I don’t think the MKS50 panel is able to update its modulator from received sysex data.
You might need to get your hands into some Lua to fix this. It’s not difficult, just a little bit long and tedious to do. But very rewarding.

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

[opuswerk]

Good job,

Glad you managed to make it work as well. Be careful to also modify all the sysex sent by the Lua scripts. Those might need some extra work 😉

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

[opuswerk]

Hello Oleg,

To my knowledge, the Matrix 6r has a slightly different Sysex implementation. I would recommend going through the sysex documentation, and then modify the sysex data of all the modulators of the Matrix1000 panel.

I’m afraid there’s no short route to get the panel to work with the m6r straight away. But i’d love to be proven wrong 🙂

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

[opuswerk]

I’ll send you the latest version when I’m back home tonight.
Still need to get around doing a proper GUI, as I believe it is a very important part of the panel, but I want to move away from the pg-800 design, and allow for a better overview of the whole state of the synth.

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

[opuswerk]

Hello,

Sorry for going missing after the last post. Life has been busy, and I spent quite a bit of time debugging what was wrong on my synth. It appeared that the jackboard had some fault, and was preventing any MIDI from going out of the synth.

So after some extra repairs, and many hours getting my head around Lua and losing and re-writing all my code a few too many times, I finally have a beta version of the panel that’s almost ready for some testing. All parameters should have understandable names, but the VST index might need some extra work to make it more user friendly in a DAW

The tone parameters now update on patch change, and are all working correctly.
What needs some extra work are:
– the Patch parameters
– a total redesign of the UI
– some testing on a non Vecoven OS.

I should be able to finish the patch parameters soon, after reading the manual once again to understand them better. However, If someone is willing to give a hand on the graphics side, it’s very welcome. Else, it’s an aspect that will have to wait a bit longer, as I can’t find any decent mac alternative to Knobman, and do not really have the time to design one at the moment.

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

[opuswerk]

I think I found my mistake, I had setup both the controller and the output of the panel to go to the same MIDI destination. After setting the Controller to none, it works fine.

I believe someone else mentioned that in another thread. So I’m sorry if this is a repeat of another thread. Feel free to delete this one if needed 🙂

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

[opuswerk]

Thanks for your response Atom.

Right now, I can select them from the dropdown list. Seeing as they have been added via the lua editor thing. But I suppose the fact that the “.lua” suffix gets added maybe is what prevents it from working? Is there something I’m doing wrong?

Of course, for sharing’s sake, it should be possible to “wrap” them within the exported panel.

Also, while here, it would be great if “Save and Compile” would compile all files. If one function crashes because of another one it has called, you need to go and save and compile both every time 🙂

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

[opuswerk]

After some more research, it seems that you can use external .lua files for some functions that are called directly within lua scripts.

But for example, you cannot use them when you assign a function directly to a modulator. Be it a comboBox, or a function called by the panel on init or on MIDI receive for example.

Is this normal an expected behaviour? It would be great to be able to get all the lua outside of ctrlr. I lost a few too many times all my scripts due to a crash.

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

[Author]

Posts