TK.

Hi Robin, thanks for the input - I just found an error in the mb64_sfb.inc file (the same error exists in the MIDIbox64E and MIDIbox MF application). Quickfix: open this file, search for MB64_SFB_Handler_02 (or go directly to line 86) and change: ;; branch to the end if no bankstick available IFSET MB_STAT, MB_STAT_USE_BANKSTICK, rgoto MB64_SFB_Handler_02_Msg to: ;; branch to the end if no bankstick available IFCLR MB_STAT, MB_STAT_USE_BANKSTICK, rgoto MB64_SFB_Handler_02_Msg hope that this helps! Best Regards, Thorsten.

the new MIDIO128 release is now available in the MIOS download section: http://www.ucapps.de/mios_download.html ChangeLog: http://www.ucapps.de/midio128_changelog.html Best Regards, Thorsten.

The MIDIbox SID from Chriss:

The MIDIbox64 from Pierrot - one of the most beautiful cases I ever saw! :)

Hi Per S, thank you for the reminder. The changes are already made, but I haven't found the time to release it (which takes some time since I always have to do some checks before) Best Regards, Thorsten.

Hi Pierrot, my suggestion: check the control elements with a simple test application first, before uploading the MIDIbox64 application, because if anything is not wired correctly, it's more difficult to sort this out with a complex program which (e.g.) unintentionally switches banks, activates groups, morphs the controller setting, or whatever... effects which you cannot explained by yourself so long you haven't used them. So: begin with the buttons and LEDs. Upload MIDIO128 and check if each button triggers a single MIDI event. Send the same events back (e.g. with MIDI-Ox) to see if the appr. LED is working. The encoder should send two events (since its connected to two pins), depending on the rotation state. You could also use the dout_buttons application to check the LEDs (two buttons are used to select one of 128 LEDs), so that you don't need to send MIDI events Once this is working, continue with ain64_din128_dout128, each pot should send a single controller event. If you still notice problems, then just write down, which application sends which events --- this allows us to tell you which hardware connections are wrong. Based on your descriptions I would say that the AIN multiplexers are not working, and that the SCLK or RCLK line of the DIN/DOUT shift register chain is not or wrongly connected. Best Regards, Thorsten.

yes, it's just like the rectifer/buffer/regulation circuit between J1 and J2 of the core modul + a transformer. Many electronic shops have such premade PSUs for cheap money - e.g. Pollin (http://www.pollin.de) has a regulated PSU with +5 V/1 A, +12 V/0,25 A and -12V/0.25A output which is an excellent solution for MIDIbox SID and MIDIbox CV And it costs only 1.95 EUR! So, just open your eyes when you go through an (online) electronic shop :) Best Regards, Thorsten.

Hallo Tobi, ja, die Ladekurve wird periodisch ueberwacht - dauert die Entladung laenger als der Grundwert, kann man davon ausgehen, dass der Touch Sensor gerade beruehrt wird. Nein, Du brauchst keinen zusaetzlichen Kondensator. Du benoetigst noch nicht einmal einen speziellen Sensor, denn wenn Du den hochohmigen Eingang der Sensorschaltung beruehrst, entsteht bereits eine kapazitive Verbindung zur Erde (ueber Deinen Koerper), und diese Kapazitaet ist ausreichend gross, um die Pulsantwort zu verlaengern. siehe auch http://www.ucapps.de/mbhp/mbhp_din_touchsensors.pdf Gruss, Thorsten.

No, there is no problem with XP. Just follow the MIDI troubleshooting guide step by step --- all issues from the past are documented there, all users were able to get the upload running based on this guide, and I don't think that there is any new, unknown problem. http://www.ucapps.de/howto_debug_midi.html Best Regards, Thorsten.

Hi Robin, alright, now it's clear - this will work. Hint: if you've saved the button number of the group, you can convert it to 1-of-8 code (which is possibly for which you are looking for) with the MIOS_HLP_GetBitORMask - the result is the LED pattern which can be forwarded to MIOS_DOUT_SRSet Best Regards, Thorsten.

yes, finally a nice studio corner with enough place for upcoming MIDIbox projects :) Best Regards, Thorsten.

Hallo Tobi, so trivial ist das gar nicht, um nicht zu sagen, es ist ziemlich tricky ;-) Hier gibts ein paar Informationen dazu, wie MIOS einen Touch Sensor auswertet: http://www.midibox.org/cgi-bin/yabb/YaBB.cgi?board=concepts;action=display;num=1062462975;start=1#1 Gruss, Thorsten.

Hi, do you see the selected group at the display? If not, the button is not assigned correctly. How did you assign the meta event to the button? With the mk_syx script, or with vmidibox16e? Bear in mind that the upload via vmidibox16e doesn't work properly with all interfaces, it's better to use mk_syx which provides the new upload format Best Regards, Thorsten.

Hi, do you see the selected group at the display? If not, the button is not assigned correctly. How did you assign the meta event to the button? With the mk_syx script, or with vmidibox16e? Bear in mind that the upload via vmidibox16e doesn't work properly with all interfaces, it's better to use mk_syx which provides the new upload format Best Regards, Thorsten.

