This may be a stupid question, but... did you try to send MIDI from your computer to the Virus?
I know that there are quite a lot of users not using the TI but instead sending MIDI to the Virus and recording the analog outputs via audio interface. They'd have run into the same issue.
Maybe I find time to hookup my Darkstar to my MPC Live and try with that setup.
Yes tried midi from the computer as well. This was when I first noticed parts being laggy/sloppy.
At this point it seems really unlikely that it's anything sequencer related, as I have had the same behavior with midi from the computer, the Cirklon, and the Mpc.
If you press config on your virus, there are 3 pages of settings related to midi. There is another one called "audio clock". Please share your settings.
If you can, also use the virus via a midi keyboard and let us know how timing goes. Make sure that the usb cable is disconnected.
IMHO you may need to check the midi settings on your sequencer. Usually when people have timing issues is when the virus is used in the TI fashion so your case is indeed currently odd.
Midi settings are as follows:
Global channel: 01
Soft Thru: off
Midi Device ID: 10
Arp Note Send: off
Midi Clock: sync to external
Midi Volume: Enabled
Program Change: Enabled
Multi Prog Change: Disabled
Audio clock: Auto @ 44.1k
( I have also tried this as internal and at both frequency settings and it makes no difference)
I agree that this case is particularly odd. There really isn't much else I can check on the sequencing side. The Virus is plugged into the same sequencer that I have been using without issue for years. As I mentioned before, I also tried sequencing it from my MPC live and from the computer as well and I get the same sloppy timing (with the Virus) from them all. It's the same setup that I use with an Ob-6, a Blofeld, a Modular, and some other gear and nothing else is sloppy or jittery.
The more I mess around with this I can only really think of 2 different scenarios that make sense.
1. My particular unit has some error or hardware fault in whatever is processing the incoming midi data, and this part is being bypassed when receiving midi data via USB in TI mode. Or -
2. There was a bug introduced in the OS (perhaps in the most recent OS update) that altered the prioritization of incoming midi data (from the DIN port)?
IDK. I can think of reasons why both of those scenarios seem pretty unlikely, but something is not working right and I can't figure out what it is.
Thanks to both of you for taking the time to run through this with me.