2017-composer's wishes
- KVRAF
- 13863 posts since 24 Jun, 2008 from Europe
Indeed i want to avoid bloatedness as much as possible. I know one little irrelevant thing won't make it completely bloated, but it's where bloatedness starts.
For M7 solution is simple and easy, imho: Name the tracks as you want, eventually including a MIDI chan nr.
For M7 solution is simple and easy, imho: Name the tracks as you want, eventually including a MIDI chan nr.
- KVRist
- 128 posts since 28 Apr, 2017 from "Me? I live everywhere, or I'd be dead"
Perhaps the best route for now is Plugins. But what happens when a plugin is no longer developed and becomes unstable? The only solution is for you to take over or lose the functionality provided by such plugins. Obviously, you have enough on your plate, so the reality is that the plugin would be ditched.mutools wrote:Open sourcing the whole project is not an option. Open sourcing specific parts or making an SDK for writing functional plugins may be an option. I'm thinking about things. Also R&Ding M8.
Unless the development of plugins is a more community based affair. Where you monitor and offer limited guidance where necessary. This way, if a plugin dev loses interest and the plugin becomes unstable, the community could offer updates/solutions.
- KVRist
- 128 posts since 28 Apr, 2017 from "Me? I live everywhere, or I'd be dead"
That's what makes this DAW so attractive, after all!mutools wrote:Indeed i want to avoid bloatedness as much as possible. I know one little irrelevant thing won't make it completely bloated, but it's where bloatedness starts.
For M7 solution is simple and easy, imho: Name the tracks as you want, eventually including a MIDI chan nr.
- KVRAF
- 7412 posts since 8 Feb, 2003 from London, UK
Perhaps any new plugin-API-based content could be required to be open source (e.g. "by use of this API, you agree to the follow licence terms .. your code will be {insert open source licence here}"). That way it would allow the community to maintain any desired content even after the original author had moved on.freddo wrote:Unless the development of plugins is a more community based affair. Where you monitor and offer limited guidance where necessary. This way, if a plugin dev loses interest and the plugin becomes unstable, the community could offer updates/solutions.
-
- KVRist
- Topic Starter
- 230 posts since 8 Dec, 2015
Mutools, could you please implement a mode that sets ruler-zoom and song-position for every track identically?
At least to me it would be useful, when I'm in Edit-mode and click a track to edit, than another one to look, what we play there, than another one, than back one to the edited track.
It would be even more attractive to see multiple tracks at the same time. But I don't ask for that because I think, that would be really difficult to implement.
But when composing, I need to get a vertical impression. The actual existing individual view has it's advantages, but not always. Should be selectable.
At least to me it would be useful, when I'm in Edit-mode and click a track to edit, than another one to look, what we play there, than another one, than back one to the edited track.
It would be even more attractive to see multiple tracks at the same time. But I don't ask for that because I think, that would be really difficult to implement.
But when composing, I need to get a vertical impression. The actual existing individual view has it's advantages, but not always. Should be selectable.
- KVRAF
- 13863 posts since 24 Jun, 2008 from Europe
I understand your request but atm can't give a confirmation / estimation when it will be implemented. As a semi solution you could assign key shortcuts to the Copy Time Zoom and Paste Time Zoom functions and use these to quickly sync editor views.
-
- KVRist
- Topic Starter
- 230 posts since 8 Dec, 2015
Is there a chance to fix racks in the rack-area in some way?
I'd find it useful, if (at least) the master-rack and eventually a spectrum analyzer would be visible always, even if you need to scroll horizontally.
I'd find it useful, if (at least) the master-rack and eventually a spectrum analyzer would be visible always, even if you need to scroll horizontally.
- KVRAF
- 7412 posts since 8 Feb, 2003 from London, UK
Drop into Modular view. Double click to open up the Master rack. Switch back to composer view. The Master rack will be floating. You can close the mixing desk, too, if you want.nenneb wrote:Is there a chance to fix racks in the rack-area in some way?
I'd find it useful, if (at least) the master-rack and eventually a spectrum analyzer would be visible always, even if you need to scroll horizontally.
-
- KVRAF
- 2270 posts since 30 Aug, 2004 from Lancaster, UK
Yes very clever and it must allow for total customization. Then it's just to save it as the default project. 
Thu Oct 01, 2020 1:15 pm Passing Bye wrote:
"look at SparkySpark's post 4 posts up, let that sink in for a moment"
Go MuLab!
"look at SparkySpark's post 4 posts up, let that sink in for a moment"
Go MuLab!
-
- KVRAF
- 2270 posts since 30 Aug, 2004 from Lancaster, UK
One idea: there are many options for default coloring of various elements in MuLab. At the same time I always color rack belonging to the same instruments group the same way, such as red for drums and purple for bass.
Since the instruments (and audio) are logically grouped (like Keys or MFO), could there be a color setting per group? That would be a great timesaver and very cool: just drag in a trance synth to create a new rack and it's color becomes screaming yellow.
Since the instruments (and audio) are logically grouped (like Keys or MFO), could there be a color setting per group? That would be a great timesaver and very cool: just drag in a trance synth to create a new rack and it's color becomes screaming yellow.
Thu Oct 01, 2020 1:15 pm Passing Bye wrote:
"look at SparkySpark's post 4 posts up, let that sink in for a moment"
Go MuLab!
"look at SparkySpark's post 4 posts up, let that sink in for a moment"
Go MuLab!
