Contribute
Register

Virus TI + 10.6.8 + Gigabyte GA X79 UD3 =*0 luck. Please help me!

Status
Not open for further replies.
Joined
Aug 27, 2012
Messages
8
Motherboard
10.6.8
CPU
3930k
Graphics
6670
Mac
Classic Mac
Mobile Phone
Greetings all.


I have my system running somewhat stably (I get intermittent Kernel panics from anything like Chrome to WindowServer - I think it's GFX related but that's for another thread). However, when I plug in my Virus TI Polar and attempt to access it in Logic/Vienna I'm presented with: midi driver failed. the midi driver failed to start or is not installed. this can happen if you have connected too many usb's. also try to install the virus ti software again.'




I've tried different version of the TI software, different USB cables/ports, peeking inside the contents of S/L/E/AccessVirusTI.kext and /L/Audio/MIDI Drivers/Virus TI MIDI Driver.plugin and I can't get this thing to get recognized in the plugin. Virus Control however can access it perfectly with no problems whatsoever.


Have read that other users have had success with their TI and Hack. Scoured the interweb for a solution and came back empty.


I would greatly appreciate any help with this issue as this piece of gear is critical in my line of work. Thank you so much!



MultiBeast 3.10.1
10.6.8
Gigabyte GA X79 UD3 F11 (Note for other SL users: Don't update the BIOS; your hackintosh partition won't boot!)
i7 3930K
MSI HD 6670
 
Joined
Nov 8, 2012
Messages
67
Motherboard
P8Z77 V Pro, 24GB DDR3
CPU
i7 3770K @ 4.6GHZ
Graphics
Nvidia GTX 670 2GB
Mac
  1. Mac Pro
Classic Mac
Mobile Phone
  1. iOS
Good luck with that chum, The Virus TI was a royal pain in the rear end when It comes to Virus+Mac and Midi/connectivity problems.
The Virus doesn't like sharing Internal USB hubs with other devices. When I had an iMac (core i7 8gb ram), the virus done nothing but complain and dish out errors. From what I learned, the virus prefers to have its own USB hub (preferably A USB pci express card).
The problem I had was that the iMac doesn't let you add/remove hardware so your stuck!
if you haven't done so, try Adding a
pci expansion card and use it solely for the virus ti.

Your issue sounds similar to the Usb problem I had with the iMac. At least this time u can add hardware.


Hope this helps


Chris
 
Joined
Aug 27, 2012
Messages
8
Motherboard
10.6.8
CPU
3930k
Graphics
6670
Mac
Classic Mac
Mobile Phone
Thanks for the reply! my experience with the shared hub problems (On an early 2011 MBP) was that despite showing the error dialog it would continue to function normally. I will try your suggestion, thank you vm!
 
