fanwander Posted April 5, 2014 Report Share Posted April 5, 2014 Hello It is possible to mute the tracks for bender-data and control-data independently from the note information. But if I see it right it is not possible to clear the bender or control tracks only, but keep the note data. Would this be possible? It would be very helpful Regards Florian Anwander Quote Link to comment Share on other sites More sharing options...
TK. Posted April 6, 2014 Report Share Posted April 6, 2014 Hi Florian, yes, I could add this to the firmware. I'm unsure about the best access method for this function - which one would you prefer: a) using a key combination, e.g. "COPY+CLEAR" (or similar) b) a dedicated button function, which can be configured in the MBSEQ_HW.V4L file on SD Card. Then you could sacrifice a typically unused button (e.g. UNDO?) and assign the new CLEAR_PB_AND_CC function to this button instead. Best Regards, Thorsten. Quote Link to comment Share on other sites More sharing options...
fanwander Posted April 6, 2014 Author Report Share Posted April 6, 2014 (edited) Hi Thorsten Thanks for thinking about it! a) using a key combination, e.g. "COPY+CLEAR" (or similar) What about doing it similar to the MUTE-Function? For sequence 1 CLEAR -> #1 Clears the whole sequence CLEAR -> #2 Clears the notes and bender, keeps CC CLEAR -> #3 Resets Velocity to 64 CLEAR -> #4 Clears bender only, keeps notes CLEAR -> #6 Clears CCs, keeps notes CLEAR -> #7 Sets note lenghts to half step length same for Sequence 2 with #9 - #16 I think this kind of clear function, which requires two button presses, would have also the advantage that you have to confirm the the CLEAR command. Florian Edited April 6, 2014 by fanwander Quote Link to comment Share on other sites More sharing options...
TK. Posted April 6, 2014 Report Share Posted April 6, 2014 This is a great idea! :smile: Please try this pre-release: http://www.ucapps.de/mios32/midibox_seq_v4l_082_pre1.zip Button assignments: o CLEAR button now allows to clear individual tracks with the GP buttons: - CLEAR+GP1: clear note triggers (values are kept but not played) - CLEAR+GP2: reset velocity values to 64 - CLEAR+GP3: reset note length values to half step - CLEAR+GP4: clear Pitchbend - CLEAR+GP5: clear all CCs - CLEAR+GP6: clear Seq1 + track configuration (*) (like before) - CLEAR+GP7: like GP6, could be used for other purposes in future - CLEAR+GP8: like GP6, could be used for other purposes in future Same for GP9..16 for Seq2 (*) track configuration won't be changed if 'PasteClrAll' set to 0 in MBSEQ_GC.V4 file As long as the CLEAR button is pressed, the LEDs act as some kind of "track activity indicators" to notify the special function, and to give an oversight about the track utilization. Unfortunately the clear functions of GP#4...8 resp. GP#12..16 conflict with the activity monitor. E.g. track 4/12 not only store the pitchbender, but also the first 3 CC lines. Track 5..8/13..16 store the additional CC lines (4 per track). But GP button 4/12 will only clear the pitchbender (by intention), and GP button 6..8/14..16 will clear the complete sequence instead the assigned CC lines. This could be confusing, on the other hand the additional button assignments are more important than a consistent display. With some dirty patches in the seq core I could improve the activity monitor depending on how important the display capabilities are. Alternatively, I could change the recording function, so that CCs are not stored in the same track like PitchBend anymore. This would also solve an inconsistency in the mute function (which mutes PB and the first 3 CCs) - a difficult decision. Best Regards, Thorsten. Quote Link to comment Share on other sites More sharing options...
fanwander Posted April 8, 2014 Author Report Share Posted April 8, 2014 This is a great idea! :smile: Please try this pre-release: http://www.ucapps.de/mios32/midibox_seq_v4l_082_pre1.zip Alternatively, I could change the recording function, so that CCs are not stored in the same track like PitchBend anymore. This would also solve an inconsistency in the mute function (which mutes PB and the first 3 CCs) - a difficult decision. Best Regards, Thorsten. Hi Thorsten, wow thanks for the quick prerelease. It works, but always affects sequence #1. If I select sequence #2 and try one of the clear commands then the corresponding part of sequence #1 is cleared. Florian Quote Link to comment Share on other sites More sharing options...
TK. Posted April 9, 2014 Report Share Posted April 9, 2014 Hi Florian, somehow I already feared that this can lead to confusion: the GP button assignments are similar to the MUTE page: button #1..#8 control Seq1, and button #9..16 control Seq2 independent from the selected sequence. Advantage: direct control over both sequences without switching Disadvantage: unusual/inconsistent UI handling It's probably better if I decouple the UI from the actual track & layer assignments (which are inherited from the "big brother" V4): - button assignments in CLEAR and MUTE page shall reflect the sequence selection, starting from button #1 - button assignments shall differ between Pitchbend and CC layers in track #4..7, which means that: o Button #1 clears/mutes note triggers o Button #2 resets velocity (mutes have same function like Button #1: no notes are played) o Button #3 resets note length (mutes have same function like Button #1: no notes are played) o Button #4 clears/mutes the Pitchbend line o Button #5 clears/mutes the first recorded CC line o Button #6 clears/mutes the second recorded CC line o ... o Button #15 clears/mutes the 11th recorded CC line o Button #16 mutes the remaining CC lines in MUTE page, resp. it initializes the whole sequence & configuration in CLEAR page Do you agree, and/or do you have additional ideas? Best Regards, Thorsten. Quote Link to comment Share on other sites More sharing options...
fanwander Posted April 10, 2014 Author Report Share Posted April 10, 2014 Aargh.... Stupid me! Nope, keep it as it is now! The concept is perfect for the muting, and should be kept consitent for the clear function. I re-tested it and now I found what foold me: the LEDs blink as soon as an event happens that can be cleared. Sequence 1 was a one bar 16 16th line and sequence 2 had a length of four bars and had only a single very short note on beat one of bar 1 and bar 3. So those steps were nearly not lit. May be it would be more helpful of the LEDs would be lit continously. This way it would be clear which tracks of which sequence are available for clearing. The information, whether there is a note played actually is not relevant while the clear process. Florian Quote Link to comment Share on other sites More sharing options...
TK. Posted April 12, 2014 Report Share Posted April 12, 2014 Ok, LEDs now lit according to the gatelength. :smile: I spent some more thoughts on this: actually it's better if the entire sequence is cleared with CLEAR+SEQ1 resp. CLEAR+SEQ2. And the GP buttons just clear the related track without hidden conventions (e.g. it wasn't obvious that GP#4 only clears PitchBend). In combination with a changed CC line assignment algorithm the CC Clear function finally becomes more useful: o CLEAR button now allows to clear individual tracks with the GP buttons: - CLEAR+SEQ1: clear entire Seq1 + configuration (*) - CLEAR+SEQ2: clear entire Seq2 + configuration (*) - CLEAR+GP1: clear note triggers (values are kept but not played) - CLEAR+GP2: reset velocity values to 64 - CLEAR+GP3: reset note length values to half step - CLEAR+GP4: clear Track 4 (Pitchbend + last CC lines) - CLEAR+GP5: clear CCs of Track 5 - CLEAR+GP6: clear CCs of Track 6 - CLEAR+GP7: clear CCs of Track 7 - CLEAR+GP8: clear CCs of Track 8 Same for GP9..16 for Seq2 (*) track configuration won't be changed if 'PasteClrAll' set to 0 in MBSEQ_GC.V4 file o changed the track and layer assignment algorithm for CCs in recording mode: Previously new CC lines were recorded into Track 4, Layer B upwards. Now they are assigned the following way: - 1st CC line is recorded into Track 5, Layer A - 2nd CC line is recorded into Track 6, Layer A - 3rd CC line is recorded into Track 7, Layer A - 4th CC line is recorded into Track 8, Layer A - 5th CC line is recorded into Track 8, Layer B - 6th CC line is recorded into Track 8, Layer C - 7th CC line is recorded into Track 8, Layer D - 8th CC line is recorded into Track 7, Layer B - 9th CC line is recorded into Track 7, Layer C - 10th CC line is recorded into Track 7, Layer D - 11th CC line is recorded into Track 6, Layer B - 12th CC line is recorded into Track 6, Layer C - 13th CC line is recorded into Track 6, Layer D - 14th CC line is recorded into Track 5, Layer B - 15th CC line is recorded into Track 5, Layer C - 16th CC line is recorded into Track 5, Layer D - 17th CC line is recorded into Track 4, Layer B - 18th CC line is recorded into Track 4, Layer C - 19th CC line is recorded into Track 4, Layer D Same for Track 12..16 for Seq2 Advantage: if only a few CC lines are recorded, we've dedicated tracks for PitchBend and CCs (Track 4-8, Layer A) which can be individually muted and cleared. Additional CCs populate the remaining layers from Track 8 backwards, so that PitchBend remains an individual track if not more than 17 CC lines are recorded. The new pre-release is available at: http://www.ucapps.de/mios32/midibox_seq_v4l_082_pre3.zip /Update: v4l_082_pre3 provides a better Seq1/2 selection handling whenever a track is cleared Best Regards, Thorsten. Quote Link to comment Share on other sites More sharing options...
TK. Posted May 3, 2014 Report Share Posted May 3, 2014 The new handling is officially released now because I'm happy with the implementation! :) -> Best Regards, Thorsten. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.