My second Radias question

[axxim]

Hi all,

Following case,
I set a bass sound in T3 which has:
Assign=Mono
Trigger=Single
Priority=Low

Then I assign the Arpeggiator (set as Trigger) to it. If I play 1 key (i.e. C3) then it plays the pattern as desired but if I play a chord (i.e. C3 E3 G3) for the other timbres it is supposed to play C3 for that bass again right? In my case it doesn't. The bass is played on C3 for about the half gate time and then jumps (glides) to G3 for the other half. What Did I missed something?

[xmlguy]

I think you're going to have to use a split if you want to precisely control the arp notes, and then set the scan zone of the arp to look only at that split, like C1-B1. I would expect that the priority is used when the timbre is triggered by the keyboard directly, but not when the keyboard is scanned by the arp to trigger the notes. In arp trigger mode, all the notes of the scan range are sent to the timbre - and I don't see how you can change the order of those notes, since the arp gate controls them, not the keyboard directly. Or at least that's my theory.

With the keyboard split, you'd just hit C1 while you're playing the C3 Major chord.

[axxim]

Well that may be a point but it's not clear to me:

The logical structure of this should be Keyboard->Arpeggio->Timbre, where the timbre shouldn't "be aware" to know of what is triggering it. In fact the Arp needs the KB infos to generate its pattern and send it to the Timbre and if I play a triggered chord or let the Arp do it, should have the same output (execept I wouldn't play it so good).

The additional split would be an alternative but my goal was to avoid an extra split below the physical KB I need to play.

In the Radias video from Gattobus which was mentioned in this forum, I think it is working like I intend. In fact, if I set the priority to "high" then it plays only the higher note.

this came right now to me: if the gate of the Arp is set to less than 100% then it releases the priority (low) key first and due the hold function, the timbre jumps to the next tone for the rest (or just a fraction) of the gate time, and the rest is the relase from the timbre... I'll test it tonight

[xmlguy]

I'd be interested to read what you find out. Sometimes just discussing the possibilities can trigger the gate arp in our own brains.

[axxim]

Hmm.. I found it!

The arp gates-off the keys from low to high and for the remainig decay time the timbre changes the pitch to the next note which then also is turned off and passed to the next, until reaching the highest played. IOW, this makes the timbre jump to the last note. That's why only the priority=high works fine with trigger arp. For low or last it won't.

So there are 3 workarounds:
Set the timbre's decay to (or near) 0
Play inverted chords
Use one of the seqs (which is a waste for a trigger only task)

[xmlguy]

That's interesting. Now I learned something new about the engine too!