👾 Issues

Audio Problems with 3.6.1 (denoiser?)
Hi, starting with Drovio 3.6.1, colleagues are reporting they cannot hear me very well. Often, they cannot understand what i say at all. I double-checked with Drovio 3.6.0 and i have no problems with the old version, also no problems with other communication tools. I suppose there is a compatibility problem with the new denoiser and my hardware/mic (microsoft webcam) or my voice. I had to switch back to 3.6.0 - is it possible to add a switch to opt-in on the old denoising? (Tried to send this via drovio "report problem", but it failed to send) ------------------ Hardware information Project version: 3.6.1 arm64 CPU type: Apple M4 Max Number of Cores: 16 Ram: Physical memory: 68719476736 OS: MacOS OS version: Version 26.6.2 (Build 25G83) Monitor: Screen 5 Width: 5120 Height: 1440 Screen 1 Width: 1728 Height: 1117 Audio devices: Audio Devices Input: default (Microsoft® LifeCam Studio(TM))(AppleUSBAudioEngine:Microsoft:Microsoft® LifeCam Studio(TM):21331000:3), CalDigit Thunderbolt 3 Audio(AppleUSBAudioEngine:CalDigit, Inc.:CalDigit Thunderbolt 3 Audio:20200000:2), Microsoft® LifeCam Studio(TM)(AppleUSBAudioEngine:Microsoft:Microsoft® LifeCam Studio(TM):21331000:3), MacBook Pro-Mikrofon(BuiltInMicrophoneDevice) Output: default (Pebble V3)(AppleUSBAudioEngine:ACTIONS:Pebble V3:㉕捤稰眷㕳愳㤷湲:1), Pebble V3(AppleUSBAudioEngine:ACTIONS:Pebble V3:㉕捤稰眷㕳愳㤷湲:1), CalDigit Thunderbolt 3 Audio(AppleUSBAudioEngine:CalDigit, Inc.:CalDigit Thunderbolt 3 Audio:20200000:1), MacBook Pro-Lautsprecher(BuiltInSpeakerDevice) Control computer permission set: true Mic access permission set: true, determined: true Input monitoring permission set: true Screen recording permission set: true Config file: { "audio" : { "agc_enabled" : true, "audio_input_device_guid" : "AppleUSBAudioEngine:Microsoft:Microsoft\u00ae LifeCam Studio(TM):21331000:3", "audio_input_device_name" : "Microsoft\u00ae LifeCam Studio(TM)", "audio_input_muted" : false, "audio_output_device_guid" : "AppleUSBAudioEngine:ACTIONS:Pebble V3:\u3255\u6364\u7a30\u7737\u3573\u6133\u3937\u6e72:1", "audio_output_device_name" : "Pebble V3" },
2
·
in progress
Keyboard layout broken on Windows with Remote Desktop running on the PC that's sharing their screen
In a Drovio session between two Windows PCs, when the sharing party is running remote desktop inside the shared session, the keyboard layout is very much broken. Concrete setup: * My PC: Windows 10, joining a Drovio session from other PC * Other PC: Windows 11, shares their desktop, runs Remote Desktop (mstsc.exe) and connects to a Windows 10 PC again On all three PCs (my, other, remote), the keyboard layout is set to German. When I type something into the Drovio session _outside_ of the Remote Desktop, everything is fine. When I type something into the Drovio session _inside_ the Remote Desktop, the keyboard layout is broken: * "Z" and "Y" are switched (German uses a "qwertz" layout, but inside Remote Desktop, it's like a "qwerty" layout) * Some special characters such as "-" and "_" don't work correctly, instead generating "ß" and "?" * The broken characters _change over time_, i.e., the layout gets more broken. For example, in today's session, the "=" character worked fine at first. After some time, it suddenly stopped working (I forgot which character was produced instead). This used to work fine in the past, but has been broken for some time (multiple months at least). It currently happens on the latest Drovio (3.5.2, installed on both PCs, "my" and "other"). And it's really, really annoying. PS: We can't start Drovio directly within the remote PC because the audio and video devices are on the host ("other") PC.
3