Release Candidate Firmware V1.20 RC5

[XORadmin]

About the CV input and recording. I was experimenting and searching for the problems i had while recording. Test keyboard was the Arturia Keystep, which i thought would be perfect to test. But the results were very bad, while the trigger was right, the notes often arrived one step too late.

I now found out that this is a problem with the keystep, it has quite a slew between notes. I researched for it and directly got to the information that it is not only my unit:

https://www.muffwiggler.com/forum/viewto...82#2283582

That means the Keystep is causing the problems that i have. What i will do is to add a adjustable delay for CV recording, so also here the correct notes are filled in on the correct steps. However, i am not sure how tricky this is going to be, as the sequencer can already be on another step when the voltage is stable....they are probably the same issues with the BSP.
I will do my best to get the release ready soon. Some more surprises are in there...

Once I used CV input of Nerdseq to record a piece from another sequencer (Cirklon). Everything went even better than I expected - notes and triggers were in place. What was little bit difficult - to find "right" Nerdseq groove setting (time signature) what fits correctly together with Cirklon clock. At the end of the day I have tried different Cirklon clocks to get the right division and leave Nerdseq groove as it was.

Yes you need of course matching clocks if you want to record 1:1 and the best solution is most probably a clock with 24ppqn on both, while nerdseq being just 6 ticks/step groove setting.

But the main problem is when using either the Keystep or the BSP as CV source and try to record that. (i didn't test the BSP as i don't have one, but checking different forum items on MW or Arturias Forum show me that it has the same issues) The fact that the CV voltage needs 3-5 milliseconds until it reaches the note, while the trigger happened already before the CV is even starting to move to the new note is actually not accepteable and forces me now to add some kind of CV delay to be sure the correct note is being recorded (and not too late then).
I expect good recording results from good sources, and average ones from bad sources. So it'll be a best possible implementation.