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

A play-this button on each FX-mixer-channel #2513

Open
musikBear opened this issue Jan 20, 2016 · 6 comments
Open

A play-this button on each FX-mixer-channel #2513

musikBear opened this issue Jan 20, 2016 · 6 comments

Comments

@musikBear
Copy link

Label: Suggestions > = 1.2.1
Just as it is useful to be able to listen to a preset in song-editor, i think it could be useful, if each single-usage mixer-channel had the same button.
A mockup :
fxmixerplaybutton
The implementation is a copy of the button in song-editor, with two important differences.

  • If more than one preset is using the same fx-channel, there should not be a play button.
  • If more than one fx-channels SEND to the channel, there should not be a play button.

The functionality became relevant as i tried to move channels around into groups. There i missed being able to listen to the allocated presets.

@Umcaruje
Copy link
Member

So, this could be a useful idea, but I think at the moment the amount of time an energy that would need to be invested in implementing a feature with such a limited use case is not something we can afford.

If in the future an instrument gets an FX channel auto-assigned (that is, that no instrument should be connected directly to master) this could prove as a useful, but for now, I can mark this as an enhancement, but I doubt it'll get implemented. Another option can be that we close this, and let it wait for better times, and then reopen it.

@musikBear you decide.

@musikBear
Copy link
Author

close this, and let it wait for better times, and then reopen it.

@Umcaruje alternatively it could just get a sceduled-mark for 1.3, or later, then it wont disappear between the closed enhancements?

@Umcaruje
Copy link
Member

@Umcaruje alternatively it could just get a sceduled-mark for 1.3, or later, then it wont disappear between the closed enhancements?

К, tbh I'm fine either way, keep in mind that this is very unlikely to get implemented.

@tresf
Copy link
Member

tresf commented Jan 26, 2016

it wont disappear between the closed enhancements?

<offtopic>As opposed to being buried with the open ones? We haven't been tagging anything for 1.3 lately because we've lost our most active developers. This changes day-to-day though, but we're in no position to guarantee any major enhancement for a major version. The developers which took assignments aren't active anymore, so we're back to the "scratch an itch" workflow, sorry. </offtopic>.

@musikBear
Copy link
Author

offtopic> because we've lost our most active developers

oh that sad! Who left curlymorphic? How about diiz? Long time since i saw any post from him. Ofcause i have no right to ask for info, but i have not seen anything mentioned about anyone leaving the team

@tresf
Copy link
Member

tresf commented Jan 26, 2016

No one is gone forever, but yes there are a few (some named above and some not named above) who's contributions were invaluable to the project.

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

3 participants