Forum Replies Created
-
Posts
-
Is the leftmost top row encoder (ie TYPE) on most BCR-2000′s a non-push button encoder?
The topmost row should all be push encoders. Have you tried gently pulling the encoder? Maybe it got stuck in “down” state somehow?
Zaq, if you do plan on using those switch encoders in the future can you please lay off that one (or at least don’t put a really important function there)?
The top left push encoder is already used to trigger the SysEx functionality. There is no plans atm to use it for further functionality.
I just had another quick idea, you could try to solder a push button to the respective pins and trigger the push with this extra button.
Not for now… I’ve replaced all encoder for mentioned above… no case work still.
And this detent issue just makes me mad really. I mean using this encoder means 1 detent 2 notes and that’s not very convinient. To remove detents means to loose ergonomics. And ZAQ didn’t answer about possibility to change firmware to get rid of this behaviour.
BTW I don’t think that this could bring difficulties to normal units as they don’t have detents and nobody would really see any change.Hi guys,
yes I´ve been on holidays but back in the office now.Egor, please PM me your email address. I have an idea how to achieve your desired behaviour with a small change in the firmware and could send you a quick prototype.
Would love to see a picture of your work as well!
Hi Radwan,
yes just like alien said, you can achieve this by adjusting the seq length to “1″ and then place the sequence start on the note you want to tune. this way it will only play this one step.Hi guys,
I´ve been and still am away on holidays for a couple of days.
Will be back in the office next week and will reply to all the forum posts then.Cheerio!
Hi Flavio,
thanks for sharing your idea!
I´m happy to say that this is already included. There is an option in the Global Menu, called “Quant Mixer”, that can be turned on and off.
Basically it links the mute functions of the mixer (of both the tracks and single drum mutes) to the Quantization setting or not. To do what you wish you´d have to set this to “off”.Cheers!
ChristianGood to hear, thanks for letting me know!
Hi Flavio,
from what you describe it sounds like the Quantization parameter in the Global Menu has too a small value for your liking. Have you tried out making it bigger? It´s a global parameter that determines when it´s time to switch after a pattern load or reset command.
Cheers,
ChristianI just though this through for a minute.
It´s highly unlikely that this feature is possible, because of the Flash Memory constraints. Sorry!Hi Roberto,
thanks for your question!The parameters shuffle and sequence length are only individual per track (of the 4 tracks), but not per drum instrument. That means while you can´t have different settings for each of the 16 drum instruments in one track, you could try spreading them out to the other tracks (every track can be a drumtrack if you set it so), then you can have different shuffle and length settings between tracks.
Let me know if you have more questions!
That is intentional. Both Load and Store have extra functionality when exiting the menu with their own button. Store stores the active setting in the selected slot, Load loads the selected slot, thus restarting the pattern (see manual P. 9). Same for Global, which will store Global settings only when exiting the global menu with it´s own button.
A usecase would be for example if your recent changes messed up your nice pattern, just doubleclick Load and you´re back to where you started with that pattern.
Or, if you want to make sure you´ve saved everything before powering off your machine, just doubleclick Store and Global.
I´m assuming you´re referring to manual pattern changes.
Have you checked the “quantization” setting in the global menu? This affects how long the Zaquencer waits after a button press to load the next pattern.
It goes from 96th note (immediately) to 4bars. Maybe try 1b or 2b in your case.Hm, I haven´t heard of that one before…
Powering off by mains vs switch will not affect this, because patterns are stored in Flash immediately.
Which Zaquencer version are you using?
Can you reproduce the behaviour now?
Maybe you have accidentally saved in another page, have you checked the other pages?
Hi Patrick,
thanks for sharing your feature idea! I´m afraid I don´t quite understand it yet though.
What do you mean by rest? A muting functionality?
The 3 LEDs that are not used are reserved for the step indicator and the sequencer parameters (start, length, offset).is there no way to ask if the pattern has changed and only then write?
good idea! I´ll think about how hard that would be to implement.
Hi coolout,
thanks for sharing your idea!
The port to the BCF2000 would be doable, but it´s still a lot of work.
First of all, the devices are not an exact match, regarding memory regions for certain functions, then one would have to get the faders/motors to work and then a sequencer would need a tight user interface (along the lines of your suggestion).
I´m not quite sure of the benefit of this port, because – in my mind – the concept of the Zaquencer relies heavily on the 32 rotary encoders of the BCR. You can see every step at one glance and have visual feedback for every parameter through the led rings. I´m not quite sure how much fun it would be with the BCF. I might still get one someday to fool around with it, see if I can get the motors to work and see how much fun the device is to use.
But at the moment I want to focus on the BCR, devising and implementing new features into this platform.I like Craig´s suggestion though. For that we´d still have to add lots of remote control over Midi, but that has been a request by many anyway so might come in the future.