![]() Just doing some research on all this and ran across this at, talking about the first Mac Pro 8 core computer:Ĭompared to the original Mac Pro that it replaced, the Mac Pro "Eight Core" 2.8 uses a more advanced architecture with faster and more efficient processors with larger level 2 caches, a more advanced vector engine, faster frontside buses (1.6 GHz instead of 1.33 GHz), faster memory (800 MHz instead of 667 MHz), support for optional faster Serial Attached SCSI drives (with the installation of the Mac Pro RAID card), and two 16-lane PCIe 2.0 slots. I'll post back if I find out anything else. So I'm going to replace the 192 with an Maudio ProFire 610 and see if I get better results. Seems like that could be a bottle neck, since other interfaces work with Core Audio directly, not with some app in between. I've been using my Digi 192 as the audio interface with Logic, which automatically fires up Digi Core Audio Manager. The other thing I want to experiment with is whether or not Digi Core Audio Manager kludges up my system. The latter would of course be processed on the other 3 available cores. I also have 2 ESX and one Space Designer in the session. I have a test loop that has and eighth note scale in octaves that is 4 bars long and that is copied on 26 Rewire midi tracks. And the note density in your arrangement is very critical as well. So the settings are very critical (buffers, Rewire Behavior, etc). But Rewire is basically a plugin, so maybe this helps as well. ![]() Probably a lot of EQ's, didn't say how many AU instruments, etc. Something about at last year's NAMM show they had a DP session running 1000 plugins. If that's the case, he may be getting a hit of extra power with that. In addition, in researching the Web, there were reports that said DP 6 is more efficient in plugin processing than Logic and other DAWs are. And he may have a faster processor than I do (It's all on one core, but my Quad Core is 2.66. Again, Kontakt 3 (what he's using) takes 142 MB of RAM empty while an empty Play takes 230 MB - close to double. So remember that my 5 PLAYS are equivalent to almost TEN of the You Tube guy's Kontakts. When it clogs up, you get the dialog box "The audio engine could not process.". But even with the Logic CPU meter pegged, the audio was playing very smoothly and reliably. BUT the Activity Monitor meter will NOT be pegged. All the Rewire stuff is being processed on one core. The Logic System Performance meter will be PEGGED on one of my 4 cores. If I keep it on Playback, and set the Process Buffer LARGE, and the I/O buffer at 512, I can play pretty smoothly all my Plays. Live makes the latency zero, but will spike the CPU and stop Logic if you have too much going on. Two, you will get a LOT more Rewire performance out of Logic if the Prefs/Audio/Core Audio Tab/Rewire Behavior is set to PLAYBACK instead of LIVE. One, the Audio System Performance meter in Logic does not correlate to the Apple Activity Monitor CPU meter. These have Winds, Brass, and Strings loaded in them, many instruments. I have 4 or 5 Plays loaded in my Bidule that is Rewired into Logic. I'm not at my computer right now but I worked on this all last night. I went back to my Rewired Bidule into Logic session. Has anyone come up with anything on this? Lots of pictures and examples of layouts. ![]() ![]() There's more about this at the Plogue forum, do a search there. This lets you assign a Bidule stream to its own processor. Assuming you have several PLAY "streams", where you have a Bidule midi in going to a PLAY which goes to a Bidule mixer (just for that Play) then you can right click on the Bidule mixer of each individual Play instance and you will see MP Assign. If you are not using Rewire, and are using Bidule only for hosting, you can assign processors in Bidule. If you are using Rewire, the Rewire spec only uses one core (or processor) it is not multi-processor compliant. You are correct, East West's suggestion only works if you are using plugin Plays in the host DAW. Does anyone know why this may be happening, I am on a mac pro 2.66 quad core intel. Problem is: No matter ho many instances I have open of the PLAY engine.one core will spike and the others do nothing (Įastwest says that you have to add more instances of PLAY to access the other cores, I think that is just in plug in mode. I love the concept, and I am hosting all of my EASTWEST PLAY Libraries in Plogue Bidule. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |