LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Device ID on Sound Input for USB Mic

I have a usb mic and I and trying to use th esound pinput configure VI.  I need to input the location for my usb mic. But going to device manager says my mic is at location 0000.0013.0000.002.000.000.000.000.000.

 

I obviously cannot use that in the location input on the vi. Is there a simple way to get around this?

 

 

0 Kudos
Message 1 of 8
(5,649 Views)

Updated: Here is a snippet of code on the left. The default is 0, the standard mic in on a sound card. But since this mic isn't on a sound card I am not sure how to use its location. Or whether this is simply a different and better way. Any one else run into this problem?

Untitled.png

Here is a photo of the properties under the device manager.

Untitle1d.png

0 Kudos
Message 2 of 8
(5,640 Views)

Hello Nate,

 

Try dropping an Acquire Sound Express VI. There is a Device combo box in the configuration dialog that shows all of the sound devices on the computer. Select the one you are using and it will give you the "device ID" number that you will use as an input to the 'Sound Input Configure' VI.

 

Hope this helps!

 

Joel C.

National Instruments

0 Kudos
Message 3 of 8
(5,631 Views)

It is oddly not listing it.  All the other applications on my machine can record sound from it, but not labview.

 

You can see the device I want to use, it is set as default.

Untitled.png

 

But it doesn't show in Labview.

Untitled.png

0 Kudos
Message 4 of 8
(5,626 Views)

Hello Nate,

 

Have you tried restarting the computer with the device connected? You might also try communicating via VISA instead.

http://www.ni.com/white-paper/4478/en

 

It can be a little more involved, you might be able to find some microphone specific VISA examples with a little bit of searching.

 

Thanks

Joel C.

National Instruments

 

0 Kudos
Message 5 of 8
(5,605 Views)

Guys,

Did it work with the White Paper suggestions? I have the same problem.

Did it solve the issue?

0 Kudos
Message 6 of 8
(5,507 Views)

Solved via Restar of PC/Win7,

Thanks

0 Kudos
Message 7 of 8
(5,500 Views)

Sorry Joel, I just noticed this topic again. I can't remember what I ended up doing anyways. I used to work for IT, so I definitely had restarted it.

0 Kudos
Message 8 of 8
(5,490 Views)