[opuswerk]

@Roman Kubiak:

This is some fantastic news. I still use the last OSX build here, working around some of its quirks, so a new version with the bugs fixed, like you seem to have done on the Windows version would be fantastic.

Btw, I’ve recently delved in the world of hackintosh, and depending on the components of your PC, it might actually be not so difficult to get OSX to run and to be able to work on it ?

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

[opuswerk]

subscribing as i’d love to get my hands on a newer build too.

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

[opuswerk]

A ramdomizer could definitely be done. Will think about it, and see what I can do on those cold evenings.
I was struggling with a MIDI feedback thing, but I believe I just figured it out.

I would however love to get a newer build for MacOS, if any one has managed that it would be a blessing.

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

[opuswerk]

@Mr.ToR: Are you using many uiCombo boxes? I believe the panelMidiPauseOut is broken for those. This might be what’s causing the feedback. i’m currently trying to wrap my head around this issue myself for my MKS70.

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

[opuswerk]

Would be ace. Btw, have a look at the pg8x gui. I find it really good.

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

[opuswerk]

Hi hhhh,

I’ve actually also just updated my mks70 to 3.16 and the flash update.
I’ve noticed this behaviour as well, and I suspect it’s due to how the parameters of the panel are updated.
I must have done something wrong on the Lua part. I will compare with some other panels to see what went wrong in my code.
If you’re a UI/UX guy, i’d love to make this panel look better as the current look is far from pleasant to my eyes. Don’t hesitate to hit me up by PM !

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

[opuswerk]

I’ve attached the sysex files here. They come from the yahoo ensoniq DP4 user group.
Hope this help. I suspect the dp4 implementation shouldn’t be tooo far from the dp2.

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

Hello @mri, let me know if you need some beta testing of the panel as I have a DP2.

Here is the full manual with the Appendix at the end: https://ccrma.stanford.edu/~dattorro/DP4_manual.pdf

Attachments:

You must be logged in to view attached files.

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

[opuswerk]

Thanks for the answer.

I completely understand your situation, and wish I could be of som more material help.
Any way I can help with that somehow, maybe use a debug log of some sort?

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

[opuswerk]

Hi all,

I’ve fixed some of the Lua, which should make the panel snappier and the modulators update better on MIDI dumps if you’re using a not so good MIDI interface.

Would love to integrate your chromatic shifter too robohymn, if you’re ok with that.

Attachments:

You must be logged in to view attached files.

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

[opuswerk]

@robohym: please upload your version. As I posted earlier, I’d love to have a proper GUI for it, inspired by this:

• This reply was modified 8 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]

@midiquestions:

I also had issues with setting the channels on the MKS70. I believe I had to reset everything to channel 1 for it to work. I didn’t dig too much into this though. Could you see if it’s working with channel 1?
It could be that you need to replace the strings in the sysex messages to the correct unit, but I thought Vecoven’s OS was smart enough to avoid this trap…
The best would be to monitor your MIDI input and change a value on the synth, and check if the beginning bytes of the string match with what the panel is sending.

@robohymn:
I was trying to do stuff like this, but didn’t really succeed. I suppose one should do some Lua to work around that limitation. I suppose maybe @atom could chip in here?
Regarding the UI, I’ve been in touch with someone who could do a MUCH better job than me and hoping he’d have some free time at some point to do the panel as well. The previous versions were laid out vertically, but I found while using it, that having the controls laid out in a horizontal fashion and following the signal path from left to right worked better for me. But heh, that’s one of the beauties of CTRLR, everyone can make their own 😀

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

[opuswerk]

@midiquestions : did you activate the sysex messages on your MKS70 ? What OS is your JX10? This panel is made to work with the Vecoven OS, but it should also work with the previous one on the Upper Tone only.

@robohymn: Thanks for trying out the panel. I was really lacking any other testers beside than myself. I don’t really understand how the methods got swapped, but anyways, I’ve fixed it and updated the panel accordingly.
Attached is the latest and fixed version. Tell me how it works out 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]

hmmmm. I never got such an error. Care to tell me how to replicate it?

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

[opuswerk]

Hello @midiquestions,

I’ve updated the panel a bit and here is the latest version. The layout has also been updated as I found some of the ways @possemo did his were inspiring.
I’ve attached a screenshot of what it looks like, as well the latest version of the panel.

Attachments:

You must be logged in to view attached files.

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

[opuswerk]

Hello @midiquestions,

I see what @possemo meant, and I don’t believe he was offensive in any way. As @quadraspleen said, it’s all free and a collaborative effort.

I will try and put up my latest version in the panels section. I’ve been using it quite a bit, and I reckon it’s pretty solid with the 3.0xxx OS. A lot of time and effort has been put in it, and seeing how frustrated I was with my MKS-70 and not being able to edit it, I suppose I’m not alone. I should mention it also should work on Tone A of a less that 3.0 OS.

I was hoping to get some feedback on the panel before putting it up, but maybe it’s not visible enough ? Don’t hesitate to let me know if something isn’t working as expected.

Anyways, I am more free of my time now, and will be updating the panel to make it work in the best way possible, as I shall be using it more and more in the coming weeks.

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

[opuswerk]

Hello TonE,

It would be great if you could upload this file somewhere here.
I was hoping there would be someway to automatically generate all the controllers that are in the Bitstream txt, and then re-arrange them. It would save a lot of time manually putting in the sysex data for each knob, and allow for the automatic creation of all the params.

I wonder if it’s doable via Lua?

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

[opuswerk]

wow Possemo,

Your panel looks good, and more readable than mine. I still don’t know where that red color comes from…. Having the vertical sliders everywhere really helps to make the panel more compact. Might switch to that on the non PWM panel too. Same goes about the visual feedback on the enveloppes.

Sooooo many new parameters. It’s gonna be fun to have them update on patch dumps 😉 Good luck!

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

[opuswerk]

Hey Possemo,

I simply did not have time to dig into the file you sent. It seems like the APR is completely different from the MKS70 one. So it means a lot of Lua needs to be rewritten. There’s so much that’s been added that it seems it should almost be another panel, with quite a different layout too.

I can definitely help you out when possible, but I too have very limited time to work on such a project, which is why it took so long to get it done in the first place. I’m the first one disappointed about this situation, but we all need to pay bills T_T. I wish I could focus more on music really.

Basically, it’s not so much work, but I guess it’s about 1,5 week fulltime. It’s just time consuming to make sure everything is working correctly, and making sure the panel is laid out in a useable and sensible way.

• This reply was modified 8 years, 11 months ago by opuswerk.

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

[opuswerk]

I’ll test this ASAP. If this works, it would save quite some Lua, especially when expanding the panel to the PWM features.

I believe Lua could be used ONLY for updating the synth on patch dumps and adding extra functions that are not on the synth, and that need extra programming, like the Patch Linking.

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

[Author]

Posts