Latency in headphones with vocal track

  • Thread starter Thread starter Jae
  • Start date Start date
Yeah, I knew you knew it... but yours was the best post to reply to in context. ;)
 
ecc83 said:
Sorry Glen but, where you bin mate?!
A mic CAN connect directly to a computer via a usb lead!
Dave.
Click to expand...
Actually, a mic can not directly feed a USB signal. USB is a serial digital protocol. Microphones are, by design and purpose, analog devices. Somewhere along the path there is a pre-amp and an A/D converter. There is quite possibly an entire 'sound card' built into the OPs microphone. What I was trying to lead the OP to realize is that IF there is a headphone output on the USB microphone that this would be the best point to monitor the signal (to avoid latency) rather than using the internal sound card which rarely provides acceptable results.

The Tracklink USB Interface does not appear to allow monitoring at the interface. The OP will probably never be able to get acceptable latency using it for multitracking.

As to the Cubase recommendation, Audacity or Sonar or Pro Tools or Reaper will all perform as well once they get a properly digitized file. I personally prefer Sonar, but I also personally prefer Fords. Other people swear by Chevys and Hondas. You have to drive a few DAWs before you can decide what is best for you. Nothing wrong in starting with Audacity.

It appears that there are more than a few ASIO zealots on this board as well. Sometimes ASIO is the only answer, but it has a lot of limitations that are not encountered using other drivers. Most of my gear works better with WDM/KS, but the cheaper gear works better with ASIO. You have to experiment with your equipment to find what works best.

Glen
 
Last edited:
gcolbert said:
Actually, a mic can not directly feed a USB signal. USB is a serial digital protocol. Microphones are, by design and purpose, analog devices. Somewhere along the path there is a pre-amp and an A/D converter. There is quite possibly an entire 'sound card' built into the OPs microphone. What I was trying to lead the OP to realize is that IF there is a headphone output on the USB microphone that this would be the best point to monitor the signal (to avoid latency) rather than using the internal sound card which rarely provides acceptable results.

The Tracklink USB Interface does not appear to allow monitoring at the interface. The OP will probably never be able to get acceptable latency using it for multitracking.

As to the Cubase recommendation, Audacity or Sonar or Pro Tools or Reaper will all perform as well once they get a properly digitized file. I personally prefer Sonar, but I also personally prefer Fords. Other people swear by Chevys and Hondas. You have to drive a few DAWs before you can decide what is best for you. Nothing wrong in starting with Audacity.

It appears that there are more than a few ASIO zealots on this board as well. Sometimes ASIO is the only answer, but it has a lot of limitations that are not encountered using other drivers. Most of my gear works better with WDM/KS, but the cheaper gear works better with ASIO. You have to experiment with your equipment to find what works best.

Glen
Click to expand...
....Right. I was trying to K.I.S.Sir.

Dave.
 
I just have some cheap Audio Technica condenser mic for now. But I do intend on recording songs with vocals and all the instruments.
 
Jae said:
I just have some cheap Audio Technica condenser mic for now. But I do intend on recording songs with vocals and all the instruments.
Click to expand...

That's fine. Get a decent audio interface and use the latest drivers from the manufacturer of your hardware. Don't get fancy with ASIO4ALL or other third party solutions unless the stock driver proves inadequate.

An audio interface is specifically designed to solve the exact problems you have. Your mic and headphones connect to the same device which can bypass the long trip through the computer and back for monitoring live inputs like your mic with little or no latency.
 
I was looking at the Tascam US-1800 USB 2.0. It has 8 mic inputs (which I need for recording drums, eventually) and a software program (Cubase LE5 that comes with it). What are your thoughts on that?
 
Jae said:
I was looking at the Tascam US-1800 USB 2.0. It has 8 mic inputs (which I need for recording drums, eventually) and a software program (Cubase LE5 that comes with it). What are your thoughts on that?
Click to expand...

I used the Tascam interface for years. Never had an issue. And I have been with Cubase ever since. All of the audio tracks on my website were done with the Tascam US1800 or the 1641(the 1800's predecessor).
 
I use a US-1800. It has never been a problem. I do the same, use most of it when tracking drums.

My only complaint about it is the headphone amp is a bit whimpy. I had to add a phone amp to it but other than that it always wprks.
 
If I decide to get a different DAW will the AI still work. (Am I using the acronyms correctly? lol)
 
bouldersoundguy said:
Sure? Starting with PT9 they opened it up to a wide range of interfaces. Maybe it's an exception?
Click to expand...

I think it has more to do with how Tascam drivers deal with buffers. I may be wrong, but I have heard of issues with changing buffer size with the 1800/1641 in Protools, because the Tascam control panel does not delegate exact buffer size numbers.

I have no way to verify this myself.
 
Yeah, I think there's a spec an interface has to comply with to be compatible with PT9 and up.
 
AND read the stickies they cover almost everything you want to know.
 
Jae, I think maybe you should just sit this one out for a while. ;)

When the forum has finished eliminating all possibilities through guesswork and what-not, someone will be in contact with you.
At least *I think* that's how it works….
 
(There are usb mics out there now. They plug directly into the computer.) Rod Norman

gcolbert said:
Dave's reply is a bit short, but the issue is that you are having the first problem that everyone has when they start recording with a computer. There are literally thousands of posts on this board that are identical to yours and thousands of replies. A little research on your part would have found at least a few of there.

The problem is called latency and it is the amount of time that it takes your computer to input the signal. process it, then send it back out to your headphones. You didn't provide very much information on what kind of interface you are using to plug your microphone in. A USB cable can not connect directly to a microphone, there must be something else going on here. If there is a headphone jack somewhere between the USB and the microphone, try monitoring (plugging your headphones) in there instead of your computer.

Personally, I think the UR22 and Cubase are not the best options, but you will find that everyone on this board is biased to the point of religion about what the best tools are. You will have to learn a bit more on your own (and Audacity may be a good starting point). The first thing that you need to get right is that stuff between the USB and the microphone.

How exactly (with what products) are you connecting the microphone up?

Glen
Click to expand...
 
ASIO4ALL is very good and would be a good starting point for him.
 
At the top of each sub forum here, the 'stickies' are placed on top of list because they were worthy of giving the most information in one thread.
 
You must log in or register to reply here.
Back
Top