There is a very simple reason you can't use the TI integration under 64-bit OSes, drivers MUST be 64-bit to work. Applications can use virtualization layers like WOW64 (Windows on Windows 64-bit) that allow 32-bit apps to run in a 64-bit OS, but you absolutely can not run 32-bit drivers in a 64-bit OS. The only way we will ever get this is for Access to write the 64-bit driver we need to talk to the TI over USB. In theory, a 32-bit Virus Control plugin could talk to a 64-bit TI driver using a host sequencer's bit bridge function, but my guess is that Access wants a pure 64-bit solution when they release it. This makes sense considering how DAWbench has shown that 32-bit plugins using bit bridge can take a serious performance hit due to the virtualization layer.
Its really frustrating too, considering I am about to upgrade the DAW to a Core i7 box with 6GB of RAM and over a 2TB disk volume, and I need 64-bit Windows to take advantage of both. Oh well, at least 32-bit XP will scream until Access gets their act together. Maybe I can get more native 64-bit plugins in that time as well.
|