LBX Stripper - create custom channel strips

[Vincent Sermonne]

~Added double-click (yes double-click - I bothered to work it out ) - but not for default value - instead to open Edit Value box.

GREAT ADD !! thank you !!

I can swap the double-click action to do default value if people prefer, and swap the Edit Value box to Ctrl-click. Whatever the general consensus is.

I like your choice.



WOAW how to do for control the bypass of the plug-in of the other track ???

[lb0]

Originally Posted by Vincent Sermonne

GREAT ADD !! thank you !!



I like your choice.



WOAW how to do for control the bypass of the plug-in of the other track ???

Use the learn button? This lets you insert parameters from any track onto the current track.

[lb0]

Originally Posted by Vincent Sermonne

GREAT ADD !! thank you !!

No problem. I wasn't sure it was possible - as I couldn't find any API to help directly with this - so I worked out a brute force method which seems to work nicely. Fortunately it's a fairly linear complexity algorithm, so to check up to 5 decimal place normalized value - it uses only maximum of 50 loop iterations. 10dp = 100 max iterations. So it's pretty fast. I'm sure someone with a better maths head could come up with something simpler or more efficient - but I'm happy with this.

[Vincent Sermonne]

I don't understand how the learn work... sorry.

[lb0]

Originally Posted by Vincent Sermonne

I don't understand how the learn work... sorry.

in FX PARAM edit mode - next to the FX PARAM label should be a 'L' button. Click to open the learn window.

