Update V2.1d to midio128

MIDIfication
1

Help

Would someone please explain the impact of this revision.  I think that I understand what it does but am not sure.

Thanks,

Johnc

2

there’s a changelog.txt included in every archive.

regards,

Michael

MIDIO128 V2.1d


   o MIDIO SysEx ID is now automatically derived from the MIOS Device ID

MIDIO128 V2.1b

   o the initial polarity of “toggle status” was wrong

MIDIO128 V2.1a


   o "program change" and "channel preassure" now sent correctly

   o the 42th and 84th DIN event now sent correctly

   o proper initialization for the case that the DOUTs are inverted

     or the DINs are not inverted

   o change in default meta event handler (midio\_meta.inc):

     nothing will be sent if first byte is 0xff

MIDIO128 V2.1

~~~~~~~~~~~~~

   o three new SysEx commands have been implemented to simplify

     the configuration data up- and download. It's a block

     oriented format and therefore doesn't require delays between

     every byte anymore. This means' date=' that data uploads can

     now also be realized without the use of MIDI-Ox so long the

     SysEx tool allows to insert delays between every block

     ("Delay after F7") - it should be 750 mS - thats the

     same requirement like for MIOS uploads.

     More infos can be found here:

        [http://www.uCApps.de/howto\_tools\_mbsyx.html](http://www.uCApps.de/howto_tools_mbsyx.html)

   o the mk\_midio128\_syx.pl script has been updated to support the

     new upload format. It can be downloaded from here:

        [http://www.uCApps.de/midio128/mk\_midio128\_syx.zip](http://www.uCApps.de/midio128/mk_midio128_syx.zip)

MIDIO128 V2.0 - MIOS based version

   o the complete MIDIO128 firmware has been ported to MIOS and is

     now running on a PIC18F452. For new projects it’s recommented

     to switch to the PIC18F452 because of the higher flexibility,

     but also the update of an existing MIDIbox to MIOS makes sense

     due to the new features - just only the processor and the

     crystal have to be changed. [/quote’]

3

Hi Johnc,

One great advantage with this release is that you can selectively update INI files if you have several chained cores. For example I have three cores with ID’s 00, 01 and 02 chained with Midimerge active. With this release I can send an INI file (SYX format) to one specific core without having to break up the MIDI connection. It requires that you tag the INI file with the core ID and do the conversion to SYX like this:

perl mk_midio128_syx.pl Midi_02.ini -device_id 0x02

The SYX file will only update the MIDIO128 residing in core ID 02.

This wasn’t possible before without manually changing the MIDIO128 and recompile it.

4

Per S,

Thanks,

I’ll try it.  Should make thanks much easire.

johnc