Logic Pro plugin performance

I am having more plug-in performance issues with Logic pro 7.2 version. I have a dual 2gig with 4mg of RAM. I am using BFD, Ivory, Trilogy, Hard Core Bass, Chris Hein Guitars, RealGuitar, Motu Symphonic, and MachFive. Even with all tracks frozen, I am having crashes right and left. I have been sending the responses to apple, with and without notes. I never get a response. I not sure they are there. I think they should tell us were the problem is or with what plug-in. Need help… I got out of Pro Tools and moved to Logic Pro because I thought Apple would have a more stable product and I wouldn't have to wait a year after a new OS to get updates. I hope Apple is listening.

I have been working with Logic Pro for about a year with very few problems. I did notices some performance issues start with the 7.2 update. I think the crashes started when I got Hardcore Bass. I have been trying to fine tune Hardcore Bass and have seen some improvements. I have try to add and remove plugins to determine the problem ones, and so far it appears to Hardcore Bass and Chris Hein Guitars.
My real question is why can't Logic tell us more information about a crash i.e. RAM, Plugin or something. I would like to be more helpful in a solution to the problem but I need more information from the application.

Similar Messages

Decoupling of Logic Pro Plugins / Convert them to AUs please.

Dear Logic Pro developers,
Would it be possible to decouple the Logic Pro plugins from Logic Pro in a future version / update?
It would be really fantastic if Logic Pro plugins could become Audio Units rather than proprietary to Logic.
Since Logic is protected by the dongle, the Audio Unit versions could still be dongle protected, but thereby providing Logic users with much more audio possibilities.
Please consider it, please! :))
best regards from berlin

Given that apple invented yet another format for OS X - and then revised it a couple of times - I think the fact that Logic's plug-ins don't support that format isn't the greatest advertisement for AU.
OK, so Apple won't buy that argument, try this: Many Apple app's (FCP, STP LP, etc) use Logic's 'proprietary' plug-ins - but which plug-ins are available in which app seems somewhat arbitrary.
For example, why no MatchEQ in WaveBurner?
Apple, at least all these proprietary, non-AU plug-ins to reside in a shared repository, and allow them to be accessed by all relevant Apple app's. . . .

Mac Pro configuration for the best Logic Pro 8 performance

Hello,
I noticed that sometimes I have little delays playing midi keyboard in Logic Pro 8.
What is the hardware configuration of Mac Pro for the best Logic Pro 8 performance?
Do I need to install any sound card or any additional software?
My hardware overview is:
Model Name: Mac Pro
Model Identifier: MacPro1,1
Processor Name: Dual-Core Intel Xeon
Processor Speed: 3 GHz
Number Of Processors: 2
Total Number Of Cores: 4
L2 Cache (per processor): 4 MB
Memory: 1 GB
Bus Speed: 1.33 GHz
Boot ROM Version: MP11.005C.B08
SMC Version: 1.7f10
thank you,
Vlad

You should definiteley get some more RAM first. Buy another 3 Gigabytes to make it 4 Gigs. The Lateny you're experiencing is due to the Buffer settings within Logic. If you set that to 64 or 128 samples (in the Audio preferences->devices->Buffer) the Latency will improve but it will also reduce the number of Plug Ins you can use at the same time as lower Buffer settings require more CPU.
You didn't mention an Audio Interface which you should obtain if you want to record live Instruments. For the start you can do everything in the Box but the analog minijack Ins/Outs built in your Mac are not really state of the art and you'll improve the sound by getting a good Firewire Interface.
Also get a second/third HD as you should not be recording onto your system drive. It's good to have one drive dedicated for recording Audio and another one for samples/Jam Packs/Loops.

Logic Pro X performance difference between iMac i7 3.5ghz (non-Retina) and the i7 4.0 ghz (Retina)?

Hello - on the verge of getting an iMac - it's for Logic Pro and some video editing with Premiere Pro (don't *really* need the Retina screen though) - i'd just like to get an idea of the performance difference (especially in Logic Pro X) between the quad i7 3.5ghz (non-retina) and the quad i7 4.0ghz (retina)?
I use loads of plugin instruments (incl. big Kontakt libraries) and effects with just a few audio tracks (only ever record max a couple of audio tracks at a time)
Thanks!

