TK.

it's realized in a way like I would implement it with hardware (I had some flip flops in mind ;-) Did you also notice the credits in seq_scale.inc? :) Best Regards, Thorsten. q

Hi, yes, each OPL3 chip requires a dedicated core - the application is already extremely busy (more busy than the MBSID) due to all the software engine features, no chance to control an additional OPL3 Best Regards, Thorsten.

Hi Chris, it seems, that a track between the 7805 and pin 31/32 is broken, this might affect port J10 as well, accordingly the supply of the SID module You can follow the tracks with the probes of your measuring instrument in order to find the location, where the track is broken or "interrupted". It could also be a bad soldering joint, but this is hard to say w/o knowing, which board version you are using Best Regards, Thorsten.

How about MIOS_ENC_MODE_DETENTED2? See also http://www.midibox.org/dokuwiki/doku.php?id=encoder_types Best Regards, Thorsten.

Yes, all 7 buttons of CS Step B don't have an appr. menu entry Best Regards, Thorsten.

Since in the meantime so many people request to join the alpha testing phase, I'm now distributing the current snapshot under ucapps.de/tmp. The current build is located under: expired I will only add a short notification to this article whenever I update the package, changes are documented in the CHANGELOG.txt file Best Regards, Thorsten. Edit: this thread is expired, MIDIbox SEQ V3.0 has been officially released under http://www.ucapps.de/mios_download.html

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

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.