rme asio driver

Kyoto wrote on 1/8/2008, 4:14 AM
vegas 8 won't remember the 'asio fireface' driver setting in preferences / audio device.

even though i click on 'apply' - when i restart the program, it has reverted back to the 'windows' driver. (and sometimes vegas crashes when i try to change it back to asio fireface - sometimes it doesn't).

using xp on a new audio-only computer with the latest versions of vegas, and the fireface 800 with the latest rme driver & firmware update.

any ideas? thanks

Comments

Kennymusicman wrote on 1/8/2008, 5:33 AM
Narrow it down a bit - do you get this problem with other apps, or just Vegas?
Kyoto wrote on 1/8/2008, 7:59 AM
Just Vegas 8 (and also Vegas 5 which is also installed).

I do not have this problem with Acid 6 however - in preferences / audio device Acid 6 is set to 'asio fireface' , and it remembers the setting. It just seems to be an issue with Vegas - Vegas does not for some reason like to be set the 'asio fireface' . Half the time it crashes upon pressing 'apply', or, the other half of the time when it does accept 'asio fireface' it still reverts back to the windows driver upon a re-start of Vegas!

Thanks for your help!

pwppch wrote on 1/8/2008, 7:28 PM
Q: Do you use the UAD plugins?

Something for you to try.

1. Start Vegas.
2. If Vegas loads your previous project, close the project, and exit Vegas. Launch Task Manager and make sure that Vegas80.exe is NOT listed. If it is, end this process and restart Vegas. Repeat this step until Vegas shuts down cleanly.

3. Restart Vegas.
4. Change the Audio Device Preferences to the RME ASIO driver.
5. Click OK
6. Exit Vegas.
7. Start Vegas.

Is the RME restored as your default device?

We have seen situations where if Vegas does not shut down properly the preferences settings you make will not be saved and later restored upon a restart.

If you continue to have problems, start Vegas while holding down the shift key. This will reset Vegas' internal prefs. Exist Vegas, and restart. Now change your default audio device to the RME ASIO drivers. Exit Vegas and restart Vegas.

Peter



TGS wrote on 1/9/2008, 12:00 AM
I don't know if this relates at all, but maybe it will help.
Since I don't know what RME is, I can't imagine what it is.
But I received this advice when I bought a FireWire mixer and I kept loosing the ASIO drivers.
It doesn't always work, but I don't use it often and that may be why. It seemed to work when I was using it often.
You have to turn on the external hardware before turning on the computer. That's all I had to do, was turn on my FireWire Mixer first, then if I started the computer, the ASIO drivers were there. (I had to load them in 1st though) But they stayed until I didn't use the mixer for a few weeks.
I don't know the logic behind it, but it's the only thing that worked for my situation.
Luckily, putting the drivers in again is easy for me.
Decided to google RME before I finished. WOW 56 channels $1500. NICE
Well, I hope I helped you. By the way, it was farss who told me about that workaround.
Kyoto wrote on 1/9/2008, 12:16 PM
That worked. Vegas was loading previous project and that's why it wouldn't accept the driver change. Thanks SONY.

Now the other issue I am having in V8 is this - it crashes often whenever I am either adding / removing or adjusting a plug in. In other words when I go to the track plugins and remove the sony eq or compressor (or add them again) it crashes. I get the "error occured during current operation" notice. Within the stuff that comes up it says 'access violation'. Module msvcp71 is blamed.

In other crashes, I've seen it blame a variety of different modules:
msvcp71
or
ws66.temp
or
vegas80k.dll

Sometimes when it crashes I am left with a buzzing/vibrating noise coming through my speakers even after Vegas shuts down. It is the same sound that I occasionally hear for a just a second sometimes during playback. (That is a playback when everything else is working OK).

Any ideas?

Thanks,

RL