Baloran Forum

The River => Discussion (English preferably) => Topic started by: falconi on December 26, 2020, 08:49:12 PM

Title: "Pressing time" of encoders.
Post by: falconi on December 26, 2020, 08:49:12 PM
Hello,
I have updated to 2.12, and all my 4 encoders seem to be working more accurate now, which is great.
However, confirming values by pressing them still sucks - a bit.;)
What I have just found out: The Problem is NOT the encoder or the applied pressure (like on Roland keyboards from the 90s). It is TIME. I just have to press longer and it works w/o any violence.

How frequently does the DUE-board read out the condition of the encoders? Could you possibly read out/ "mux" with a higher frequency?

Thank you!
Title: Re: "Pressing time" of encoders.
Post by: Baloran on March 27, 2021, 05:45:26 PM
The DUE does not read encoders. It has enough work as it is to manage the multiplexed distribution of signals to the voice cards and only does that ;)
The panel is managed by its own (ARM Cortex M4 clocked at 72 MHz Teensy 3.2) which does only that and gives orders to the DUE ;) the 11 encoders of the panel are managed by a dedicated ATMEL 1280 ...
The Riverkey is managed by another ARM Cortex M4 which does only that (keyboard decoding, layers, sequencer and arpeggios) and manages the two encoders.
So the reading frequency of the encoders and encoder buttons is 1000x per second. Isn't that enough for you ?
I'm making fun of you a little, but there are many other constraints in such a product. EEPROM access speed, I2S and SPI exchanges, multiplexing etc...
So functionally, which encoder do you find slow? I will see if I can make the speed impression better....