Saved beatjump

[acolombier]

Feature Description

Similar to saved loop, it would be great to be able to add saved beatjump. This would allow the track to automatically jump from a preset point to another preset point. This usecase would be be to skip sections of the track with low interest (silence for example).

Currently, the workaround is to set to cues with various colour or label (eg the first one red with labelled silence, the second one green labelled chorus) and use the first red cue as visual marker, helping timing the second cue jump. This is suboptimal as:

• It uses two cues
• It is hard to perfectly time and usually leads to audio little glitch

Like for saved loop, it would be great to be able to enable or disable the jump

[Swiftb0y]

This is similar to the "Serato Flip"-like proposed feature of "Mixxx Macros" (see wiki and past failed GSoC PRs).

[acolombier]

Indeed, I think that feature would have been covered by macros. Do I understand correctly that the macros feature was abandoned?
Could we consider saved beatjump without the whole macros framework?

[ronso0]

Do I understand correctly that the macros feature was abandoned?

Yes, sort of. The idea is still good, even though IIUC #4528 was canceled because a) there were some unedited reviews and b) Xeruf lost interest and moved on to other projects.

Could we consider saved beatjump without the whole macros framework?

I'd say yes.
It requires a special cue type, basically like a loop cue with start and end position (where start may be after end to allow one-time backward jumps?) and do the In -> Out seek like a reverse loop.
As you described, activation would be identical to 'catching loops', just that it 'loops' once.

Setup could be pretty much the same like creating a manual loop (set In pos, seek, set Out pos).
I think as a starter, we could adopt the looping controls In / Out and add a "Jump".
Adjusting LoopingControl will be a lot of Fun ™️ 😆

---

A related feature I was thinking of recently:
simplify the workflow of turing a loop cu into a regular hotcue which currently requires deleting the loop cue and create a hotcue in the same position.

[acolombier]

Yes, sort of. The idea is still good, even though IIUC #4528 was canceled because a) there were some unedited reviews and b) Xeruf lost interest and moved on to other projects.

That's a shame. The idea is great and this feature could have been a real game changer with complex routines. Hopefully, someone picks up the work where it's been left at eventually.

I'd say yes. It requires a special cue type, basically like a loop cue with start and end position (where start may be after end to allow one-time backward jumps?) and do the In -> Out seek like a reverse loop. As you described, activation would be identical to 'catching loops', just that it 'loops' once.

Yes, exactly what I had in mind, with potentially one-time backward too potentially, although that last one my be tricky to make a "one off"

A related feature I was thinking of recently: simplify the workflow of turing a loop cu into a regular hotcue which currently requires deleting the loop cue and create a hotcue in the same position.

Yes, I'm also suffering from this lack of flexibility with saved loop. I think we could extend the WCueMenuPopup to provide a way to change the cue type, and also the out (or goto for beatjump). It could be as simple as Set the (goto/out) to the current position, with position adjusted automatically if quantised is enabled. I think that could be a way to get this feature out with a minimum amount of UI change, and while also generating value with Hotcue management overall as you suggested.

[JoergAtGithub]

I just pushed a PR with an updated version of #4528 : #13172
Just the backend, no GUI.