Have something to say?

This board helps us understand what actually matters to you, what improves your workflow, what slows you down, and what you’d love to see next. 💡 Upvote what matters to you!

Tell us what would make our gear more useful in your daily setup. Your feedback directly shapes what we build and what we’ll prioritize. 💜

‼️ Important: If you have multiple ideas, suggestions, or bug reports, please create a separate post for each one so we can track and address them individually.

Pinned

In Progress

Creator Micro v2, knob1 - Battery charging issue (MEGATHREAD)

Hey everyone, If you’re experiencing problems with battery charging on your Creator Micro v2 or Knob1, please read the whole post before installing the diagnostic firmware. IMPORTANT NOTE: This update does NOT include a fix. It is designed solely to gather diagnostic data so we can understand what is preventing the charging cycle from completing. Installing it is not mandatory, but your participation would greatly help us resolve the issue. We’ve already solved about 90% of the charging issues reported so far, thanks to everyone who submitted feedback. However, there’s still a small number of cases where the problem persists, and we need to gather more information to identify and fix them. We are in contact with the chip manufacturer to figure out what’s going on, and your detailed reports are essential. Please include in your comment: What exactly happens when you try to charge (LED behavior, percentage stuck, etc.) Which cable and adapter you’re using Whether charging ever worked correctly Any other symptoms To ensure we collect detailed diagnostic data on your specific case, we have created a custom version of Input and a matching device firmware with an integrated system which collects battery information and charging status. We kindly ask you to leave Input open in the background so the diagnostics can run continuously. You can keep using your device as usual during this process! The more data we are able to collect, the faster we are be able to provide a definitive fix. Instructions First, download and install the custom Input application that matches your operating system: Input for Mac (Apple Silicon): input-0.13.1-rc.4-arm64.dmg Input for Mac (Intel): input-0.13.1-rc.4.dmg Input for Windows: input-Setup-0.13.1-rc.4.exe Next download only the firmware that matches your device model from this post: Creator Micro V2 custom firmware: firmware_cmv2_v0.3.0-rc.2_merged.bin Knob1 custom firmware: firmware_knob1_v0.3.2-rc.3_merged.bin ⚠️ IMPORTANT NOTE: Due to the diagnostic data being sent from the device, you might notice a small delay in typing every 10 seconds. This is completely normal and will go away when you decide to go back to the stock firmware. Finally install the custom firmware, to do so follow these steps carefully: Open the Input application and connect your device via USB. (If you have other Work Louder products turn them off) Once the device appears in Input, go to the Setup tab. Click Advanced Flash. Click Bootloader and wait until the button turns yellow. This means the device is in bootloader mode. Click Choose firmware file and select the custom firmware you downloaded. Click the Flash button that appears and wait until the flashing process finishes. Do NOT disconnect the device during flashing. When finished, exit the Advanced Flash screen. After the custom Input application and firmware are installed, you may continue using your device as usual. Thank you for reporting! Great new is that this is something 100% fixable in software and we just need to tweaks the right levers.

Davide // Work Louder 29 days ago

5
🐛

Bugs

Feedback on Input’s UI and UX

As a product designer, I see several issues in Input’s current UI and UX that impact usability, consistency, and perceived product maturity. Below is a structured summary of areas that could be improved: Once an icon is assigned to an action, there is no way to remove it without deleting and recreating the entire action. It would be more user-friendly to allow clearing or resetting the icon directly. When creating a new multi-action, selecting keys/actions from long dropdown lists can become cumbersome. Providing search within these dropdowns would make it much easier and faster to find the desired key or action. The interface appears to use multiple icon libraries, which results in visual inconsistency. Standardizing on a single, cohesive icon set (such as an open-source library like Lucide which contains thousands of icons) would improve visual harmony and make it easier for users to find relevant icons. Whenever an action is created or modified, the hardware updates immediately, which feels slow and interrupts the workflow. Providing a setting to switch between manual and automatic updates would make the experience more efficient. The “My actions” section in the drawer can become difficult to manage when working with multiple apps and many shortcuts. As the list grows, it becomes harder to locate the right action. Allowing users to organize actions into groups or folders (for example, by app or context) would significantly improve navigation and usability. Requiring users to open a drawer every time they want to add or edit an action introduces unnecessary friction. Making this interface persistent (such as a sidebar that remains visible) would reduce repetitive interactions and make better use of screen real estate. Basic keyboard shortcuts are not consistently supported within Input. For instance, using ⁠cmd + A to select the entire HEX code in the RGB context menu does nothing. Supporting standard platform shortcuts (select all, copy, paste, undo, etc.) would make the product feel more polished and efficient for power users. From an accessibility standpoint, the app appears to use relatively small font sizes and button styles with insufficient contrast. Increasing type sizes where appropriate and ensuring buttons meet recommended contrast ratios would improve readability and make the app more inclusive. Many interactive elements do not have tooltips or any form of inline explanation. Adding concise, informative tooltips for icons, controls, and less obvious features would reduce the learning curve and help users build confidence faster. Overall, the app currently gives the impression of being somewhat unfinished or in an early stage. Addressing the issues above, tightening visual consistency, and refining interaction details would substantially improve the quality and maturity of the product.

Balázs Barta 9 days ago

💡

Feature Request

Bluetooth connection

Hello! I just go the creator micro x framer. Love the design and quality! However, I’ve been having some rough time setting up. Probably user error since I just opened the box but would appreciate the help! On input, press to record key wasn’t working so I had to manually search Bluetooth connection has been painful. I have MacbookPro and iPad. I would like to switch connection seamlessly. But when either is connected, it won’t disconnect unless i turn off bluetooth of the device. After that, when I click “pair” and it shows up as “Accessory” and nothing works. I don’t see the name on the other devices, “Accessory” is not connected. I long press for bluetooth mode but it just blinks through 3 lights and back to first layer. So I restart the device, and it goes to search mode but pairing is unsuccessful on ipad. “Took too long to connect” At this point, the device won’t get out of bluetooth search mode, so I need to restart. Is there a cancel bluetooth search mode button? Is there a way to change input while on ipad? Hard to set it up for Procreate when I want to finetune the set up when I have to keep having to connect to MBP via wire and bluetooth when bluetooth is not working Thanks for the support!

Rachel About 1 month ago

3
💡

Feature Request

`[Temp] Layer x` Index Shifting/Dropping

Keybindings that use ‘Layer x’ or ‘Temp ‘Layer x’ break when the layer list is modified (re-ordering/deletion) The ‘issue’ is a result of layer keybindings being tied to layer’s index instead of key. When the layer list changes, the resultant shift/deletion may silently point to a layer that no longer exists or to an unintended layer due to index shifting x —> x - 1 Possible solutions? Layer change dependency notification (w/ action identifier) w/ option to delete anyway w/ option to delete + Input automatically updates action layer (or) block deletion of layers with action/keybinding dependency Color Code Actions with [temp] layer step pointing to deleted layer

Scott Lanning 15 days ago

💡

Feature Request