palm38 wrote:palm38 wrote:you might be able to do this via NOTION 4 External MIDI staves without needing to do ReWire 2
This sounds interesting!
This can be a good solution for your specific needs . . . 
Instead of trying to control Logic Pro 9 via ReWire 2, you will control and play Logic Pro 9 virtual instruments via one or more NOTION 4 External MIDI staves, and this is separate and independent of ReWire 2 . . .
DETAILS AND THOUGHTSNOTION 4 provides External MIDI functionality, and this is done in score setup, where you will find a button in the lower-right corner for "External MIDI" . . .
The way it works is that the music notation is provided on an External MIDI staff, and you can have several of them, where what happens is that the music notation is sent in MIDI format to either (a) an virtual MIDI device residing and running on the same computer or (b) to an external MIDI device, which typically will be something like a physical MIDI keyboard synthesizer . . .
As an example, I did some experiments with NOTION 4 External MIDI staves and used them to control and to play virtual instruments in Reason 6.5 and Reason 7 (Propellerhead Software), and I did this at first without doing a ReWire session, as I recall, but later I added ReWire, since ReWire handles MIDI synchronization, but I need to verify this, because I might used ReWire all the time . . .
On the other hand, I also did an experiment where Digital Performer 8 was the ReWIre host controller and both NOTION 4 and Reason 7 were ReWire 2 slaves, but at the same time the NOTION 4 score had External MIDI staves that were controlling Reason 7 virtual synthesizers, and this worked nicely, hence I think that the NOTION 4 External MIDI functionality is separate from ReWire, per se . . .
Testing this with NOTION 4 and Reason 7 requires doing everything in specific order, even if there are no ReWire channels defined in the Reason 7 project, because if NOTION 4 is started first, it is a candidate to become the ReWIre host controller, and Reason 7 only acts as a ReWire slave (unless being able to act as a ReWire host controller is a new feature in Reason 7, which is unlikely but could be possible and is something I need to check) . . .
However, if Reason 7 is started first and then NOTION 4 is started, I think this scenario might isolate the ReWire aspect . . .
And I just did this test, and the results were as predicted, where to be specific I started Reason 7 first and opened the test project that has two virtual synthesizers which are connected with a "virtual MIDI cable" to NOTION 4. Then I opened NOTION 4 and played the song using the NOTION 4 transport, where the result was that the Reason 7 virtual instruments played correctly but the Reason 7 transport was not slaved to the NOTION 4 transport, which is the clue that there is no ReWire 2 session, since Reason 7 only acts as a ReWire 2 slave, not a ReWire 2 host controller, and by starting NOTION 4 after Reason 7, if NOTION 4 is acting as a ReWire 2 host controller, it is not aware of Reason 7 as a candidate for being a ReWire 2 slave, which even though it is a bit confusing makes sense if you think about it for a while, because if in this specific scenario Reason 7 became a ReWire 2 slave after it was started, then one would expect NOTION 4 acting as a ReWire 2 host controller to be able to control the Reason 7 transport, which is not what happens, hence I am confident that the External MIDI functionality in NOTION 4 is independent of ReWire 2, although when ReWire 2 is happening, there are benefits in terms of gaining automatic MIDI synchronization, and this also makes sense when one considers that NOTION 4 can be the only digital music application running and can control external physical MIDI keyboard synthesizers via NOTION 4 External MIDI staves, where in this scenario ReWire 2 is irrelevant . . .
In other words, I think the following bits of information are accurate:
(1) NOTION 4 External MIDI functionality is independent of ReWire 2, such that ReWire 2 is not required to use the NOTION 4 External MIDI functionality . . .
(2) However, if activated, ReWire 2 can enhance the functionality of NOTION 4 External MIDI staves with respect to virtual instruments communicating via a "virtual MIDI cable" due to the ability of ReWire 2 to handle MIDI synchronization as well as coordinating the various transports of digital music production applications participating in the ReWire 2 session
For reference, when I refer to "viritual MID cables" I am referring to the IAC Driver that comes with Mac OS X and its ability to create software communication links, "cables", or "pipes" between MIDI applications for purposes of sending and receiving MIDI data on the same computer, such that in this example if you want NOTION 4 to send MIDI data to Reason 7, then you create a "virtual MIDI cable" using the IAC Driver and then use this "virtual MIDI cable" to connect NOTION 4 to Reason 7 . . .
The "virtual MIDI cables" are created on the Mac using the Audio MID Setup application in its MIDI window, where basically you need at least one IAC Bus and the IAC Driver needs to be online. Once this is done, you can create the specific connections in the digital music production applications . . .
More specifically, once you have at least one IAC Bus with a channel assigned, then when you run NOTION 4 you will enter score setup and create an External MIDI staff, which you assign to the MIDI Port and MIDI Channel for that MIDI Port, where MIDI Port and channel need to match the MIDI Port and MIDI Channel that you specified for the IAC Driver's IAC Bus in Audio MIDI Setup . . .
Then, in Logic Pro 9, you will connect the virtual synthesizer to the IAC Bus and IAC Channel, where you might be able to give it a special name, but perhaps not . . .
And in this scenario, even though NOTION 4 is not the ReWire 2 host controller and Logic Pro 9 is not a ReWire 2 host controller or slave, hence NOTION 4 is responsible for its audio generating and playing and the NOTION 4 transport only controls NOTION 4, what happens is that since the music notation for the Logic Pro 9 virtual instruments being controlled and played via NOTION 4 External MIDI staves are playing notes based on their sequential appearance in the NOTION 4 score, everything is synchronized, because what happens is that no matter where you start in the NOTION 4 score, the notes for the virtual instruments in Logic Pro 9 are sent in real-time and in this scenario Logic Pro 9 simply plays the MIDI notes and commands that it is sent, so for example if you start at the beginning of the song, then Logic Pro 9 is sent the music notation for its virtual instruments beginning at that time in sequential order, and it plays the music notation in real-time so that everything is synchronized, but is you start at measure 22, then Logic Pro 9 starts receiving the MIDI stuff at that point, and again Logic Pro 9 just plays it . . .
I have not done this experiment with Logic Pro 9, but I did it with Reason 7, and it works as predicted. As time allows, I will do the experiment with Logic Pro 9 to verify that it works this way with Logic Pro 9, although I think it is reasonable to suggest that it works the same with Logic Pro 9 . . .
Explained another way, when one uses a NOTION 4 External MIDI staff, it makes no difference whether the MIDI instrument being played is (a) a real external MIDI keyboard synthesizer connected to the computer via an external MIDI interface and real MIDI cables or (b) is a digital music production application running on the same computer and connected with a "virtual MIDI cable" via the Mac OS X IAC Driver and one or more IAC Buses with appropriate IAC Channels, which is fabulous . . .
Fabulous! 
P. S. I did a quick test using the Logic Pro 9 "Instrument" template, which loads a bunch of Logic Pro 9 instruments and has each one set to listen and to respond to MIDI, and it works very nicely with NOTION 4 External MIDI staves, where the specific sequence was first to start NOTION 4 (64-bit) and then to start Logic Pro 9, where when Logic Pro 9 starts it presents a warning that it will not function as a ReWire host controller or slave, which is fine so ignore the warning, and then the Logic Pro 9 project continues to load, and there are 20 or so virtual instruments, all of which work and respond to the music notation sent from NOTION 4 via its External MIDI staves, but since the Logic Pro 9 project is configured generically, to audition each instrument you need to click on its track in the Logic Pro 9 Mixer, which is a handy way to do it for example purposes . . .
In practice, you will provide the specific IAC Bus and IAC Channel(s) for each Logic Pro 9 virtual instrument rather than setting all of the Logic Pro 9 virtual instruments generically, but this is easy to do, and it works without needing to use ReWire 2, hence if your goal is to be able to play Logic Pro 9 virtual instruments from your NOTION 4 score, then you can do this via NOTION 4 External MIDI staves
without needing to do anything with ReWire 2, and this is very easy to do on the Mac, for sure . . .
For sure! 
P. P. S. I will make a short video on this later, perhaps tonight, but at this point I have no doubt that it works, where for reference you also can do this with any virtual instrument that has a standalone player application, hence in this respect Logic Pro 9 is just the "player app" for its virtual instruments, and it plays whatever the connected NOTION 4 External MIDI staff tells it to play, where to be specific you can have multiple NOTION 4 External MIDI staves, hence are
not limited to just a single such instrument . . .