What is the best strategy to play along a backtrack sample

Rosen Sound · Post by **Rosen Sound** » Wed Sep 28, 2011 5:54 am

SanderXpander wrote:Good of you to point that out, Robbinhood. I would however still advise anyone to use the sequencer mode for the OPs case. Because unless in your very specific case (don't stop the sequencer, skip over the combi, mono program after) there is no problem at all.

And yours might be fixed in 1.5 next month.

you dont have to skip the combi, thats how i ran into the bug live.. i pressed program up cause i thought the seq was over - it wasnt

SanderXpander · Post by **SanderXpander** » Wed Sep 28, 2011 6:12 am

Are you saying the problem still occurs with no combi in between? That would make it a bit worse, in my opinion.

Rosen Sound · Post by **Rosen Sound** » Wed Sep 28, 2011 6:14 am

i think the combi needs to be there. which is the case for me...

Dniss · Post by **Dniss** » Wed Sep 28, 2011 6:23 am

robbinhood wrote:press play, then program up, without pressing stop. Then skip over the combi and go to a mono program, and have fun with a hanging note. This is why i re sample all of my sequences and assign them to the lowest C. just go into program mode > basic > and press HOLD and it will play to the end. its also best to make the program mono that way if you accidentally hit the key, it will start over instead of playing over itself...

I have to admit you got me there.
It's an audio track. Would that cause the same prblm?

I guess I'll have to find the original thread, not sure how to find a mono prgrm either.

I hope it doesn't apply to me, cause doing like this really just opened up a whole new horizon of ideas.

But I'll check it out, I wouldn't want to find the hard way (live)

Dniss · Post by **Dniss** » Wed Sep 28, 2011 6:25 am

SanderXpander wrote:I thinkBy the way, if you use the sequencer/song from the setlist, you can tell is to auto-start upon selecting it. One button less to press!

I was looking for that this evening with no avail.

May I ask where you find that option?

SanderXpander · Post by **SanderXpander** » Wed Sep 28, 2011 6:25 am

Okay, so while not trying to make light of your bug, there are very specific circumstances to trigger it;
1. Play a sequence from the setlist
2. Don't press stop/wait till it's really over and switch to the next slot (a combi)
3. Switch to the slot after that (a monophonic program)
Now notes will stick, correct?

It's good to be aware of this current bug, but I will still say using the sequencer is a much nicer and more elegant solution for the OP's case, as long as he can avoid the above specific situation. Even just pressing stop on the sequencer would preempt it.

Rosen Sound · Post by **Rosen Sound** » Wed Sep 28, 2011 6:30 am

SanderXpander wrote:Okay, so while not trying to make light of your bug, there are very specific circumstances to trigger it;
1. Play a sequence from the setlist
2. Don't press stop/wait till it's really over and switch to the next slot (a combi)
3. Switch to the slot after that (a monophonic program)
Now notes will stick, correct?

It's good to be aware of this current bug, but I will still say using the sequencer is a much nicer and more elegant solution for the OP's case, as long as he can avoid the above specific situation. Even just pressing stop on the sequencer would preempt it.

if you press stop, AFAIK the bug will not occur... I just like bitching about it cause it ruined a live show for me.

heres a video that describes it.

And for an answer, if you use a sample instead of a sequence you wont runi nto it.. i just re sampled the seqeuence and load it via ram as an audio file instead of sequence...

http://www.youtube.com/watch?v=RB7nzVvKkSo

jick · Post by **jick** » Wed Sep 28, 2011 8:44 am

danmusician wrote:Another disadvantage to the OP's original intent would be note stealing. If you ended up overloading the polyphony of the Kronos while the note with the sample was playing, that sample would stop playing because the note would be "stolen." I experimented with something like this in the M3 and had that problem...

That's really a disadvantage.. Is there a way to avoid this? I guess there is no option that can let you prioritize patches when it comes to polyphony?.. It would be great to make the user samples (I use quite some too, sometimes samples over a minute) top priority, so they are never stolen. Sounds like a great feature to me actually..