Loop Cancels When Pressing Play

[Zaren]

System: Windows 10 x64
Mixxx Version: 2.1 Beta, 2017-12-23 (not sure of the exact commit details)
CPU: Intel i7-6700K Skylake, 64-bit, 4.0 GHz
Sound Hardware: KMI K-Mix
Controller: Numark Mixtrack 3

Description of Issue:
I often select a loop before pressing play on my controller. This allows the loop to start after the deck mix is centered, so that I don't have to fade in my loop. In past versions, of Mixxx when I press play on my controller, a Numark Mixtrack 3, the loop begins playing without incident.

In the Mixxx 2.1 Beta, if I have a loop selected and then press play, the loop deactivates/un-arms as the track starts playing. I'm not sure if this is a bug or a new "feature," but it is seriously detrimental to the way in which I (and my DJing partner) use Mixxx.

Please fix this or at least give an option so that this behavior can be unselected.

Also, I apologize if this issue has been fixed since the 2.1 Beta version that I compiled (circa 2017-12-23). I have been out of town and have not had a chance to compile the latest code.

Also, I apologize if there is already an option to change this behavior and I have somehow missed it. There are lots of changes in 2.1 Beta!

[Be (be.ing)]

> I often select a loop before pressing play on my controller.

What do you mean by "select a loop"? Do you set a new loop or do you use the reloop button?

[Rudolf Gallander (akkarin169)]

I think I know this problem: If quantized mode is enabled and you start the track with the active loop just before the other deck passes a beat marker, then the quantize logic will move the playing position out of the loop and thereby cancel it.

[Be (be.ing)]

I'm guessing this was introduced by https://github.com/mixxxdj/mixxx/pull/1367

[Zaren (czchmate)]

Sorry about the delay in the response. I activate a new loop on my controller (4-measure, 8-measure, etc.) and then press play. I don't know what the re-loop button is.

Rudolf is correct, I do have quantized mode on.

[Zaren (czchmate)]

I don't mean to be a pain, but I was wondering if any progress had been made on this?

Is it covered by https://github.com/mixxxdj/mixxx/pull/1367 or https://github.com/mixxxdj/mixxx/pull/1428 ?

You guys work so hard. I am really sorry if this bug report is just irritating. I wish that I could help with the coding, but everything in here is really beyond my abilities.

At least I can compile. Please let me know if I need to beta test any fixes.

Thanks!

[Be (be.ing)]

If you don't see any activity on the bug or any related pull requests on GitHub, there most likely has not been any progress. PR 1367 made a lot of changes to how loops are handled, so I'm guessing this bug was accidentally introduced by a change made then.

[Daniel Schürmann (daschuer)]

I can confirm the issue with Quantize Play.

[Daniel Schürmann (daschuer)]

https://github.com/mixxxdj/mixxx/pull/1487

[Daniel Schürmann (daschuer)]

https://github.com/mixxxdj/mixxx/pull/1487

[Swiftb0y (swiftb0y)]

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