There’s also an enhanced version of Live Captions in the works, which will be able to translate a number of different languages in real time, whether that be from audio in a video or on a live call.Īn "advanced Copilot" is on the way. Other AI features include something called Super Resolution, which will use NPU hardware to upscale the quality of videos and games. If you don’t remember the name or contents of a document, the search term “find me the document that Bob sent me on WhatsApp a few days ago” is something search on Windows will actually understand. For example, you could type “FY24 earnings” and every instance where that term was on-screen will reappear for you to see and open.ĪI will also enhance search in Windows, with the ability to use natural language to find things that you’ve previously opened or seen on your PC. The company is working on a new history/timeline feature that will let users scroll back in time through all the apps and websites that Copilot has remembered, which can be filtered based on a user’s specific search criteria. Sources say these AI features will be “groundbreaking.” Unsurprisingly, the big focus for Hudson Valley is on next-generation AI experiences that are being woven and integrated throughout the OS, much of which will likely require new NPU hardware to function.Īccording to my sources, Microsoft's blockbuster new feature will be the introduction of an AI-powered Windows Shell, enhanced with an “advanced Copilot,” that’s able to constantly work in the background to enhance search, jumpstart projects or workflows, understand context, and much more. It is a hard to parse protocol designed to have a low memory and bandwidth footprint.Hudson Valley is all about AI. Using HID as wire protocol has been discussed, but for me, it is a no go. I would keep consumer events as keystrokes, not the best of designs but it works that way on… all OS? We can change that on the future.I propose to stick to USB HUT codes, we already have constants for them and are collision free. (No support for usb golf irons! What a shame!). In fact, they not even all USB Consumer usages. Linux seems to use a custom scancode map not aligned with USB.This class not only reduces boilerplate on current input device drivers, but also allows wmi/acpi/platform drivers to send input events (brightness, rfkill…) A kernel side helper class, lets name it InputDevice.Yes, this is a clone of what Linux does with evdev, but to be fair it is a simple protocol on both kernel and user space side. Events are small packets with: timestamp, event type, event value. All input drivers use the same protocol: An ioctl query returns device name, type and all events this device is capable of.Not really offtopic but… we seem to agree that Input stack needs some changes but we don’t share an opinion on what or how. We had some discussions on gerrit but it went too much offtopic. Users may then be able to just deactivate those rules and provide their own. One idea I had for the new shortcut preferences was to have a list of “default” actions provided by the system, which would be stuff like “Mail → Open application/x-vnd.Be.URL.mailto” Or user facing “Mail Button → open new draft email” PS/2 is unlikely to get a “huge” number of new keys anyhow) But i have not fixed it since the keymap doesn’t forward this currently at all, hence the idea to increase the size of the keymap structure. (I had adjusted the PS/2 Driver to forward events for keypresses of media keys, according to what osdev wiki has, there is one button i have unbound and one error in the code. Yes there are controls that are not buttons, but that seems like a bad reason to not bind any of them to buttons, all HID and non-HID media keys I have at home are actuall buttons. This should then be “easily” bound to running applications or running specific functions in applications, for example the “play/pause music” function for a media player.Īs for binding the keys to not keystrokes, I don’t know. Ideally the new preferences would take a “Press key combo now” aproach to shortcuts so it doesn’t matter that much whether the key is known or not (I mean hey, if you connect a flfire to your computer and want to bind that, why not?) That is capabilities discovered through getsuites is inacessible now. I think redisigning it is in order, especially because a huge chunk of functionality of applications. We can hardcode a list of most used ones if we want to keep shortcut preferences as it is. I also want to emphasize that consumer usages can’t be all faked as key strokes.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |