Thanks man! I’m curious, there are many way to use this thing, do you care to tell how you’re using it?
Press and hold would seem reasonable, yes. Let me just put that one on the TODO list…
The Monome? I’ve mostly used it with MolarVSTi, which is kinda a step sequencer/clip trigger combined with a sample cutter/live looper.
Great!
I’m seriously considering to use Renoise for my live setup. 
Yes, surely your contribution will become part of the next release. I’ve been on a bit of a time crunch lately, otherwise it would already be out there:-)
Hey, is there any support for the akai mpk25?
cheers
@Rootmitten: no, not as of yet. But several of the MPK25’s siblings are supported, so I’d say that it shouldn’t be too hard to support.
Look at the existing MPK49 device (Duplex/Controllers/Akai-MPK49), and you can see how it could be done?
i postet this one in tips and tricks:
and wanted to ask if something like this could be possible with the duplex or as a XRNX Tool
this would be a great tool i think, but i have absolutely nothing to do with lua scripting - it was just an idea because i like that tool but it only works with Synaptics touchpad and it is a bit tricky to use it as a standalone application, would be great to use for every renoise user
peace
Ps: maybe this fits also or better to ideas & suggestions - than to duplex than put it there
Can you commit your changes to SVN please?
I’ve got a disabled Duplex that I can not enable because the one in the repo is API 1.0
It’s much easier for me, and I’m assuming all SVN users, to roll back on a timestamp than it is to arse with a downloadable conflicting version.
In fact, it’s kind of wierd to me that you aren’t committing the changes. IMHO it’s deprecated.
Just commit it as you go, pretty please? It’s SVN. Better broken than stale.
I will simply publish the beta as it is tonight, because I’ve not had time to work on Duplex for the past couple of months. This is the reason the SVN has not gotten an update since the 2.7 - I couldn’t release Duplex before that, since it’s using API features which are unique to the 2.0 API.
Also, I’m a bit in doubt as to the best way to release the files in the future. Since Duplex is supposed to support every version of Renoise from 2.6+ and on, I’m maintaining multiple manifest files for this purpose.
But then I guess anyone who’s using the SVN (a.k.a. “bleeding edge” files), the standard practice would be to support the most recently released stable version. So, this means there would never be any Duplex updates on SVN while alpha, beta testing.
I don’t think anyone said you had to support multiple version of Renoise? IMHO let the 2.6 version rot in deprecated heaven. Same for future versions. Seems like an exercise in masochism?
For SVN, you make some valid points but that’s not how I remember it. The Lua API was not touched in the alpha testing until very last thing. The 2.0 API version bump and the beta were a few days apart. I also remember committing as soon as things were in beta and so did many others, so SVN for “stable” is questionable.
As an aside, is anyone gonna do a Faderfox LV3 template? Pretty please? 
Cheers.
Ping pa ding ding dong put a donk dong yo ding dong yo…
SVN update?
Suggestion: Add the Live Looper script by IT-Alien to the Recorder.
Hi all,
I am quite a new -happy- user of Renoise, I have bought a Ohm64 controller last month and thus I’m using Duplex which is a great tool.
And I wanted to switch configuration directly from my device and so I’ve discovered Lua 2 weeks ago: I made some corrections in Duplex code because Midi mapping didn’t work for me and I have also created a new Application called SwitchConfiguration.
If some guys are interested, I put in this reply 2 .zip files containing these modification made from Duplex 0.97:
- Duplex_MidiMapping_Correction.zip contains the correction for Midi mapping for switching configuration
- Duplex_SwitchConfiguration_Application.zip contains the new Application named SwitchConfiguration and an example of configurations with Ohm64 device (it also contains the correction for Midi mapping)
Important Note: to create the SwitchApplication, I needed to modify the __init signature of Application objects. Indeed, I pass a reference of Browser instance to BrowserProcess and then a reference of BrowserProcess to Application instances. Thus I have modified all existing applications by changing their __init constructor… hum.
Quick installation instructions:
- Install Duplex 0.97
- Download one of the attached file (or both) and unzip somewhere on your hard drive
- Replace the files located into the Duplex folder by the unzipped files
- Start Renoise and launch by selecting Tools > Duplex > Ohm64Switch
Hope it can help…
Best Regards,
Welcome to the forums Sham, great first post 
Like Jonas said, great first post!!
Wow, you have been modifying Duplex at the absolute ‘core’ level to pull this off. IMHO the Browser class is the most complex part, but perhaps you think otherwise now.
Can’t wait to check it out … a lot of existing device configurations could benefit from this
Thank you for your comments and glad to see that these few lines of code can be useful.
I usually use Python in my daily work and Lua syntax is not so far.
I have some other ideas for Duplex and I hope I will have the time to implement them. For instance, I would like to add a new feature in XML parser to unite functionally speaking e.g. no more need to use 2 Mixers in a configuration and thus offset could disappear. (could be nice for Effects also)
I will keep you up to date.
Thx again !
Best Regards,
Yeah, the offset is a bit of a hack really. At the time, I was helping another Ohm64 user to get the device running properly - before that, Ohm64 had very limited support. At the time, it seemed like a simple workaround, but it’s really a hackish solution that you’d have to repeat in every other application. The framework could deal with this sort of stuff, that’s really what it’s there for.
Btw: The MIDI mapping fix and the switching config app both look good. Thanks!!
Huge bump, since there’s a new version (0.98) out now!!
New features include sham’s modifications (SwitchConfiguration), and the massive new Notes On Wheels performance sequencer.
First post has been updated with download and descriptions. Enjoy!!
@nightmorph: Honestly I haven’t yet tried the newer protocol, when obviously I should. Thanks for the reminder 
Just discovered that the newest version of automap will do something strange to the remote SL25, and perhaps other controllers from novation: under some circumstances, the MIDI message into the controller is ignored - causing glitchy behavious like toggle-mode buttons that doesn’t display the correct state, and perhaps more strange behavior.
Seems like it’s an issue with the automap software because I tried downgrading to automap 3.5, and that version works fine
So basically, if you have novation gear and want to use Duplex, stick with automap 3.5 until this issue is sorted out.
Hello,
First of all I would like to thank for including my app to the new release of Duplex !
I didn’t have many time these last days to try to add some features to Duplex. Moreover my Ohm64 has a problem and I need to send it back for repair.
To replace it in the meantime, I have received an APC40 today And I have noticed that the mapping of APC40 was not corrected if I refer to a previous thread and to the post of Satobox (Need Help Setting Up Duplex And Apc40).
So in attachment you can find the APC40 XML mapping file corrected.
Best Regards,
PS: hum… it’s pity that the XRNX project use SVN as versioning tool. I really like SVN but I think that Git is far more better. (it’s just a thought from a developer)