I owned the imac and then returned it for the 2.6 MacBook Pro. After using both there is a noticeable speed difference between the 2. Not a huge difference but there is certainly more lag using the MacBook Pro. I found that lots of the lag went away when I attached to an external display though. At the end of the day I think you just need to decide if you need the portability or not. At first I thought I would keep the imac and then get a cheap MacBook Pro to use on the road but the thought of having multiple Lightroom catalogs sounds very annoying to me. Plus all the transferring back and forth. I will say also that I've been getting a lot of freezes in Photoshop on my mbp and weird errors like the sleep wake failure error some people are talking about when connected to a USB device. I didn't have any of these problems with the imac

Evolution MK449C Mod Wheel problem with Logic Pro/VSL Performance Tool

I'm using the latest version of Logic Pro on a new Intel Mac Pro. My controller keyboard is the Evolution MK449C, connected via a USB cable.
When using a Logic Audio Instrument assigned to the ESX Sampler Plug-in (running various samples, mostly from the Vienna Symphonic Library,) Logic's Transport Window doesn't register any modulation information generated from my keyboard.
As the VSL Performance Tool relies heavily on the Mod Wheel info to effect the sounds, I'm at a bit of a loss to spot the solution. When I assign a different conroller to the Mod Wheel, i.e. volume, pan, pitch bend, etc., I can see the info in the Transport Window with no problem, so I know the wheel itself is working okay.
Has either Logic or the ESX got some kind of controller filter, - maybe I've accidently turned something on that cuts out any incoming modulation. Can anyone help?
Thanks
Mac Pro Mac OS X (10.4.8)

It's good to know someone else is having a similar problem (if one can call that good!)
I've been poking around and I've also noticed this: If I create a cello part in Garageband, articulation works everytime I open it. If I take that Garageband song and open it in Logic, articulation still works everytime I open it. The Logic file in this instance is saved as a "Logic Song." I don't know how to tell, but I'm assuming the Logic song is drawing it's sound files from the Garageband song (I don't know how to check that).
However, if I save the newly created Logic song as a project - with all sound files being copied to folders within a master project folder - articulation does not work when I reopen the file.
Strange. And frustrating.
MacPro 2.66 2GB RAM & Powerbook 400mhz "Pismo" Mac OS X (10.4.7)

Need advice about Macbook internal HD and Logic Pro

