I would like to use VB-Matrix (or an alternative of VB-Audio) to convert the audio stream from an audio source such as VLC or Kodi into ASIO format, which is fed into AudioVero's AcourateConvolver.
The sampling rate should be specified by the source (VLC or Kodi) not by the target (AudioVero's AcourateConvolver).
Currently Matrix (and Voicemeeter) seem to regard the target as the master for setting the sampling rate - apart from that they work fine!
How do I proceed?
Any help appreciated!
Set master sample rate by audio source VLC or Kodi
-
UlrichRchb
- Posts: 2
- Joined: Mon Sep 15, 2025 10:08 am
-
Vincent Burel
- Site Admin
- Posts: 2214
- Joined: Sun Jan 17, 2010 12:01 pm
Re: Set master sample rate by audio source VLC or Kodi
Matrix and Voicemeeter are using a master clock (internal or base on device) so the working samplerate is not specified by the source, even if the source can be in a different samplerate.
Only HIFI-CABLE and ASIO bridge is supposed to do that. The ASIO device sample rate is expected to follow the samplerate used on HIFI-CABLE input (playback device).
Only HIFI-CABLE and ASIO bridge is supposed to do that. The ASIO device sample rate is expected to follow the samplerate used on HIFI-CABLE input (playback device).
-
UlrichRchb
- Posts: 2
- Joined: Mon Sep 15, 2025 10:08 am
Re: Set master sample rate by audio source VLC or Kodi
I tried to implement your suggested HIFI-CABLE and ASIO bridge solution, but was not successful.
ChatGPT stated:
Vincent Burel’s statement is technically correct, but:
it refers to internal / legacy test builds or older Windows versions (Win7/Win8) or 32-bit ASIO hosts
Your setup is:
- Windows 11
- 64-bit AcourateConvolver
- modern driver stack
- multiple VB-Audio products already installed
➡ The combination no longer works in practice. Your screenshots prove this beyond doubt.
Can this be fixed by manual registry cleanup?
Technically: yes.
Practically: not worth it.
You could:
- delete ASIO keys under HKLM\SOFTWARE\ASIO
- remove VB-Audio CLSIDs
- disable driver signature enforcement
- reinstall in test mode
But even if you succeed:
- the driver is still 32-bit only
- unstable
- unmaintained
- and may break again on the next reboot or Windows update
For an audio server / purist setup, this is the wrong direction.
The honest conclusion (no more chasing ghosts)
You have now conclusively demonstrated:
✔ Hi-Fi Cable works
✔ WASAPI source-clocking works
✔ AcourateConvolver works
VB-Audio ASIO Bridge (public v1.0.0.7) does not work on your system
At this point, continuing to fight the installer is wasted effort.
ChatGPT stated:
Vincent Burel’s statement is technically correct, but:
it refers to internal / legacy test builds or older Windows versions (Win7/Win8) or 32-bit ASIO hosts
Your setup is:
- Windows 11
- 64-bit AcourateConvolver
- modern driver stack
- multiple VB-Audio products already installed
➡ The combination no longer works in practice. Your screenshots prove this beyond doubt.
Can this be fixed by manual registry cleanup?
Technically: yes.
Practically: not worth it.
You could:
- delete ASIO keys under HKLM\SOFTWARE\ASIO
- remove VB-Audio CLSIDs
- disable driver signature enforcement
- reinstall in test mode
But even if you succeed:
- the driver is still 32-bit only
- unstable
- unmaintained
- and may break again on the next reboot or Windows update
For an audio server / purist setup, this is the wrong direction.
The honest conclusion (no more chasing ghosts)
You have now conclusively demonstrated:
✔ Hi-Fi Cable works
✔ WASAPI source-clocking works
✔ AcourateConvolver works
VB-Audio ASIO Bridge (public v1.0.0.7) does not work on your systemAt this point, continuing to fight the installer is wasted effort.