VB-Audio's Forums

Hello,

I have Voicemeeter 10.0.5.1 installed on Windows 10 x64.

It works fine at 44100 and 48000, but crashes as soon as 88200 or 96000 is selected (Preferred Main Sample Rate).

The ASIO driver is of course compatible with both. The same configuration used to be working fine on Win 7 64, so I'm quite surprised.

Is there any way to find out what is happening?

Thank you

Never heard about this problem before...
what do you mean by "crash" ? is there a Windows Message ? Voicemeeter is frozen or you just get no sound ?
what is your ASIO driver ?

Hello Vincent,
Thanks for looking into that.

ASIO driver is Merging Ravenna ASIO driver latest version (10.1).

Voicemeeter doesn't crash when selecting a RME HDSPe ASIO driver for the output (@ 96000). So the driver might have some responsibility.

On the other hand, other ASIO hosts (Foobar, HQPlayer, JRiver MC) can handle any rate (as far as I can tell, I didn't test them all), so Voicemeeter might also have some responsibility.

I have tried with no input selected (in case their own rate would play a role), same result. I just thought I could try Banana too. I will and let you know.


I got this in the event log:

Nom de l’application défaillante voicemeeter.exe, version : 1.0.5.1, horodatage : 0x57f65ce7
Nom du module défaillant : voicemeeter.exe, version : 1.0.5.1, horodatage : 0x57f65ce7
Code d’exception : 0xc0000005
Décalage d’erreur : 0x00027505
ID du processus défaillant : 0x1ad4
Heure de début de l’application défaillante : 0x01d25c7b5cf4f874
Chemin d’accès de l’application défaillante : C:\Program Files (x86)\VB\Voicemeeter\voicemeeter.exe
Chemin d’accès du module défaillant: C:\Program Files (x86)\VB\Voicemeeter\voicemeeter.exe
ID de rapport : 69b76ce8-4040-422d-a09a-7a0bed3a31b9
Nom complet du package défaillant :
ID de l’application relative au package défaillant :

Working configuration and crash look like this. Crash is just after Windows pretends to look for a solution for a few second, and right after 9600 or 88200 has been selected as Preferred Main SampleRate (exact sequence of events : select rate, sound stops right away, , VM hangs for a few seconds, and then Windows gives the bad news):

as a side note, topic subscription doesn't seem to work. I didn't get a mail (not even as spam) although this topic is "watched" according to my user panel. Just to let you know, no big deal as far as I am concerned.

Well, no luck with Banana, it crashes the same way for the same reason.

Strangely enough, I had uninstalled VM and rebooted before installing Banana and rebooting again, but after Banana crashed, VM was available as if it was not really uninstalled or installed along with Banana. Don't know it that's "normal".

ok, i will check it and correct the problem if i can in the next update.
you can also ask to Merging to check their driver with Voicemeeter...

Foobar, HQPlayer, JRiver MC are surely not openning ASIO device with 64 i/o max (like Voicemeeter does)... you should make the test with a DAW like Cubase, Reaper, Protools...

uninstalling Voicemeeter does not help... yes Voicemeeter Banana package installs also Voicemeeter standard.

all e-mail services are off on this forum.

Thank you Vincent, I'll see what I can get done on my side. I sent a mail to Merging support.

Please let me know if you need me to run some tests for a future version.

ok just installed Ravenna ASIO driver V 10.1.2

Debug session shows that buffer pointer provided by Merging Ravenna ASIO Driver might be not valid at 96 kHz

My debugger breaks when using this pointer:
Asio_BufferInfo[4].buffers[1] = Bad Pointer.

...Or they forgot to limit the number of i/o to 2 or 4 (instead of 8)
the fact is that Voicemeeter will open 64 channels if present,
that's maybe why you have not the bug with other applications openning only 2 channels...

Are you reporting this information to Merging? I'm happy to do it if you prefer, but it's obvious it would be quite difficult for me do discuss details.

Just for information, in case that might be useful, based on what you observed, I thought it might be worth it to quickly test 96000 while reducing the number of output channels managed by the driver (through the Ravenna ASIO panel), as a possible workaround. That got my PC to reboot after a Windows msg saying that VM was not responding (not the same msg as before).

I suppose there isn't much more to do before Merging fixes their driver then.

BigBen wrote:Are you reporting this information to Merging?

yes it's done... they will correct it in next version i guess...