TK.

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.

Do you have an explicit suggestion? (Reichelt part number) Best Regards, Thorsten.

Hi Robm, ok, this possibly wouldn't work with this low-cost solution due to the missing amplifier. And an amplifier would also require a schmitt trigger circuit to improve the stability. All this is integrated in the QT320 device (-> keyword hysteresis). You only have the connect the DINs with the appr. OUTx pins of the QT320. The programming of the sensor characteristics could also be done from a MIOS application, but it requires some programming skills... Best Regards, Thorsten.

Hi Pay_c, yes, this could be the reason, From the SID datasheet: "CAP1A/CAP1B/CAP2A/CAP3A - these pins are used to connect the two integrating capacitors required by the programmable Filter. C1 connects between pins 1 and 2, C2 between pins 3 and 4. Both capacitors should be the same value. Normal operation of the filter over the audio range is accomplished with a value of 1000pF for C1 and C2. Polystrane capacitors are preferred. In complex polyphinic systems, where many SID chips must track each other, matched capacitors are recommended. The frequency range of the filter can be tailored to specific applications by the choice of capacitor values. For example, a low-cost game may not require full high-frequency response. In this case, larger values for C1 and C2 could be chosen to provide more control over the bass frequencies of the filter. NOTE: Cut-off frequency variation may occur from chip to chip due to process variations, and power supply voltage. Capacitor values and voltage regulation can compensate for these variations." Sidenote: the suggested C1/C2 values are the same which are used in the original C64 designs. As the datasheet says, the best value differs with the chip version. Best Regards, Thorsten.

Wow, da ist sogar ein 82'er dabei! :) Hast Du die Bilder schon an Kubi geschickt? (http://www.kubarth.de/sid/index.html) Im habe ich auch schon seit Monaten ein paar Photos von meinen SIDs versprochen, aber man kommt ja zu gar nichts mehr... :-/ Gruss, Thorsten.

http://www.germankraft.de/ Best Regards, Thorsten (has got his tickets ;-))

Hi PW, what does the press say? ;D Best Regards, Thorsten. P.S.: Too all guys who don't know the famous MIDIbox magazine yet:

Oh, this has some historical reasons - in the first months I just wanted to prevent that everybody has to change the wiring of his box with every new release. The very first MB64 supported only 16 LEDs and 24 buttons, and I improved the driver successively. However, today the shift registers are freely assignable to the button and LED entries in main.asm (thats the purpose of the DIN_MAP and DOUT_MAP). Als the menu buttons are free assignable to any pin (not only to the first 64, but also to the remaining 64 digital inputs...) Best Regards, Thorsten.