2018/09/14 15:27:39
pretttyugly718
Hey All, 
 
My latency tends to drift. At first, when I load a synth, the latency feels spot on. Meaning that there is no audible delay. I never had this problem with my last interface (MOTU 828x.....terrible product/customer support). Now, with my current interface (Tascam Celesonic 20x20), latency is introduced over time (or if i switch patches or add samples to the synth). When I notice this, I can turn the audio engine off and then back on again and only then does the problem (temporarily) go away. Anyone else dealing with this? I wonder if it's Interface Specific because none of my previous 3 interfaces on weaker PC's did this. Any thought? Thanks.
 
Lee
2018/09/14 15:58:29
JonD
Are you sure your USB3 ports are performing as USB3 to match your interface?  IIRC, Win 7 ended its development without native support for USB3 (though there is a workaround/fix). 
2018/09/15 12:15:28
bvideo
Theoretically possible it's the interface driver. An early version of the driver for mine had the weird behavior of having a different latency every time it was stopped/started, seemingly random.
2018/09/16 16:10:16
henkejs
If you're talking about MIDI latency, setting IgnoreMidiInTimeStamps=1 in the TTSSEQ.INI file might help your problem. It worked for a previous interface I owned.
 
IgnoreMidiInTimeStamps= Boolean 0 (disable)
 
This line determines whether or not SONAR ignores any
MIDI time stamping that a MIDI driver does. If you’re
experiencing increasing delays between the time you
play a MIDI note on a controller and the time you hear
SONAR echo it, setting this line to 1 may help. Also, if
you find that SONAR is recording MIDI data at a different
time from when the data was played, setting this line to 1
may help. If the MIDI driver is using a different clock from
SONAR, the time discrepancy increases the longer that
the MIDI driver is open, so you need to tell SONAR to
ignore the timestamp that the MIDI driver adds to the
data (set the value to 1).

 
Post edited for clarity.
2018/09/17 22:14:00
pretttyugly718
@JonD - Yea I have it rigged to work at USB3 speeds. I am, however,  interested in your workaround/fix. 
 
@bvideo - I agree. It's Been over a year since Tascam's last software update for device I am leaning towards the driver as the main culprit
 
@henejs -I've researched that and did it but did not notice a change. Thanks.
 
Thanks Walkers,
 
Lee
2018/09/20 04:22:17
JonD
pretttyugly718
@JonD - Yea I have it rigged to work at USB3 speeds. I am, however,  interested in your workaround/fix.



It's not "my" fix, in that I've never had to deal with it personally - only read about it.  Basically, because Win 7 didn't natively support USB 3, you have to incorporate the USB 3 driver another way.  The best solution IMO is to upgrade to Win 8.1 which does install the driver (but, of course, many users may not want to go that far). 
 
If you've already managed to install the USB 3 driver, then you don't have to worry about it.  I would still verify in Device Manager that you actually have the USB 3 host controller working.
© 2024 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account