Jump to content


  • Posts

  • 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

MIDIbox Tweaker (3/4)



  1. @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.
  2. Do you mean stable USB drivers for development purposes? I'd only use a Hackintosh/Mac to be able to compile an app, not for music making, if there is no other way around it. Do you know who did the original Windows toolchain?
  3. 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?
  4. Hi, Any tips how to optimize NG to get better velocity performance? I'm getting very few velocities. I'm getting a very coarse velocitiy resolution. I'm using a STM32F4 core and have a 5 octave keyboard plus an AINSER8 attached. No menu or displays. I'm thankful for any tips.
  5. 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.
  6. Ok, i found an answer here http://midibox.org/forums/topic/20751-fatar-tp40l-midification/?do=findComment&comment=181241 If this is the best way, i'd like to know what kind of pedal is the best. Normally closed or normally open?
  7. 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
  8. 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
  9. @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!
  10. 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.
  11. Thanks @m.str yes, i'm talking about the NG app. I'll give banks it a try.
  12. Hi @m.str yes i've considered banks, but think that isn't what i really want. Does banking display the items of each bank in the display like a normal menu without the need of dedicated hardware controls? As i understand it, it can build banks of hardware inputs (ie 8 encoders in a row). Thanks
  13. Hi, i'd like to add some pages for various parameters to the menu. Those parameters will be normal midi parameter/CC and should send midi events. It seems like the current menu system is directly coded in C. Is there a way to add menu items or submenus per config file (NGC for example)? Thanks in advance
  • Create New...