Page 1 of 1

Audiophile Firewire users??? Cue button freezing???

Posted: Fri Sep 09, 2005 10:34 am
by DJSK
I just wanted to see if there are any other Audiophile Firewire users out there with my similar problem? I use the Audiophile Firewire to cue between tracks when using Live. Sometimes the software will freeze up momentarily and then an audiodropout will occur and then the Cue button on my audiophile will freeze and I can no longer switch between tracks. From then on I will have audio dropouts periodically. As soon as I close out ableton the cue button unfreezes and starts working again. I can restart live for a little bit but eventually the problem will happen again. It seems to happen more frequently if have my Evolution UC-33e controller hooked up. Or when I don't disable the stock sound card. However it still happens. It also happens in version 4.1.4. While not as frequently as version 5.0.1 it does happen. It also happens in the new 5.0.2 beta as well. Any one else have this same problem and have any suggestions? ASIO4ALL Drivers don't help nor does increasing my buffer settings. Any one with any suggestions. Even the support staff seem to be a little stumped by this one.

Posted: Fri Sep 09, 2005 2:47 pm
by stallos
I have experienced a similar problem with the cue switching button.

Every once in a while it just stops working, in addition to that sometimes the headphones volume control also stops working. You can still control things from the M-audio control panel but its quite annoying.

Mine seems to fail sometimes independently of live.

anyone else, I doubt DJSK and I are the only ones

cheers
stal

Posted: Fri Sep 09, 2005 2:52 pm
by poshook
same here, but I am sure it is not Live's problem because the same bug is with Logic 5. M-Audio driver seems to be bad

Posted: Fri Sep 09, 2005 3:14 pm
by Morphos
It's not Live's fault, the M-Audio driver is crap. I've had exactly the same problem with my Audiophile, not to mention countless others since I got it. Each new driver fixes something and breaks something else. The front panel controls freezing up was a known issue at M-Audio which was supposedly fixed in the latest driver release, it didn't fix it for me so I've sent my Audiophile back.

Posted: Fri Sep 09, 2005 8:06 pm
by DJSK
I guess I will just have to wait it out and see if they can get a decent drivers. Thanks.

Posted: Fri Sep 09, 2005 8:09 pm
by AdamJay
hmm, mine doesn't exhibit this behavior.

but i'm still not entirely happy with the Firewire Audiophile. Its too bad, the price was good, it sounds good, and has all the features one would want for a good firewire device with cueing capabilities.

Posted: Fri Sep 09, 2005 8:56 pm
by Morphos
AdamJay wrote:hmm, mine doesn't exhibit this behavior.
Is that on Mac or PC? I reckon these problems are specific to PC, which certainly points to a driver issue. I've sent mine back for testing and so far they have been unable to reproduce the fault that I and so many others are experiencing. But otherwise, all the things you mentioned are the reason I bought it in the first place.

Posted: Fri Sep 09, 2005 9:01 pm
by AdamJay
Morphos wrote:
AdamJay wrote:hmm, mine doesn't exhibit this behavior.
Is that on Mac or PC? I reckon these problems are specific to PC, which certainly points to a driver issue. I've sent mine back for testing and so far they have been unable to reproduce the fault that I and so many others are experiencing. But otherwise, all the things you mentioned are the reason I bought it in the first place.
on a Mac, indeed.
not without crappy drivers on OSX either though.
can't get a usable latency below 12ms, can't hotplug, baaaahhh...

Posted: Sat Sep 10, 2005 1:25 am
by inis
ive had similair problems but mine went away just by opening the M-Audio settings menu and leaving it open during my set. I just have a preset with the channels and routing set up the way i want and i open it before i start my set. Havnt had any problems since.

Posted: Sat Sep 10, 2005 4:47 am
by DJSK
8O What? Man if that is all I have got to do I am going to feel like a moron. I guess I will have to try that.