FIrechild

I´ve got a response on Gearslutz which was to use a midi plugin in reaper which worked perfectly. It is strange you just cant set up a virtual knob in Logic and assign a nrpn number to it instead of cc.

Did you solve this? I am interested as well, only because the Moog Source is using NRPN 2 for cutoff... When using NRPN with hardware-synths you will see that the timing of MIDI-notes will be as bad as an unquantized row of 16ths played at 180 bpm...meaning if you not need it STAY AWAY from NRPN. The higher resolution thing will be useless with the unacceptable MIDI-timing due the the limited MIDI 1.0 protocol where every single event will be sent in serial meaning they will arrive late as soon as you send more than simple MIDI on offs.

There is a MIDI script for Reaper that is splitting Polyphonic Aftertouch to different MIDI channels and then converting Poly AT to Channel pressure. A great use for this is to play with Polyphonic Aftertouch on Oberheim Xpander. You have to edit the script to make a round robin on 6 MIDI channels instead of 16. http://forum.cockos.com/showpost.php?p=1245297&postcount=58 However I thought it was based on javascript but I had no luck just pasting the script to the Logic script plugin. Here is a video when I am playing live on a Roland A-80 controlling the Oberheim Xpander with Poly AT .

I have a computer that is still on 10.6.3 for some compatibility reasons. However I´m looking for the latest logic version running on 10.6.3. I have found 9.1 but I think 9.1.5 will run on 10.6.3 so if someone can post a link or something I would be really glad !

This 9.1 update is even better than the 7.2 to 8.0 update! Best minor update so far!

You are getting out of RAM. Look at your activity monitor and you will see that your virtual RAM is reaching 3 Gb and that´s a limit for 32 bit applications ( logic 9 is a 32 bit app). Solution. Don´t use BFD2 which consumes enourmos amount of RAM or use it as a standalone app or in another host like Mainstage. Route MIDI internally using OS X built in virtual MIDI cables, called IAC found in MID and sound settings.

There seem to be the same limit as in Logic 8. 2.3 Gb real memory can turn up to be as much 4 Gb virtual memory and then no 32 bit application can handle more.

Ok, as already discussed there is an annoying "memory getting low" box at approx 2.0 Gb RAM usage in logic 9 but you can just continue working but then at 2.30 Gb RAM usage this box comes up and you have to quit Logic ! Why! Any workaround? http://evan.se/bilder/memory.png

adef, Logic works this way. Every singel channelstrip has to load all plugins on one single core, so if you are working with just one channel strip, you will see an extremely unbalanced load, but in an ordinary popsong there will usually be more one track, let´s say 8 tracks...now...the load is spread over 8 cores... It is that simple. The turorials in this subject is just confusing. If you are running out of power using only just one channelstrip there is something wrong with the plugins, update to latest versions. The Apple "workarounds" are just piece of crap. Not from real life scenarios. If you have to do such a foolish workarounds you should have an 8 core 0.4 ghz computers which does not exist, exept in laboratories from 1996.

You have already everything under control. The new dual quad Nehalem MacPro´s are not yet fully supported by Logic 8.0.2. The singel quad works great but the duals are confusing Logic due to the virtual cores. Logic has an 8 core limit at the moment but after the next update your machine will be one of the fastest macs around.

Don´t fade out at all when bouncing. When bounced you just double click on the file, sample editor opens and then drag mouse over the end area and choose "fade out".

PLaying around with ONE synth always uses power from one single core. Plugins and AU instruments on a single channelstrip can´t be distributed on multiple cores. Maybe with Snow leopard.