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

Dynamic Track Control FX targets only work with one 1 fx #907

Open
mortfell opened this issue Jan 21, 2024 · 3 comments
Open

Dynamic Track Control FX targets only work with one 1 fx #907

mortfell opened this issue Jan 21, 2024 · 3 comments

Comments

@mortfell
Copy link

mortfell commented Jan 21, 2024

Using the method referenced in this issue 42

We can map controls in realearn to the "Track FX parameters" and will receive feedback correctly... but In cases where Track Control FX in Reaper span multiple FX slots, only effects from the lowest numbered fx slot are recognized and targeted.

These controls are intended to be global to the track and usable across multiple fx slots so this is not the behaviour when mapping to Reapers actions for controlling Track FX Parameters.
If you control using reapers own actions for accessing "track fx parameters" it works across multiple fx slots as expected, but of course there is no feedback available.

As mentioned in issue 42, this feature in Reaper is a bit odd because it doesn't allow us full control of the order FX appear, but I still find myself using track control mappings and I know others do as well.

@helgoboss
Copy link
Owner

How to make track control FX span multiple FX slots? I guess I don't know that feature.

@mortfell
Copy link
Author

mortfell commented Jan 21, 2024

Oh hey. I'll try and explain it better.
It's already possible to use ReaLearn to control parameters across plugin slots with Track Controls

If you assign fx parameters from multiple fx slots in reaper using "Show In Track Controls"
Reaper doesn't care if these come from different fx slots.
Parameters will organize in the track control panel grouped by the order of the plugin slots they come from.

For instance if slot 1 is reaeq and you have a hi pass filter enabled as a track control
and slot 2 is a delay effect and you have the feedback enabled as a track control
TCPFX 1 will be hi pass filter
TCPFX 2 will be the feedback

If I have controls mapped in ReaLearn using Reaper actions:
Adjust track FX parameter (01 through 16)
AKA Reaper Action ID's: 950 to 965
The controls on the surface map to the track controls sequentially across fx slots in the order they appear.
So this works fine ! But doesn't provide feedback, so is a problem for using with something like a midi fighter twister that has an LED ring.

What i'm trying to see is:
In issue 42 linked above you suggest using:
Set FX to and enter tcp_fx_indexes[0]
Set FX parameter to and enter tcp_fx_parameter_indexes[0]
To get feedback from the track control fx parameters.

This works! and I can access, for instance, 8 parameters by assigning Set FX parameter sequentially
ie. tcp_fx_parameter_indexed[0]
tcp_fx_parameter_indexed[1]
tcp_fx_parameter_indexed[2]
etc.
But using this method, controls will only successfully map to fx's from the first slot that has parameters enabled with "Show In Track Controls".
Is there a way I could adjust the method I'm using to access parameters from more than one slot?
or is there a limitation in the current implementation of this method?

thanks!

@ankarfeldt
Copy link

Was playing around with this yesterday as well.
Would be great to map across the different FX that could be shown in the "Track FX Parameter".

For instance see this picture. There's 3 plugins that all have a parameter shown in as a Track FX Parameter.
Skærmbillede 2024-02-21 kl  20 01 35

Through the Action window, I could use these below, and they would just control each of the Track FX Parameters in the order they appear. But it doesn't give me feedback on my motored faders. Would be awesome to have that.
Skærmbillede 2024-02-21 kl  20 01 16

But maybe the Reaper API lacks this.
Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants