TK.

How about following solution: a special GP button function in SONG page which copies the current pattern set and mutes into a "phrase slot" of a song. This would allow us to quickly store and restore a complete scene (so - not only the mutes) into up to 16 phrases per song, and it would allow to visualize & edit the scenes later (e.g. to remove pattern changes if they are not wanted). As a side effect, this would also allow to chain the phrases to a complete song (if desired)... some kind of interactive song step recording. Best Regards, Thorsten.

Better idea: Similar to Actions like Jump Position/Song/Select Mixer map, a "Mute" Action could be provided which allows you to enter a mute pattern into a song step. E.g.: [tt] Pos A1 Mute oooo **** **** **** Pos A2 x2 1:A1 2:A1 3:A1 4:A1 Pos A3 x2 1:A2 2:A1 3:A1 4:A1 Pos A4 Mute oooo oooo **** oooo Pos A5 x4 1:A2 2:A2 3:A1 4:A1 Pos A6 x4 1:A2 2:A2 3:A1 4:A2 Pos A7 Jump A5 [/tt] Remember that each song is splitted into 16 phrases, so that you can define up to 16 mute scenes this way. E.g. - if you don't use pattern selection at all. [tt] Pos A1 Mute oooo **** **** **** Pos A2 Stop Pos B1 Mute oooo oooo **** **** Pos B2 Stop Pos C1 Mute oooo oooo oooo **** Pos C2 Stop [/tt] etc. Best Regards, Thorsten.

such an handling isn't practicable while playing live, as you don't have direct access and a sufficient visual feedback while selecting a mute scene (where did you store a certain scene, how many times do you need to push the Fwd/Rew button) In addition, I think that especially in song mode, Fwd/Rwd should be used for the intended purpose, and not assigned to multiple functions depending on a menu page. So, you think that even after one month you still remember, which pattern you assigned to Mute scene #13 for Song #41, and Mute Scene #4 for Song #12 while playing live? I don't think so... This would be my personal preference as well, since this is the intention of phrase mode. Providing different use models only leads to unnecessary confusion (and too much effort at my side - consider, that after each change I've to ensure, that all options are still working - even features I would never use by myself!) (deleted as misunderstood, since I already got a better idea) Best Regards, Thorsten.

Following lines: movlw 0x90 ; check for Note On at channel #1 cpfseq MIOS_PARAMETER1, ACCESS rgoto USER_MPROC_NRE_NoNoteChn1 [/code] have to be replaced by: [code] movf MIOS_PARAMETER1, W ; get status byte andlw 0xf0 ; mask out MIDI channel xorlw 0x90 ; check for Note On bnz USER_MPROC_NRE_NoNoteChn1 ; skip if not a Note On event (ignore wrong label name) Replace: USER_SR_Service_Finish clrf MIOS_PARAMETER1 movlw 0x00 call MIOS_DOUT_SRSet movlw 0x01 call MIOS_DOUT_SRSet movlw 0x02 call MIOS_DOUT_SRSet movlw 0x03 call MIOS_DOUT_SRSet [/code] by: [code] USER_SR_Service_Finish movlw 0x00 call MIOS_DOUT_SRGet movlw 0x00 ; (*1) andwf MIOS_PARAMETER1, F movlw 0x00 call MIOS_DOUT_SRSet movlw 0x01 call MIOS_DOUT_SRGet movlw 0x00 ; (*2) andwf MIOS_PARAMETER1, F movlw 0x01 call MIOS_DOUT_SRSet movlw 0x02 call MIOS_DOUT_SRGet movlw 0x00 ; (*3) andwf MIOS_PARAMETER1, F movlw 0x02 call MIOS_DOUT_SRSet movlw 0x03 call MIOS_DOUT_SRGet movlw 0x00 ; (*4) andwf MIOS_PARAMETER1, F movlw 0x03 call MIOS_DOUT_SRSet movlw 0x04 call MIOS_DOUT_SRGet movlw 0x00 ; (*5) andwf MIOS_PARAMETER1, F movlw 0x04 call MIOS_DOUT_SRSet (*1) .. (*5): instead of 0x00, you have to set an AND mask which matches with your requirements. E.g., if the rightmost DOUT of the second SR shouldn't be cleared after 1 mS, use "movlw 0x01" instead of "movlw 0x00" if two rightmost DOUT of the second SR shouldn't be cleared after 1 mS, use "movlw 0x03" instead of "movlw 0x00" if only the leftmost DOUT of the second SR shouldn't be cleared after 1 mS, use "movlw 0x80" instead of "movlw 0x00" etc. Best Regards, Thorsten.

The EXIT button exits the page and it exits the menu. ;) You could also call it MENU if you want. Best Regards, Thorsten.

Hi, could you please try this updated release: http://www.ucapps.de/mios/midimon_v2_0c.zip I noticed that v2_0b contained an expired J5_IO driver, which got some changes meanwhile. This could be the reason. Best Regards, Thorsten.

Best Regards, Thorsten.

Please wait until Twin-X restores some forum files from the backup. It's totally clear which features are missing (all modifications have been logged), and it isn't required that you start to list them here. I just don't want to spend time for something which can be solved in 1 minute by copying files from the backup. Best Regards, Thorsten.

If you are using MIDIbox64E, open mb64e_midi.inc, search for MB64E_MIDI_SendEncEvent_M3 , and replace the code by: MB64E_MIDI_SendEncEvent_M3 ; == ENC_MODE_40_1 --- modified to send 0x40/0x41 movlw 0x41 btfsc MIDI_EVNT_VALUE, 6 movlw 0x40 movwf MIDI_EVNT_VALUE rgoto MB64E_MIDI_SendEncEvent_Send [/code] Best Regards, Thorsten.

It should work with 11 instead of 02 See also mios_backup.txt o if additional BankSticks are connected, do the same like above, but change the BankStick ID (1-7) like shown here: +--- BankStick ID | F0 00 00 7E 40 00 01 40 00 20 00 F7 F0 00 00 7E 40 00 11 40 00 20 00 F7 F0 00 00 7E 40 00 21 40 00 20 00 F7 F0 00 00 7E 40 00 31 40 00 20 00 F7 F0 00 00 7E 40 00 41 40 00 20 00 F7 F0 00 00 7E 40 00 51 40 00 20 00 F7 F0 00 00 7E 40 00 61 40 00 20 00 F7 F0 00 00 7E 40 00 71 40 00 20 00 F7 For 64k BankSticks use: F0 00 00 7E 40 00 01 40 00 40 00 F7 F0 00 00 7E 40 00 11 40 00 40 00 F7 F0 00 00 7E 40 00 21 40 00 40 00 F7 F0 00 00 7E 40 00 31 40 00 40 00 F7 F0 00 00 7E 40 00 41 40 00 40 00 F7 F0 00 00 7E 40 00 51 40 00 40 00 F7 F0 00 00 7E 40 00 61 40 00 40 00 F7 F0 00 00 7E 40 00 71 40 00 40 00 F7 [/code] Time to change your avatar (Homer Simpson? ;)) Best Regards, Thorsten.

It will work again once I get access to the backup. Most pages (58 .html files) are repaired now based on my private backups or new package releases. Best Regards, Thorsten.

Hi, a script kiddie has attacked the midibox.org server through a security hole. Some files have been modified (links to a phishing site have been added), but I've a complete log so that all changes are documented. I quickly repaired the most important pages with default files or personal backups, and waiting for Twin-X to get access to the latest backup files. Best Regards, Thorsten.

Shipped today: ballpein PTOPRoJect Flexinoodle Protosx lindeborg Sold out! Best Regards, Thorsten.

Ich habe ein aehnliches Problem mit P18, und bei mir liegt es an einem Scanner Treiber, der im Hintergrund immer mal wieder ueberprueft, ob der Scanner angeschlossen ist. Wenn ich ihn deaktiviere, gibt es keine sporadischen Aussetzer mehr. Gruss, Thorsten.

I don't see a reason why MIOS_MF_FaderMove() should behave different if called from another hook, it should even work from an interrupt service routine. But there could be an issue with the "manual move detection", because your faders are not moved precisely enough, so that the driver "assumes" that they are manually moved. In such a case, MIOS_MF_FaderMove() positions will be ignored for a short timespan. In order to overcome this, just call MIOS_MF_TouchDetectionReset(<fader-number>) before calling MIOS_MF_FaderMove(<fader-number>, <new-position>) Best Regards, Thorsten.

Mute scenes are feasible, but the described handling conflicts with the multi-mute selection, as you already noticed. I also find it confusing, if settings for a song have to be done in another page. Any other ideas? probably yes ;) no problem yes, meanwhile the MIDI IN Port for Transposer/Arpeggiator/Recorder can be selected between "All" and an individual port. With a separate selection it's possible to define the MIDI Clock Source port. Best Regards, Thorsten.

Thats normal, but I will improve this in one of the next releases. Best Regards, Thorsten.

Hi, there shouldn't be a performance problem, especially not with sm_fast or sm_slow, as these routines are executed much faster than a new MIDI event could arrive. How does it work if the first core is removed from the chain (keyboard directly connected to MIDI In of second core which executes sm_fast)? If you still notice failures, try a dummy application w/o any app code but Merger enabled. If you still notice failures after such a change, it's a hardware issue (hints to such issues later if required) Best Regards, Thorsten.

Ok, so it is the MIDI interface. I would propose to check an alternative MIDI Monitor (e.g. MIDI-Ox) to ensure, that the problem isn't related to your Java installation. It could also make sense to check the MIDI cable (or just try another one if available) Best Regards, Thorsten.

Thanks for testing - this simplifies remote diagnosis :) One purpose of the test is to check the SysEx robustness of a MIDI interface, but another purpose is to check, if the chain: MIDI Out of your MIDI interface -> MIDI In of Core Module -> MIDI Out of Core module -> MIDI In of your MIDI Interface is working. For this test, you could also send MIDI Notes (e.g. with a virtual keyboard), or any other MIDI event just to check if it goes through the chain. MIDI Data displayed by the MIOS Studio Output monitor should also be displayed by the Input monitor. Apparently there is an error in the chain. Now you've already an hint, that the error isn't related to the PIC. Accordingly, it isn't required to update the firmware (usually it isn't required to update MIOS or the firmware anyhow, it's very very unlikely that the internal flash memory gets corrupted) Next test: check if your MIDI Interface is working. Loopback MIDI Out->MIDI In of your MIDI interface, and send some MIDI notes with MIOS Studio. Result? Best Regards, Thorsten.

Could you please try TEST INOUT1 - this test ensures, that the whole MIDI IO path is working w/o the PIC. Depending on the results we could give you more hints Best Regards, Thorsten.

Great work guys! :) Would you borrow me your Solder slave for creating a duo coloured 16x16 BLM? ;) Best Regards, Thorsten.

Thank you! It fits nice below the daily Dilbert :) Best Regards, Thorsten.

Congratulations! You mastered SMT soldering! :) Best Regards, Thorsten.

I would expect D7, D6, D5, D4, D3, D2, D1, D0 (see also this table) How is MIOS_DOUT_PinSet() triggered - via buttons, MIDI, MIOS Studio, ...? Best Regards, Thorsten.