LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Error 4800 occurred at Acquire Sound

Solved!
Go to solution

Hello guys. This is my first post. I've been trying to use the Acquire Sound express VI for my school work. However, that was not very successful and I kept seeing this error coming out. Do anyone know how to solve it please?anguswong159_0-1585731561511.png

I think that's not the problem of my program because I've also tried the example given by LabVIEW but the same error comes out once the program is related to my microphone.

The following is my setting on the Acquire Sound VI.

anguswong159_1-1585731821822.png

It seems that LabVIEW can actually detect my device, but I don't know why it cannot use it. And when I change the resolution to 4 bits, another error occurs.

anguswong159_2-1585731975910.png

 

Did I do something wrong or is it the problem of my hardware? I am using a macbook to run LabVIEW 2019SP1 (64bit) Windows version using Bootcamp btw. 

0 Kudos
Message 1 of 9
(3,195 Views)
Solution
Accepted by topic author anguswong159

Well, I see several "Red Flags":

  • I generally prefer to use basic VIs, not Express VIs, as I have better control (and, one hopes, a better understanding) of what is going on with the code.
  • The Sound VIs are made to work with the Windows sound system.  I tried the Acquired Sound VI (in LabVIEW 2019, but I've also used Sound in earlier versions of LabVIEW, but using the Sound Functions, not the Express VI), and it always "worked for me".
  • I notice you are running on a Mac, using what I presume (?) is a PC emulator.  Do you know if this system is sufficiently "Windows-compatible" that you can expect "hardware-specific" implementations to work with different hardware?

Bob Schor

Message 2 of 9
(3,142 Views)

Thanks for your help!

 

I have tried an example provided in the LabVIEW which uses basic VIs instead of Express VI, but the error also comes out.

anguswong159_0-1585825507653.png

It starts from the Sound Input Configure.VI. 

 

For the third point you've mentioned, I don't quite understand. But for other software like the browser or Zoom, the microphone works fine. And for LabVIEW, the speaker also works fine for some sound output VIs. Errors only occur when I use sound input VI.

0 Kudos
Message 3 of 9
(3,134 Views)

Sigh.  What do you expect me to do with a picture?  Attach your VI, which would let me:

  • Carefully examine it (there are aspect of the picture that I can't quite see clearly.
  • Test the code and see the error for myself.
  • Try to modify the code and see if I can "fix" the error.

One thing that I notice is that you are acquiring samples at quite a high rate, and appear to be trying to take many seconds of data all at once.  I've not done a lot of sound recording, but I would be tempted to take at most a second at a time and use a Producer/Consumer design to "export" the "sound bite" (bad pun!) and write it to a file for later playback.

 

Please attach your VI and I'll try to take a better look.

 

Bob Schor

0 Kudos
Message 4 of 9
(3,124 Views)

I am so sorry. The reason why I didn't attach the file is that the VI is quite short and simple so I believe that is not the reason causing the problem.

 

Here are the files anyway. I had the error on both of them. 

Download All
0 Kudos
Message 5 of 9
(3,119 Views)

I have a Dell Laptop (about 4 years old) running Windows 10.  I have 32-bit LabVIEW 2019.  If I plug headphones into my laptop and run the program "Simultaneous Sound Input and Output", then start talking, I can hear my voice through the headphones, with no gaps or breaks, as long as I keep the program running.  

 

Note the sample size in the example -- it is a reasonable size.

 

Bob Schor

0 Kudos
Message 6 of 9
(3,098 Views)

Please check if your mic is detected in your laptop when plugged in. Maybe you will need to upgrade your driver.

Certified LabVIEW Architect
System Test Architect
Electrical Engineering
JLR
0 Kudos
Message 7 of 9
(3,089 Views)

It is detected and it works on other software. And the driver is also the latest version.

0 Kudos
Message 8 of 9
(3,080 Views)
Solution
Accepted by topic author anguswong159

I've solve it by using Parallel Desktop to run Windows instead of Bootcamp. (In other words reinstalling Windows using a different method:).) The error just disappear automatically. Thanks everyone.

0 Kudos
Message 9 of 9
(3,071 Views)