Design & Performance Info?

[mark4man]

People,

How does one go about obtaining technical design & performance info on SONAR? Seems like they're too busy to answer questions of this nature over at tech support (&...rightfully so, considering all the run-of-the-mill operational type inquiries they must receive.)

The reason I ask is...if you peruse the forums where the Pro Tools users hang out, they seem to bat back & forth weighty, system-wide type issues on a regular basis...signal path, floating point operation, summing calcs, node depth...that sort of thing.

I'd like to find out such things about SONAR...to see how well it stacks up against PT (once & for all.)

Must be some white papers around somewhere, right?

Thanks,

mark4man

 

[laptoppop]

The Sonar forum on www.cakewalk.com is quite active.

But there is a big difference between PT and Sonar. PT runs on proprietary hardware, while Sonar runs on readily available PCs. What you'll find out there is a lot of Sonar folks talking about which PC is best, what video card to use, which hard disk, etc. The performance of Sonar is tightly coupled to the PC being used -- you just can't make generic statements about performance because Sonar can run on a wide variety of platforms.

This has one huge advantage -- for a similar level of performance, Sonar is MUCH cheaper. It also uses industry standard plugins - both VST and DirectX that are cheaper for the same plugin than the proprietary PT format plugins.

-lee-

 

[mark4man]

Lee,

I'm not asking for comparitive info where none can be found...I'm looking for topology data, that's all.

mark4man

 

[Teacher]

Lee,

I'm not asking for comparitive info where none can be found...I'm looking for topology data, that's all.

mark4man

I agree it would be interesting BUT that should be the LAST thing your worrying about when recording

 

[James Argo]

The reason I ask is...if you peruse the forums where the Pro Tools users hang out, they seem to bat back & forth weighty, system-wide type issues on a regular basis...signal path, floating point operation, summing calcs, node depth...that sort of thing.

I'm so glad that our (Cakewalk users) main concern is making music.
Here's what you should do: Write a song, perform, record, mix, post in the clinic, re-write (after someone's comment), re-record, remix, re-post in the clinic, realize it still doesn't sound good enough, buy additional gears, attempt to re-record again, remix again, re-post in the clinic again, then... you'll forget about that floating point operation thingee...


Jaymz

 

[mark4man]

Guys...

I'm not WORRIED about it. It INTERESTS me, OK? I'm curious about it. I'm currently doing everything Jaymz detailed in his reply; & making decent progress about it...but I also like to learn the nuts & bolts as I go.

See...I usually like to lay around at night & read technical crap. The house is painted, it's too cold to play horseshoes; & I don't throw the I Ching anymore. I've also seen all the made-for-TV Christmas movies (&...if one more Nordic barbarian tribe gallops across the screen en route to destroying a shopping mall...I swear...I SWEAR...I will pull an Elvis on my television. I'll shoot that son-of-a-bitch to pieces...the wife 'll be screamin'...the cats 'll be divin' under furniture...)

[Now watch...someone at the NSA will read this; & I'll soon have black helicopters hovering over the back yard...swat teams rope falling into position...]

mark4man


BTW - Did I mention I also read "Digital Fortress"?