<sigh> I'll take the bait. For the benefit of all... I've got a fresh coffee to help me churn through this real quick...
Freddie H
Mooch4056
too many pages to read in this thread
anyone got the conclusion or the cliff notes?
The last 10 pages in this thread is about being a Pro Tools fan-boy.
Baloney with a side of cheese, thank you. The only fan-boy around here is you Freddie, and we all love you for it. However, it's doesn't really help Cakewalk's case, to be honest, and it makes Sonar users look less well-informed than they really are.
Nothing about VS SONAR X1.
Make that extra cheese, please.
Its much easier to talk about how good PRO TOOLS are instead of talking about versus features and implantation. Perhaps they know already they have lost before it all begins.
Not sure what you mean by "implantation," but it kind of goes with the whole endearingly ludicrous statement. I suppose you mean "implementation" -- oh well, I'll move on...
Here you have some VS questions.
The answers should be fairly obvious, but I'll do it quickly:
1. Limits of RAM on project?
You are probably referring to your pet issue, x64. Sonar is a mature x64 platform and Pro Tools 9 is still x86 (32-bit). Therefore Sonar x64 has oodles of access to RAM and Pro Tools does not.
For a composer/songwriter/producer that uses a lot of sample libraries (i.e. Kontakt, etc.) then this is a very big issue and Sonar obviously trumps Pro Tools by a mile. The workaround with Pro Tools is that you use something like VE Pro, or you don't use a lot of sample libraries. :)
However, it must be stated that both apps install and run and are supported on Windows 7 x64. Sonar just gets to access all the RAM, Pro Tools does not.
Verdict: Sonar hands-down for sample-heavy people.
2. VST-support?
Sonar: Yes. Pro Tools: No. (EDIT: Well, I guess I have to mention that there is a VST/RTAS wrapper, but many people consider it less than ideal.)
In practice, this may or may not affect you. Pro Tools uses RTAS instead of VST. Many plugins do not come as RTAS plugins, and never will (especially old legacy VST plugins that have been abandoned by their developers). However, to be fair, there are plenty of great RTAS plugins, including RTAS-only plugins.
Verdict: If you have an existing collection of plugins that don't have RTAS versions, then Sonar hands-down. If you are new to the game, personally I think it's a wash, but some people may legitimately make a case that having access to the larger VST community/market/library is worth it, and that is a very reasonable point of view... so the verdict is slight favor to Sonar, depends on your preferences though.
3. Direct x support?
I'm assuming you mean DX plugin support. If you have old cherished DX plugins then this is an obvious win for Sonar. However, this is 2010, not 2003, and the prevailing plugin standards are VST and RTAS for Windows (plus TDM for PT HD rigs). DX no longer enjoys industry-wide support. Once Steinberg dropped it back with Cubase 4, it has been fading in importance, and we all know that.
Verdict: If you have old DX plugins you need to use, Sonar wins. Otherwise, this is irrelevant.
4. 64bit support?
See #1 regarding x64 instructions and RAM access.
As for the mixing engine, Sonar has the option to mix with a 64-bit double-precision engine (audio resolution, regardless of whether or not you are running the x64 or x86 version of Sonar).
My understanding is that Pro Tools HD uses a 48-bit fixed integer engine by default, but Pro Tools HD Native uses a 64-bit floating point engine. However, Pro Tools 9 (the version we're actually talking about here) uses a 32-bit floating point engine. I could be wrong on all that.
Verdict: If you want or need a 64-bit double-precision engine, then Sonar obviously wins. This is a big discussion, with many opinions, and not worth it to get into here. Personally, for me, it's irrelevant... 32-bit float is perfectly adequate for the most demanding mixes. It's good enough for Cubase and Nuendo and others as well, and far beyond the limits of what my human ear can discern in the real world. I've tried to convince myself that 64-float is audibly better, but I was just fooling myself. It's far more important to know how to mix something than worry about whether or not you have a 64-bit engine. If you can't mix worth crap, 64-bit sure isn't going to save you. In my opinion, 64-bit float is more about marketing than about real-world results. But, then again, this one does technically go to Sonar. :)
5. Maximum audio tracks in HD version VS SONAR X1
Obvious win for Sonar. Which can technically support unlimited tracks.
The standard Pro Tools 9 supports 96 mono or stereo tracks, 64 instruments, 512 MIDI tracks, 160 Aux tracks and 256 busses.
PT 9 w/ CPT2 and PT 9 HD ups some of the numbers, but still have limits. (i.e.: 192 voices/tracks)
Verdict: technically, Sonar. In the real world: depends on your needs. I've had projects go over 100 tracks, but to be honest, that type of project becomes very uncomfortable in Sonar in my experience. Pro Tools manages large numbers of tracks much better, IMO... and frankly, if we talk about this issue, we should talk about Cubase/Nuendo too... but let's not.
6. Audio engine
Not sure what you mean by this one -- both have good audio engines. If you are referring to 64-bit mix engine, see #4. If you are referring to performance -- i.e.: low-latency performance -- the initial numbers are actually coming out quite strong for PT9. Vin (TAFKAT, the benchmark guy) has recently run some tests with the universal benchmark that put PT9's engine in surprisingly good light with low-latency performance... putting it roughly in the same ballpark as Cubase/Nuendo and Reaper.
Verdict: A wash, really. Up to you what matters the most. But to play it safe, I'd suggest Sonar users not go there... the initial numbers are looking rather good for PT9. ALSO, we don't know what types of improvements might be coming in Sonar X1.
7. Midi functions and features. (How tight are MIDI VS SONAR)
I think we've covered this a few times in this thread, but in my usage, I'd clearly give the win to Sonar for MIDI features. I listed several features in another post in this thread, no need to duplicate that. There are many more. Sonar's MIDI-sequencing roots are clearly present, and Sonar is a serious MIDI tool. Having said that, Pro Tools' more simplistic MIDI features are well-thought-out and executed well. They are clean, effective and work very well for what they do. As for how tight the timing is, I have not found major issues with either of them.
Verdict: For a serious MIDI users, Sonar hands-down. If your MIDI needs are lighter, Pro Tools wins based on simplicity and polish, in my opinion. Your mileage may vary.
8. VST/ RTAS Instruments function.
Not sure what you mean. See #2 and #7. In the real-world, both support virtual instruments, with the edge to Sonar for its more comprehensive MIDI editing and instrument tools (i.e. the synth rack, etc.).
Verdict: Sonar
9. Icons or color skin?
A purely subjective issue with regard to its value, and we don't know what will be available with the new Sonar X1 interface. Sonar supports icons and various color customizations. Pro Tools does not have icons like Sonar's but it does have color customizations. This is such a lame specific thing to focus in on compared to the big picture of some of the other issues -- the big question should be which has the better interface? Or better workflow? And that is a big discussion that is very subjective. Put it this way, you can customize both applications to varying degrees, but its usefulness will boil down to what is more important to you and YOUR workflow. PLUS, we don't know the extent of customization that you can do to the new X1 interface. I suspect it will be very good for Sonar. But PT9 is nothing to sneeze at in this department.
Verdict for interface: My guess is that Sonar X1 will do well in that department, but this is highly subjective and each person has to decide for themselves. Pro Tools 9 is by no means a clumsy, archaic, unwieldy interface. Sonar X1 also does not appear to be a clumsy, archaic, unwieldy interface from what they have said/shown so far.
10. Streaming & stretching algorithm of AUDIO?
This is a very valid question, one I can't comment on very well except from a subjective perspective. Personally, I think it's a wash for the most part, and ultimately depends on what you need/want to do. There is some material that I think Sonar sounds better time compressing/expanding, and some material I think Pro Tools is better at. Personally, I think it's a matter of actual features and your workflow... what can each DAW app do with regard to things like time compression/expansion, elastic audio, beat detective, audiosnap, etc.? That is just too big to cover here, and you'll have your advocates for anything. Plus, in all fairness, other apps should be drawn into the discussion -- neither Pro Tools or Sonar have built-in sample editors, for example. So you'll have to break down the features carefully and analyze where they might fit into your projects.
Verdict: I think they're complimentary, and I'd rather have both their toolsets than assume one is better than the other... because they are completely different beasts.
11. Clip base automation? Destructive faders?
Sonar has clip-based automation, which is a great tool. Not totally sure what you are referring to with destructive faders, though... maybe you're referring to Pro Tools destructive cross-fades? Anyway, if that's what you mean, it's irrelevant since it's totally undoable and does not modify the source audio in Pro Tools. It just prints the crossfades instead of rendering them in real-time, probably a throw-back to TDM roots of PT. Whoopdedoo, irrelevant. If you're referring to something else, please clarify.
Verdict: Sonar takes one home with clip-based automation, and I'll add that its clip-based effects are a great feature. Pro Tools does not do either of those things. However, in all fairness to Pro Tools, it does manage automation very well -- much better than Sonar IMO -- such that clip-based automation is frankly not a big deal, or even irrelevant in day-to-day work. But your mileage may vary. The real win for Sonar comes with clip-based FX, which is a very powerful feature that does not have a comparable feature in Pro Tools. Also, we don't know the extent of Sonar X1's new features... so this could also change the comparison.
12. there are more... VIDEO PRO TOOLS HD VS NUENDO..
Indeed, there are more, and your list shows your own bias and lack of understanding of Pro Tools. I'm not defending it, and I'm not trying to give you a hard time, but your list above is so narrow it's missing out on many, many other important areas that could have a huge impact on someone's work. Let me add a few more areas.... and I don't mean this as a criticism (or biased endorsement) of Sonar, but it shows that this is a bigger comparison than we can really make in this thread. Here are a few more...
13. More comprehensive plugin collection out of the box.
Verdict: Sonar -- I'll give that one to Sonar since there are some gems in there... it does come with more essential/useful plugins IN THEORY, but with questionable implementation in some cases... i.e.: it comes with a linear multiband but we all know it can't be used/edited well in real-time -- hope that's fixed with Sonar X1. Pro Tools, on the other hand doesn't come with a multiband at all, to my recollection (maybe I missed it). And so forth....
14. Better customer support.
Verdict: Don't know for sure, but my guess is Cakewalk... I haven't had to deal with Avid customer support, and I do like this forum and the Cakewalk folks. They're good guys. Guess is, Cakewalk and Cakewalk community might have an edge here.
15. Offline non-real-time bounce.
Verdict: Technically, Sonar. However, there are workarounds that render this irrelevant to experienced Pro Tools operators.
16. Excellent multi-lane automation and editing tools
Verdict: Pro Tools. Automation in Pro Tools just works the way it should (more or less). I'll leave it at that. Then, when/if you upgrade to Pro Tools CPT2 or HD/HD Native, it comes with vastly superior automation tools. But that costs a lot more. :)
17. Strong video support and compatibility with current frame rates
Verdict: Pro Tools. For post folks, there's no question here, hate to say.
18. Strong post-oriented workflow and editing features
Verdict: Pro Tools
19. We could break down #18 into many sub-issues such as ripple/shuffle/slip and other advanced editing features
Verdict: Pro Tools -- with combination of regions and shuffle editing, Pro Tools can effectively emulate ripple editing and many other editing techniques (actually, Reaper takes the cake on ripple for speed of use, but that's another discussion). Pro Tools is very deep in this area.
20. Strong track, region and group management and filtering
Verdict: Pro Tools by a mile.
21. Routing a channel to a bus or track that can then be recorded?
Verdict: This has been requested in Sonar, but Pro Tools does this important feature, built in. Other people in this thread have shown workarounds for Sonar... but your audio device needs to support it.
22. To be fair, I should add Track freezing...
Verdict: Sonar hands down.
23. Advanced Project management?
Verdict: Pro Tools by far, but in all fairness, we don't know what Sonar X1 will bring. But as of Sonar 8.5 it's a big gap. No, not a big gap, a huge gap. Cakewalk has hopefully paid attention to project management in other apps for Sonar X1.
And we could go on and on and on... how about this one...
24. Session interchange with largest group of studios (i.e.: industry standard, like it or not)?
Verdict: Well, we know that one. That may or may not be important to someone.
In the end it will be about what works best for you. I believe that Sonar is very strong in the compositional area, and we all know the shortcomings in the post and film/video area -- and Sonar does not really claim to be a post-oriented application. (Although some of their recent marketing hints at stronger post features... it's possible that X1 or X1.1 or X2 resolves some of this). Anyway. that's why I believe Sonar and Pro Tools are rather complimentary.
In either case, both are impressive, powerful programs and it should be obvious to anyone that very pro results can be had from both of them. And no matter what features they have (or lack) it comes down to the operator's skill and talent. :)
EDIT: For spelling and a tiny bit of clarification. :)
post edited by eratu - 2010/11/13 11:40:03