[update] os128XL Ver1.13 and os2xl 3.24, 08-DEC-2012

i've been doing a lot of reporting lately for os128xl - pretty much nightly. the jj team has been smashing these bugs and responding to all of my comments/questions.

awesome.

-----------------------------------------------------
Bug fixes: 128XL Ver1.13 08-DEC-2012
-----------------------------------------------------
1. [MAIN]

[SAMPLE REPEAT]
REPEAT does not work with the pad of even number other than BANK A.
Moreover, the value of the velocity by the pressure of a pad does not change.

2. [PROGRAM]

A pad cannot be selected while playing a sequence.

-----------------------------------------------------------------
Bug fixes: MPC1000 OS2XL Ver3.24 01-DEC-2012
-----------------------------------------------------------------
1. [MAIN GRID]

When cursor is in the bar field, a copy event will be erased if F6 (ERASE) is performed after F4 (COPY).

2. [GRID]

The different pad is selected when F3 (VIEW) is opened in LOOP EDIT mode.

3. [STEP EDIT]

[View:NOTES]
Selection of a pad cannot be performed with a pad.

4. [MAIN]

Recording will be canceled if the FULL LEVEL button is pushed during recording.

Good work. Wicked to see it getting better all the time, so when/if I eventually update myself to the XL screen, the OS'll be as good as possible.

is anybody else having issues with chopping? let's say i take a perfect four bar sample, i chop it into sixteen pieces, and map it out on the pads. it crams the 4 bars into 14 pads, and then gives me weird ultra stereo chops for 15 and 16. it really seems like a bug to me.

also, auditioning your chops, while you're chopping, seems to be really cumbersome. ie lagtime, and messed up auditions... is this problem unique to my machine? these things really mess up my workflow. i'm tempted to install the os2xl and work half screen, until all these issues are sorted out.

the larger the sample, the worse the lag in TRIM. i've reported that one.
i'll test the chopping bug tomorrow. you talking NDC or destructive?

Nym wrote:the larger the sample, the worse the lag in TRIM. i've reported that one.
i'll test the chopping bug tomorrow. you talking NDC or destructive?

thanks for the info, nym. i'm talking about destructive chopping. i actually thought jj got rid of nondestructive chopping a few updates ago. if he didn't, i gotta find it, cause the destructive chop ain't cutting it!