Forum Replies Created
-
Posts
-
Hi David,
while I can´t help with finding a repair center, my first impression was that it might not be related to the hardware if the buttons send weird codes. What do you mean by that exactly, weird midi messages?
The classic hardware error is when one button triggers many functions at the same time.If you don´t experience that, and especially if previous versions worked fine, I suggest that you try re-uploading the firmware, to see if that might get rid of your error.
You can also play with rolling back to 1.03 and then reupload 1.04 etc..Best,
ChristianEDIT: Confirmed and fixed in version 1.041:
Hang-ups from too many notes will not happen anymore.Ok, so… first of all, the Midi CTRL Alpha and Beta are completely independent of each other. You can reach every mode by just working with one of them.
Glide is a submode of Ratcheting mode (not Delay), so set the Midi CTRL (let´s just say Alpha here) to “rATC” in Global menu.
Then if you selecet Midi CTRL Alpha in the main menu and put the value on 120-123 you have selected a glide mode.Bear in mind that with the special modes from 120-125 the repeat duration is always “repeat until next step”. If you don´t hear any repeat after setting the above settings, either the note length of the step is too long, or the distance between steps too short. Try reducing the note length, or reducing the clock divider to get the steps further apart.
Great thinking, I like this idea!
The nr of the turned encoder could always be the pauses between notes. (Encoder nr 2: place a note every second step, etc).
So simple, yet powerful.To not waste encoders, how far does this idea make sense?
8, 16? What to do with the other encoders?
Maybe also encode the offset in the row or so?
You might want to place every other note, starting with the 1st step, or also starting with the 2nd step…-
This reply was modified 9 years, 2 months ago by
Christian.
Hi, Cristian. In my account I don’t have a link to download the new firmware 1.04. What happen?
Hi neutrok,
the update distribution is different when you bought the Zaquencer used. I just wrote you an email.Best,
ChristianHi Majonymus,
thanks for the link to the code and your suggestion.
Unfortunatey it´s not that easy. I can´t use that code, because the code is under GPL and using that code would make the whole Zaquencer open source.Also, coming up with a working code is really the smallest problem (kinda weird, right?).
The bigger issues are with memory, and especially user interface. It´s always a balance between adding new features and keeping usability. I am very aware of this balance and try hard not to upset it by cramming too many features. Also as I wrote, with the current structure of the Zaquencer I can´t treat the individual drum instruments with different sequence lengths, only per track.So I hope you see there are many more issues than just getting a source code for a feature.
Hi guys, thanks, happy you like it!
Amazing – excuse me while I get my coat, its cold outside and I need to run through the streets and tell everyone.
Haha Tommy, I had to LOL when I read this
When will it be available for download?
It´s already available for download in your account.
Hi aaron, yes that´s right. Every new version is basically a complete, self contained software. It can be installed just like the first version, or also the original Behringer firmware. You can go straight to version 1.04.
Your presets should all not be touched at all and should be safe, but I recommend, at least to record them as Midi to have some form of backup before updating.
Starting of version 1.03 you can export them via SysEx.
I have never heard of problems with the presets due to updating before though.added in 1.04
Added basic two note intervals in 1.04
Added in 1.04 with the following modes:
- delay
- inverse delay
- ratcheting
- random ratcheting
- glide up & down
- mini arpeggiatorAdded in 1.04 with the following modes:
- delay
- inverse delay
- ratcheting
- random ratcheting
- glide up & down
- mini arpeggiatoryes these are the push button ones.
seems you were right about that heh
Ok, the first step to a hardware upgrade is in reach anyway.
Because of the other thread “Knobs replacement” I´ve finally bit the bullet and ordered the Bourns direct replacement for the BCR´s push encoders:
Top is original, bottom is Bourns PEC12R-4030F-S0024
That is the same type, not rasterized, 24 ppr, with push function.I have already tried them in the BCR and they work great. The physical resistance is a little lower in the Bourns (it´s easier to rotate), which in my opinion is great and feels like higher quality actually. The encoders in my old BCR from 2004 feel the same way.
I have ordered quite a few of those and will sell them for 3 Euro per piece+shipping. I´m thinking of ways to incorporate it into the store, in the meantime just PM me if you´re interested or write to support@zaqaudio.com
P.S. Flavio I´ve found a great way to desolder them, I just did 2 and it took me about 10 minutes altogether.
Like we said, put iron on 450° and make sure to only desolder when the iron has 450°. The thing is that when desoldering the fat pins, the heat gets absorbed very quickly and you have to wait a bit before continuing.
Start out with adding fresh tin, and when it´s liquid, remove it with the pump immediately. Repeat this (adding tin, removing with pump), until all tin is gone. I did not need to use the wick, and it was 100 times easier than the first encoder I´ve tried (from the same machine).
At the very end if there is only a tiny bit of tin holding the pin, apply some pressure to the pin with the iron until it let´s go of the tinned border and is free floating.This even worked with the fat pins at the side, just a little bit more difficult.
Good luck!
-
This reply was modified 9 years, 2 months ago by Christian.
-
This reply was modified 9 years, 2 months ago by