Installing Sound and vibration toolkit

[Shuggy1]

I am currently upgrading to a newer version of LabVIEW (v24Q3) on a stand alone Windows 11 machine and trying to install the sound and vibration tool kit with it. 

The latest SVT available is V23 online. Install fails as the advanced signal processing toolkit installed is not the same version of SVT. Unfortunately the last version that both SVT  and ASPT were both released together was 2021. 

If I try installing SVT  and ASPT  at v21 with LabVIEW v24Q3 it does not work either.

If I want to use SVT do I need to use an old version of LabVIEW? Does anyone have SVT installed with a current release or is this an issue with offline installers? 

Shuggy

[dsb@NI · Accepted solution]

Sorry, I didn't notice your post earlier.

*** Copied from internal escalation ***
This is a known issue which is seen with LabVIEW 2024. We are working on getting this added to the known issues list. Can you please try the below workaround and see if this fixes the issue.

Workaround:

1. For LabVIEW 32-bit, copy LVASPT_TFA.dll from C:\Program Files\NI\LVAddons\aspt32\1\resource to C:\Windows\SysWOW64
2. For LabVIEW 64-bit, copy LVASPT_TFA.dll from C:\Program Files\NI\LVAddons\aspt64\1\resource to C:\Windows\System32
3. Relaunch LabVIEW

*** End Copy ***

I was able to reproduce the issue locally, and this workaround did work for me in LabVIEW 2024 Q3 64-bit.

[Shuggy1]

Thanks Doug,

I am using LabVIEW 64-bit and the above solution has resolved the issue. Thank you! For information, a warning was noted on the install that the Advanced signal processing toolkit was needed to be installed (v23) however a v24 version was installed through the LabVIEW installer prior to the SVT install, following installation of the SVT the ASPT was recognised and all is working fine.

Thank you

[iyogurt]

Is this fixed in LV2025? I ported some code from LV2023 to LV2024Q1 and while I could get S&V TK installed, when opening my code I found a number of dll calls that couldn't locate sndvib.dll. One specific VI is "OAT Convert to Even Angle Signal.vi", it has a few dependencies internal to it that cannot find that dll and cause a broken run arrow. If I create an empty project in 2023Q1 and 2024Q1, create a new VI, and add that VI to it the dependency trees will be the same in the project, the file locations will be the same, but the VI will have a broken arrow in 2024. I've attached a screenshot of this, left is 2024Q1, right is 2023Q1.

[dsb@NI]

This issue has been escalated to the owning team. No fix has been released, so please continue to use the workaround for now.

[iyogurt]

That workaround doesn't solve my problem. See my screenshot. 90% of my S&V Toolkit has no issues, but many of the functions have Call Library nodes that call sndvib.dll that do not work in 2024Q1. I'm going to upgrade to 2024Q3 and see if that resolves it.

[MR_DE]

Hi iyogurt,

did you find a solution? I have a similiar issue...