Oh, I can replicate this issue on my nanoKONTROL2 too. I’ve misunderstood that it is the nanoK2’s dedicated issue. It should be fixed.
@danoise;
Below is the difference of the signals between Mackie-Control mode and CC mode. Simply these are the results when I pushed a Mute button twice. Could you tell me where I should edit??
(It seems that we need “Note-ON signal with 0 velocity” for turning off leds, maybe. )
So, the problem with the LED only applies when using the (note-based) Mackie Control mode, and not the common (CC-based) mode?
Yes, any incoming notes with a velocity of 0 is already interpreted as a note-off. I can’t remember if something similar is happening to outgoing communication, but I’ll check what can be done about it.
Yes, only when using the Mackie Control mode.
The LED which turned on once never turned off unless I extract USB plug. Changing config cannot turn off LEDs too.
I confirmed that turning on&off LEDs works in Ableton Live, with this Mackie Control mode.
Btw, this is the problem only about LED.
I can control Renoise correctly except the LED behavior.
Yes, of course the mackie control mode works with cubase, live and other application… I don’t how it works with software.
It’s seem it’s just duplex that don’t send the “off” message to hardware, so if you’re pressing button on hardware or in renoise leds should turn on or off.
The problem don’t make renoise unusable but it’s just annoying for live.
Which is something which should be fixed, obviously
As the lead dev of Duplex, I have been a bit on a time-crunch lately - but I’ll promise to look at it ASAP
It’s probably simple to fix, but it’s always more tricky when you don’t actually have the hardware…
Duplex 0.98b11 has arrived: download link has been updated, as well as SVN
New core classes: UIKey, UIKeyPressure, UIPitchBend, OscClient
New application: Keyboard (including various device-configs)
Release notification for applications
Event handlers now receive message as argument
New option for MidiDevices: “allow_zero_velocity_note_on”
The big news (apart from a large number of internal changes and additions) is the ability to trigger samples via the Keyboard application.
A lot more info on that one is arriving shortly, as a separate topic. Edit: here
If this is the case, could you check with the new release? I have made it an option to allow sending notes, having the feature turned on for the Mackie Control.
I’ve found the most stable and reliable way to use my monome with duplex is to use the monomeserial configuration in duplex and the Max 5 serialosc->monomeserial bridge patch. Of course not the most ideal solution, but it seems to work consistently.
I did a quick edit to the monome128_keyboard lua file to try it out on my 64 (I just took out all the pads on the right.) Seems to work great, thanks for your work!
Cool, the monome configuration is a bit on the simple side ATM.
I think the final version should be a little more like the launchpad, where you at least get to control volume and have one (or more) keyboard splits to work with?
Is there support for Novation Remote SL61 (version 1 not mk2? I see mk2; or is mk2 backwards compatible with v1 SL61?).
Nevermind I sorted this. It works backwards compat. I had to choose “User2” as automap target on SL61.
Wow, this is crazy. Renoise is working better with my hardware than Ableton.
Presonus FaderPort: works flawless
APC40: works 99%
Remote SL61: works flawless
This is truly a testament to the skill of the development team of renoise.
Massive props. You guys are my fucking heroes.
I able to get the FaderPort and APC40 working together in Live, but not consistently - it was buggy. The Automap in SL61 clobbered some other stuff too. Renoise actually works better than any others so far.
I feel a little bit spoiled having so much control, but the reason I have these devices is because I couldn’t get some to work in other hosts; StudioOne and FaderPort obviously are in harmony, but so is Renoise now.
You guys are making it extremely hard to justify using anything but Renoise. If I didn’t have the need for a piano roll and session -> arrange recording in live (and the follow actions), with some better audio track handling, I wouldn’t even use any of the other hosts I own.
I’m willing to test and help out with Renoise in any way I can with my hardware devices.
Also I have an iPad and can help test touchOSC or OSC or whatever you guys need.
A while back, I received some feedback that a few controls didn’t work in SL 25 mk1 (namely, buttons beneath the faders). But perhaps this is not an issue with your device, being a different model and all?
That would be rather awesome. TouchOSC on iPad is possible, but so far we’ve not made any configurations for it. It wouldn’t be hard to make, but for some reason the TouchOSC editor doesn’t come with the iPad templates (except one called “Mix 2 iPad”), and I would like to base any standard Duplex configuration around those (as they are accessible to Android users as well. For some reason, you can’t edit nor import TouchOSC templates to that platform).
Assuming that the iPad version of TouchOSC comes with a set of templates made specifically for that device, does anyone knows where it’s possible to pick up these files?
I am trying to add settings for the Korg M3 to Duplex 0.98. So far the code seems to be quite self-explanatory and with the Duplex manual, most questions are answered for me. But some are still in my mind:
Is it possible that Duplex auto-switches configurations for effect, mixer, transport and so on? I mean if I click on the “mixer” tab in Renoise, could duplex autoload the mixer config and if I click on the “pattern editor” tab, Duplex could load the “effect” config?
Or do I have to include all controls within one config then?
Is this actually possible?
I would like to use the M3’s drum pads for track muting in the mixer config. The pads transmit midi notes from c-1 to g-1 with velocity. How do I describe them then as toggle buttons in the controller map? I tried different types, without any result.
Is it possible to define custom settings for the Duplex “Device Settings” dialogue which transmit sysex values? So I could do some remote setup here.
I can see your point - an even closer integration with Renoise. But since each configuration can be made up from multiple individual applications, it’s not easy to decide if a given configuration is valid for a given view (mixer, pattern etc). We have no semantics to tell us this.
But I guess it could be set up manually, if the SwitchConfig application was expanded with these options:
Option: Sync config to active view
Enabled
Disabled
Option: Mixer view
Launch config #1
Launch config #2
Launch config #3
etc.
Option: Pattern view
Launch config #1
Launch config #2
Launch config #3
etc.
…and because “sync” really means “both ways”, it would also mean that activating a specific configuration should switch to a particular view in Renoise. Quite useful!!
Hmm… I have no problem using drum-pads as toggle buttons on my Remote SL, they are configured as type=“button” in the control-map. Would be quite strange if a drum-pad acted as a toggle-button on the hardware side… are you sure that you’ve described the correct note/pitch values in the control-map - can you see input from your device when you enable Duplex’ MIDI-dump feature?
Not as such, no, the device settings are pretty generic in nature. But tell me, are you looking for a way to set up your device per-configuration, or globally (for any configuration that deal with the M3)? Because, if it’s global then it’s quite easy to create a dedicated M3 “driver” which can contain sysex code - this is already done for several devices which require a specific command as they are initialized (e.g. the APC controllers).
danoise, my working let me try and understand. I have an older version, SL61, not the first RemoteSL, but the 2nd gen, SL61, not the mk2. The one in the middle
I can test for you. What is it specifically that is broken? The buttons don’t work, I guess I should have been more specific when I said works flawless I never use those buttons, only the knobs and the transport controls.
The way things are setup the APC40 works almost 99%, including the auto-magic 8 knob controllers on the focused DSP, faders, etc. The SL61 transport works, which is the main thing I was hoping for. The only thing that doesn’t work on that is the Loop button. The buttons under the faders and the knobs aren’t working. You mention loading a mk2.xml file, but I don’t know how to load this. I have Automap 4 installed though. Don’t know if this matters or not? The Faderport works as it should everywhere.
So I think maybe it is a bug, and I gave you false hope. Apologies for that. If you need help with the RemoteSL61 stuff I can try to help.
I have TouchOSC for iPad and the controller editor software too. You can make your own from scratch. I can send you these files if you need them. The files are TouchOSCEditor.exe, from touchosc-editor-1.2-win32.zip - TouchOSC Editor v1.2 Copyright (c) 2009-2010, RJ Fischer http://hexler.net
Does this help you? Let me know if I can be of more assistance. I can test/edit layouts if I am given good instructions. I’m still getting up to speed with the new stuff in 2.8 and learning lua/tool API stuff so have patience
I just realized I had to download one called LiveControl to use it with TouchOSC. (I am from Ableton land)
So yes you are right you probably know this all. If you want the LiveControl for reverse engineering let me know. It has a pdf doc, and the obvious layout files, etc.
Exactly, the row of buttons beneath the faders. It was mentioned that in the previous models, those buttons were not MIDI-mappable at all. I find that strange, but it’s possible. And if so, there’s nothing we can do about it really.
Can you see if Duplex is receiving any input when you press those buttons (enable the MIDI-dump feature and look in the console)?
Oh, and I have no idea why the loop button isn’t working. I am currently pimping the Remote configuration, so I’ll definitely look into this, and put some new features in there while we’re at it…
I did? The only file I can think of is the automap layout for the remote, it’s called Remote-SL-MKII.automap, and can be applied via the automap software.
Yeah, I have that as well but I don’t want to create new layouts, because Android users can’t use them. Instead I want to base the Duplex configs on the default set of templates, and so far I’ve not found anything but the “Mix2 iPad” template. But perhaps the iPad doesn’t even come with dedicated templates apart from that one?
It’s possible to make some awesome stuff with the editor, of course. Here’s a layout I did a while back:
I’ve created a voice-manager class for Duplex, and seems to work like a charm. No more stuck notes when using the Keyboard.
Also, I’ve added the keyboard application “here and there” (Remote pads, Launchpad, AKAI LPD8, monome…).
And it’s becoming just a matter of editing the configuration to support a device, so it seems the whole key/keyboard feature is getting there.
Hi danoise! after our talk in this topic: Midi On Multiple Renoise Instances
I have tried the triplestack midi-keyboard. besides that my problem with opening midi ports on the second Renoise instance isn’t solved with this, I don’t get any sound out of it.
this is what I do and see:
-Load an instument and checked if it makes sound
-load up duplex midi keyboard and set my midi ports up
now I can see the graphical keys correspond with what I press at my controller but it doesn’t sent it to the assigned or with ‘follow selection’ selected instrument.
I tried with a VSTi and with a sample. Am I missing something?
Most likely, it has to do with the OSC server in Renoise not being enabled:
Sorry, it’s not entirely obvious. Please check if this is the reason?
The final version of Keyboard will most likely remind you of this, the first time it is being launched.
)