Joined
Aug 27, 2012
Messages
8
Motherboard
10.6.8
CPU
3930k
Graphics
6670
Mac
Classic Mac
Mobile Phone
USB 3.0 NEC PCIe Card (Followed http://www.tonymacx86.com/general-h...drivers-caldigit-lacie-oyen.html#post482394): Detected on profiler, not detected by the plugin

USB Bracket into Mobo: Same result as plugging into standard 2.0, mobo (X73UD3) seems to have all USB 2.0 ports on a single bus

USB 2.0 Hub (http://kkspielwiese.access-music.de/forum/index.php?page=Thread&postID=17165#post17165) : No bus-shared message, MIDI driver still failed. This gives me the feeling that this problem is 100% software related. Too many variables changed with the same result!

About to test by trashing ~/Library/Prefs/ByHost/com.apple.MIDI.xxxxx

EDIT: Didn't do anything different. I'm not quitting yet.
 
Joined
Nov 8, 2012
Messages
67
Motherboard
P8Z77 V Pro, 24GB DDR3
CPU
i7 3770K @ 4.6GHZ
Graphics
Nvidia GTX 670 2GB
Mac
  1. Mac Pro
Classic Mac
Mobile Phone
  1. iOS
hey mate

Virus control is a nightmare. Out of Interest.... what sample rate have you got the Virus set to? is it at 48khz or 44khz?
this is another thing the Virus doesnt like. 48khz.....
I got all sorts of errors and midi problems when it comes to 48khz sample rates.
This was a known issue with the virus and access said that they were gonna repair this in the latest OS5. Im not too sure if they did, i still see people complaining about it on their forum.

When I had it at 44khz, I had no issues with midi or connectivity problems.


Chris
 
Joined
Aug 27, 2012
Messages
8
Motherboard
10.6.8
CPU
3930k
Graphics
6670
Mac
Classic Mac
Mobile Phone
Chris,

I'm almost certain it's been on 44.1 but I will check.

I just finished installing (drivers & firmware):

Virus TI Software Suite 5.0.1.05.pkg
virus_ti_software_installer_v50010.dmg
virus_ti_software_installer_v45300.dmg
virus_ti_software_installer_v45115.dmg
virus_ti_software_installer_v45016.dmg
virus_ti_software_installer_v40501.dmg
virus_ti_software_installer_v40201.dmg
virus_ti_software_installer_v40018.dmg
virus_ti_software_installer_v33340.dmg
virus_ti_software_installer_v30300.dmg

And alas; the same error every time! I read here (http://www.tonymacx86.com/audio/74140-10-8-2-midi-issues.html) that USB 3.0 was causing errors, specifically the PXHCD kext (which I've since deleted after giving up on the 3.0 on the TI which is a 1.1 device o_O). Tried disabling USB 3.0 in the BIOS and still nothing.

I'm trying the final version on that list as I write this. I'm nearly out of ideas. Perhaps it's the multibeast IOUSBFamily kext? In which case what do I do?

EDIT: Oldest version on that list couldn't even detect the TI. As per your advice I checked the settings on the Virus (Why didn't I think to do this earlier?) and it looks like the audio clock freq was locked to host. but the MIDI sync was set to 'external'. I'm reinstalling latest fw and testing it out set to 'Internal'. Fingers crossed
 
Joined
Aug 27, 2012
Messages
8
Motherboard
10.6.8
CPU
3930k
Graphics
6670
Mac
Classic Mac
Mobile Phone
This is what my console gets when I try and instantiate the plugin:

Code:
12/5/12 3:45:41 AM    kernel    *** Connected to client 206 ***
12/5/12 3:45:42 AM    kernel    est 0xc1-81-0000-0001
12/5/12 3:45:42 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0001
12/5/12 3:45:42 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0030
12/5/12 3:45:42 AM    kernel    before m_pUSBDevice->DeviceRequest 0x41-01-0000-0012
12/5/12 3:45:42 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0001
12/5/12 3:45:42 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0001
12/5/12 3:45:42 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0001
12/5/12 3:45:42 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0001
12/5/12 3:45:42 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0001
12/5/12 3:45:42 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0001
12/5/12 3:45:42 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0001
12/5/12 3:45:42 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0001
12/5/12 3:45:42 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0001
12/5/12 3:45:42 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0001
12/5/12 3:45:42 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0001
12/5/12 3:45:42 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0001
12/5/12 3:45:42 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0001
12/5/12 3:45:42 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0001
12/5/12 3:45:42 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0001
12/5/12 3:45:42 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0001
12/5/12 3:45:42 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0001
12/5/12 3:45:42 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0001
12/5/12 3:45:42 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0001
12/5/12 3:45:42 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0001
12/5/12 3:45:42 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0030
12/5/12 3:45:42 AM    kernel    before m_pUSBDevice->DeviceRequest 0x41-01-0000-0012
12/5/12 3:45:42 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0001
12/5/12 3:45:42 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0001
12/5/12 3:45:42 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0001
12/5/12 3:45:42 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0001
12/5/12 3:45:42 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0001
12/5/12 3:45:42 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0001
12/5/12 3:45:42 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0001
12/5/12 3:45:42 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0001
12/5/12 3:45:42 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0001
12/5/12 3:45:42 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0001
12/5/12 3:45:42 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0001
12/5/12 3:45:42 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0001
12/5/12 3:45:42 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0001
12/5/12 3:45:42 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0001
12/5/12 3:45:43 AM    kernel    est 0xc1-81-0000-0001
12/5/12 3:45:43 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0030
12/5/12 3:45:43 AM    kernel    before m_pUSBDevice->DeviceRequest 0x41-01-0000-0012
12/5/12 3:45:43 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0001
12/5/12 3:45:43 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0001
12/5/12 3:45:43 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0001
12/5/12 3:45:43 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0001
12/5/12 3:45:43 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0001
12/5/12 3:45:43 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0001
12/5/12 3:45:43 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0001
12/5/12 3:45:43 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0001
12/5/12 3:45:43 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0001
12/5/12 3:45:43 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0001
12/5/12 3:45:43 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0001
12/5/12 3:45:43 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0001
12/5/12 3:45:44 AM    kernel    est 0xc1-81-0000-0001
12/5/12 3:45:44 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0001
12/5/12 3:45:44 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0001
12/5/12 3:45:44 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0030
12/5/12 3:45:44 AM    kernel    before m_pUSBDevice->DeviceRequest 0x41-01-0000-0012
12/5/12 3:45:44 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0001
12/5/12 3:45:44 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0001
12/5/12 3:45:44 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0001
12/5/12 3:45:44 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0001
12/5/12 3:45:44 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0001
12/5/12 3:45:44 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0001
12/5/12 3:45:44 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0001
12/5/12 3:45:44 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0001
12/5/12 3:45:44 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0001
12/5/12 3:45:44 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0001
12/5/12 3:45:45 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0001
12/5/12 3:45:45 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0001
12/5/12 3:45:45 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0001
12/5/12 3:45:45 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0001
12/5/12 3:45:45 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0001
12/5/12 3:45:45 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0001
12/5/12 3:45:45 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0001
12/5/12 3:45:45 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0001
12/5/12 3:45:45 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0001
12/5/12 3:45:45 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0001
12/5/12 3:45:45 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0030
12/5/12 3:45:45 AM    kernel    before m_pUSBDevice->DeviceRequest 0x41-01-0000-0012
12/5/12 3:45:45 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0001
12/5/12 3:45:45 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0001
12/5/12 3:45:45 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0001
12/5/12 3:45:45 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0001
12/5/12 3:45:45 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0001
12/5/12 3:45:45 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0001
12/5/12 3:45:45 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0001
12/5/12 3:45:45 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0001
12/5/12 3:45:45 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0001
12/5/12 3:45:45 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0001
12/5/12 3:45:45 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0001
12/5/12 3:45:45 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0001
12/5/12 3:45:45 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0001
12/5/12 3:45:45 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0001
12/5/12 3:45:45 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0001
12/5/12 3:45:45 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0001
12/5/12 3:45:45 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0001
12/5/12 3:45:45 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0001
12/5/12 3:45:45 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0001
12/5/12 3:45:45 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0001
12/5/12 3:45:45 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0030
12/5/12 3:45:45 AM    kernel    *** Connected to client 206 ***
12/5/12 3:45:45 AM    kernel    Requesting status: 0x00000000
12/5/12 3:45:45 AM    kernel    Requesting status: 0x00000000
12/5/12 3:45:45 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0022
12/5/12 3:45:45 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0022
12/5/12 3:45:45 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0022
12/5/12 3:45:45 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0022
12/5/12 3:45:45 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0022
12/5/12 3:45:45 AM    kernel    before m_pUSBDevice->DeviceRequest 0xc1-81-0000-0022
12/5/12 3:45:45 AM    [0x0-0x1a01a].at.co.vsl.viennaensemblepro[206]    fwUpdaterActive: No updater detected
12/5/12 3:45:45 AM    [0x0-0x1a01a].at.co.vsl.viennaensemblepro[206]    Loading firmware package from resource fork
12/5/12 3:45:45 AM    [0x0-0x1a01a].at.co.vsl.viennaensemblepro[206]    fwUpdaterActive: No updater detected
12/5/12 3:45:45 AM    [0x0-0x1a01a].at.co.vsl.viennaensemblepro[206]    IO Config is set to : 0
12/5/12 3:45:46 AM    kernel    Requesting status: 0x00000000
12/5/12 3:45:46 AM    kernel    Requesting status: 0x00000000
12/5/12 3:45:46 AM    kernel    Requesting status: 0x00000000
12/5/12 3:45:46 AM    kernel    Requesting status: 0x00000000
12/5/12 3:45:46 AM    kernel    Requesting status: 0x00000000
12/5/12 3:45:46 AM    kernel    Requesting status: 0x00000000

Any help would be greatly appreciated. Thanks!

EDIT: Got it working. Go here: http://www.insanelymac.com/forum/topic/239311-usb3-capable-iousbfamily-1065106610671068/ and DL the attached kexts

The problem was that the provided IOUSBFamily doesn't support OHCI (USB 1.1 if i'm not mistaken)
 
Joined
Nov 8, 2012
Messages
67
Motherboard
P8Z77 V Pro, 24GB DDR3
CPU
i7 3770K @ 4.6GHZ
Graphics
Nvidia GTX 670 2GB
Mac
  1. Mac Pro
Classic Mac
Mobile Phone
  1. iOS
Sounds familiar to me.

When the Virus is set to Synced to Host, the DAW's project has to be at 44khz for the Virus not to freak out :banghead:
What I done was set the following;

Virus' Audio clock to 44khz
Cubase project to 44khz
Focusrite Saffire pro 24 DSP to 44khz (it follows cubase's lead anyway, but in windows the focusrite tells cubase what to do, strange lol)

Thats how I got the Virus to work with no problems.

But saying all that, you would think Access would allow 48khz to be more stable and offer up to 96khz for samples.

check these posts i done on the Access forum

http://virus.info/forum/index.php?page=Thread&threadID=3325

http://virus.info/forum/index.php?page=Thread&threadID=3691
 
Joined
Mar 1, 2014
Messages
2
Motherboard
z390
CPU
i9 9900k
Graphics
rx560
Hey guys had the problem too, but it had to o with usb 3 ports on the back. My virus kept telling mer there was a midi problem when i was connected to the back of my motherboard ports (ga-z87x-ud5h) Then i tried the usb 2 ports which are one the front of my case (factal design define R4) which are really the same thing as brackets connected to the motherboard internally, and it works now!! I use the latest virus os which is Virus TI Software Suite 5.0.8.00

Hope that helps you guys out
 
Joined
May 15, 2014
Messages
3
Motherboard
10.9.2
CPU
Intel Core i7 4.29GHz
Graphics
GTX 770
Mac
  1. Mac Pro
Classic Mac
Mobile Phone
I am still suffering this issue!
'MIDI Driver Failed'

My problem in brief:
when I load my virus plugin software in logic it comes up with the message ... \'MIDI driver failed - the midi driver failed to start or is not properly installed. this can happen if you have too many USB devices connected. Also try installing the software again\'

I have tried removing all other usb devices AND re installing the software (also have tried changing buffer size within logic and processing speed etc, giving logic a reboot every time).... still have the same issue... I know the Virus is USB hungry but even when I remove EVERYTHING I have the same issue.

I have just upgraded my computer to a Hack Pro: 4.29 GHz Intel Quad Core i7 16 GB 1600 MHz DDR3 NVIDIA GeForce GTX 770 2048 MB Software: OS X Mavericks 10.9.2 Virus software: 5.0.8.00 (which I have re-installed a few times to make sure)
I am using Logic 9 - Version 9.1.8 The motherboard I have (GIGABYTE 787X-UD7) supports 8 USB 3.0 ports and 2x thunderbolt ports.. Surely this machine should satisfy the needs of the Ti2.

Other heavy duty synth plugins seem to work fine ie. Omnisphere

I NEVER had this problem while i was using my previous set up: early 2008 iMac 2.8 Ghz Intel duo core also running mavericks 10.9.2 I\'ve been using my Virus Ti2 for nearly everything for the past 2-3 years and it has become a integral part of my sound. Its really slowing down my workflow while not having it fully functional! Desperate help needed!!

support told me this :

Dear Joe,
Thank you for your email. In this case I recommend to remove the entire TI OS suite from this Mac with the help of the Access uninstaller which you will find here:

APPLICATIONS -> ACCESS MUSIC

Additionally please remove the Virus Midi driver under

[macintosh hd]/[library]/[audio]/[midi drivers]

Whenever this has happened, please shut down the Mac, wait a few seconds and then restart the computer again. Next repair the disk permissions with the help of the "disk utility" program which you will find under

APPLICATIONS -> UTILITIES

and then install the very latest OS once again on the Mac and the TI and see if this helps. To install the TI OS again on the TI hardware, please unplug the power from your Virus TI and remove any other cable going from/to the TI. Wait approximately 30-60 seconds. While plugging back in the power only, hold down the EXIT button. This will force the unit into USB UPDATE MODE. Next try again to load in the very latest OS and check if this helps.


I have spent today following these steps above...

I completely unintalled virus software + midi drivers
repaired my disk permissions,
reinstalled latest available Virus TI2 software suite.

When I first re booted and checked if it had worked it gave me the same warning message -
‘G-Raid device detected on the same USB Hub.. please re configure USB set up and rescan..’

When I removed the device in question, and re launched the TI2 software suite, I somehow almost RANDOMLY managed to get passed the MIDI driver failed message, and I thought I was getting somewhere…. However now NO AUDIO OVER USB was getting to logic from the TI OS! after doing a restart, I was back to the same MIDI driver failed message....

I have then tried plugging analogue outputs 1/2 on virus into my sound card and bang, audio returns, exept its frequently with problems such as stuck notes/latent response….. MIDI is travelling to the virus TI2 over USB , but audio is not returning….

- I have tried changing some settings on the TI2 like sample rate 44.1-48kHz .. no difference, clock source internal/auto.. no difference.

My problem still persists, now its a case of - RANDOMLY unplugging and plugging my keyboard USB a few times, unplugging and plugging my virus USB, only sometimes (rarely) will the virus software will load..currently very..very.. unreliable.....
Even when it does load after 20 attempts, again no audio over USB, only analogue audio which, like I mentioned, has problems all over the place i.e. timing issues + artefacts… what shall I do !?!?

Very strangely, the Ti’s Core Audio + Bit Accurate devices show up on my Audio devices, and when I hook up my speakers to the analogue outputs of the TI, it works! its just the software that I can’t get working!


I have also tried using it without the software, running midi cables from my MIDI keyboard to the Virus TI2 (desktop by the way) and creating an external MIDI track with correct midi outputs, and an armed audio track..
In this set up, I STILL can’t get MIDI to send to the Virus, I have gone through the config menu on the TI hardware checking the MIDI settings, but to no avail. HOWEVER, when I click ‘SHIFT+SEARCH (AUDITION) on the Virus TI Hardware, Sound successfully makes it to the audio track I armed…


I have also tried using the TI software in Ableton, same MIDI Driver Failed message again..

MUST be something to do with the TI OS / my motherboards USB port settings/ config.....

CAN ANYONE HELP?! ;.;

Joe
 
Status
Not open for further replies.
Top