LIMITED TIME OFFER: $0.99 for 3 months of Music Maker Supreme. $14.99/mo after. Not for users in Quebec. Ends 12/15/19. Terms apply.
Get it Now

Latency Correction

Comments

10 comments

  • Official comment
    Jess

    Hi Luke, thank you for your suggestion! At the end of each month we'll review all of the feature requests that we’ve received and pass them on to the rest of the team. Please let us know if there’s anything else!

    Comment actions Permalink
  • batyalevy

    I have the same problem. In audacity, one is able to measure the latency (by laying down a click track, counting to it, and then measuring the precise number of seconds of latency), and then audacity has a place where you can enter that number so that it automatically shifts your recording each time to account for the latency. Here is a video about it:

    https://www.youtube.com/watch?v=CEIEDGExoqM

    0
    Comment actions Permalink
  • Q Kiser

    Has there been any update on adding a feature to compensate for latency as the original post here asked about and that applications like Audacity have?  I did read the article from a couple years ago on latency (https://support.soundtrap.com/hc/en-us/articles/205508282-Why-am-I-experiencing-latency-), but couldn't find an update, so thought I'd check.

    0
    Comment actions Permalink
  • adelespinassesoundtrap

    It's insane that Soundtrap doesn't have this feature. Every DAW I've used for a real project has had it. There's no reason NOT to have it.

    There's no way to actually eliminate latency. Some users with some (expensive) hardware manage to get it down to a few milliseconds, but that would still be too much for some drummers. Also, the lower you make the latency, the more you risk dropouts, especially in complex projects with lots of tracks and effects.

    Why not add one simple feature that fixes the problem, rather than "working with Microsoft and Google" to try to reduce the problem in a way that doesn't actually fix it?

    This is the one reason I'm using Bandlab instead of Soundtrap. As far as I can tell, Soundtrap is more capable in other ways and more reliable, but I can't use it because of this one dumb thing.

    0
    Comment actions Permalink
  • Marvin D. Toll

    Latency issues have been very frustrating for our choir singers... they are always slightly behind the beat. I recently checked out the Latency Test feature in Bandlab and interestingly, it established over 200ms for my browser while over 50ms for my cell phone. Unfortunately, latency correction is a critical success factor for our use of Soundtrap.

    _Marvin

    0
    Comment actions Permalink
  • Marvin D. Toll

    hmmm... I've changed my opinion. Turns out that the DAWs that enable proactive latency determination, and "automagically" adjust are not the panacea one would hope for.  For example, I recently tested a DAW that registered my latency between 230 and 270ms depending on the day. That is, I'm finding that latency (and subsequent determination) is not always consistent.

    So I'm back to manual adjustment for latency... as the more viable/precise solution.

    _Marvin

    0
    Comment actions Permalink
  • adelespinassesoundtrap

    Yes, with some setups the latency doesn't seem to be consistent. I usually re-check the latency when I first open the program for a recording session. It should stay the same throughout the session, at least. Re-check if you have to restart the program.

    (The inconsistency is one problem where Microsoft and/or Google might need to be involved. I've seen it even with fancy hardware running ASIO drivers with a native Windows DAW. If that experience is universal under Windows and doesn't happen in MacOS, that by itself would be an excellent reason to get a Mac if you're doing multitrack recording. But I don't know if that's the case.)

    0
    Comment actions Permalink
  • Marvin D. Toll

    We have begun training our folks on how to perform manual alignment themselves... so they can listen to a more complete project. The following text was sent to our choir members:

    So what about the Latency issue?
    I now believe that track alignment is effectively handled manually... which I can take care of on my end. However, if you want to try aligning your own track, the following video (from 2:41 to 4:10 only) demonstrates the process usable within Soundtrap (after you turn off the "Snap to grid" button): 
     
     
    Note: It would be great if the Soundtrap team published a user video on this issue.
     
    _Marvin
    0
    Comment actions Permalink
  • jack schachner

    Marvin, my experience is very similar to yours. Latency not always the same ... and some times it increases slightly during a long track. (Windows, Firefox - there's a caution message about Firefox working but not supported.)

    I can't seem to time shift my track. Is that because I don't 'own' the studio? The steps in the video you link to don't seem to work for me.

    Quite right, Soundtrap Team should publish a video on this.

    Jack

     

    0
    Comment actions Permalink
  • Marvin D. Toll

    I can only think of two reasons you cannot "shift your track".

    1. The track starts all the way at the begging and there is no room to shift. (Delete or "Adjust Start" the very beginning of the track.)

    2. When aligning a track you always want to deselect the "Snap to grid" button.

    The following video (from 2:41 to 4:10 only) demonstrates the process usable within Soundtrap (after you turn off the "Snap to grid" button): 
     

     

    0
    Comment actions Permalink

Please sign in to leave a comment.