Acoustica User Forums

Hi ,

all of a sudden I cannot select my firewire interface any longer. I have re-installed the drivers, I use Mx7 pro and W7 pro.
I have recently updated to the latest Version of Mx7, but cannot recall if I have tried to open the interface after that.
As if mixcraft were not seeing the ASIO drivers, but MX detects a change in available devices OK.

EDIT: just noticed that it has to do with admin privileges. What I changed was to replace the hdd where the programs were located with a new drive (1:1 copy). Maybe to do with ownership.

Please advise, thanks.

-helmut

Edit: just realize, it was an entirely different drive I replaced. Nothing changed on the program drive

Try to run MC as an admin once, and see what happens.

However, it can lead to many unforeseen things to copy programs to another disk and run them from there (assigning the same drive letter is not always enough, and some software may run flawless, other software not at all). Some manufacturers tackle this issue by making a roaming version of their software.

So, at least do a reinstall of MC and see if that helps.

Yeah, it runs as admin. I try a re-install.

thanks,

-helmut

EDIT: Nope. Re-install changes nothing.

Pity. I'm not familiar with Firewire, so forgive me if it doesn't make sense:

-does Windows see the interface (device manager)?
-does it still work with stuff like mediaplayers?
-does resetting it help? (from within the Mixcraft program folder: "Reset Audio To Factory Defaults")

You could also try to take ownership of the stuff on your new disk and see if it changes it.

sometimes just unplugging & plugging the interface back in works. (make sure Mixcraft is not open @ the time.)
been there,done that many times....

Juno wrote:-does Windows see the interface (device manager)?
-does it still work with stuff like mediaplayers?
-does resetting it help? (from within the Mixcraft program folder: "Reset Audio To Factory Defaults")

You could also try to take ownership of the stuff on your new disk and see if it changes it.

Windows sees the device. MX too - it recognoizes a change in available devices.
Never used it with other players.
Resetting cannot be activated - I cannot select the Asio button.
Ownership changes nothing.

At which point does Mixcraft try to load the ASIO drivers? Looking at the log text did not make me wise. As different to the admin´s log text file, there is no reference to ASIO whatsoever.

I uninstalled mixcraft and the focusrite programs and re-installed everything again - at no avail.
I am at the end of my wisdom.
Everything works as administrator.

-hg

I'm sorry it's still not working. However:

aquataur wrote:Everything works as administrator.

Does that mean that MC sees and uses your interface when you run MC as an admin?

Exactly so. As any other user, I cannot select the option "ASIO" in the audio devices tab.
I do not really know what caused the problem, because this used to work until two days ago.

It must have to do with rights and / or ownership, but I can´t see where.
The Mixcraft guys any idea where to look?

Support recommended a few things that were not leading to the desired goal.

It came to mind to install MX6, since they can coexist peacefully and lo and behold, I can activate ASIO.
But not in MX7 Pro.

-helmut

So, it's very likely not the audio interface.

Things you could try if you haven't already:

-"reset audio to factory defaults" link: try it in admin mode
-uninstall MC, reboot, reinstall using admin mode

all done, all done.

Support is at it. I sent them the log files.

-helmut

noone suggested restoring your computer to a restore point right before you lost it (asio)?

I´ve tried all that. I suppose this is a case for waiting... Some problems solve themselves.
I can run MX in administrator mode, which is only a slight effort.

Before we all waste more time with that ...
Thanks to all the help.

-helmut

Hi,

You can easily set Mixcraft to always run in admin mode via its icon properties on the compatibility tab.

Other than that, did you try uninstalling the Saffire's audio drivers and then installing them again?

Greg