Page 1 of 2 12 LastLast
Results 1 to 10 of 17

Thread: Griffin PowerMate tool

  1. #1

    Griffin PowerMate tool

    Hi,

    Here is a little tool to use the Griffin PowerMate with any OSC enabled application.
    The attached zip contain an executable tool that can be double clicked (it will open a Terminal window), and an example Osculator file.

    When the tool is launched, it searches for a PowerMate. I have not installed the drivers, so I can't tell for sure if there is no side effect with the software provided by Griffin, but I guess it should be ok. If there are some strange interactions, I would recommend to either uninstall the Griffin software or disable it there is a way to do so.

    Right now, only one PowerMate can be used at a time.

    The tool sends OSC messages to port 8000, which is the default input port of OSCulator.
    The sent messages are as follows :

    • /powermate/button
      A message with one float argument (0 or 1), that gives the state of the button. 0 is released, 1 is pressed.
    • /powermate/button/long
      A message with no argument telling if the press on the button was a long press (600 ms).
    • /powermate/button/double
      A message with no argument telling if the button has been double clicked in a short time (200 ms).
    • /powermate/rotation
      The current rotation. It can go indefinitely in the positive of the negative direction. The message has one float argument that starts at value 0. 1 represents one full rotation in the clockwise direction, 2 two full rotations, and so on. -1 is one full rotation in anti-clockwise direction.
    • /powermate/rotation/bounded
      The current rotation but stops at the [-1 1] bounds. The initial value is 0.
      Note: I was wondering if I should not rather make it start at 0.5 and limit the bounds at [0 1]
    • /powermate/rotation/cyclic
      The current rotation, but wraps around [0 1], that is, when a full turn is done, the value wraps at 0 again.
    • /powermate/rotation/increment
      No argument. Sent every time the value increases.
    • /powermate/rotation/decrement
      No argument. Sent every time the value decreases.
    The tool listens for OSC message on port 7999.
    It reacts to the following OSC messages:

    • /powermate/rotation/reset
      Resets the /powermate/rotation message to its initial value (0).
      No argument.
    • /powermate/led
      Changes the led brightness.
      One float argument between 0 and 1. A value of 0 means that the led is turned off, and a value of 1 means full brightness.
    Attached Files Attached Files
    Last edited by camille; 07-14-2011 at 01:33 AM.

  2. #2
    Hi there,
    Very nice tool so far. I'm wondering, is it possible to get this so that the increment/decrement can be run the entire time? Or can we have another event such as "wheel is incrementing" and "wheel is decrementing"? Problem I'm having is that Applescripts and such will only be run on the initial increment/decrement. If you don't stop, or move very quickly, the script is run just once, and you're left spinning the dial without any effect.

    Thanks

  3. #3
    Hi!

    Note that in OSCulator, AppleScripts are triggered once and are supposed to be short lived events. I don't think that even a change to the powermate tool would help you solve this problem. Also AppleScripts are rather slow and long to execute, whereas the PowerMate events are fast in comparison, which means that the OS could certainly decide not to execute an AppleScript at a given moment.

    Maybe a solution would be to add an argument that indicates the rotation direction to the /powermate/rotation message, so that you can trigger the AppleScript but only when the direction changes. Do you think it would work for you?


    Best,
    Cam

  4. #4
    Cam,

    Thanks much for the reply. I think that this would be useful, though not necessarily for my case.

    Perhaps I need to study a bit more about how Osculator works. I was just making a quick volume-knob which didn't use Griffin's driver. However, it seems like there are much faster ways to do so, without Applescript.

    Thanks.

  5. #5
    Camille,

    Is it also possible to connect multiple powermates?

    Best, Sam

  6. #6
    I'm very curious about this. I recently purchased a PowerMate Bluetooth and am looking for a way to get MIDI CC out of it. Should this work with the bluetooth version?

  7. #7
    Hi Naenyn,

    I don't know if this the PowerMate tool has been tested successfully with a Bluetooth PowerMate.
    This tool is free, would you like to try?

    Camille

  8. #8
    I'd be happy to try it once I receive it this week. =)

    I'm assuming it'd work the same way as the USB version...

    Does the USB version stop sending messages when the max value is achieved? Or does it loop back around to zero?

  9. #9
    Does the USB version stop sending messages when the max value is achieved? Or does it loop back around to zero?
    There is a different message for both cases, look at the dictionary in the first post.

  10. #10
    I am trying it out on mac os 10.9 with latest osculator (2.13.2) version and it is not working. The scripts is executing ok but I am getting no response in osculator. Any hints perhaps ? I tried running the executable as root but that didn't make a difference.

Page 1 of 2 12 LastLast

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •