Forum Replies Created
-
Posts
-
Hi davidu,
thanks for your input.
Right now it´s not possible to chain tracks, only patterns as described above.
You can edit the patterns in chain mode, but you have to doubleclick “store” before the next one loads or your changes will not be kept. I understand that this is not ideal, but maybe it´s something that one could get used to.I will think about your idea some more to see if it could be realized with reasonable effort. But I am really not sure at the moment.
Hi Flavio,
thanks for your questions, and ALien, thanks for your answers
I have written a bit about the autosave over here, in Alien´s request:
https://zaqaudio.com/forums/topic/pattern-autosaveHi ALien,
I have already thought about this option, and while it would be great to have, I have decided against inplementing it for a very specific reason.
All existing flash chips, and so also the one in the BCR, only have a limited life in terms of writes (usually a couple 100.000). While through regular use you are hard-pressed to ever reach this limit, with an Autosave function it would definitely be reachable, and it´s hard to say how fast. If you picture using Autosave in conjunction with pattern chain, you can imagine that you can get heaps of writes in a very short time. While I could just put the info into the manual, I doubt that it would reach every user of the Zaquencer, so I decided not to provide the function in the first place.Thanks, it´s now up again.
Hi beau,
thanks for your question!Well, yes the limitation of the limited time resolution applies to all sequences that the Zaquencer is able to represent. It makes no difference in this regard if the sequence has been created in realtime or offline. An import of an existing midi file is not a trivial task and in addition will always be limited by the time resolution.
If somebody wants to have a go anyway, I could imagine this as an additional function for the open source Zaquencer Preset Manager that has just been released (import .mid file, write into a .syx file for the Zaquencer). Let me know, I´ll gladly help with the pattern spec of the Zaq.
Hi Nigel,
thanks for your question!
Just by updating the firmware, the stored patterns will not be changed at all.If you then actively work with the export/import function you may choose to overwrite existing patterns by sending the device a batch of new ones.
It´s pretty well protected by having to press a certain button in the store menu, and it will only overwrite when a valid Zaquencer pattern has been received over Midi, so accidental writes should be as good as impossible.Hi guys,
thanks for the warm reception
@Christa, yes all successive updates contain the changes from the previous ones, so the encoder filter is also in 1.03.@Alien, yeah there are lots of possibilities for the preset manager! Right now the name might be a bit too big, as it only allows to validate the SysEx files so far
But who knows what´s to come! Also it´s open source, so if anyone is interested I´ll be happy to assist in a community development effort Ability to export/import the presets and global settings through SysEx added in version 1.03!
Hi Mike,
sounds like you are pretty well equipped, already with a Midi patchbay and a nice setup of synths! While I don´t have personal experience with Midi patchbays, I imagine it would be best to just hook up all your synths/Zaquencer/computer to the patchbay and then have the option to really route very flexible how you want to use it (jamsession/recording/keyboard input, all just a routing setting away). Does it also do Midi Merge/Split operations?
You could use it to distribute the clock, or collect Midi input for the Zaquencer from different sources (keyboard/computer/controller).If you want to hook up everything to the Zaquencer at the same time, and don´t plan to use every voice of each drumcomputer, you could check out the following tip here, to trigger up to 16 sounds from both drummachines from only one Zaquencer track:
https://zaqaudio.com/forums/topic/hook-up-more-drummachines-to-the-same-trackI see you´ve found the “Getting Started” already so maybe you´re already set?
It´s a bit hard for me to get into your thought process and what you want to accomplish with the setup, but if you have more specific questions I´ll be happy to address them.
Hi Eric,
thanks for sharing your request!
It has been discussed in the past (the list is getting quite long, I know):
https://zaqaudio.com/forums/topic/mute-off-with-pitching-a-stepI do not want to change it because the users might have been gotten used to how it works now, or might even consider it a feature that the two paramters are completely independent (like von haulshoven in the other thread).
can I help you with understanding the tap write? do you have specific questions?
Hi Damien,
thanks for your post! The Zaquencer does not have a slide function. Usually this is more to be found in the respective synth that you send the Midi data to. Maybe you can enable/disable it in the Synth by sending CCs from the Zaquencer?Hi Roberto,
thanks for your message and for sharing your idea!
The thing is, during development we´ve tried switching off the quantization, but because of the limited internal time resolution (Midi pulses), the smallest raster spacing was something like 20ms. This was enough to really mess with the feeling of a performance, so that it felt even worse. This is why we decided on enabling the quantization for recording.Best,
ChristianHi Damien, thanks for writing back here! Happy to hear that all is ok now.
Enjoy your Zaquencer!!great post, thanks for the motivational words!!
I´ve had started work on the lightshow some time ago, but then more pressing topics came up and so I´ve put it aside. with your post you reminded me of that and I´ll revisit it again after the next update! should not be too much work left to do…