Is this a control-map for new (not yet supported) controller?
If so, you have to make new folder which is renamed to the controller’s name.
And put the control-map(.xml) and config file(.lua) into the folder.
Then put the folder into;
C:\Users\YourName\AppData\Roaming\Renoise\V2.6.1\Scripts\Tools\com.renoise.Duplex.xrnx\Duplex\Controllers
If the control-map is for a already supported controller, you should edit the controller’s config file.
For example, please open and see the buttom of the “Launchpad.lua” file.
There is a commented-out code already there.
It’s the config for the second device called “Launchpad (2)”.
Control-maps are not selectable as such - they are referenced by the device configuration, which are all specified in the [device].lua (like satobox explains).
The Launchpad is a good example of a device with different control-maps for different purposes. But actually, the commented-out section is for making a secondary device turn up under a different name. If you ever wanted to use two launchpads next to each other, this is an example of how to do it.
Nevermind I Tested it, I made a map for the Akai MPK49 (and maybe other models 2!), everything is working fine apart from the transport buttons.
they use MMC I recalled there was another topic somewhere about this. can someone give a hint? or should I leave them out?
Hmm, indeed MMC seems to be a problem.
I have an old KeyRig25 midi-key which can send MMC signals too, and I made a little control-map for it.
When I use both Duplex’s midi port and native Renoise’s midi port, the MMC signals seem to be disabled.
When I close Duplex’s midi port, MMC signals work fine again.
Btw, though maybe Dr. Drips already know this thing, there is a workaround in MPK49.
According to the MPK49 manual, it seems that you can change the MMC signals which are assigned to the transport buttons. So if you change them to MIDI-CC signals and assign Duplex’s Transport application to them, they will work maybe.
Anyway, I hope that there is a true solution for this common MMC problem.
I saw this also in the manual but I planned to make it work right out of the box with any ‘generic’ preset on the mpk49 (should also work with mpk61 and mpk88)to make it easy for users.
this would mean rhat i must include a preset for it to work.
thank you satobox for your reply.
However, it will be ideal if both can be used, since users must not edit their controller’s buttons manually as Dr. Drips said.
Currently, Renoise can handle MMC, so I think taht Duplex should just only bypass MMC sysex messages to Renoise (well, just a thought of an amateur though… ).
Dear Duplex team,
im working on M-16DX Controller Files for Duplex thanks to Satobox starter thread first things are working.
M-16Dx is a digital Mixer from edirol
Now i have following questions :
1st Track selection.
Is it possible to select a track directly via button ? I saw that it is possible to switch trough them with 2 buttons, but I want to switch directly to e.g Track 3 with CC#14|Ch3 and to Track 4 with CC#14|Ch4 and so on.
2nd Effects:
The mixer has EQ Encoders: for Hi Mid and Low.
Is it possible to make duplex load the “DSP Mixer EQ”-plugin for all channels automatically and assign their parameters directly to a CC ?
3rd : Solo switches
I want to map switches as solo switches which does work perfect for one button pressed.But if i press two of them together the result should 2 Tracks unmuted and the rest muted istead of only one solo channel. Any ideas ?
I hope the questions are clear
thanks for reading and
thanks in advance for help
best regards Max
Actually, this is not directly supported, but it has been suggested a number of times. I think I’ll make a really simple application that does exactly this - TrackSelector or something like that.
The Effect application is mostly designed to control existing effects. Have you tried to add the Mixer EQs first, and then use the application to control them afterwards?
As for assigning specific parameters to a specific control, this is something which is planned. Eventually, you’ll get a “effect dashboard” which contain all the favourite effects in that particular song (but we need to figure out how to save script data in songs first)
Haha, yes, actually that would make sense. Currently, any solo button which is pressed would turn off all other tracks by calling the internal solo() API method. This might change, as what you are describing sounds a bit more useful
1 Would be very nice if you implement such a thing!
2 I disagree a bit from my point of view for using existing Effects inside songs. If i wanted to use that i can use a song template with assigned CCs inside Renoise already.
Very handy (but hard to script) would be an Api-function called InsertFxOnDemand
Where options for this app is :
(CC or whatever assignment)
Tracknumber= (if not specified by RowIndex)
DSP Name (Item from List of Renoise Standard DSPs)
Then the Encoders could mapped to
Application Effects.DSP
mappings
DSP=“Filter”
Param1 =
group = “Encoder”
index=xy
track=3
And then a routine which checks wether Fx is already there or adds it into the DSP chain accordingly to Track or RowIndex
3 Looking forward to it !
Thanks for the answers i’m looking forward the next changes
For example, in the current layout for the APC40, I am worried whether the Device Selector part is really comfortable or not. Though now the device selector is set to 16 buttons there temporary, if there is the TrackSelector app, it’s better to set the direct track-selector to 8 buttons & the device-selector to 8 buttons, I think.
Also, I want to request to add the Effect device page navigator (2 buttons for controlling visible device page) to the Effect app.
Well, already there are many requests about Duplex though , since it’s a very unique approach for supporting external controller, I hope it will grow step by step. I think it will be one of the most strong point of Renoise.
Not least because you now joined the documentation efforts. I just discovered your “getting started” topic on writing a control-map.
Great stuff, this was something that was sorely lacking. Most of the info is probably a bit technical, so it’s nice to see a more friendly version
About the TrackSelector app: having direct access to specific tracks and a next/previous style control should cover everything?
Also please add the “Track Increment” option, like Matrix and Mixer apps.
Because Mixer, Matrix, and TrackSelector apps in the APC series should be set to do the same (page changing) behavior.
Sorry if this already was discussed — I use Launchpad and when I close Renoise, the pads stay shining. I have to disconnect Launchpad to turn them off. Is there a way to solve it?
Apart from this I can’t describe how much I love this magic combination — Renoise + Duplex + Launchpad. Pure win!
Hey I’m running the akward stage Akai MPD 26. Can anything be done with duplex? I’m not familiar with the tool to begin with and I tried just running it as MPD 32 but it doesn’t (seam) to recognise it.
Also, from what I could tell Duplex can’t mass trigger different patterns in the matrix. If that’s the way it is I’m not sure this is of any use to me… but I wanted to try getting some more capabilities out of my mapping so I thought I’d try and figure this out. I was really hoping I’d be able to trigger a horizontaly progressing triggering of pattern matrix blocks (say, a beat) while also being able to control the patterns horizontally.
No idea if this is even possible but I thought I’d ask. I know I could achieve a similar effect by running two instances of Renoise but I’ve noticed some glitchy stuff happening there when I do that. This is how I make my tracks rather than by tracking it out so I can’t really stand to tolerate that.
).
