asked Mar 19 '14 at 10:17 by wiggy (290)

Anyone know the exact difference between the Loop Start/Length and the two blue flags? The blue flags read out in ms at the top, and the knobs are a %, presumably of the loop length. But why have two different things? Also how do you set the bit at the end, mine just stops after looping.

I also did not quite dig the loop function of Bitwig's sampler. I think you set the actual loop with the two flags. There is no snap function at crossing points helping durings this process. And the zooming is a pain in the a** since it seems to be impossible to stay focused to the region of interest during zooming in. Once you set the loop you can use the % loop length knobs to enable a shortening of the former selection from the beginning or the end, although I have no idea what this could be useful for. There is a reverse arrow in the top of the window that seems to reverse the loop. I had the hope it would play the loop back and forth in order to better hide the loop during prolonged playback but that is not the case. One of the problems of understanding the sampler is the missing playback marker. You can simply not see what the sampler is doing…


answered Mar 23 '15 at 15:25 by Ulrich (547)

edited Mar 25 '15 at 15:05

What two blue flags? I only see one blue flag in arrangement which indicates the playhead. Can you add a screenshot?


answered Mar 24 '15 at 14:14 by JBlongz (67)

The blue flags in the sampler only appear once you enabled the loop (circles).

alt text


answered Mar 24 '15 at 17:47 by Ulrich (547)

Correct, those blue flags set the loop point and are activated when loop is enabled. The reasons why you have two sets of flags is to have the sample start from outside the loop point. For example, I have a long synth sample that I want to play as an instrument across all keys, but I want it to sustain as long as I hold a chord. The first orange flag will be where the sample starts, then I set a smooth loop area where it will sound like its hold a steady note. The last flag becomes irrelevant and usually kept at the end of the sample.

What is missing currently is a crossfade or waveform zoom, which will make it easier to set a clean loop and avoid those audible pops that can occur when the beginning and end of loops differ in amplitude.


answered Mar 24 '15 at 18:03 by JBlongz (67)

edited Mar 24 '15 at 18:07

I dont get what the loop start and length knobs are for though. They seem to shorten the selected loop region yet another time. Also when you turn the loop start knob the yellow marker does not move accordingly. Very confusing. I would really like to see a sample playhead marker to see what the sampler is actually doing.


answered Mar 24 '15 at 18:07 by Ulrich (547)

Zooming is possible btw. You hover with the mouse in the bar below the wave display which makes the mouse arrow transform to a magnifying glass symbol. Then klick and hold while dragging up and down. The problem ist, that the handling of the zoom is very nervous making it impossible to stay focused to the region of interest. A snapping function at zero crossing would also help finding valid looping points more easily.


answered Mar 24 '15 at 18:12 by Ulrich (547)

Ok I see what you mean...I was looking from the Multisamples edit view. What you noticed in the main sampler device could be a bug. I think those blue flags are should respond to the knobs. Even so, there is no loop when enabled.


answered Mar 24 '15 at 18:25 by JBlongz (67)

edited Mar 24 '15 at 18:26

Maybe it´s a bug but I think that would be a bit awkward based that it´s 1.1.6. already and was like this since the beginning. Also the behaviour of the two (Flags vs. Knobs) is somewhat different. Maybe there is a creative way to use for these two ways of regulating the loop bracket. It would be sure helpful though if there would be a description in the manual telling how to use them.


answered Mar 24 '15 at 19:42 by Ulrich (547)

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]( "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



Asked: Mar 19 '14 at 10:17

Seen: 2,447 times

Last updated: Mar 25 '15 at 15:05