The system is performing well overall. The mic latency issue has been resolved, which is a significant improvement. However, there are still three remaining issues:
The name change in the host file is sometimes reflected in the router, but other times it reverts back to "glkvm." The new name does appear in the command prompt, so that part seems fine.
There is still an annoying issue with mic noise, specifically crackling.
The mic name still appears as sink/ source after toggling through the various options.
It was mentioned in earlier post that disabling the "Enable audio enhancements" option could help reduce noise, but that option does not appear at all.
"Microphone Access Denied" from controlled Win 11 and then it gets reset to "Mute".
I think it is caused by that GLKVM app 1.1.0 downloaded from AppStore is not authorized to use the microphone from the client system. It should be in the list "Privacy & Security -> Microphone", next to Zoom, WhatsApp, MS Teams, browsers, etc.
UPDATE: microphone works when Comet accessed from the browser.
I'm still seeing an issue with the keyboard on a Mac-to-Mac setup (this was also happening with the previous firmware). Any key combo involving 'Command' gets repeated as long as the 'Command' key is held down.
Here's how to reproduce it:
Hold down 'Command'
Press and release 'W' to close a window
Keep holding 'Command'
The issue is that multiple 'close window' commands are sent rapidly, even though 'W' isn't being pressed anymore. So unless I release 'Command' very quickly, it keeps closing windows. As far as I can tell, this happens with any 'Command' combo.
working well! I had the same issue after upgrading from 1.3.x to 1.4 beta1 as I did beta2, I had to reset the device for tailscale app to work again, it just hung and was spinning, overall everything is working as stable as 1.3 but with more features! jiggler back saving the day.
I think I've figured out the issue. It appears that COMET cannot synchronize time via NTP - at least it couldn't when these logs were generated. This might be causing Tailscale's abnormal behavior. I can see both the connman process and ntp process are running. Do you have any firewall rules that might be blocking NTP protocol?Or your COMET can't access internet?
Nothing stopping it. This happened on both upgrades of 4, I couldn’t even pull the debug log when I first had the issue, the output was.
{
"ok": false,
"result": {
"error": "str",
"error_msg": "Error collecting logs: ZIP does not support timestamps before 1980"
}
}
When trying to get the logs exported, even with the time zone and such set
it has the correct UTC setting but the date/time was, Wed Dec 31 17:04:45 MST 1969 is the date output
After a reset it got right and I was able to proceed. This was coming from the latest 1.3 to the first beta 4, now the 2nd beta I was able to at least pull the log.
No rules or anything customized other than the display size.
Extremely Noisy Microphone in Google Meet via glkvm.local
Hello,
I'm having a problem with microphone audio when running a Google Meet call on my Windows Surface Pro 8, which I'm controlling from my MacBook Air via my KVM (glkvm.local).
What Works: Audio I receive on the Macbook air is perfectly clear. Latency also seems good.
What Fails: My microphone audio is extremely noisy and completely unintelligible to the other person on the call.
To test this, I started a Google Meet call and sent the link to my girlfriend, who joined from her iPhone. She confirmed she couldn't understand anything I was saying because my audio was just loud static. Both of us were on the same local network.
The microphone input is crackling, and overall audio quality is noticeably inferior compared to PiKVM. To verify this, record mic input using Windows Voice Recorder through both PiKVM and Comet, then compare the recordings. This was tested on a Dell Latitude and an Acer gaming PC.
Mouse movement becomes jerky when handling large amounts of text or data, such as in a table or spreadsheet. In contrast, PiKVM delivers smoother cursor performance under the same conditions. The test setup was: RDP → Computer 1 → Comet → Computer 2 (spreadsheet).
This is the first time working with a device such as this, and I am pretty impressed about the overall quality of it...
Consistent Audio, Video, and Microphone for about five hours with no issues.
Just in case, I am using a Macbook M1 13 inch as the PC connected to the Comet KVM and Dell 7320 Detachable with the Windows client.
Ability to change the device’s name that appears as KVM in Windows and MacOS.
A couple of adjustments on Microphone custom naming and Microphone Volume management.
If possible, camera support with customizable name .
Host PC: MacBook Pro 13 M1
Host OS: MacOS 26 beta
Comet firmware: v1.4.0 beta2
Client OS: Windows 11 pro x64
Client App: 1.1.0 Release1
Just as a suggestion, it would be fantastic if the GL-RM1 could remember—or let us save—session-level presets for the following:
-Custom EDID profiles (ideally with multiple slots)
-Speaker state (I always need it on)
-Vertical scroll direction (I use reverse)
A “last-used” or “default preset” option would spare us the repetitive setup and keep workflows humming.
the tailscale issue popped up for me after changing the EDID, and or after enabled/disabling the disc mount. It is all related to time. Each time tailscale was failing it was because the time was not being set. One key difference I noticed is I've had the cloud connect disabled. As soon as I enabled the cloud it sync'd the time and tailscale was working again.
I think there is a bug related to when it attempts to sync time, without the proper time it will not connect to tailscale