Open lossius opened 10 years ago
is having a @range attribute for j.remote wouldn't be more powerful than adding a new dataspace ? what is the use case that implies to send "60 MIDI" or "-25 Max4Live" to the panning parameter ?
j.balance~ and the other panning-related externals expect left-right position to be in the snorm (-1, 1) range, while live.dial in Pan mode provides values in the -50, 50 range. Considering that it is also very common to describe panning using MIDI values (with mapping that is described in the MMA MIDI specification) it seems sensible to make this a dataspace.
I would not generally want j.remote to have an [AT]range, as range-handling should be the responsibility of the model, not the view. If range is to be limited in a view for practical reasons, that could be done using the widgets.
PS: Please remember that whenever we use the @ sign in the issue tracker, Github interpretes it as the name of some registered developer, and they get mail notifications that they are probably not interested in.
sounds like a useful dataspace to me. I would indicate in the dataspace name that this panning is meant for stereo, not surround panning in general.
@Nilson : Do you have a good suggestion for what the dataspace should be called then?
I'm thinking that it might be useful to add a panning dataspace. So far I can see it having three
MIDI: 0 - 127, 64 = center Max4Live: -50 - 50, 0 = center snorm: -1, 1 0 = center norm: 0, 1 0.5 = center
Any thoughts?