TK.

Thanks! :) And here's another one: MIDIboxSEQ V4.064 ~~~~~~~~~~~~~~~~~ o corrected tap tempo function [/code] Best Regards, Thorsten.

Yes... and you don't need a (complicated) library to generate XML, just output the text into a file. Example: my $outfile = "myfile.xml"; my $dcolfovalue = 10; my $dcopwmvalue = 20; open(OUT, ">${outfile}") || die "ERROR: cannot create ${outfile}!\n"; print OUT <<HERE; <?xml version="1.0" encoding="UTF-8"?> <tal curprogram="55" version="1"> <midimap> <map param="14" controllernumber="1"/> </midimap> <programs> <program programname="Startup" category="Lead" dcolfovalue="${dcolfovalue}" dcopwmvalue="${dcopwmvalue}" ... </programs> </tal> HERE close(OUT); [/code] replace the "..." by the additional parameters (I think that you got the point) And use variables instead of static numbers - the variable values have to be derived from the SysEx... somehow. And see http://www.perl.org for free books about perl which will help you to learn this (simple but powerful) programming language. Especially the "perl cookbook" gives a lot of code snippets for many purposes. Alternatively use the docs which are already installed on your computer (type "perldoc") - I learned perl based on these manuals. Best Regards, Thorsten.

Hast Du die DIN/DOUT Module eigentlich schonmal "normal" getestet, also im default MIDIO128 Setup? (einfach die SD Karte entfernen...) DIN: wenn ein Eingang mit Masse verbunden wird, sollte eine MIDI Note gesendet werden DOUT: laesst sich am einfachsten ueber das MIOS Terminal testen, tippe bspw. mal "set dout all 1", "set dout all 0" oder "set dout <pin> 1" (<pin> von 0..127) Gruss, Thorsten.

Did you already try to contact the developer of this software? You need to know how the values are scaled in this XML file in relation to a Juno106 I guess that writing a conversion script would also be interesting for him... Best Regards, Thorsten.

The reported issues have been fixed in v4.063 Best Regards, Thorsten.

It's fixed in v4.063 Best Regards, Thorsten.

Question: are you using Wilba's Panel? And how do you tap the tempo - with MENU+PLAY, or in the BPM page? Best Regards, Thorsten.

The new release is available now! :) Aside from midilab's bugfix we got following changes: MIDIboxSEQ V4.063 ~~~~~~~~~~~~~~~~~ o The "Guide Track" now synchronizes tracks and pattern changes independent from the "steps per measure" option o it's now possible to change or disable a guide track from a song position entry o the "RATOPC" (restart all tracks on pattern change) option now resets the track synchronously with the next step o the clear button now clears the track immediately (2 second delay has been removed). Please discuss in the MIDIbox forum if you don't like this change. o the copy/paste/undo functions now also copy the track and drum instrument names [/code] Best Regards, Thorsten.

Ok, no problem! :) The behavior of the Single Mode is now changed in v3.009: http://www.ucapps.de/midio128_changelog.html Best Regards, Thorsten.

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. Best Regards, Thorsten.

Shipped today: woluf Jojoce Fr@nk joma2 sneakthief Will be shipped once I got the money: Sampas Elektruck Best Regards, Thorsten.

No problem, I can provide signed and unsigned format + the desired min/max range. 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. :) Yes, all displays which are listed at the MBHP_LCD page are supported. :) Best Regards, Thorsten.

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: 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) :) Best Regards, Thorsten.

Well, either a single CC value will apply the pattern to a column, or to a row. From my point of view it's like rotating the matrix by 90°, therefore I used this term. Best Regards, Thorsten.

Hallo Alexander, Du hast die Matrix auf die jeweils vierten Shift Register gesteckt - war das Absicht? Gruss, Thorsten.

