PlanetZ forums - scopeusers.com

I also have a Teensy 3.6 (and a 2++): What would be the best alternative to the official audio shield for Teensy 3.6?

Have you already tried to remove the card, reseat the io board and put it back in place on the pc?
It must have the io plate recognized and working, otherwise there is a good chance that there is a hardware fault.

astroman wrote: ↑Fri Aug 17, 2018 4:59 pm you may consider to split the setup into multiple mixers if you're controlling it from another surface anyway.

Yes Astroman, i am considering that too!
Thank you.

I don't have a Xite-1. Sorry, can't answer that part of the doubt. But i would say that that section is refering to the ADAT or S/PDIF for ADAT B port.

Thats for you to choose if you want to use S/PDIF or ADAT on THAT port.
For instance I found out that my Korg M3 wants it as S/PDIF, not ADAT.

Hi guys. I am in the process of starting a new musical project that will require me to have individual controll on the audio monitoring for each of the 6 band members. I already made a midi controller in touchosc for that (great tool indeed) as a test and if this is doable i will put more tracks to ...

I was wrong, it was Ableton, and needed to be in Admin and Win 8 compatibility Mode. So, not XP.
Sorry for having misleaded you.

garyb wrote: ↑Wed Aug 08, 2018 8:27 am i don't need compatibility mode for Cubase 5 and win10 here...neither for win7...

That is the point. IIRC the problem is exactly that it WAS on, not letting things work right.
Pitty i don't remember what was the thread and where, but i think it was here in the Z.

Wasn't there someone mentioning some issues worked with Steinberg and then he found out it was something with compatibility mode or so?

ok, but i think his problem is that he isn't using the v7 key. he's using his keyfile, which doesn't have the new v7 key. whether driver signing is off or on, the problem isn't related. :) senior moments and a lifetime of brain abuse....or that might be me... I would be surprised if a long time use...

That is what he is going to with the command line command i gave him Gary: put driver signing on again.

You should save the Scope folder uninstall, reboot and re-install (you know the rest )

Hehehe.
Yes, it works in W10.

Do you mean, how to remove the driver signing enforcement thing?


command prompt as admin:
bcdedit /set testsigning off

restart

I usually put the file itself in the folder. Don't remember if i have used that import function.

The key file should be in the bin folder and Scope run as admin.
I have V7 PCI with Windows 10 and have no issues on that regard.

The badge is the "Administrator Mode" i was refering to.
It should work if you put a shortcut into the startup folder.

I use a batch file for that: @echo off echo "Starting SCOPE" start "" "H:\Program Files\SCOPE PCI\App\Bin\Scope.exe" Change the "H:" for "C:" if you have Scope intalled in the C: drive. Also, make a shortcut for that batch file and it will be that sh...

What is the issue you are dealing with? No sound?

Yep still Aluminum 16v 47uF caps. You must run in a very hot and/or dry environment, to have so many caps dry out on you at the same time. I don't think the environment is a problem. I think it is a matter of board's age. I'm doing it more as a precaution, as the real problems i notice are on the D...