Drone7
I watched your video. This is one if the weirdest things I've seen in a DAW. Despite the so-called improvements, the whole Sonar graphical methodology looks extremely disconcerting to me. Is this normal Sonar behaviour? I've never seen such a thing. Does Sonar always take time to update the Waveform like this even though the previous interference has been resolved?? I say again, I've never ever seen such a thing in a DAW before. Someone pease tell me if this is normal for Sonar?
In my books, I would deem lots of data as a session running 21 realtime softsynths, 10 stereo tracks of audio at 24bit 96khz plus 90 realtime effects plugins, 7 tracks playing-back samples. Would such a session cause this behavior in Sonar with the following PC specs... Haswell Quad Core i7, 16 gig Ram, 2 gig dedicated graphics card, SSD.
Weird in what way? Maybe you didn't understand what his video was demonstrating. He is loading a huge high sample rate audio project where the wave pictures have not been yet cached. In *any* DAW when you load such a project it needs to literally read every sample of audio to determine how waveforms have to be displayed. You can try it for yourself - import a large number of big wave files (a few hours in duration preferably) into any daw and you will see it trying to render the waveforms.
Also your scenario listed does not constitute any significant disk load. We are talking about a disk streaming optimization here so we need a ton of wave files not synths. So your scenario wouldn't be relevant.
I assume Bill's test is similar but what I did was load an audio project at 96K with about 15 GB of audio. When that is done SONAR literally has to process 15 GB of audio data before all pictures are rendered. This process is done in parallel as a background task. In fact many DAW's don't even parallelize this so it would be much slower than SONAR.
In earlier versions this parallel task could interfere with playback causing dropouts. The new design removes this limitation.
When I tested this even a blazing fast Haswell E with 16 cores would drop out. With the new system fix even a slow system is able to handle the workload and wont drop out. Even though most users aren't loading 15 GB audio projects the fix will make their system more resilient to dropouts under disk load. I see this as a huge improvement...