asked Dec 16 '15 at 23:05 by blueNan (51)

edited Dec 16 '15 at 23:07

I recognised strange behavior in the clip launcher:

  • I play a clip.
  • Then I stop it before its over. (so far so normal)
  • WRONG: Then the beginnig of the clip plays again (first event/note)
  • After that it stops as excepted.

Same issue via mouse and via Lauchpad Pro sessions view.

Is this a known issue?

Hey there, I have this same issue.

I have been noticing this for a while now. But it doesn't always happen.

I decided to try and figure out what is happening

And the conclusion that I have come to is that I believe that it has to do with the position of the transport phase.

If you stop the transport and then start the transport again by the launching of a scene or clip, the clips start playing on the downbeat of the first beat of the first bar which at the beginning of the phase cycle.

But if the transport is playing and you launch a clip or group of clips at some odd time within the transport's phase cycle, clips will not stop as expected. Instead, they will stop once the phase cycle has completed.

It's rather annoying and makes for sloppy live performances. So I am going to take it up with Bitwig support to see if there is a way this can be changed or if it's possible to improve this in an update.

link

answered May 10 at 07:57 by Pspiralife (71)

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

Markdown Basics

  • *italic* or __italic__
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Tags:

×22
×8
×6

Asked: Dec 16 '15 at 23:05

Seen: 817 times

Last updated: May 10 at 07:57