John_W._Couvillon Posted December 19, 2006 Report Share Posted December 19, 2006 HelpWould someone please explain the impact of this revision. I think that I understand what it does but am not sure.Thanks,Johnc Quote Link to comment Share on other sites More sharing options...
audiocommander Posted December 19, 2006 Report Share Posted December 19, 2006 there's a changelog.txt included in every archive.regards,MichaelMIDIO128 V2.1d~~~~~~~~~~~~~~ o MIDIO SysEx ID is now automatically derived from the MIOS Device IDMIDIO128 V2.1b~~~~~~~~~~~~~~ o the initial polarity of "toggle status" was wrongMIDIO128 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 0xffMIDIO128 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 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.zipMIDIO128 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'] Quote Link to comment Share on other sites More sharing options...
Per S Posted December 22, 2006 Report Share Posted December 22, 2006 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 0x02The 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. Quote Link to comment Share on other sites More sharing options...
John_W._Couvillon Posted December 24, 2006 Author Report Share Posted December 24, 2006 Per S,Thanks,I'll try it. Should make thanks much easire.johnc Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.