TK.

Only problem: how to transfer the old forum articles to the SQL database? Best Regards, Thorsten.

Face lifting

no, it behaves correctly. A much more detailed list + schematics with measuring points can be found here: http://www.ucapps.de/howto_debug_midi.html Best Regards, Thorsten.

J2 can either be used as input or output, here it is used as 5V input. A connection via J1 is not required in this case. This saves some electronic parts Best Regards, Thorsten.

Hi Erik, ok, it seems that you've mixed the MIOS upload procedure with the configuration of a PIC16F based firmware. One reason again to discontinue the old stuff, it produces too much confusion and "communication effort". :-/ On a PIC16F firmware the black bar should disappear immediately after power-on (note for MIOS users: it disappears during the boot phase, ca. 2 seconds after power-on) If the bar is still there, your display is not connected correctly or your PIC is not running. Is there any sign of life from your PIC (MIDI messages on pot moves?) Best Regards, Thorsten.

Hi Christoffer, well done! Looking forward for some audible impressions :) If you want to enjoy the advantages of the upcoming features, use the PIC18F - I will also replace the PICs of my slave modules sooner or later. Best Regards, Thorsten.

Hi Klass, I'm using the MAX6007B as 2.048V voltage reference and the LM324 as amplifier to extend the voltage range. This makes the AOUT module more flexible for different CV requirements - there is no need for a second voltage reference. Best Regards, Thorsten. P.S.: although this schematic is preliminary, it's already working very fine :)

Hallo Yamboo, schau mal in das main.asm File, dort steht beschrieben, wie man die Bildschimausgabe auf die verschiedenen Displaytypen mapped. Gruss, Thorsten.

What prevents you from adding the "CC on/off' button? Best Regards, Thorsten.

Custom MIDI messages are already possible with every MIDIbox, they can either be configured on-screen via MIDI learn or direct modification, they can be configured with the mk_syx script or with the vmidibox editor from a PC/Mac But multiple MIDI messages triggered by a single button/pot/encoder/fader/etc... can only be realized by implementing Meta events, and I don't plan to change this since a lot of (wasted) memory would have to be reserved for such a feature which is only used by 1% of all users... so - it's better to implement a dedicated application of you need on-screen editing of multiple events. MIOS provides all the basics, only the user interface has to be implemented (programming effort: ca. 2-3 months) Best Regards, Thorsten.

Which control unit do you mean exactly? MIDIbox SID? See this page http://www.ucapps.de/midibox_sid_cs.html Best Regards, Thorsten.

yes, a 2x20 display will working a 4x4 field at the right side will left blank. You need to change the source code if you want to display additional informations if no pots are connected: clamp the unused analog inputs to ground!!! if no buttons are connected: don't forget the 10k pull-up resistors!!! what do you mean exactly? PSU: just send me the current layout of your PCB Best Regards, Thorsten.

The DINX1 circuit is so simple that you don't need a PCB or vectorboard layout, just take a look into the schematic Best Regards, Thorsten.

1) yes, you need to add an entry in the encoder table assigned to volume. However, my suggestion would be not to control it digitally (since the resolution is only 4 bit!) but to control the volume from the analog output 2) will be implemented sooner or later (in 2-3 months when other tasks have been finished) Best Regards, Thorsten.

Die MB64SEQ ist ein offenes Design, da lassen sich noch eine Menge Optionen unterbringen. Per default wird die Applikation so konfiguriert sein, dass sie mit meiner bestehenden MIDIbox64 und MIDIbox LC Hardware perfekt zusammenspielt, und wie die aussieht, ist ja bereits dokumentiert. Du moechtest fuer jedes Poti eine eigene LED - kein Problem, wird es optional geben, kostet mich vielleicht 10 Assembler Zeilen. Was noch? Gruss, Thorsten.

yogurt

You can use CC #12 to switch between different wavetables w/ zero latency. However, only the wavetable will be changed and not the other sound settings. If more flexibility is required, I highly suggest to sample the sounds and to play it with the sampler - thats the common way with synthesizers Best Regards, Thorsten.

It's called "Lötlack" (loetlack w/o umlaut) Reichelt ordering #"Kontakt 227" (200 ml) or #"Kontakt 228" (400 ml) Mike uses the same spray for his PCBs - maybe it wasn't enough on yours (my PCBs are still ok after more than one year) Best Regards, Thorsten.

Hi Shar, the current applications don't allow to realize this without recompilation. Keyword: Meta events Source code: mb64_meta.inc Best Regards, Thorsten.

Hi Nos, are you using the PIC16F or MIOS based MIDIbox64? PIC16F: won't work due to the debouncing feature which has been implemented for cheap buttons and cannot be disabled w/o other restrictions. It could work with MIDIO128 when the update frequency is decreased to 1 mS MIOS: just open the main.asm, set the DEFAULT_SRIO_DEBOUNCE_CTR to 0, reassemble and upload the new code and it will work. If the trackball provides the same signals like an incremental encoder (2 outputs, gray code), you could also define the two DINs as encoder input in mios_tables.inc and add a special handler which sends (for example) Inc/Dec MIDI events (CC #0x60 for increment, CC #0x61 for decrement) Best Regards, Thorsten.

Hi, do you know the resistance of the faders (values between 1k and 10kOhm are ok) and the output curve (must be linear, logratihmic faders/pots won't work) Best Regards, Thorsten.

Hi Iain, MIOS supports 128 digital inputs, but the MIDIbox64 application has been designed for 64 buttons to keep it compatible with the established data structure. I don't plan to change this data structure since it would require a lot of effort (not only on the application side, but also the documentation and the editors would have to be changed....). So, there are two solutions: either you enhance the application by yourself so that all 128 digital inputs are working as MIDI triggers (for static MIDI events it's very easy, for customizable events the effort is very high), or you wait for MIDIbox NG (see: http://www.midibox.org/cgi-bin/yabb/YaBB.cgi?board=news;action=display;num=1065215244) which will be hardware compatible, but will open much more additional possibilities w/o changing the source code. Of course, the MIDIO128 application uses the same core module, and it's also possible to upload the code on a MIDIbox64 within 5 seconds... but it isn't possible to use both applications at the same time. Best Regards, Thorsten.

Ist bereits zu 80% komplett, habe allerdings schon seit drei Wochen nicht mehr daran gebastelt, weil andere Sachen dazwischengekommen sind, die nicht weniger interessant waren (Stichwort: AOUT) An den naechsten beiden Wochenenden bin ich nicht zuhause, vielleicht klappt es aber mit der finalen Release noch vor Weihnachten. :) Gruss, Thorsten, P.S.: achso, wer eine halbfertige Alphaversion testen moechte, schreibe mir einfach eine PM ;-)

Edelweiss

Hi LO, so I think the reason is clear, the digital signals of the MIDI connection have influence on the analog signals. The proper solution: use two seperate shielded cables or use a cable where every single wire is shielded to ground. To the non-insulated cables: connect them all to ground, maybe this already helps. This could also help. You're avoiding a ground loop in this way which can also influence the analog signals. Best Regards, Thorsten.