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

Effects rack #6388

Closed
Rossmaxx opened this issue Apr 27, 2022 · 8 comments
Closed

Effects rack #6388

Rossmaxx opened this issue Apr 27, 2022 · 8 comments

Comments

@Rossmaxx
Copy link
Contributor

Rossmaxx commented Apr 27, 2022

I feel like it would be a good idea to have an effects rack similar to controller rack. This window contains all the effects controls.

IMG_20220427_204118
this is a mock up i made with pen and paper.

This is a good way of organizing all those effects control windows into one single window. This can also help people with RSI issues as they don't need to locate different controls as everything is available within one window. This can also help move us closer to budislav's single window concept.

This idea is just my opinion. If you differ from my view, feel free to do so. This issue is meant to initiate discussion on this topic. If anyone is kind enough to make a design and send it in here, feel free.

Do note that to implement this, we would need to have a redesign of all the effects plugins.

@musikBear
Copy link

If i understand you you would like a screen where all effect-plugins that has been used in the complete project are both listed, and can be edited.
Is that correct?

@Monospace-V
Copy link
Contributor

iirc you still can't open Peak Controllers from Controller Rack... god help you if you forgot to name it, now you gotta scroll through all your instruments and guess which controller corresponds to what on the controller rack 😬 I'm a bit upset about that.
If it's the same thing with FX- unmapped, uneditable directly from there, just some info, it's going to be pretty useless.

@Rossmaxx
Copy link
Contributor Author

If i understand you you would like a screen where all effect-plugins that has been used in the complete project are both listed, and can be edited. Is that correct?

You are correct. That's exactly what i want.

@Rossmaxx
Copy link
Contributor Author

Rossmaxx commented Apr 27, 2022

iirc you still can't open Peak Controllers from Controller Rack... god help you if you forgot to name it, now you gotta scroll through all your instruments and guess which controller corresponds to what on the controller rack 😬 I'm a bit upset about that. If it's the same thing with FX- unmapped, uneditable directly from there, just some info, it's going to be pretty useless.

#2944 is the fix for the issue you stated and it's very similar to my proposal (tbh that's what gave me the idea in the first place.)

@Monospace-V
Copy link
Contributor

#2944 is the fix for the issue you stated and it's very similar to my proposal (tbh that's what gave me the idea in the first place.)

Not finished, and unmerged. But thanks for pointing it out. I felt like there was a report for that but I couldn't find it.
I notice that the issue you linked to doesn't appear to have info on what parameter each controller is mapped to. Not capable of compiling it to check though.

@Rossmaxx
Copy link
Contributor Author

Rossmaxx commented Apr 29, 2022

I notice that the issue you linked to doesn't appear to have info on what parameter each controller is mapped to.

The solution to that issue can be found in my mockup (ie my pen sketch). In the title bar of the peak controller, we can just add
audiofileprocessor/808kick

Hope that fixes it.
Pinging @BaraMGB

@RiedleroD
Copy link
Contributor

I've long wanted a way to split, copy, merge and manipulate individual channels in the effects tab - but I think that'd need a complete rework of the effects system, wouldn't it?

Still, I wanted to mention that because if we're collecting ideas for a unified effect rack, this could be relevant.

@Rossmaxx
Copy link
Contributor Author

Looking back, some of what i specified is stupidity and not really practical. I'll open another issue with better proposal and mockups later

@Rossmaxx Rossmaxx closed this as not planned Won't fix, can't repro, duplicate, stale Apr 13, 2024
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