Error opening Direct Sound device

mickelin

New member
I'm running a script calling Comskip and VideoRedo to cut commercials from mpg-files. It works well except every now and them VideoRedo gives the error message "Error opening Direct Sound audio device". I have tried the "Edit without audio" option, but it does not help. Any ideas?
 

Danr

Administrator
Staff member
no idea. Any messages in the log file? Does it only happen in batch?
 

Danr

Administrator
Staff member
This isn't something we are looking into. From what I can tell it's unique to your system. Are you by chance running over RDP (remote desktop)?
 

stevec

New member
I don't know, whether it helps or not, but every so often, I end up having that message when running in batch mode (from a PowerShell script). I'm using
TVSuite 4 H.264 thou.

And, yes, I'm using RDP on a 64 bit Windows 7.

EDIT: I managed to find some logs, but nothing really useful.
2012-04-30 21:51:26 Startup - Number of PTS checks: 8
2012-04-30 21:51:27 Using display driver: Silent Mode
2012-04-30 21:51:27 DirectSound open error.
2012-04-30 21:51:27 Unable to play video: Error opening DirectSound audio device.
 
Last edited:

Danr

Administrator
Staff member
There could be a number of reasons why the DirectSound device won't open especially under RDP. You might want to play with either the direct sound device on the T>O>Devices page, and/or the RDP setting of whether to direct audio from the remote computer to the RDP client.

However, if you set audio none T>O>Devices page, then it should never even attempt to open the DirectSound device. If it does could you be pointing to a different COM object in batch than the interactive one? If you run our batch manager, it should check that the COM version is the same as the interactive one.

Finally, the next beta build will also automatically disable audio if running silently. This too will prevent the directsound device form being opened as well.


1) If you specify no audio while editing, it won't attempt to open the direct sound device at all.
 

Danr

Administrator
Staff member
There could be a number of reasons why the DirectSound device won't open especially under RDP. You might want to play with either the direct sound device on the T>O>Devices page, and/or the RDP setting of whether to direct audio from the remote computer to the RDP client.

However, if you set audio none T>O>Devices page, then it should never even attempt to open the DirectSound device. If it does could you be pointing to a different COM object in batch than the interactive one? If you run our batch manager, it should check that the COM version is the same as the interactive one.

Finally, the next beta build will also automatically disable audio if running silently. This too will prevent the directsound device form being opened as well.


1) If you specify no audio while editing, it won't attempt to open the direct sound device at all.
 

TheCurator

New member
Parital-Solution for Direct Sound Issue when RDP

For both the DirectSound issue and Video Error messages simply disable the video driver in the Playback Device settings.

While not 100% effective it seems to avoid most of the errors I get on a regular basis if I forget to disable the setting.

How do I use VideoRedo normally you may ask.

I am using VideoReDo to re-encode and cut commercials from hundreds of shows I'm pulling off of my TiVo. This is time consuming so I RDP from my office regularly and initiate BatchCMD files remotely.

I get the error when either re-encoding from .mpg to .mp4, and I also get the errors when I am using the Ad-Detective from the batch file method.

I have found that if I do not disable the video driver I get the 'Error Opening Audio Device' or another 'Can't Display Video' error message even though there is no visible opening of VideoReDo on the desktop.

The problem does not seem to happen when I am active in the RDP session, meaning, I am actively logged in, and doing something else that prevents the session from dropping.

If I allow the connection to time out and disconnect when I log back onto the machine I am greeted with either an audio or video error message and my batch file is stalled awaiting me to acknowledge this error.

I hope I have been clear about when the error occurs. If there is any ambiguity to my statement about when the error occurs please let me know.
 

TheCurator

New member
Just a note .. I avoid direct sound errors by disabling the video driver for playback devices. I suspect it has to do with the fact that there is an HDMI audio driver associated with my video card. I've tested the difference between having a video driver selected, and having it disabled. There is a correlation with this DirectSound error message and the "VIDEO". Again, this issue only occurs if my RDP session has ended, or my systems screen is locked. Still logged in mind you, but screen locked.
 

Danr

Administrator
Staff member
The RDP and video driver issue seems to be correlated with using the VMR9 driver in TVS. However, the error is a video open error, not an audio open error. The new EVR driver (T>O>Playback) should address that. At least it does for my RDP editing.
 

ellinj

New member
The RDP and video driver issue seems to be correlated with using the VMR9 driver in TVS. However, the error is a video open error, not an audio open error. The new EVR driver (T>O>Playback) should address that. At least it does for my RDP editing.
Dan, Sorry for bumping an old thread but I am having the same problem with TVSUite 3 when processing from Tivo using Kmttg. I am doing this via RDP. Works fine when the RDP session is open, but I get an error that the Direct Sound device can not be opened. I have tried in Video Redo Configuration changing the PLayback Device Video Driver to Disable, not sure what you are reffering to regarding the new EVR Driver.
 

ellinj

New member
I am willing to upgrade if you think this is going to solve my issue?
Well, as it turns out I am having pretty good luck with the "edit without audio setting" and video driver to disable. Not sure what I am missing out on by doing this though.
 

Danr

Administrator
Staff member
I do all my real editing, as opposed to development and testing, on a production HTPC via RDP. Both RDP client and server are W7. I get the best experience with the EVR driver. No issue with audio or video other than network lag. For W8 clients, I always switch TVSuite to the EVR driver.

Typically, the video driver setting (VMR7, VMR9, EVR) only affects the video and not the audio, so it's likely that the audio driver issue is related to something else. Two things to look at are: (1) the audio settings in the RDP options. Are you bringing the audio to the host system or leaving at the remote system? (2) Are there any applications open on the remote system that might have exclusive control of the audio driver? This is the typical issue when VideoReDo can't open the remote system.

Finally, if you can always try TVSuite V4 as an eval before purchasing an upgrade.
 
Top Bottom