FX Container with mapping pannel

[Georgedayren]

Fx Container with mapping pannel

Vote above, please.

Sometimes in my project i have too many Fx instances on some track, become not comfortable, and i not only one with that problem. FX Container can solve this, and new way for save favorite fx chains in containers.

One instance vs. hundreds

[dasombre]

I really hope that FX-chain improvements are next on the list.
It really seems very outdated and not practical at all at the moment.

The concept above is what I'm hoping for:
parallel chains in one track, and macros for those (with Min/Max assignments).

Please Devs, let this be next!

[mschnell]

There already have been multiple feature requests on this issue. A "container with Macro Parameter 'knobs' " in fact is the way to go.

IMHO such a container (or multiple containers, in fact container even should be able to host other containers) should be just an optional different view on the FX chain (plus provide the macro parameter handling) as the routing already is possible by Reaper out of the box. So no "real" audio routing needs to be done in the "container".

-Michael

[dim-x]

This would be great.

[Georgedayren]

Better way to call it - "FX Folder", it's like track folder, but FX. It's easy, but, i think, developers don't read this thread...

[mschnell]

Originally Posted by Georgedayren

Better way to call it - "FX Folder", it's like track folder, but FX. It's easy, but, i think, developers don't read this thread...

Bad idea, IMHO ! A container should be usable exactly like - and generally look quite like - a plugin, even though part of it's function is similar to a folder.

-Michael

[Stevie]

What about Blue Cat's Audio PatchWork ??

https://www.bluecataudio.com/Product...uct_PatchWork/

[mschnell]

Nice, but the task in question does not need to use CPU cycles to route the audio streams through anything additionally to/from the active plugins. Reaper already does provide the routing. Only a more "user friendly" GUI to configure the routing and control the plugin parameters is requested.

Moreover such a "master" plugin will not be able to hold JSFX plugins. IMHO this is a nogo.

Besides, a price much higher than Reaper itself seems rather inappropriate for the additional GUI comfort.

(See several other threads on that issue...)

-Michael

[Georgedayren]

in patchwork you can't map many parameters to one knob, and you can't map "bypass plugin", this very important for me

[Lokasenna]

This will get you halfway there: http://forum.cockos.com/showthread.php?t=170044

[Georgedayren]

Lokasenna, i want to use presaved containers with saved mapping

[Georgedayren]

up and vote!

[mpl]

So you suggest to add additional mess with routing, saving A LOT of plugin state data (take a look at RPP with at least one Kontakt instance), make project file more than 1Gb which will hold all this data, add more mess to REAPER FX chain GUI (which is already looks like nerd heaven)?

Thanks, but I don`t want to get a "WTF?" when opening someone`s project with pure madness like this.
Use powertful REAPER routing instead this piece of hell.

[Ozman]

How about LBX Stripper?

[Georgedayren]

Originally Posted by mpl

So you suggest to add additional mess with routing, saving A LOT of plugin state data (take a look at RPP with at least one Kontakt instance), make project file more than 1Gb which will hold all this data, add more mess to REAPER FX chain GUI (which is already looks like nerd heaven)?

Thanks, but I don`t want to get a "WTF?" when opening someone`s project with pure madness like this.
Use powertful REAPER routing instead this piece of hell.

In Ableton it works fine!


Stripper - good thing, but 20 instances samplomatic in one channel in mixer looks like train station

[Georgedayren]

Up! Up! Up!

[occultron]

this has been my #1 FR for REAPER for years...

[krahosk]

FX container is now implemented as of v6.77+dev0305 - March 5 2023.