Window Message - how to set up? - Bome Forums Archive 2005

Specker

2015-01-01 21:02:48

I´m completely new to Bome.
So far i love this program, i use it for my DAW called Tracktion 5.
I managed to midi map certain keyboard shortcuts to my Korg Nano Kontrol midi device.
That works perfect so far.

The problem is, that when it comes to commands like (control + c) or something like that, with two keystrokes,
the DAW won´t recognize it, i really don´t get why..

I just want to midi map the copy command.
This could also work with a windows message, right?

The Windows Message is #0301 WM_Copy Decimal 769.
I have no clue how to get this into Bome, so Bome will do the copy command.

Could you please help me with this?

DvlsAdvct

2015-01-02 16:49:35

Hi Specker

I'm not too sure on how to program Windows Messages yet, since I use them so infrequently, but I'll pass that up to the boss man and I'm sure he'll have an answer.

As far as the keyboard shortcuts, we've had different interactions from different DAWs, some being more accepting than others. One thing that has worked for me is to not use the Keyboard Action command, but instead have two different translators, one for button press and one for release, for each button (ctrl and C separately). I put a delay on the C press. It looks something like:

Code: Select all

Translator 1: Press Ctrl
Incoming Message: 90 30 7F
Outgoing Message: Keystroke Down Action: Ctrl

Translator 2: Press C
Incoming Message: 90 30 7F
Outgoing Message: Keystroke Down Action: C
5ms Delay

Translator 3: Release Ctrl
Incoming Message: 90 30 00
Outgoing Message: Keystroke Up Action: Ctrl

Translator 4: Release C
Incoming Message: 90 30 00
Outgoing Message: Keystroke Up Action: C

Let me know if that works.
Jared

Specker

2015-01-02 20:23:18

YES!!! It works!!! THX!!!

I managed to get rid of pretty much all my midi problems with this method today, incredible!

About the WM_Messages, i think this thread is really informative:
http://www.bome.com/forums/viewtopic.ph ... sage#p4368

I downloaded the software winspector-spy and tried some things but had no luck so far..

but anyway.. thank you for that fantastic workaround!