Hi,
I've been running SCS 11.6.2.1 under WIndows 7 with TASCAM US122Mk2 interface using the ASIO drivers with no problems for some time, and now all of a sudden I'm getting a 1.5second delay between triggering a cue in SCS and hearing the result on the output of the interface. The ASIO driver is set for low latency, and nothing has changed other than window and anti-virus updates. If I switch to the DirectSound drivers, all is OK, so it's something to to with ASIO, but I can't work out what;s changed.
I'd welcome some ideas on how to trouble shoot this.
Thanks,
Now getting 1.5 Sec latency with TASCAM US122Mk2 ASIO driver
Re: Now getting 1.5 Sec latency with TASCAM US122Mk2 ASIO dr
I would try it again after a machine restart without the ANTIVIRUS software running, even an update can cause an issue, please report back the result of that attempt, good bad or otherwise and let us know what Antivirus you have.
Re: Now getting 1.5 Sec latency with TASCAM US122Mk2 ASIO dr
OK, will do. AV is Avast Free.
Re: Now getting 1.5 Sec latency with TASCAM US122Mk2 ASIO dr
OK, so i turned off all the Avast components, rebooted and all was OK. So I then re-enabled each of the four main shields one at a time, rebooting after each change,and, lo and behold....................still all OK!
Puzzling..... so I had a think and had an idea....the first time I saw this problem, I remembered that I had started SCS immediately I logged on, before Avast was up and running (i.e. before the Avast icon appeared in the tray). On the subsequent tests, I'd allowed the machine to reboot whilst I was doing other things, so Avast was up and running BEFORE I started SCS. So I tried rebooting and starting SCS before Avast had started up and the problem returned.
This seems to be reliably reproducible and I'd be interested to know what the failure mechanism is!
Thanks,
Dave
Puzzling..... so I had a think and had an idea....the first time I saw this problem, I remembered that I had started SCS immediately I logged on, before Avast was up and running (i.e. before the Avast icon appeared in the tray). On the subsequent tests, I'd allowed the machine to reboot whilst I was doing other things, so Avast was up and running BEFORE I started SCS. So I tried rebooting and starting SCS before Avast had started up and the problem returned.
This seems to be reliably reproducible and I'd be interested to know what the failure mechanism is!
Thanks,
Dave