Then - simply move any parameter within the plugin window (ie. the VST's own plugin GUI) - this parameter should appear in the Learn box in Stripper.

Then drag the control image from the Learn box to the grid.

Let me know how you get on

[Vincent Sermonne]

I miss something ?

[lb0]

Originally Posted by Vincent Sermonne

I miss something ?

Ah yes - disable TBProAudios metering plugin before using learn function - for some reason it plays havoc with reapers last touched fx parameter.

Hopefully this can be fixed in the future .

[Vincent Sermonne]

Originally Posted by lb0

Ah yes - disable TBProAudios metering plugin before using learn function - for some reason it plays havoc with reapers last touched fx parameter.

Hopefully this can be fixed in the future .

and with a js have the same probleme too...
But when i desengage it, it work perfectly !!!
The "MEM BUTTON" is it for ?

[lb0]

Originally Posted by Vincent Sermonne

and with a js have the same probleme too...

any particular one? it might just be the way some js's work - but it seems to be reapers GetLastTouchedFX api function that gets affected - not much I can do from my end...

[lb0]

Originally Posted by Vincent Sermonne

and with a js have the same probleme too...
But when i desengage it, it work perfectly !!!
The "MEM BUTTON" is it for ?

MEM BUTTON - set the default value - this will be the value it switches to. Basically it allows for toggling a parameter between 2 states. One state is the fixed one (default value of the control), the other is whatever the current value of the parameter is.

So say you wanted to compare different gain settings on an EQ - set the mem buttons default value to (example) 0 - then move the gain (using another knob control mapped to the same parameter) - then you can use the MEM button to toggle between the new gain setting and 0 (without resorting to bypassing the band). If you want to easily change the default value of the MEM button - use Ctrl-right-click will set the default value to current value of parameter.

[Vincent Sermonne]

Originally Posted by lb0

any particular one? it might just be the way some js's work - but it seems to be reapers GetLastTouchedFX api function that gets affected - not much I can do from my end...

I have send to you a pm with the js code

[Vincent Sermonne]

Originally Posted by lb0

MEM BUTTON - set the default value - this will be the value it switches to. Basically it allows for toggling a parameter between 2 states. One state is the fixed one (default value of the control), the other is whatever the current value of the parameter is.

So say you wanted to compare different gain settings on an EQ - set the mem buttons default value to (example) 0 - then move the gain (using another knob control mapped to the same parameter) - then you can use the MEM button to toggle between the new gain setting and 0 (without resorting to bypassing the band). If you want to easily change the default value of the MEM button - use Ctrl-right-click will set the default value to current value of parameter.

WAOUW ! You can make like a preset ! I want more than 2 Yes a preset list will be great for my project...

[lb0]

Originally Posted by Vincent Sermonne

I have send to you a pm with the js code

thanks - there is a common thing about both TBPros and that one in which they use _Automate - which I assume triggers the last touched fx value to update. I think we'll just have to disable for now when required. Or I could add a flag or something that auto disables all flagged fx when the learn window opens? So you would need to flag any problem fx for each project.

[lb0]

Originally Posted by Vincent Sermonne

WAOUW ! You can make like a preset ! I want more than 2 Yes a preset list will be great for my project...

Surely for more than two - you would use a cycle button? Or am i not fully understanding you?

[lb0]

Originally Posted by Vincent Sermonne

WAOUW ! You can make like a preset ! I want more than 2 Yes a preset list will be great for my project...

Maybe you misunderstand my description:

https://www.youtube.com/watch?v=ODwtVVWdj5o

[timbralzoom]

Originally Posted by lb0

Maybe you misunderstand my description:

https://www.youtube.com/watch?v=ODwtVVWdj5o

i think "preset list" sounds like one MEM button to control all eq parameters,
kind a A/B but more like the full alphabet

if so.....i like it!

[Vincent Sermonne]

Originally Posted by lb0

Maybe you misunderstand my description:

https://www.youtube.com/watch?v=ODwtVVWdj5o

It Is incredible !! You Script is fantatic !!

[timbralzoom]

Originally Posted by Vincent Sermonne

GREAT ADD !! thank you !!



I like your choice.



WOAW how to do for control the bypass of the plug-in of the other track ???

parameters from another track ability (Learn) was my main reason to add first
all vurmsmeter bypasses

[Vincent Sermonne]

French mac users have problems for load the script:
http://forum.cockos.com/showpost.php...5&postcount=27

[lb0]

Originally Posted by Vincent Sermonne

French mac users have problems for load the script:
http://forum.cockos.com/showpost.php...5&postcount=27

Hmmm... can you check whether they have downloaded RAW version from Github? Sorry - I must apologise that my french is very poor to your excellent English

There sometimes are issues with downloading the file as part of the zip file.

Alternatively - you can copy and paste all the script code into a new script within Reaper and saving...

[timbralzoom]

Originally Posted by Vincent Sermonne

French mac users have problems for load the script:
http://forum.cockos.com/showpost.php...5&postcount=27

this might be not relevant but,
just in case i would like the share my way to get Scripts from github:

-do not download direcly
-click to LBX Stripper.lua link,
-see and click to "RAW" button in the new page,
-copy all text from this RAW page,
-paste to a new note pad txt
-rename txt to "LBX Stripper"save it and change extension txt to lua.
so far so good to me.

[lb0]

Originally Posted by timbralzoom

i think "preset list" sounds like one MEM button to control all eq parameters,
kind a A/B but more like the full alphabet

if so.....i like it!

Ok - will ponder this - are you able to elaborate more what you (and Vincent) are thinking?

[lb0]

Originally Posted by timbralzoom

this might be not relevant but,
just in case i would like the share my way to get Scripts from github:

-do not download direcly
-click to LBX Stripper.lua link,
-see and click to "RAW" button in the new page,
-copy all text from this RAW page,
-paste to a new note pad txt
-rename txt to "LBX Stripper"save it and change extension txt to lua.
so far so good to me.

Yes - although (at least in firefox) you can view the RAW file - right-click the page and choose Save Page As... - this will save it with the correct name and extension all done.

[Vincent Sermonne]

Originally Posted by timbralzoom

this might be not relevant but,
just in case i would like the share my way to get Scripts from github:

-do not download direcly
-click to LBX Stripper.lua link,
-see and click to "RAW" button in the new page,
-copy all text from this RAW page,
-paste to a new note pad txt
-rename txt to "LBX Stripper"save it and change extension txt to lua.
so far so good to me.

Yes but from their posts, that's what they did.

[lb0]

Originally Posted by Vincent Sermonne

French mac users have problems for load the script:
http://forum.cockos.com/showpost.php...5&postcount=27

Hi Vincent,

I've taken a quick look at the french discussion - and could only pick out snippets. But it looks like they've tried the RAW version yes?

Would you be able to ask albatteur to copy down the code for his error line and pass to me. I don't know what version he is running - so need to see the code at line 686 to get an idea of what is going on.

Also check he has the latest version... and run again - then the line numbers will coincide and I can check.

[lb0]

Originally Posted by Vincent Sermonne

Yes but from their posts, that's what they did.

Hi Vincent - from one of Albatteurs screenshots - he has the controls/strips/graphics/icons folder in the LBX folder.

Should be in the LBX/LBXCS_resources/ folder.

Not sure why the error line is 686 - but can you ask Albatteur to place them where they should be - and running again.

I have posted a message on that thread - but incase I'm not fully understood.

Thanks for your help with this.

[Vincent Sermonne]

Originally Posted by lb0

Hi Vincent - from one of Albatteurs screenshots - he has the controls/strips/graphics/icons folder in the LBX folder.

Should be in the LBX/LBXCS_resources/ folder.

Not sure why the error line is 686 - but can you ask Albatteur to place them where they should be - and running again.

I have posted a message on that thread - but incase I'm not fully understood.

Thanks for your help with this.

ok ! your welcome !

[lb0]

Originally Posted by Vincent Sermonne

ok ! your welcome !

Not 100% sure if it will sort the problem - as mine gives error @ 935 when I put the folders in the wrong place. But maybe Mac's work slightly differently. Certainly there is nothing wrong with the code at 686 that he took the screenshot of. That's more like the problems you get with a dodgy download (not RAW file)...

Still - shall await a response.

[TBProAudio]

Originally Posted by timbralzoom

Thank you so much! TBProAudio!

Great use of my small JSXF code. In any case your VUMeter readout does not really look in line with needle pos?
I recently posted a VUMeter image strip which fits perfectly to JSFX...

Or did i miss something?

[lb0]

Originally Posted by TBProAudio

Great use of my small JSXF code. In any case your VUMeter readout does not really look in line with needle pos?
I recently posted a VUMeter image strip which fits perfectly to JSFX...

Or did i miss something?

Hi TBPro - I've been trying out your jsfx and it works great. One thing I've noticed is that when activated - it takes over the value returned by the reaper.GetLastTouchedFX API - so I cannot 'learn' other parameters until I disable it. Is this fixable? I guess it's due to the slider _Automate bit (not up with JSFX lingo). Is this constantly outputting values? Can it be made to output a value only when the value is different from the last? (or is it all 'under the hood') - I'm wondering if this might fix the issue. I really don't know how it works TBH

Vincent posted a GIF video on the previous page of this thread that shows the problem.

If not - it's not a big deal - I can cope with disabling the meter JSFX where necessary - it's just too good not to have

[TBProAudio]

Originally Posted by lb0

Hi TBPro - I've been trying out your jsfx and it works great. One thing I've noticed is that when activated - it takes over the value returned by the reaper.GetLastTouchedFX API - so I cannot 'learn' other parameters until I disable it. Is this fixable? I guess it's due to the slider _Automate bit (not up with JSFX lingo). Is this constantly outputting values? Can it be made to output a value only when the value is different from the last? (or is it all 'under the hood') - I'm wondering if this might fix the issue. I really don't know how it works TBH

Vincent posted a GIF video on the previous page of this thread that shows the problem.

If not - it's not a big deal - I can cope with disabling the meter JSFX where necessary - it's just too good not to have

Well, yes I saw the posts around this issue. For now I´m sorry, because i will be off for the next 3 days, so no quick solution.

But after my return I will have a look at it, sure. Outputting only new values could be a valid option, I will check this.

[timbralzoom]

Hi,
i am just an hobbyist about this technical stuff of metering...
( i mean at this level amateur : is it moving? yes ah! there is a signal i can try manipulate with fx )
decided to rec. a video
i hope make sense
https://www.youtube.com/watch?v=okFO3dSAcW8

also thanks for the graphic somehow i miss it!

[lb0]

Originally Posted by TBProAudio

Well, yes I saw the posts around this issue. For now I´m sorry, because i will be off for the next 3 days, so no quick solution.

But after my return I will have a look at it, sure. Outputting only new values could be a valid option, I will check this.

Absolutely no expectations here. Thought I would mention it - but don't worry or spend any time on it if it will take you too much time. I'm over the moon with what you've provided (as I've said before - DSP stuff is way out of my league).

