Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: Improved loop control (a.k.a. poor man's loop based sequencing) #21

Open
Gimmeapill opened this issue May 11, 2016 · 4 comments

Comments

@Gimmeapill
Copy link

Dear Rui,

I understand loop based sequencing may not be a high priority (as with other linear DAWs - fair enough), but wouldn't it be possible to improve a bit the looping control to make it more "pattern like"?
I'm thinking here about moving the loop section on the fly while playing with keyboard shortcuts / midi cc.
Something like "Shift current loop section's next start point forward/backward by X beats", and once the play head reach that start, move the loop end marker accordingly and continue looping without disruption. Or one step further: define several loop boundaries and bind them to keyboard shortcuts / midi and jump there on the next loop occurence.

The only implementation examples I am aware of who do that well are trackers: Renoise & Buzz for example. I hope this makes kind of sense, and apologies if the feature was already dismissed - I didn't find it mentioned anywhere.

@rncbc
Copy link
Owner

rncbc commented May 26, 2016

something like that about location markers and scripting arein the long term plans. yes.

cheers.

@Gimmeapill
Copy link
Author

Just saw your note on Ableton_link and transport modes in the latest release notes. This goes in the same direction isn't it?

@rncbc
Copy link
Owner

rncbc commented Apr 21, 2017

i guess it's not the same direction at all. at least in terms of anything related to loop-control.

ableton_link is kinda a plg-and-play, shared metronome, so it tells peers or participants a common tempo (bpm) and beat phase to link in on the fly.

whether you can take advantage of jack_link for jack-transport-aware applications, such as qtractor, is probably a way too vague of a stretch in regard to loop-control, if you know what i mean.

cheers

@Gimmeapill
Copy link
Author

Ah ok, thanks for the clarification. Yes, that's probably not very useful in qtractor yet.
But getting rock solid on the fly bpm and measure sync with the ableton world for jack applications (if I understood correctly what this jack_link is about) sounds like a rather good thing to have. Interesting :-)

rncbc pushed a commit that referenced this issue May 4, 2020
qtractor v0.9.14 translations update call
rncbc pushed a commit that referenced this issue Feb 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants