i build this (if it can be considered a pad controller)
still have to give the firmware some final touches, but works great.
i think it is probably fun with any pad or button controller. the double trigger problem that can be seen in the beginning o…
check for a short between pin 12 an 13 of U4 (which is the 165 shift register those buttons are connected to according to the schematic)
edit: julian was faster
i think at least for the random one, 4 bit /step is plenty. if you implement like widdly suggested, the resulting value can still have a more fine resolution because the randome parameter only sets the upper boundary for the randome generation.
the…
Maybe some kind of bad solder joint on the lcd connector that causes problems only when there is mechanical pressure to the pcb on certein points - which would cause a problem when those voice buttons are pressed.
Its unlikely but i had a similar pr…
It's not like someone forces you to live in the boonies
The exact same thing happened to me before i moved to a slightly bigger city. It took several days to fix it. ( disconnected from the world, that felt like several weeks obviously.)
I hope …
.. thinking about this maybe instead of steh shift per step another idea would be to have a more complex shuffle/swing algorithm with a few more parameters. like different amounts for different groups of steps (like every other 16th, 8th etc.) this …
i think shift per step kind of contradicts the whole substep concept a bit but would be usefull.
i found myself moving steps in increments of substeps trying to get some groove going. this is not very intuative to handle and requires a lot of butto…
it's not that hard to solder with batch1 boards.
i soldered a flatcable directly to the header on the mainboard. (because i did't want any cables beeing visible on the top side of the pcb.) it's 14 connections by the way.
i thought about the possib…
i see.
nice. i always liked plain c more than all this object oriented mumbo jumbo =P~
to me, the most anoying bug is:
49 - double triggering while recording quantized notes
i think
1. bugs
2. missing features/finetune
3. nice to have
makes most sense. (only my opinion of course)
in 2. and 3. there are some things that require thinking about the "whole philosophy" of the lxr before beeing implemented i imagine.
like…
maybe reaper won't send "midi start" in that case, but "midi continue" (0xFB). if that is not implemented it would explain the problem. would make sense, because i think continue is usually used together with "song position".
i can confirm the reset/clock stuff with c-trig works aswell
there is still some strangeness with the clock in of lxr but i am probably just to tired right now to figure out wats wrong.
ill do further tests soon.