Pressing "reloop/exit" button breaks playback

[Jan-Philip Gehrcke]

I am using 1.12 from git (checkout on May, 23rd), built on 32bit Linux (Ubuntu 14.04).

I am able to reproducibly confuse the loop component (at least I think this is not intended).

The erroneous state
================
In this state, just pressing the "Loop" button (Deere) causes silence, if not within in/out markers. The track is not exactly stopped, it is in a short loop (with the waveform wiggling back and forth) without any output level (not even noise). I can get out of there by again pressing "loop". As a clarification: normal program behavior is that the "Loop" button press is ignored.

How to reproduce?
===============
- Start Mixxx
- Load a track to deck A
- Start track
- Press "Loop" button (reloop/exit) -> is ignored, right behavior
- Set loop-in marker
- Set loop-out marker
- In the loop, press "Loop" for deactivating the loop
- Wait until playback leaves the deactivated loop
- Press "loop" -> playback hangs (waveform wiggles) -> incorrect behavior?!
- Press "loop" again -> playback proceeds

Another important note
===================
 I have some times seen a more severe version of this. When following the steps above, we can afterwards still set other in/out markers right during playback, and the corresponding loop is immediately entered. In the more severe version of the above "problem" the playback stops right in the moment of setting the loop-out marker (playback, set loop-in, set loop-out -> silence). This definitely is wrong. And since the symptom is the *same* as in the reproducible case above, I guess that these problems are closely related. Unfortunately, I have no repro for the more severe version of the problem.

Fun-fact
======
 I have a VMS2 controller. What I have seen is quite interesting: once *in* the silence/wiggling state, when I then switch off the controller, the playback continues normally. I do not now if this helps, but I thought you should know. In any case, the repro above works *without* controller attached to the computer.

[Owen Williams (ywwg)]

I'll take a look at this

[Owen Williams (ywwg)]

Fixed.

[Lee Matos (lbot)]

Can I make a request on this one? In traktor there is the concept of "loop activate" which is means that when the playback head enters the loop zone it begins looping. This allows you to set a loop as a "trap" that way when you can do some snazzy transition stuff. (I like to do that when I have a big bpm drop for dramatic effect to loop a chorus or something and shift the tempo on a predefined loop.)

This is kind of out of the scope of this bug, but I figured it might be a good time to bring it up. This also would lead to the need for the ability to store a loop as a cue so these "traps" could be predefined. Just some thoughts.

[Jan-Philip Gehrcke (jgehrcke)]

@ Lee: sounds great. So far, the only possibility to activate a loop in Mixxx is in the moment the playback head is *within* the loop, right (I am still a beginner with Mixxx). If that is true, then the behavior you describe for sure sounds very convenient and adds a lot of flexibility.

[Swiftb0y (swiftb0y)]

Mixxx now uses GitHub for bug tracking. This bug has been migrated to:
https://github.com/mixxxdj/mixxx/issues/7484