newbieTrying34 wrote:Here you go:
Thanks. I'm trying to figure out what triggers all of this, more specifically. Like, why does VM opening the realtek device, cause it to send its own output to its own input, but opening that device with other apps, doesn't do that. So I'm trying to figure out whats different about how the device is opened.
So, one thing I noticed is that in windows settings, you have the realtek set to work at 192kHz, but in VM it's opening at 44k1. What happens if you try windows at 44k1, or voicemeeter at 192k? What happens if you disable exclusive access to the realtek device (forcing it to be opened as a shared device by VM, as other apps would, rather than exclusive, as VM normally does)?
To explain - these tests are not intended to fix the problem, nothing of what I'm saying at this point is, these are just tests to see what happens - what we are trying to do is find out what the problem is, so it can be fixed. The idea with checking these settings, is to figure out if having voicemeeter open the driver as the other applications do, will stop the device from glitching out.
newbieTrying34 wrote:You mean on the A1 output from Voicemeeter right?
I meant all of them but I think you've already confirmed my suspicions here.
newbieTrying34 wrote:muting A1 no longer sends feedback to mic input, unmuting starts sending it again. Muting the VAIOs via the sound icon in task bar (or sound control panel) or muting the video player also no longer sends feedback, unmuting starts sending again.
Right, so what you're seeing is that when you stop sending audio to the realtek output, it no longer appears at the input. To further explore this, what you need to do is mute the VAIO devices in voicemeeter (not in windows as you've already tested) and mute the mic input in voicemeeter. Now, no audio should be coming into VM (because VAIO and mic muted), and so none should be leaving it... but you'll still be able to see the mic input levels (greyed out) in voicemeeter's meters. Now, play an audio file from the VM 'tape deck and make sure it is sent to A1. It is now outputting to the realtek device and you should hear it play. Look at the meter for the mic. Is it still silent, or do you see the meters moving (but greyed out because muted)?
newbieTrying34 wrote:So what is happening is that when I launch Voicemeeter with one of the VAIOs selected (as just about every user does anyway) instead of closing the recording side of the VAIOs (output from Voicemeeter) like it should, it keeps them open and working as a throughput to the input side.
If that were the case, then it would happen regardless of the mute states in VM, it would just be constant.... (edit) Also, you can see that the audio feedback is coming from the realtek mic input, not the VAIO inputs..... No, what you're seeing is that the realtek output is being fed back to the realtek input, and not by voicemeeter. It's just that it starts doing it when voicemeeter is started.....except for....
newbieTrying34 wrote:reverted to Windows HD audio.... now all audio goes to the mic with and without Voicemeeter.
How? This is not normal behaviour and there's practically no chance this driver does this or it'd be all over the internet with everyone with a realtek card talking about how it doesn't work.
Rather than stop with this driver, you should continue with the problem there. Having made the problem worse, is NOT a bad thing. It's a GOOD thing. You're NOT trying to fix it yet! You're trying to BREAK it. Breaking it, helps you figure out exactly WHAT breaks it, and then, once you know what breaks it, you can try to fix that.
You mentioned some "audio shielding" what do you mean by that? I'm starting to wonder if there's another factor involved here which has not been considered yet.