TK.

I've currently no clear picture of what you are trying to do, therefore I cannot give you a clear answer. I asked for the MIOS application, because the implementation will heavily depend on the program which has to be modified. E.g., the MIDIbox64/64E is programmed in assembler, the MIDIbox LC (new version) in C. On the other hand: in my oppinion it is not really useful to integrate flashing LEDs into a Logic Control emulation, because the host flashes the LEDs by itself if required. E.g., when you select the Solo button, the Mute LEDs of all not-soloed tracks will flash. An additional flash algorithm from MIDIbox internal would propably only confuse. Best Regards, Thorsten.

Hi Gerald, it sounds like the power routing is not correct, if Vs and Vd are not connected, the ICs are powered through the data lines, and this can cause such effects. J1 seems to be ok, so check especially J2 (the 5V domain) No, the Vs pin of J1 should be left open if the wiring is based on the mbhp_4xsid_c64_psu_optimized.pdf diagram, otherwise you would get a ground loop which would increase the background noise Best Regards, Thorsten.

Hi Jens, I was able to reproduce issue 2) - I will fix this in the next version 4) the combination SIDx + menu button is really clever, I will go for this solution (about 10 lines of additional code...) Best Regards, Thorsten.

It's now possible to switch between the pattern sets in v2.3 Best Regards, Thorsten.

The change is now available in v2.3 Best Regards, Thorsten.

A new release with some nice new features :) From the ChangeLog: MIDIbox64SEQ V2.3 ~~~~~~~~~~~~~~~~~ o the clock can now be divided by BPM/1,2,3,..15,16 for each track seperately. Before this change it was BPM/1,2,4,8,16,32,64 It's possible to switch back to the old behaviour with the DEFAULT_BPM_DIVIDER_BEHAVIOUR switch in main.asm o the song menu handling has been overworked: - for 2*2x40 LCD option, there is now an additional info screen at the right side (second display) - song mode can be enabled/disabled in song menu by pressing the SONG button (again) - if not in song mode, the pattern set will be changed immediately (see usecases below for the reason) - song position now named A1..P8 instead of 1..128 for easier orientation - song positions are now divided into parts A..P, each part consists of 8 pattern sets, each pattern set can be looped up to 16 times. - song number, song position, loop/jumps now controllable with the general purpose buttons Usecases of the new song handling: a) for song mode enter the song menu and press the button twice. Press the "A" button + one of the 16 GP buttons to select the song Press the "B" button + one of the 16 GP buttons to select the part -> the sequencer will change to the part immediately, if the sequencer was not running before, it will be started automatically b) this allows you to divide a song into multiple parts. At the end of a part, you can either set a jump to the first step of the part (so that the part loops), or you can set a jump to the next part. Note: if a song part consists of 8 song positions, it is not possible to set an additional jump. The sequencer will jump to the next part automatically (this ensures compatibility) c) it's always possible to change the part during the sequencer is running - it won't affect the realtime behaviour :) This allows you to change between breaks/fills/chorus or whatever during a live session d) If you don't want to use the song mode, the new handling is still useful for you - it allows to save up to 128 pattern sets within a song. Press the "A" button + one of the 16 GP buttons to select the song Press the "B" button + one of the 16 GP buttons to select the part (this already provides a quick access to 16 pattern sets) Turn the datawheel to select pos 1..8 within a part Similar to song mode, changes will take place immediately without affecting the sequencer timings. The selected pattern set will loop endless until you are changing to a new one [/code] Best Regards, Thorsten.

Great! Looking forward for the public version! :) Best Regards, Thorsten.

The updated file can now be downloaded from this URL: http://www.ucapps.de/midibox_sid_cs/mbsid_panel2fix.dwg Best Regards, Thorsten.

Hi George, MIOS standalone is ok, but once you got the MIDI interface running, it would be better to burn the bootstrap loader into the PIC and to upload MIOS through MIDI. Because this allows you to update MIOS in future without PIC burner. However, MIOS itself provides a seperate BSL, so you should be able to upload an application via MIDI (hope that the troubleshooting guide helps...) Best Regards, Thorsten.

Hi Lorin, definitely! The example track sounds very impressing, I would build one! :) Maybe I can help you to port hardware and code to the MIOS platform - are you planning an open source release? Best Regards, Thorsten.

Hi Taylor, normaly it can be programmed into the application, MIOS code doesn't need to be touched. Which application are you using exactly? Best Regards, Thorsten.

Hallo Torben, mit diesem MIDI Merger geht das nicht - MIDI merging mit mehreren MIDI Ins ist nicht trivial (deshalb gibt es so etwas auch nicht zu kaufen) - heutzutage bevorzugt man meistens PC/Mac Interfaces mit mehreren IO Ports, und routed die Ein-/Ausgaenge direkt in der Host Software. Gruss, Thorsten.

Alright - now I see the error (in the outdated .gif file). I'm not able to view the .dwg file (it's from Klingen) - I will ask him for an update Best Regards, Thorsten.

Hi Alkex, the displaytech LCDs which I'm normaly using are also stuffed with a KS0066U controller - it's 100% compatible, but (and this is good!) faster than HD44780 Best Regards, Thorsten.

