The question is phase-coherence. There are ways to lock specific processing blocks on the same dsp now, but I think that the newer AD stuff does it at a lower level. I didn't plumb through the entire devkit (which u can download a demo of) but I did read through some of the technotes for the newer Kits & Sharc releases and confirmed some form of support for phase compensation when Red mentioned it to me a while back. I'm sure Frank (and hopefully SC) know a lot more about it than I. I just don't know where the STDM interconnects fit into the overall scheme of things, since u can't just open up Scope.exe in the devkit and see what Creamware sees. I'm sure they can figure it out though...
nominations for the worse 10 things about creamware
The question isn't zero-latency. I don't see that being achievable given modern digital technology & laws of physics. Perhaps string theory or some unthought of GUT will get us past relativity but for now...
The question is phase-coherence. There are ways to lock specific processing blocks on the same dsp now, but I think that the newer AD stuff does it at a lower level. I didn't plumb through the entire devkit (which u can download a demo of) but I did read through some of the technotes for the newer Kits & Sharc releases and confirmed some form of support for phase compensation when Red mentioned it to me a while back. I'm sure Frank (and hopefully SC) know a lot more about it than I. I just don't know where the STDM interconnects fit into the overall scheme of things, since u can't just open up Scope.exe in the devkit and see what Creamware sees. I'm sure they can figure it out though...
The question is phase-coherence. There are ways to lock specific processing blocks on the same dsp now, but I think that the newer AD stuff does it at a lower level. I didn't plumb through the entire devkit (which u can download a demo of) but I did read through some of the technotes for the newer Kits & Sharc releases and confirmed some form of support for phase compensation when Red mentioned it to me a while back. I'm sure Frank (and hopefully SC) know a lot more about it than I. I just don't know where the STDM interconnects fit into the overall scheme of things, since u can't just open up Scope.exe in the devkit and see what Creamware sees. I'm sure they can figure it out though...
The Mod III shell needs some * serious * fixing once for all !
The VDAT is indeed most cumbersome, drop " the make it behave like hardware " add stereo and less than 8 tracks option ( most of the time 1 stereo track needed here, duh ! )
Make TripleDAT LE able to record above 16 bits ( shouldn't be that hard )
The VDAT is indeed most cumbersome, drop " the make it behave like hardware " add stereo and less than 8 tracks option ( most of the time 1 stereo track needed here, duh ! )
Make TripleDAT LE able to record above 16 bits ( shouldn't be that hard )
-
CarvinGuitarFreak
- Posts: 130
- Joined: Wed Sep 20, 2006 4:00 pm
Ten worst things?
Poor Midi implementation
No 96Khz support for Dynatube
No 64bit support (Yet?)
VDAT bugs
STS bugs
GUI speed
Hard to get in contact with Creamware
Maximum of 3 cards per machine (I think?)
Very little updates
Is PCIe going to happen or what?
Still one of the best audio production solution, even with the above. Wish I could get 4 cards into my machine. Damn.
CGF
Poor Midi implementation
No 96Khz support for Dynatube
No 64bit support (Yet?)
VDAT bugs
STS bugs
GUI speed
Hard to get in contact with Creamware
Maximum of 3 cards per machine (I think?)
Very little updates
Is PCIe going to happen or what?
Still one of the best audio production solution, even with the above. Wish I could get 4 cards into my machine. Damn.
CGF