definitely not intended. To make this clear I added following topic to the "Known Limitations" section: > no support for big GLCDs, no support for touchpanels. Re-inventing Lemur, an iPad or similar tablet PC is out of scope. > However, second-hand iPad1s are cheap today, and you could connect to the MBNG via OSC Already considered! :) > Storing/Restoring snapshots of the configuration (e.g. to use the controller as synth programmer with patch storage) > SysEx receiver/dumper to store and "fire" SysEx dumps to/from SD Card you will also like this one: > "Morhp" function to fade smoothly between two snapshots Best Regards, Thorsten.

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. :) Specs: http://www.ucapps.de/midibox_ng.html 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. :santa: Best Regards, Thorsten.

Really great design! Finally a simple & newbie-friendly solution which will be useful for many projects! :) I will definitely support it in the upcoming MIDIbox NG, and also in MIDIbox CV V2 While writing this I noticed that I actually need three PCBs - one for MBCV2, and two others for MBNG because 16 encoders won't be enough for my usecase - I added myself to the list and of course I will pay for the PCBs! :) Best Regards, Thorsten.

Is it really required to provide 0..10V for controlling VCOs? This was also my first assumption at the time I started with the MBHP_AOUT module and searched for DIY solutions in the web to get a basic understanding about this topic. But in the last years I got my hands on analog synths which always provided a TUNE or FINETUNE knob to set the basic offset. From this offset it was possible to play keys from -5 to +5 octaves. Some of these synths even didn't allow to play the lowest (audible) frequencies without a negative voltage. So: which synthesizer (or VCO module) really needs the positive 0..10V range? Best Regards, Thorsten.

Hm... SysEx transfers are working correctly with the Microsoft driver when all 4 ports are enabled, that's interesting! Please continue analysis - it gives me some hope that we could get rid of the Korg driver workaround. Best Regards, Thorsten.

Alright, I analysed the file and think that it's (more or less) invalid, because after the header and the first track there is an unknown identifier. E.g. Quicktime @MacOS also refuses to play this file... but it can be opened with Logic Studio. However, since the first track is available (and format 0 files only contain one track...), this error is ignored now and your .mid file will be played! :) I also fixed the other two issues in version v3.008: http://www.ucapps.de/midio128_changelog.html Best Regards, Thorsten.

I just doublechecked this with my own MBSEQV4L by using MIDI IN2/OUT2 - it works. There are two possible reasons: 1) an unexpected dependency on IN3/OUT3 - could you please check the transfers with IN1 or IN2? 2) the way how MBSEQ forwards SysEx data conflicts with the MIDI driver? The "standard" module/midi_router isn't used by this project, since there is not enough RAM to buffer incoming SysEx streams. Instead, SysEx data will be passed bytewise to the host in SEQ_MIDI_ROUTER_ReceiveSysEx() This method works (at least) fine under MacOS I remember that you are using the USB MIDI driver from Korg... are you able to check the transfers with the Microsoft legacy driver? (in this case you probably have to reduce the number of USB ports to 1 again... but it's just to get a better understanding of the issue) Best Regards, Thorsten.

Hi, did you stuff the J15_S jumper to select the 5V option? Without this jumper buttons and LEDs won't work correctly: Guide: plug a MIDI keyboard into the MIDI IN socket, a MIDI synth to the MIDI OUT socket (or route it from your PC to the USB port of MBSEQV4L), press the "RecLive" button, press "Play" and start to record a nice sequence. The button functions are explained at this page: http://www.ucapps.de/midibox_seq_lite.html Best Regards, Thorsten.

@Frank: I added your request to our secret GM5x5x5 preorder list which will be passed to Nils. To all: GM5 chips are SOLD OUT! I will hold back two GM5 chips for the case that somebody screwed up his soldering work. And the remaining GM5 chips for the However, since ca. 1750 chips have been spread over all 5 continents meanwhile, chances are high to get spares (or even prebuilt units) in the Fleamarket Best Regards, Thorsten.

Hi Pete, welcome to the forum! :) I haven't expected problems with Type 0 files, on the other hand I never tried this format. Could you please attach an example to this thread, then I can check this tomorrow. Best Regards, Thorsten.