[ChristianKeymaster]

Added note repeat as part of Midi CC remote control in version 1.5

[ChristianKeymaster]

Added Midi CC control for most parameters in version 1.5

[ChristianKeymaster]

Added parameter preview without affecting it for Main and Global menu in version 1.5

[ChristianKeymaster]

Added triggering of all 192 available patterns in version 1.5

[ChristianKeymaster]

Monitoring mode for tap write added in Version 1.5

[ChristianKeymaster]

Hey Jan, I think you´ll find that the update 1.5 brings what you wished for (although a little different). You can now select to load patterns without affecting the mutes.

[ChristianKeymaster]

Midi CC Input added in Version 1.5. Please check the updated manual for all available commands.

[ChristianKeymaster]

p.s. as another quick idea (from on the road), maybe can you try to make zaquencer the master an see if this runs better with the other gear?

[ChristianKeymaster]

From what you describe it sounds like it might be connected to the external clock. i’ve had the case that in some circumstances if the clock stops coming in from the master the zaquencer may appear frozen. can you please try with a different clock setup or verify that your clock is working reliably (from ableton and the interface).

i am out of the office until saturday and can help troubleshoot more next week.

cheers!

[ChristianKeymaster]

First, please upgrade to 1.042 and see if the problem persists. Lots of bugfixes happend inbetween these versions.

[ChristianKeymaster]

This is new. What version are you running? Internal/external clock? How´s the rest of your setup?

[ChristianKeymaster]

Hi guys,

thanks again for submitting your bug reports. With all these reports, this topic is highest on the priority list right now (after releasing the next update).

The thing is, I´ve already bought a cheap Miditech Thru box (which was reported in this thread to have shown the error) and had the Zaquencer running with it for 30 hours or so, but the bug did not show even once here…! I tried before without the Thru, but also wasn´t able to provoke the bug.

I have a feeling that if we want to have a chance to catch this bug it has to be a joint effort. I´m asking again that when you´ve encountered the bug and are interested in having it fixed, please export your global settings and pattern as a .syx file and send it to support@zaqaudio.com (we haven´t received a single mail regarding this issue yet). Please include additional info about your complete hardware setup, the more detailed the better, maybe even a diagram. Most of you already included more info, which is great, but I actually need all the relevant information to make sense of it.

I think the following should be sufficient for the email:
- global settings/pattern as .syx files
- Zaquencer version
- Output A/B
- Through box (yes/no, which one?)
- all other connected devices (and how are they connected exactly -> diagram would be best)
- is there a Midi USB interface somewhere in your setup?
- estimated frequentness of the bug (happend x times in x hours of play)
- anything else you can think of

If you want to help testing beyond that, and actively want to look for the bug, the most valuable info would be to have only one synth connected to the Zaquencer (and nothing else, not even to the synth´s through). So “Zaquencer->Synth”, have it show the error, and then submit the data above. The fewer variables the better, when trying to pinpoint a bug.

Thanks!

[ChristianKeymaster]

Looks good, but I do not have any experience with the BCR´s switches and a quick search revealed no information. My guess is that if the dimenstions are the same and the “electrical” properties (like which pins are connected on push) then it should work. You should be able to get all the necessary info from the datasheet.

I´d be very interested in this as well, so if you decide to give it a go and try them out please post back here!

[ChristianKeymaster]

So, what´s possible right now is to trigger a pattern directly by number (patterns 0-127).
This can be done by sending the corresponding CC message (see manual page 22 for all the details: “Trigger Enable & Trigger CC Nr” https://zaqaudio.com/files/Zaquencer-Instruction%20Manual_1_04.pdf).

This feature is also contained in the free demo, so you can try before buy to see if it really does what you need.

[ChristianKeymaster]

Thanks for sharing the idea about the chords, but as you´ve guessed this is unfortunatley impossible. The chords are built on runtime upon the existing base note by getting the chord intervals from a lookup table. Applying the scale alters the base note, but it can´t affect the predefined chord intervals.

[Author]

Posts