Hi!
If I use an external Firewire HD for my projects. The Audiofiles gets saved ( recorded ) in the "audio" folder inside the projects folder on the external HD.
Does it have ANY impact on my macbooks ( logic pro's ) performance that the internal HD of the macbook is only a 5400 RPM HD.
Ill try to be silly clear here so u'll understand my question right.
Is the internal Hard disk used in ANY way if the project is on an external HD. Is the internal HD used for playing samples "live" for Ultrabeat, RMX, EXS24 and so on or not or that doesnt matter for performance.
I need to avoid the intern HD so I am wondering what to do. Should I buy a new 7200 RPM HD even if the projects is situated on external HD.
To be uberclear: Macbook, black, intel core duo, 2.0 Ghz, 1 GB intern. 100 Gb 5400 RPM internHd. Logic Pro 7.2.3. External FW HD 7200 RPM. Latest Tiger update.
/ Mikke

yes the internal drive has an impact on performance. this is related to how much RAM you have, but even if you have the max 2GB RAM that you can have in a macbook (or 3GB if they updated it to that like the pros), OSX still uses the system drive for a great deal of swap files. logic does too. it's just the way it all works. back in OS9 days, you may (or may not) remember a thing called virtual memory.. well that hasn't disappeared from OSX as many people think, it's actually built in and always operating under the hood, but it self-manages... there's no need for a user to assign amounts of hard drive for VM, or to assign the memory allocation for applications. OSX does it all by itself, and it does make judicious use of the system drive just to function.
logic also is part of this equation. depending on how you set it up, if some of your exs library is on the system drive (such as the basic library or garage band sounds), then it's possible that logic will access the sys drive at times if you have exs streaming enabled. also, if your freeze files get created on the sys drive, they'll be read from there too.
with all that in mind, the other thing is that the 5400rpm is not really that slow. in fact, if it is a drive that uses the new PMR technology (the 5400s in the latest macbook pro do use this, don't know about the standard macbook), then there have been plenty of tests out there that show it's almost as fast as a 7200rpm longitudinal drive, and under some circumstances, faster.
personally, I ordered a macbook pro with a 7200rpm because I want my system drive to be as zippy as possible for all the fast read/writes that the system does. battery life is not an issue for me as it will always be used in a powered situation. a good review of the 7200rpm drive vs the new PMR 5400s that are the options in the new macbook pros that I read on the net said that the 7200 still does have the slight edge in performance. except, curiously, when the drives are both getting full, at which point they both slow down and the 5400 almost equals the 7200. I wish I could remember the site so I could post the link, it was a laptop review site and they ran their own tests so it wasn't just based on quoted specs.
anyway for me I'm still going to use an external FW800 for audio and sound library, the internal is just for system. I made the choice to go 7200 for the system performance reasons above, but I really don't think you'll be disappointed with the 5400.

Logic Pro quit unexpectedly while using the Logic Pro plug-in

I cannot open Logic at all now. It crashes stright away with the above error heading...!
Can anyone help with this?
Thank you
Simon

It's quite a long report but it looks like the important/relevant bits are at the top although it doesn't cast suspicions over any plug-in as far as I can see:
Process:         Logic Pro [14387]
Path:            /Applications/Logic Pro.app/Contents/MacOS/Logic Pro
Identifier:      com.apple.logic.pro
Version:         9.1.8 (1700.67)
Build Info:      Logic-17006700~1
Code Type:       X86 (Native)
Parent Process: launchd [233]
Responsible:     Logic Pro [14387]
User ID:         1477199388
PlugIn Path:       /Applications/Logic Pro.app/Contents/MacOS/Logic Pro
PlugIn Identifier: com.apple.logic.pro
PlugIn Version:    9.1.8 (1700.67)
Date/Time:       2014-01-20 21:04:00.958 +0000
OS Version:      Mac OS X 10.9.1 (13B42)
Report Version: 11
Anonymous UUID: 7D02E385-EFB3-BAD9-BE08-5F82FA33A7DE
Sleep/Wake UUID: 8BDB4BF9-C601-4482-9B85-3FEE2F646F9C
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGABRT)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000022
VM Regions Near 0x22:
--> __PAGEZERO             0000000000000000-0000000000001000 [    4K] ---/--- SM=NUL /Applications/Logic Pro.app/Contents/MacOS/Logic Pro
    __TEXT                 0000000000001000-0000000000beb000 [ 11.9M] r-x/rwx SM=COW /Applications/Logic Pro.app/Contents/MacOS/Logic Pro
Application Specific Information:
abort() called
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib                  0x94696952 __pthread_kill + 10
1   libsystem_pthread.dylib                 0x98d45167 pthread_kill + 101
2   libsystem_c.dylib                       0x9b55840c __abort + 187
3   libsystem_c.dylib                       0x9b558351 abort + 172
4   com.apple.logic.pro                     0x003e6729 std::ostream& TraceOutContainer<CEvs>(std::ostream&, CEvs, char const*, int) + 3842985
5   libsystem_platform.dylib                0x98d57deb _sigtramp + 43
6   com.apple.logic.pro                     0x005b9175 std::ostream& TraceOutContainer<CEvs>(std::ostream&, CEvs, char const*, int) + 5754357
7   com.apple.logic.pro                     0x005b8809 std::ostream& TraceOutContainer<CEvs>(std::ostream&, CEvs, char const*, int) + 5751945
8   com.apple.logic.pro                     0x005b96d1 std::ostream& TraceOutContainer<CEvs>(std::ostream&, CEvs, char const*, int) + 5755729
9   com.apple.logic.pro                     0x005d016a std::ostream& TraceOutContainer<CEvs>(std::ostream&, CEvs, char const*, int) + 5848554
10 com.apple.logic.pro                     0x005d1d6c std::ostream& TraceOutContainer<CEvs>(std::ostream&, CEvs, char const*, int) + 5855724
11 com.apple.logic.pro                     0x005ae427 std::ostream& TraceOutContainer<CEvs>(std::ostream&, CEvs, char const*, int) + 5709991
12 com.apple.logic.pro                     0x005d2439 std::ostream& TraceOutContainer<CEvs>(std::ostream&, CEvs, char const*, int) + 5857465
13 com.apple.logic.pro                     0x005a97fe std::ostream& TraceOutContainer<CEvs>(std::ostream&, CEvs, char const*, int) + 5690494
14 com.apple.logic.pro                     0x00410d1e std::ostream& TraceOutContainer<CEvs>(std::ostream&, CEvs, char const*, int) + 4016542
15 com.apple.logic.pro                     0x001ccf45 std::ostream& TraceOutContainer<CEvs>(std::ostream&, CEvs, char const*, int) + 1641413
16 com.apple.logic.pro                     0x00616967 std::ostream& TraceOutContainer<CEvs>(std::ostream&, CEvs, char const*, int) + 6137319
17 com.apple.logic.pro                     0x00613735 std::ostream& TraceOutContainer<CEvs>(std::ostream&, CEvs, char const*, int) + 6124469
18 com.apple.Foundation                    0x95e4878b __NSFireTimer + 117
19 com.apple.CoreFoundation                0x95c6b186 __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__ + 22
20 com.apple.CoreFoundation                0x95c6ab43 __CFRunLoopDoTimer + 1395
21 com.apple.CoreFoundation                0x95ce52ad __CFRunLoopDoTimers + 349
22 com.apple.CoreFoundation                0x95c226c3 __CFRunLoopRun + 1779
23 com.apple.CoreFoundation                0x95c21d5a CFRunLoopRunSpecific + 394
24 com.apple.CoreFoundation                0x95c21bbb CFRunLoopRunInMode + 123
25 com.apple.HIToolbox                     0x90d36e2d RunCurrentEventLoopInMode + 259
26 com.apple.HIToolbox                     0x90d36bb2 ReceiveNextEventCommon + 526
27 com.apple.HIToolbox                     0x90d3698d _BlockUntilNextEventMatchingListInModeWithFilter + 92
28 com.apple.AppKit                        0x94f3b5a9 _DPSNextEvent + 1602
29 com.apple.AppKit                        0x94f3aad0 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 119
30 com.apple.AppKit                        0x94f2d35c -[NSApplication run] + 727
31 com.apple.prokit                        0x00fc880d NSProApplicationMain + 353
32 com.apple.logic.pro                     0x0002bad5 DummyConnection::DummyConnection() + 193
Thank you for your time on this...

Classic Analog Arpeggiator sound sample on the Logic Pro Site

Does anyone know how to duplicate the Classic Analog Arpeggiator sample demonstrated on the Logic Pro X site?
http://www.apple.com/logic-pro/plugins-and-sounds/ > Plug-ins and Sounds > Keyboard Sounds > scroll down the page to Arpeggiator and MIDI Plug-ins. The Classic Analog sample is below the Arpeggiator.

What you use for a sound is up to you..... but there are many presets for both the ES2 and the Retro synth you could use with a but of tweaking...
Tip: Play around with the Cutoff and Resonance controls.... in the synth itself or via the Smart Controls if they are assigned...
As for the sequencer pattern....
Set up the midi sequencer like this to get the same sort of pattern at 120 bpm.... starting off from the default, and make these changes as per the screenshot below.
Now play notes at the lower end of the keyboard and you should get something close depending on the synth sound you choose...

Is macmini enough for a musician that works with logic pro and 10 plugin softsynth at the same time?

I use to work with a music platform like garageband or logic pro and at the same time I am working with a lot of plugin software like toontrack, ik multimedia, musiclab, native instruments etc. On my PC which has the same specification as macmini i7 2.3GHz this was a big problem especially when I was selecting effects like reverb, chorus or compressor so I had to export tracks all the time. What is the minimum specs that I should have to work without any problem? Any help will be appreciated.

Welcome to Apple Support Communities
For what you want the Mac, the Mac mini is OK. It has got a quad-core processor that will give you the performance you need and 4 GB of RAM that you can extend to 16 GB, apart from a removable hard drive.
The problem is the GPU, but as the applications you are going to use don't require the best GPU, it will work properly. If you want the Mac mini, go for it. An iMac may give you better performance, but the Mac mini is correct.
If you buy it from Apple, you have 14 days to return the Mac mini if it doesn't work correctly with the apps you need

Logic pro are crashing with plugin

Last week I bought Keylab 49 from Arturia. After installing the software, so now my DAW, Logic Pro 9, started to crash very often. One problem I have not had before on my computers. I use a Macbook with 2.4 GHz Intel Core 2 Duo processor (4GB memory) and a Macbook Pro, 2.3 GHz Intel Core i5 processor (4GB memory). Sometimes it crashes in the middle of a project, but it can not open a project where Arturia Keylab 49 is used as a plugin. Very frustrating when I want to use KeyLabs Synthesizers as part of my project. Both of my computers running OS X Mountain Lion. What's wrong and why it does not work as it should?

It's partly due to the ^&^$# Arturia software.
Try this, see if it helps.
Delete the Logic 10 preferences file AND the shared control surfaces file.
In the Finder, choose Go > Go to Folder from the menu.
Type ~/Library/Preferences in the "Go to the folder" field.
Press the Go button.
Remove the com.apple.logic10.plist file from the Preferences folder. Note that if you have programmed any custom key commands, this will reset them to the defaults. You may wish to export your custom key command as a preset before performing this step. See the Logic Pro User Manual for details on how to do this. If you are having trouble with a control surface in Logic Pro.
then delete the com.apple.logic.pro.cs file from the preferences folder.
Be sure and remove both files. (with Logic not running of course) next time Logic boots these files will be recreated.

Expected performance of logic pro mixing on 13" MacBook Pro?

I am considering the 13" MBP over the 15" because of cost. I could afford the 15" but it is a considerable price jump for me and I am afraid I am just being tempted by the classic "you must buy the fastest of fastest computers" bug. I would rather spend the money saved on an Apogee Duet and external monitor.
I would like to know what kind of performance level I can expect from the 13" base model MBP with 2.4ghz, 4GB RAM and 250GB hardrive.
I would not be recording more than 2 tracks at a time with it, but I would like to be able to take studio recordings of my band and import them into Logic, and have enough processing power to work with 16-20+tracks with effects without it being a complete slug or crashing.
will this base model meet my expectations?
I am coming off of a PowerPC G4 1.3Ghz 14" ibook with 1.3GB of RAM, running Garageband with up to 10 tracks and seeing pretty slow performance but still "getting er done" so to speak.
I am also slightly concerned about buying a 13" because of the 4 year old Core Duo processors, but again. Having the fastest for the sake of fastest is a trap i would like to avoid.
Thank you so much for any insight, guidance, advice and experience you have had with this scenario.

Clintage3 wrote:
It seems to have some weird issue with if you're using a virtual instrument MIDI track, if you have it selected while recording, it gives the disk too slow error.
That is not entirely correct. It really depends on a few other factors too (like what plugins are used/active in the project, AND of course the power needed by the particular instrument of which the track is selected). Sculpture will stress the CPU a lot more than let's say, the ES1. So it is not a given that having a Software Instrument Trackb selected during recording will result in an overload, but if you have overloads with an SI track selected, it'll probably go away when you select an audio- or aux track.
The only reason to have an SI track selected during recording is when you are capturing a complete performance (playing AND singing). when I do that I use a separate project with just one SI track and one audio track and no insert plugins. After capture, I'ld open the (main) project and import those two tracks from the "capture" project.
It is always better to underestimate the performance of your Mac when recording. Even better is to understand how to manage the CPU 'needs' of Logic Pro, like which plugins are "gasguzzlers" (Space Designer, Sculpture etc) and which are relatively light.

Performance issues with Logic Pro 9

Hi,
I'm experiencing quite big performance issues with Logic Pro 9:
bad midi timing and sync, user interface is kinda slowing and less reactive, ...
Mac Pro 2x2.26 Ghz Quad, 4Gb ram, early 2009, shipped with 10.5.6 now upgraded to 10.5.8
Should I upgrade to 10.6.2?
Thanx

Hi,
I'm using the same machine ...
I never get any performance issues
I bought my mac in March 2009 and I was ben ready to work in less that 3 days without issue...
so more details about your setup are required to answare!
4GB ram???
I suggest to check your ram!!!
Ram must be compatible with Xeon Nehalem Try specification!
if you add 1GB of ram from nor clear manufactor.. i suggest to disconnect the addition 1GB RAM
G

After upgrading to 10.7.5 some of my AU plugins can not be validated in Logic pro. (I got error message "Remove property listener". I can not work anymore. What should I do?

After upgrading to 10.7.5 some of my AU plugins can not be validated in Logic pro. (I got error message "Remove property listener". I can not work anymore. What should I do?
VIBAC

I downloaded and installed
OS X Lion 10.7.5 Supplemental Update
and that solved my problem completely. (368 AU plugins now works!)

HOW TO FIX LOGIC PRO CRASHES WITH NEXUS PLUGIN ON MAC OS X 10.6.8 !! =)

After updating my Mac OS X to 10.6.8, my Logic Pro would always crash when opening a project file that uses the Nexus (version 1) plugin...
I spent hours upon hours, LONG DAYS AND NIGHTS trying to resolve the issue searching all over the internet for solutions and NOTHING helped besides the suggestion to upgrade to Nexus 2, which was not possible for me, or downgrade my OS X to 10.6.7 ...which wouldve been a very annoying procedure for me...
SOOOOO....
I dont know why, but my instincts told me to try this solution, out of hope, and it WORKED!!
So i felt like it was my duty to help my fellow Logic Pro users/producers with this annoying problem!!
You can thank me by checking out my music @ FAMEisFAMOUS.com and adding me at:
-Twitter.com/FAMEisFAMOUS
-Facebook.com/AiricFame
HERE'S WHAT YOU DO:
--GO TO APPLICATIONS
--AND SIMPLY MOVE (DRAG) THE ReFX FOLDER TO YOUR DESKTOP (OR ANY OTHER FOLDER YOU'D LIKE, AS LONG AS ITS NOT IN YOUR APPLICATIONS FOLDER)
--NOW OPEN LOGIC PRO AND TRY USING THE NEXUS PLUGIN
--IT'S GOING TO ASK YOU TO LOCATE THE "0TestTone.nxs" FILE
--NAVIGATE TO THE LOCATION ON YOUR MAC WHERE YOU MOVED THE REFX FOLDER
--OPEN THE NEXUS FOLDER / SAMPLES / ROM /
AND THERE YOU WILL FIND THE "0TestTone.nxs" FILE
--ONCE YOU APPLY THAT, TRY TESTING THE SOUNDS IN THE PLUGIN AND IT SHOULD BE WORKING FINE!
--NOW EVERYTIME YOU SAVE, AND REOPEN LOGIC YOU SHOULD BE GOOD TO GO!!
Hope this works for you like it did for me...
Much Love!,
-Airic Fame
FAMEisFAMOUS.com

Hi Airic Fame!
I had just the same problem and tried your way to fix it. WORKED PERFECTLY!!!
thousend thanks!!!! you're a Genius!!
Martin

After Installing Logic Pro X, my Logic Pro 9's 32-bit AUs don't work. The 32-bit bridge doesn't open and run either in my Logic pro 9. My 32-bit AU plugins are crossed out. Help?

After Installing Logic Pro X, my Logic Pro 9's 32-bit AUs don't work. The 32-bit bridge doesn't open and run either in my Logic pro 9. My 32-bit AU plugins are crossed out. Help?

michaelvee wrote:
As an overworked professional, I simply have to consider the very viable options out there. Never thought I'd be seriously considering a Cubase product.
It's a Steinberg product, not a Cubase product.. in case you haven't been paying attention Steinberg developed the virtual instrument for use in it's programs way back in Cubase 3.55.. the plethora of virtual instruments and the advent of low-latency drivers can be directly traced to Steinberg/Cubase development.. Logic also borrowed Cubase's arrange page format back in the 1980's. Cubase has borrowed from Logic to be sure but Steinberg has long been an innovator for many of the things we take for granted today. It was Logic/Emagic who licensed the VST technology and ASIO low latency format to use in Logic 4.xx. It was Apple who adapted VST to it's own AU format. Also, Cubase and Nuendo have undergone a lot more innovation over the past three years, Yamaha has been good as a parent company. Cubase is not Nuendo's little brother by the way, they are very close, same exact audio engine, same robustness, they can exchange files, the only difference being Cubase doesn't have some of the high end post features that Nuendo has. I use both Cubase and Logic and occasionally Nuendo at the University here.. I know both programs fairly well, believe me, both Cubase 6 and 7 can hold their own with any DAW out there, they just don't come with a bunch of ready made loops and preset instruments.
LogicX will never be able to use 32-bit instruments without a third party solution, nor will it ever include the Bridge. At least according to the people I know.

Logic Pro plugin performance

Similar Messages

Maybe you are looking for