[RJHollins]

testing the latest version [only briefly ... more later tonite].

note: I did have to re do [again] the 'display value' offset option. I saved and reloaded without issue.

This is expected [so no problem] as we beta-test.

[lb0]

Originally Posted by RJHollins

testing the latest version [only briefly ... more later tonite].

note: I did have to re do [again] the 'display value' offset option. I saved and reloaded without issue.

This is expected [so no problem] as we beta-test.

bit puzzled by this one though - not noticing same behaviour here. if it saves ok once and you close and reopen and it's ok - i'm not sure why it would then lose the setting later on. I've checked the load/save code - seems ok. I assume you are just saving and loading the project - not working with strips in particular (although they also seem to work ok).

[lb0]

Originally Posted by RJHollins

testing the latest version [only briefly ... more later tonite].

note: I did have to re do [again] the 'display value' offset option. I saved and reloaded without issue.

This is expected [so no problem] as we beta-test.

perhaps if it happens again - you could send me your rpp file? This is where the data is saved - would be good to see if the data is no longer in the project file.

[RJHollins]

Hi lb0,

The change in value has happened when I've updated to a newer version of LUA.

I figured that something might have changed in the new release, since once I save a layout, quit reaper, start a new project, drag in my LBX strip, all loaded correctly.

But I did have to make a offset correction with [at least] two LUA updates.

