onid said:I love to work with Logic, and the synths/plugins that comes with 7.0 are really good! The only reason why I use Pro Tools right now is becouse we got a control24 to the studio, and its kind of nice to mix with real faders.
Razorjack said:I've seen a control|24 being used with Logic before.
black sugar said:To me the most important feature of a DAW is Plugin Delay Compensation.
If your DAW doesn't automatically compensate for plugin latency on inserts and sends, have fun with your calculator and figuring out delay compensation for every track. That alone made Protools LE/M-Powered unusable for me. Fuck that.
OzNimbus said:This is the exact reason I use SawStudio: It's written in 100% machine code, meaning the language your processor speaks. Everything else, including PT, is written in higher level languages such as C++, etc. In layman's terms, the language has to be translated down to machine code before your processor can read it. This means a massive performance hit. Hence the DSP cards for PT.
Another way of looking at it: If you write a program to have a chicken cross the road in Machine code, the chicken crosses the road. If you write the same program in C++ or your language of choice, the chicken would first have to circle the block 1000 times before it could cross the road. Yes, it's that big of a performance hit.
Muttley said:I'm sorry, but speaking from a programmers point of view that's bunkum.
C++ is not an interpreted language as you imply (maybe you're thinking of Java). A C++ program is indeed converted to machine code by a compiler, but this is done at build time by the developer. What you install on your machine and run is already machine code.
Plus, I bet that SawStudio is written in Assembly Language (I don't think anyone these days sits there typing in hex codes to program ), and this then needs to be compiled to machine language by something known as an assembler which basically does the same job as a compiler does for C/C++. And unless it totally bypasses the operating system it's going to need to use OS libraries and APIs that, on the whole, will have been written in C/C++ anyway.
C/C++ is generally used for large programming projects because it's a much quicker language to develop in. Plus the huge majority of programmers out there would probably make far less efficient machine code by hand than a compiler can.
Huge amounts of optimisation can be done of C++ code, either in the compilation process or by inlining small assembly routines if required (rarely).
Also, don't forget that CPUs are stupidly fast these days, and the major bottlenecks for audio software are through memory, disk and bus bandwidth limitations. Machine code won't help you there at all.
At the end of the day, machine code is not inherently better than C++, and C++ is not inherently better than machine code. They're basically two tools for getting the job done, and what you use is basically down to personal taste. Kinda like the whole Mac vs. PC nonsense (my Commodore 64 is better than your Spectrum, etc.).
Just my 2p.
Muttley
guitarguru777 said:I love my Sonar and ill most likely never switch. That being said im saving up for a Mac .... lol makes no sense i know ....
ltratt said:Chaps, I can well believe that SS has many advantages over other systems, but in 2006 those advantages are exceedingly unlikely to be noticeably effected by whether it's written in assembler or C.
Seriously, it really doesn't mean a massive performance hit compared to fairly low-level languages such as C. Sometimes it will be a small performance hit, yes, but except in highly unusual circumstances (certain limited aspects of audio processing possibly being one of them) it is no longer possible for a human to beat a compiler.
Actually, that's probably where some of the speed gain lies. It bypasses Windows. No registry hooks. Uninstalling is as simple as deleting the directory.Quote from Muttley:
And unless it totally bypasses the operating system it's going to need to use OS libraries and APIs that, on the whole, will have been written in C/C++ anyway.
It's been hard to bit my tongue on this one, but with due respect, OzNimbus you really don't know as much as you think.OzNimbus said:Actually, that's probably where some of the speed gain lies. It bypasses Windows. No registry hooks.
-0z-
kelch said:It's been hard to bit my tongue on this one, but with due respect, OzNimbus you really don't know as much as you think.
Ok, let me clarify: You're right... it's written in assember. My bad. I've always got the two terms mixed up. Ok, commence crucifixion!kelch said:When you stated Machine Code you really meant Assembly Language.
High level languages like C, C++ are not interpreted, but compiled... it's not a distinction without a difference
Todays compilers also do instruction scheduling/optimizations which would really be a chore for a human and with Hyper-threading... well.
Writing a Windows program solely in Assembly is a real job... a much better approach is to develop it in C/C++ and optimize certain portions by hand.
I'm not convinced SAW bypasses Windows. In NT it's impossible unless Kernel mode drivers are installed... an NT task can't get to the HW. Anyways, there's no reason to bypass the OS.
Secondly, what's a Registry Hook? The Registry is just a data DB.
BTW: Samplitude is a great DAW program.
Muttley said:Not used it extensively, but it doesn't seem particularly intuitive. That may be down to me though.