Hi there, I got the new email. Mentioned working hard on MTP. But can’t find release notes or anything.
Is there an update?
Hi there, I got the new email. Mentioned working hard on MTP. But can’t find release notes or anything.
Is there an update?
Not yet, but based on the email, maybe something pretty soon.
Steve Caldwell
Bome Customer Care
Yessss.
MTP update! can’t wait.
Out of curiosity, is there a specific feature you are looking for?
Dark mode. Customizable brightness and saturation.
Row colour-shading banding.
Colours. Presets have their own colours, group colours, translators can have their text be coloured. A palette to save, import/export colours. Disabled things would have their text greyed out, still readable but grey. Groups could have the background for that whole group coloured.
Group headers (within the presets) to divide translators into sections. They would be collapsible by a drop down arrow. Each group would have its own separate index to number the translators, alongside the static global index. Selecting the group header selects all its translators. Groups can be affected by outgoing actions, which affects all the translators in the group at once.
Preset groups. I would make each MIDI device have a collapsible group of presets. The group governs all its presets, and has its own default MIDI in/out (presets have higher priority). It can be disabled itself, or used however presets are. Which affects all the presets in its jurisdiction. Translator outgoing can affect entire groups, just like presets. If a group was disabled, its presets still have their checkboxes checked, but the preset text is greyed out, for visual reference of why they aren’t working.
Also preset subgroups. The main group is for the device, the subgroups are for different things that the device does.
Icons. Stop flags would put a stop sign icon onto translators etc. A translator, if it’s outgoing effects another translator, and this one is blue text, it will have a blue outgoing arrow icon. Any translator that is affected by this one would have a blue incoming arrow. Changing the translator colour would change its arrow colour. Or there could be a column for in/out arrows.
Stop flags could have ‘except for’ added on as secondary actions. "Stop processing except do process this other thing/s (such as enabling a light. So that the stop flags can be where they should be, instead of having to be only with the lights translators, etc.)
Multiple outgoing actions for one translator. A translator sends a command but also toggles a light, etc.
An option to make the translator “numbered outgoing” latch onto presets. Currently if I want to affect multiple presets in a single action I have to use ‘by index number, not by name’, but if I move the presets then the translator breaks, having different numbers, and I have to redo it. This would latch onto them, changing its numbers when the presets change.
Or, all objects would have a static ID, not just an index number. MS Project does this for when entries get moved around it doesn’t break anything linked to it. You could search by ID. Incoming/outgoing actions can use the ID #.
App latching (MTP starts when FLS starts, closes when FLS closes)
…
…
woo hoo! that is a great feature request list!
Some of them are already available (I think), some of them are already planned in one or in another way, and some are entirely new. We’ll add them to our feature tracker.
As always, no promises, especially for the upcoming release, but we’ll report back here when any of these features make it into a release.
Thanks!
YES
YESSSS
YESSSSSSSSSS
It won’t let me post unless I type something.