Acid 4.0e won't share audio port

TETI wrote on 8/19/2003, 4:06 PM
When trying to edit a file in SoundForge 6.0 from Acid 4.0e the file loads and the meters move but there is no audio. I'm using an RME digi 96/8 Pad audio card. I can open a file out of Vegas 4.0 into SForge with no problem. On the advice of SoFo tech support I've uninstalled and reinstalled Acid (several times). The problem goes away but then reappears. I also tried opening a file from Acid into Wavelab and the same thing occurs. I've tried the various audio preference options tp no avail. I've also contacted RME tech support but have found no solution. I don't think it's a card related issue because I can freely move between Vegas and SoundForge. Also, if I play an audio file in Vegas and switch back to Acid, Acid's timeline cursor won't move. Every other Acid function is OK however.

Can anybody help?

Thanks,
John

Comments

pwppch wrote on 8/20/2003, 12:29 AM
What drivers are you using in ACID? ASIO or Wave?

In the ACID general prefs, there is an option to

"Close all Audio and MIDI ports when Vegas is not the active application"

Is this optioned checked or unchecked?

What sounds like is happen is that the audio ports are getting lock for use by either ACID or Forge.

Do you have Realtime input monitoring enabled in ACID? If so, disable it as this locks the ports open in ACID and may prevent the RME card from being used by multiple apps.

When ACID's time line cusor wont move, is Vegas actively playing? Again, some drivers do not like being shared between multiple apps. If Vegas is using the driver for any reason, then ACID may not be able to.

Peter



TETI wrote on 8/20/2003, 9:16 AM
Peter,

I'm using ASIO drivers. I've tried the "close all audio ports . . ." preference both ways. Makes no difference.

Do you mean "enable realtime midi input monitoring"? I can't find an option for audio input monitoring.

Acid's time line cursor won't move if Vegas has played an audio filed and is stopped. I've never tried playing them simultaneously.

Thanks,
John
TETI wrote on 8/20/2003, 10:09 AM
Peter,

I disabled "realtime midi input monitoring" and I can now hear audio in Forge. That seems to be it.

Vegas still locked out Acid. I switched Acid to Microsoft Sound Mapper and it plays even with Vegas open. I don't understand much about how drivers work. Why did changing to MSM allow audio in Acid when the RME ASIO driver wouldn't?

Thanks for your help,
John
pwppch wrote on 8/20/2003, 10:13 AM
Yes, I meant "enable realtime midi input monitoing". Do you have it on or off?

I can't repro this with other hardware. I don't have the RME hardware you have.

What if you use Wave in ACID/Vegas vs ASIO? Does the problem persit?

To be completely clear:

- Start Vegas 4.0
- Load a file onto a track
- hit play. YOu hear it.
- Stop play.
- Open file on track in Forge.
- Hit play. You hear it.
- Tab back to Vegas. Hit play. You hear it.

Please, if this step by step is WRONG, please update so I have an exact repro. The simplest repro, the better. Please do this for ACID as well. Note all settings - Close Audio MIDI ports, Realtime monitoring in ACID, ASIO, wave, etc.

Peter


pwppch wrote on 8/20/2003, 10:18 AM
There you go. (Nevermind my last post)

Realtime MIDI input monitoring is for listening to softsynths. Enabling this opens the audio hardware.

Many device do not permit the sharing of audio hardware between apps. This is completely driver dependent. ASIO is by definition a non-shareable driver modle (though some vendors have worked out a mechanism to accomplish this.)

Wave drivers can be multi-client. WDM based drivers are by defintion multiclient.

It sounds like the RME ASIO drivers are just typical ASIO drivers : that is, non shareable.

Peter

TETI wrote on 8/20/2003, 11:48 AM
Peter,

Thanks for the explanation about the drivers.

Having spoken to SoFo tech support several times and the RME tech (who was familiar with SoFo apps) you were the only one who thought of the "enable Realtime monitoring" function. Maybe they just assumed I was smart enough to know about that.

It was driving me a bit nuts because it was intermittent. Now I realize it was happening when I had a Softsynth inserted and monitoring the midi input.

Much appreciated.

John