PlanetZ forums - scopeusers.com

Hi I installed scope 7 this morning and all is good, apart from this annoying error message when I launch scope

''timeout waiting for acknowledge from dsp 6 (communication not stalled)

this didn't happen with 5.1 , if I click ok then scope loads as normal,

if I add a new device or open the settings, I get the error 'your computer is too slow.aborted'
and if I click ok the synth loads as normal

also got a blue screen of death when testing solaris sample oscillators, so I assume no fix yet .

any idea how I fix this?

The problem was rectified by reinstalling scope 7

I solved it by installing Scope 7 over the old Scope 5.1. Before that I was installing Scope 7 on a fresh partition (with no older Scope) and wasnt able to get rid of that error even after multiple install / reboots.

Is your install Scope 7 afresh, or is it an update to a previous Scope 5.1 ?

over 5.1

Suspected as much. Have you done a Scope 7 install fresh & got the error ?

What I'm trying to do is establish a pattern for a bug report - eg whether XITE-1D Scope 7 fresh install gets a DSP 6 error across more than 1 user's machine.

Hi Dante,
I spoke too soon, the Error came back on booting today, So I tried a clean install and got the same error.
Error happens on both clean install and install over 5.1
Windows 7 x64 SP1
32 gb ram
Xite1D
Scope 7 x64

Damn. Mine only comes up on clean install, not over-old install. But I'm on Win8 and Win10 so slightly different from your system.

Whatever, it does seem XITE-1D specific whether clean install or not.

You could try the old XITE-1D hotfix (haven't tried this so don't know if it works) http://scope.zone/index.php?id=1978&lg= ... scope_xite

Definitely not xite 1D specific. Having the same problem with my xite 1 after installing Scope 7 over the top of a Scope 5.1 install on Windows 8 32bit. It worked straight after the first install, I then installed the SDK, which also worked and then went back to Scope and getting the error messages. Will keep investigating.

Great thanks Will - I wont bother mucking with the XITE-1D hotfix then

Problem persisted after removing driver (and then again, as the 5.1 driver took over). Did a few reboots, which didn't help. Eventually power cycled the Xite-1 and at last it's working again. Makes me a bit nervous, I have to say. Will report back if it recurs.

don't install the driver twice. both v7 and sdk7 install the driver...

Will, on the XITE-1D the message refers to DSP #6. Is that the same on the XITE-1 ?

I got the same with my xite1 last month. Try to investigate on the power supply side.

dante wrote: ↑Wed Dec 13, 2017 4:21 pm Will, on the XITE-1D the message refers to DSP #6. Is that the same on the XITE-1 ?

My error message was exactly the same as yours

guppy wrote: ↑Tue Dec 19, 2017 4:33 am I got the same with my xite1 last month. Try to investigate on the power supply side.

I had a different issue with the Xite-1 not being seen on a 5.1 install (Win 7 64bit) the other day, which was also resolved by power cycling the Xite-1 (+ reboot). I wonder whether we're just seeing a different symptom for the same issue on Scope 7.

w_ellis wrote: ↑Tue Dec 19, 2017 4:46 am

guppy wrote: ↑Tue Dec 19, 2017 4:33 am I got the same with my xite1 last month. Try to investigate on the power supply side.

I had a different issue with the Xite-1 not being seen on a 5.1 install (Win 7 64bit) the other day, which was also resolved by power cycling the Xite-1 (+ reboot). I wonder whether we're just seeing a different symptom for the same issue on Scope 7.

I don't think so, My xite 1D worked fine with 5.1, the same day I installed 7.0 and got the error message,
so I uninstalled 7.0 an put 5.1 back...and no error message, i reinstalled 7.0 and error returns

I also get that error message on the XITE-1, but for DSP 7.

I have other issues with the unit since Scope 5, which appear to be hardware related, so I can't really expect normal operation. I thought it also had to do with the hardware. But this message only appeared after installing Scope 7, and, if others seem to have it as well, it could be related to the software.