Taperssection.com
Gear / Technical Help => Post-Processing, Computer / Streaming / Internet Devices & Related Activity => Topic started by: Electric Cowgirl on October 13, 2003, 10:17:18 AM
-
Hey all-
Tried to run my UA5->laptop this past weekend and FAILED. Everything was working perfectly for Kaki King and the first half of Gordon. In the MIDDLE of Gordon's set I lost levels completly for what seemed like no reason... batteries were good, all settings were correct, all cables were properly connected.
When I tried to start recording again (wavelabs) I got an error message that was something like this: The audio card is not equipped to support the current bit rate and/or sample rate. Check to make sure the audio card is not in slave or autosync mode.
WTF?! Anyone else had this happen to them?
-
It sounds like a driver failure to me, and the only thing that should have helped would be to restart. Did you try that and see? Were you running dat backip? Also, are you using the MOST current driver edirol has out there or just the strdard driver that windows xp installs for it? I would check these things and then try running tests at home in front of a sound source. You are more than welcome to bring your stuff over and tape my speakers for hours on end to get this whole thing worked out.
Daryan
-
bummer!!!!!!!!!
sorry to hear
-
D- I installed the drivers that came with the UA5 on cd. There were different drivers for each OS.
Of course I tried to restart the comp. This was the first thing that I tired. I also checked to see if the UA5 was functioning properly thru the control panel. The computer was telling me that the UA5 was working but wavelabs all of a sudden decided it was not capable of sending 24/96.
I also tried switching it to 16/44.1 and wavelabs gave the same error message.
I took everything apart and put it back together, rebooted and still got the same error message. Totally baffeling!!! Every other problem has been something fairly simple, but this is strange.
-
I would uninstall all drivers that are on there, and get the updated drivers from edirol...I assume they have updated them anyway. Then, reconfigure everything and see if it becomes stable. As I said, I can start your gear at my house and run music through the computer for hours on end to test it all out. How was the show anyway?
daryan
-
D- Thanks for the offer to help.....but I would perfer to fix it myself. I am not at all trying to be rude, I apprecitate your help, but it does not help me when you take my computer and start pushing buttons. I have no idea what you are doing therefore I learn nothing. If I am going to run this laptop rig I need to learn how to troubleshoot and fix my machine. Getting advice from others will help me learn, but just turning it over to someone else won't help me become more computer literate.
I will try to uninstall the drivers and then reinstall them. If there is an updated version...ie newer than the cd they sent me I will try installing that driver instead. Thanks for the feedback!!!
-
I really do think it was most likely a driver failure issue!
Daryan
-
I have had problems with the drivers before....the computer always told me that the drivers weren't functioning properly and that I needed to reinstall them. This was not the case on Friday, but I will still try to reinstall.
-
that's weird that it would crap out right in the middle of something...did you check and make sure that the ua5 was still selected as the sound card? ya know, i think the problem is that 24/96 is not stable over usb, as has been debated before. perhaps the rig (i say that as i am not sure whether to specify drivers/recording software/hardware) just had enough of trying to take the 24/96 signal and just shit the bed.
becky, do extensive testing at home at 24/96, let it run for at least 2 hrs, and then repeat a few times!!! see if you get any dropouts or similar problems as this.
also, did you follow the advice i posted about setting up a laptop? it should in the archival section...anyways, those steps should help eliminate any other factors from causing disruptions in recording, ie. unwanted services taking up resources, etc.
i don't know too much about the buffer settings in wavelab (that's what you're using, correct?) but you may try playing with those and definitely post results of any and all tests so we can keep track of what you've done and what is left to try out. overall, good luck!!!
-
Becky, have you tried 24/48? There isn't a whole lot of difference between 96 and 48 at 24 bit!
Daryan
-
Becky, have you tried 24/48? There isn't a whole lot of difference between 96 and 48 at 24 bit!
Daryan
Well except for a much larger file :P
-
Becky, have you tried 24/48? There isn't a whole lot of difference between 96 and 48 at 24 bit!
Daryan
yes, do try it at 24/48 also if the problems persist at 24/96, i bet it will work fine in that scenario, thus proving my theory correct about 96khz being unreliabe over usb, and securing my position as the smartest man in the universe!!! :o
-
Can anyone actually HEAR the difference between 48 and 96 at 24 bit. Simp, you are definately about to take over the world.
daryan
-
Can anyone actually HEAR the difference between 48 and 96 at 24 bit. Simp, you are definately about to take over the world.
daryan
Well I dare say there is a difference. Other wise why would it exist. But by saying can anyone hear the difference may not be the right way to phrase that. SOme would have you believe that MD is as good as DAT because they can't hear the difference. We of course know better.
-
Guys....I tried changing the sample rates....it didn't make a difference. All of the settings were also correct. what I mean by this is: UA5 was properly selected as the soundcard, all settings on the UA5 were correct, all setting in wavelabs were correct. Perhaps another function was using up some of my resources causing the programs to screw up. I have some ideas that I will test, of course I will post my findings. Thanks!
-
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
-
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.
-
So you can't run coax and usb at different bitrates out of the ua5?
D
-
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.
-
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
-
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
-
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.
-
[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!!
-
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:)
-
Yeah, you need to use Edirol's driver for 24-bit... ASIO. Don't forget to turn that Advanced switch on!
-
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.
-
they tell you not to run minime usb at 24/96... it's not reliable. 24/48 over usb ONLY
-
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
-
I run usb out of the mini-me all the time and have yet to have one glitch @ 24/48
Daryan