Access Music User Forum

Hi, new to the forum and just bought a Virus.

I've had the same problem as Spanda, the AU doesn't always complete the initial Starting Up process (does about half of the white bars but never goes any further). Reboot fixes it.

Also I feel like the Virus came with patches already in the ROM V, X, and Y spots (I could swear I was playing some patches in those areas, and I hadn't done any updates yet or anything), and then when I did the 3.3 update, they're empty now. Could be just me though, just figuring this thing out now...

Virus TI2 Keyboard
Pretty recent iMac
10.6.2
Logic 9.0.2

As an update, I'm pretty much finding the AU plugin never completes startup anymore. Not sure what combo of restarts and reboots gets it working again but I had to downgrade back to 3.1 to get productive again. I don't know if it matters but I run my Logic at 96 kHz.

I've got problems with this, too. I've been in contact with support for quite a while, but they haven't been able to reproduce my problems yet.

There are workarounds, however:

- The TI2 is recognized by my MacPro, if I turn it on BEFORE the MacPro.
- If I turn it on AFTER booting my Mac, it shows "USB" in the display but is not recognized by the plug-in. The Polar keyboard sends no MIDI data into Logic either.
- BUT: I can force the recognition by re-scanning the MIDI setup in the "Audio-MIDI-Setup" app.

When I do that, everything works fine. Maybe this helps others, too?

BTW: I checked this with no other USB devices connected (except for keyboard and mouse) - doesn't help. I guess, this is a 3.3 only problem since I switched from a TI1 with 3.2.x directly to the TI2. I only disconnected the TI1 (which had been working perfectly all the time), connected the TI2 with the same USB cable and installed beta 3.3. Since then, the problems are there.

What I haven't tried so far due to a lack of time: Downgrade to 3.2.x firmware and drivers.

Best regards,

Christian

EDIT: Just doing it now. Will report back...

It's strange though with 3.3 :

- The VCC recognizes the TI2, it can be updated, backupped and restored.
- The TI2's MIDI and audio drivers are recognized in the Audio-MIDI-Setup (not greyed out). They are also recognized as being there in my MIDI monitor app.
- USB link established is shown in the display
- "USB" is permanently shown in the upper right corner.

BUT: The plug-in doesn't recognize the connected TI2, and the TI2's keyboard doesn't send any data. It only works when I start it before the Mac OR when I re-scan the MIDI drivers.

Hence the question: Is the MIDI driver f**** up?

I'm gonna try it now with beta 3.2.x (which worked before with the TI1).

Best regards,

Christian

Heck, no!!!

At least with a simple restart of my Mac, it still doesn't work! The TI1's good karma seems to be gone - even after the downgrade, TI2 won't send anything when just connected to the Mac. AND: The TI1 (which I still have here) now shows the same problem with a version it worked nicely on before...

It's really irritating: I disconnect USB - the display reads "USB link lost". The TI-driver is greyed out in the Audio-MIDI-Setup. I plug the cable back in, the display reads "USB link established", and the driver icon in the AMS is active again. The TI2's keyboard automatically goes local off, like it should be! So, my Mac perfectly recognizes the new USB device. Even the TI2 recognizes that it's in USB mode. It can even be talked to via VCC!

But when I start Logic or my MIDI monitor app, the Virus plug-in does NOT recognize the TI2, and no MIDI data can be sent from the TI2 (note or controller data, no matter). I have to re-scan the MIDI drivers to get it to work.

So where's the problem? Is it the MIDI driver? Or is it Snow Leopard? Or the combination of the two? Why did the TI1 work perfectly with this version but the TI2 doesn't?

Maybe we could help each other with clearly reproducing this. Can anybody with a Mac try it please? Only if Access knows it's not just me they'll be able to fix it.

Help would be much appreciated!

Christian

I took the exact same steps and got the exact same result with 3.2. I've had to revert to 3.1 and just reboot every once in a while to get the Mac to see the Virus and to get the VC to find it too. Everything kinda works with 3.1, just the sync is way out. I'm just gonna stick to 3.1 for now and use it old-school MIDI cables and analog outs until the Access boys know what's happening.

That's great guys, but I think we have to differentiate between the platforms: Problems under Windows 7 won't be the same (or have the same reason) as under Mac OS X. My problems with OS X can only be reproduced by people using Snow Leopard 10.6.x and starting up their Virus TI2 *after* the Mac has booted.

Of course, this doesn't mean you shouldn't try to reproduce yours! Nothing can be more annoying than eagerly waiting for an official release and then realising that the problems stay the same because too few users sent their reports to the support team.

Best regards,

Christian