64 bit driver issue with CME VX series and MainStage???

Question

64 bit driver issue with CME VX series and MainStage???

I was using a Mac Book Pro 2.16 GHz Core Duo and was having major issues with CPU usage in Main Stage so I upgraded to the new 2.4 GHz Core 2 Duo, and the CME VX8 audio interface doesn't show up as an output option anymore... Does Mac OS 10.5 not have 64 bit drivers for the CME VX audio interface? Also, I thought I'd see a performance difference with the new MacBook Pro, but the difference is negligible. Talk about a disappointment... Is there anything that I can do besides adding memory (ordering 4 gig today) that could help with the performance of Main Stage?

Thanks,
Ron

MacBook Pro 17" 2.4GHz 2GB RAM, Mac OS X (10.5.1)

Posted on Dec 18, 2007 10:31 AM

Reply

Answer 1

aerol

Level 3

555 points

Dec 18, 2007 10:46 AM in response to Ronald Johns Jr.

Is the audio interface class compliant? If not then you will need to install drivers from the manufacturer. Can the audio interface be seen by Logic, system prefs or Audio MIDI Setup? If not then it's not a problem with Mainstage.

It would be odd if only Mainstage couldn't see a device... since it shows the devices that are presented to it by CoreAudio and CoreMIDI.

Reply

Answer 2

Dec 18, 2007 10:49 AM in response to Ronald Johns Jr.

Actually, a second reboot fixed it... One other problem is I only have 48k as an option, which I've noticed uses a bit more processing power than 44.1... Is this a limitation of the interface? I'm still having processor issues too - I can't have more than 2 preset patches layered at once... Otherwise, the proc will max out and kill the sound. I've got the I/O buffer set to 256 too - this setting has a bit more latency than what I'd like, but it's usable... Any suggestions would be greatly appreciated...

Message was edited by: Ronald Johns Jr.

Reply

Answer 3

Dec 18, 2007 10:52 AM in response to aerol

That was one thing I should have checked, but it seemed strange after the first reboot that the audio interface wasn't recognized, but the midi interfaces were. At any rate, it seems to be fine now. I guess my questions about performance issues should be in a different thread. I'll mark this is answered and start a new thread.

Reply

Answer 4

Dec 18, 2007 10:54 AM in response to Ronald Johns Jr.

The driver issue was resolved with a second reboot. I'll start a new thread about the proc issues...

Reply

Answer 5

Feb 13, 2008 12:48 AM in response to Ronald Johns Jr.

Guys be careful with CME VX you have to use the USB port near to the power supply otherwise you are going to have major problems.
Because this is the high speed port...

Reply

Answer 6

Feb 13, 2008 9:07 AM in response to dimitris108

It only has 1 USB port to use... It has a USB hub built in, but it only has one B-Type plug that is available for connecting to a computer...

Reply

Answer 7

Feb 13, 2008 9:44 AM in response to Ronald Johns Jr.

No I talking about usb port on mac book pro.

Reply

Answer 8

Feb 13, 2008 9:45 AM in response to Ronald Johns Jr.

Guys be careful with CME VX you have to use the USB port near to the power supply on the mac book pro otherwise you are going to have major problems.
Because this is the high speed port...

Reply

Answer 9

Feb 13, 2008 11:31 AM in response to dimitris108

Oh man! Ok - I guess I've just been lucky since I've always used the USB port next to the power port during live gigs... I thought all 3 USB ports on the MB Pro were 2.0 though... Also, isn't the CME VX8's USB port 1.1 anyway? I didn't think it was 2.0...

Reply