Capture One and Exposure knobs

0
0

Hi,

I’ve got the following settings for Bome and the XTouch Mini (see attached bmtp).

The aim is to use it with Capture One photo editing software so I can usse the knob to increase and decrease exposure. The program sees the shortcut as numpad + and -.

I’ve got the keycommand to work correctly with the program, when turning the knob (but the same shortcut happens both anti clockwise and clockwise).

Here’s the output from the log (doing a small burst).

1: IN 0.8 Control Change on ch. 11 with CC#:1 (0x01) and any value set ‘pp’ to value=112
2: OUT 0.8 Alt(Num +) : keystroke suppressed (main window active)
3: IN 0.8 Control Change on ch. 11 with CC#:1 (0x01) and any value set ‘pp’ to value=113
4: OUT 0.8 Alt(Num +) : keystroke suppressed (main window active)
5: IN 0.8 Control Change on ch. 11 with CC#:1 (0x01) and any value set ‘pp’ to value=114
6: OUT 0.8 Alt(Num +) : keystroke suppressed (main window active)
7: IN 0.8 Control Change on ch. 11 with CC#:1 (0x01) and any value set ‘pp’ to value=116
8: OUT 0.8 Alt(Num +) : keystroke suppressed (main window active)
9: IN 0.8 Control Change on ch. 11 with CC#:1 (0x01) and any value set ‘pp’ to value=118
10: OUT 0.8 Alt(Num +) : keystroke suppressed (main window active)
11: IN 0.8 Control Change on ch. 11 with CC#:1 (0x01) and any value set ‘pp’ to value=117
12: OUT 0.8 Alt(Num +) : keystroke suppressed (main window active)
13: IN 0.8 Control Change on ch. 11 with CC#:1 (0x01) and any value set ‘pp’ to value=116
14: OUT 0.8 Alt(Num +) : keystroke suppressed (main window active)
15: IN 0.8 Control Change on ch. 11 with CC#:1 (0x01) and any value set ‘pp’ to value=115
16: OUT 0.8 Alt(Num +) : keystroke suppressed (main window active)
17: IN 0.8 Control Change on ch. 11 with CC#:1 (0x01) and any value set ‘pp’ to value=114
18: OUT 0.8 Alt(Num +) : keystroke suppressed (main window active)

Is there anything I can do with the bmtp settings so that it sees I’m rotating clockwise or anti-clockwise?

I’m pretty new to this but once I get this working, I’ll be able to figure out the rest. Thanks!

Attachments:
Marked as spam
Posted by (Q&A Forum: 1, Answers: 4)
November 24, 2018 3:22 am
79 views
0
Private answer

Hi,

I created a much simpler version (no timers). The caveat would be that if you move the fader too fast,  your application may not see all of the keystrokes depending on how quickly it can handle them.

Each fader uses a single global variable. I have 2 faders programmed. The first using ga and the second using gb.  The faders are in pairs, one for right/up movement and one for left/down movement.

I also programmed a button to disable movement for calibration using variable g0. If you run out of room on either end, simply press the button while repositioning the fader to the center. The button disables both faders for calibration.

Of course you will need to assign your own cc’s and outgoing keystrokes but hopefully since this is a much simpler design, it will be more to your liking so that you can modify as necessary.

You will also need to adjust your input device. I used and APC-MINI with the first two faders and the round button above the first fader as the calibration button.

 

Enjoy!

Steve Caldwell
Bome Q and A Moderator and
Independent Bome Consultant/Specialist
bome@sniz.biz

Marked as spam
Posted by (Q&A Forum: 42, Answers: 3296)
November 25, 2018 4:00 pm
0
Private answer

Try this.

All I did was

  1. Remove the redundant translator in preset 2
  2. Change the outgoing Timer in preset 2 to Fader 2
  3. Change the two incoming translators  in preset 2 to look for Fader 2 instead of Fader 1

Untested as I don’t have a MIDI controller handy so going off of memory.

You did fine on changing variables but didn\'t change the timers for the second set.

Attachments:
Marked as spam
Posted by (Q&A Forum: 42, Answers: 3296)
November 25, 2018 3:40 am
0
Private answer

Thanks Steve.

Could i ask though, how do you get a second set/knob to work? I read the manual and understand the difference between variables and global variables, but for some reason my second “preset” affects the first. So when I move on knob on the midi, two sets of controls are being affected. and I can’t figure out why (see attached)

Attachments:
Marked as spam
Posted by (Q&A Forum: 1, Answers: 4)
November 25, 2018 2:27 am

You need a different timer on the second fader. I recommend you call it “Fader 2” otherwise you are still triggering fader 1 keystrokes.

( at November 25, 2018 2:34 am)

Thanks, I tried that but it’s still controlling the first one even though I’ve changed all variables. Think this program is beyond me in the end but thanks for helping anyway. I’ll mark this as resolved as think it’s better I get a loupedeck.

( at November 25, 2018 3:30 am)
1
Private answer

I just realized the project file in the video did not put out keystrokes but only converted absolute cc to relative cc. The below takes the relative value and then using 2 translators either executes a right key output or left key output depending on the direction of the knob. It should get you closer to what you want but you might need to change the outgoing keystrokes for your application.

 

Marked as spam
Posted by (Q&A Forum: 42, Answers: 3296)
November 24, 2018 7:27 am
Amazing, it works! Thank you for taking the time as it made my weekend! I guess to add an additional knob, I’d have to change a global variable. I’m trying to make sense of it all! Does the ”set variable to value pp” have to be different? So if the variable isn’t global it can always remain pp right per preset? Edit: this is far more complicated than I thought. Changed the ”Ga, gb and gc” to ”ha, hb an hc” but for some reason the second slider controls the first due to a variable still referencing the other one. Argh, will try to find it.
( at November 24, 2018 9:51 am)

Glad to help and that it worked for you! (even though I never tested it before sending).

( at November 24, 2018 3:19 pm)
1
Private answer

Hi,

Yes, as suspected,  it looks like your knob puts out an absolute value instead of a relative value.

Please see the below  tutorial video on YouTube:

 

https://youtu.be/VCvxPZawJyE

In the description, there is a link to the project file that was used in the video.

There is also a link to both the video and the project file in the below thread:

 

https://www.bome.com/support/kb/new-tutorial-map-absolute-control-change-to-relative-encoder-with-bome-midi-translator-pro

 

Basically what you will be doing is converting an absolute value to relative for your knob and then using the relative value to determine whether to move positive or negative.

If you do this with multiple knobs for different parameters, each knob will need to be assigned a different global variable.

 

Steve Caldwell
Bome Q and A Moderator and
Independent Bome Consultant/Specialist
bome@sniz.biz

 

Marked as spam
Posted by (Q&A Forum: 42, Answers: 3296)
November 24, 2018 7:12 am