1.4 version Keyswitching

Question

Hi,

Suppose I have 40 different patches with 5 velocity groups and 3 seqpositions, that makes 600 groups. How do I relate a note number to one patch withits three seqpositions simultaneously?

Is it possible to implement the (group) tags as solution here?
So far I used a combination of CC1 and CC2 values for changing between the 40 patches. Should I delete those definitions, or is it possible to combine them, so it is up to the user if he.she chooses the CC option or keyswitch.

Up to now I don't get much functioning, I have studied the manual, so far no luck. Any help would be appriciated,

Answer 1

Hi!

Thanks so much for getting in touch!

You can have as many bindings as you want within a note or CC mapping. For example, you can map a note being hit, to enabling 20 groups and disabling the rest by having a binding for each group. It is also definitely possible to have both CCs and Notes performing keyswitch functionality at the same time.

That being said, I see how this could get cumbersome with so many groups. I have been toying with the possibility of adding an "enabled" property to the tags, which would also be controllable using keyswitches and/or UI menus. Since it's possible to have several tags per group, I'm still trying to decide what the exact logic should be. Probably it will work in such a way that in order for a sample to play, all of its group tags will need to be enabled (in computer science terms this is referred to as AND logic). Would this be a helpful addition?

– Dave

Comments

HI,
Thanks for your fast reply. At the moment I have things working now, There are some issues left if I may say so.

1. The original dspreset consists of many groups (as stated before), All coherent samples were written in many many separate groups; this was related to velocity ans sequenceposition as well.
In this keyswitching 'conversion' I'll have to rewrite the patches as in 1 group now, with all samples related to their sequencepos. That takes some time with about 14000 lines of code. Even with Sublime Text!

2. In the midi section of the script, I have been working now with only three (test) groups, Point is that I need to define for each note each time which groupos are false and true.
Example:
<note note="85">
  <binding type="general" level="group" position="0" parameter="ENABLED" translation="fixed_value" translationValue="true" />
  <binding type="general" level="group" position="1" parameter="ENABLED" translation="fixed_value" translationValue="false" />
  <binding type="general" level="group" position="2" parameter="ENABLED" translation="fixed_value" translationValue="false" />
  </note>

If I need to do this for 40 groups I'll need another 40x40 lines of code this way (with many possible mistakes/human errors. Oh no!

I am afraid I don't fully understand your reply ;  (in computer science terms this is referred to as AND logic).. Sorry, what exactly does this mean?
If your answer means a solution for my problem, yes it would be very helpful.

I had a hope, that the keyswitching implementation woudl have been a bit simpler, like e.g. just one line with only a sort of true definition that automatically excludes other groups.Maybe with the tags parameter included and leaving out the position one.?

 <note note="85">
  <binding type="general" level="group" tags="staccato" parameter="ENABLED" translation="fixed_value" translationValue="true" />
  </note>

I am not a code writer, so this may seem silly. Anyway, hope to hear from you soon again!
Best
Erik

BTW: as soon as I add this in a group line: loCC1="42" hiCC1="49" loCC2="0" hiCC2="40", the keyswitching doesn't work for that patch/group.

---

Sorry. You can ignore that comment about "computer science AND logic". I think I was overcomplicating my response. ;)

I will implement this tag functionality. Most likely the actual format will be something like this:

<binding type="general" level="tag" identifier="staccato" parameter="ENABLED" translation="fixed_value" translationValue="true" />

---

That would make me very happy Dave, you will be rewarded with a NFR of my latest release when ready. See on www.musesamples.com.

Dave, is there a sort of planning? I mean there is some urge at the moment, sorry.
Can you provide a expected release date?

---

I have been working with the keyswitch version1.4.7 version to check things with my xml.

I notice some strange things;
- DS says 135 samples are missing, shown as without any extention, named 'AG' (which is in the name of the file itself only). There is no 'AG' in the xml to be found!
- RR gives suddenly missing notes, I have checked the seqposition 1000 times, they derive from the CC version of the xml. Seqpositions are placed in the sample tags themselves.
- Not consistent volume anymore of groups, some are way softer.

Issues to be solved I guess.....

Best
Erik

[edit: first two issues were due to a stupid omission in the xml/dspreset. They have been solved. ]

After reloading I hear all possible patches (stacked) until I touch a KS key. Is there a way to avoid this?