I will certainly watch for any abnormalities, since you say that is unexpected to happen. I now have a clearer purpose in upcoming testing. Will definitely keep you posted whether there is issue or not, so that you know.

THANKS

[lb0]

Originally Posted by RJHollins

Hi lb0,

The change in value has happened when I've updated to a newer version of LUA.

I figured that something might have changed in the new release, since once I save a layout, quit reaper, start a new project, drag in my LBX strip, all loaded correctly.

But I did have to make a offset correction with [at least] two LUA updates.

I will certainly watch for any abnormalities, since you say that is unexpected to happen. I now have a clearer purpose in upcoming testing. Will definitely keep you posted whether there is issue or not, so that you know.

THANKS

Ok - well I'm still not sure it should have happened. If it keeps happening I'll have to try and repeat it here. I suspect it may be certain circumstances that I've not come across yet.

Would like to see how double-click editing of values works for you and with Nebula. I really didn't think it would be easily possible but I worked out a way

EDIT: Ah - I see it's with a saved strip (not rpp project file) - I suspect with any old strips - you would need to set the display offset values and then resave the strip. Otherwise the strip will always be missing the display offset value as it isn't saved automatically - you would need to manually save the strip again once the values are set.

[RJHollins]

I'll check the 'Double Clk' editing ... forgot bout that new feature.


I just checked my saved STRIP file [not the one saved into an RPP - i've not tested that yet].

anyway ... I re-loaded and it was fine, just like I had saved. I'll post if this situation changes ... don't want to distract your attention unless something changes.

going to DBL-CLK check

[RJHollins]

ok ... have Reaper & LBX running in the background, as I've started testing the DBL-Clk edit function.

Dbl-Clk'ing a KNOB brings up an INPUT box.

I not exactly sure what values I should enter? I tried [from programming knobs myself] values from 0-1 ... with 0.5 the mid-point. I also tried values that would relate to actual values, like a volume knob ranging from -15 to +15.

In all cases, enter a number would send the knob pointing to either the MAX or MIN at the extreme position. I've not found any number that move the knob into any points in between ... including the 0-point.

This knob does point to a NEBULA plugin. I've tried both GAIN and FREQ knobs ... same extreme only result.

I need some clarification as to the numbers and ranges I should be entering [which I assume would work the same regardless of the parameter they control [as long as it is a numeric control] ... or there is another issue ???

thanks