TK.

I must say that I don't have a clear oversight over all the different versions and revisions. You could compare the layout with the schematic in order to find this out. You can also run the interconnection test to check the pinning if you are unsure. Best Regards, Thorsten.

Hi, the link to the .jpg file doesn't work. However, from the specs this seems to be a simple and good working configuration. Not sure about the VU meters, but from my experience transmitting them via MIDI is not accurate enough, better to build a analog circuit here Best Regards, Thorsten.

[@uote]When I upload any SID app, I start to get a high pitched tone from the audio output than never stops untill I reload MIOS again. Does this mean the PIC is ok, bad wiring or dead sid? you don't need to reload MIOS again, MIOS is not windows... ;-) If you get a high pitched sound, it could be, that the interconnections are not correct, or that there is a short. The mbsid_interconnection test helps to debug this, but you need to upload the .hex file, not the .syx file! Thereafter read the debug instructions in main.asm (or README.txt, don't remember). Best Regards, Thorsten.

it tells you, that the bootloader is up-to-date MIOS Studio doesn't support the required "delay after F7" function, therefore you cannot send .syx file properly with this tool. I know this is not obvious for a newbie, and have Adam informed about this Could it be, that your core is already running properly? Best Regards, Thorsten.

Hi, you only need to follow the instructions on these pages: http://www.ucapps.de/mbhp_core_old.html http://www.ucapps.de/mbhp_sid_old.html Best Regards, Thorsten.

Hi, the PSU requirements which are mentioned at the MBHP_CORE page mainly consider the usage of a single 7805 for multiple core modules. But in your case this is not recommented. Just stuff all components, and power the core modules via Port J1. You can use a single voltage source for this, if it is strong enough (this depends on how many LCDs and LEDs should be driven) You don't need to modify the firmware in order to chain two MIDIbox64, this configuration can be done within the MIDI menu. The first MIDIbox in the chain has to be configured as "MIDIbox Link Forwarding Point", and the second as "MIDIbox Link Endpoint" Best Regards, Thorsten.

Which file of the update package is uploaded here? Did you read the comments in README.txt? Best Regards, Thorsten.

Hallo, wenn sich die LEDs (DOUTs) nicht ansteuern lassen, dann liegt es wohl am SC, SR oder DO Signal (Kurzschluss?). Mit dem srio_interconnection_test kann man diese Signale testen. Gruss, Thorsten.

Yes, this is possible - you can request a SysEx dump with Serge's MIDIbox Editor, thereafter you can save the bank as .ini file, and edit it like before. To ensure that nothing gets unintentionally lost (e.g. for the case that you click the wrong button), you could create a full backup of the flash and EEPROM contents like described here: http://www.ucapps.de/mios/mios_backup.txt Best Regards, Thorsten.

Here some pictures of Sasa's Traktor Controller. He wrote: What a fantastic work!

P.S.: if compatibility does matter, you could write a custom LCD driver instead of switching between the displays via MIOS_LCD_Init A CLCD custom driver is already available, you only need to redirect the enable lines depending on the cursor position Best Regards, Thorsten.

LCDs cannot be cascaded, the data and control lines have to be connected in parallel, and the enable lines have to be controlled seperately. By using the MIOS_LCD_Init function with different parameters for IO pin assignment of the enable line, you can select as much LCDs as IO pins are free. Anyhow, you will need to adapt the software... if you build up an application from scratch, this will be easy. If you are trying to consider LCD switching in an existing application, it will be a lot of effort Best Regards, Thorsten.

I second that, 32 buttons/LEDs are very important, the additional LEDs not at least to display the current sequencer position correctly. A roll function (selectable like the accent for each step seperately) would be usefull as well Best Regards, Thorsten.

it's not recommented, especially if you want to use the MBSEQ V3 firmware later, where I won't support other display options than 2*2x40 LCDs anymore - with the advantage, that I have the freedom to totally customize the screen layouts This is, how the V3 screen currently looks like: Best Regards, Thorsten.

This is the new red-blue housing for two SIDs, made by Rio :)

