I know that one of the key factors for me in choosing a computing platform for audio work is latency... essentially, the difference in time between when an audio signal enters the computer and when the audio signal exits via, i.e., a soundcard's audio outs.
So far, I've tried to stick with Macs because of their reasonably low latency figures. However, I'd be willing to consider a switch to Linux if it, too, could guarantee me reasonably low latency figures.
Have any attempts been made to do cross-platform latency comparisons--i.e., Mac, Windows 9x/nt/2k/etc., Linux?
For the Windows world, you might try Understand for C++ from Scitools (www.scitools.com), or CC-Rider from Western Wares (www.westernwares.com). Both allow you to generate function call graphs for a body of C or C++ source code. Understand for C++ seems a little less picky than CC-Rider in terms of dealing with missing include files, whereas CC-Rider seems to be a little more stable overall, but both are pretty cool tools.
Slashdot Mirror
I know that one of the key factors for me in choosing a computing platform for audio work is latency... essentially, the difference in time between when an audio signal enters the computer and when the audio signal exits via, i.e., a soundcard's audio outs.
So far, I've tried to stick with Macs because of their reasonably low latency figures. However, I'd be willing to consider a switch to Linux if it, too, could guarantee me reasonably low latency figures.
Have any attempts been made to do cross-platform latency comparisons--i.e., Mac, Windows 9x/nt/2k/etc., Linux?
-m
For the Windows world, you might try Understand for C++ from Scitools (www.scitools.com), or CC-Rider from Western Wares (www.westernwares.com). Both allow you to generate function call graphs for a body of C or C++ source code. Understand for C++ seems a little less picky than CC-Rider in terms of dealing with missing include files, whereas CC-Rider seems to be a little more stable overall, but both are pretty cool tools.