os2, 1.01
on some heavy duty sh1t
record+playstart/playstart bug
1 - enter any recording mode or main screen
2 - hit RECORD+playstart
3 - record performance
4 - before LAST BAR (before sequence loop), hit PLAYSTART
5 - BUG: recorded performance is deleted.
NOTE: notes are not deleted with OVERDUB instead of RECORD:
1- hit overdub+playstart
2- record performance
3- before last BAR (seq loop), hit playstart
4 - notes are not deleted.
--------------------------------------
TC SWING does not work when applied AFTER recording.
1 - load project
2 - record performance with TC OFF
3 - apply TC 1/8 with SWING 60%
4 - BUG: TC is applied, SWING is not applied
5 - NOTE: let TC = 1/8 with SWING 60%
6 - record performance.
7 - NOTE: TC is applied, SWING is also applied.
----------------------
a midi note assignment bug remains
1 - load project, including a DRUM PROGRAM
2 - set track to MIDI
3 - enter GPE, RESET pad to note 35-96 (chromatic)
4 - assign a sample to pad A01. assign A01's NOTE to 0 (c -2)
5 - record performance of A01. NOTE: sample plays when pad is struck.
6 - replay performance. BUG: pad A01 is recorded, but not played.
7 - assign A01's note to 36 (C-1)
8 - assign A02's note to 35 (B-0). assign a sample to A02.
9 - record performance. NOTE: pads play assigned samples.
10 - replay performance. BUG: the sounds are switched.
11: IMPORTANT NOTE: change TRACK to DRUM instead of MIDI.
12: play performance. NOTE: recorded pad A01 plays correct sample. recorded pad A02 also plays correct sample.
13: assign sample A01 to note 0 again. record performance. replay performance. NOTE: recorded A01 plays correct sample
NOTE: bug only exists in MIDI tracks.
question: is it necessary to make a distinction between DRUM and MIDI? could it not be that these are made to be the same, 1 track type? could it be that MIDI GRID EDIT become simply another EDIT option? it is my favorite editing sequencer, i always use it for INTERNAL SOUNDS as well. i do not understand why there is a difference that exists between MIDI and DRUM tracks.
________
SIMILAR: an inconsistency in DELETE and SEQ EDIT
1 - load a DRUM program. set a track to DRUM.
2 - record performance.
3 - hit ERASE.
4 - observe the "NOTE" option. hit a pad: the pad is "selected" for deletion.
5 - NOTE: a user can selectively delete ONLY pads A03, A14, and B10. this is very useful
6 - enter SEQ EDIT. a similar specification exists.
7 - change track from DRUM to MIDI
8 - enter ERASE or SEQ EDIT.
9 - INCONSISTANCY: a range exists instead of selective notes. a user cannot delete certain notes by striking them to "Select." this is inconvenient and is time consuming.
again, it is a difference between MIDI and DRUM tracks.
it very confusing to me why these 2 exist when 1 could exist.
______________________
in INST pgm GPE, a sample's ORIGINAL NOTE cannot be set higher than 99 D#6
1 - load a sample
2 - create INST pgm
3 - enter INST pgm GPE, assign a sample to 1
4 - in SAMPLE tab of GPE, move to ORG column.
5 - attempt to set ORG to 105 A_6
6 - BUG: ORG cannot be set higher than 99 D#6
7 - enter TRIM. assign ORG to 105 A_6. NOTE: this is successful.
8 - reenter INST pgm GPE. examine sample 1's ORG note.
9 - NOTE: in INST pgm GPE, ORG is displayed "99 A_6" <-- this display is incorrect.
________________________________
