XITE 1 with Windows 10

[garyb]

the device not migrated message is nullified by the later one saying that the driver is installed.

obviously, m$ has made changes to the audio system, which affects wave drivers. the only thing i'm confused about is that there definitely have been reports of the wave drivers working...

[frokka]

the device not migrated message is nullified by the later one saying that the driver is installed.

I'm not sure you can draw that conclusion so easily.
The later ones could be generic and not dependant on the result of the first.
Or it could be that MS has forgotten to adapt the later code to a new conditional section that deals with the migration.
Or what about the matureness of error reporting in previous Windows versions?

[garyb]

it shouldn't matter to windows about migration. there's nothing to migrate. the hardware and driver work or they don't.

if Microsoft has done something strange that won't allow a driver to work, if the device is not "migrated", removing the device and the driver from the computer and reinstalling it from scratch should fix that. even better would be a fresh install.

i believe that "migration" refers to using the old settings and files. since the Scope driver is unsigned, i don't believe this is possible.

[mausmuso]

Hi There,
I have managed to get the 24 Bit wave source working on my windows 10 32 bit PCI Scope machine.
I followed method 2 in this video
https://www.youtube.com/watch?v=UpuHUNosvk0
Restarting the windows audio service and away it went.
Prior to that I was experiencing the same test failure described here by others.
Have not as yet upgraded my 64 Bit XITE-1 machine so not sure if it will work in that environment.
Hope this helps
maus

[frokka]

Wow, that worked for me too!

So weird that restarting those services has an outcome different to rebooting,
but apparently there is something slightly imperfect in the boot process.

Thank you Maus

[dawman]

I always install 2 x 24bit Source modules, then delete 1.
Somehow this allows to listen to YouTube tutorials and add FX to the voice.

Most guys sound like Caroline Kennedy, so for being tortured I require a slow Flange and broadcast quality doubling like a NASCAR Speedway commercial or something.
Some TC Fireworx mangling and Reverb help me feel like I have my own private instructor speaking from a podium too.

[garyb]

great!

[auntybiotic]

for what it's worth, man, everyone should know even if windows says its fine not to reboot, you always should or at least restart services..
had so many usb controller issues until i got into this 'trick'
windows hates boutique

EDIT - rereading, i missed the overall point - ignore my ridiculous comment

[garyb]

several other reports of success by restarting the audio services...

[guppy]

I always install 2 x 24bit Source modules, then delete 1.

I have to load 2 x 24 bit source modules and delete the 1st one too, on windows 8.
I'm happy to see that i'm not alone

[TOM.DJ]

I guess, when windows starts, the driver fails, as SCOPE is not yet loaded, and the WAV source is not working.

We could make a VB Script, which starts scope, and after scope is started, automatically restarts the service(s).
There are a lot of examples.

also another option is to use the SC command in a batch file, but there you cannot check if scope is running as easy as in VB Script.

i'll check what's possible.

Regards Tom.

ok fixed it! I'll make a tutorial how to implement the my script and upload it onto the forum tonight.

[TOM.DJ]

1. Download the attached zip file and extract it to your desktop.
2. Open an exporer and browse to: C:\windows\system32 (or your location for this system32 folder).
3. Copy the 2 scripts to your system 32 folder and leave the window open.
4. press windowskey+R to open the run dialog.
5. type: SHELL:STARTUP
6. Hold down ALT and drag the "RestartService.bat" from the system 32 folder to the new opened startup folder to create a shortcut.
7. On the shortcut, right click, and open the properties page.
8. navigate to the "Shortcut tab" and click on the Advanced button.
9. Select "RUN AS ADMINISTRATOR"
10. Press OK/Apply
11. Restart the PC.

Done. WAV source works directly when starting windows.

[garyb]

Tom, this is great work, thanks!!!!

[dawman]

I have to load 2 x 24 bit source modules and delete the 1st one too, on windows 8.
I'm happy to see that i'm not alone

I don't know a thing about tech savvy tricks but always twist knobs until things sound good and load modules and refuse to believe Scope won't find a way.

[auntybiotic]

Hello All,

May I ask, when you upgraded to Windows 10, did you perfom a clean install or did you do complete the upgrade via 'Windows Update' ?
If it was via 'Windows update', did you find the need to reinstall scope or did it all just 'work, with the exception of the reported wave driver issues / fix above?

Sorry for the dumbass question...

Mark

[mausmuso]

Hi There,
I just upgraded windows (from win 8.1 pro) and it all worked (except the wave module, which needed an audio service restart).
I have just installed (as a clean install) XITE SDK 64Bit which also seems to work ok as well on win 10.
maus

[auntybiotic]

Thanks for the feedback.

I decided to go for it & upgraded (w10, 64bit) without issues & no reinstall of drivers or 5.1 was required.
I had to restart the Audio Service but only had to do this once. Every reboot since it has worked.

This is highly unusual for a new ms os so i remain suspicious

Mark

[garyb]

win10 is NOT a new os. it's simply win7 service pack 3....

[auntybiotic]

win10 is NOT a new os. it's simply win7 service pack 3....

i think you know what i mean though, gary

whilst i agree it doesn't have any major 'boiler room' changes, you never quite know what to expect...