Strange fader values getting sent to Max/MSP

Anything related with the original Lemur Hardware.

Strange fader values getting sent to Max/MSP

Postby jfhallst » 29 Jan 2013 02:14

I'm sending fader info from the Lemur to Max/MSP (6.0). my fader addresses are set up as "/1/fader1", "/1/fader2", etc. with a data range of 0-1. When the data is received in Max addresses of "/Fader/z", "/Fader2/z" with values of 0 or 1 appear at intermittent intervals and the faders don't move smoothly. the z business almost always appears with a zero value when I take my finger off the slider.

Anyone have any idea what's up?
jfhallst
Newbie
 
Posts: 1
Joined: 13 Nov 2012 14:24

Re: Strange fader values getting sent to Max/MSP

Postby nick_liine » 27 Jan 2014 14:55

As you noticed, the default namespace is differs in Lemur from TouchOSC. You can set Custom OSC addresses for objects in Lemur. There are also some examples on how to force something similar to the TouchOSC format:
http://liine.net/en/community/user-library/view/152/

Bear in mind that the naming philosophy is inherently different in both apps.

Hope this helps,
Nick
nick_liine
Liine Staff
 
Posts: 337
Joined: 01 Oct 2010 11:06


Return to Legacy

Who is online

Users browsing this forum: No registered users and 1 guest

cron