|
|
|
07-24-2020, 05:10 AM
|
#9761
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,183
|
Quote:
Originally Posted by poetnprophet
hey there, you also have to make sure the file name of the zon file for the FX is written exactly right. Basically same as how it's listed inside the zone, but without the : and ()
|
Actually, the filename doesn't matter at all, as long as it doesn't conflict with another filename -- the internal name must be exactly right as you state.
__________________
To install you need the CSI Software and Support Files
For installation instructions and documentation see the Wiki
Donate -- via PayPal to waddingtongeoff@gmail.com
|
|
|
07-24-2020, 06:39 AM
|
#9762
|
Human being with feelings
Join Date: Aug 2006
Location: Berlin
Posts: 11,817
|
The method of correctly showing FX parameters of a plugin on my Faderport 16 control surface eludes me.
In this example ReaComp is the first insert on a track.
The FX Zone is basically just one parameter for testing:
Code:
Zone "VST: ReaComp (Cockos)"
SelectedTrackNavigator
Fader1 FXParam 0 "Thresh"
FPScribble1 FXParamNameDisplay 1
ZoneEnd
In my "Buttons|" zone, part of the home zone is this:
Plugin MapSelectedTrackFXToWidgets
Pressing the Plugin button gets me this log entry:
IN <- FP16s1 Plugin 1.000000
IN <- FP16s1 90 2b 00
That second message is the button being let go of. The MST "Plugin" widget only uses
Code:
Widget Plugin // labeled "Edit Plugins"
Press 90 2b 7f
FB_TwoState 90 2b 7f 90 2b 00
WidgetEnd
I have another button to reload the home zone, but shouldn't this setup be enough ?
There was an attempt to use focused fx, but that had the same result. Nothing at all happened.
|
|
|
07-24-2020, 07:30 AM
|
#9763
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,870
|
Quote:
Originally Posted by airon
Code:
Zone "VST: ReaComp (Cockos)"
SelectedTrackNavigator
Fader1 FXParam 0 "Thresh"
FPScribble1 FXParamNameDisplay 1
ZoneEnd
|
Try:
Code:
Zone "VST: ReaComp (Cockos)"
SelectedTrackNavigator
Fader1 FXParam 0
FPScribble1 FXParamNameDisplay 0 "Thresh"
ZoneEnd
Also put:
Code:
OnTrackSelection MapSelectedTrackFXToWidgets
in your FaderPort16 Zone,
and put
Code:
Plugin ToggleMapSelectedTrackFX
in your Buttons| Zone.
|
|
|
07-24-2020, 11:02 AM
|
#9764
|
Human being with feelings
Join Date: Jan 2011
Location: The Hague, The Netherlands
Posts: 17
|
Hi friends, I bought the Faderport 8 a couple of days ago.
Following the instructions on the CSI installation I put the CSI-folder in Reaper resource path, closed Reaper and put the reaper_csurf_integrator.dll in Plugins-folder of same resource path. But when I restart Reaper, after two seconds, Reaper stops, vanishes. I tried everything..
I think it's got something to do with the the fact I had to install Microsoft Visual C++ 2019 runtime. WITHOUT installing Visual C the Control Surface Integrator didn't show up. But WITH Visual C installed Reaper stops..
Any suggestions?
|
|
|
07-24-2020, 11:18 AM
|
#9765
|
Human being with feelings
Join Date: Aug 2006
Location: Berlin
Posts: 11,817
|
Thank you sir, that worked nicely.
Now I'm curious how to solve the Focused FX problem. The method detailed in the wiki does not appear to work.
Another already solved problem is that of really fucking dumb spread of values on the 0 to 1 scale, like the Decay time on Valhalla Room. Or the threshold of ReaComp only going to 0dB (=1.0 VST parameter).
Can anyone recall where to find those fun little parameter step ranges and how one could map them to a 14-bit fader so the parameter is mapped to a range of values that an absolute encoder/fader can control in a more convenient manner ?
I recall large tables being posted and referenced somehow. Maybe all I need is a pointer, if anyone would be so kind.
|
|
|
07-24-2020, 11:46 AM
|
#9766
|
Human being with feelings
Join Date: Jul 2007
Location: New Joisey
Posts: 5,990
|
Quote:
Originally Posted by airon
Can anyone recall where to find those fun little parameter step ranges and how one could map them to a 14-bit fader so the parameter is mapped to a range of values that an absolute encoder/fader can control in a more convenient manner ?
|
What exactly are you looking for? Got an example.
If you're talking about how to calculate the number of parameter steps, take the number of steps on the plugin, subtract 1 and divide the result by 1 for the step size.
So if your plugin parameter has 3 steps. Take 3, subtract 1. You get 2. Divide 1 by 2 and you get 0.5. That's your step size. Steps start at 0.0 and end at 1.0. So you get:
( 0.0 0.5 1.0 )
If your plugin parameter has 4 steps, it's 1 divided by 3. The result is .333. Now, round that up to .334 or .34. Your step size is:
( 0.0 0.34 0.67 1.0 )
|
|
|
07-24-2020, 11:52 AM
|
#9767
|
Human being with feelings
Join Date: Aug 2006
Location: Berlin
Posts: 11,817
|
An interesting behaviour here.
I'm creating a zone for Valhalla Room on the Faderport 16. Thankfully I won't need a second bank of parameters.
Whenever I touch a fader that parameters value shows up on the scribble strip. In fact it shows up on ALL scribble strips.
Anyone know how to show the value of a parameter on just one scribble strip ?
Code:
Zone "VST: ValhallaRoom (Valhalla DSP, LLC)"
SelectedTrackNavigator
FPScribble1 FXParamNameDisplay 1 "predelay"
FPScribble2 FXParamNameDisplay 2 "decay"
FPScribble3 FXParamNameDisplay 3 "HighCut"
FPScribble4 FXParamNameDisplay 4 "earlyLateMix"
FPScribble5 FXParamNameDisplay 5 "lateSize"
FPScribble6 FXParamNameDisplay 6 "lateCross"
FPScribble7 FXParamNameDisplay 18 "diffusion"
FPScribble8 FXParamNameDisplay 19 "type"
FPScribble9 FXParamNameDisplay 9 "RTBassMultiply"
FPScribble10 FXParamNameDisplay 10 "RTXover"
FPScribble11 FXParamNameDisplay 11 "RTHighMultiply"
FPScribble12 FXParamNameDisplay 12 "RTHiXover"
FPScribble13 FXParamNameDisplay 13 "earlySize"
FPScribble14 FXParamNameDisplay 14 "earlyCross"
FPScribble15 FXParamNameDisplay 15 "earlyModRate"
FPScribble16 FXParamNameDisplay 16 "earlyModDepth"
Fader1 FXParam 1
FaderTouch1 TrackTouch
TrackTouch+FPScribble1 FocusedFXParamValueDisplay 1
Fader2 FXParam 2
FaderTouch2 TrackTouch
TrackTouch+FPScribble2 FocusedFXParamValueDisplay 2
Fader3 FXParam 3
FaderTouch3 TrackTouch
TrackTouch+FPScribble3 FocusedFXParamValueDisplay 3
Fader4 FXParam 4
FaderTouch4 TrackTouch
TrackTouch+FPScribble4 FocusedFXParamValueDisplay 4
Fader5 FXParam 5
FaderTouch5 TrackTouch
TrackTouch+FPScribble5 FocusedFXParamValueDisplay 5
Fader6 FXParam 6
FaderTouch6 TrackTouch
TrackTouch+FPScribble6 FocusedFXParamValueDisplay 6
Fader7 FXParam 18
FaderTouch7 TrackTouch
TrackTouch+FPScribble7 FocusedFXParamValueDisplay 7
Fader8 FXParam 19
FaderTouch8 TrackTouch
TrackTouch+FPScribble8 FocusedFXParamValueDisplay 8
Fader9 FXParam 9
FaderTouch9 TrackTouch
TrackTouch+FPScribble9 FocusedFXParamValueDisplay 9
Fader10 FXParam 10
FaderTouch10 TrackTouch
TrackTouch+FPScribble10 FocusedFXParamValueDisplay 10
Fader11 FXParam 11
FaderTouch11 TrackTouch
TrackTouch+FPScribble11 FocusedFXParamValueDisplay 11
Fader12 FXParam 12
FaderTouch12 TrackTouch
TrackTouch+FPScribble12 FocusedFXParamValueDisplay 12
Fader13 FXParam 13
FaderTouch13 TrackTouch
TrackTouch+FPScribble13 FocusedFXParamValueDisplay 13
Fader14 FXParam 14
FaderTouch14 TrackTouch
TrackTouch+FPScribble14 FocusedFXParamValueDisplay 14
Fader15 FXParam 15
FaderTouch15 TrackTouch
TrackTouch+FPScribble15 FocusedFXParamValueDisplay 15
Fader16 FXParam 16
FaderTouch16 TrackTouch
TrackTouch+FPScribble16 FocusedFXParamValueDisplay 16
ZoneEnd
|
|
|
07-24-2020, 12:08 PM
|
#9768
|
Human being with feelings
Join Date: Aug 2006
Location: Berlin
Posts: 11,817
|
Quote:
Originally Posted by airon
|
Solved this myself.
FX Zone:
FocusedFXNavigator
F16 Zone:
OnFXFocus MapFocusedFXToWidgets
Plugin ToggleMapFocusedFX
This was rather hard to find. The documentation HAS to be changed for this.
It is still claiming that using "widgetname MapFocusedFXToWidgets" as a trigger an accomplish this, but this no longer works. The method above does.
Quote:
Originally Posted by Funkybot
What exactly are you looking for? Got an example.
If you're talking about how to calculate the number of parameter steps, take the number of steps on the plugin, subtract 1 and divide the result by 1 for the step size.
So if your plugin parameter has 3 steps. Take 3, subtract 1. You get 2. Divide 1 by 2 and you get 0.5. That's your step size. Steps start at 0.0 and end at 1.0. So you get:
( 0.0 0.5 1.0 )
If your plugin parameter has 4 steps, it's 1 divided by 3. The result is .333. Now, round that up to .334 or .34. Your step size is:
( 0.0 0.34 0.67 1.0 )
|
I need to remap incoming data to different VST parmater data than it's currently doing. I've got a reverb decay parameter whose value goes from 0.1 to 10 seconds within less than 10 millimeters of my fader travel. It's linear as the reverb time goes to 100 seconds. It's unusable this way.
Thus, I want a ease-in curve, like the third fade-in shape for items in Reaper. More values from my fader would
Some folks appear to have made such data, but I don't know if this can be applied to absolute controls.
Last edited by airon; 07-24-2020 at 12:48 PM.
|
|
|
07-24-2020, 01:21 PM
|
#9769
|
Human being with feelings
Join Date: Jul 2007
Location: New Joisey
Posts: 5,990
|
If you want to just limit the parameter range, that's an option. You can see this:
https://github.com/malcolmgroves/rea...rameter-ranges
I imagine that will work for other widget types. Give it a shot at least.
|
|
|
07-24-2020, 05:53 PM
|
#9770
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,870
|
Quote:
Originally Posted by airon
Some folks appear to have made such data, but I don't know if this can be applied to absolute controls.
|
I don't think it will work with absolute controls, only encoders. And those huge tables were a PITA btw, I haven't used them since encoder acceleration was introduced.
|
|
|
07-24-2020, 09:33 PM
|
#9771
|
Human being with feelings
Join Date: Aug 2006
Location: Berlin
Posts: 11,817
|
A feature request it is then.
There are plenty of offending parameters like that, even in ReaComp. It seems to be an aspect of design overlooked by some plugin designers.
So, the request:
Mapping 7-bit and 14-bit(often with 10-bit resolution) controllers to FP32 0 to 1.0 data via curves, likely upon startup. That‘s a 32 kb lookup table for 14 bit controllers, which is likely adequate for any OSC controller as well.
Parameters for setup could be curve type and one additional parameter for bendines. The fun detail here is that this would need to be part of the zone file, as faders would want to be used in a linear fashion as well.
I realize this may or may not be possible for quite a while.
|
|
|
07-25-2020, 12:30 AM
|
#9772
|
Human being with feelings
Join Date: Aug 2019
Location: Forest City
Posts: 336
|
Hi.
I´m looking for FX_zones of Fabfilter products for 8 channel surface.
Anyone so kind to share, please?
Cheers, WT
|
|
|
07-25-2020, 04:47 AM
|
#9773
|
Human being with feelings
Join Date: Aug 2006
Location: Berlin
Posts: 11,817
|
The C4 zone folder has some for the ProQ3 iirc.
Still, I wish this was as easy to setup as it was on the Avid Icon consoles. Perhaps the S5/S6 are easy too.
@Geoff , getting better I should hope. Please do.
|
|
|
07-25-2020, 07:09 AM
|
#9774
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,183
|
OK, I had the cataract operation for the other eye about 2 weeks ago. Just got cleared by the doctor yesterday to drive again, so I'm now back to more or less normal
Because of the delay, I posted some interim builds with the new architecture:
CSI beta Test.zip
reaper_csurf_EuCon Test.zip
Those brave souls out there -- you know who you are -- please give the new builds a try.
Have a look at CSI.ini and MCU.zon for examples of how to modify your existing files.
Basically:
CSI.ini now has params for number of channels, Sends, FX, etc.
The "|" notation has been removed from Zone naming line, it still exists in the body of the file, but now the type of navigator determines how many to make.
I'm sure there will be questions / issues, etc. so don't forget this is a test only
__________________
To install you need the CSI Software and Support Files
For installation instructions and documentation see the Wiki
Donate -- via PayPal to waddingtongeoff@gmail.com
|
|
|
07-25-2020, 07:38 AM
|
#9775
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,870
|
Quote:
Originally Posted by Geoff Waddington
OK, I had the cataract operation for the other eye about 2 weeks ago. Just got cleared by the doctor yesterday to drive again, so I'm now back to more or less normal
|
Glad to hear you're on the mend Don't over do it!
Quote:
Because of the delay, I posted some interim builds with the new architecture:
CSI beta Test.zip
reaper_csurf_EuCon Test.zip
|
These don't seem to be links?
|
|
|
07-25-2020, 07:41 AM
|
#9776
|
Human being with feelings
Join Date: Aug 2006
Location: Berlin
Posts: 11,817
|
Quote:
Originally Posted by Funkybot
|
I gave that a go, but all that did was limit up to where the controls did anything. It did not spread the value range on to the entirety of my absolute controller, in this case a 100mm fader.
|
|
|
07-25-2020, 07:41 AM
|
#9777
|
Human being with feelings
Join Date: Jul 2007
Location: New Joisey
Posts: 5,990
|
Quote:
Originally Posted by MixMonkey
Glad to hear you're on the mend Don't over do it!
These don't seem to be links?
|
Search the stash. They’re over there.
https://stash.reaper.fm/v/40102/CSI%20beta%20Test.zip
|
|
|
07-25-2020, 07:42 AM
|
#9778
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,870
|
Quote:
Originally Posted by Funkybot
|
Gotcha!Cool
|
|
|
07-25-2020, 07:48 AM
|
#9779
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,870
|
Quote:
Originally Posted by WaveTrans
Hi.
I´m looking for FX_zones of Fabfilter products for 8 channel surface.
Anyone so kind to share, please?
Cheers, WT
|
Here's my ProQ3 for Mackie C4. You can probably de-construct it to use with your surface. I've included a parameter list to go with.
Last edited by MixMonkey; 09-06-2020 at 11:44 AM.
|
|
|
07-25-2020, 08:41 AM
|
#9780
|
Human being with feelings
Join Date: Aug 2019
Location: UK
Posts: 65
|
Multiple Instances of Same Effect Bug?
Hi
I managed to get my XTouch Mini working to control an instance of my Waves LA2A compressor. However, if I add more than one copy of the same effect on the same track, only one of them is controllable.Is this a bug or am I doing something wrong?
I'm calling the effect using:
Zone Home
OnTrackSelection MapSelectedTrackFXToWidgets
ZoneEnd
Also, the LA2A has a toggle switch to switch between compressor and limit mode. I have this mapped to a button press on my controller. When I press the button, the switch changes from compressor to limit mode. I was hoping that a second press would switch it back but this doesn't seem to be the case. Is there a way of achieving this functionality?
Thanks
Simon
|
|
|
07-25-2020, 08:50 AM
|
#9781
|
Human being with feelings
Join Date: Aug 2006
Location: Berlin
Posts: 11,817
|
Quote:
Originally Posted by Pompeysie
Hi
I managed to get my XTouch Mini working to control an instance of my Waves LA2A compressor. However, if I add more than one copy of the same effect on the same track, only one of them is controllable.Is this a bug or am I doing something wrong?
I'm calling the effect using:
Zone Home
OnTrackSelection MapSelectedTrackFXToWidgets
ZoneEnd
Also, the LA2A has a toggle switch to switch between compressor and limit mode. I have this mapped to a button press on my controller. When I press the button, the switch changes from compressor to limit mode. I was hoping that a second press would switch it back but this doesn't seem to be the case. Is there a way of achieving this functionality?
Thanks
Simon
|
Yeah, try this :
SomeButtonWidget FXParam 2 [ 0.1 0.3 0.6 1.0 ]
This will cycle through these four values every time the widget SomeButtonWidget is triggered. I just tried this myself and it works nicely.
For users of Notepad++ here are three language definitions for MST , ZON and OST files.
https://stash.reaper.fm/manage_file/...adPlusPlus.zip (2kB)
Use Language / User Defined Language / Define your own language , and the IMPORT button you find there to integrate them in to Notepad++.
Last edited by airon; 07-25-2020 at 09:00 AM.
|
|
|
07-25-2020, 09:25 AM
|
#9782
|
Human being with feelings
Join Date: Aug 2019
Location: UK
Posts: 65
|
Quote:
Originally Posted by airon
Yeah, try this :
SomeButtonWidget FXParam 2 [ 0.1 0.3 0.6 1.0 ]
This will cycle through these four values every time the widget SomeButtonWidget is triggered. I just tried this myself and it works nicely.
For users of Notepad++ here are three language definitions for MST , ZON and OST files.
https://stash.reaper.fm/manage_file/...adPlusPlus.zip (2kB)
Use Language / User Defined Language / Define your own language , and the IMPORT button you find there to integrate them in to Notepad++.
|
Thanks. I also found out, if it's only a two state button the toggle function works - e.g. Toggle+LayerA_UpperButton1 FXParam 4 "Comp/Limiter".
Thanks for showing me how to step through parameters. How do you get the numbers in the brackets? The LA76 compressor has the ratio buttons which I can step through using the code you provided but I need one more value to step through all 5 paremeters.
Any thoughts about the issue with multiple versions of the same effect on one track?
|
|
|
07-25-2020, 09:29 AM
|
#9783
|
Human being with feelings
Join Date: Jul 2007
Location: New Joisey
Posts: 5,990
|
Quote:
Originally Posted by Geoff Waddington
OK, I had the cataract operation for the other eye about 2 weeks ago. Just got cleared by the doctor yesterday to drive again, so I'm now back to more or less normal
I'm sure there will be questions / issues, etc. so don't forget this is a test only
|
Hi Geoff, super glad to hear things are going well and normalcy is returning!
I'm kicking the tires on this test build and there's definitely some weirdness. The #1 issue at the moment is Banking. Using the X-Touch One with either the default MCU .mst/.zon files or my modified .mst/.zon files (made updates to the .zon for the new syntax which is much simpler!), it just refuses to bank properly. I can get it to go as high as Track 9 at times (in a 2-9 bank) but that's it.
Selected Track Navigator where everything is hardcoded to Fader1 seems to work though.
EuCon crashed the first few times I tried, but starting by checking out MIDI Devices and will work up to EuCon.
|
|
|
07-25-2020, 10:15 AM
|
#9784
|
Human being with feelings
Join Date: Jul 2007
Location: New Joisey
Posts: 5,990
|
Also, FocusedFX didn't work at all.
Returned to the May 5th build for now. Definitely like the simplicity of the new .zon syntax and look forward to that getting stable.
|
|
|
07-25-2020, 10:41 AM
|
#9785
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,183
|
Quote:
Originally Posted by Funkybot
Also, FocusedFX didn't work at all.
Returned to the May 5th build for now. Definitely like the simplicity of the new .zon syntax and look forward to that getting stable.
|
Thank, was just trying to see if you could even get to the stage where you could say Focused FX doesn't work -- which it doesn't
Also glad to see Selected works.
Bummer on Track Bank and EuCon.
Thanks for the quick look, just what was needed.
If you knew how much was changed you would be amazed even that much works -- I know I am
__________________
To install you need the CSI Software and Support Files
For installation instructions and documentation see the Wiki
Donate -- via PayPal to waddingtongeoff@gmail.com
|
|
|
07-25-2020, 10:41 AM
|
#9786
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,183
|
Quote:
Originally Posted by Pompeysie
Any thoughts about the issue with multiple versions of the same effect on one track?
|
That is not supported -- yet
__________________
To install you need the CSI Software and Support Files
For installation instructions and documentation see the Wiki
Donate -- via PayPal to waddingtongeoff@gmail.com
|
|
|
07-25-2020, 10:44 AM
|
#9787
|
Human being with feelings
Join Date: Aug 2006
Location: Berlin
Posts: 11,817
|
Quote:
Originally Posted by Pompeysie
Thanks. I also found out, if it's only a two state button the toggle function works - e.g. Toggle+LayerA_UpperButton1 FXParam 4 "Comp/Limiter".
Thanks for showing me how to step through parameters. How do you get the numbers in the brackets? The LA76 compressor has the ratio buttons which I can step through using the code you provided but I need one more value to step through all 5 paremeters.
|
There are probably a few ways. I just tested one and it worked fine I suppose.
Create a project with your plugin in question. Set that track to LATCH and place the playhead at the start of the project. The preferences should have Automation/Automatically add envelope in writing mode checkbox ticked.
Play and go through the settings of your parameter in question. Press stop. Save. Open the project in a text editor.
There you will find something like this:
Code:
PT 0.096 0.08333333 0
PT 3.16266667 0.08333334 0
PT 3.18933333 0.16666667 0
PT 4.86933333 0.16666667 0
PT 4.91733333 0.25 0
PT 6.27733333 0.25 0
PT 6.31466667 0.33333334 0
PT 7.53066667 0.33333334 0
PT 7.568 0.41666665 0
PT 8.81066667 0.41666666 0
PT 8.848 0.5 0
PT 10.16 0.5 0
PT 10.192 0.58333331 0
PT 11.504 0.58333331 0
PT 11.536 0.66666668 0
PT 12.976 0.66666669 0
PT 13.008 0.74999999 0
PT 14.43733333 0.75 0
PT 14.48 0.83333331 0
PT 15.92533333 0.83333331 0
PT 15.94133333 0.91666668 0
PT 17.376 0.91666669 0
PT 17.41333333 1 0
PT 24.56533333 1 0
You can keep the project open. Set timeline to SECONDS to get a match to the timecodes in the session data.
Now you have values attached to the different states of the plugin.
Quote:
Any thoughts about the issue with multiple versions of the same effect on one track?
|
Renaming an instance of the plugin you want treated differently does the trick. Name the second instance something else.
This other name should have its own Zone file if you want to use both at the same time in SelectedTrack mode. For FocusedFX this is easy. Just make a copy of the Zone file.
This worked for me. Actually I'll be using this mechanism as well, since I have a pre-comp EQ and a post-comp EQ. The pre-comp EQ will get a different zone with the name I give that instance. It's an extra step to change it if you put that plugin in, but that's a very small price to pay for that kind of flexibility.
So renaming an instance works fine.
Last edited by airon; 07-25-2020 at 10:53 AM.
|
|
|
07-25-2020, 11:22 AM
|
#9788
|
Human being with feelings
Join Date: Jul 2007
Location: New Joisey
Posts: 5,990
|
Quote:
Originally Posted by Geoff Waddington
Thank, was just trying to see if you could even get to the stage where you could say Focused FX doesn't work -- which it doesn't
Also glad to see Selected works.
Bummer on Track Bank and EuCon.
Thanks for the quick look, just what was needed.
If you knew how much was changed you would be amazed even that much works -- I know I am
|
Hey, I figured if you weren't ready to post it as an official update, that I should keep expectations low and treat it as a preview build. So not surprised some things weren't working.
If you want someone to privately check things out and test ahead of an official shift, feel free to shoot me some builds via email (same name here at gmail) or PM. Otherwise, no sweat, I'll eagerly await your progress.
|
|
|
07-25-2020, 11:23 AM
|
#9789
|
Human being with feelings
Join Date: Jul 2007
Location: New Joisey
Posts: 5,990
|
Quote:
Originally Posted by airon
Renaming an instance of the plugin you want treated differently does the trick. Name the second instance something else.
So renaming an instance works fine.
|
Clever! I love the ingenuity of this crowd.
|
|
|
07-25-2020, 11:41 AM
|
#9790
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,870
|
Quote:
Originally Posted by airon
Renaming an instance of the plugin you want treated differently does the trick. Name the second instance something else.
This other name should have its own Zone file if you want to use both at the same time in SelectedTrack mode. For FocusedFX this is easy. Just make a copy of the Zone file.
This worked for me. Actually I'll be using this mechanism as well, since I have a pre-comp EQ and a post-comp EQ. The pre-comp EQ will get a different zone with the name I give that instance. It's an extra step to change it if you put that plugin in, but that's a very small price to pay for that kind of flexibility.
|
Re-naming a plugin in an FX chain also works and has some advantages over re-naming individual instances ie the chains (even if they only contain one plugin) can be saved and reloaded.
|
|
|
07-25-2020, 12:55 PM
|
#9791
|
Human being with feelings
Join Date: Aug 2019
Location: UK
Posts: 65
|
Quote:
Originally Posted by MixMonkey
Re-naming a plugin in an FX chain also works and has some advantages over re-naming individual instances ie the chains (even if they only contain one plugin) can be saved and reloaded.
|
Got ya, I think. So, for example, I might have two instances of an LA2A in an effects chain and I could call one LA2A and the other LA2AB then have two different on files, one for each?
|
|
|
07-25-2020, 04:40 PM
|
#9792
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,870
|
Quote:
Originally Posted by Pompeysie
Got ya, I think. So, for example, I might have two instances of an LA2A in an effects chain and I could call one LA2A and the other LA2AB then have two different on files, one for each?
|
Yep, you got it It's the name of the plugin within the chain that CSI sees and that's what has to match the FX.zon file.
The only difference between naming the instances in an FX chain and @Airon's method, is that the chain can be saved and reused, so you don't need to remember what you called the plugin. Other than that, they're identical
|
|
|
07-26-2020, 12:49 AM
|
#9793
|
Human being with feelings
Join Date: Aug 2019
Location: UK
Posts: 65
|
Quote:
Originally Posted by airon
There are probably a few ways. I just tested one and it worked fine I suppose.
Create a project with your plugin in question. Set that track to LATCH and place the playhead at the start of the project. The preferences should have Automation/Automatically add envelope in writing mode checkbox ticked.
Play and go through the settings of your parameter in question. Press stop. Save. Open the project in a text editor.
There you will find something like this:
Code:
PT 0.096 0.08333333 0
PT 3.16266667 0.08333334 0
PT 3.18933333 0.16666667 0
PT 4.86933333 0.16666667 0
PT 4.91733333 0.25 0
PT 6.27733333 0.25 0
PT 6.31466667 0.33333334 0
PT 7.53066667 0.33333334 0
PT 7.568 0.41666665 0
PT 8.81066667 0.41666666 0
PT 8.848 0.5 0
PT 10.16 0.5 0
PT 10.192 0.58333331 0
PT 11.504 0.58333331 0
PT 11.536 0.66666668 0
PT 12.976 0.66666669 0
PT 13.008 0.74999999 0
PT 14.43733333 0.75 0
PT 14.48 0.83333331 0
PT 15.92533333 0.83333331 0
PT 15.94133333 0.91666668 0
PT 17.376 0.91666669 0
PT 17.41333333 1 0
PT 24.56533333 1 0
You can keep the project open. Set timeline to SECONDS to get a match to the timecodes in the session data.
Now you have values attached to the different states of the plugin.
Renaming an instance of the plugin you want treated differently does the trick. Name the second instance something else.
This other name should have its own Zone file if you want to use both at the same time in SelectedTrack mode. For FocusedFX this is easy. Just make a copy of the Zone file.
This worked for me. Actually I'll be using this mechanism as well, since I have a pre-comp EQ and a post-comp EQ. The pre-comp EQ will get a different zone with the name I give that instance. It's an extra step to change it if you put that plugin in, but that's a very small price to pay for that kind of flexibility.
So renaming an instance works fine.
|
Thanks very much for your help. Very much appreciated.
|
|
|
07-26-2020, 02:14 AM
|
#9794
|
Human being with feelings
Join Date: Aug 2019
Location: Forest City
Posts: 336
|
Quote:
Originally Posted by MixMonkey
Here's my ProQ3 for Mackie C4. You can probably de-construct it to use with your surface. I've included a parameter list to go with.
|
Excellent, thanks.
This helps a lot.
Cheers WT
|
|
|
07-26-2020, 09:41 AM
|
#9795
|
Human being with feelings
Join Date: Aug 2019
Location: UK
Posts: 65
|
Zones and FX
Hi
Still playing with my X-Touch Mini (not a euphemism!). I want to try and map Pro-Q 3 (FabFilter) to it. I have attached an image of the surface if you are not familiar with it.
I only want to map Frequency, Gain and Q to three of the rotary controllers but I want to do this for any new band that I add to the software UI. I suspect I can do this using different zones but I'm really unsure of the syntax to use.
My idea is that when I press one of the buttons (or even one of the encoders) it instantiates a zone for one of the bands and allows me to use the first three encoders to control Freq, gain and Q. Push the next button or the next encoder and I am controlling the next band using the same three encoders.
Does this make sense?
Thanks
Simon
|
|
|
07-26-2020, 11:28 AM
|
#9796
|
Human being with feelings
Join Date: Aug 2006
Location: Berlin
Posts: 11,817
|
Take a look at the C4 zone files for the ProQ3.
You need button controls to change between bands.
It‘ll work by changing Zones. One zone per band. That makes 24 of them.
|
|
|
07-26-2020, 03:13 PM
|
#9797
|
Human being with feelings
Join Date: Dec 2019
Location: Los Angeles, CA
Posts: 64
|
FX parameter "default value"
Hey all,
I'm setting up my new Midi Fighter Twister to be my FXFocus surface. Everything is working well thus far, but I've hit a snag. Let's use a compressor as an example. I have the first encoder mapped to "Threshold". I would like to be able to push the encoder and have the threshold value snap to its default — the same thing that happens when I alt-click the threshold knob in Reaper.
I know you can apply modifiers on the control surface's end (e.g., holding a button while moving a fader) but I cannot find any indication that you can use a control to trigger something like a "command-click" in Reaper. I've looked over the Wiki and did some forum searches, but I can't find a solution for this.
Thanks for your help, as always!
|
|
|
07-26-2020, 03:30 PM
|
#9798
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,870
|
Quote:
Originally Posted by mattrglenn
Hey all,
I'm setting up my new Midi Fighter Twister to be my FXFocus surface. Everything is working well thus far, but I've hit a snag. Let's use a compressor as an example. I have the first encoder mapped to "Threshold". I would like to be able to push the encoder and have the threshold value snap to its default — the same thing that happens when I alt-click the threshold knob in Reaper.
I know you can apply modifiers on the control surface's end (e.g., holding a button while moving a fader) but I cannot find any indication that you can use a control to trigger something like a "command-click" in Reaper. I've looked over the Wiki and did some forum searches, but I can't find a solution for this.
Thanks for your help, as always!
|
You could achieve the same result by mapping the press to send a single value- the value that represents the default. The syntax is exactly the same as that used for stepped values, except there's only one 'step'.
|
|
|
07-26-2020, 04:39 PM
|
#9799
|
Human being with feelings
Join Date: Jun 2015
Location: Sydney, Australia
Posts: 180
|
Quote:
Originally Posted by airon
Solved this myself.
FX Zone:
FocusedFXNavigator
F16 Zone:
OnFXFocus MapFocusedFXToWidgets
Plugin ToggleMapFocusedFX
This was rather hard to find. The documentation HAS to be changed for this.
It is still claiming that using "widgetname MapFocusedFXToWidgets" as a trigger an accomplish this, but this no longer works. The method above does.
|
OK, given you're the most recent one to go through this, do you want to write something up and post it here. We can then update the docs.
Cheers
Malcolm
|
|
|
07-26-2020, 05:08 PM
|
#9800
|
Human being with feelings
Join Date: Sep 2017
Location: London, England.
Posts: 4,870
|
Quote:
Originally Posted by Geoff Waddington
Those brave souls out there -- you know who you are -- please give the new builds a try.
Have a look at CSI.ini and MCU.zon for examples of how to modify your existing files.
|
Gave it a whirl I have faders, pans, displays, buttons. VCAs and banking.
Sends, FXMenu (and presumably FX mapping) are missing. Also the Hold modifier is broken.
Not bad for first test! I like the setting of the surface size in the CSI prefs
I'm currently using the build from April 24th as the Sends toggle works correctly in that one (I'm pretty sure that the builds after that one were addressing Eucon issues, so I'm not really missing out on anything )
|
|
|
Thread Tools |
|
Display Modes |
Linear Mode
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -7. The time now is 09:21 AM.
|