tago
Members-
Posts
273 -
Joined
-
Last visited
Recent Profile Visitors
The recent visitors block is disabled and is not being shown to other users.
tago's Achievements
MIDIbox Tweaker (3/4)
1
Reputation
-
@Phatline Here the pcb layout. There is a voltage reference (U3) (center bottom - looks like a transistor) and on the right side an opamp (U2) to scale the voltage range because of the limited rotation angles of the wheel pots. I did that with the help and recommendation of @FantomXR and others. Can't find the original thread at the moment. See how the Vref (red) goes to the opamp (U2) and then to the jumper J8 where both wheels are connected to.
-
Hi Phatline, i'm using an AINSER8 module (see that perf board on the third photo). So pots aren't directly connected to the core. Power is coming via USB. I'll take a look into the docs for a middle offset function. I think Doepfer is calling it 'plateau' on their keyboard controller boards. I assume there is no way around something like that. EDIT: do you think it could be because the pot is old/used?
-
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
-
@Hawkeye Thanks for providing more details and trying to fix this issue. I know what you mean by rescanning/reconnecting the Core after uploading via MIOS Studio. It's not ideal but workable. I really hope Thorsten will look into it and update the toolchain. Getting an additional computer is really a hassle. This hobby is already expensive enough. It should also help to get more people onboard with MidiBox, having lower hurdles.
-
Thanks @Hawkeye A pity Windows is not supported anymore. I think that's makes it lesser accessible to us Windows people. Is there really no one in reach who has the chops to update the toolchain? For the love of the Midibox project. If i only had an idea about those things, i would do it. Maybe i can go the Hackintosh route, but that sounds like much work better invested in other things. So with a Hackintosh i can compile the most recent NG app? @TK. What do you think about the situation? Any chance to get it working for Windows/Linux again?
-
Here is some talk about open vs closed: https://forum.arduino.cc/index.php?topic=695264.0 In the second post someone says: "One disadvantage of a N/C is that with a pullup, as most switches spend the majority of their time in the un-pressed state, you will have increase current consumption." If this is correct i'd get a normally open pedal.
-
I'm no expert. I guess you should see debug output in the MIOS Studio terminal. Search for "debug" in http://www.ucapps.de/midibox_ng_manual_fs.html
-
Hi, i want to add a sustain panel to my NG based keyboard controller. Which switch type is the best? Normally closed or normally open? (i somehow think normally open would be better, because the circuit is only closed on press = less energy consumption) What would be the best way to connect them? Via analog or digital input? Thank you
-
@m.str What apps do you run on your controllers? How are the banked menu items displayed exactly? Can you changed them per menu encoder? Thank you!
-
I've tried banking 8 pots and get little bars for each event on the second line of the display, but can't find a way to display the corresponding labels and change the values just using the menu encoder. I think i need something like an generic EVENT without any hardware control associated to it.