VoiceMeeter (All) bugs: EQ settings not saved (A/B)

The Virtual Audio Mixer discussions and support...
Post Reply
Teasy
Posts: 1
Joined: Fri Jan 11, 2019 10:02 am

VoiceMeeter (All) bugs: EQ settings not saved (A/B)

Post by Teasy »

Hi there,
Thank you for your continued efforts to keep VoiceMeeter running and improving! :)

Bug description:
Specifically after pasting a preset (usually for the "B" preset) for EQ settings, and you close the settings, it is not saved, and sometimes (at least in older versions) overwrites preset "A" (!)
So using presets is sometimes a scary experience ;)
So for a long time I have avoided them like the plague, until I found a workaround.
The first bug may be related to VoiceMeeter not flagging "preset was changed" after pasting (see below: Workaround 2, step 3).
The second bug may be related to either how VoiceMeeter saves or loads the B preset to file (see below: Workaround 2, step 6).

Bug reproduction:
1) Open EQ settings for an output channel
2) Change some settings (like decibel EQ sliders) (to notice a change)
3) Click copy (preset) -- "Ch.Copy"
4) Open EQ settings for a *different* output channel
5) Click preset B
6) Click paste (preset) -- "Paste"
7) Close settings
8) Open the same output channel EQ settings again (step 4)
You will see that either the B preset was not saved, or it has overwritten preset A (older version).

Workaround 1 (tested and works :P):
1) Buy additional sound card ;) (i actually did :P)

Workaround 2 (doesn't actually work!):
1) After pasting a copied preset, change one of the sliders in the EQ
2) Close the settings
3) Opening it again will show that the preset was saved (in memory!) properly.
... BUT
4) Close VoiceMeeter
5) Open VoiceMeeter
6) Open EQ settings and all B presets are GONE! (for all audio channels)

I hope you can fix this! :D
Thank you <3
Vincent Burel
Site Admin
Posts: 2133
Joined: Sun Jan 17, 2010 12:01 pm

Re: VoiceMeeter (All) bugs: EQ settings not saved (A/B)

Post by Vincent Burel »

ok, thanks for the bug reproduction, it will be corrected in coming update.
Post Reply