Forum Replies Created
-
Posts
-
Hi Opuswerk,
I coudn’t agree more with you :´( Maybe the new Vecoven OS4.0 has a “PG800 compatibilty mode” which would mostly work with the actual panel. But I want a panel that implements the new features. It’s already in progress and some parameters are already working. If possible I use CC’s (not all Parameters react to CC’s) and I want to make graphic envelopes. When I get news (or when I am stuck somewhere) I will post it here.
Thanks for your offer to help me out if necessary.Ah, and I have to mention my promise to do the pwm-mod for you… I generally don’t
say I won’t do it but I somewhat underestimated the amount of work. And there is a risk of turning your MKS-70 into a brick which I really don’t want to happen. But I can make you the following offer: When you get the pwm-kit someday we could do the mod together with my equipment. With two additional helping hands the mod would be done faster. I guess it would take two weekends at max.Hi there. Not much activity lately :). No problem, I will make a panel for the Vecoven OS4.0 myself. After all it seems that I am the only one here on the Ctrlr-forum that will be able to test it. It will take a lot of time because I too am busy with other things. But when I get something done worth publishing I will post it here.
So long.I put the patchdumps from opuswerk, my old v1.08 and my new vecoven v4.0 together in one textfile to compare them. It looks like the opcode 35 (APR – all patch parameters) has been changed to 38. I don’t know if this is a feature or a bug but now it is clear why program-change is the only sysex string that still works – this one has not been changed (34). The opcode for IPR (36) seems like it has been changed too. I will check this out this evening.
Hi,
I did it. pwm-mod installed. 🙂 It looks like I could avoid to brick my mks70 🙂 Now it seems there is some work to do on the panel. But maybe there are some wrong parameters on the mks70 – there are many new things on the midi-page. For now the panel does not work any more. All I can do is change a patch. That too is the only thing the panel updates when I change a patch on the mks70 (e.g. it changes from A1 to B2).I recorded a program change and I attached it on this post. For now I am too tired to look into it.
Cheers
The UI combo content is just the displayed text string, in your case the combo would still send the values 0, 1, 2, 3.
I use the newest build of ctrlr, and with this it definitely works. Values are changed with the ones that you set. For example “16 = 100” displays “16” and sends “100” resp 64 in hex. I checked the results in the midi-monitor.
Edit: I saw now that this example was quite wrong, but I’m sure you got the point. Here is an example which is actually correct for “dco1range”:
uiComboContent:
16 = 0
8 = 50
4 = 80
2 = 100MidiMessageSysexFormula:
f0 41 36 00 24 20 01 0b xx f7The “xx” variables must be lower case.
And of course MidiMessageType set to Sysex.
Hi opuswerk,
I never bought a eprom-burner because I use it too rarely. As a starting point I would look here:
http://www.classic-computers.org.nz/blog/2012-10-21-eproms.htm
The CPUs are already desoldered and the sockets are in place. I noticed that I miss practice for soldering/desoldering. I haven’t done it for a long time. I really hope I did not fry any chips…
I had to wait for some ribbon cable and other things I ordered so I looked into the MKS-70 panel and now I understand it much better. I have a question about the “uiCombos”. You made a piece of lua-code to set the sysex-strings, but you could make it simple by just defining the changing values in the uiComboContent like this:
For example dco range (you have to put dec. values):
16 = 100
8 = 80
4 = 50
2 = 0And then you can set the sysex-string like the other controllers with the MidiMessageSysexFormula like this (just an example from dco tune): f0 41 36 00 24 20 01 0d xx f7
Or does this has some disadvantages?Hi opuswerk,
According to Fred the OS v4.0 should be downwards compatible. So, everything should work as before as long as you don’t use the new features. The new sysex-IPR parameters are already documented. Or is my way of looking at this naive/noobish? I will see, But first I have to finish this plumbers job. You don’t plan to get a PWM-kit?I never looked into Ableton Live. I always used Cubase (very old ver.). Now with my new x64 Windows-PC I am trying out Reaper.
I received the kit from Fred yesterday. So, yesterday I fitted the components on the daughterboards (I ordered a non-luxury version). The new PWM-kit pictures on vecoven.com are showing the use of ribbon cables. This looks nice, I think I will do it this way. I’m still looking for the best way to fit the daughterboards in the already crowded 2U-Rack of the MKS. The PWM-kit pictures are all taken from a JX-10 where you have plenty of space. But no problem, I will find a way it will just take some time.
If everything goes well I will need a patch editor to explore the new features. Will have to try to get into sysex…
I found a good starting place for this. Do you know it already?http://llamamusic.com/super-jx/mks70SysEx_I.html
http://llamamusic.com/super-jx/mks70SysEx_II.htmlOn part 1 he explains the weird KeyMode, as well as many other JX-sysex specialities.
Hi robohymn, interesting that you don’t need to disable MIDI-thru. I think the MKS-70v is not that bad. It is quite a different concept which limits its functionality. For instance you can eiter send or receive data but not both at the same time. This way a MIDI feedback loop is impossible. I think the price is quite ok. But, yeah the opuswerk-panel should cost about 60€ when compared.
And now for something completely different: my Vecoven PWM-Mod-kit has been shipped! Yess! :-))
Edit: Just saw, that Fred published a list of the new features:
http://www.vecoven.com/superjx/pwm/index.html
omg! The SuperJX, already rich on parameters will become UberJX :-). Implementing all these parameters in the panel will be a bit of work.So it was the third possibility: I don’t have a clue when it comes to sysex. My posts may not make much sense, sorry for that.
With Reaper I have to disable all midi-thru options in the Ctrlr Panel otherwise it will do a feedback-loop. I cannot use the “input from plugin host” this seems not to pass sysex data. But selecting the Input from the Midiinterface works fine. On the other hand “output to plugin host” works well. Maybe this is information is of some use for some people.The Keymode does not update with my MKS70 even with the new panel. Maybe this is due to my firmware v1.08. Apart from this all parameters seem to update. At this state the panel is really useful, much better than the editor from vst-plugins.de.
@opuswerk: here is a dump changing a patch on the MKS70.
About the Keymode issue: I found another editor, looks nice, costs about 20€ but there is a demo version where keymode is implemented (the demo lacks some other essential parameters). I wanted to record the code that it sends when changing keymode but until now I did not managed to get it. I am using Reaper at the moment which is really great for the price but I still have to get familiar. I will keep trying but maybe you get this much faster yourself:http://www.vst-control.de/MKS-70v.html
By the way: I am still using MKS70 v1.08 firmware, MidiexpressXT(first usb ver.), Cockos Reaper as VST-Host.
Edit: Strange, I tried to read the data with the “verbose” verson of your dump. But either I did something wrong or these dumps are quite different (or – 3rd possibility – I am not able to read sysex at all). Here is how I made the dump step by step:
1.) Let the Ctrlr Midi Monitor listen to INPUT (raw data).
2.) Change a Patch on the MKS70 – e.g. form A1 to C4
3.) Wait until nothing more happens in the Midi Monitor, copy/paste in a textfile.I finally got my mks70 connected to the pc. Had to fight with midi feedback loops on my old midiexpress but now it seems to work. This is really well done!
@opuswerk: do you mean to load a patch with the editor and record the data? I did this. Textfile attached.Cheers
Hi, it is great to see you guys working on the panel.
@superlewing: (Ah, another capital citizen)…Yes it’s true, the MKS-70 has already an impressive set of parameters. And yes I too definitely have still a lot to explore on how the parameters interact with each other.
@opuswerk: I am waiting for the kit. It should be shipped shortly. Fred told he was quite overwhelmed by all the requests. So he is unsure what he will do when the first batch is finished. But I think there will be some way for people who absolutely want the kit. Also, I am still missing a comprehensive documentation of all the new features. We can meet on tuesday if you want, but I haven’t much to show you apart from a tiny studio that is an absolute mess. But maybe I can get some progress this weekend.Yeah, of course I forgot the french capital of our vast country – pardon monsieur :))
I do live in Bern the capital of Switzerland (no, the capital is not Zurich nor it is Interlaken 🙂
Looking forward to receive Fred’s kit. I will keep you informed. But I won’t hurry things. Although extensively betatested the PWM-kit is still an early bird. Actually there is just a basic wiring guide available. I attached it to this post, so you can look for yourself.
I would argue that soldering is much easier than programming a nice panel like yours 😉 It really depends on the tool. I got this (german site but you get the point):
http://www.elv.ch/profi-100-w-loet-entloetstation-lf-8800.html
With this one soldering is a breeze. The desolder pump is great too. I wouldn’t want to desolder a chip without this. I am far from being a “good tech” – just a hobbyist. Anyway – I make you (of course superlewing too) the offer to do the soldering work if you want. Apart from desoldering the old CPU it seems quite an easy task. You just need a little patience. You would have to send the boards to switzerland (where I live).
But lets take it slowly. I have to successfully mod my own MKS-70 first.
Hi,
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.
Ah I see. This is quite sophisticated. I have to say that I cannot test it because I am reorganizing my studio at the moment.
So you guys won’t do the PWM-Mod and therefore won’t enhance the Ctrlr-Panel. No problem.
@opuswerk: sure, there are sometimes more important things in live. Wish you and your family all the best.
@superlewing: the mod is indeed not the easiest one. Desoldering the CPU worries me a bit too, but I have a good soldering/desoldering station which I think is mandatory.Here some copy/paste from the Gearslutz thread – for now that’s all I know about the additional features. To me it looks too good to be ignored:
– 4 envelopes (2 multi-points, 2 ADSR), all loop-able (faster envelope *is subjective*, ask the beta testers)
– new waveforms for the LFO
– a 2nd LFO, can be modulated by LFO1 (and LFO2 can be modulated by LFO1, so you get LFO cross-mod)
– DCO PWM waveform (if daughter boards are installed)
Another quote where Quavermass is writing about faster envelopes:
There are many parts to this answer…Firstly Fred has diched some of the timing that was imposed by the 100 percent utilised 8031 cpu (which could just about run the soundboards)…..the effects of this were that some voice updates got differing amounts of time to update the DAC/CV`s to drive the synth…thus some sloppy envelope action, there were other subtle artifacts which were found and cured with Freds new software which would lead you to think that the envelope software was to blame (DCO phase problems etc)
Secondly..the “New” envelopes have the six stage Time/Level format, Identical to those in the Alpha Juno synths…with these you can set your own slope to the attack and decay times….I have found that a Zero attack to full on T1/L1 and playing with the T2/L2 for a very short decay to a lower level will give a nice MKS80 type “Spike” in your sounds…
Finally the way all these new parameters interact with extra routings,LFO crossmod and LFO 1 AND 2 can be applied to the VCF (as well as aftertouch,velocity etc)..so a light touch on the parameter levels..and a little self control will make this synth sing…..start cranking things up and you will get some truly odd SFX type sounds or saturate the DAC/CV and end up with the same old JX stuff
…
LFO can Free run,sync to first keypress or per keypress.
…Hi opuswerk and superlewing. Nice that someone is working on a panel for the MKS-70. Maybe you know that Fred Vecoven’s PWM-Mods are about to be shipped to endusers (like me). There are a few other editors around for the MKS-70. With firmware 1.08 some are working quite nicely.
But opuswerks panel will be the easiest to implement the new PWM parameters quickly. If nobody is doing it I will have a try myself. By the way – Fred’s firmware (I think since v.3.0) allows of programming by CC’s instead of Sysex. Both should work, but to me CC looks easier.
First I will have to fit the PWM-Mod. If I manage not to brick my MKS-70 while modding I will have a look into opuswerks panel.
So far thanks for your work!
