First off......THANK YOU!!! This program is amazing and so needed.
I am trying to assign the buttons from the Contour Shuttle ProV2 to macros in Soundflow. The device comes up under HID as "Shuttle Pro #1" but when I try to record one of the buttons nothing happens - it doesn't recognize the button press. A workaround is to create a keyboard shortcut and then use the Shuttle macro software to assign the Shuttle button to that keystroke. Yes it works, but is a bit clunky when trying to syncronize macros in the cloud across my 2 rigs. It would require me to update those same assignments in the Shuttle software on each computer manually. Any way to get Soundflow to recognize each individual button on the Shuttle?
- Christian Scheuer @chrscheuer2020-04-18 22:13:59.454Z
Hi Jonathan :)
THANK YOU for the kind words :)@Fokke did we test the Contour Shuttle Pro last week at your place and did we get it working for you?
Christian Scheuer @chrscheuer2020-04-18 22:41:50.016Z
The immediate things I can think of are (specific for HID devices):
- First make sure no other Application has seized the device (for example, ControllerMate, Keyboard Maestro or a specific driver).
If one of these apps has seized/captured the device, SoundFlow won't get access.
We should be able to see that info if you send us your log - click this link to report the bug:
Please click here to send us the information we need
Fokke van Saane @Fokke
I tested the old shuttle pro here, although i took it apart and only used the buttons instead.
I also tested the Shuttle Xpress, the smaller one. SF was able to see all buttons and controllers.But yes; you should un-install the Contour Software, because it 'steals' the unit making it unavailable for SF.
- First make sure no other Application has seized the device (for example, ControllerMate, Keyboard Maestro or a specific driver).
- JIn reply toJonathan_Grossman⬆:Jonathan Grossman @Jonathan_Grossman
Thanks!
Yes, that worked. Now for the tricky part. How can I get SF to distinguish between a left scroll and a right scroll of the Shuttle jog wheel? As of now, I can get it to see the wheel is being turned, but it just registers as being triggered, but not recognizing the direction I am pushing it
Christian Scheuer @chrscheuer2020-04-20 08:42:00.839Z2020-04-20 10:28:18.343Z
Hi Jonathan.
It's likely due to that the device sends this as one message.
You might have luck by using
event.trigger.value
in your script to check if the value is negative or positive. Try logging it to see if you can see a difference:log(event.trigger.value);
This should show different values depending on the direction you move.
If they show the same for each direction, we'll have to take a closer look.- JJonathan Grossman @Jonathan_Grossman
That log trick is helpful. Yes, it is showing different values. Scrolling to the left, the numbers go down, to the right then numbers go up. Min value 1 max value 256. Looks like an infinite scroll so the numbers wrap around when they get to the min or max
Christian Scheuer @chrscheuer2020-04-20 20:18:41.958Z
Okay, since it's sending absolute numbers but actually is a relative/virtual thing, you need a little piece of code to track what was the last number so you get the delta:
if (globalState.lastShuttleValue !== undefined) { var delta = event.trigger.value - globalState.lastShuttleValue; if (delta < -127) delta = 255-delta; if (delta > 0) { //Moved right. Do something here log('Moved right'); } else if (delta < 0) { //Moved left. Do something here log('Moved left'); } } globalState.lastShuttleValue = event.trigger.value;
- JJonathan Grossman @Jonathan_Grossman
I tried your code using the following but it still only zooms in: UP ARROW
if (globalState.lastShuttleValue !== undefined) {
var delta = event.trigger.value - globalState.lastShuttleValue;
if (delta < -127) delta = 255-delta;if (delta > 0) { sf.keyboard.press({ keys: 'arrow up' }); log('Moved right'); } else if (delta < 0) { sf.keyboard.press({ keys: 'arrow down' }); log('Moved left'); }
}
globalState.lastShuttleValue = event.trigger.value;
- JJonathan Grossman @Jonathan_Grossman
And.....again.....had the key stroke named incorrectly.
Man you have the patience of a parent with octuplets! Thanks.
- JJonathan Grossman @Jonathan_Grossman
Works now.
Christian Scheuer @chrscheuer2020-04-21 11:00:23.828Z
Awesome, thanks for checking Jonathan!
Christian Scheuer @chrscheuer2020-04-21 11:01:07.142Z
You can see this for a reference on the correct key names:
https://forum.soundflow.org/-88/how-to-automate-the-keyboard