Rio

Hey ok, so did you test the PICs with MIOS Studio ? All I know, it’s hard to damage PICs… maybe the untouched ones give a livesign for their ID there. Maybe someone has experience with PICKit2 for that chips, if you stuck in any case... I'm interested in the result, if it worked well with the pickit2… Good luck, greetings rio

Are you sure that you fried it? Maybe only the mios/bootloader needs to flash again (http://www.ucapps.de/mios/mios_v1_9h.zip). Therefor you need to upload mios til 2 seconds after switch on! It should show READY afterwards… Please try it first. Pay attention about yoir PIC Ids too. You have to chose the correct Id inside mios studio. It also possible to change the ids via http://www.ucapps.de/mios/change_id_v1_9g.zip greetings, rio

Hehe - 17 years! Enormously to see the evolution. For me the most useful features are: - mixer - router - track options, especially the transpose option - massive support of ports ... these controller options right on the board saved additional equipment (and the associated complex handling) - everything can be automated in all. very well thought out. Greetings, rio

Hey TK, Thank you very much for your efforts on the MBSEQ firmware ... when did it all start? It is already a life's work ... Awesome: D Greetings, Rio

Thanks for detailed Infos. maybe it will be good next time to commit what has been changed and for which variant it is (or affects). Thanks and greetings, rio

Ok, and what has changed in rev. 2597? Please can you explain it to me? It affects TPD and blm8x8 sources - or I am wrong? greetings, rio

It is not good to use further check-ins in this way ... the branch was always cleanly maintained for years. I use the master branch all the time for my V4. At this point, I'm not sure if I can continue build releases from that branch.

Please can anyone explain me what the last commit 2597 in repository means: It is a bugfix or a discussion? It isn‘t clear for me … Is it v4 related or only v4+? If I take a look inside source, it’s more blm8x8 related, right? I hope the master branch will not mixed up for uncertain testing purposes… greetings. Rio

Have fun with your new baby ;)

Hi beautyofdecay, i want buy a set of line driver (Rx / Tx) boards. I am from Germany. Please contact me via PM :) Greetings, rio

