Duplex: Apc40/20 Layout Suggestion

I’ll try it out Sato.

Here’s some more info I dug up:
Using ableton to turn off all lights = Dumb Mode, You only have 1 (Bank/Template)
Turning on APC40 and Connecting straight to Traktor = Regular Mode, 8 (Bank/Templates)

After trying your instructions, I had no progress. Managed to get the scripting-thingy up and running, but the CC’s didn’t change. :(

Wooooh, I’m so sorry for that, DoubleDeep. :(

Then, it seems that we cannot use APC40’s bank change function in Renoise.
I’m sorry to let you waste your precious time.

Anyway, I’ll remake the APC40 map because there are some what I understood this time.

Really thanks!! :)

Not to worry Sato, my time isn’t all that precious. ;) Too bad about the banks tho!
-Looking forward to seeing your new map!

I updated the current state on the first post.

About APC40:
It should work with so-called “US-version”.
If possible, I don’t want to make another version (Asia version) since I want to avoid troublesome maintenance.
I think it can be supported by updating APC40 itself, maybe.
Though I’ll make it if surely required. ;)

Well, we cannot use the Bank change function of APC40’s knobs though, I think it’s not a big problem.
If Duplex and Renoise evolve more, the function similar to it (or even more convenient one) will be added.

Please report if there is a part which does not work properly.

Thanks Satobox!

-The matrix-config works great and fixed the issues I was having with the previous version. I’d like to see one small feature on it tho: The ability to scroll through/select next and previous track with either the Cue Level knob, or the two unsigned buttons on the Activator-row. And perhaps next/previos Track DSP aswell.

-I’m not sure that the XYPad-config is working, as nothing happens when I press any of the Clip Launch-buttons.

-The Grid Pie-config crashes Duplex upon launch.
Edit: On 2nd try it ran OK.

I’m really excited to see how those two new configs will evolve, and I also hope a stepsequencer will be integrated. I’d love it if the knobs-section of the apc40 had other roles in these new configs, as I’ve got 2 apc40s and would love to use them both for different roles in Renoise. I can’t tell you how to configure them tho, as it’s only wishfull thinking! ;)

Have a lovely Christmas! :walkman:

The Cue Level knob is a relative knob which is not supported in Duplex yet, so let’s wait until it will be ready.
Well then, which do you like, setting it to 3rd&4th buttons on the Activator-row, or 7th&8th buttons under the Device Control knobs??

You need to set Renoise’s *XY Pad Device to anywhere, then you can see the cursor point on the Clip Launch-Grid.
See this thread in detail.

Hmm, if such a crash happens frequently, I’ll ask Danoise to check it. Any error message appaered??

I think that the StepSeq app needs to be improved still. StepSeq config can be made even the present conditions, but it may not be convenient enough. Cie’s LaunchPad sequencer or mxb’s padKONTROL sequencer are much better, I think. Let’s wait when it will be evolved a bit more.

Wooow APC80!! ;)
Well, for giving various roll to knobs, I’d suggested such a 8-knobs device.
Also, we can make “Notes On Wheels” config. It may be interesting indeed.

Btw, you can also edit config files by yourself. Although it may look difficultly, in fact, I have only combined some parts which already be in Duplex. When you are free, you had better read this. B)

I’m sorry Satobox, it seems I missed the fact that I could allready select next/prev Track DSP with the 3rd and 4th buttons under Device Control (7th and 8th are used for metronome and song-follow modes). Let’s use the buttons on the Activator row for next/prev Track then?

I’ll try to grab a screenshot of the error message, if it shows up again. And sorry again for being too lazy and not reading the documentation!

Haha, no sorry at all and I’ve updated the APC40 file again.

Merry Christmas!! :D

Hey danoise, I have 1 question about XYPad app.

I tried to make a new config for APC20 & 40, which have 2 XYPad and 1 Repeater like this image:
(Also I updated the config files in the first post)

3727 XY_Repeater_config.png

When I push a glid button on the XYPad area (though it’s very small area “3 X 3” ;) ), the glid button isn’t lit except the left bottom button. I think that this is because I set both “XY_grid” and “X, Y_sliders” at the same time in this config.
I can understand that the grid button isn’t lit while I control XYPad by sliders, but when I push the glid button, I want the button to be lit.

The Repeater app works like I described, even the Free value mode (the glid button is lit when I push the button).

Btw, Ableton’s “Push” seems great. It’s a ultimate controller. :rolleyes:

Yes, I downloaded your files and it’s the same here. I’ll look into it …

We should those configurations into the next version, right? They are quite cool :slight_smile:

Yeah, thanks. I’m glad too. :D

Yeah, basically this is the problem - there is only one “actual” XYPad in Renoise, but this setup is trying to control it using two different approaches.
And because each one uses a different value-range, the error arises …

I guess you did read the instruction, it’s mentioned that you need choose a specific input method…buttons, slider, etc.

