Nothing but trouble..

[MBTC]

Originally Posted by DIGITAL SCREAMS

Oh man.

Sorry to hear your woe's but the TI2 works fine for me in Cubase 5.

Virus hardware and software is very solid on my system. Its impossible (given the complexity of peoples set ups these days) trouble shoot your issues. I'd say your sequencer and 64bit system are not compatible.

That's possible.. My OS is 64-bit and my DAW is 32-bit (FL doesnt have a 64bit version yet). The driver to the hardware of course is 64-bit, which is pretty new for Access (but it shouldn't be, considering widespread adoption of 64bit over the last 2 years). It also shouldn't be an issue in a 32-bit DAW and 32-bit plugin of VC, but I guess it could be. If so, the virus is not yet ready for me or more likely vice versa

Originally Posted by DIGITAL SCREAMS

Even with a '5 bar patch' on your virus you should get ample poly - are you getting this even when you've disconnected all midi/usb cables from the Virus?
DS

No, I tried exclusively with the USB since that is the setup I would be using it with in my DAW. I know with some other setups I would get the full glory of this synth, but I had to judge it based on the pricetag and Total Integration selling point alone.

[Choond]

Its a pity about the 64 bit OS. ASIO4all.dll sometimes sorts out latency/ immature driver issues for a lot of hardware. But it only works on XP 32 bit.

[MBTC]

Originally Posted by Choond

Its a pity about the 64 bit OS. ASIO4all.dll sometimes sorts out latency/ immature driver issues for a lot of hardware. But it only works on XP 32 bit.

In this case I don't think the issue was ASIO, because I had the option of Creative ASIO (for the X-Fi card in this system, which is what I normally use with excellent success.. like 2ms with no issues whatsoever), or the TI ASIO. It seemed to behave identically regardless of which I used as the sound card.

At this point I am holding tight. I am looking forward to see what the next Virus model brings to the table.

[NabLa]

Originally Posted by Choond

Its a pity about the 64 bit OS. ASIO4all.dll sometimes sorts out latency/ immature driver issues for a lot of hardware. But it only works on XP 32 bit.

I use ASIO4ALL in Windows 7 64.

[MBTC]

Today, the beautiful desktop crawled herself back on to a UPS truck (total shipping expense back to seller, including destination insurance was about $30 US out of pocket for me). I don't regret the experience at all, it demonstrated to me how powerful current soft-synths are on a good PC, and although I do love the sound of the Virus, for DAW work it cannot justify the $2k pricetag. I can only hope someone takes notice of the post above this and turns the next generation Virus into something that I can truly use. To summarize that would mean perfecting "total integration" and fixing latency issues with USB. I'll even take firewire at this point.

[mitchiemasha]

Sorry to hear you gave up on the virus. Goodbye!

[MBTC]

I only gave up on it in its current incarnation, not permanently. I'll follow it's progress and buy again if the latency issues are overcome.

[feedingear]

As I stated earlier - no latency issues for me, if it is set up properly.

[boborulz]

Same here...

[MBTC]

I set it up according to Access' recommendation for my host, and the latency persisted. Beyond just the latency, the performance of VC inside the host was atrocious, just interacting with it using the mouse was a nightmare (and this is a Core i7-965 with 6GB, Win7 64bit). It's possible that those of you with no latency issues are getting good results with the 32bit driver and the 64bit still has bugs to work out.

Either way, I'm glad for those of you it works for -- all things considered, including the disappointing polyphony, I just decided it would not be worth the hassle for me in its current form.

As I said, I'm not giving up completely. I'd love to incorporate the great Virus sound into my music someday. My guess is that if the next iteration of the product supports the full throughput of USB and the software becomes a bit more stable, Total Integration might become a feasbile option for a lot more folks (including me).