Hi Shum, so far I remember, after the installation of the yamaha driver, there should be a new icon in the system setup directory (where you also setup the display, the soundcard, the network, etc...) - click on this icon, and you should be able to select the COM port. Regardless of the selected COM port, MIOS Studio and MIDI-Ox should already list a new MIDI interface, do you see it? Best Regards, Thorsten.

If Trevor has no problems with this, it's ok. Nevertheless, I would mention the original name in each re-used file, regardless if (small) modifications have been made or not. It's just good style To the CC - in the FAQ http://creativecommons.org/faq#Can_I_use_a_Creative_Commons_license_for_software? you can read: Can I use a Creative Commons license for software? Creative Commons licenses are not intended to apply to software. They should not be used for software. We strongly encourage you to use one of the very good software licenses available today. [/code] either GNUPL if it's ok for you if somebody uses the code commercially (e.g. sells your projects on Ebay for profit), or no "copyleft" license at all, but just something like this hint, which can be found in most of my projects in the meantime: [code] ; Copyright <date> <name> ; Licensed for personal non-commercial use only. ; All other rights reserved. Best Regards, Thorsten.

What I don't like on this project is, that he is using Trevor Page's source code, and replaced the copyright by his own. And he uses a license which is not intended for software. Best Regards, Thorsten.

Hi Moxi, yes, this is normal for all newer releases, since it was too difficult to keep this file up-to-date for all the different MPLAB versions (I don't use it) The recommented build process is described here: http://www.ucapps.de/howto_tools_mpasm.html Best Regards, Thorsten.

Still works fine and makes fun - next target is to enhance the track length of MBSEQ to 32 steps, this can take some time, since a lot of code has to be changed... however, I've a new motivation to finish this soon ;-) Best Regards, Thorsten.

Found the solution: the trigger event controls some S&H modules, and they can be bypassed. So, it seems that 4 assignable parameters and the gate can be controlled via MIDI (I haven't tried this under realtime conditions yet), each sample module can be assigned to a seperate MIDI channel - nice toy! Best Regards, Thorsten.

I'm just doing the changes in Massive 1.1 for MIDI control over the sample modules. It isn't so easy like expected, because the voices are using some kind of multiplexing in order to transmit values and events over a single wire (Smpler Macro, G input). I found out how to control the gate and the "yellow" parameter (normaly assigned to velocity or pitch), but the pitch value is only taken when two pulses are sent over the "2trg" line. However, I will keep trying. There is at least the possibility to remove this multiplexing completely (but it's a "Massive" change ;-) MBSEQ V3 will support a configuration, where for example two CCs and one note (gate) with variable length is sent from a single track - this is ideal for controlling the Massive sample modules (I see it now as one of the reference applications) Best Regards, Thorsten.

I haven't read the complete thread, but if you only need an hint how to measure a data rate: just count the ticks within a constant time span, and capture/reset the counter periodically, e.g. from the Timer() function. It's the same approach like discussed here http://www.midibox.org/forum/index.php?topic=3858.0 Best Regards, Thorsten.

Hi Evan, welcome to the forum! I'm a Reaktor user since R3. I don't use it so often (since I'm more busy with MIDIbox development than making music), but it's always big fun to play with it. E.g., for these arpeggiator examples: http://www.ucapps.de/midibox_seq_tutorial4.html I used the Junatik synth. In the first (experimental) MBSEQ demo at my website I used a slightly modified Vierring filter. I replaced the integrated step sequencers by generic CC receivers, and controlled them from the MBSEQ. I think, that a similar approach is possible with Massive Attack - I will try this out this evening (thanks for the inspiration!) I'm currently working on MBSEQ V3, and this is a nice check for all the mods I made today. Best Regards, Thorsten.

Mir ist eingefallen, dass bei der LED Matrix Option die Shift Register ("DEFAULT_TRACK_LEDS_*_CATHODE") falsch zugewiesen waren. Darueber sind schon zwei Leute gestolpert... Du wahrscheinlich ebenfalls. Die Version v2.4b gibt es nun an bekannter Stelle Gruss, Thorsten.