VST Audiobay question...

  • Thread starter Thread starter pikingrin
  • Start date Start date
pikingrin

pikingrin

what is this?
Couldn't find a specific answer on this one... I am using Cubase SL3.0 (with the updates if that makes a difference), and I have had a bothersome question off and on for some time. Up under the VST system link in device setup, there is a place to test everything. I can't put a screen shot up here as my recording is done on a seperate computer. Anyway, there is a check box to the top right of the popup that is titled "Self Test". Below it, there are two drop down menus titled "ASIO input" and "ASIO ouput". I am assuming that this is some kind of diagnostic test to make sure the ASIO driver is operating correctly. When I select my input and output then check the self test, it starts it's process. It says transmitting and starts counting. There are two secitons under the transmitting that say "received" and "error", and whenever it transmits the test, it adds it to the error column instead of the received. What is this all about? Is there a problem with my setup somewhere?

I can still record and playback just fine, I have always been able to, but this has always confused me. If I can give any more specific info let me know, and thank you in advance for your responses!
 
I think I know what you're talking about.. when cubase tests the audio hardware and the i/o that you're using.. lets say its Asio Full Duplex.. it will check the actual buffer size that it can use, which refers more to cache and memory space for samples and sample lengths. If you're getting an error chances are that the latency is too low for the hardware you have... if you were to set the latency for a couple ms higher, I'd be willing to bet that your errors would cease..

just a thought
 
My buffers are set at 512k, about 12.something ms. I think I read somewhere that 12 ms is still high, so I don't know if that could be the reason behind it. Thanks for the input though!
 
What soundcard and drivers are you using? How many buffers are you using? What are your global setting on? Do you run full duplex?
 
Wow, okay... You will have to walk me through some of these questions... :o

My "soundcard" is my Tascam FW1804 interface, I disabled my realtek "card" in the bios and in windows. The only buffer that I have ever messed with is in the FW's control panel. Right now, I have it set at 256k, roughly 6.something ms of latency, just changed it this morning to see if it would make any difference.

Not sure what you mean by global setting or full duplex. Care to explain?
 
You should visit www.tascam.com and select the FW1804 from the pulldown menu to make sure you have the current version of the drivers. You should always use the drivers provided by the hardware manufacturer. Click on your ASIO driver pulldown menu and make sure that your tascam interface is selected. My guess is since your latency is below 10ms you have dedicated tascam drivers.

The tests you are doing are probably testing the multimedia drivers that come with Cubase which you don't use. Since this isn't causing you any problems I'd say if it ain't broke don't fix it. :)
 
Yeah, my master ASIO driver that is selected for use is the one that came with my Tascam unit. I have never updated the drivers though, but I plan on checking into that one of these days. Sucks because my machine is not hooked up to the net and all I need is for one virus to get onto my USB drive and my recording PC is shot. Or maybe I'm just a little paranoid, I dunno.
NYMorningstar said:
The tests you are doing are probably testing the multimedia drivers that come with Cubase which you don't use. Since this isn't causing you any problems I'd say if it ain't broke don't fix it.
Click to expand...
I like that answer more... :D

Just a little curiosity that has been in the back of my mind for a while. :o
 
Ignore those tests, they are MME ASIO tests and have no bearing on anything you will using with the Tascom
 
altitude909 said:
Ignore those tests, they are MME ASIO tests and have no bearing on anything you will using with the Tascom
Click to expand...

I have never had one of those test come up with anything good. Always errors, no matter what. I just ignore them now. Everything is working fine.
 
Cool to see that I'm not the only one. Thanks for all the feedback guys! :)
 
You must log in or register to reply here.
Back
Top