Windows 10 version 1607 problem:

An area for people to discuss Scope related problems, issues, etc.
Post Reply
marcianus
Posts: 26
Joined: Sat Mar 27, 2004 4:00 pm

Windows 10 version 1607 problem:

Post by marcianus » Tue Dec 06, 2016 10:04 am

I have updated windows 10 to a new version, 1607 from 1511:

Windows 10 Professional x64 spanish.

There is no audio:

"Los servicios de audio no responden"

Restarting AUDIO SERVICE (Servicio de Audio) and WINDOWS AUDIO ENDPOINT BUILDER (Compilador de Extremo de Audio de Windows) seems to be useless at this time.

Someone else with the same problem?



Everything works correctly on the same machine with windows 7

User avatar
garyb
Posts: 21192
Joined: Sun Apr 15, 2001 4:00 pm
Location: ghetto by the sea

Re: Windows 10 version 1607 problem:

Post by garyb » Tue Dec 06, 2016 10:59 am

reinstall the driver.
you must first disable driver signature enforcement, just like the first time that you installed Scope.

this is normal. the Scope driver is unsigned. since Microsoft no longer considers Windows to be a product, but is now a service, they think that they can administer yourt computer as they see fit. during major updates, unsigned drivers are removed.

pastor

Re: Windows 10 version 1607 problem:

Post by pastor » Tue Dec 06, 2016 11:50 am

minor diversion but i found someone made an article with video about Scope on Win 10.
http://www.noizefield.com/tutorials/son ... windows-10

User avatar
garyb
Posts: 21192
Joined: Sun Apr 15, 2001 4:00 pm
Location: ghetto by the sea

Re: Windows 10 version 1607 problem:

Post by garyb » Tue Dec 06, 2016 12:29 pm

yes, but that method is actually the harder method(it works!). :lol:

i think option 2 here is easier:
http://www.top-password.com/blog/how-to ... ws-10-8-7/

marcianus
Posts: 26
Joined: Sat Mar 27, 2004 4:00 pm

Re: Windows 10 version 1607 problem:

Post by marcianus » Tue Dec 06, 2016 12:49 pm

pastor wrote:minor diversion but i found someone made an article with video about Scope on Win 10.
http://www.noizefield.com/tutorials/son ... windows-10
garyb wrote:yes, but that method is actually the harder method(it works!). :lol:

i think option 2 here is easier:
http://www.top-password.com/blog/how-to ... ws-10-8-7/

Thanks to all. I try again.

The problem is strange. I have two boards: a Pulsar II and a Scope. Only the Scope "crashes". Windows 10 does not allow me to select it as default audio device. All DSPs, IO modules, etc, etc are present and selectable in the Scope environment.

User avatar
garyb
Posts: 21192
Joined: Sun Apr 15, 2001 4:00 pm
Location: ghetto by the sea

Re: Windows 10 version 1607 problem:

Post by garyb » Tue Dec 06, 2016 1:14 pm

both in the same computer?

if so, they're not really individually selectable in Windows...

marcianus
Posts: 26
Joined: Sat Mar 27, 2004 4:00 pm

Re: Windows 10 version 1607 problem:

Post by marcianus » Fri Dec 09, 2016 6:46 am

garyb wrote:both in the same computer?

if so, they're not really individually selectable in Windows...
Yes. In the same computer.

I can select individually which board is the "default audio device" in the same computer with Windows Seven.
The problem is only about the Scope board in W10.

User avatar
garyb
Posts: 21192
Joined: Sun Apr 15, 2001 4:00 pm
Location: ghetto by the sea

Re: Windows 10 version 1607 problem:

Post by garyb » Fri Dec 09, 2016 11:55 am

nope. windows cannot see individual cards. if both cards are in the same computer connected via an s/tdm cable, windows still doesn't see the cards. windows sees the drivers. by default, there are two sets of wave drivers available and both are in the playback dialog, but you may not have two sets of wave drivers in your routing window. if you have two sets in the routing window, then both sets will work in the playback dialog.

there could be less or more wave drivers registered in windows, the number of Scope wave drivers available in Windows can be adjusted in the "properties" dialog of the device in the device manager on the "settings" tab.

Post Reply