The pad LEDs do light up now while using the mouse, but I still can’t get the hardware to send and receive proper messages. Pressing a pad turns off its LED but does not control pattern on/off anymore, but everything seems to function on the Duplex interface. The transport and mute buttons also turn off LEDs once the hardware button is pressed, until it is changed via the mouse, or a track is soloed and then unsoloed. Using the rotary dials does update the LEDs and navigate through patterns/tracks, but not in a way that makes any sense to me yet 
It seems strange that the pads stopped working to control the pattern matrix.
So, basically it can work in either absolute or relative mode, which makes sense for a LED based controller.
In relative mode, the QuNeo seem to be transmitting what Renoise refer to as “Relative bin offset” (see MIDI mappings),
However, endless rotaries are not supported in Duplex so we need to focus on the “location”, where the rotaries should transmit an absolute value.
Kazakore mentioned this thing about values starting from the top right corner. Could this have anything to do with it?
Also, try controlling some straight-forward parameter like volume, panning where it’s easier to tell what is going on
That is strange. I just checked, using a simple pure-data patch to emulate the QuNeo and the application responded just fine.
Have you tried enabling the MIDI-dump feature in Duplex, confirming that the messages being received by Renoise match the values we’d expect?
The lower four pads should send note messages with a numeric note value from 0, 2, 4 & 6 (in the QuNeo editor, that would be C-2, D-2, E-2 and F#-2
So, for instance when pressing the lower-left pad, the incoming message should be MIDI 90 0 79 (90 is note-on, 0 is note number and 79 velocity)
Really? The description I read (and tried to portray to you) I didn’t think sounded like that at all. But that could be due to a confusion by either myself or the user who posted on their forum. I’ll try and remember to take a MIDI Dump of using the rotaries in Relative mode some time soon to confirm…
Shame. How would you have going clockwise to take you to the last send and then back to Track1 then? Plus you will always get stuck at 0 or 127 
Is it just Duplex doesn’t support it or it’s hard to script correctly? Navigation with the rotaries is something I was considering coding (up/down with one and track or column with the other.)
The rotaries in the Lua API themselves don’t go further than the min and max value which are float values ranging from 0.0 to 1.0.
You could however scale offsets going from 0.001 to 0.999 to the range of 0 to 127 and whenever the value on the rotary turns 1.0, the rotary is put back to position 0.001 and when the rotary hits 0.0, it is changed to 0.999. (The object range is based on float values so there are acutally a lot of decimals that go behind the comma)
There are always tricks to make something turn “infinite”. It just depends on what scaling model you apply and what you actually use on the scale that you translate the numbers to.
It’s mostly a matter of representation. The viewbuilder API doesn’t have such a control for us to script, so it’s not possible to represent visually.
Once we have something like that, the standard modes (relative bin offset, etc.) would of course need to be supported.
Edit: OK, what vV says is correct - it’s not that bad a workaround to have a rotary which simply move slowly between min/max. I’ll see what I can come up with
Nice idea about column navigation, btw. A ColumnSelector to complement the TrackSelector ?
So0rry, for the initial paragraph, which you have responded to vV, I meant specifically within Duplex. I know there are lots of ways it could be done yourself within the API (although I am yet to do anything that actually uses a CC value myself) such as comparing against previously received number to know if it went up or down and then repeated 0s or 127s being treated the same as a decrement/increment (as long as the digital knob continues to send out min/max value on turning once it meets the end of the range.)
Although I do have to again admit I am hardly even a Duplex initiate and I am assuming Urbster1 was referring to control from within Duplex and not native when he was talking about the issues he had…
I went ahead with support for relative dials in Duplex,
it’s very beta and experimental so any feedback would be appreciated 
(download: see this post for a more recent version)
The feature is simple to use - apart from figuring out how to set up your controller (can’t help you there),
you need to add a “mode” attribute to a control-map parameter:
mode=“rel_7_signed” - Increase at [065 - 127], decrease at [001 - 063].
mode=“rel_7_signed2” - Increase at [001 - 063], decrease at [065 - 127].
mode=“rel_7_offset” - Increase at [065 - 127], decrease at [063 - 000].
mode=“rel_7_twos_comp” - Increase at [001 - 64], decrease at [127 - 065].
I’ve used the “rel_7_signed2” mode on my Remote SLMKII, seems to work flawlessly, but other devices/modes are untested.
Note also that this feature is only effective with 7bit MIDI controllers, so far.
–
@urbster1: So, perhaps one of these four modes will work for the QuNeo?
Check out the new QuNeo preset, btw. The only difference from the previous one is that I’ve enabled local LED feedback for the pads
@danoise, thanks, where should I find the new Quneo preset? I thought it was in the new version of Duplex but I may be missing it. I will have a go with it tonight.
Yes, the preset is located in the download itself - inside the /Controllers/QuNeo folder.
A bit puzzled about the way that pads seems to display stuff, but a simple MIDI dump to the console might reveal what is going on.
The same goes for the rotaries, there is no guarantee that the QuNeo is in fact using one of the four modes I’ve prepared 
This is Preset 10, which has the Rotaries as Relative and doesn’t have any Pressure or Note associated. Direction is CC6.
So a 1 for clockwise and a 7F for anticlockwise motion. (Seems reverse logic to me but at least it makes sense.
I got confused looking at the one with Note and Pressure on Preset1. Turns out the Note number was the same as the CC used for direction so I thought the Note Off was a zero value send to CC4 at first but it seems the same.
Cool, that sounds like “rel_7_twos_comp”. My modifications would most likely work then…
Here’s a new version - if you haven’t already done so, load the QuNeo preset before you start Duplex
EDIT: Attachment removed, go to this location for the latest beta
Almost there … soon, we can come up with some interesting device-configs 
Something up with the latest file. Doesn’t give the option to drop it onto Renoise.
Re-zipped it and it worked. Maybe you accidentally hit wrong compression type? Dinner’s ready now though 
Great, and those pads - are they working too?
Ah, yes I propable rar’ed instead of zipping … all good now.
Hey, it seems I was busier than I was expecting-- I finally downloaded the latest Duplex beta posted Oct 31 and made sure to overwrite the old preset. The pads respond just fine with LEDs but when I press them, nothing happens. Before, they would mute/unmute patterns in the matrix. It seems the rotary dials navigate patterns but it’s nearly impossible to tell where I am given that the pads won’t respond when pressed. The Duplex tooltip says “Press to toggle muted state, hold to focus this track/pattern” which works fine using the mouse, but the pads should be sending MIDI data to Duplex, and I am not sure why they stopped working. 
If I’m not mistaken, I re-enabled local LED feedback in that preset. You are sure that the LEDs does in fact respond to what is happening in Renoise -
for example, try to mute or unmute some matrix slots to see if the controller will reflect this change?
I would suggest that you map the dials to something more basic. Try to replace the device configuration with this -
it will replace the first dial (controlling the pattern-sequence) with one that will be able to control any Hydra device
(but you will need to add / bring focus to a hydra device before it does anything!!)
Click to view contents
–[[----------------------------------------------------------------------------
– Duplex.QuNeo
----------------------------------------------------------------------------]]–
– test of the QuNeo control-map
duplex_configurations:insert {
– configuration properties
name = “QuNeo”,
pinned = true,
– device properties
device = {
class_name = “QuNeo”,
display_name = “QuNeo”,
device_port_in = “none”,
device_port_out = “none”,
control_map = “Controllers/QuNeo/Controlmaps/QuNeo_default.xml”,
thumbnail = “Controllers/QuNeo/quneo.bmp”,
protocol = DEVICE_MIDI_PROTOCOL
},
applications = {
Mixer = {
mappings = {
levels = {
group_name = “VerticalFaders”,
},
panning = {
group_name = “HorizontalFaders”,
},
mute = {
group_name = “HorizontalArrowsLeft”
},
solo = {
group_name = “HorizontalArrowsRight”
},
master = {
group_name = “CentralFader”
},
},
options = {
pre_post = 2
},
},
Hydra = {
mappings = {
input_slider = {
group_name = “Encoders”,
index = 1,
},
},
},
Matrix = {
mappings = {
matrix = {
group_name = “Grid”,
},
–sequence = {
– group_name = “Encoders”,
– index = 1,
–},
track = {
group_name = “Encoders”,
index = 2,
},
},
},
Transport = {
mappings = {
start_playback = {
group_name = “Transport”,
index = 3,
},
stop_playback = {
group_name = “Transport”,
index = 2,
},
edit_mode = {
group_name = “Transport”,
index = 1,
},
block_loop = {
group_name = “AnythingButton”,
index = 1,
},
},
},
PatternSequence = {
mappings = {
display_next = {
group_name = “VerticalArrows1”,
index = 2,
},
display_previous = {
group_name = “VerticalArrows1”,
index = 1,
},
}
}
}
}
One way to investigate this would be to enable the MIDI dump feature from the Duplex tool menu, and then copy-paste the information here.
Kazakore has already been so kind as to share the information about sliders, but what exactly happens when a pad is pressed is still unknown.
there is a video and zip download of an Ableton configuration, with two presets, that may suggest some use cases…
(crossposted from post.monome.org)
looking around i saw a video from kmi “ableton under pressure”
the download of an example liveset they are using is at
http://files.keithmcmillen.com/downloads/quneo/QuNeo_AbletonUnderPressure_set.zip
the vst included in the zip to make meters doesn’t seem to like windows live 8.3.4 or the 64 bit beta, but the set still works and there are examples of strategies to be studied.
probably made on mac
New QuNeo software released.
That was actually a lie; at the time it was only an announcement of features. It has now actually been released 
Seems there are some changes to the way the LEDs are lit from external MIDI (IE from Renoise/Duplex) so there might be some minor modifications needed.
Sorry, my hard drive died so my rig was out of commission for a couple months. Needless to say everything’s fine, I have decided to pay my friend and keep this Quneo. Unfortunately I updated it to the latest firmware and it seems to have lost communication with Duplex, so perhaps the preset has changed or something else is amiss. I will take a peek around and see if I can figure out what is going wrong and report back if I fix it. If so, I wanted to post a video of what was and was not working from before so we can hopefully get those issues ironed out.