Jump to content


Photo

Duplex/Applications/Effect: How to assign a button to a parameter

DuplexEffect lua midi applications

  • Please log in to reply
2 replies to this topic

#1 jrod420

jrod420

    New Member

  • Normal Members
  • Pip
  • 3 posts

Posted 12 March 2017 - 13:51

Hi,

 

I want to map some specific buttons on my midi-controller to some specific parameters of a plugin, using Duplex application "Effect". So far, I only saw examples, where a group of buttons is "dynamically" mapped  to plugins of the current selected track (I think it is called "paged" navigation). I would simply need a "static" mapping.

 

Is that possible at all?

If yes, do I just need to edit the lua script of my controller?

 

I have already looked at the tutorials and documentation but couldn't find the solution (I'm sorry if I overlooked it :unsure: ).

 

 

Cheers,

JRod



#2 danoise

danoise

    Probably More God or Borg Than Human Member

  • Renoise Team
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 6113 posts
  • Gender:Male
  • Interests:wildlife + urban trekking

Posted 12 March 2017 - 16:13

Hi JRod, 

 

I want to map some specific buttons on my midi-controller to some specific parameters of a plugin, using Duplex application "Effect". So far, I only saw examples, where a group of buttons is "dynamically" mapped  to plugins of the current selected track (I think it is called "paged" navigation). I would simply need a "static" mapping.

 

The short answer is no - static mappings is not how Duplex Effect is designed to work. 

Instead, it shows you stuff depending on the selected device and/or track.

 

My own workflow involves gathering devices in the master track where they can then be controlled. 

And sure, it's possible to add static mappings too. But first there is an important question that needs answering: "where should this mapping information be saved". 

I'd say that the song comments is a OK-ish place. And I've got code from another Duplex app that could be used for this purpose. 


Tracking with Stuff. API wishlist | Soundcloud


#3 jrod420

jrod420

    New Member

  • Normal Members
  • Pip
  • 3 posts

Posted 13 March 2017 - 13:47

Hi Danoise!

 

thank you very much for your reply and your time man!

 

And sure, it's possible to add static mappings too. But first there is an important question that needs answering: "where should this mapping information be saved". 

I'd say that the song comments is a OK-ish place. And I've got code from another Duplex app that could be used for this purpose. 

 

So, it should be possible to add the feature "static mapping" to Duplex, but up to now it is not available, right?

About the location of mapping information I cannot give advice as I'm not familiar with the functionality, yet. I fully trust you in that point ;)

 

I naively thought that I just can map a button X to the e.g. 4th parameter of 2nd plugin of first track. This would be static enough for me as I don't change the structure of the project. In this case, I would assume the mapping information simply in the lua-script of the controller. 

 

Alternatively, I could use native midi-mapping of Renoise. But Duplex' feature "pass unhandled midi messages to Renoise" seems to not work for me (I posted this issue here )
 


Edited by jrod420, 13 March 2017 - 13:53.






Also tagged with one or more of these keywords: DuplexEffect, lua, midi, applications