Jump to content


  • Content Count

  • Joined

Community Reputation

0 Neutral

About TK.

  • Rank
    MIDIbox Guru
  • Birthday 11/17/1972

Contact Methods

  • Website URL

Profile Information

  • Gender
    Not Telling
  • Location

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Great that it's working now, but further diagnosis is difficult remotely (maybe a picture helps) Best Regards, Thorsten.
  2. Yes - did you ever try the "Live Forwarding" feature of the Jam page? Best Regards, Thorsten.
  3. Yes, the function is different, see also the MIDI Router documentation under http://www.ucapps.de/midibox_seq_manual_m.html Alternatively, also "Track" can be selected as target channel. In this case, incoming MIDI events will be routed to the MIDI port and channel of a track depending on the incoming MIDI channel number. Usecase: MIDI events, such as CC or Notes, should be sent from a master keyboard or MIDI controller to synths which are assigned to different port and MIDI channels in the track configuration. Just select the track with the MIDI channel on your keyboard/controller, the ro
  4. TK.

    No more https?

    No SSL so far - thanks for the reminder! Best Regards, Thorsten.
  5. Hi, yes, you should read 5V on C3, C4 and J2. But based on your measurements the capacitors don't cause the problem (it would be a short, resulting into 0V at pin 1). Sounds like a bad solder joint or broken track? What happens if you connect pin 1 and 2 with a short wire? Best Regards, Thorsten.
  6. This feature was requested from a user who just wanted to forward MIDI messages to the preconfigured MIDI port/channels of the tracks without further processing, and this is how it's working. Your request goes into a different direction, it's more like a multi channel live/recording function - currently we can only record or play live (+ FX) on a single (selected) track. Allowing more channels would lead to higher RAM consumption, but it could be provided as a MIDIbox SEQ V4+ option, only working on a STM32F4. I'm unsure how Mutes should be handled in this case. I would expect that i
  7. Yes, this makes a difference, because the ADC channels have to be selected differently in the firmware. Here a build for PIC18F4685 - untested (hope that it works): http://www.ucapps.de/mbhp/mbhp_mf_ng_v1_005_pic18f4685.zip Best Regards, Thorsten.
  8. I found this firmware in my backups, the link is working again Best Regards, Thorsten.
  9. It took a bit longer than expected, but finally we've a new forum software and also the gallery should work again Yes, I'm definitely interested on "reporters" for the wordpress blog; let me update the installation, thereafter I can give you access :) Best Regards, Thorsten.
  10. Very cool transparent case! :) Best Regards, Thorsten.
  11. Hi Richie, in MIOS Studio, MBHP_MF_NG configuration tool, please check the MIDI configuration. E.g. the "operation mode" defines, what kind of MIDI events are sent, and the "touch sensor mode" defines, under which conditions they are sent. Best Regards, Thorsten. P.S.: Don't know where to find the MIDI 3 IN/OUT wiring schematics, maybe the forum search function helps.
  12. Unfortunately gallery rebuild times out, and it requires a forum update: https://invisioncommunity.com/release-notes/ Will check it later this week - updating the forum SW is on my backlog anyhow (since several years ;) Best Regards, Thorsten.
  13. @latigid on some history on this: while previous boards had a pull-up device for this pin, the STM32F4 Discovery Board had a pull-down, therefore I did'n activate an internal pull device to avoid cross-currents. Good that you didn't completely remove the option for an external resistor! :) @Hawkeyegreat demo, I like it! :) With the step sequencer features the LoopA even becomes interesting for me as a guy who unlearned live playing (too much automation - I was better >20 years ago ;-) The graphics are epic! :) Best Regards, Thorsten.
  14. It's difficult to predict if a reversed J19 connection could damage the DAC, but I still use the same board that I got from Seppoman many years ago, and somehow it survived although I sometimes did really stupid wrong connections. Typical test procedure at my side: connect the module (this can be done while MBSEQ is running) crossing fingers that I didn't misinterpreted the schematic enter CV page, re-select the interface with Encoder #16 (e.g. select AOUT, than back to AOUT_NG) -> this will initialize the DAC set different calibration values wi
  • Create New...