There seem to be a few tutorials on how to make a template in Cubase with VEP, but very little with Logic (?). That's probably not a good enough reason to get Cubase instead as I already have Logic Pro X. Having said that, I don't know much about Logic even if I've had it for some years. I have actually more experience with FL Studio than Logic, but Fl Studio on Mac is not ready yet. All I've done in Logic is recording some ideas, and the little I tried with the piano roll and automation was so different from FL Studio that I lost some motivation.I wonder if any of these DAWs are best when it comes to working with VEP?I will have the daw on the master Mac, and VEP is on the slave PC.Is it all about preferences, or is Cubase better as most ppl seem to use that with VEP? I've read that in Logic there's a limit on number of MIDI ports, so each instance in VEP can only have 16 channels. If I've understand it correctly.

Hallo Mc Arnes,

I'm not fully up to date but after having used Logic for a long time I siwtched already to Cubase 2 years ago and just am about goning to start learining it. If basic aspects didn't change (what I guess) than we have the following Pro & Con:

Pro Logic

1) Logic (as optimized for Macs) and especially Logic Pro X (which I dond't use) have a significant better CPU performance as Cubase on a Mac. Just on a PC Cubase gets this or even a better performance. Logic seems to have somethin like the double performance in idle (song not playing) and active modes.

 Pro Cubase

1) As alraedy mentioned: Expression Maps. You can switch articulations manually in the editor (in Logic callerd pianoroll editor)

2) the editor is by far more userfriendly imo, at least compared to old logic pro: Only the fact that though you can draw curves in both (velocity, modwehell etc.) under the notes, in logic it seemde a pain in the a. compared to the way you can draw it in Cubase. And also a little detail but very often needed, that in Cubase you can hit one of the piano notes to check which note you are on (even before your draw a note for example) or select a piano note and all the notes in this line are selected. I have no idea why logic never implemented this obvious stuff. Drawing automation curves is still very bad implemented at least in logic Pro (as I don't know or use logic Pro X)

3) Cubase FOLDER Tracks are great for orchestral templates. Nor Digital Performer, nor Reaper or any Sequencer i know have thos Folder Tracks. In Logic (this is the "funny" part) you can (and unfortunateley I tried) create so called "folder tracks" packing many sequences into one folder AFTER you recorded them and not BEFORE (as in cubase) which doesn't really make much sense. The Folder Tracks are a heaven send I guess. Especially in thos large orchestral templates.

4) Multiple stems: The ability to render audio to multiple stems. For example you can in one step create one Audio for Strings, one for Brass, one for Woodwinds one for melodic Percussion, Harp, Piano, one for not melodic Percussion and one for "Extras" in one go. I'd be surprised to here you can do that in logic meanwhile? Anyone who works with it may chime in.

5) With Logic you have this anoying AU Limitation not being able to use more than 16 Midi channels for one AU resulting in having to open many VE Pro Instances. This resulted in very enoying ONE CORE SPIKES pretty quickly when streaming many voices because even with VE Pro Logic has problems with distributing Processor load which Cubase ironically managed better having VST3. Now I know there are WORKAROUNDS for logic and I used them all. Again precious lifetime wasted in building complicated logic templates to work around the AU limitations and gues what? Again a freaking PAIN IN THE ... you know ... ;) x

6) for composing music to video again i don't know about logic por x but i find ite VERY usefull that when in Cubase you hit the arrow you step 1 FRAME forward and in logic I couldn't manage getting this to work.

So finally I got my huuuuuge Logic Pro template with: 

- Automation work arrounds (routing automation in a diferent way so that it doesn't get mixed up within the midi tracks!)

- AU 16 Channel limit work arounds

- complex routings in logics (very flexible i have to admit) environment even adding some nice "Voice splitters" to create some custom made "Auto-Divisi" Instruments which logic allows

- pre created tracks to pack them in logics folder tracks and beinig able to "unpack" and pack them with key commands quickly

-> And what for I have to ask my self? Month of messing around with work arrounds which in the end apperade desperate intends to not even COME CLOSE to the Cubase features I'd love to imitate in short which are (resumed):

1) Expression maps

2) professionally (easy) editable CC-Curves

3) Track Folders (vs Logic's "folder tracks")

4) Offline Bouncing to stems (propably not even reachable with a workaround)

5) VST3

So I'm more than happy to start with Cubase 6.5 (not even the newest one) even being on a Mac (where Cubase sadly is not optimized for). Any experiences of Cubase users here?  

Well ... ;)

Peter Schwartz and Ski Switcher's approaches remember me of those typical workarounds which require quiet a lot of intelligence and creativity in order to somehow deal with logics shortcomings :/

I highly respect those guys! 

But for us useres wanting to make music instead of prgramming this is one more work around added to my list! Jese i saw that Video and admired the flexibility offered by logics environment. But than again I compare the ELEGANCE of this solution:

https://imgur.com/a/In09e

to this one:

https://imgur.com/a/IDM6Y

... ;-/

Well I don't know but for a user asking in which direction to go and yet being at the beginning I'd say recomend Cubase if THIS is the way things are going with logic. 

Originally Posted by: Ashermusic

Anyway, not looking to start a DAW war, both are fine tools.

Me neither! Also I totally agree with you in Logic being more CPU friendly by far (at least again using those famous workarounds to overcome the 16 Midi-Ch. limit). It's just that I fought that battle for many, many years and am hardly tempted to go this route again. The only real argument for me to go through all that pain was logics CPU efficiency.  

Otherwise I am "angry with logic" >;) and NOT by any means with people like you or all the others who really HELP people working with logic which decide to do so! All my respect! In my opinion you are heros because without the help of all those "environment specialists" and people like you i would have felt lost in the middle of building a logic orchestral template. (There should exist quiet some of my desperate posts from those times and I remember you being one of the few lights here who helped me out! So I'm greatfull for that!! (My "bashing" goes against 'Apple's Logic' as oposed to EMAGIC in my eyes don't really LISTEN any more to musicians needs)

Well never mind, it has to been said that you are one helpfull guy and it is good news to hear about things having changed in Logic. Of course we have to consider that I left logic (not even cared about testing Logic Pro X) and missed all of those developements. So good news for logic fans and of course there is no perfect DAW!

Maybe I'll give it a try with logic one day again under these circumstances. Simply because I am an Mac Pro and OS X Fan! :)

Keep up the good work!  

The only 2 things I dislike about Logic are:

- the inability to display multiple controller lanes at the same time below the piano roll. 

- the inability to unload tracks from memory (DP does this with one button click, Cubase with a couple)

Otherwise I love Logic.

To the OP re articulation mapping in Logic, I have been quite happy with Audio Grocery's Logic Articulation Editor. I use it in my templates and it is simple and pretty flexible without need of getting into programming side of things. Just my 2cents.

Cheers

I mostly agree with Steve's post. However, unless things have drastically changed with newer versions of DP, while it is a great DAW ( I would LOVE to have the Chunks feature in Logic) it is or was less efficient with CPU than Logic.

If you use Peter Schwartz's ArtZ ID (or SkiSwitcher if 16 MIDI channels ins enough, as it is for me) then the lack of MIDI ports in Logic is a non-issue.

All the DAWS have pros and cons but I have the definitive answer as to which one is best to use with VE Pro......wait for it.... it's cvming.., almost there....THE ONE YOU KNOW BEST!