Input Monitoring latency

Author
rheil
Max Output Level: -90 dBFS
  • Total Posts : 18
  • Joined: 2010/01/05 08:40:20
  • Status: offline
2010/01/28 07:23:18 (permalink)

Input Monitoring latency

Hi,
 
I just bought a new interface, its the zoom r16. I am having some latency issues. My playback is fine but whenI turn on the input echo and insert a guitar plugin I get Latency popping.
 
I tried Wdm/km, Asio, and Asio4All with no success. Its a pretty cool interface but i ran out of options on how to solve the problem.
Im running Sonar 8 producer.
 
Anyone have any ideas?
#1

20 Replies Related Threads

    emwhy
    Max Output Level: -62 dBFS
    • Total Posts : 1402
    • Joined: 2006/01/03 15:09:02
    • Status: offline
    Re:Input Monitoring latency 2010/01/28 07:36:56 (permalink)
    What size is your buffer? Generally a buffer size of about 128 samples will get your latency down to about 2.5 ms. Anything above that for inout monitoring will start to give you issues. Also do you have any additional plug-ins across a buss or the master buss? I had a project where I forgto that Ozone was patched across a buss and got all kinds of latency while tracking a vocal until I figured it out.
    #2
    rheil
    Max Output Level: -90 dBFS
    • Total Posts : 18
    • Joined: 2010/01/05 08:40:20
    • Status: offline
    Re:Input Monitoring latency 2010/01/28 07:43:38 (permalink)
    I have it at 128 and i also tried 256. It doesnt seem to like 128 for some reason. Playback is best at 256 and 46.4 ms
    I have no additional plugins being used.
    #3
    WDI
    Max Output Level: -54.5 dBFS
    • Total Posts : 2069
    • Joined: 2007/08/28 02:31:11
    • Status: offline
    Re:Input Monitoring latency 2010/01/28 08:31:42 (permalink)
    Looks like the zoom r16 driver is ASIO so as recommended by Zoom definetly use ASIO as your driver mode in Sonar (Options/Audio/Advanced). Also, make sure no other drivers are selected besides the r16 (Options/Audio/Drivers). This confuses people sometimes, if ASIO4All drivers are selected you must first uncheck all the ASIO4All driver to be able to select the Zoom ASIO drivers. This is because the ASIO protocol only supports one driver. And Sonars interface could be more user friendly in this area. But anyways...Also, unless you have some other device that needs ASIO4All, I would uninstall it just to keep things clean. I have no experience with ASIO4All to know if it could cause problems or not.
     
    The section under Option/Audio/Advanced/File System is not where you set latency for input monitoring. Leave both Read and Write caching unchecked.

    You should probably also check out Zooms site to make sure you have the latest drivers and firmware for the r16.
    http://www.zoom.co.jp/english/download/software/r16.php

    When using ASIO you set the buffer setting outside of Sonar. I'm not sure if the r16 provides an interface for doing this but if it does it should open up when selecting the ASIO Panel button under Options/Audio/General.

    However, I'm not really sure what problem you are having from the description. Are you getting a delayed sound when playing the guitar. Or are you getting crackles like your CPU can not keep up and a drop is about to happen?

    post edited by WDI - 2010/01/28 08:52:02

    Sonar 7 PE
    Windows XP Pofessional (SP3)
    MSI K8N Neo4-F
    AMD Athlon 64 3500+
    2 GB PC 3200 Ram
    RME Fireface 800
    Edirol FA-66
    CM Labs MotorMix

    Old stuff: ARJO
    #4
    rheil
    Max Output Level: -90 dBFS
    • Total Posts : 18
    • Joined: 2010/01/05 08:40:20
    • Status: offline
    Re:Input Monitoring latency 2010/01/28 09:19:42 (permalink)
    I am using the updated zoom driver, I also uninstalled the Asio4All driver after it was no help. The problem is the crackling noise, If i mess with the buffer its just really bad delay. I have a pretty good PC, AMD Athalon 2.8 Ghz dual core w/4gb of Ram. I am only using one driver at a time still with bad results. I will try the other things you mentioned when i get home from work.
    #5
    papa2005
    Max Output Level: -43 dBFS
    • Total Posts : 3250
    • Joined: 2009/08/01 16:43:11
    • Location: Southeastern, US
    • Status: offline
    Re:Input Monitoring latency 2010/01/28 09:21:57 (permalink)
    What guitar plugin are you using? That could be the culprit.

    Regards,
    Papa

    CLICK HERE for a link to support for SONAR 8.5

    CLICK HERE to view a list of video tutorials...
     
    CLICK HERE for a link to Getting Started with Session Drummer 3...
    #6
    rheil
    Max Output Level: -90 dBFS
    • Total Posts : 18
    • Joined: 2010/01/05 08:40:20
    • Status: offline
    Re:Input Monitoring latency 2010/01/28 09:32:46 (permalink)
    I am using TH1 Overloud, I tried different plugins and still have the  same issues. Even if i use no plugins whatsoever I still hear the crackling noises. Its only when i have the input echo turned on.
    #7
    CJaysMusic
    Max Output Level: 0 dBFS
    • Total Posts : 30423
    • Joined: 2006/10/28 01:51:41
    • Location: Miami - Fort Lauderdale - Davie
    • Status: offline
    Re:Input Monitoring latency 2010/01/28 11:02:28 (permalink)
    You need an ASIO buffer of 32, 64 or 128. Since 128 doesn't work for your pc, try 64...
    Wait, i just seen your using a Zoom s an interface. If you want low latency, get a sound card /interface, not a recording device. That zoom lacks the drivers needed for low latency. Use the zoom as it was intended. To Record audio.
    If you use the hardware as it was intended for, youll have no problems. So i would get a sound card (and stop using the zoom as one)...
    Just my simple (yet thoughtful) thoughts....
    Cj

    www.audio-mastering-mixing.com - A Professional Worldwide Audio Mixing & Mastering Studio, Providing Online And Attended Sessions. We also do TV commercials, Radio spots & spoken word books
    Audio Blog
    #8
    brundlefly
    Max Output Level: 0 dBFS
    • Total Posts : 14250
    • Joined: 2007/09/14 14:57:59
    • Location: Manitou Spgs, Colorado
    • Status: offline
    Re:Input Monitoring latency 2010/01/28 11:16:32 (permalink)

    Playback is best at 256 and 46.4 ms

     
    Where are you seeing 46.4ms? Is that what SONAR is reporting for round-trip latency? Yikes. Must be a ton of "hidden" latency. Definitely sounds like this thing is not optimized for use as an interface.
    post edited by brundlefly - 2010/01/28 11:19:29
    #9
    rheil
    Max Output Level: -90 dBFS
    • Total Posts : 18
    • Joined: 2010/01/05 08:40:20
    • Status: offline
    Re:Input Monitoring latency 2010/01/28 11:27:35 (permalink)
    Thats under the Wdm/km not the Asio. I cant get anything right with the Asio. I will try the Asio with a different buffer and see if that helps.  I just got this as a upgrade over my toneport Ux2. It says it can also be used as a interface.
    #10
    MurMan
    Max Output Level: -70 dBFS
    • Total Posts : 1040
    • Joined: 2008/12/10 19:11:36
    • Location: Sunny San Diego
    • Status: offline
    Re:Input Monitoring latency 2010/01/28 11:37:13 (permalink)
    rheil

    ... The problem is the crackling noise, ....
     
    Crackling noise is usually a symptom of maxing out an input, not latency.  Check all of your levels and peak indicators. 



    Sonar 8PE & VS, Presonus Firestudio, VS-100, AlphaTrack, Nord Stage Compact, Roland Sonic Cell,  Axiom 49, dbx 386, Event TR-8's, Kawai 650, ...
    #11
    brundlefly
    Max Output Level: 0 dBFS
    • Total Posts : 14250
    • Joined: 2007/09/14 14:57:59
    • Location: Manitou Spgs, Colorado
    • Status: offline
    Re:Input Monitoring latency 2010/01/28 11:47:22 (permalink)
    Crackling noise is usually a symptom of maxing out an input, not latency. Check all of your levels and peak indicators.

     
    I disagree. Clipping distortion is distinctly different sound than "crackling" from dropped buffers. I think he's on the right track.
     
    I would suggest Googling the Web at large. There's probably an answer out there. You can also Google with site:forum.cakewalk.com appended to find more threads here. I found one that suggested the R16 has an "interface" mode setting. Have you found and enabled that?
     
     
    #12
    MurMan
    Max Output Level: -70 dBFS
    • Total Posts : 1040
    • Joined: 2008/12/10 19:11:36
    • Location: Sunny San Diego
    • Status: offline
    Re:Input Monitoring latency 2010/01/28 12:26:10 (permalink)
    brundlefly
    I disagree. Clipping distortion is distinctly different sound than "crackling" from dropped buffers. I think he's on the right track. 
     
    You may be right.  But I hear lots people describe clipping as crackling.  The terminology being used here isn't that precise.  Google "latency popping", the op's description, and you get this thread as #2. 
     
    Never hurts to eliminate common problems first. 



    Sonar 8PE & VS, Presonus Firestudio, VS-100, AlphaTrack, Nord Stage Compact, Roland Sonic Cell,  Axiom 49, dbx 386, Event TR-8's, Kawai 650, ...
    #13
    rheil
    Max Output Level: -90 dBFS
    • Total Posts : 18
    • Joined: 2010/01/05 08:40:20
    • Status: offline
    Re:Input Monitoring latency 2010/01/28 12:40:02 (permalink)
    It prompts you when you plug in the USB if you are using it as a interface, i will check and see if there is any other setting that needs to be disabled when in use as a interface. It's definitly not a clipping problem cause I hear the crackling popping noise even at a low signal.
     
    I chose this model over the V-Studio 100 since it records 8 inputs simultaneously. I heard the vstudio does not.
    I wanted to use this as a interface and portable recorder since I play in a rock cover band and it would be nice to record practices and shows. hopefully its able to do that. 
    #14
    CJaysMusic
    Max Output Level: 0 dBFS
    • Total Posts : 30423
    • Joined: 2006/10/28 01:51:41
    • Location: Miami - Fort Lauderdale - Davie
    • Status: offline
    Re:Input Monitoring latency 2010/01/28 12:41:24 (permalink)

    Thats under the Wdm/km not the Asio. I cant get anything right with the Asio. I will try the Asio with a different buffer and see if that helps. I just got this as a upgrade over my toneport Ux2. It says it can also be used as a interface.
    They claim and say allot of things. but that zoom has not been proven to be good. dont believe everything they tell you ansd read. Of course they want you to buy their product and theyll claim anything. Your toneport was 10 times better than the zoom as an interface. Get an audio soyund card and your problems will go away. Its that simple. Zoom doesnt have good Drivers for low latency. Thats a fact
    Cj
    I chose this model over the V-Studio 100 since it records 8 inputs simultaneously

    yuo should have researched before buying the zoom. The V-studio is way way better. If you want 8 channels to record with, Echo or Motu or RME or m--audio would have been a way way way better choice. Stop wasting your time with that zoom
    post edited by CJaysMusic - 2010/01/28 12:43:23

    www.audio-mastering-mixing.com - A Professional Worldwide Audio Mixing & Mastering Studio, Providing Online And Attended Sessions. We also do TV commercials, Radio spots & spoken word books
    Audio Blog
    #15
    WDI
    Max Output Level: -54.5 dBFS
    • Total Posts : 2069
    • Joined: 2007/08/28 02:31:11
    • Status: offline
    Re:Input Monitoring latency 2010/01/28 12:42:56 (permalink)
    CJaysMusic


    You need an ASIO buffer of 32, 64 or 128. Since 128 doesn't work for your pc, try 64...
    Wait, i just seen your using a Zoom s an interface. If you want low latency, get a sound card /interface, not a recording device. That zoom lacks the drivers needed for low latency. Use the zoom as it was intended. To Record audio.
    If you use the hardware as it was intended for, youll have no problems. So i would get a sound card (and stop using the zoom as one)...
    Just my simple (yet thoughtful) thoughts....
    Cj


    Actually, if you check out the r16 they market it as an interface with low latency ASIO drivers and comes with Cubase4, as well as a control surface. Perhaps he just doesn't have it set up correctly in Sonar.
    post edited by WDI - 2010/01/28 12:44:21

    Sonar 7 PE
    Windows XP Pofessional (SP3)
    MSI K8N Neo4-F
    AMD Athlon 64 3500+
    2 GB PC 3200 Ram
    RME Fireface 800
    Edirol FA-66
    CM Labs MotorMix

    Old stuff: ARJO
    #16
    CJaysMusic
    Max Output Level: 0 dBFS
    • Total Posts : 30423
    • Joined: 2006/10/28 01:51:41
    • Location: Miami - Fort Lauderdale - Davie
    • Status: offline
    Re:Input Monitoring latency 2010/01/28 12:46:35 (permalink)
    Everything that ive seen (read) about that zoom is bad. There were a few threads on this unit and noone could get low latency and/or good performance with it.
    This poster is having the exact same problems as the others. The others never solved it either. Its not looking good for the zoom.
    And like i said, dont believe the marketing gimmicks. They can claim low latency. I can claim im good looking and have hair.
    Cj
    Example. The Art tubefire says they have low latency drivers. That interface is crap also. you always go with what works. yuo never go by what the company says/ Common sence will take you along ways
    Cj
    post edited by CJaysMusic - 2010/01/28 12:48:02

    www.audio-mastering-mixing.com - A Professional Worldwide Audio Mixing & Mastering Studio, Providing Online And Attended Sessions. We also do TV commercials, Radio spots & spoken word books
    Audio Blog
    #17
    brundlefly
    Max Output Level: 0 dBFS
    • Total Posts : 14250
    • Joined: 2007/09/14 14:57:59
    • Location: Manitou Spgs, Colorado
    • Status: offline
    Re:Input Monitoring latency 2010/01/28 12:54:25 (permalink)
    Never hurts to eliminate common problems first.

     
    True. But since a larger buffer elminated the "crackles" that suggested it is indeed a buffering problem. A larger buffer would not affect clipping. No biggie. Just wanted to head off what I thought was a "red herring".
    #18
    bitflipper
    01100010 01101001 01110100 01100110 01101100 01101
    • Total Posts : 26036
    • Joined: 2006/09/17 11:23:23
    • Location: Everett, WA USA
    • Status: offline
    Re:Input Monitoring latency 2010/01/28 14:57:56 (permalink)
    My money's on the amp sim as the culprit. Its own latency is forcing the OP to set the buffers lower than they might otherwise require for acceptable latency.


    All else is in doubt, so this is the truth I cling to. 

    My Stuff
    #19
    rheil
    Max Output Level: -90 dBFS
    • Total Posts : 18
    • Joined: 2010/01/05 08:40:20
    • Status: offline
    Re:Input Monitoring latency 2010/01/28 15:42:16 (permalink)
    bitflipper


    My money's on the amp sim as the culprit. Its own latency is forcing the OP to set the buffers lower than they might otherwise require for acceptable latency.


    I was thinking the same thing at first, but It happens even with a dry signal.
    #20
    mitchpetel
    Max Output Level: -85 dBFS
    • Total Posts : 275
    • Joined: 2007/11/06 12:19:41
    • Location: London, Ontario, Canada
    • Status: offline
    Re:Input Monitoring latency 2010/09/29 10:12:03 (permalink)
    Bottom Line is that R16 and Sonar are not a good match. I have gone through all of the steps above as well and still not had any luck. I have found lots of posts on the net with other people having similar lack of results with compatibility.

    My next step is to install the copy of Cubase LE that came with the R16 and try integrating those two just to see if it can do what it claims.

    Rheil: If you need to record multiple track simultaneously do what I do. Record up to 8 tracks at a time on the R16 (using the built-in metronome) and then connect it to your PC in card reader mode and just import the wav files in to your DAW.

    Good Luck

    Sonar X1 Studio, Win 10 64bit , Roland Quad-Capture, (Alesis MultiMix16 USB 2.0 , Zoom R16), M Audio KeyRig 49 USB controller ezDrummer, NI Studio Drummer, Groove Monkee MIDI loops, PODxt,
    #21
    Jump to:
    © 2026 APG vNext Commercial Version 5.1