Where are my dedicated ASIO SCOPE drivers??

Nestor · Post by **Nestor** » Fri Oct 21, 2005 7:14 pm

Win XP
SFP 4
SX 3
Pulsar I

I’ve done a software upgrade, particularly upgraded all MOBO drivers, etc. To do this I have installed everything anew because it is always better when doing a general upgrade.

What is my problem? I can’t find the dedicated ASIO driver from Pulsar, called “ASIO Scope”.

I have done this, of course, as usual:

file://localhost/H:/Desde%20Disco%20O/PROGRAMAS%20ÚLTIMOS/f735c2304d8ed9eec1256c7e003b17fd.htm

The only thing I get are the multimedia ASIO drivers, with 786 milliseconds. What is going on, why can’t I find the dedicated ASIO Scope? Am I missing something I don’t remember?

Please, would you like to give me a hand with this?

Thank you people

Post by **garyb** » Fri Oct 21, 2005 11:16 pm

you have asio modules in the project and nothing?
reinstall the driver. if nessessary, reinstall sx.

Nestor · Post by **Nestor** » Sat Oct 22, 2005 12:50 am

Exactly, and nothing... Never seen that before.

I've already installed SX, but not the drivers. I'll install the drivers and see what's going on. Cheers

Nestor · Post by **Nestor** » Sun Oct 23, 2005 1:39 pm

Bizarre, still Multimedia drivers and Direct X drivers, but not SCOPE Asio… I can’t understand what’s going on. I have done it many times in the same system, and there is nothing obvious to my eyes I can think off.

Yes, the drivers are in the device manager, and working fine. In fact, I do have audio and can for instance work with audio files.

I have reinstalled SX and still the same drivers… What could it be, where is the trick?

djmicron · Post by **djmicron** » Sun Oct 23, 2005 2:08 pm

i don't know if this could work for your problem, but after upgrading my system i've encountered a similar problem, but just when opening existing projects with asio drivers.
The problem was solved by deleting the asio drivers from the routing window and reloading from the devices menu.
The operation must be done with the host sequencer closed.
In the case of nothing solved, try to open another application that use asio drivers, just to understand if the problem is scope related or cubase related.
Hope this could help

[ This Message was edited by: djmicron on 2005-10-23 15:11 ]

LHong · Post by **LHong** » Sun Oct 23, 2005 2:35 pm

Hi,
Like djmicron said,
The problems seems be around the ASIO(2) Source and Dest from Scope routing Windows.

When you open the Cubase, it will check the SCOPE ASIO drivers available. In your case, it only can detects the Wave Source and/or the Wave Dest from the "Scope routing Windows", but not any ASIO at all!
So, try to reload the ASIO(2) would helps!
Then restart the Cubase.

Good luck,
LongStudio

Nestor · Post by **Nestor** » Mon Oct 24, 2005 5:49 pm

Hello people, thank you very much for your answers!

I have tryed all this before, but nothing... It's quite strange, never had this before. Could it be a problem with some intel drivers? Perhaps the new DirectX 9.0c? No idea... I am quite lost honestly...

LHong · Post by **LHong** » Mon Oct 24, 2005 8:18 pm

Sorry to hear that!
The problem seems be around the Scope Driver.

How about this: try to re-install the SCope Windows Driver Manually.

For example: Close all Applications, from Hardware Manager -> Creamware Scope (RightClick), choose Update Driver...Be sure to select Specific Location (Advanced). Follows on screen instruction to install the 4.0 Driver...
Then Reboot the PC.

Good luck,
LongStudio

Nestor · Post by **Nestor** » Wed Oct 26, 2005 9:58 pm

A driver incompatibility was killing me. It was all about the latest Fast Track 376 Promise Drivers, which collided with my 1005 BIOS for the ASUS P4PE. I upgraded my BIOS to 1007 and downgraded the Fast Track 376 to it’s CD bundled version that came with the motherboard and things started to look better.

The whole system after the upgrade became mad, it would ask you at any time for drivers that were already installed, it would restart spontaneously without prompt, it would crash when reading CDs or DVDs, it would stop searching for IDE drivers for about 3 minutes in every boot… My eyes were quite big I can tell… I thought the motherboard was gone bad, or perhaps the HD. It was not easy to guess what the hell was doing this mess…

Not always new drivers work well with each other. This is what I dislike from the PC world: the endless possibilities when you have a problem, with tens or even hundreds of possible reasons and so, thousands of possible solutions! Uf!

Thank you for your answers

Nestor · Post by **Nestor** » Wed Oct 26, 2005 10:00 pm

How did I came to decide this solution? Errrmmm, good question...

I don't have a clue... but I'm very satisfied I did!

djmicron · Post by **djmicron** » Thu Oct 27, 2005 2:35 am

i don't know your motherboard model, but with modern pc, it's better to install xp in acpi mode and it is better for performance and driver compatibility.

Nestor · Post by **Nestor** » Thu Oct 27, 2005 7:10 pm

That's right, I do use ACPI anyway. My motherboard is an Asus P4PE. Cheers

ChampionSound · Post by **ChampionSound** » Thu Dec 08, 2005 2:09 pm

