DP and PT do WAY better in this department. You cannot separate the MIDI in that way, unless doing some crazy stuff in the environment which is just absolutely annoying. So if you have 2 MIDI devices that are transmitting say Port A Channel 1 and Port B channel 1, they are merged into the same channel. ![]() For instance, Logic doesn't understand the concept of MIDI ports on inputs. Granted, Logic is amazingly efficient with AUs and no other DAW has ever come that close to me in terms of efficiency, be prepared for the nightmare that external midi is with Logic. While the OS can run 64-bit code, for instance, Chess on leopard is 64-bit, not all portions or libraries from my understanding are 64-bit. Going to Logic is not going to help you as Logic also is limited to 4 Gig, as is Digital Performer. Worse, the OS libraries that PT is using DO count towards that 4 gig as those libraries are mapping into the address space of PT. This means that you are going to be stuck using 4 gig of RAM for PT. While this can all happen as multiple threads, this is not multiple processes. ![]() It loads up like a library into the code space and PT calls and passes data with the functions of the library. The RTAS/AU/VST provides an exact interface that PT (or other hosts) know how to talk with and everything under the hood can be whatever it wants. ![]() To put it further, it works very much like polymorphic object-oriented coding. From what I understand of RTAS is that, like AU and VST, RTAS plugins are a set of code that gets loaded into ProTools within ProTools memory space. So I've not specifically programmed with RTAS, but I have with AU and VST APIs before.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |