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

FX set offline/online - Track "all by name" not working when using "*" #549

Closed
Matt37137 opened this issue Mar 30, 2022 · 9 comments
Closed
Labels
enhancement New feature or request high priority

Comments

@Matt37137
Copy link

Reaper takes cpu when fx are online, even when You mute the track they are on or take fx off. You implemented set fx online, but only one by one. It's great, but it would be awesome, if we could do it faster, with all fx on a track.

@helgoboss
Copy link
Owner

You can do that already. Just use "All by name" and enter "*".

@Matt37137
Copy link
Author

Matt37137 commented Mar 30, 2022

Actually I don't... I tested it, and it doesn't work. It works only if I give relearn exact name of the track. Every character must be the same. If i use "" or "?" it won't do the action, even when I select "by name" not "all by name". The "" works great in "fx all by name", but not track.

EDIT: Tested on 2.13.0-pre.1

@helgoboss
Copy link
Owner

Not the track selector (you already know which track). The FX selector. Check this out: https://imgur.com/a/8eFjTFu

@helgoboss
Copy link
Owner

Or do you want to do that on multiple tracks at once? In that case, please adjust the description.

@Matt37137
Copy link
Author

Matt37137 commented Mar 30, 2022

Yes, but I'm looking for a solution to do this on more than one track, with "all by name". So I would only need one mapping to offline multiple tracks. But great info about using just "*" to select all things, didn't though about that.

EDIT: I thought it would work that way, because in option "all by name" I can always use "*". Didn't know that wasn't implemented, yet.

@Matt37137 Matt37137 changed the title Track: set all fx online/offline FX set offline/online - Track "all by name" not working when using "*" Mar 30, 2022
@helgoboss
Copy link
Owner

Okay, this is a general limitation at the moment: "All by ..." selectors don't "multiply". E.g. if you target multiple tracks via "All by name" and multiple FX via "All by name", then only the first track is considered, but all matching FX on that first track. Would not be difficult to change this, but obviously one has to be careful with this because used wrong it can affect many FX in many tracks ... e.g. it can be slow, be changing too much in one go so users get confused.

@Matt37137
Copy link
Author

Ok, I understand. That's why I thought about using something like Track: offline/online all FX, just like Track: enable/disable all FX. In this case, It could be used with only one "All by name" for tracks, because You can't change FX.

Now I'm using, select tracks: all by name, and then use reaper action: fx offline, which is very slow. So I get that it wont be lightning fast, but everything will be faster than my current approach.

As I can see, using "all selected tracks" in FX offline doesn't work either.

With that limitation on board, I would need to make like 30 of those mappings :)

@helgoboss
Copy link
Owner

Yes, "All selected tracks" shares the same limitation.

Well, I think building extra targets would result in too much target bloat, so I guess I will just lift this limitation. But it will probably not be considerably faster than your current solution ... maybe it will save some time because it doesn't need to select the tracks that it affects.

@helgoboss helgoboss reopened this Mar 30, 2022
@helgoboss helgoboss added the enhancement New feature or request label Mar 30, 2022
@Matt37137
Copy link
Author

Best way would be, that reaper actually unload CPU and ram, when using "disable all fx", but we have, what we have :) Selecting multiple tracks at once is actually quite a long process. Would very appreciate if You would lift this limitation! :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request high priority
Projects
None yet
Development

No branches or pull requests

2 participants