Activating/Deactivating preset with shortcut? - Bome Forums Archive 2005

Scr1pter

2016-05-30 10:56:10

Hello,

I have the trial version of the BOM MIDI Translator.
(Downloaded it yesterday.)
Actually, I'm really impressed of its functions even though I haven't tested much.
I faced one little issue (I found a little work-around, but maybe there is a cleaner solution).

When you have a list of presets it doesn't seem possible to easily activate/deactivate a preset.
Yes, I know there is a checkbox which can be checked/unchecked, but a script doesn't know this

So I'm looking for a quick way to:
- select a specific preset
- activate or deactivate it (no toggle!)

My work-around would be:
{
..1. Beeing in the preset area (can be accessed by CTRL+1)
..2. Pressing the arrow keys to go to the specific preset
.....(e.g. x times arrow up, 3 times arrow down = Preset 4)
..3. Placing the mouse cursor on a neutral position in the preset area
..4. Rightclick
..5. Pressing arrow up 4 times
..6. Pressing space bar
}

Of course I will not do this manually but using a Logitech Script (I have some devices).
It's possible, but I really would prefer not to move the mouse cursor because this is an error source.
Strangely, pressing the menu key of my keyboard (which is normally between RWIN and RCTRL) does nothing.
In the manual I found no shortcuts to activate/deactivate a preset either.

I would like to have this kind of automation because during work I would just press 1 key to switch a preset.
(This would switch to MIDI Translator, activate/deactivate a preset) and switch back to my DAW - within 1 second.

Edit
1. I use the trial of the MIDI Translator Pro
2. Shift+F10 doesn't work either. So maybe it's not a problem with the menu key itself but a general problem. F10 works to open the title menu, though.

Edit 2
Last question (for this thread):
Is it true that MIDI Translator Pro must always be maximized in order to work?
I saw a YouTube video where a guy said that if you minimized it, it wouldn't work anymore.
It has to be maximized (can be in background, but maximized.)

Best regards

DvlsAdvct

2016-05-31 15:37:04

Hi Scr1pter

Create a new translator, and the Message Type (where it says MIDI Message) drop-down should have an option for Presets. From there you can activate and deactivate presets, which would save you a TON of time.

Let me know if that works.

Jared

Scr1pter

2016-06-01 10:39:29

Hello DvlsAdvct,

Thank you for your reply.

I made some checks and now I found an almost perfect solution.
(Basically I did what you suggested.)
I created one preset which had 4 different translators.
Each translator activates a specific preset and deactivates the others (except the 1st one).
For this I just use Incoming: key stroke, Outgoing: Preset change.
It even works if MIDI Translator Pro is in background or minimized.

So, why it's just almost perfect then?
Because I really wish to use something like CTRL+Num4 as key stroke.
Right now I made it with Num 1 till Num5, but I'm very sure that in daily work
I will always need these keys in another application.
Perfect would be something like CTRL+SHIFT+Num4.
(Those key combinations I would add to my Logitech Gaming devices, so I will press 1 key only.)

Can this be changed somehow?
I had the idea to open the Preset file, but I doubt I can trick the program.

Code: Select all

[Preset.0]

Name=Test1
Active=1
PresetSwitchIgnore=1

Name0=New Translator
Incoming0=KAM10000KSQ10001065
Outgoing0=Pres020005Test2
Options0=Actv01Stop00OutO01

Name1=New Translator
Incoming1=KAM10000KSQ10001062
Outgoing1=Pres020005Test3
Options1=Actv01Stop00OutO01

Name2=New Translator
Incoming2=KAM10000KSQ10001063
Outgoing2=Pres020005Test4
Options2=Actv01Stop00OutO01

Name3=New Translator
Incoming3=KAM10000KSQ10001064
Outgoing3=Pres020005Test5
Options3=Actv01Stop00OutO01

It seems those values are similar to HEX codes.
But I doubt it will work to combine two codes with a +.

Probably it can be solved by using a script?

Best regards

DvlsAdvct

2016-06-01 16:00:16

You can use global variables to create additional keystroke shift commands. It would look something like:

Code: Select all

Translator 1: Ctrl Down
Incoming Message: keystroke
Down Action
CTRL
Rules: g0=g0+1
if g0>2 then g0=2
Outgoing: None

Translator 2: Ctrl Up
Incoming Message: Keystroke
Up Action
CTRL
Rules: g0=g0-1
if g0<0 then g0=0
Outgoing: none

Translator 3: Shift Down
Incoming: keystroke
Down Action
Shift
Rules: g0=g0+1
if g0>2 then g0=2
Outgoing: none

Translator 4: Shift up
Incoming: Keystroke
Up Action
Shift
Rules: g0=g0-1
if g0<0 then g0=0
Outgoing: none

Translator 5: Keystroke
Incoming: Keyboard
Num 4 
Up and Down action (can't remember the exact language)
Rules: if g0!=2 then exit rules, skip outgoing action
Outgoing: [i]Whatever MIDI message you want[/i]

Does that make sense?
J

Scr1pter

2016-06-03 09:17:59

Yes, it does make sense and I will test it.
However, I'm thinking if the better solution will be to use incoming Notes rather than key strokes.
My Oxygen IV has 8 Drum pads which send single MIDI notes on channel 10.
I don't really plan to use them as Drum pads, so using them as 8 buttons might be the better idea.
Then I will also check if it's possible to hold 1 Drum pad and to press another one in order to switch a preset.
(I guess it will be possible thanks to the (almost) unlimited features of MIDI Translator Pro.

)