So loading the iPad layout for TouchOSC actually crashes TouchOSC - in fact it may cause the app to crash immediately upon loading. After a couple hours of troubleshooting, I discovered that there seems to be a problem with the parameter names “DevicePresetNext” and “DevicePresetPrev”. Changing the names to “PresetNext” and “PresetPrev” in the TouchOSC editor seemed to fix the problem; of course those names need to be changed in the Duplex TouchOSC_iPad xml Controlmap file as well. Hope this helps anyone else having the same problem I did!
Thanks.
Meanwhile, tested BCR knobs movement more with NRPN preset. Cannot syncronize values yet…If you turn the knob slowly, values stay in sync. But if you turn fast, renoise shows lesser angle. And if you turn value by mouse onscreen (does not matter fast or slow), BCR indicates all correctly (by ring dot). So, I suspect, what all is up to BCR device and its issues. Is anybody else has his own experience with BCR and Duplex in NRPN mode? Does it has knob values in sync perfectly?
P.S. Using Renoise on Mac (OS X El Capitan).
Meanwhile, tested BCR knobs movement more with NRPN preset. Cannot syncronize values yet…If you turn the knob slowly, values stay in sync. But if you turn fast, renoise shows lesser angle. And if you turn value by mouse onscreen (does not matter fast or slow), BCR indicates all correctly (by ring dot). So, I suspect, what all is up to BCR device and its issues. Is anybody else has his own experience with BCR and Duplex in NRPN mode? Does it has knob values in sync perfectly?
P.S. Using Renoise on Mac (OS X El Capitan).
Funny, I was just working with the BCR tonight, as I want to re-engineer this and some other aspects of Duplex. I’m suspecting the fact that Renoise sends out a response while you are turning (this is part of the new approach, to have bi-directional parameters that synchronize themselves less aggressively).
I wonder if you will have better luck with the absolutemode. It might be a better fit, at least I can’t remember why I chose R114 mode to begin with.
To test if this is really the case, I’d suggest editing a single parameter on the BCR (make it use the A 14 mode), and specify mode= "abs_14"for the corresponding parameter in the control-map. Would be curious to hear if that improves things 
Ok… Thanks (was out of sync a little with music last days). Will try it on my setup.
Also want to ask a question: there are some new Behringer devices came on market last year or two - the X-Touch series. It is a bit expensive, but not as expensive as Mackie MCU Pro. Do you plan to add it’s support. Can it possible to show info from renoise’s channels to it’s displays?
Funny, I was just working with the BCR tonight, as I want to re-engineer this and some other aspects of Duplex. I’m suspecting the fact that Renoise sends out a response while you are turning (this is part of the new approach, to have bi-directional parameters that synchronize themselves less aggressively).
I wonder if you will have better luck with the absolutemode. It might be a better fit, at least I can’t remember why I chose R114 mode to begin with.
To test if this is really the case, I’d suggest editing a single parameter on the BCR (make it use the A 14 mode), and specify mode= "abs_14"for the corresponding parameter in the control-map. Would be curious to hear if that improves things
Seems what it works for me…search speed values to find proper one (maybe 128-256 will be enough). Values are in sync now. Do not exactly understand what times ago top row of knobs (on 1st group) control channel volume, but now - it controls panning…
Values are in sync now
Cool, that’s good to hear.
I’m not sure about the panning though, Perhaps you are running a different configuration?
You can always change these things as you like, by modifying the right files.
Configuration:BCR2000_MixerEffect-NRPN.lua → says that panning is assigned to the group called"Encoders1"
Controlmap:BCR-2000-NRPN.xml → where the group is defined.
Here’s a nice guide on how those files are laid out:
https://forum.renoise.com/t/how-to-start-editing-duplex-files/30979
hi guys,
here is my first Duplex controller map … and my last one for Behringer’s CMD serie. I tried the CMD DC-1 but at the end, I’m not satisfied with the hardware …
… but I build the map for learning too … and maybe my work is useful for owners of other CMD controllers too, for building their own new map etc. B)
The map contains the Duplex modules Transport, Effects, StepSequencer, Navigator and TrackSelector
6748 CMD_DC-1.zip
In order to get all features of the map working (including an advanced Duplex step sequences), you need an update of some Duplex modules (applications) too. (More information in this thread.)
This updated versions are currently not a part of the official Duplex release and may contain bugs. use it at your own risk! 
6749 Applications_Updates_20160523-EDL.zip
cheers, Dax
6747 
here is my first Duplex controller map … and my last one for Behringer’s CMD serie. I tried the CMD DC-1 but at the end, I’m not satisfied with the hardware …
… but I build the map for learning too … and maybe my work is useful for owners of other CMD controllers too, for building their own new map etc. B)
Checked out the source, handsome work.
Very useful additions which definitelyshould be included.
Btw. I think it’s not too much “hacked” in the new StepSequencer application code … maybe a little bit, but I didn’t changed the old code. I only added some workarounds to get the new grid mode working.
Hey, I’m a new renoise user (I love it), and want to find a controller for it to get things even faster.
I was offered trade a monome 256, but I couldn’t be sure if I can get Duplex to work with 256 version.
Or maybe other solutions that I’m not aware of?
I don’t know if I can get anybody to help me with creating a custom tool.
So I would like to know if there’s anybody using 256 with renoise also
Ta-daa. A brand new version of Duplex (v1.01) for your consumption!
Check the first post in this topic for download:
https://forum.renoise.com/t/duplex-beta-versions/30625
It fixes a number of issues, brings new features (perhaps most importantly, high-res automation recording is now standard).
And it also represents my initiative to reduce the codebase by transitioning to cLib/xLib libraries where possible - this release represents the first step in that direction.
I have tested this as much as I could, but I would really appreciate if you could lend me a hand here.
The list ofknown issueshas shrunk to just 2. But I’m sure there are more lurking…
So basically - if you own one of the supported controllers, run some of the configurations - play around, and see if something breaks.
Also, there is some much improved documentation for the applications and Duplex itself.
Once we find that the release is solid, I’ll strip the debug information and release it on the tool page. Until then…
Enjoy!!
–
Changelog for this release:
- Core: Several classes have been replaced with their cLib/xLib counterparts.
- Core/Display: retain size of viewbuilder buttons when setting long text string
- Documentation: switched to a new format, github-flavored markdown.
- Added: Eran Dax Lonkers StepSequencer contributions + other features
- Added: Keyboard - HarmonicWrapped layout, tweaked configurations
- Added: High-res automation recording for Mixer, Effect, XYPad and Repeater apps.
- Fixed: Issue w/N.O.W.: Allow unmapped phrases (API5)
- Fixed: Issue w/N.O.W. (https://github.com/renoise/xrnx/issues/66)
- Fixed: Issue w/N.O.W. (https://github.com/renoise/xrnx/issues/56)
- Fixed: Issue w/TrackSelector (https://github.com/renoise/xrnx/issues/83)
- Fixed: Issue w/XYPad (https://github.com/renoise/xrnx/issues/55)
Nice!
- Added: High-res automation recording for Mixer, Effect, XYPad and Repeater apps.
But does this mean, Renoise will neverget proper highres recording natively? 
And something like:
- Renoise could get the possibility to record any slider, not only for right mouse button. So in context menu of any slider “enable recording” and “disable recording”, plus an additional “record automation” button next to the record button, which disables all recording. So you could also record any meta signals. So from the API, you would simply enable recording for a slider and let Renoise do the automation recording.
coll, it might finally be time to get my head round this… prospective gear I have includes:
Korg PadKontrol
Launchpad
Novation Remote SL
Stanton SCS3 (WEIRD Ribbon thing!)
@ffx: you’re referring to the tuned shortcuts, I guess?
There also is an “endless feedback” problem in Renoise’s current implementation of observing VST parameters. While writing automation, the automation values are sent back to the vst, so the vst parameter observer will trigger again, which writes again automation etc. etc. Stuck in an endless loop. This should be prevented internally. Also vst plugins may round the value, so the sent in value and sent back value will differ. It is not possible to filter this out by checking for same values. I would define the following problems/thoughts about it, that should be fixed (IMO):
Oh, I remember that we talked about this. The “xAutomation” approach I’m using now is simpler than it used to be - I ditched the “latch mode”, it now has only two modes: “punch in” and “interleave”.
But with plugins, indeed that particular thing (rounding) might still pose a problem, I dunno… I say, let’s investigate
coll, it might finally be time to get my head round this… prospective gear I have includes:
Korg PadKontrol
Launchpad
Novation Remote SL
Stanton SCS3 (WEIRD Ribbon thing!)
Launchpad is definitely plug and play. It has a lot of “configurations” ready to go.
And it would be awesome to (finally) get the PadKontrol into the family. I’ll revisit this thread from 2014:
https://forum.renoise.com/t/padkontrol-in-native-mode-for-duplex/41724
As for the Stanton and Remote SL, they were missing from thelist of controllers. I’m sure we can get something running. But I own a Novation Remote myself, the SL-MKII model, and it’s great quality (hardware) but the LED feedback via Automap/MIDI is unfortunately not 100% working. I even contacted Novation to let them know of the issue.
So I’m pretty sure that the first model fares equally well. Which means, great because you’ll most likely be able to record precise automation, but anything beyond that (bi-directional communication) is a bit unknown.
…
@ffx: why the smiley, it seems you are genuinely concerned?
You should know that MIDI notifiers are fired in the “realtime thread” and picked up by lua almost immediately. Of course, we are talking computers so nothing is ever completely realtime, but it’s pretty damn close.
We need to produce some measurements before we can talk about “accurate” timing, no?
Also, I was not aware that OSX should behave any different. Could you check that this is still the case? Like I mentioned, the implementation has changed.
I have a Mac too, so I can test this from here as well. But it’s a hassle because I would need to reinstall a bunch of software.
…
Well, if you’re not feeling like testing this thing, you can still throw me a bone or two.
Remember, it’s a different implementation now. I am aware that the previous version could screw up high-LPB automation - my bad.
Also, I was not aware of any difference between OSX and Windows. This is obviously important to know, as the API is supposed to work similarly across platforms.
Sounds like I need to boot my Mac up and run some tests after all.
Now, for the bone: can you give me an example of a plugin where you experience problems with rounding/feedback? Preferably a cross-platform, non-commercial one.
If I’m lucky I might be able to make some parameter feedback ** cue ugly teeth smiley 
**
Another beta , v1.02. Get it here
v1.02
- Core: replace OscClient with xOscClient
- Added: Detect Renoise OSC server on startup
- Added: Tool options dialog + clean up menu
- StepSequencer: Changed default options (always write, enable preview and note names)
- Updated documentation
Detecting OSC on startup is a good one: you’ll be a lot less likely to wonder why some features (Keyboard, forwarded MIDI messages) aren’t doing anything.
And a dedicated tool options dialog means that I could clean up the tool menu a bit.
Also, I found myself wondering why the newly upgraded step-sequencer didn’t write any notes - d’oh!
So those default options are now more intuitive - you can always configure it differently later on.
Yet another release, v1.03
Download:https://forum.renoise.com/t/duplex-beta-versions/30625
Guess this the first time that Duplex got two releases in one day
Also, the OSC server detection is now waiting a bit longer before it concludes that no server is available.
Don’t want the fix for a nuisance to become a nuisance in itself…
v1.03
Core: Improve performance by using table-based lookups where possible
Added: MMC transport control is now optional, can be enabled/disabled via options
Added: pitch-bend as an additional input method for the UISlider component
(this also fixes issue with Mackie Control: https://github.com/renoise/xrnx/issues/50)
Fixed: StepSequencer: error when pressing button in out-of-bounds area