MAYDAY!! MAYDAY!!

I have a major problem!
I'm continueing with this thread, because I have a sort of similar problem:

ASUS P4T-E
512 MB RIMM
Win XP, SP1

I installed Scope 4.5 "successfully". The scope environment seems stable, I can load all devices and so on.
The only thing is, that I can't run the same SX 2.2 anymore along with Scope! With scope 4.0 everything was working fine.
Now every time when I open cubase after I loaded my project (including ASIO drivers in the project) a window appears:

"Samplerate could not be set. This may be due to sampleclock being set to external sync"

After that, cubase continues loading up.
Now when I go to Devices -> Device Setup -> VST Multitrack
In the ASIO driver box, I only have the choice between "ASIO DirectX Full Duplex Driver" and "ASIO Multimedia Driver"
I'm almost sure that there was always a third option: ASIO SCOPE Driver, the one which I need of course.

I reinstalled cubase, without any success

And I already checked the settings in the scope environment and these are still OK,
44.1K samplerate and scope is master.

Obviously Cubase can't find the scope driver anymore. Is the ASIO scope driver missing in SFP 4.5?? Is there a way I can fix this?

BTW, the scope card itself is recognised by Windows XP (no questionmarks in the hardware devices list)

Can anybody please help me out? How can I make Cubase see the ASIO Scope Driver again?

thanks a lot!!

cheers, Darce

astroman · Post by **astroman** » Thu Dec 08, 2005 2:29 pm

Imho you ran into this trap

On 2004-11-20 13:39, garyb wrote:
it's a windows thing......
http://www.rme-audio.de/english/faq/10entrye.htm

good luck, Tom

ChampionSound · Post by **ChampionSound** » Thu Dec 08, 2005 2:45 pm

Hi Tom, I quickly read this link, but I don't think I have the same problems as described on this page. I only updated from SFP 4.0 to 4.5. I changed nothing else!
Well if I can't solve this problem within the next two days, I'll try to install SFP 4.0 again and see what happens.
These problems always happen if I just get great ideas for new songs

BTW, in which directory should the Asio Scope Driver be installed on the harddrive? Maybe I can put the file manually where it should be?

Thanks! Darce

[ This Message was edited by: ChampionSound on 2005-12-08 14:49 ]

astroman · Post by **astroman** » Thu Dec 08, 2005 3:52 pm

I usually try to avoid these things as my 'developement roots' are MacOS based and any Windows internals are nothing but scum for me.
It doesn't matter how many million installations exist - the concept s*cks by default, it's built to s*ck...

This attitude doesn't exactly qualify me as a Windows expert, yet I'm pretty sure that the registry 'overflow' is exactly the source of your problem.

YOU didn't change anything, of course not.
But the installer did what it ever did, it added something to the registry.
It possibly adds a new driver entry whenever you run it - or sometimes and simetimes not.

I don't have Cubase myself but I've read several times that it requires the multimedia drivers for whatever reason to do it's setup.

If the registry entry of such drivers 'overflows' then you'll end pretty much where you are.

cheers, Tom

[ This Message was edited by: astroman on 2005-12-08 15:53 ]

Post by **hubird** » Thu Dec 08, 2005 4:17 pm

I even don't know what the registry is or is good for

you don't have that on mac

might be said now and then, not?

(had a nice smilie in mind, but http://www.mysmilies.com/?cat=sprites&page=90 just shows the red-cross-in-square icons since a long time

Can't be the registry, at least

)

Nestor · Post by **Nestor** » Thu Dec 08, 2005 5:50 pm

I’m sorry to here that, I know how frustrating it can be.

But, before you get into more depth, have you done the basic move? If you didn’t, please do the following:

1- go to your “C” drive
2- go to “Scope” folder
3- go to “App” folder
4- go to “IOEnabler”
5- open “IO Enabler.exe”
6- tick “Enable ASIO Drivers”
7- go out with “Save”

You are probably done.

My problem was driver related, but not checking “Enable ASIO Deivers” in this box may cause similar problems, not being able to see the dedicated ASIO drivers.

Tell us how it went; good luck!

Post by **garyb** » Thu Dec 08, 2005 8:08 pm

hmmm, i've done 3 succesful 4.5 updates in 2 days and not had a problem(i know someone who had a different problem, but it's unrelated to this....).

there's no reason for the asioscope driver to be gone, maybe a driver reinstall, restart and reinstall of cubase, restart and rechoosing asioscope will work. you might try one step at a time....i hate to say it, but when things get really screwed up, it's better to start from scratch so you can eliminate sources of trouble.....

ChampionSound · Post by **ChampionSound** » Thu Dec 08, 2005 11:52 pm

Nestor, Astroman, Hubird and Gary, I LOVE YOU, GUYS!!

Nestor, you saved my life

The IO Enabler did the trick.
I hadn't set it up yet, because I thought it was only meant for XTC mode, because of it's name.
As far as I can remember, Scope 4.0 didn't have this extra program and activated the ASIO drivers automaticly, but appearently I had to do it manually here.

Thanks again

PlanetZ forever!!!

cheers, Darce