-
-
Notifications
You must be signed in to change notification settings - Fork 74
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
Reuse Playback-object ? #78
Comments
Hi Thomas, Right now there is no way to update BUT I have plans regarding what you talking about. So please don't close the issue and let's discuss what API will be most flexible and useful. I suppose we should introduce some collection type (like ObservableCollection) which will fire some event like Does this sound good for you? Max |
Hi Max, |
Thomas, Right now I'm working on documentation of DryWetMIDI so I'll return to this task as soon as possible. Please be patient :) |
Thomas, I'm ready to implement the feature. Please tell me what kind of objects do you want to track first? Low-level ( |
Hi Max, By the way: Best regards |
Thomas, Yes, you can use instances of any class that implements OK, I'm starting the feature implementation :) |
Small piece of news. I'm implementing the feature in separate branch: playback-source. It's quite difficult task with a lot of things involved so please be patient. I suppose the first implementation will not be effficient in terms of performance but I hope we'll improve it with your feedback :) |
Setup benchmarking to store API performance metrics in InfluxDB Cloud to monitor how new feature will affect playback latency. |
Hi Max,
I have a question referring the "Playback" object:
If I created a playback-object, and I'm now using it (e.g. also by having added EventHandlers and play-event filters) and now I'm modifying the midi-events:
Do I always have to recreate a new Playback-object? Or can I anyhow reuse it and give the updated chunks/midi-events to it? (So I don't always have to add the event-handlers to it, or to set a new current time........)
Best regards
Thomas
The text was updated successfully, but these errors were encountered: