Troubles with the sequencer and a looping sample chop

So I chop a sample, set it to loop and extract it to a pad. All is well so far. So I try to record a 4 bar sequence. I hit the the sample chop loop on beat 1 and plays fine the first time the sequence plays thru all 4 bars. When the sequence runs thru its 4 bars and goes back to beat 1 the sample chop does not play anymore, very frustrating.

When you place a pad with Loop enabled into a sequence, it plays on the first trigger but stops on the second one. I'm not sure whether this is user error or just a limitation of the design.

someone explained it to me like this and it made sense: when loop is enabled on a pad it will start when it is pressed or triggered, and stop when it is pressed or triggered. when a loop as added to a sequence and triggered on 001.01.000 it will play and loop until the sequence starts over and it is triggered again, at which point the loop stops the same way it would if you using the device in sample mode and hit the pad again. that's why it comes back around on every other loop of the sequence.

the workaround I found is to set my sequence length to the length of the sample (usually 2 bars, sometimes 4), then use the "double seq" with SHIFT+PAD3 so I don't have to re-trigger a sample manually for 16 bars. I just start with a 2 bar sequence then double it to the length of the phrase I want to work with. once you get used to it, it's extremely fast.

I've come across the same trouble. When recording sequences that use samples with LOOP engaged, for example a 2 bar rhythm loop, and I set the seq to be just 2 bars, the device records the first 2 bars with the sample playing, and then an additional 2 bars with silence. However, if the sample is set to LOOP off, the seq records and plays fine. So I must engage loop when jamming, but when I plan to record sequences, first of all I have to remember to turn off LOOP for those samples. A bit annoying until you get used to it.

Another thing is that in STEP EDIT I can see which pad is played and when (the time position) and also the velocity, but I can't see the duration of the event (the time the pad has been pressed). Probably is asking too much, so instead of editing thru that limited interface is better to practice until your performance is good enough without further editing.