leifiju

Also, the saving of settings does not work for the octave number, so I still cannot make a default preset tailor made for my controller.

For instance, if I use a 61 keys keyboard, with the default Oct at 3, the upper half of the displayed keyboard will go 2 octaves higher than my actual setting of "no octave change" on the hardware keyboard, so I find it quite impractical in a default/template quick use.

Again, let me know if can help.

Hi @OCH,

Thanks for this great update !

It adresses all the little drawbacks I had with the device.

However I want to point out a new bug : when the device put upon a track, it seems to quickly open then close a secondary window (less than half a second).

As I work in full screen mode (macOs Sequoia), it instantly takes me out to the main desktop, and I have to manually go back to Live.
And as Keyboard Monitor is on all my MIDI tracks, templates and default midi track, it's too inconvenient for me to work with and I will have to switch back to 1.1.3 until this is corrected.

Let me know if I can help in any way to describe or record the behaviour I'm encountering.

Cheers

Hi there @OCH,

I believe there might be a problem in your upload file for 1.1.3, because the Ableton history problem remains, and when hovering your logo on the device it says "v 1.1.2"

Cheers

Hi,

I noticed another bug in the device : sustain pedal changes are recorded as actions within Keyboard Monitor, and therefore as changes in Live's undo history.

For instance if I playback a midi clip with lots sustain pedal strokes, I'll have to do a whole lot of Undo to undo something I've done 10 or 30 seconds ago.

Cheers

@Crampe

Thanks a lot for the reply and details :)

Cheers

Hey there !

Love this device, but unfortunately it's not working correctly when using the (-) gain button. The values are incorrect.

For instance, if I set the shortcut to change gain by 1dB, on a 0dB clip, the first (-) click gets at -1.18, the second at 2.60, the third at 4.27, and so on. So if I want to lower the gain by 6dB, I get a 10.8dB reduction !

It must be a mistake in some operation in the treatment of negative values.

Could you correct this ?

Thanks a lot !

Come to think of it, I have another request, if I may : in sizes above 25, there's enough room to bring back the sustain pedal icon and or the wheels, that would be neat :)

I for one never use the floating window

Hi, great device !

Is it possible to store the keyboard size state in the next update ?

It is my default midi track, but I would like it to always be 49 keys by default, but it always comes back at 25, even in saved sessions, it's really frustrating.

And I can't access the patch in M4L as you prevented any change.

Cheers

@offthesky

I figured this could not be avoided without compromising the very purpose of the device

Thanks for the reply and details !

I will probably upload my version some day (need to clean the patch and translate text and currencies), and I will credit you of course

Thank you for your device !

I've used it to make my own device calculating the rate per hour according to the budget I have on the project (can't believe a plugin company charge this function 50$/€)

There's only one problem : with the time saving action (at each minute passing), if it occurs when you're undo/redoing stuff, it can ruin some work.

Have you got a workaround for this ?

Otherwise it's really great :)