However, I would like to make this solution more flexible, but I would need to change some stuff pretty deep inside the Duplex framework.
This wouldn’t be a problem if it wasn’t because I currently have no access to a device running TouchOSC, a pretty important controller not to break.

So, for now you simply have to stick with a single method for controlling those XYpads - either the grid, or sliders/knobs :slight_smile:

EDIT: I just released a version including your BPM control modifications B)

Ah, ok I see.

But I want to leave the config file in this thread, since actually the config works fine as it is. To be lit or not is not a big problem. If a APC user read here and see the image above, he can understand it easily, I think.
(though I’ll remake it if I think of a layout better than it. ;) )

Btw, please include the new Mackie Control config (with panning knob support) too in the next update. It’s more commonly used config than APC.

oh man, i’m having some issues getting my apc20 working properly using duplex. all my tabs just play notes, as if the device is in “note mode”. in fact, note mode is highlighted when it first turns on. i’m not able to turn it off though.

any help would be greatly appreciated.

here is my output from terminal. it looks like there’s a bunch of stuff being sent to the device on initialization. then, the bottom “receives” are the top 4 pads on my apc20.

MidiDevice: Akai APC20 send MIDI 80 34 0
MidiDevice: Akai APC20 send MIDI 81 34 0
MidiDevice: Akai APC20 send MIDI 82 34 0
MidiDevice: Akai APC20 send MIDI 83 34 0
MidiDevice: Akai APC20 send MIDI 84 34 0
MidiDevice: Akai APC20 send MIDI 85 34 0
MidiDevice: Akai APC20 send MIDI 86 34 0
MidiDevice: Akai APC20 send MIDI 87 34 0
MidiDevice: Akai APC20 send MIDI 80 34 0
MidiDevice: Akai APC20 send MIDI B0 2F 6C
MidiDevice: Akai APC20 send MIDI 97 32 7F
MidiDevice: Akai APC20 send MIDI 86 32 0
MidiDevice: Akai APC20 send MIDI B0 7 59
MidiDevice: Akai APC20 send MIDI B1 7 59
MidiDevice: Akai APC20 send MIDI B2 7 59
MidiDevice: Akai APC20 send MIDI B3 7 59
MidiDevice: Akai APC20 send MIDI B4 7 59
MidiDevice: Akai APC20 send MIDI B5 7 59
MidiDevice: Akai APC20 send MIDI B6 7 59
MidiDevice: Akai APC20 send MIDI B7 7 59
MidiDevice: Akai APC20 send MIDI 80 30 0
MidiDevice: Akai APC20 send MIDI 81 30 0
MidiDevice: Akai APC20 send MIDI 82 30 0
MidiDevice: Akai APC20 send MIDI 83 30 0
MidiDevice: Akai APC20 send MIDI 84 30 0
MidiDevice: Akai APC20 send MIDI 85 30 0
MidiDevice: Akai APC20 send MIDI 86 30 0
MidiDevice: Akai APC20 send MIDI 87 30 0
MidiDevice: Akai APC20 send MIDI 80 31 0
MidiDevice: Akai APC20 send MIDI 81 31 0
MidiDevice: Akai APC20 send MIDI 82 31 0
MidiDevice: Akai APC20 send MIDI 83 31 0
MidiDevice: Akai APC20 send MIDI 84 31 0
MidiDevice: Akai APC20 send MIDI 85 31 0
MidiDevice: Akai APC20 send MIDI 86 31 0
MidiDevice: Akai APC20 send MIDI 87 31 0
MidiDevice: Akai APC20 send MIDI B0 E 59
MidiDevice: Akai APC20 send MIDI 90 50 7F
MidiDevice: Akai APC20 send MIDI 86 33 0
MidiDevice: Akai APC20 send MIDI 87 33 0
MidiDevice: Akai APC20 send MIDI 84 33 0
MidiDevice: Akai APC20 send MIDI 85 33 0
MidiDevice: Akai APC20 send MIDI 80 35 0
MidiDevice: Akai APC20 send MIDI 80 36 0
MidiDevice: Akai APC20 send MIDI 80 37 0
MidiDevice: Akai APC20 send MIDI 80 38 0
MidiDevice: Akai APC20 send MIDI 80 39 0
MidiDevice: Akai APC20 send MIDI 81 35 0
MidiDevice: Akai APC20 send MIDI 81 36 0
MidiDevice: Akai APC20 send MIDI 81 37 0
MidiDevice: Akai APC20 send MIDI 81 38 0
MidiDevice: Akai APC20 send MIDI 81 39 0
MidiDevice: Akai APC20 send MIDI 82 35 0
MidiDevice: Akai APC20 send MIDI 82 36 0
MidiDevice: Akai APC20 send MIDI 82 37 0
MidiDevice: Akai APC20 send MIDI 82 38 0
MidiDevice: Akai APC20 send MIDI 82 39 0
MidiDevice: Akai APC20 send MIDI 83 35 0
MidiDevice: Akai APC20 send MIDI 83 36 0
MidiDevice: Akai APC20 send MIDI 83 37 0
MidiDevice: Akai APC20 send MIDI 83 38 0
MidiDevice: Akai APC20 send MIDI 83 39 0
MidiDevice: Akai APC20 send MIDI 84 35 0
MidiDevice: Akai APC20 send MIDI 84 36 0
MidiDevice: Akai APC20 send MIDI 84 37 0
MidiDevice: Akai APC20 send MIDI 84 38 0
MidiDevice: Akai APC20 send MIDI 82 39 0
MidiDevice: Akai APC20 send MIDI 83 35 0
MidiDevice: Akai APC20 send MIDI 83 36 0
MidiDevice: Akai APC20 send MIDI 83 37 0
MidiDevice: Akai APC20 send MIDI 83 38 0
MidiDevice: Akai APC20 send MIDI 83 39 0
MidiDevice: Akai APC20 send MIDI 84 35 0
MidiDevice: Akai APC20 send MIDI 84 36 0
MidiDevice: Akai APC20 send MIDI 84 37 0
MidiDevice: Akai APC20 send MIDI 84 38 0
MidiDevice: Akai APC20 send MIDI 84 39 0
MidiDevice: Akai APC20 send MIDI 85 35 0
MidiDevice: Akai APC20 send MIDI 85 36 0
MidiDevice: Akai APC20 send MIDI 85 37 0
MidiDevice: Akai APC20 send MIDI 85 38 0
MidiDevice: Akai APC20 send MIDI 85 39 0
MidiDevice: Akai APC20 send MIDI 86 35 0
MidiDevice: Akai APC20 send MIDI 86 36 0
MidiDevice: Akai APC20 send MIDI 86 37 0
MidiDevice: Akai APC20 send MIDI 86 38 0
MidiDevice: Akai APC20 send MIDI 86 39 0
MidiDevice: Akai APC20 send MIDI 87 35 0
MidiDevice: Akai APC20 send MIDI 87 36 0
MidiDevice: Akai APC20 send MIDI 87 37 0
MidiDevice: Akai APC20 send MIDI 87 38 0
MidiDevice: Akai APC20 send MIDI 87 39 0
MidiDevice: Akai APC20 send MIDI 81 33 0
MidiDevice: Akai APC20 send MIDI 80 33 0
MidiDevice: Akai APC20 send MIDI 80 32 0
MidiDevice: Akai APC20 send MIDI 82 33 0
MidiDevice: Akai APC20 send MIDI 81 32 0
MidiDevice: Akai APC20 send MIDI 83 33 0
MidiDevice: Akai APC20 send MIDI 82 32 0
MidiDevice: Akai APC20 send MIDI 90 34 7F
MidiDevice: Akai APC20 received MIDI 90 35 7F
MidiDevice: Akai APC20 received MIDI 80 35 7F
MidiDevice: Akai APC20 received MIDI 91 35 7F
MidiDevice: Akai APC20 received MIDI 81 35 7F
MidiDevice: Akai APC20 received MIDI 92 35 7F
MidiDevice: Akai APC20 received MIDI 82 35 7F
MidiDevice: Akai APC20 received MIDI 93 35 7F
MidiDevice: Akai APC20 received MIDI 83 35 7F

