• Content count

  • Joined

  • Last visited

Everything posted by TK.

  1. Hi *, this thread informs you about the latest release, and it gives you the possibility to write down your feedback (bug reports, questions about existing features, suggestions for new features, etc...) The current MBSEQ V4 release can be downloaded from Please read the CHANGELOG.txt for latest changes Documentation: IntroductionHardwareFrontpanelInstallationTutorialsMenu PagesSessions16x16+X Button/LED MatrixOSC OptionV3->V4 UpgradeFirst Steps (not ready yet)Known issues and Troubeshooting tips (no known issues yet ;))  Best Regards, Thorsten.
  2. In the last days I worked on a major MBHP_MF update, mainly triggered by Screaming Rabbit who gave me a big package of different Alps faders for free! :) Design Targets: find a solution to handle high-quality faders like Alps K faders with "coreless" motors find a solution for MBHP_CORE_LPC17 which doesn't deliver stable enough ADC conversion results due to the reduced 3.3V voltage range find a solution for MBHP_CORE_LPC17 which cannot handle touch sensors properly without heavy CPU load (resp. without an additional external device or microcontroller) find a solution which is compatible with PIC based projects for best usability find a solution which is DIY friendly and doesn't require additional gear (e.g. chip programmer) for something which isn't part of the MBHP yet find a solution which can be easily tested and troubleshooted (no need to learn new processes) Following circuit is the result: a dedicated PIC controller controls the motorfaders directly it can be accessed via MIDI (only) - this allows standalone usage, cascading (to chain multiple modules), and the re-use of existing infrastructure such as MIOS, MIOS Studio and MIOS Bootloader the module can either be connected to a PC directly, or controlled from a second PIC or STM32 or LPC17 (note that MBHP_CORE_LPC17 has a third and even a fourth MIDI IO port at TTL level so that the available two MIDI IO pairs are still free) native support of various protocols (e.g. PitchBender, CCs, even Logic Control and Mackie Control Emulation) support for 8 touch sensors instead of TC4427 I'm using L293D now - not at least because of the integrated diodes. due to the direct motor control connections, the PIC is now able to generate PWM with 50 uS steps for improved motor speed control while a motor is moved since the firmware is dedicated for this task, there was enough memory free to integrate advanced features, such as runtime-calibration and motor position tracing Two snapshots of the prototype - currently I've only tested the circuit with high-quality K Faders, which were not properly controllable with MBHP_MF_V1 Meanwhile PCBs are available (layout created by SmashTV - thank you!!! :) ) MIOS Studio got a new configuration tool: Especially the calibration is much easier now, not at least because of the new motor position tracing feature: Currently following modes are planned: [*] PitchBender Chn#1..#8 [*] PitchBender Chn#9..#16 [*] CC#07 Chn#1..#8 [*] CC#07 Chn#9..#16 [*] CC#16..#23 Chn#1 [*] CC#24..#31 Chn#1 [*] Faked Logic Control [*] Faked Logic Control Extension [*] Faked Mackie Control [*] Faked Mackie Control Extension There is no real need to add more modes, considered that MIDI events can be mapped on the host PC and/or from another microcontroller (like Core32) which uses MBHP_MF_V3 as a companion. By using Pitchbender events, the highest resolution (10bit) is available. More about this topic (e.g. test of different motorfaders) after holidays. :) Best Regards, Thorsten.
  3. MIDIbox CV V2 Concept

    (continued from ) It's funny that you ask for this today, because currently I'm planning the "full featured" control surface of the upcoming MIDIbox CV V2 application. In distance to MBCV V1 it uses the MBSID sound engine, optimized for the needs for a CV controller. It features two LFOs, ENV, ARP... per channel! And with a much higher update rate than MBSID V2 (I think that up to 5 kHz can be achieved when all modulators are running in parallel, by disabling modulators even higher frequencies are possible) -> even FM modulation is possible by using two LFOs in "fast" mode /edit: meanwhile the feature list has been enhanced by a second multi-stage ENV2, a modulation and a trigger matrix! The sequencers (bassline/wavetable) will be integrated later, so: they will be available as well of course! Here the current list of parameters: /edit: removed, since it's obsolete! I'm still a bit uncertain how to continue this project, because I think that without a good control surface it won't be usable in practice. The SCS (Standard Control Surface) (2x20 LCD + 4 menu buttons + SHIFT button + encoder) gives access to all parameters, but the usage is too cumbersome. Therefore I thought that I should start with a "virtual control surface" by using Lemur, and once I'm happy with it, I can translate it into hardware. ;) Any additional ideas? E.g. how would your "dream interface" for this project look like? Best Regards, Thorsten.   /edit: meanwhile we've a demo video! :-)  
  4. Neues C64 Netzteil funktioniert nicht?

    Ok, ich habe in den entspr. Schaltplaenen dann mal Pin 4 und 5 miteinander verbunden. Wurde ja auch so langsam mal Zeit ;-) -rw-r--r-- 1 TK staff 12558 Dec 30 2015 /Users/TK/Sites/ucapps/mbhp/mbhp_4xsid_c64_psu.pdf -rw-r--r-- 1 TK staff 17371 Jul 1 2007 /Users/TK/Sites/ucapps/mbhp/mbhp_4xsid_c64_psu_optimized.pdf -rw-r--r-- 1 TK staff 22704 Jul 1 2007 /Users/TK/Sites/ucapps/mbhp/mbhp_8xsid_c64_psu_optimized.pdf -rw-r--r-- 1 TK staff 5799 Jun 10 2006 /Users/TK/Sites/ucapps/mbhp/mbhp_sid_c64_psu.pdf Gruss, Thorsten.
  5. Neues C64 Netzteil funktioniert nicht?

    Frueher hat man auch Leute auf den Mond geschossen ohne zu bedenken, dass man das in 35 Jahren genau so wiederholen moechte... soviel zum Thema Nachhaltigkeit ;-) Schaust Du bitte nochmal auf den Schaltplan? Ist es nun Pin 4 oder 5, der bei Dir funktioniert? Gruss, Thorsten.
  6. Neues C64 Netzteil funktioniert nicht?

    Super! :) Ich hoffe, dass ich in diesem Schaltplan ebenfalls Pin 4 eingetragen habe? -> Interessanterweise steht hier: das Pin 4 manchmal "nc" (not connected) ist, und 5V lediglich auf Pin 5 "garantiert" ist. Gruss, Thorsten.
  7. Neues C64 Netzteil funktioniert nicht?

    Hallo Krizz, ich verwende das gleiche Netzteil von, da mir das mit den alten C64 Netzteilen zu gefaehrlich geworden ist - das bisher verwendete ist mittlerweile 35 Jahre alt, die Gefahr ist zu gross, dass irgendwann der 5V Regulator seinen Geist aufgibt und die Chips mit Ueberspannung versorgt. Gestern habe ich das neue Netzteil nach vielen Wochen mal wieder an meine MB6582 angesteckt, interessanterweise war die Spannung etwas niedriger als sonst. Das Backlight des Displays war dunkler als sonst, und nach einigen Minuten wurde der PIC reseted (wahrscheinlich der Brownout Reset, der bei VDD<4.5V anschlaegt)). Habe das Netzteil dann aus, und wieder eingeschaltet: danach lieferte es die volle Spannung (5V). Auch heute laeuft es problemlos, werde mir das aber beim naechsten Mal genauer anschauen. Insofern waere es interessant zu wissen, ob das neue Netzteil auch bei dir funktioniert, wenn es erstmal warm geworden ist? Danach aus/einschalten - vielleicht hilft es ja. Falls nicht, macht es u.U Sinn, zu kontaktieren (kann ich uebernehmen) - vielleicht kennen die das Problem bereits. Gruss, Thorsten.
  8. Hi Rainer, I can help you on this - you got a PM Best Regards, Thorsten.
  9. SammichSID set clearGate in MIOS?

    First of all we've to align on terminology: MIOS is an operating system, but we are speaking about the MIDIbox SID V2 application which is installed on your sammichSID hardware together with MIOS. It's the MIDIbox SID application which controls the SID registers. Second: there is no "clear gate" bit. In the video, you will see at 0:52 that the Gate bit (rightmost switch) is set to 0. And that's the same what MIDIbox SID is doing. And when you listen carefully, you will notice the same background noise, sometimes also called "leakage noise" With some SID chips (especially the older ones), this leakage noise is much louder. You are using 6581 R2 - this early chip version could be affected much more from this design flaw. From an interview with Bob Yannes: You can set Atk, Dec and Rel to 0 in the OSC page, and configure the filter in the FIL page. Best Regards, Thorsten.
  10. SammichSID set clearGate in MIOS?

    Just set the ABW (ADSR Bug Workaround) flag on your sammichSID. Search on this page to get more information about the consequences:  ABW (ADSR Bug Workaround): an option which provides a less usual method to overcome the ADSR bug. Whenever the envelope is retriggered, the ADSR registers will be zeroed for at least 30 mS (time can be increased with the delay parameter). Thereafter the original ADSR values will be written back, and the gate will be activated. This results into a more deterministic envelope, but the latency makes it unsuitable for live playing. So, this feature can only be used in conjunction with a sequencer, which allows to compensate the delay (which allows to play the notes earlier by a given time). Another way to avoid it: set A, D, R to 0 and let the SW based Filter ADSR control the volume - this will also work live - and is used by most sammichSID patches. Best Regards, Thorsten.
  11. MIDIbox SID Walkthrough

    The collection of problems reported in the last weeks, and the appr. solutions, can now be found here: This is a living document which will be enhanced in future Please let me know, if an important hint is missing Best Regards, Thorsten.
  12. I opened a separated forum section for discussions about the MIDIbox BLM, since this project is not tightly coupled with the MIDIbox SEQ project, but can also be used standalone.   Schematics:   mbhp_blm_scalar.pdf the "BLM_SCALAR" module mbhp_blm_scalar_module_interconnections.pdf interconnection diagram. 5 x BLM_SCALAR modules are required for a complete BLM16x16+X mbhp_blm_map.pdf the mapping between BLM_SCALAR and Buttons/Duo-LEDs.     I'm not planning to layout the PCBs by myself, but volunteers already evinced to help out! :) Just start to coordinate your efforts here.   Some input from my side:   as you know I created the BLM16x16+X on veroboards (link to Gallery) For me this was less time consuming than layouting and ordering PCBs, especially since at the time where I started this project it wasn't clear if the SRIO hardware will work stable - I used tricks that I never tried before to reduce the chip count. With the prototype I've proven that the concept is working, so that I can release the schematics for layout.   If somebody really plans to build the circuit on verboard like me instead of waiting for the PCBs, be warned that you need some soldering experience, a lot of time and especially patience!   It took me ca. 40 hours to complete the BLM16x16+X on verobards. It was hard work and I would never do this again! ;) With PCBs I expect only ca. 15 hours work, a more stable construction, and less risk for wiring errors (-> newbie friendly).   My costs so far (all parts ordered at Reichelt):   LED 5 RG-3 Duo-LED, 5mm, 3pin, rot / grün 300 45,00 Euro TASTER 3301B Kurzhubtaster 6x6mm, Höhe: 9,5mm, 12V 300 30,00 Euro 1N 4148 Planar Epitaxial Schaltdiode, DO35, 1 300 6,00 Euro To speed up the wiring I used "verowire" (german: "Fädeldraht"), and I used 7 x "H25PR200" veroboards which won't be required for a PCB based solution, therefore they are not listed in the list above.   I strongly recommend you to order 300 LEDs/Buttons/Diodes as well although only 289 are used. E.g., at my order Reichelt only sent me 296 LEDs instead of 300 - good that these were spares! I had the remaining components for the 5 BLM_SCALAR modules + 1 PIC based MBHP_CORE already in my "personal stock". If you are interested in the part numbers you will find the references at the MBHP_DIN and MBHP_DOUT page.     Layout suggestions: in the last months I got some mails about how a BLM layout could look like, and this only showed me that it will be very hard to find a universal solution.   E.g., somebody proposed to prepare the layout for different button footprints. My comment: due to the increased amount of drill holes this will lead to much higher costs for everybody.   Somebody else proposed to use RGB LEDs instead of Duo-LEDs, since they are cheap at EBay My comment: this will increase the costs for everybody again, and it will be hard to find the same LEDs at such a high amount. E.g., consider only 30 people would like to join the PCB order - they would have to find ca. 8700 RGB LEDs from the same seller, or some of the people would have to buy more expensive RGB LEDs from a regular electronic shop. Another point that needs to be considered: for the BLM16x16+X I already chained 15 74HC595, MIOS8 supports 16 DOUT shift registers maximum. Increasing the amount of DOUT registers to control the blue LEDs will lead to difficult software changes. Third point: RGB LEDs draw much more current, especially more than Red/Green LEDs. Blue LEDs probably require additional transistors (or ICs) as source driver. The additional 74HC595 and these source drivers will require a different BLM_SCALAR module - again it doesn't make sense to bring this into an universal layout that is intended for my original project. I'm sure that most people will be happy about a cost efficient solution with Red/Green colour LEDs (like me).   Buttons: this will also become a difficult topic. I will use these ones: But I'm not sure if this construction will be stable enough. A better solution could be the usage of the same buttons and caps that where used on Wilba's MBSEQ frontpanel.   Partitioning the PCBs: the SRIO and BLM circuit has already been separated. The SRIO boards are stacked under the BLM board. It has to be considered if a huge BLM board is better than splitting the circuit into two or three parts (think also about the reduced shipping costs...)   For the BLM_SCALAR boards I recommend separate modules for each 16x4 matrix, because it is too difficult to plug the board into more than 2 large dual pin header sockets. Note that this approach would also allow you to use the same BLM_SCALAR boards for different BLM board designs!   Matrix routing: can be changed if really required. The firmware has to be adapted accordingly (changes are difficult for somebody who never worked with forward/backward matrix transformations before, see main.c) Therefore changes in the routing are only recommended for people with software programming skills.   Additional features: I will add 6 faders to my BLM16x16+X, because I find it important to get the possibility for manual sound changes with one hand, while sequences are changed with the other hand (therefore it's better to have the close to the matrix). The firmware is prepared for up to 8 pots/faders.   More informations/suggestions on request. However, my hope is that this will become a community project where experienced people will help out and where I don't need to support you that much! I could be interested to join the PCB/kit bulk order as well! :)   /Update Oct-2015: after 5 years finally we got a kit created by Latigid On! ->   /Update Jan-2016: new firmware blm_scalar_v1_1 can be downloaded from It contains prebuilt hex files for various hardware configurations:   o project_without_ain.hex            -> without AIN enabled (use this if J5 pins not connected to ground)   o project_with_4_mapped_ains.hex     -> for Latigid On's BLM PCB layout, only 4 faders used   o project_with_4_unmapped_ains.hex   -> AIN pins are mapped 1:1   o project_with_8_mapped_ains.hex     -> for Latigid On's BLM PCB layout if 4 faders + 4 extension AINs are used   o project_with_8_unmapped_ains.hex   -> AIN pins are mapped 1:1     /Update Jan-2016: if you are using a PIC18F452, it's required to change the PIC device configuration while flashing the bootloader: the brown out reset level has to be changed from 4.5V to 2.7V as shown in this picture: Otherwise PIC could be reset sporadically (depending on the number of enabled LEDs) because the voltage level could fall below 4.5V! This change is only required for PIC18F452, other pics (such as PIC18F4620 and PIC18F4685 will work w/o this change). Unfortunately this change can only be done with a PIC programmer. Please contact me for the case that you don't own a PIC programmer. I could send you a replacement PIC18F452 Alternatively use a PIC18F4620 or PIC18F4685 if you own one Best Regards, Thorsten.
  13. Winter time is DIY time - and this year I decided to explore the capabilities of the ESP32 platform. There might be synergies with MIOS32, but I'm very sure that I won't fully integrate this Microcontroller into the MIOS32 ecosystem --- this hasn't been considered 10 years ago when I started with the 32bit platform, and it would take too much time to make everything compatible (with many compromises - e.g. no native USB support, and we know that this is important for best performance!) However, I think that ESP32 is a pretty good companion device to a STM32F4, hence potential candidate for future MIDIbox enhancements. E.g. the NodeMCU ESP32 available at Reichelt for 10 EUR supports Dual-Core (!) @240 MHz with WiFi and Bluetooth, 512k RAM, 4MB external Flash, incl. USB programmer on PCB - compare this with a PIC18F*! ;-) I started with Bluetooth, and the result can be found here: This so called "BLE MIDI" service should work with any OS which supports this protocol. So far only tested on MacOS and iOS... but it should also work with Linux and Win10. This will be the basis for further experiments at my side - I'm able to communicate with the device via MIOS Studio. :-) (however, application download has to be done with the ESP32 ecosystem - means: the appr. based bootloader) In future also a WiFi connections as demonstrated in Pedalino might be possible, but I'm not there yet - focus is on the application itself, knowing that the MIDI interface options won't be so fast like known from the STM32F4 based platform. E.g. how accurate can we control a Motorfader with the PWM LED outputs of a ESP32?  If it works, it could be connected like a MBHP_MF_NG module via traditional UART based MIDI to a MIDIbox NG. And will it be possible to control a SRIO chain? Might be interesting for a future BLM16x16+X with (only) optional WiFi and Bluetooth connects. Best Regards, Thorsten.
  14. Analog pins are permanently polled by the AIN driver, this is done via DMA in background (so that the CPU isn't loaded) If you've to set pins before the next scan, then just use a AIN ServicePrepare callback. See also following tutorial which shows how to scan a touchscreen - actually a similar handling like described for your use case: Best Regards, Thorsten.
  15. MIOS32_BOARD_* functions are intended for reading the pins in digital, and not in analog mode. For Analog readouts you've to use the AIN driver. See following tutorial: Best Regards, Thorsten.
  16. ADSR SysEx [SOLVED]

    Yes, you are right, NRPN changes are only forwarded to the edit buffer. Well, there is an alternative firmware development kit available for the BC devices which should allow to implement this, but it will require some programming knowledge: Best Regards, Thorsten.
  17. MB8080 zu MB9090

    Weitere Anpassungen sind leider wesentlich komplizierter (und ich habe schon sehr lange nicht mehr an dieser App gearbeitet) Gruss, Thorsten.
  18. ADSR SysEx [SOLVED]

    Hi Dhayv, unfortunately there is no way to change these parameters via SysEx independent from each over. In the Ctrlr Panel I solved this with some LUA scripting, but with generic MIDI controllers this will be difficult (resp. impossible). However, you could control it via NRPN instead, see: To the hex numbers: $06 stands for "Direct Write of Parameter into Patch Buffer" $01 is the WOPT, explanation in the sysex doc $00 is the upper part of the parameter address Best Regards, Thorsten.
  19. Hi Dimitri, there are two ways how you can achieve this: store/restore the track setup as a PRESET: Menu->Evnt, and then PRESET with GP Button #15 or store an entire setup as a session, and if you would like to use it as a template for another session, just use the "Save As" function Best Regards, Thorsten.
  20. MIDIbox SEQ V4 Release + Feedback

    Should be fixed now, please try at your side: Best Regards, Thorsten.
  21. Could you please try following tutorial application: It shows the intended way, how to use J5 pins as inputs. And it's also a good test application to ensure, that the pins are (still) working. Best Regards, Thorsten.
  22. MB8080 zu MB9090

    Das kann ich Dir reinkonfigurieren :) db "CH ", 4, 7, 1, 0 ; Track 8 // shared with OH, Switch via 4.6 (see DEFAULT_909LIKE_HH_CONTROL_ENABLED) db "OH ", 4, 7, 1, 0 ; Track 9 // shared with CH, Switch via 4.6 (see DEFAULT_909LIKE_HH_CONTROL_ENABLED) ;; Optional 909-like OH/CH selection pin. ;; In order to use this feature, set DEFAULT_909LIKE_HH_CONTROL_ENABLED to 1, and ;; select the tracks to which the OH and CH are assigned in DEFAULT_909LIKE_HH_TRACK_OH/CH. ;; Change the DEFAULT_TRKINFO table in the header of this file, so that both track triggers share the same pin! ;; Then define the DOUT pin which should select OH/CH in DEFAULT_909LIKE_HH_SWITCH_SR/PIN below #define DEFAULT_909LIKE_HH_CONTROL_ENABLED 1 ; 0 to disable, 1 to enable #define DEFAULT_909LIKE_HH_TRACK_OH 9 ; OH track number - this track will set the SWITCH pin to 0 #define DEFAULT_909LIKE_HH_TRACK_CH 8 ; CH track number - will set the SWITCH pin to 1 #define DEFAULT_909LIKE_HH_SWITCH_SR 4 ; DOUT shift register of the SWITCH (1..16, 0 disables the assignment) #define DEFAULT_909LIKE_HH_SWITCH_PIN 6 ; switch pin (0..7 for D0..D7) Somit: Trigger auf 4.7, Switch auf 4.6 .hex File an bekannter Stelle. Gruss, Thorsten.
  23. MIDIbox SEQ V4 Release + Feedback

    Ok, something to try out: It also features the auto-track selection for recording (in MIDI configuration page, turn Chn. encoder to right to select "Auto") Best Regards, Thorsten. 
  24. MB8080 zu MB9090

    Kein Problem, ich habe das .hex File nochmal neu generiert (und unter dem alten Link abgelegt) Gruss, Thorsten.
  25. Cool! :) Best Regards, Thorsten.