Forum Replies Created
-
Posts
-
Good idea to unify flam with ratcheting. I´ll think about that.
Placing notes before the step for ratcheting/flam should be possible. We do it for negative “Note Delay” values already. Good points raised by Siegmar these are cases which need special attention then.Great, thanks for letting us know!
Thanks for your question!
The note repeat rate should be shown when you´re in mixer menu, hold down the note repeat button and turn an encoder at the same time (to adjust repeat rate). If you don´t turn the encoder, it will just show dt4 (or whatever track holds your first drumtrack).
Regarding the behaviour of your note repeat button, have you checked if the button itself is working correctly? Can you try if it works as “Page >” in Store/Load Menu (should advance the Page count).
It´s not possible yet, but thanks for the feature request. It´s hereby noted!
Hi Will,
there are three things you have to check out for adressing a Synth:
- the Zaquencer track you´re planning to use must be unmuted: Mixer Menu->Track Buttons 1-4 toggle mutes (Track 1 is unmuted as default, the others are muted)
- in the Global Menu, the Midi Out A/B of the track has to correspond to the Midi Out port where the Synth is connected
- in the Global Menu, the Midi Out Channel of the track has to be set to match the Synth´s Midi ChannelThat should do it. Please try these steps and let me know if you have more specific questions.
Did you have success using one single Synth yet?
Hi again,
yes the USB method only works for one single upload coming from the original Behringer firmware.USB functionality is disabled in the Zaquencer, both the Demo and the full version.
To answer your question specifically, if you´d use the USB method to upload the Demo and do not have a working Midi interface, you wouldn´t be able to upload the full version afterwards.If the fault lies with your Midi interface, I highly recommend getting a SysEx capable Midi Interface (like the inexpensive M-Audio Midisport Uno) to retain flexibility in uploading firmwares.
Cheers!
Hi luffajo,
sorry to hear that the install is not a smooth process for you.You didn´t mention that you see numbers counting up during install, so I think that there is something wrong with the transmission. It sounds like it´s either the interface or certain settings.
Please have a look at this thread for possible solutions:
https://zaqaudio.com/forums/topic/firmware-installation-helpLong live randomness
Thanks for clearing that up, I´m happy it wasn´t coming from the Zaquencer.Hi TV Treated,
thanks for your feedback, happy to hear you like the Zaquencer!I am currently not aware of a misbehaviour that sends notes while the steps are muted. If it persists, please write a bug report with more details in the bug reports forum.
Off the top of my head, maybe it´s the case that there is another track active which sends at the same time as the muted note from one track is being passed.
Cheers!
Hi dyLAB,
you have to exit the Global Menu by hitting the “Global” button to write the Global params to flash. If you exit by “Exit” button they are not stored permanently (also see manual page 9).Please note that the track mutes are stored with each preset individually and not globally.
Also note that the free Zaquencer demo (should you be using that) is not able to store any settings in flash, as part of the demo limitation.
Hi Michelus,
das ist normal. Das Leuchten der LED zeigt den Mutestatus des Tracks an.
Diesen kannst Du im “Mixer” Menü verandern.
Dauerleuchten heißt “mute”, und wenn die LED aus ist ist der Track nicht gemuted, produziert also Noten.Bitte prüfe das doch nochmal in der Hinsicht.
Beste Grüße,
ChristianP.S.: schreib mir gerne wenn Du weitere Fragen hast, aber bitte lieber eine Mail an christian@zaqaudio.com, da ich das Forum gerne auf Englisch halten möchte.
Hi prndrsn,
first of all, if you use caution it should be safe to pull the encoder hats to remove them.
Secondly, while I don´t exactly know the cause of the slow/unresponsive encoders I really don´t think it´s because of the hat, becuase they are really pretty tight on the shafts (once you pull one off, you´ll see). I rather suspect the error in the wipers of the encoder. Maybe by applying pressure you improve the contact of the wipers.One user, Martin, has reported success with exchanging encoders.
Please see also this thread:
https://zaqaudio.com/forums/topic/knobs-replacementHi prndrsn,
thanks for sharing your thoughts about this topic.
It is interesting for me to hear how this is perceived.
I understand your motivation to write this is to help and smoothen the process and be able to convey more safety to the users, which I greatly appreciate.You´ve edited your post at the beginning, stating that you´ve read the FAQ in the meantime.
For anyone following this thread, I´ll post the relevant section from the FAQ here again:Q: What if my BCR2000 with an installed Zaquencer license should break? Can I
transfer the license?
A: As a general rule, the Zaquencer license is bound to one BCR device.
Still, if your BCR with a Zaquencer license on it should break, please get in touch with our customer service at support@zaqaudio.com. We don´t want to leave our customers hanging, but we will evaluate every case on an individual basis and reserve the right for asking for proof and denying the support request.This is our official policy regarding this topic.
While it would be nice if we could provide our customers with more safety regarding a
license transferral process, we can´t make any promises to avoid legal obligations.
On top of that we also have to protect ourselves against software piracy and this is why we handle this on a per-case-basis.
As a background, so far a bit more than 1% of Zaquencer users wanted their license transferred because of problems with their BCR.
To work out a fully automated system in software is not a viable option for us at the moment because the number of cases is just too small and we´d rather invest the development time into new features of the Zaquencer itself.Thank you for understanding our one-device-per-license policy and respecting our decisions in this regard. I´d like to add to your understanding of this by saying that this policy is an absolute necessity for realizing the Zaquencer at all from a financial point of view. I acknowledge that this carries certain inflexibilities for our customer, which is not ideal. In the end though it´s a compromise I hope our customers a willing to make, with the benefit of getting such a product at all.
Again, thank you very much for your input, and for voicing your ideas. It is really
appreciated! I hope I could make it a bit more clear why the license system is how it is and that it really works in practice without problems.Hi Craig, happy to hear that! At the moment I´m mainly working on the SysEx export/import functionality for the patterns. I´ve made progress, but it´s unfortunately turning out to be more complicated than expected and I wasn´t able to resolve all the issues yet. So for now it´s still the plan to release the next update when I get this feature into satisfactory working state.
Sounds great, thanks!
I´ve found that not all Midi Interfaces are created the same. In several threads throughout the web I´ve seen hints that a big difference is the hardware buffer that they supply. The Behringer BCR needs it´s firmware messages in packets of 306 bytes (or so). I´ve found some interfaces that only had a buffer of 256 bytes and so were chopping up the SysEx message so the BCR couldn´t understand them anymore.
This is not always depending on the price of the interface. I have seen extremely cheap ones that work and expensive ones that don´t. The cheapest one that we´ve found to work reliably is the M-Audio Midisport Uno, but there are lots of others too.
Good luck and have fun with the testing!