Open nametobechosen opened 1 year ago
could you please check 253
With 253 I had no crash "on its own", but some cases where mute did not work (hotkey, main window, icon).
When I changed the microphone in the main window, it crashed:
`Exception: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation.
---> System.Runtime.InteropServices.InvalidComObjectException: COM object that has been separated from its underlying RCW cannot be used.
at IntPtr System.StubHelpers.StubHelpers.GetCOMIPFromRCW(object objSrc, IntPtr pCPCMD, out IntPtr ppTarget, out bool pfNeedsRelease)
at int NAudio.CoreAudioApi.Interfaces.IAudioEndpointVolume.GetMasterVolumeLevelScalar(out float pfLevel)
at float? MicSwitch.Services.MultimediaDeviceController.getVolume() in C:/BuildAgent/work/61454f6050c7a045/Sources/MicSwitch/Services/MultimediaDeviceController.cs:line 85
at MicSwitch.MainWindow.ViewModels.MicrophoneControllerViewModel(IMMCaptureDeviceProvider deviceProvider, IFactory<IMMDeviceControllerEx, IMMDeviceProvider> deviceControllerFactory, IComplexHotkeyTracker hotkeyTracker, IFactory
Message:
Exception has been thrown by the target of an invocation.StackTrace:
at object RuntimeMethodHandle.InvokeMethod(object target, in Span
What type of inputs/outputs are you using ? How are they connected?
All these exceptions that you're getting basically mean that even if I will handle them micswitch won't be able to mute/unmute device. Probably it is related to issues with audio library that I am using (NAudio). As this issue is not reproducing on any of my PCs I won't be able to find the reason why it breaks, so you probably better try some other solution
I am mainly using a Jabra headset which is connected via bluetooth. In addition there are laptop speaker, laptop mic and camera mic available (but typically not used). The setup is not changed since several months where MicSwitch worked without any problem. No sure when which updates of MicSwitch, Jabra and Windows were done. All are on latest versions.
Because I don't know how to reopen #102 , I create this one as followup. 1.0.252 crashed as well.