Roxor 4.2 and Steppa v0.26

We are pleased to announce that Roxor 4.2 and Steppa v0.26 are available on the downloads page.

Roxor 4.2 features:

  • Launching!  I think I’ve figured out all of framework problems I was having.
  • Auto-updates, and if not fully automatic, try “check for updates” in the application menu.

Steppa v0.26 features:

  • takes advantage of the /midinotenum1 – /midinotenum8 OSC messages that Roxor can emit… so for instance, in Roxor, there are what we call stepper controls labeled “Note number” and sub-labeled 1 through 8 as see highlighted in yellow in this image:Midi Note Number stepper controls in Roxor
  • Steppa will now take advantage of these controls and let you set the arbitrary midi note number to whatever these controls are set for.  This is awesome, because now you can really expand, for instance, which of the 25 instruments in Apple’s Logic Ultrabeat plugin you want to loop with in roxor+steppa:
    instruments_ultrabeat20090721

    Or instead of being stopped at instrument 8 in Propellerhead Reason’s Redrum drum module, you could push one or two channels out to address redrum’s 9th and 10th instrument slot by changing the midi note number controls up a couple of numbers.
    redrum_big

    And further research has shown that you easily use roxor+steppa to control synth and sampler modules in any Apple Mac OS X application that can receive and utilize midi notes…  some of which include PureData, Quartz Composer, Chuck, Live, Logic, Garageband, Motion (!)… the list goes on and on and on.

Big huge ups to Derek on implementing midinotenum!!  It’s awesome!

3 thoughts on “Roxor 4.2 and Steppa v0.26”

  1. I'm getting inconsistent patterns of behavior for roxor 4.2… I have several reports of it definitely launching without problems on leopard (10.5), and so far one report of it not launching on tiger (10.4) … I just checked the compilation rules, and it looks like I've got the target architecture set correctly (10.4) and the 10.5 features are turned off (garbage collection, etc.) so I'm not sure why, but so far it looks like 10.4 users are not having so much luck getting it to launch. If you've had success or no success launching, please let me know here.

  2. Aha, we've figured out what's going on here. I'm using the @property declaration method in Xcode with objective-c 2.0, which requires Leopard (mac os x 10.5) or higher… so time to start a “system requirements” section.

  3. Aha, we've figured out what's going on here. I'm using the @property declaration method in Xcode with objective-c 2.0, which requires Leopard (mac os x 10.5) or higher… so time to start a “system requirements” section.

Leave a Comment