slicing sample: region playback in os2xl

hey i need opinions from os2xl users.
go slice a sample and see if anything different happens.

spoiler: when you hit a region when chopping in SLICE, the pad now plays as if it were POLYPHONIC and ONESHOT. this means that the touch will play the entire region when you tap it. it also means that when you go from 1 region to the next region, the first region will continue playing.

this is not the way it happened in os2 or os1. i reported it as a bug, but jj said that this was on purpose because it is more convenient.

EDIT: CORRECTION: i didn't see the quoted text in GMAIL. jj was referring to something else, the DELETE causing a STEP INCREMENT in DRUM GRID EDIT. as this slice thing stands, i still consider it a bug and have not been in contact with jj about it other than to report it as a bug.[/i]

unfortunately, it makes it very difficult to do this:

http://www.youtube.com/watch?v=2K3sfXO6 ... annel_page

because when you cut a sample in half and both regions are still plenty large, they have to play out in their entirety. this jumbles what you are hearing as you've already moved on to other regions and are adjusting their start and end point.

i sorely miss the behavior of a REGION to be "note on" and "monophonic"

what do you think? i want a little more public opinion

Option to switch would be nice. Note On though is what I'd prefer. Didn't check, but does triple stop at least work?

yeah triple stop works but it's still painful to have to do all the time.
so for you, note on ie the way it used to be is what you'd prefer?

I hate the way it is in os2xl.

hahah i take it you noticed?
this is good, keep it coming...

I've just tried os2xl "slice" (which should be named slice and no chop in the trim screen, it's confusing for a second)
and it's not a problem for my worflow which mainly consisted in keeping pressed pad one and then right arrow on and on.

I think it doesn't need to be polyphonic and it would be better to have the choice as an option.
I hope i won't have some repercussions in NDC (which was note on unfortunately at the beginning)

Just for my own curiosity NYM, before doing that video of dividing and conquer didn't you get any luck with autochop on that break?

i havent had much time with xl yet, but i think mono/one shot makes alot more sense from a fast workflow perspective.
of course an option would be nice but im not really sure id ever use it, might be somewhere better to use that code space.

yeaaaah, good thinking, MONO ONESHOT would be far better than POLY ONESHOT or MONO NOTE ON.

i think the MONO/POLY is the problem here, not the ONESHOT/NOTE ON
because by specification, NOTE ON implies a MONO playback

le rat, i did not try AUTO on that break or any others, i find that i'm faster using the dnc method than AUTO because i will be going to every start/end point to adjust anyway.

yeah mono one shot would be great... was going to post that idea until i read the other posts!the poly oneshot is a nightmare.
also i would like the region parameter to be accesible only by shift and right cursor.

also i would like the region parameter to be accesible only by shift and right cursor.

i suggested "shift+bar < and >" = change range value (not enter RANGE parameter)
your suggestion would also be nice.

i wanted to make sure everyone saw my edited first post - i misunderstood my correspondence with murai - he was referring to a different bug i reported, NOT to the slicing samples bug.