More Layers for 3.0.7?

[chrislines]

With the removal of the ability to chromatically trigger (C2, C2#, D2 etc) multiple Sliced pads with one Sequence (which was possible in previous versions) the flexibility for Sliced samples is much reduced. Now one Sequence can only trigger one Sliced pad chromatically.

Although the new Layers feature does go some way to address this with A, B, C, D Layers ie Layer A = C2, Layer B = C2# etc, 4 layers is quite limited. Increasing the number of layers (to ideally 16) would offer much greater flexibility.

Hopefully others will see the benefit of this particularly if you are using chromatically sequenced sliced wavs.

[-thus-]

With the removal of the ability to chromatically trigger (C2, C2#, D2 etc) multiple Sliced pads with one Sequence (which was possible in previous versions) the flexibility for Sliced samples is much reduced. Now one Sequence can only trigger one Sliced pad chromatically.

Although the new Layers feature does go some way to address this with A, B, C, D Layers ie Layer A = C2, Layer B = C2# etc, 4 layers is quite limited. Increasing the number of layers (to ideally 16) would offer much greater flexibility.

I understand your first paragraph perfectly but then I get lost in your second paragraph. Why are you only playing one note/slice per layer in your example? Maybe it would help to know what kind of music you’re making and what sounds are being sliced on each pad.

[Steve]

Consider sharing your workflow and desired outcome. I agree, your second paragraph is a bit confusing.

[chrislines]

To clarify, I am sequencing traditional Pop music on the Black Box. I produce the tracks in my DAW then export various stems the length of the song.

I then slice up each stem into verse, chorus, bridge, chorus 2, outro etc. So there could be 8 or 10 sections in a song.

I keep each stem (eg kick, snare, bass) separate on its own pad so that I can pass each stem to a separate output. So I may have 8 or more stems needing to be triggered at once for each section of a song.

So... I then used to use Seq 1 for say verse 1, Seq 2 for chorus etc. I would program all required pads using the 1st slice (C2) in Seq 1 and then slice 2 (C2#) into Seq 2 etc.

In 3.0.7 I cannot do this as one Seq can now only control one pad, not multiple pads. So to sequence multiple pads at once using one Seq isn't possible.

The use of the layers was so I could utilise Layer A = C2, Layer B = C2#, Layer C = D2 & Layer D = D2# therefore each layer would be for a different slice/section of the song. My suggestion of more Layers was so I could trigger up to say 16 slices from the same Sequence.

Hope that makes more sense?

[Steve]

It does; thank you for the clarification. Your previous workflow may not work so well in v3, as you have figured out. Sequences now have a 1:1 relationship with pads. You can certainly achieve this with an external sequencer, though I understand not wanting to do that. You can also use a Pad Seq and Slice Seq to step through the sections. Or, you can try using the sequence layers with Song scenes and use MIDI notes to trigger the scenes as needed. If you set it up properly, you can trigger multiple layers in a single scene.

[chrislines]

Thanks for your suggestions. Could you clarify what you meant when you said I could use a Pad Seq and Slice Seq to step through the sections? This is what I am doing already I think. Also what type of external sequencer do you have in mind? Thanks.

[Steve]

Any external sequencer could work. If you use a Pads seq type, you only trigger the pad as if touching it. This does not play the individual slices by pitch (C2...ascending). Instead, it triggers the current slice. If you then set the SLice Seq to Random, every trigger will play a random slice.