Ahh, no no. I think your output data is normal, it’s not in “note mode” (As far as you use Duplex, APC20 never will be the “note mode”, I think).

If you hear notes when you hit every CLIP LAUNCH buttons, probably you have set APC20 on the Renoise’s Preferences panel as a midi device. Please don’t set APC20 as a Renoise’s native midi device. It’s enough if you set midi i/o port in Duplex only.

I set my Renoise Preference midi device to none, have it set in Duplex alone. I’m seeing data in the console. But nothing is happening at all. None of the faders move the faders in the Duplex browser, navigation doesn’t work, nothing.

ug sorry… i didn’t click run… shameful

You mean this or is it sarcastic?

No sarcastic at all. Maybe Rolling Eyes emoticon might give you misunderstanding though, I simply was impressed to see their movie on that day.
Well, I’m not going to buy it though (it’s expensive for me and I don’t need Live ;)/> ).

Hey guys I’ve been able to get my apc20 working well in GripPie mode, but in Matrix mode the page left and page right buttons aren’t working. Is this a known issue?

Ohhh thanks. Indeed, I have been overlooking it. :(
It seems that the “page” mapping of the Mixer app was changed a bit.

Please change like this;

Duplex/Controllers/APC20/Configurations/MatrixNavigatorTransportMixer.lua

line:112

Wrong

  
 page = {  
 group_name = "Transport",  
 index = 5,  
 },  
 },  
  

Correct

  
 prev_page = {  
 group_name = "Transport",  
 index = 5,  
 },  
 next_page = {  
 group_name = "Transport",  
 index = 6,  
 },  
 },