TK.

Reducing the resolution is propably not what he want... He could also reduce the update rate by disabling the "dynamic priority" feature with MIOS_AIN_DynamicPrioSet(0). This will result into a static update rate of "number_of_pots * 200 uS" for each pot, accordingly when the number of pots is set to 64 (all unused analog inputs have to be clamped to ground), this will result into a delay of 12 mS, which is propably enough. And if this doesn't help, he could modify the TMR0L reload value in mios_isr.inc, IRQ_Timer0, but this requires a manual change in MIOS. It's not controlable from the application, since such a flexibility was not required yet... Best Regards, Thorsten.

Dein Gehaeusedesign ist wirklich sehr individuell! :) Gruss, Thorsten.

maybe I could explain you what I meant? I would tell you the background behind this "trick", if I would know if it is worth the effort... Best Regards, Thorsten.

Hi Alex, the presets can be edited in cv_presets.inc Best Regards, Thorsten.

I will add the possibility to connect a LED for Play and Pause into MBSEQ V3, and an untested BPM LED digit output as well. For the 3 digits you will need one DOUT SR for the 8 segments, and 3 free DOUT pins for the cathodes Best Regards, Thorsten.

This topic has been moved to Miscellaneous. [iurl]http://www.midibox.org/forum/index.php?topic=7721.0[/iurl]

This topic has been moved to Miscellaneous. [iurl]http://www.midibox.org/forum/index.php?topic=7767.0[/iurl]

really nice design! Best Regards, Thorsten.

This is the MIDIbox64 made by Danial aka. URBatORB - he built it into a selfmade wooden box, but considers to replace the frontpanel (+covers) by alu. However, it already looks very functional! :) He wrote (in german):

Hallo Lemonhorse, irgendetwas ist mit Deiner Datenhaltung nicht in Ordnung - in der offiziellen Release steht der Eintrag auf 5. Ich habe gerade den Wert 4 ausprobiert - funktioniert. Ich kann mich erinnern, dass es in irgendeiner Beta Version schonmal Probleme mit diesem Setting gab, doch die sind schon laengst gefixed... Gruss, Thorsten.

Ja, Microchip hat den EUSART Bug nicht gefixed, insofern ist das MBHP_IIC_MIDI modul fuer eine MBSID V2 mit einem oder mehreren Slaves zwingend notwendig. Und: evtl. werde ich bereits in die MBSID V1 eine Option einbauen, mit der die Slaves einen eigenen MIDI Out erhalten. Vorteil: so kann man Automatisierungsdaten getrennt an den PC senden, ohne dass eine Rueckkopplungsschleife entsteht. Fuer diese Option benoetigt man ein weiteres MBHP_IIC_MIDI Modul Gruss, Thorsten.

Hi, MIOS itself doesn't allow to throttle the MIDI bandwidth, but maybe there are tricks to achieve the same without writing an own handler which delays SysEx messages: you could send some 0xfe events after a SysEx message - each 0xfe will cause a delay of 320 uS, and they should be ignored from the Synth A proper solution would require some more effort at the application side Best Regards, Thorsten.

As a nice programming experience, porting MIOS to other microcontrollers isn't a bad idea. The OS itself isn't tied that much on the uC architecture (so long the applications are programmed in C). I for myself would never spent the effort to write a port for just another 8bit micro, but intellijel: if you want to do this for the AVR, the final results (e.g. performance) would be interesting! Best Regards, Thorsten.

Here the same question: did you use a DIN_R3 board from SmashTV? Some pins are not where expected, see also the errata http://www.avishowtech.com/mbhp/mbhp_dinR3.html Best Regards, Thorsten.

Are you using a DIN_R3 board from SmashTV? Some pins are transposed, see also the errata at http://www.avishowtech.com/mbhp/mbhp_dinR3.html Best Regards, Thorsten.

This posting has disappeared after the server crash, so here the next attempt: This is the MIDIbox SEQ V3 built by Rio, who didn't hesitate to use the new firmware, even it's very bad documented. Note the 4 individual MIDI Out ports: :)

The problem is, that the menu pages are organized for 2x40 usage (8 buttons below the menu items). Also the main page doesn't wrap so nice on a 4x20 screen Best Regards, Thorsten.

You could organize a "group buy" for special parts in order to get better prices... Best Regards, Thorsten.

Hallo Lemonhorse, ein 2x16 LCD ist nach wie vor erlaubt, Du musst jedoch in main.asm (bzw. im setup_* File, welches Du verwendest), den Eintrag: #define CS_MENU_DISPLAYED_ITEMS 5 auf 4 setzen Gruss, Thorsten.

Really great frontpanel work! :) Is this ready for the MIDIbox of the Week section? :) To 3): you have to select the encoder type "MIOS_ENC_MODE_DETENTED2" in setup_mbseq_v2.asm In MBSEQ V3 I will make this as the default encoder type, since this is the right one for Voti's and SmashTV's encoders To 2): it makes sense to debug the DINX4 modules, I wrote down some informations about this here: http://www.midibox.org/dokuwiki/doku.php?id=din_module Best Regards, Thorsten.

Hi, normaly I avoid the use of special chips for MBHP, because they increase the complexity and the support effort. In addition, everything which can only be purchased from a small number of distributors should be avoided, since this increases the shipping costs and ordering effort. Best example is the MAX525 - many people suggested this chip years ago, finally I put this into the MBHP, but at the end there is only a small number of people who really built the module (due to the high costs), and we still have no "cheap&simple" solution for a CV converter (assumed that the MBHP_AOUT_LC is only for freaks with enough endurance for soldering so many resistors). To the MAX7221: it's a nice chip, but temporary not available at Reichelt, which could mean, that Maxim is going to discontinue it. Unfortunately this happens very often... :-/ Best Regards, Thorsten.

For a filter example, see this posting: http://www.midibox.org/forum/index.php?topic=6542.0 Can your TX81Z do the same? ;-) Yes, the outputs are noisy! Best Regards, Thorsten.

So far I remember, the current bandwith is about 20GB/month, it increases non-linear (we had about 15GB/month last year) However, there is no need to move server, I'm very happy with the current solution, it runs much more stable and really fast compared to the servers we had ca. 3 years ago! Can't thank Twin-X often enough! :) Best Regards, Thorsten.

I thought that the informations in the FAQ are sufficient for deciding, if a MBHP_IIC_MIDI module is required or not. If you want to have an easy answer: yes, under normal circumstances it's required for MBSEQ V3 - and since MBSEQ V3 supports up to 4 IIC_MIDI modules for 4 seperate MIDI outs, this approach also brings some advantages. Best Regards, Thorsten.

Hi, could it be that you've mounted the MAX232, but want to use the "normal" MIDI In/Out ports? Best Regards, Thorsten.