Meanwhile I’ve a clear vision how the upcoming MIDIbox NG project should look like.
It will replace the PIC based MB64, MB64E and MBLC projects by a technical up-to-date and especially more flexible approach in the hope that even newbies without programming skills will be able to customize the controller for their needs.
I’m open for discussions - implementation will start in December (however, most of the routines are already available since they are part of MIOS32 or unreleased applications) - therefore the first beta version will probably be available before christmas.
Will it be possible to have a *large* number of LCD’s?
I’ve always felt that every control element needs a programmable label to identify it and give feedback as to it’s current state.
An example might be an array of 64encoders with a 2*40 LCD for every 4,6, or 8 knobs, that’s a total of 16, 12, or 8 LCD’s. I will surely build such a sick puppy!
Will it be possible to have a *large* number of LCD’s?
I’ve always felt that every control element needs a programmable label to identify it and give feedback as to it’s current state.
An example might be an array of 64encoders with a 2*40 LCD for every 4,6, or 8 knobs, that’s a total of 16, 12, or 8 LCD’s. I will surely build such a sick puppy!
Yes, it will be possible to connect up to 8 CLCDs or GLCDs.
And it will be free definable how and where “control elements” (buttons/encoders/pots) output messages.
Example for a minimal controller:
Sysex+NRPN (incl nonstandard) support ?
Receiving & sending SysEx and NRPN will be supported.
E.g. I’m planning to create a programmer setup for Waldorf Blofeld (SysEx), and I will also create a setup for sammichSID (NRPN)
Will it be possible to send “negative” values via nrpn ? (Essentially just Alesis/Akai f*cking with anyone trying to make a editor for their products)
No problem, I can provide signed and unsigned format + the desired min/max range.
Apparently Alesis/Akai have managed to deviate quite a bit from the standard, not limited to :
"MIDI insists MSB is sent for 7 bit NRPNs
Interesting, from where did you get this information?
I only own an older version of the MIDI spec (v4.2) which doesn’t clearly specify the value format. It gives the master tuning RPN as an example, where the value is located in the MSB, and the LSB is declared as “don’t care” - but the spec doesn’t say that this rule should also be applied on custom NRPNs
However, thanks for the hint anyhow!
When potential differences are considered during the first implementation, enhancements (even more exotic formats) will be a no-brainer in future.
I own a Roland XV-5080 which is a bit like like a JV-xx, only with more sounds. I hope it will be possible to define your way of editing patches/banks/rhythm sets. There’s a great page that explains the somewhat convoluted hierarchy employed by the JV-90, most likely all JVs, XVs, Fantoms and “new Jupiters”/Integra etc. It would be interesting if it was possible to define text lists on the SD-card with default patch/wave/drumkit names for the various expansion boards since some of these synths address these cards depending on the slot the card is installed in. That way it would become possible to load sysex, change the destination card slot to fit your particular synth and upload it.
I haven’t looked, but I assume that there’s a similar story for Yamaha Motifs, Korg Tritons, Kurzweils, Ensoniqs and E-mu boxes from the 90’s onward. If someone was ambitious he or she could make a programmer for an MR-Rack, a Fantom-XR, a Motif-XS or… Well. Lots of work :frantics:
No problem, I can provide signed and unsigned format + the desired min/max range.Interesting, from where did you get this information?
AWESOME! <3
Now, I got this information while researching the Miniaks apparently really zany Midi/NRPN spec, so it’s not guaranteed information (Hence the quotes around the entire block)
There generally seems to be a cr*pload of “undocumented/meh, let’s just do it our way” going on with a lot of things that are Midi related.. Blarhg..
There generally seems to be a cr*pload of “undocumented/meh, let’s just do it our way” going on with a lot of things that are Midi related.. Blarhg..
I agree!
Also at other places the (30 years old) MIDI spec is sometimes not precise enough and gives too much room for interpretations, which then results into complex software which has to consider many special cases.
I just read the part where the MB-NG is used for a DIY keyboard. Does that mean that the planned (direct) controller-support (pots, encoders, switches..) for the MB-KB project is stopped?
If so, is there a technical reason for it or is it just an economic decision (save development resources)?
How would you link the two cores? Simply via midi (bi-directional) or is there another way?
I just read the part where the MB-NG is used for a DIY keyboard. Does that mean that the planned (direct) controller-support (pots, encoders, switches..) for the MB-KB project is stopped?
I’m not TK but I can say that reading just a part will more often than not get you things in the wrong way. So, no, it is not stopped, in fact most of it is already there.
I just read the part where the MB-NG is used for a DIY keyboard. Does that mean that the planned (direct) controller-support (pots, encoders, switches..) for the MB-KB project is stopped?
If so, is there a technical reason for it or is it just an economic decision (save development resources)?
How would you link the two cores? Simply via midi (bi-directional) or is there another way?
cheers
Lars
I’m not TK but I can say that reading just a part will more often than not get you things in the wrong way. So, no, it is not stopped, in fact most of it is already there.
Maybe I read something wrong (or I’m just ignorant)… but the confusion to me is that the MB-KB appears to have a plan for functionality that overlaps the MB-NG quite a bit. So for people who just want a custom keyboard controller with a fist full of knobs and buttons, what are the limitations in the MB-KB (assuming a future ver. supports 128 pots + a bunch of DIN/DOUTs), that would necessitate building a MB-NG to go with it? Is it just fewer DIN/DOUT’s, or something else?
Either way I’m stoked that the MB-NG is out soon! The news has finally got me off my ass to drill my panel. This will be the best Christmas present Thanks TK!
I’m also not TK, but would think that seeing the functionality of the KB interface is working (and well by the looks) that the interface is reasonably modular and can be included with various midibox configurations with different benefits and trade-offs.
I get my 2 Keybeds (61 keys) from the local Doepfer agent next week. Cant wait to build my custom dual manual keyboard!
