search

mixxxdj / mixxx

Mixxx is Free DJ software that gives you everything you need to perform live mixes.
http://mixxx.org
Other
4.5k stars 1.28k forks source link

add control to activate the next loop cue #11813

Open robi970 opened 1 year ago

robi970 commented 1 year ago

Feature Description

(reference)

Mixxx 2.4 gives the possibility to insert multiple loops (hotloop) in the same track.

but it doesn't have a command to assign to a pad to cause that pad to toggle the next hotloop.

for some years now, many consoles have had some customizable pads and I believe that being able to dedicate just one to the activation of the track's hotloops simplifies the work infinitely.

in this comment, on the forum, I have inserted some clarifying images.. Thanks for the attention

ronso0 commented 1 year ago

related request that came up in the discussion: control to assign active (unassigned?) loop to next free hotcue

robi970 commented 1 year ago

I noticed that no one took charge of this proposal. I think maybe I haven't been able to describe the usefulness of the function I requested, so I thought I'd insert a short descriptive video.

in the description I call them HotLoop because I believe that this function should be assigned to the "LOOP" and not "CUE" pads section. Consequently, the HotLoops must be numbered over 8 (mine start from HotLoop21) in the video I assume the insertion of 3 HotLoops: 21, 22 and 23, but in the track they have not been inserted in ascending order.

As you can see in the video, I call the first HotLoop (HL21), then, assuming I forgot that they are not in ascending order, I activate HotLoop22. opss.. I notice the error and activate Hotloop 23. Then I activate HotLoop22.

if instead there was a single command capable of activating/deactivating the various HotLoops in temporal succession, instead of using 3 pads, I would have used a single Pad to create this video, without risking making the mistake of activating the wrong HotLoop

https://github.com/mixxxdj/mixxx/assets/135370043/2e003b9a-8a5f-473a-aaae-d42885a9b470

ronso0 commented 1 year ago

I noticed that no one took charge of this proposal.

You're description/use case is very clear. We're about to release 2.4 which has been two years on the making, and this request is definitely low prio, so don't expect anything soon.