TK.

Hi Goule, welcome back! Just added you to the programmers group ;) If you reduce the strings to 15 characters + terminator (CTL_NAME[16][8]), it will fit into 256 bytes, and it will also be easier to integrate this into a BankStick structure (2^n bytes should always be prefered) Best Regards, Thorsten.

Nice work, Nils! Do you allow me to add this demo to the webpage? Best Regards, Thorsten.

It was a quickfix (see troubleshooting section) base address of encoder table corrected (encoders were not working on new installations) I updated the changelog Best Regards, Thorsten.

Great! Please keep us up to date, especially about your album! :) Best Regards, Thorsten.

Hi, 9 should be bank 1-8 10 should be bank 9-16 (it's an documentation error in midibox64.ini) Best Regards, Thorsten.

Hi Crisp, just attach the schematic to this thread Best Regards, Thorsten.

The PCBs are look fine, thanks Nils! :) I will put the layouts on my website once the boards have been successfully tested by someone Best Regards, Thorsten.

Yes, the meters are much better, because with Reaktor I was able to construct my own "algorithm" :) It basically consists of a rectifier, amplifier, lin/log-converter, slew limiter (to smooth the waveform), sample&hold stage, step filter (events are only forwarded if there is a difference of >= 1) and CC output unit: 8 of these macros are stacked together, and the S&H stages are clocked at 50 Hz to reduce MIDI traffic: It looks simple, no? :) Best Regards, Thorsten.

I quickly hacked a MIDIbox based firmware for the Stribe project, and already had a lot of fun with it in conjunction with Reaktor. The released firmware is available in the MIOS download section Temporary updates can be found in the Repository Reduced MBHP_CORE circuit for Stribe board (can be soldered on the prototyping area). The Arduino modules are not required for this solution. More #1 More #2 More #3 More #4 The firmware is currently running on a PIC18F452, but future updates will use a PIC18F4620 (e.g. for optional OSC support) Best Regards, Thorsten.

I created a driver for the MAX7221 - the code could be used as basis for PWM chips as well. It works in assembler and C programs :) So, just tell me which chips you finally want to use, and I will add the appr. drivers to the project Best Regards, Thorsten.

Yes - since some days there are also C usage examples for GLCDs! :) Unfortunately they are based on the new project structure, which isn't documented yet. Basically, you would use a "MIOS base" package, which includes the drivers, include files, and even some graphical fonts - and your application itself would only contain a small set of files anymore. So, here is the C example: http://svnmios.midibox.org/trunk/apps/examples/lcd7/ks0108/c/ And here the graphic font package: http://svnmios.midibox.org/trunk/modules/glcd_font/ You won't be able to compile the code with the old approach that is currently documented on my website. Therefore I created a temporal package for you, which should give you a good starting point (instead of the global "mios base" structure, it uses a local file structure) -> http://www.ucapps.de/tmp/ks0108_c_example.zip In addition, you need to install the "posix_bin" directory as described here Best Regards, Thorsten.

Hallo, bei der MBSID V1 ist es normal, dass am Anfang SysEx Dumps and die Slaves gesendet werden - damit muss man leben. ;) Controller senden: ist die CC Funktion aktiviert? Dafuer gibt es eine eigene Taste (und LED) Gruss, Thorsten.

no, you can defined button numbers from 0 to 127 - hm, maybe the button function is overruled by an encoder entry? How does your encoder table look like? Best Regards, Thorsten.

Hi Keith, the usage of Meta Events isn't the right approach here, for your plans it's better to write a dedicated application based on the C wrapper. Many people already did this in the past, some of them introduced their project in the forum (unfortunately there is no complete list of projects, so you need to use the search function) Best Regards, Thorsten.

no - for more inputs you need something like the MIDI Router project Best Regards, Thorsten.

-> http://www.midibox.org/forum/index.php/topic,11115.0.html Best Regards, Thorsten.

Since the MIDImerger project is still quite popular, I created a new variant which is based on the PIC16F88. Not only that this chip is smaller and cheaper - it's especially possible to use it without external crystal with a sufficient accuracy :) -> http://www.ucapps.de/midimerger.html Best Regards, Thorsten.

I found the error: in mb64_lcd.inc, search for BRA_IFCLR MB64_CFG0, MB64_CFG0_SNAP, ACCESS, MB64_LCD_PrnVBar_Normal and replace it by BRA_IFCLR MB64_CFG0, MB64_CFG0_SNAP, BANKED, MB64_LCD_PrnVBar_Normal The change is already commited to the repository, and a new precompiled version will be released soon Best Regards, Thorsten.

Man koennte die MIOS interne merge Funktion einschalten, um eingehende MIDI Events weiterzuleiten (erfordert modifikation im Source Code), doch fuer Deinen Anwendungsfall ist das nicht empfehlenswert, denn der Clock wuerde dann mit einem Delay von mindestens 1 mS + Jitter weitergeleitet, ausserdem wuerde es auch die internen MBSID Timings zusaetzlich belasten (bspw. wenn soviele MIDI Events quasi gleichzeitig eintreffen, dass die In/Out Buffer nicht mehr ausreichen - in diesem Fall bleibt die Sound Engine solange stehen, bis die Buffer wieder frei sind) Geschickter waere es, der MBSID einen MIDI Thru Port zu spendieren. Man muss hierfuer kein komplettes MBHP_LTC Modul aufbauen, es reichen schon ein 74HC00 + DIN Buchse + zwei 220 Ohm Widerstaende auf Lochraster. So koenntest Du den MIDI Clock von Deinem Sequencer direkt an den Gameboy weiterleiten. Gruss, Thorsten.

Swinkels is currently very busy @work, therefore the documentation (schematics, etc...) hasn't been updated yet on his website, and the latest firmware isn't available as well. I recomment you to inform him about your interest, this can be very motivating :) In addition, somebody could support him by creating (and testing) a PCB layout for the stereo option? (I don't find the time for this, I built SwinSID on a veroboard...) Additional wiring

Both is strange. LCD: you considered the 4bit interface (D0-D3 should not be connected)? LCD interconnection test done? Strange Sound: it's interesting that the waveform and volume (or ADSR setting?) changes while you are playing different notes. It could either be a powering problem, connection problem or firmware upload problem - hard to diagnose via remote, but let's start with the power problem: does it also sound so strange when the LCD (and especially the backlight) is *not* connected? Best Regards, Thorsten,.

It definitely was the wrong topic (just consider, that other people should still be able to find informations about this issue some months later) Sounds like a bug, I will check this soon Best Regards, Thorsten.

Thats what I explained three times, please read my answers again. In difference to your explanation, I'm using the common wording which you can also find in your DAW documentation. Illusory I'm not interested in a cooperation with you - too different interests, and too time consuming ;) However, the most clever way would be to integrate the sequencer engine completely into the VSTi, and to communicate with external devices with the given interfaces (MIDI, USB, doesn't matter... it only depends on your programming skills) Best Regards, Thorsten.

Yes, especially when you are programming in Whitespace Best Regards, Thorsten.

http://www.midibox.org/dokuwiki/midibox_speakjet Best Regards, Thorsten.