-
Notifications
You must be signed in to change notification settings - Fork 115
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
Redesign the orchestra pit model #150
Comments
I guess we can support both modes: probably by introducing a notion of "shared" and "owned" instruments, so that the latter will have their settings saved within a project and tracked in a version control. The code changes seem straightforward, but the UI side needs some thinking.
Mind suggesting the way it should look from the user's perspective? Maybe some hotkey to bring up the current instrument's window, if it has one? |
Also refactor the PluginWindow class a bit
For orchestral music, the concept of having an orchestra pit with some well known presets is probably quite good, as you can focus on creating the music rather than monkeying about with adding half a string section to each new project. However, for electronic music, it's often the case that each project will demand entirely different instruments (or at least different variations of instruments based on some common presets). Perhaps it would be a good idea to allow per-project instruments to be set up - after all, this is a common pattern in most DAWs and notation software.
Another issue for me is that I like to be able to tweak and listen to my synths from inside the piano roll/arranger interface, which I am able to do in any other DAW, but I don't think that's possible in Helio - for me, I will often explore different sound design and melodies at the same time as some melodies feel better with some synth presets, and I found that one often influences the other.
The text was updated successfully, but these errors were encountered: