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

MIXER - Allow Vertical Stretching To The Mixer Window #3258

Closed
miketurn opened this issue Jan 13, 2017 · 9 comments
Closed

MIXER - Allow Vertical Stretching To The Mixer Window #3258

miketurn opened this issue Jan 13, 2017 · 9 comments

Comments

@miketurn
Copy link
Contributor

miketurn commented Jan 13, 2017

If vertical stretching was allowed in the Mixer window, using the channel name label cutoff point (represented by the red line in the following graphic) then you could stretch the mixer out, allowing you all the room you need for channel name labels.
mixer - current

Here is what it can look like....
(A side benefit would be that you would also be able to see all effects linked to that channel if desired, rather than a limiation of 4 effects.)
mixer - vertically stretched

@BaraMGB
Copy link
Contributor

BaraMGB commented Jan 13, 2017

Why to heck you want to use such long channel names? You invested a massive amount of brain energy to this issue. 😳

@mikobuntu
Copy link
Contributor

mikobuntu commented Jan 13, 2017

I think the channel names space could be increased a bit perhaps ( not just as much as your mockup tho @miketurn) ...and the idea that we see more effect plugins is good , but I would prefer the mixer LED's to be taller and to have some markers at crucial DB levels. there is another post somewhere that describes better scaling of the levels. I will make a mockup with my thoughts in my next reply.
Being a Bitwig user I love the way we can maximise the mixer channels for fine tuning levels, right now in LMMS it is a bit of a guessing game as to what level we are actually at...

@Spekular
Copy link
Member

Spekular commented Jan 13, 2017 via email

@miketurn
Copy link
Contributor Author

@BaraMGB

Why to heck you want to use such long channel names? You invested a massive amount of brain energy to this issue. 😳

Just trying to help to improve the program, but thank you for the comment that makes me feel good about spending time on it, hopefully you feel good about yourself too.

The second graphic obviously is overdone to show that the window has have been stretched vertically, I am not saying anyone HAS to stretch it out that far, it just gives others the options to adjust the height.
As mentioned it also allows you to see more effects if desired.

Have a great day

@BaraMGB
Copy link
Contributor

BaraMGB commented Jan 13, 2017

Actually I like this approach. It would work with an (evetually) implementation of a one-window-solution in future.

@tresf
Copy link
Member

tresf commented Jan 13, 2017

vertical stretching [...] in the Mixer

Yes.

I told you I would rock your worlds, with this post. This post was so massively ground breaking that it caused a "Major Service Outage" at GitHub when I tried to post it, the servers just couldn't handle it!
If you don't believe me just ask the angry rainbow colored 404 unicorn.

🦄

@musikBear
Copy link

buuut it will still be quite difficult to read those verticals 👎

@miketurn
Copy link
Contributor Author

Okay....
Well while I am on the track of upsetting some, I guess this would be a good time to keep the train running with the following....
This idea of being able to vertically stretch the mixer may also offer a solution for the following....
#1974 (Which I am aware has been closed)
I posted some thoughts at the bottom of that thread if anyone is interested in some opinions.
As I mention there, I agree that it is a tough decision and I get why it may not be wanted, but might be worth some consideration, maybe something modular.

@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.

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

8 participants