[ChristianKeymaster]

Hm, that´s a new one.
Reinstalling the firmware might help.
Please send a quick mail to support@zaqaudio.com to request the download link.

Cheers,
Christian

[ChristianKeymaster]

Hi Jo,
nono it´s not a no-go zone don´t worry.

It´s just that I haven´t heard from Behringer in a while so I don´t really know what the status is on the project. My active phase for the collaboration was already some time ago and I am now also waiting for the release of the BC32.

Best,
Christian

[ChristianKeymaster]

Hi Markus,
I see how this could be annoying :-/
I’m not aware of any behavior in the Zaquencer that could cause this at the moment.
Can you please give me more information on the Volca? Which Midi messages would cause it to change pitch or sample volume?

What is the Retrokit cable doing? Might it be altering Midi messages in a non-benficial way?

Can you reproduce the error reliably in some circumstances?

Best,
Christian

[ChristianKeymaster]

Hi,
thanks for sharing your input.
It is possible to limit the range of the randomization by using the “gain” parameter of the wave generator.
It´s not set to a specific note, because the wave generator can also be used for other parameters. Rather it´s set as a percentage of the total range.
Please see manual page 15 for an illustration how this works.

[ChristianKeymaster]

Hello,

sorry I must have missed your post.

1/ the scale setting is global over all patterns. you can permanently apply a scale to a single pattern and store it to flash. this allows for different scales between patterns. please see the manual p.21-22 for how this works

2/ no, there is no way that the current scale change is being visualized

3/ the note length setting allows for really long notes, doesn´t this do what you need?
other than that, I guess it would rather be a setting in a synth, how it handles overlapping notes

[ChristianKeymaster]

Hi Bryan,

it could be that there was a in error in uploading the firmware.
You can just try again and do it the same way as before.
Counting up to 16 is fine.

You have listed all possible reasons that I can think of too.

Please try reuploading the firmware and then write to support@zaqaudio.com with your findings. It´s easier for me to follow up on this via email.

Thanks,
Christian

[ChristianKeymaster]

Hi Richard,

you can preview the value of every encoder by holding “page <” when turning.
This will not alter the parameter, but display it in the LCD.

Cheers,
Christian

• This reply was modified 3 years, 11 months ago by  Christian.

[ChristianKeymaster]

Hi Matthew,
thanks for your question!
It´s not basic at all, no worries.

So, what the numbers mean is the following:
they denote the distance (in semitones) from the base note, that the chord will be built upon.

Let´s give an example, Chord 1: 3,7
When you choose this chord it will build on the base note that´s programmed in the step a chord with 2 notes, one of 3 semitones distance, one with 7 semitones distance, resulting in a minor chord. Lets say your base note is c, then the chord will create a d# (3 semitones distance) and a g (7 semitones distance), which gives c minor as a chord.

You can reference the table on Wikipedia if you want to find out the names of the chords:
https://en.wikipedia.org/wiki/List_of_chords
(column “p.c. #s” corresponds to the Zaquencer notation. In this table, 0 is the base note, which is omitted in the Zaquencer table, t stands for 10 and e for 11)

0: base note only
1: 3,7 Minor chord
2: 4,7 Major chord
3: 3,6 Diminished chord
4: 4,8 Augmented chord
5: 3,6,9 Diminished seventh chord
6: 3,6,10 Tristan chord
7: 3,7,10 Minor seventh chord
8: 3,7,11 Minor major seventh chord
9: 4,6,10 Dominant seventh flat five chord
10: 4,7,9 Major sixth chord
11: 4,7,10 Harmonic seventh chord
12: 4,7,11 Major seventh chord
13: 4,8,10 Augmented seventh chord
14: 4,8,11 Augmented major seventh chord

Best,
Christian

[ChristianKeymaster]

Hi Francisco,
thanks for your question!
Unfortunately it is only possible to ratchet all the instruments on one step together.

Best,
Christian

[ChristianKeymaster]

Hi! I am not aware of a behavior like this originating from the Zaquencer.

I recommend testing several things to investigate the issue.
- check out a different midi receiver
- omit the program change message to the cycle
- look at the Zaquencer’s midi output with a monitoring software like Midi-OX.

If the cycle really needs some time to react to the program change, maybe it’s an option to use a negative note delay on the first step, or send the command on the last step of the previous loop.

[ChristianKeymaster]

Hi Simon,

thanks for taking the time to write and for your feedback!

I can´t promise anything, but I´ll keep it in the back of my mind, in case I get around to doing a redesign of the overlay again.

Best,
Christian

[ChristianKeymaster]

Great that it worked! Aaah yes you´re right. That question hasn´t popped up so far. True, the scale function is global and would also affect the transposing track, so you cannot hit the semitones as transpose steps that do not belopng to the scale.

[ChristianKeymaster]

Hi Rafael,
yeah this should work with the rerouting feature that was introduced with version 1.5.
For the transposing track you choose “In” in the Midi Out settings from the Global Menu. This will mirror the output back to the input of the BCR internally. For the rest of the configuration, I’ve described the process here:
https://zaqaudio.com/forums/topic/transposing-one-track-through-looping-back-another-track

This refers to an old version and still says to use a cable from out to in. You can omit this by using the rerouting feature as described above.

[ChristianKeymaster]

Hi Facundo,

the push function of the encoder nr. 8 shown is not important.
It only has a use in the global menu, to display the “Transpose Enbl” Parameter without changing it, but since version 1.5 that can also be done by holding the “page <” button.

It should be fine.

Best,
Christian

[ChristianKeymaster]

Hi Tym,

When chaining patterns and determining the length, we had to take into account all 4 tracks of a pattern. I decided that it should play as long as the “slowest” track needs time to complete it’s sequence.

Please see also here in the manual, from page 25:
“The duration for how long one pattern in the chain will be played, depends on it ́s slowest track. The slowest track (the track needing the most time) will be played through once before switching to the next pattern. The time that a track lasts is being determined by it ́s CLOCKDIVIDER and SEQUENCE LENGTH settings.In pattern chain mode, the Step Counter indicator (three moving dots on the lower right in the LED ring) and the start- and endpoint (one static dot on the lower right in the LED ring) will reflect the track taking the longest time.”

Can you please check that all 4 tracks are set to the 21 step length and try again?

With the manual switching, there is a “quantization” feature, that finishes the current bar (P.23).
When you turn that off, the pattern change happens immediately.

Haope this helps!

Best,
Christian

[Author]

Posts