Unfortunately, I do not have enough idea of asm, but I was able to implement at least a CC 120 (for a chosen midi channel), which reloads the same preset, which internally resets the registers. Maybe it is useful for someone to manually delete the hanging tone. At least you have to add following code in these files: sid_midi.inc (insert before CC 123 detection: --> ;; check if All Notes Off (CC#123 == 0)) ;; ####################################################### ;; # CC 120 reload preset ;; ####################################################### ;; check if CC 120 (CC#120) movlw 0x78 cpfseq SID_MIDI_PARAMETER1, BANKED rgoto SID_MIDI_CC_NoInitPreset movf SID_MIDI_PARAMETER2, BANKED bz SID_MIDI_CC_NoInitPreset SID_MIDI_CC_InitPreset goto CS_MENU_MS_NotifyInitPreset SID_MIDI_CC_NoInitPreset ;; ####################################################### ;; # END MODIFICATION ;; ####################################################### cs_menu_ms.inc (insert before program change routine -> ;; This function is called to forward a Program Change event to the control surface) ;; ####################################################### ;; # init/reload preset routine ;; ####################################################### ;; -------------------------------------------------------------------------- ;; This function is called to forward a Init Preset event to the control surface ;; Input: ;; o midi channel in SID_CURRENT_CHANNEL ;; o patch number in SID_MIDI_PARAMETER2 of INDF0 lower value ;; -------------------------------------------------------------------------- CS_MENU_MS_NotifyInitPreset ;; request patch send to SIDs with matching channel number SET_BSR SID_BASE clrf PRODL ; PRODL used as counter CS_MENU_MS_NotifyInitPresetL ;; calc pointer to channel entry lfsr FSR0, CS_MENU_SID_M_CHN movf PRODL, W addwf FSR0L, F ;; check if channel number matches movf INDF0, W xorwf SID_CURRENT_CHANNEL, W, BANKED andlw 0x0f bnz CS_MENU_MS_NotifyInitPresetLN ;; get patch number matches (in this case don't change the patch) movlw (CS_MENU_SID_M_PATCH-CS_MENU_SID_M_CHN) & 0xff addwf FSR0L, F andlw 0x7f ;; copy INDF0 to SID_MIDI_PARAMETER2 and masked 0x7f movf INDF0, W andlw 0x7f movwf SID_MIDI_PARAMETER2 ;; store patch number movff SID_MIDI_PARAMETER2, INDF0 ;; skip if patch change already requested movlw (CS_MENU_TX_M_CTR-CS_MENU_SID_M_PATCH) & 0xff addwf FSR0L, F BRA_IFSET INDF0, 7, ACCESS, CS_MENU_MS_NotifyInitPresetLN ;; request patch change movlw 0x81 movwf INDF0 CS_MENU_MS_NotifyInitPresetLN incf PRODL, F BRA_IFCLR PRODL, 2, ACCESS, CS_MENU_MS_NotifyInitPresetL return ;; ####################################################### ;; # END MODIFICATION ;; ####################################################### I know, it's not the best solution (I miss my assembler depth ... actually I just wanted to refresh the SR ). However, you must be aware that this will cause any changes to the preset to be lost. ..most of the code was taken from the program change routine. This CC is useful for me, after the 6581 was used and the SID is still audible after use. I can then trigger this CC to end the hanging sound. Greetings, rio

yes you are right, I could now break it down on two devices, where it did not work as expected. Thanks for the explanation. Greetings, rio

################################################## # Running status optimisation # Enabled by default, should be disabled if a MIDI # device connected to a MIDI port doesn't fully # comply to the MIDI specification. # Expects two parameters: port number and 0/1 to # disable/enable the optimisation. ################################################## Can someone explain me what the difference is to 'normal' midi out or what exactly does that do? Most of my synths/device don't understand this optimization... Greetings, rio

I would like to take this opportunity to say "thank you" again. After years of working with it, I can still discover new things, implement my ideas and nice that the firmware for the LPC17 was still in place, which I still use. The device is or remains the heart of my synthesizer & it runs stable & fine - I do not know any other hardware that covers the range or is so flexibly applicable. By the way, mentioned that the firmware is also open source. Best regards, rio

Hi, Yesterday I played around with the loopback feature. If I had set a track to bus 1 then I can already see the NRPN LSB descriptions for the CC inside that track - nice, but If i choose another bus (2,3,4) the standard description of the CCs is shown again. Is that intended or a visual bug? best regards, rio

Thank you!

since V4.093: Is it possible to include this representation as an option (e.g. display edit notes transposed: yes/no) in the option page? For me, it's quite difficult to find or remember the original/root notes of the track again when editing live.

Hi, i am from germany and want take the lpc17 Core board (5€) and the full Lpc17 core (25€). Pls PM. greetings, rio

hi, When "Midi Remote Key" is pressed, you can control multiple SEQ functions with different midi notes (which can be triggered by your controller or keyboard): http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fsequencers%2Fmidibox_seq_v4%2Fdoc%2Fmbseqv4_remote_functions.txt&peg=2562 PS: If you have general questions to "how to use the SEQ", then it's best to create an own thread. Greetings, rio

As i remember, C-6 is the default remote key that is configurable to V4.093 in MBSEQ_HW.V4 file: ################################################## # MIDI Remote Keyboard Function ################################################## # The note number which activates the remote function # 96 = C-6 (some MIDI monitors display C-5) # 0 disables the remote keyboard function MIDI_REMOTE_KEY 96 # The CC number which activates the remote function # (e.g. to control it with a footswitch) # Allowed numbers: 1-127 for CC#1..CC#127 # 0 disables the function (default) MIDI_REMOTE_CC 0 ..but since V4.094, it's configurable in Option Page, like TK mentioned here: http://midibox.org/forums/topic/13137-midibox-seq-v4-release-feedback/?page=49#comment-179576 Greetings, rio