10-12-2017 05:18 PM
I closed LV restarted and created a new vi, and it still doesn't work even when I dropped in from the palette.
10-12-2017 05:42 PM - edited 10-12-2017 05:51 PM
Your file doesn't exist
Try the attached it works for me. I had to zip it to attach it. It is just a renamed copy of
C:\Program Files (x86)\National Instruments\LabVIEW 2014\examples\instr\niFgen\demoSoundFile.wav inside the zip
10-12-2017 05:55 PM - edited 10-12-2017 05:56 PM
I am also still having issues. My version of LabVIEW is 2016, I'm not sure if the error is specific to the version though? I'm not clear on the fix you suggested earlier.
10-12-2017 05:58 PM
Still doesn't work for me. I opened the Play Sound File.vi and selected the file and tried to run the vi and I still get Error 4810.
10-12-2017 06:16 PM
Yes, it works in LabVIEW 32bit, but generates error 4810 in LabVIEW 64bit. Why don't you use LabVIEW 32bit?
10-12-2017 06:55 PM
Seems odd that you can't play .wav files in 64-bit. I want to use 64-bit so I can utilize more than 2GB RAM. Currently I use just under 2GB, but I can't believe I'm going to be limited by a sound alert. Come on NI I paid a premium to have a simple function like this work.
10-12-2017 08:03 PM - edited 10-12-2017 08:05 PM
Running on 64bit windows, 32bit LabVIEW can use up to 4GB of RAM.
Often, more efficient code can save much more... 🙂
10-30-2017 03:00 PM
I concur that Play Sound File.vi is broken in LV 2017 x64. I have filed a support request with NI (#7723194).
There is a workaround for 64-bit LabView, as the other Sound Output functions do seems to work; see attached.
"Play Sound Until Done.vi" uses VI lib functions to read the wave file and send the data to the designated output device.
"Play Sound Asynchronously" runs the above VI asynchronously so that control returns to the calling function before the sound file is complete. I haven't yet duplicated the functionality I had with 32-bit LV2015, in which playing a second file interrupted the first.
> Why don't you use LabVIEW 32bit?
Come now, Altenbach 🙂 NI sells and supports 64-bit LabView, and this is a documented function on both platforms. It is very reasonable to expect it to work. This NI's bug, and they will have to fix it.
-Rob Calhoun
10-30-2017 08:23 PM
@Rob_Calhoun wrote:
I concur that Play Sound File.vi is broken in LV 2017 x64. I have filed a support request with NI (#7723194).
There is a workaround for 64-bit LabView, as the other Sound Output functions do seems to work; see attached.
"Play Sound Until Done.vi" uses VI lib functions to read the wave file and send the data to the designated output device.
"Play Sound Asynchronously" runs the above VI asynchronously so that control returns to the calling function before the sound file is complete. I haven't yet duplicated the functionality I had with 32-bit LV2015, in which playing a second file interrupted the first.
> Why don't you use LabVIEW 32bit?
Come now, Altenbach 🙂 NI sells and supports 64-bit LabView, and this is a documented function on both platforms. It is very reasonable to expect it to work. This NI's bug, and they will have to fix it.
-Rob Calhoun
I do not believe anyone disagreed with you.
11-01-2017 11:35 AM
I looked into this issue, and there is a workaround to this bug. You can replace the "Play Sound File.vi" with "Sound File Read Simple.vi" and connect its output data to a "Play Waveform" express VI. This worked for me in LabVIEW 2017 x64.