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

Add a button to enable a piano-roll TCO #4209

Closed
musikBear opened this issue Mar 2, 2018 · 4 comments
Closed

Add a button to enable a piano-roll TCO #4209

musikBear opened this issue Mar 2, 2018 · 4 comments

Comments

@musikBear
Copy link

Enhancement:
We have all done this:
Dobble click a TCO pressed play, and had -no- replay..
Yes the track is muted..
So the 'fix' is to

  • close this piano-roll
  • find the track in question in song-editor
  • enable the track
  • re-locate the TCO in question
  • open that (by now free¤%%#) piano-roll

Because of that i suggest a diode inside piano-roll, that will enable replay-Something like
piano-roll-enabler

@WrillicR
Copy link
Member

WrillicR commented Mar 2, 2018

This is a great idea, and it'd definitely find myself using it. I think a better title may be 'Add a button to mute a piano-roll TCO '.

@tresf
Copy link
Member

tresf commented Mar 2, 2018

Muted piano rolls shouldn't stay muted when played from the Piano Roll editor. This is really a bug in my eyes. Adding a "mute" LED as an indicator that song-playback won't occur is a good idea, but BB tracks would need to be enhanced with this as well, as they add an additional layer of potential muting.

But to take this further, most of this is a UI band-aid because we have a clunky MDI-style windowing system. A single-window interface would guarantee that we have the potential for all components to be on-screen at the same time.

@musikBear
Copy link
Author

A single-window interface

true 👍

@tresf
Copy link
Member

tresf commented Mar 11, 2019

As part of a pruning effort, this enhancement request is archived into a dedicated "Better Workflow" checklist here #4877.

@tresf tresf closed this as completed Mar 11, 2019
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

4 participants