Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
User Manual V2.0 Preliminary
#11
Hi, hopefully two quick questions.

1) I note that mapping destinations includes MCON for CC and NRPN -- is there a reason that PBND isn't included? Is there currently a way to send PBEND? Thanks!

2) Have you considered adding variables to FX commands like PBND? All the way above the top value, for example? 3FFF-># A-># B etc? It's true that mapping the different ranges might be a bit weird, but you're already doing that between 12 and 14 bit numbers.

Thanks!
Reply
#12
(12-04-2023, 05:41 AM)proxemics Wrote: Hi, hopefully two quick questions.

1) I note that mapping destinations includes MCON for CC and NRPN -- is there a reason that PBND isn't included? Is there currently a way to send PBEND? Thanks!

2) Have you considered adding variables to FX commands like PBND? All the way above the top value, for example? 3FFF->#  A->#  B etc? It's true that mapping the different ranges might be a bit weird, but you're already doing that between 12 and 14 bit numbers.

Thanks!

1) Pitch Bend is not a Midi Controller and so it is not included yet. You can send Pitch Bend in multiple ways using a Midi Track already. Via the Automators (and thus indirect from the mappings is possible). Via FX overrule also fed from the mappings. Also you are just a few days too late, else I could have thought about it to be in the V2.0 release.

2) Not sure if I understand what you mean and I am not sure if it is possible to fit that into the current workflow. Maybe you can explain and think about how it would fit.
PLEASE use the search function if something have been asked or discussed before.
Every (unnessesary) forum support means less time to develop! But of course, i am here to help!  Smile
Reply
#13
(12-04-2023, 08:25 AM)XORadmin Wrote:
(12-04-2023, 05:41 AM)proxemics Wrote: Hi, hopefully two quick questions.

1) I note that mapping destinations includes MCON for CC and NRPN -- is there a reason that PBND isn't included? Is there currently a way to send PBEND? Thanks!

2) Have you considered adding variables to FX commands like PBND? All the way above the top value, for example? 3FFF->#  A->#  B etc? It's true that mapping the different ranges might be a bit weird, but you're already doing that between 12 and 14 bit numbers.

Thanks!

1) Pitch Bend is not a Midi Controller and so it is not included yet. You can send Pitch Bend in multiple ways using a Midi Track already. Via the Automators (and thus indirect from the mappings is possible). Via FX overrule also fed from the mappings. Also you are just a few days too late, else I could have thought about it to be in the V2.0 release.

2) Not sure if I understand what you mean and I am not sure if it is possible to fit that into the current workflow. Maybe you can explain and think about how it would fit.
Okay! Thanks for answering. I don't want to distract you from the good work you're doing. 

On 1) I have a specific use case in mind. I'm using a faderport8 to do some of what you do in the firmware video with the 16n, but in this case it also has automated sliders so various "scenes" could be recalled. So for a particular pattern, on entering the pattern Nerd would send the song's existing notes to the motorized faders, then modifying the faders would update the nerd with new note values. I want to use these faders for a lot of things, borrowing from that killer Droid module. The faderport faders are 100mm, a lot of travel, so they use pbnd for sends and receives. In the end I will probably wire up a raspi to translate i2c -> pbnd to do this.

You can see https://xor-electronics.com/forum/showth...5#pid10165 that I had asked about it before! Just to say that I didn't wait to until the release to ambush you... Tongue but it wasn't until the 2.0 manual that I saw how it was implemented in one direction.

On 2) the PBND FX on a midi track currently takes CONSTANT values from 0000 to 3FFF as its argument. Could it also take VARIABLE values? So the actual FX column in a midi track would instead of 
PBND 27FA
look like 
PBND #  A

I see what you mean about FX overrule. I hadn't thought of that yet... but I still think it would be superior to have PBND be sendable as well as receivable in the mappings window; I have 8 PBND signals to send on a single midi channel.

Thanks! Again, I can hack my way past this... but I doubt I'll be the last person who wants to send PBND programmatically from mappings.
Reply
#14
1) Oh yeah ahaha.... I got all of this as a source and I didn't realize you meant it as a destination. Well, not for this release then, but I planned also a Midi destination and maybe it will find its way to any fixed which might be needed ( I hope not ).

2) That is actually possible with the mapping overrule. You define a mapping row which should overrule FX 1,2,3 or 4. If the FX got PBND xxx then the xxx value will always be overruled with the mapping value (which can be a variable or whatever). I decided to use this instead of PBND #A in the FX since that would mean that I would need to implement this for every single FX function and most of them don't allow any more numbers.
I do agree coming directly from the mapping -> PBND is much more elegant.
PLEASE use the search function if something have been asked or discussed before.
Every (unnessesary) forum support means less time to develop! But of course, i am here to help!  Smile
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)