-
Notifications
You must be signed in to change notification settings - Fork 183
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Virtual audio capture doesn't work with Microsoft Expression SDK #16
Comments
I wonder if it's rejecting its format type, what does the output of ffmpeg On Mon, Sep 21, 2015 at 11:37 AM, tomason16 notifications@github.com
|
Thank you for the quick reply. It throws this error: |
oops try list_options instead of show_options |
The output of the command is: |
dang I was hoping it would be something besides 44100. Unfortunately I'm On Wed, Sep 23, 2015 at 12:49 PM, tomason16 notifications@github.com
|
Yes. |
Hi,
First, I would like to thank you for this development, it's great!
I'm trying to record by using the virtual audio capture device as the audio device in Microsoft expression SDK.
The code:
var audioDevices = EncoderDevices.FindDevices(EncoderDeviceType.Audio);
for (var deviceCount = 0; deviceCount < audioDevices.Count; deviceCount++)
{
try
{
if (audioDevices[deviceCount].Name == "virtual-audio-capturer")
{
_job.AddAudioDeviceSource(audioDevices[deviceCount]);
}
}
catch (Exception)
{
}
}
_job is actually a ScreenCaptureJob which is documented by Microsoft.
All other audio devices can be added by that method. Only when adding the virtual audio capture device, it throws an error -
{"Fail to set device to audio device source."} System.Exception {Microsoft.Expression.Encoder.ArgumentErrorException}
When using ffmpeg to try and record audio from the virtual device, it doesn't report any issues, so therefore it seems that it's installed properly (i just registered the relevant dll).
Microsoft expression SDK seems to actually recognise it, as it's in the list of devices, but throws the error above.
Please assist.
Thank you!
The text was updated successfully, but these errors were encountered: