What is the best way to deal whit a big amount of MIDI data Input ?

[cybercharles]

Hi

What is the best way to deal whit a big amount of MIDI data Input ?

I have many MIDI data to deal with my work space. MIDI data come IN from external machine or by virtual link like MIDI yok between LIVE and USINE.

I want to know what is the best way to drive this information at the inlet of USINE. The purpose is optimizing the treatment of this information.

For example what is preferable?

-using one inlet of the MIDI IN setup and using filter module (by channel, controller…) in the patch
-using as many inlet as it possible in the SETUP and making a selection at the input of the track

Other question: is it intelligent to sort data by type ? for example having only NOTE input, only Control Change input and so on…

Is MIDI data treatment having priority? For example MIDI note pass in the treatment before control change or program change?

This questions are very acute … I hope somebody have answers!

All the best for 2010

charles

[23fx23]

from what ive tested, it's good to have a small usine bloc size to catch highest midi event number if you use many.
also using sometimes the "unpack" features that will reorder events bloc after bloc on the top parent midi in module.
using several midi inlet from setup allow pre-filtering by devices, but it's not more efficient than one only from what i remember.
and then filtering by type is intelligent for having all the infos for later patching.
relating priority i cannot answer if midi itself has a priorority, but seems windows consider midi as a low priority thread and if you're getting high on cpu, midi can become crasy.

hope it can helps.