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
Refactoring of TimeManager #152
Comments
|
I presume that the new TimeManager will be able to ramp BPM on the fly? It would be a pity to lose that functionality (even though its currently buggy..) Agreed that LibRubberband is OT for this rework (so should be a seperate PR) and that JACK time slave is "additional" when done (so can be done later, to avoid having to rework twice). The main TimeManager and TimeObserver indeed need refactoring in one big bang, please refrain from starting this work until #153 is completed (it will cause any patches no longer apply cleanly). |
|
"ramp BPM on the fly?": Do you mean change BPM on the fly? Yes, that is a must.
I'll wait until you give me the o.k. to go! |
|
luppp and hydrogen and seq24 are not working well together because of the jack time master, sequentially seq24 crashes and sometimes hydrogen crashes when I try mistakenly to stop the time in one of the two programs but not in luppp |
|
I love the idea of JACK Transport. Unfortunatly its not as easy to implement as it might seem. Note also that the restlying of the codebase is completed, so theres' nothing (bar time and priority) stopping this work from going ahead :) |
|
Hi, just for the info: My time plans are a bit delayed. But I'll expect
to START the refactoring latest beginning march.
regards Gerald
…On 02/02/2017 12:20 AM, Harry van Haaren wrote:
I love the idea of JACK Transport. Unfortunatly its not as easy to
implement as it might seem.
RE other programs crashing, thats for their bug trackers.
RE Luppp not behaving as it should; that is known, and should be
addressed by this refactoring work.
Note also that the restlying of the codebase is completed, so theres'
nothing (bar time and priority) stopping this work from going ahead :)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#152 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AHO9dDff7unNuV0EtnnutXtyfM4aEEHbks5rYRNXgaJpZM4LDrXo>.
|
|
@geraldmwangi - thanks for the update - no stressure (stress / pressure :) |
|
Hey @geraldmwangi, how are things going? ;) |
|
He gcrk,
Stressy as hell. My PhD was revoked by one of the referees. He doesn't
like my style of writing . Have to revamp the whole thing:(
And you?
Gerald / JimsonDrift
…On 08/03/2017 12:26 PM, Georg Krause wrote:
Hey @geraldmwangi <https://github.com/geraldmwangi>, how are things
going? ;)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#152 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AHO9dIBRBdrY6QFxsEaYXbaNrnXz7_v9ks5sUaBHgaJpZM4LDrXo>.
|
|
@geraldmwangi ouch - sorry to hear that - Good luck! -H |
I would like to suggest a redesign of TimeManager class and the TimeObserver class.
The features I would like to implement are the following:
together with Tap-tempo a drummer, percussionist could controll the TimeManager with a pad for Nudge,
and another pad for Tap-tempo
Some of the features can be implemented separately (rubberband, jack slave), but the others must be done in one redesign of TimeManager. Am I missing more features/aspects?
The text was updated successfully, but these errors were encountered: