Topic: 24/96 Failure!??

[cpclark]

are'nt there two seperat drivers for 16 bits and 24 bits, i know when i had mine, it said that you cant have both drivers installed at the same time, you might have to roll back the drivers or unistall and reinstall the 16 bit driver and see if it works, and do the same for 24, hope this helps

[Simp-Dawg]

are'nt there two seperat drivers for 16 bits and 24 bits, i know when i had mine, it said that you cant have both drivers installed at the same time, you might have to roll back the drivers or unistall and reinstall the 16 bit driver and see if it works, and do the same for 24, hope this helps

hmm this does sound familiar chris...maybe that's why becky couldn't get it to work at 16 bit on the 2nd try.

[DaryanLenz]

So you can't run coax and usb at different bitrates out of the ua5?


D

[dklein]

I'm with Daryan on the driver failure causing your ongoing problems.  The initial one may have been caused by power interruption or the USB cable getting pulled?

I noticed that if I turned the advanced switch off, next time I booted up, the UA-5 was loaded with the standard driver automatically (with win2k) and the special driver was gone and needed to be reinstalled.  The UA-5 is still recognized, but not with the special driver (in my case the WDM) and you get the error message you described when trying 24 bit, any sample rate.

Other observations:
Twice lost power on the UA-5 - caused the pc to spontaneously reboot
If you turn off/disconnect the UA-5 you must close and restart Wavelab for it to be recognized again (UA-5 must be on)

I copied the driver install disc onto my pc so I don't get caught without them if it fucks up again.

[Electric Cowgirl]

I'm with Daryan on the driver failure causing your ongoing problems.  The initial one may have been caused by power interruption or the USB cable getting pulled?

 Definatly weren't any power issues or pulled cables.

I noticed that if I turned the advanced switch off, next time I booted up, the UA-5 was loaded with the standard driver automatically (with win2k) and the special driver was gone and needed to be reinstalled.  The UA-5 is still recognized, but not with the special driver (in my case the WDM) and you get the error message you described when trying 24 bit, any sample rate.

This could be part of the issue....must find user manual!!

Other observations:
Twice lost power on the UA-5 - caused the pc to spontaneously reboot
If you turn off/disconnect the UA-5 you must close and restart Wavelab for it to be recognized again (UA-5 must be on)

I am aware that the UA5 must be plugged in and turned on before the computer is booted up and that the power must not be interrupted without shutting down the comp first.

I copied the driver install disc onto my pc so I don't get caught without them if it fucks up again.

GREAT IDEA! +T for the feedback!!!


The only thing that I don't understand is why the problem occured in the middle of the set!! If the drivers weren't working properly why was I be able to get a signal in the first place??  

Everything was working perfectly for Kaki King.  I shut everything down and changed the UA5 battery before Gordon.  I rebooted my comp. and everything was perfect. I checked to make sure the UA5 was selected as the soundcard, checked that the autosplit function was on, and checked all of the UA5 settings.   Everything looked good and I was getting nice levels for about and hour, then blam nothing.  When I noticed that there weren't any levels I tried to start recording again.  This is when I got the error message: The audio card cannot support the current bit rate.  Check to make sure it is not in slave or autosync mode.    

Does this inspire any other ideas??
Thanks

[dmonterisi]

i have 2 very unlikely thoughts...first is that with PCs, shit just happens that you can't explain...it's not as bad for me now under xp pro, but my old pc used to simiply stop every so often.  but that's not a very good explanation.

my only other thought is that you had some background service kick on at that point that caused too much stuff to be going on inside the machine at once.  for example, any power managment settings or anything like that might've kicked on right at an hour or anything like that?  the only thing i can suggest is reinstalling and then trying to recreate the situation at home and see if it does it again...good luck
-damon

[dmonterisi]

one other thing i just thought of...what did you have your auto-split set for?  if the failure occurred right around an hour, that's right at the 2 gig limit (1 hour 24/96~=2gig)...maybe something went haywire when wavelab tried to split it or something else associated with the autosplit.

[Electric Cowgirl]

[quote author=dmonterisi link=board=5;threadid=7888;start=15#msg91959 date=1066150003

my only other thought is that you had some background service kick on at that point that caused too much stuff to be going on inside the machine at once.  for example, any power managment settings or anything like that might've kicked on right at an hour or anything like that?  the only thing i can suggest is reinstalling and then trying to recreate the situation at home and see if it does it again...good luck
-damon

This is a good thought!  I will go back to the thread Simp mentioned and set it up so no background services can kick in.  I changed the power management settings to make sure that the screen stayed on the whole time and the comp. would not go into standby mode at all.

I think I will uninstall the UA5 drivers and any extra programs that I don't want, defrag it, reinstall the drivers, copy them to my desktop, and set it up following the instructions in the thread Simp mentioned...to prevent background services from kicking in.  Then I will do some tests and see if this bs happens again.

Thanks guys!!

[Electric Cowgirl]

Woohooo....success on Friday for ulu.  I'm still not sure what happened at Gordon, but heres what happened friday....

I didn't change anything.  I showed up friday and decided to plug it in and see what happens.  So I set-up and fired the lappy up.  Same error (see first post).  So I check all of the settings on the UA5...they were correct.  I check all the settings on wavelabs and change the file to 24/96 from 16/44.1....and wahla it worked.  So who ever mentioned that the UA5 uses different drivers for 16 bit and 24 bit is 100% correct!!  

Now if I could only find my manual perhaps this type of thing wouldn't happen:)

[mirth]

Yeah, you need to use Edirol's driver for 24-bit... ASIO. Don't forget to turn that Advanced switch on!

[hzgone]

Just to add to this real quick.  I had nothing but problems running with usb and the mini-me, no matter if i was running at 16/44 or 24/96 switched to a vxpocket and all fixed.  But it looks like you got it all working again.

[Tim]

they tell you not to run minime usb at 24/96... it's not reliable. 24/48 over usb ONLY

[hzgone]

that is what i read from apogee a little while ago, but i still had problems with usb.  They are gone now thanks to the vxpocket

[DaryanLenz]

I run usb out of the mini-me all the time and have yet to have one glitch @ 24/48


Daryan