MIDI Button (note) to mouse click at various coordinates

Hi Steve

Thank you very much for quick response I think I haven’t been clear with my first question so let me explain what I try to do. I want to set 4 individual midi push buttons for DR to change between the scopes: parade, waveform, vectorscope and histogram so basically first click is always at the same coordinations but the second one for each midi button is not and this is where my problems start when I set the first button everything work perfect but when I set the second button the first one also does the coordinates of second one could you please support with this. thank you very much Rob

OK, I misunderstood your requirement. You want 4 buttons each to click on a different screen location. The following does this. Just modify

  1. The device alias for the input device you are using.
  2. The incoming triggers for translators 1.0 through 1.3
  3. The rules for the desired click coordinates in translator 1.0 through 1.3

I have them set to 100-100, 200-100,300-100, and 400-100

You should be able to capture the desired coordinates in the outgoing action if you don’t want to use the local variables pp and qq within the rules.

Midi-button-note-to-mouse click.bmtp (3.7 KB)

You can learn more about aliases from this tutorial.

I’m also moving this discussion to a new thread because it was different than the original requirement.

Steve Caldwell
Bome Customer Care


Also available for paid consulting services: bome@sniz.biz

Thank you but to change the scopes first you need to click to open the pop up menu and click again to select which scope you want to choose and the Timed-Mouse-Click-with on input is perfect for thistles say if I set coordinate for Parade it does work but then when I set second translator for waveform the Parade midi button does waveform too when the waveform is deactivated the parade work as set in first place. sorry for trouble

What are the coordinates you for the popup menu. Then the coordinates for each selection thereafter? Note that if the coordinates move on the screen, then we will be clicking on the wrong coordinates so they must be at a fixed location.

I can set up the translators to click on the coordinates of the popup and then with a delay click on the desired coordinate. What would you need to do to then get rid of the popup window. I could add that too.

Steve Caldwell
Bome Customer Care


Also available for paid consulting services: bome@sniz.biz

so when I click on popup menu and select the correct scope te popup menu disappears so that is not the problem

coordinates for the popup menu x=1760 y=758 then parade x=1760 y=784 waveform x=1760 y =804 vector scope x=1760 y=824 histogram x=1760 y=844 thank you so much

OK,

In this version I added the coordinates you wanted.

I then added translator 1.4 that does the popup.

In the rules, I call tranlator 1.4 using Perform. I then delay the output for the second click for ga milliseconds. You can change the default delay value ga in the rules of translator 1.2 and then restart the project for it to take effect. I set it to 500ms.

You can find out more about ‘Perform’ in this tutorial.

Midi-button-note-to-mouse clickw-popup.bmtp (4.5 KB)

Steve Caldwell
Bome Customer Care


Also available for paid consulting services: bome@sniz.biz

This is Amazing Steve Thank you Very Much The Best Customer Care I have ever experienced

1 Like

Midi-button-note-to-mouse clickw-popup.bmtp (4.5 KB)

MFT-Resolve-2020-12-04.bmtp (5.6 KB)

Hi Steve,

Can you please help to integrate this 2 to work together the Vision3_V1.2 is the file where I try to do it but I have the problem with when I stop turn the knob on MTF - Resolve_Encoder Preset it always reset the parameters to the starting position. thank you Rob

Vision3_V1.2.bmtp (27.3 KB)

Hi, Sorry integrating 3 different project examples into a single project is beyond the scope of free support.

I’m not entirely sure what your objective is here. The first example shows how you can switch presets and then drag mouse from a different position depending on incoming CC number

The second one show how you can press click down at a given screen location.

The third project seems to want to send keystrokes depending on a given cc input. The last preset looks like the beginning of what I suggestion for dealing with popup and then drag. I believe this is the project that you want to encorporate more functionality based on the first two examples but am not sure. Keep in mind, each example was stand-alone and did not consider the combined project requirements.

I suggest that if you want a complete solution you reach out to me via email for paid consulting services.

Steve Caldwell
Bome Customer Care


Also available for paid consulting services: bome@sniz.biz

Thank you for the explanation — that helps a lot.
I understand now that each of the examples was meant to work on its own, and not necessarily together.

My goal is just to combine those behaviours into one project, and I wasn’t expecting you to handle all of that through free support. I’m definitely happy to pay for consulting if that’s the best way forward.

Could you let me know how your paid service works and what your pricing looks like?
That way I can understand what to expect and we can see if it’s a good fit.

Thanks again for your time and for being willing to help.

Sure, send an email to the below email address.

Steve Caldwell
Bome Customer Care


Also available for paid consulting services: bome@sniz.biz