Adding a value to a controller

Inspired by ThreeDee's filter 'Branching', I started to expand and experiment a bit with that filter.
I ran into the following problems :

Branching has many Perlin Noise Components. I want to have one controller to adjust all the Angles of the Perlin Noises, but giving them slightly different values.
I tried to add different amounts for each Perlin component to the basic controller. I used Add from the RGBmath. But that does not work, as the Angle input from the Perlin Noise component does not accept the RGBmath output.

So basically, I want to have a slider and add different amounts to this control signal that must go into the Angle input of the Perlin. How do I do that?

I attached a simple example of the question.

FF Question 2.ffxml

You're a rapid replier, Rachel, thanks.
I had seen your answer yesterday, just as I was going to bed, so it had to wait until today.

I get your solution, quite clever. I hadn't thought of that. I was too fixated on doing it with arithmetic.

Still, it would be nice to have some basic arithmetic components for controller values (+ - x / at least).
In more complicated situations than my example, it might not be possible to do it with Remapping.

I will think of some situations where I think 'real' arithmetic is needed.

Your solutions give some new possibilities to to simple/basic things with the controllers + it also opens up some new possibilities.

In the same vain, I came up with a solution for a simple "On/Off" for each channel of a MultiBlend. See attached example.

I know Switches, I know Curve Switches (the blue ones), but what are Map switches?
I would like to learn more as to 'recalculate' (meaning, putting the controller values through a function) controllers that can go into the Grey inputs.

E.g. how can I make 1 controller give control values of 50 -100 for grey input 1 and at the same time go from 50 down to 0 for the second grey input?
A easy function would do the trick, but that seems not possible in FF.

I also think it would be great if every component has a bypass switch so it can let through the signal without affecting it. Of course with a switch object it is possible, but these objects take up much space in the editor and do make the whole filter less clear. A simple Bypass option would do the tick, like on an effect pedal for a guitar

FF Example On-Off.ffxml

Check out this topic to look at an example using Map Switches to deal with grey inputs. Towards the bottom of the topic is a Map Switch example to show a workaround to manipulate otherwise "constant" grey values.

Grey inputs are very different than green ones. With a green input, for example, you can specify a different value at every pixel which is powerful, but much more complex. Grey values are a constant value over the whole bitmap, which is partly why they are made for control components. I can’t emphasize enough how much more complex green inputs are hence many inputs are grey.

Lua is powerful but has limitations. The main one being it can only use one core of your CPU. I’ve done a few filters with it: I found it difficult to work with, especially debugging.