Quote:
Originally Posted by Sonic Nomad 
The following is an assumption;
The way I see it is the DAE is a "soft" version of TDM.
DAE is at the core of the LE system so all the other components are written around it.
I get the feeling that DAE is not just a driver that allows the app to talk with the interface but that is the CORE of Le the system - take it away and all you left with is a GUI.
And this why without a TOTAL rewrite or new engine we will never see features like;
ADC
Bounce to disk.
3rd party sound card support - although they did this with M-Audio but seems the implemented this into the engine coding. So for third party support they'd have to write the implementation into the engine itself.
Dunno if this makes sense to anyone but this is how I figure it to be.  As I said this is an assumption. Flame on! |
I totally agree with you Nomad. In fact I've stated similar thoughts in the AES thread.
BTW I should point out to others not quite understanding what DAE actually stands for.
Digidesign
Audio
Engine
I think others are comparing it to Core Audio and ASIO. BTW does anyone remember
Digidesign had HTDM? Notice how that plugin format disappeared? What does it
stand for? Host Time Division Multiplexing. This was dropped because computers
were still too slow compared to the new cards that were coming out. They decided
to put more focus into RTAS and TDM. I found this page.
HTDM Q & A
Of course I've never used a TDM system and I could be wrong. Maybe some PT
veterans can chime in about this HTDM thing. It seems to have been different than
RTAS even though it was host based as it would have to integrate with TDM when
running both in the same session.