Forum Replies Created
-
Posts
-
Hi Paul,
thanks for voicing your concern.
Now that the 1.01 has been released I will pick up working on the SysEx export feature again but it will be some time until I can confirm that it´ll succeed (see above in this thread).But you can rest assured that adding the SysEx feature and installing that update in the future will not break your existing patterns, just like installing the 1.01 didn´t.
There might be an update in the far future that changes the way patterns are organised internally and that would break them, but I will first try to finish the export.
Also if an update would break the patterns, I would issue a big warning in the newsletter etc.Alien´s approach is much recommended in the meantime, to record your musical patterns as raw midi data into a DAW or similar. You won´t easily get them back into the Zaquencer (except with using Tap Write mode, which might be a pain because it doesn´t register all the parameters like Note Length Delay etc..), but at least you have a backup of your music.
Hi Daniel,
did you already enter your challenge code on this page?:
https://zaqaudio.com/authorization-form
(you must be logged in to access the page)You will then be sent a response code that you must enter into the device.
Please also see this page for more info:
https://zaqaudio.com/forums/topic/authorization-instructionsAlien is right, it´s most likely the Midi Interface.
My understanding is that a few interfaces out there have a too small hardware buffer to store the complete SysEx messages, so they get chopped up and the BCR doesn´t understand them anymore.A cheap one that we´ve found to work is the M-Audio Midsport Uno:
http://www.thomann.de/gb/maudio_midisport_uno.htmDo you have the possibility to try out another interface? Maybe borrow one from a friend?
Hi Rich,
thanks for sharing your request!Midi Velocity was added to Tap Write in version 1.01.
Note length unfortunately is much harder to implement.Please cosider for now using the Note Length parameter manually after having recorded the sequence.
Footswitch support added for 1.01.
The way it works now is:
- Footswitch 1: Start/Stop
- Footswitch 2: Next Pattern / Chain
If a chain is enabled, it will forward the chain as many patterns as the chain is long.
If not it will just select the next pattern.I obviously can´t please everyone but I went with what I though was in the interest of most here. Hope you like it!
Fixed in 1.01
Email sent
Fixed in 1.01
Fixed in 1.01
Hi pure,
thanks for sharing your feature request!
I do like the idea, and it might also work from the technical side. The programming might be a little tricky though.It will be quite a while before I´ll get to look into it. The roadmap for the next two updates is fixed and I should be able to check it out some time after that.
Hi Arno,
I´ve just checked this in the code and confirmed it on a device, and then I also remembered.
The thing is that the global quantization doesn´t affect the pattern switching by eternal CC at all and it was intentionally designed that way.
The idea behind it was actually more that the CCs were sent by an external device like a computer or an MPC for arranging a track. Live arrangement with a floorboard was not the main focus so far when designing the function. It should still work if you press the button right on the time you wish to change the pattern though.So, in your case the drum track is behaving correctly and the strange thing is actually that the chord track is following the quantization. According to the way the code works (and also my test here), this shouldn´t be possible.
Can you please verify that the chord track really follows the quantization in your case?
Maybe you were thrown off by the drumtrack not following the quantization when you expected it to.
Maybe you could also try testing different quantization settings for which it should always behave the same (not follow any quantization)?Hi Arno,
thanks for your bug report!I haven´t gotten around to look at it until now, but I will do so tomorrow and post back here.
In the meantime, can you please send me more specifics so I can try and reproduce the behaviour:
- which midi channel & CC number did you send on the FCB1010?
- which track number is chords, which is drums?
- is it the same between all patterns or only specific ones?Cheers!
ChristianHi Miroslav,
thanks for your question!
While I don´t have any personal experience with BCR replacement knobs, some people over here http://forum.djtechtools.com/showthread.php?t=19052 exchanged experiences about fitting spare parts. One guy reported success in exchanging an encoder. If you need more information, maybe you can post there or even send them a private message?Ok, great to hear.
Thanks for posting back here!Ok, the Kenton Midi Thru 5 arrived today and I can confirm that it works nicely with the Zaquencer. The setup is: all 4 tracks go out from the Zaquencer on Output A to the Midi Thru and are split from there to 4 synths. I can then adress every synth on it´s own Midi channel, exactly how it should be.