Forum Replies Created
-
Posts
-
Hi Gilles,
thanks for sharing your idea!
If all 32 encoders would be push, I´d totally agree and it would make for an awesome workflow.
Like it is now though, I´d think it´d lead to more frustration than everything else. Like, when you´ve really gotten used to doing it for the first 8 steps, but not being able for the rest.
Also we might need the push function of the encoders for other more important things in the future, so I kinda like having them reserved up there.
Cheers!
The way I see it, you´d only have to set sequence start on one pattern and then copy that as a default pattern to all slots and start working from there. This should take about one minute and will then give you the exact workflow of the original.
What exactly do you mean by “wrong visual interpretation of patterns and fails in changing patterns”?
Remapping the encoders is only part of the work. Maintaining, versioning and testing a second flavor of the software is the bigger part.
I really don´t think it´ll be a problem at all to just use the original firmware for this mod and it still working as intended. Everything should really wrap around correctly.
Do you already have a Zaquencer running? Please check it out in detail for your intended change. If you find something that would really break with your intended mod, let me know and I might re-think my position.Great idea to make an extra row of buttons along with the encoders!
Unfortunately, with all the Zaquencer-related things to do (just look at the Feature wishes thread), I don´t think we can support a dedicated firmware mod for the probably few people who want to mod their hardware.
But the good news is, I´m not sure if it´s even needed if you only plan to move the top encoder row to the bottom. When you try and think it through, it´s hard to find a usecase where moving the top row to the bottom would break things. Sure, the global params would be in a different position, but that´s no worry. All the sequence params can be freely set across the board and should correctly wrap around. The only thing that would be off will be the step number display in the LCD, but that´s no biggie in my mind.
Can you think of other things?
Hi Egor,
interesting idea to replace the encoders.
I am definitely interested in how this will play out, please keep us posted here!Unfortunately, I would highly recommend finding push encoders for the top row, though.
It is definitely planned in the future to use them for different (and also important) functions. The problem is that the BCR is running out of buttons, and I want to avoid double functions on the buttons if possible.we have different BCRs here ranging from 10 years ago to the most recent ones. they are all slightly different in appearance but I can confirm that they all work the same.
I was really surprised when I recently saw the first BCR without the embossed side-panels. I wouldn´t have thought that Behringer would make a big design change like this anymore… cool, though!first of all, great track on the vid!
the cursor is being displayed like this:
- when pattern chain is enabled, the cursor always displays the track that takes the longest to play through once. this has been implemented, so you see when the next change of pattern is imminent
- when the chain is not enabled, the cursor always shows the speed of the selected track
this is why the cursor display might differ between the two modes.there is one sentence in the manual about this on page 23 in the explanation of the pattern chain. I agree this explanation could be more detailed though.
I´m not quite sure I understand the problem in the video though.
to me the cursor always seems slower in the first pattern than in the second one, regardless of pattern chain, no?the latest ones that we bought didn´t come bundled with any software at all.
there are a few related downloads on the Behringer homepage like drivers and utilities.
but I think that´s not what you had in mind, I guess rather some sort of light versions of DAWs or so? unfortunately there is nothing of that sort.how are you exiting the global menu?
all settings are only stored by exiting through pressing the “global” button again (see manual page 9).are the musical patterns stored correctly?
you could always try a flash reinit (hold page < and start/stop while powering on the BCR) or even reuploading the whole firmware to see if the error goes away.
looks awesome! the second overlay is on it´s way.
Normally you should be able to post a pic by using the direct link to the .jpg between the img tags. I see you´ve tried something similar above, but between added url tags.
Maybe that´s why it didn´t show.Oh yeah that´s right.
We only use the MSB(most significant bit)-byte and the LSB is always set to 0. So, you get the whole range but less resolution between the steps.
This seems to be common practice with other manufacturers as well.Loving the Midi cat
The tail is Midi-In only? Or can you also use the cat as a controller somehow?
It should be in there already, no?
The whole Midi range 0-127 for the command has been implemented.
It has been a while since I´ve tried it, but my understanding is that pitch bend value 63 equals no pitch bend, below you have negative, above positive pitch bend effect.Great to hear!
Thanks for posting back here and have fun with the Zaquencer!Hi Neil,
I haven´t tried that case here and unfortunately I don´t have the Kenton anymore.
Are you able to record the Midi output of the Kenton into a PC with Midi Ox or similar?
Maybe I could see something in the data.