Hi Robin, first question: yes second question: yes (MIOS_PARAMETER1 won't be overwritten) third question: I'm not sure what you are planning to do exactly, but I want to warn you that the DOUTs won't be updated directly, but only every 1 mS Best Regards, Thorsten.

Must be an electrical problem (bad soldering, missing pull-up resistor, bad button), but why did you wrote about this at the programming board? Best Regards, Thorsten.

Must be an electrical problem (bad soldering, missing pull-up resistor, bad button), but why did you wrote about this at the programming board? Best Regards, Thorsten.

Thats a declaration error in the wrapper, I will fix this Best Regards, Thorsten.

Thanks for the input, Pilo! :-) nW: yes, you can use global variables. Just look into the generated assembler file to see what SDCC is doing with these variables. Yes, you need the preliminary release of MIOS V1.8, otherwise your program will crash due to overwritten FSR2[LH] More infos can be found at the MIOS C introduction page: http://www.ucapps.de/mios_c.html Best Regards, Thorsten.

Hi Nacho, this means that you forgot to disable the internal MIDI thru function of MIDI-ox which forwards incoming data to the output(s). This function disturbs the communication with the core and should therefore be deactivated: once you did this, deselect all MIDI In/Out ports and select them again (easiest solution), or modify your port mapping directly (expert solution) More details can be found at the Bootstrap Loader page: http://www.ucapps.de/mios_bootstrap.html Best Regards, Thorsten. P.S.: a Java based uploading tool which replaces MIDI-ox and is easier to use (since it doesn't provide so much options...) will be published in the next days

Hi *, you've possibly noticed that I haven't answered some of your postings in the last time although they were explicitely addressed to me. Since people started to send emails in the hope to get a response at this way, its possibly better to explain the reason here, so that I can simply refer to this article. I'm about to move to a new flat and therefore won't have so much time for MIDIbox tinkering and support in the next weeks. Instead I'm busy with renovation and organisatorical work - at least until end of August. When I feel boring I will possibly make some music or implement a new feature into an application (like every time when I start to make music ;-)), but please don't feel confused if you notice website changes or sporadic signs of life from me but nothing else... thanks for your understanding! I wish that all experienced MIDIbox guys are helping newbies more than before - don't let them down, remember the time where other people helped you. At the beginning it could be difficult to find the right tips, but from other people errors you will learn a lot - believe me! :) Best Regards, Thorsten.

Hallo, diese Frage koennte ich Dir evtl. beantworten, wenn Du mal mehr ueber Deine Beobachtungen bei den vorangegangenen Tests schreiben wuerdest - hast Du die Leitungen durchgemessen, wenn ja wie? Und mit welchen Resultaten? Hast Du ein Multimeter? Oder suchst Du nach einer alternativen Moeglichkeit zum Testen ohne Multimeter? Gruss, Thorsten.

And I hoped that you are learning from all the tips and code snippets that I gave you in the past... However, here the assembler variant... if it doesn't work immediately, please first try to find out the problem by yourself to avoid a massive attack of ping-pong mails here in the forum (e.g. check the main.err file) In distance to the C example this code sends the events via MIDI channel 16, because channel 1 should be reserved for the LC protocol ;; -------------------------------------------------------------------------- ;; This function is called by MIOS when a pot has been moved ;; Input: ;; o Pot number in WREG and MIOS_PARAMETER1 ;; o LSB value in MIOS_PARAMETER2 ;; o MSB value in MIOS_PARAMETER3 ;; -------------------------------------------------------------------------- USER_AIN_NotifyChange LC_MF_FaderEvent ;; save the fader number in LC_FADER_NUMBER movwf LC_FADER_NUMBER movlw 0x01 IFNEQ LC_FADER_NUMBER, ACCESS, rgoto LC_MF_FaderEvent_Not1 LC_MF_FaderEvent_1 movlw 0xbf call MIOS_MIDI_TxBufferPut movlw 0x10 call MIOS_MIDI_TxBufferPut movf LC_FADER_NUMBER, W call MIOS_AIN_Pin7bitGet call MIOS_MIDI_TxBufferPut return LC_MF_FaderEvent_Not1 movlw 0x02 IFNEQ LC_FADER_NUMBER, ACCESS, rgoto LC_MF_FaderEvent_Not2 LC_MF_FaderEvent_2 movlw 0xbf call MIOS_MIDI_TxBufferPut movlw 0x11 call MIOS_MIDI_TxBufferPut movf LC_FADER_NUMBER, W call MIOS_AIN_Pin7bitGet call MIOS_MIDI_TxBufferPut return LC_MF_FaderEvent_Not2 ;; the rest of the LC MF handler ;; ... ;; ... ;; ... LC_MF_FaderEvent_End ;; thats all return Best Regards, Thorsten.

Wow! I like this style, and the SID sounds are making the songs even more interesting :) Best Regards, Thorstem.

A MIDIbox made by Alex aka. "mb944" - he uses it for controlling Traktor: