No.
This is because every video editor has
scaleable playback... it's like a DAW's soft drop out feature on steroids.
SONAR has a soft drop out feature... but it is a very light treatment.
Video apps have so called scalable playback and the app can shift to a lower resolution display (it throws away or drops pixels on the fly) and it can drop lots of frames (variable framerate) while the transport remains smooth.
Audio apps can't drop out very much data without the sound being effected greatly and that defeats the purpose of the DAW.
Persistence of Vision allows a video edit person to view video playback comfortably even if pixels are being cast away or the frame rate is being altered on the fly. It works ok... so it works ok.
So, what does all this mean? It means that video apps are actually pretty light on the computer compared to a multi track DAW.
Video apps rarely combine more than a few streams as layers. The video playback requires huge data transfers and sometimes massive amounts of CPU but relatively little
CPU juggling.
A multi track DAW with 10 tracks and a couple dsp on each track is juggling stuff like crazy.... and we hear timing so precisely that any choke or cough is readily apparent.
This is one reason that soft drops have limitation towards their helpfulness... they can't drop much before we hear the drop. This is why when a DAW does go over the cliff so to speak... it can end up at the white screen etc. DAWs run much closer to the edge than a properly run video editor.
Now, I can operate a video editor in such a way that I can crash it every time. You can try to play back cpu intensive distribution video codecs and edit it and you will hate your video editor. You can crash a video editor easily... but you have to use it in an way that
is possible but was never intended by the code writers.
If you use a DAW normally and you use any dsp you think you may use you can easily come up with mix and match combinations of CPU and PDC juggling that brings your system to a halt with a great big drop out... or worse.
This is one of the reasons so many people with systems that seem adequate find that their DAW doesn't work 99.99%. It may not be their system... it may their expectations.
The way I have found comfort using my DAW is that I use dsp and routing that seems to work... and every time I stumble upon a new routing combo of my favorite dsp that doesn't work; I don't do that anymore.
If you've gone through your system and feel it should be up to snuff then I suggest you carefully evaluate your choice of dsp and Vi and try to figure out what combo of routing may be stressing the playback beyond your sample buffers capability to smooth it over.
The first thing to do is to ascertain which of your plugs and instruments push the PDC beyond the buffer limitation and then take a look at where those plugs and instruments are sitting in the routing matrix.
Do you have a PDC user routed to another PDC user? DO you have some PDC users running in parallel?
Imagine a car engine running without a timing chain? If you can. IF you can do that... imagine a car engine running with multiple timing chains. Does it seem complicated? It is.
The best I can do is recognize the symptoms of soft dropouts and re evaluate my routing before the crash... which I do... and that keeps me at 99.99% happiness.
Maybe that can work for other people to?
Food for thought?
best regards,
mike