Forum Replies Created
-
Posts
-
This question is quite a few months old but:
Currently in Studio One 3.5+ what you need to do is –- Add a generic keyboard in Options from which you’ll receive MIDI IN from the BCR/Zaquencer – enable “Split Channels”. I call this ZAQ IN.
- Add a generic instrument to which you’ll send MIDI OUT – enable Clock. I call this ZAQ OUT.
Now on your MIDI/Instrument track you need to be either sending or receiving MIDI from one of those, basically. But if you just want to send out clock then you just need the generic instrument with MIDI out. You don’t need to add a MIDI track for it; as long as it is set up Studio One will send Clock out to it when you press play. If you want no delay you need to activate the “Z” buffer feature in the DAW. It takes more processing but you get “0 ms” delay.
Hi, I just updated to 1.5 through a PreSonus Audiobox 44VSL USB interface.
Great update, by the way!Martin, it is a thing to me
– https://soundcloud.com/loqvst/t-e3-work-in-progress@rempesm – The Clock Divider trick works really well, thanks. However I always need to have one of the tracks with a really slow divider setting which pretty much limits the zaquencer to 3 tracks.
@rempesm
Ahhh this is really interesting as I write a lot of 3/4 techno and was wondering if I’d be able to do so in Zaquencer. Thanks for the reply
I’ll take some time to study it next weekend or whenever I have free time.@zaq (Chris?),
That solution sounds perfect! I believe that would make us able to mess around with the instruments and tracks layers in a more flexible way.Regarding the grid thing (which I think is far too complex and you solution is way better), what I was suggesting would be a feature that would set how many loops a given pattern will play through until it reloads itself from memory. Just like we set the length of a pattern, we could be able to set up to how many times it loops. And then if we chained the patterns, we could have patterns go like this, for example:
Pattern 1 – loops 2 times
P2 – 4 times
P3 – 1 time
P4 – 8 times
ETC…Which would basically consist of a song-writing mode, I guess.
But the thing would be that during that interval of so many loop bars set for each pattern it would loop without reloading itself from memory and therefore allowing for over 4 bars of muted tracks, instruments, notes, etc.
And if you always wanted it to reset, you’d just set the loop times to 1.@rempesm
I still have to get around playing with the Clock Divider. I read about it on the manual but I thought it was a bit confusing so I need to see it in action. One thing you said is confusing me though, didn’t you mean to say “32 steps of a mute” instead of “32 bars”? Because if I can have 32 BARS of a mute in a pattern that is looping, then that’s more than enough for my needs. I usually need 8 or 16 bars.Hey! Thanks for the reply.
The thing about muting Tracks in Zaquencer/BCR is that I’ve been using Tracks 1 and 2 as different melody layers that control a Minibrute. If I want to mute one of these layers for a period longer than 32 steps I can’t. And in that case I can’t mute the Minibrute since that would kill both layers. Also, if I’m using a soft or hardware synth for pads, for example, muting the outgoing notes on the Zaquencer allows the release to go for as long as I want to, while muting the synth cuts that effect. Anyway, I could go on and on about situations were muting the MIDI notes is better than muting the synth. This is my only gripe with Zaquencer so far.
One thing I’ve been thinking that could help this, maybe, is if you provided grid intervals longer than 4 bars? And while the interval is not reached, the current pattern just loops? For the type of music I make having 16 bars of mute would be wonderful.
For now I’ll try to make versions of my patterns with muted elements and see how that works. Thanks for the help
Glow in the dark yes please!