Hi, I think it's better to answer your questions in the SID boards, since some are "FAQ"s 1) yes, it's not possible to select the BankStick with JSynthLib - the core library doesn't prove such a opportunity, as a JSynthLib user I'm "mightless" It's also a known problem that the "get" function doesn't work properly - in the meantime this concept has been changed (you could download the latest sources from the CVS), but it's not complete yet and a little bit buggy... 2) which patch? 3) known and intended behaviour, the reason can be found here http://69.56.171.55/~midibox/forum/index.php?topic=4878.0, an improvement is also built into the current beta version of v1.7303 which is available on request 4) I see the point - yes, it could be useful (especially for the TB303 emulation) - which button combination would you prefer as a shortcut for such a function? Best Regards, Thorsten.

You could implement this via software to save hardware costs... Best Regards, Thorsten.

Hi, you should hear a nice PWM patch after you've uploaded MIOS and the main.syx (or any other .syx of the midibox_sid_* package). I guess, that there is a problem with you hardware - did you try the SID interconnection test? Best Regards, Thorsten.

Hi, the button handlers are in cs_menu_button.inc Using switches instead of buttons shouldn't require big changes Best Regards, Thorsten.

Hi Chriss, undo your changes and add following lines to cs_menu_button.inc CS_MENU_BUTTON_Ins1 bcf CS_MENU_MODE, CS_MENU_MODE_INS_OP movlw 1 << 0 rgoto CS_MENU_BUTTON_InsOP_Cont CS_MENU_BUTTON_Ins2 bcf CS_MENU_MODE, CS_MENU_MODE_INS_OP movlw 1 << 1 rgoto CS_MENU_BUTTON_InsOP_Cont CS_MENU_BUTTON_Ins3 bcf CS_MENU_MODE, CS_MENU_MODE_INS_OP movlw 1 << 2 rgoto CS_MENU_BUTTON_InsOP_Cont CS_MENU_BUTTON_Ins4 bcf CS_MENU_MODE, CS_MENU_MODE_INS_OP movlw 1 << 3 rgoto CS_MENU_BUTTON_InsOP_Cont CS_MENU_BUTTON_OP1 bsf CS_MENU_MODE, CS_MENU_MODE_INS_OP movlw 1 << 0 rgoto CS_MENU_BUTTON_InsOP_Cont CS_MENU_BUTTON_OP2 bsf CS_MENU_MODE, CS_MENU_MODE_INS_OP movlw 1 << 1 rgoto CS_MENU_BUTTON_InsOP_Cont CS_MENU_BUTTON_OP3 bsf CS_MENU_MODE, CS_MENU_MODE_INS_OP movlw 1 << 2 rgoto CS_MENU_BUTTON_InsOP_Cont CS_MENU_BUTTON_OP4 bsf CS_MENU_MODE, CS_MENU_MODE_INS_OP movlw 1 << 3 rgoto CS_MENU_BUTTON_InsOP_Cont [/code] Best Regards, Thorsten.

Hi Jorge, please believe me: there is no error in the released files, you will only find this mismatch at a picture of my own SID case. You are writing about the OSC section (which provides a DADSR curve) - pwx wrote about the ENV section. Best Regards, Thorsten.

Hi. this is a common HD44780 compatible LCD, it should work without problems. Quality would also be interesting for me - it would be a great alternative display! Best Regards, Thorsten.

Hi Moxi, pattern sets can be saved within a song. Since a song has 128 positions, you can save 16*128 different setups there. Once I've enhanced the song mode (see previous mails and ToDo list), it will be possible to recall the setup without pressing the "play" button before. Also quick changes will be possible (e.g. with an external keyboard) Best Regards, Thorsten.

Hi Chriss, this should be possible by changing the CS_MENU_BUTTON_InsOP_Cont in "cs_menu_buttons.inc" . Currently it either moves the pointer to CS_MENU_SELECTED_INS_FLAGS or CS_MENU_SELECTED_OP_FLAGS into FSR0 depending on the CS_MENU_MODE_INS_OP flag... Quick change: add four additional OP button functions and set the CS_MENU_MODE_INS_OP flag there. Clear this flag within the instrument button functions Best Regards, Thorsten.

This is a really fancy MIDIbox64E made by Moxi! He wrote:

Hallo Andreas, dies ist eigentlich kein generelles PIC Programmierer-Forum, hier geht es hauptsaechlich um MIOS Projekte. Aber ich kann Dir zumindest den Hinweis geben, dass an einigen Stellen das Bus-Protokoll nicht eingehalten wird. So z.B in folgenden Zeilen: MOVLW B'00001000' ;Display AUS MOVWF PORTB CALL Pause2 MOVLW B'00000001' ;Clear Display MOVWF PORTB CALL Pause2 [/code] ich vermisse den Strobe (E=0 -> E=1 -> 2 NOPs -> E=0). Unter http://www.ucapps.de/mbhp/prg/lcd_v1.zip findest Du einen Beispielcode fuer meine alten PIC16F basierenden Projekte, vielleicht hilft es weiter. Die Bank-Warnungen habe ich mit: ERRORLEVEL -302 ; SUPPRESS BANK SELECTION MESSAGES deaktiviert (man muss beim PIC16F hoellisch auf die Bank Selection bits achten...) Warum ein Stack Underflow auftritt, kann ich auf anhieb nicht sagen. Evtl. liegt es daran, dass die Start Routine nicht sauber abgeschlossen ist. Nach dem letzten CALL befindet sich nichts mehr - der PIC wird hier beliebigen Code ausfuehren. Es waere besser, das Programm mit einer Endlos-Schleife zu beenden Gruss, Thorsten.