Search the Community
Showing results for tags 'issue'.
Hi, I built two identical controller keyboards using CORE_STM32F4 running MIDIbox NG. They currently feature analog ins, two wheels and octave up/down buttons. It was very hard and time consuming to build these without a proper workshop (used mainly beech wood and aluminium). Issues: #1 One big problem i have is that the velocity resolution is very low. It looks like just 5-10 values are generated, nothing in between. It's too coarse for playing properly. #2 Another problem is that i get random pitch wheel values when in zero position. I wonder if there is kind of a plateau range around the zero position to mitigate that. Or maybe it's because of a faulty pot? Thanks for your help
first of all: thanks to TK for all your great work!! so i finally got a seq v4 and soldered everything yesterday. i got a MBHP_CORE_STM32F4, Wilba SEQ CS board and MBHP_MIDI_IO. i used the wilba MBSEQ_HW.V4 file without any changes and the newest firmware version (088) no magic smoke after the first power up, but not all the buttons are working. only step 6,7, 10 ,11 of the step buttons are working and some of the other buttons also do nothing. (i didnt check which ones exactly, because i am unfamiliar with the user interface and never sure if every button should do something in the menu page i am in) the encoders all work fine. i didn't solder the leds yet, because the panel is not ready and it will be easier to get them in the right position if i do them later. i did check the solder joints visually and the orientation of the ics on the CS Pcb -no obvious problems there. my roommate also build a unit for himself and we sourced all the parts together. his unit has the exact same problem. thats why i think it is not a simple solder error like a short or wrong orientation of some part. (because that would be unlikely to happen twice.) please help me with troubleshooting. i don't really know where to start looking. i am a midibox noob by the way. (only did a seqv4lite in the past) so it is probably a noob mistake...