|
|
|
10-25-2016, 01:43 PM
|
#441
|
Human being with feelings
Join Date: Jun 2015
Posts: 685
|
Quote:
Originally Posted by zappsunzorn
Forgive me for the OT but am I the only one that sees "LBX Stripper" and thinks they are on the wrong forum for about half a second
|
Yep. Pictures of semi-naked ladies probably should be added as default background graphics.
If the name will be changed, I propose "META-INTERFACE" (metaplugin is already taken by DDMF...)
|
|
|
10-25-2016, 01:50 PM
|
#442
|
Human being with feelings
Join Date: Apr 2014
Posts: 4,171
|
Quote:
Originally Posted by zappsunzorn
Forgive me for the OT but am I the only one that sees "LBX Stripper" and thinks they are on the wrong forum for about half a second, or gets self conscious when others might have a passing glance at the thread title.
|
haha - well - if it gets a few more views... (that probably end in disappointment!)
I thought it was an amusing title - but still absolutely relevant - maybe says more about my sense of humour...
EDIT: I originally called it LBX Channel Stripper - but thought that too boring and not snappy enough...
EDIT 2: I did question it though when searching for my original LBX Stripper video on youtube - the related videos were quite interesting.
|
|
|
10-25-2016, 01:52 PM
|
#443
|
Human being with feelings
Join Date: Jun 2015
Posts: 685
|
I think the name is great. It has multiple meanings: it can also be about "stripping" the interface down to basics, and only displaying the relevant parameters of plugins without the eye candy fluff.
|
|
|
10-25-2016, 01:57 PM
|
#444
|
Human being with feelings
Join Date: Apr 2014
Posts: 4,171
|
Quote:
Originally Posted by Sju
I think the name is great. It has multiple meanings: it can also be about "stripping" the interface down to basics, and only displaying the relevant parameters of plugins without the eye candy fluff.
|
good point. of course I thought of that too when coming up with the name (i didn't!!)
Anyway - those who have downloaded and are trying the latest version - is the reaEQ gain fixed now - or have you noticed any other funny (unfunny for me) things when changing parameters. I knocked up the denormalize solution pretty quick without really thinking - but seems to work well for me.
|
|
|
10-25-2016, 02:08 PM
|
#445
|
Human being with feelings
Join Date: Apr 2014
Posts: 4,171
|
Quote:
Originally Posted by Veto
Just FYI lb0, I can't seem to get any errors with a "hand-compound" chunk of these names above and reading it with your functions.
Maybe there's is only an issue on restoring the strip (reading the saved .strip file and joining it together)?
The .strip file itself would be interesting, i.e. was the correct name saved.
I'm not able to confirm this either . Both methods lead to the same .RPP chunk on my machine. Very strange.
Another FYI, this is what I found out what the most interesting line of the FX chunk looks like, depending on different situations:
The green part are linux shared objects so it's system dependent, but they should not be of interest anyway.
With SlickEQ and Sju's issue that would resolve to:
whose FX names all gets perfectly read on my system
Hope that helps a bit to get that tenacious critter.
|
Thanks very much for that Veto. I'm a little confused as to the problem Sju has been having - as for VST's I'm simply matching 'VST*:' up to the following ' (' I have all the SlickEQs on my studio computer - but not on my development laptop. Maybe I'll have to go and have a play down the end of the garden...
|
|
|
10-25-2016, 02:19 PM
|
#446
|
Human being with feelings
Join Date: Apr 2014
Posts: 4,171
|
Quote:
Originally Posted by Veto
Just FYI lb0, I can't seem to get any errors with a "hand-compound" chunk of these names above and reading it with your functions.
Maybe there's is only an issue on restoring the strip (reading the saved .strip file and joining it together)?
The .strip file itself would be interesting, i.e. was the correct name saved.
I'm not able to confirm this either . Both methods lead to the same .RPP chunk on my machine. Very strange.
Another FYI, this is what I found out what the most interesting line of the FX chunk looks like, depending on different situations:
The green part are linux shared objects so it's system dependent, but they should not be of interest anyway.
With SlickEQ and Sju's issue that would resolve to:
whose FX names all gets perfectly read on my system
Hope that helps a bit to get that tenacious critter.
|
I should say that the 'error' (in that the plugin fails to load) will occur on dragging the strip into a new track. The error is likely happening that the name I've grabbed is not recognised/usable by TrackFX_AddByName function.
|
|
|
10-25-2016, 02:20 PM
|
#447
|
Human being with feelings
Join Date: Apr 2010
Location: Turkey/Istanbul
Posts: 1,820
|
yes ReaEQ thingy is gone now!
also
i can't say how much i loved new learn function
now its very easy to define style for parameters knob/slider/button
...
just one click to one that already exist in the grid line
then move a parameter from vst done... learned parameter
will appear as last clicked form! magic!
..
testing parameters from all track goes so far so good!
|
|
|
10-25-2016, 02:23 PM
|
#448
|
Human being with feelings
Join Date: Apr 2014
Posts: 4,171
|
Quote:
Originally Posted by Sju
Yep just SlickEQ. I tried again in a fresh project, and renaming the plugin to "SlickEQ" in the FX Browser caused it not to be detected, when trying to load the strip to another track (I get the NOT AVAILABLE message on the knob).
Another thing that I noticed is that, after creating the test chain with renamed plugin, if I then clear the naming in the FX Browser, insert the plugin again on the same track and save the chain, when I try to drop it on the grid it doesn't create a knob at all. Maybe it corrupts the strip file somehow?
Anyways, everything works fine when I use the default plugin names.
|
Do you still have the .strip file? Could you send it to me - or post the [fxname] and [fxchunk] parts that are failing? Is the [fxname] bit missing? If so - then my parsing is failing to even pull a usable name, or it may not have got the whole thing or the right bit - would be good to see it...
EDIT: If you keep the strip file - it should still have the entire fx chunk in it for the failed plugin - so if I manage to improve the vst name detection - you will still be able to load it.
|
|
|
10-25-2016, 02:27 PM
|
#449
|
Human being with feelings
Join Date: Apr 2014
Posts: 4,171
|
Quote:
Originally Posted by Veto
No, better not
This issue is indeed very confusing.
Maybe Sju could check his saved .RPP if both renaming methods indeed lead to different .RPP's if he don't mind. Or upload the .strip file which doesn't work.
Unfortunately SlickEQ is not available for linux, so that I could test it in-depth.
God I hope I don't messed other stuff up with my string pattern fu
Ok, thanks for that info.
|
Honestly - my original attempts wouldn't have worked at all - so I appreciate all the help you've provided me.
The main thing I can suggest to anyone using my script - is for now - do not rename any plugins I haven't had any reports of problems in cases where there has been no renaming.
|
|
|
10-25-2016, 02:51 PM
|
#450
|
Human being with feelings
Join Date: Jun 2015
Posts: 685
|
Quote:
Originally Posted by Veto
This issue is indeed very confusing.
Maybe Sju could check his saved .RPP if both renaming methods indeed lead to different .RPP's if he don't mind. Or upload the .strip file which doesn't work.
|
Hmm yeah I actually didn't check the RPP, just the text field in the pop-up.
Quote:
Originally Posted by lb0
Do you still have the .strip file? Could you send it to me - or post the [fxname] and [fxchunk] parts that are failing? Is the [fxname] bit missing? If so - then my parsing is failing to even pull a usable name, or it may not have got the whole thing or the right bit - would be good to see it...
EDIT: If you keep the strip file - it should still have the entire fx chunk in it for the failed plugin - so if I manage to improve the vst name detection - you will still be able to load it.
|
Don't have the file I think, but it's a reproducible bug; I'll post it in a moment.
Meanwhile: closing a project tab while Stripper is active causes some of the preferences to reset, mainly locked window width/height.
|
|
|
10-25-2016, 02:58 PM
|
#451
|
Human being with feelings
Join Date: Apr 2014
Posts: 4,171
|
Quote:
Originally Posted by Sju
Hmm yeah I actually didn't check the RPP, just the text field in the pop-up.
Don't have the file I think, but it's a reproducible bug; I'll post it in a moment.
Meanwhile: closing a project tab while Stripper is active causes some of the preferences to reset, mainly locked window width/height.
|
Thanks for the report - I noticed something odd going on there but don't use it enough yet to work out what it was.
Think I'm saving the lock settings in the wrong place - global - whereas they probably should be project level.
EDIT:think I'll leave them global - but i know why they reset to zero and will fix in next update.
Last edited by lb0; 10-25-2016 at 03:06 PM.
|
|
|
10-25-2016, 03:00 PM
|
#452
|
Human being with feelings
Join Date: Jun 2015
Posts: 685
|
From the RPP:
Code:
NAME orig
<VST "VST: TDR VOS SlickEQ GE (Tokyo Dawn Labs)" "TDR VOS SlickEQ GE.dll" 0 "" 1415852337
NAME fxbro
<VST "VST: renamed" "TDR VOS SlickEQ GE.dll" 0 "" 1415852337
NAME mcp
<VST "VST: TDR VOS SlickEQ GE (Tokyo Dawn Labs)" "TDR VOS SlickEQ GE.dll" 0 renamed 1415852337
NAME both
<VST "VST: renamed" "TDR VOS SlickEQ GE.dll" 0 renamed 1415852337
From bugged .strip:
Code:
["fxname"]="VST: renamed",
["fxchunk"]="VST \"VST: renamed\" \"TDR VOS SlickEQ GE.dll\" 0 \"\" 1415852337\
Last edited by Sju; 10-25-2016 at 03:07 PM.
|
|
|
10-25-2016, 03:10 PM
|
#453
|
Human being with feelings
Join Date: Apr 2014
Posts: 4,171
|
Quote:
Originally Posted by Sju
From the RPP:
Code:
NAME orig
<VST "VST: TDR VOS SlickEQ GE (Tokyo Dawn Labs)" "TDR VOS SlickEQ GE.dll" 0 "" 1415852337
NAME fxbro
<VST "VST: renamed" "TDR VOS SlickEQ GE.dll" 0 "" 1415852337
NAME mcp
<VST "VST: TDR VOS SlickEQ GE (Tokyo Dawn Labs)" "TDR VOS SlickEQ GE.dll" 0 renamed 1415852337
NAME both
<VST "VST: renamed" "TDR VOS SlickEQ GE.dll" 0 renamed 1415852337
From bugged .strip:
Code:
["fxguid"]="15FFD825-93FD-41B7-ADA6-6D5A92AE01A6",
["fxchunk"]="VST \"VST: renamed\" \"TDR VOS SlickEQ GE.dll\" 0 \"\" 1415852337\
|
Thanks - really useful - but WTF!
Yeah - renaming via fxbro - will completely stuff up what I wanted in all situations.
renaming mcp should be ok
It seems I need to search for the string before the .dll - but I take it this won't work for Linux or Mac's ?? Grrrr...
Will really have to think this through...
In the meantime - if you have to rename - use the mcp (pretty sure that should work ok from what I'm seeing) - let me know if it doesn't work either...
|
|
|
10-25-2016, 03:13 PM
|
#454
|
Human being with feelings
Join Date: Jun 2015
Posts: 685
|
yep MCP renaming seems to work no probs so far. Glad the issue is clear now thanks again and gn for now
|
|
|
10-25-2016, 03:35 PM
|
#455
|
Human being with feelings
Join Date: Oct 2008
Location: Right Hear
Posts: 15,618
|
lb0 ... just got the newest
confirmed it fixes the Cockos EQ gain knobs being stuck when at -inf
but now I find something else strange:
to fully see it you will need to dl from the stash my recent LED's
so there are two parts to this issue:
I would normally use one of the LED pngs as a button [or INV BUTTON] for
bypass... and until this version of the script that worked as expected...
But now when I try to drag in the parameter for Bypass, I get nothing
...so that is part one
Part two is that now the 'preview' in the list of possible knobs displays the png in the 'off condition'... so I really see almost nothing since the off state is virtually black...
I don't know what the solution would be cuz it is only a 2 frame png file
I know awhile back you set the default value for displaying the knob choices at near 50% and for most knobs that IS a big help...
..any way to solve this for simple 2 frame button pngs???
BTW... back aways, I thought the file names knobs were not showing... it was my own error... I did not have the LBX window open enough to see the 'CONTROLS' label at the top right... silly me, sorry for my mistake
|
|
|
10-25-2016, 03:43 PM
|
#456
|
Human being with feelings
Join Date: Apr 2014
Posts: 4,171
|
Quote:
Originally Posted by hopi
lb0 ... just got the newest
confirmed it fixes the Cockos EQ gain knobs being stuck when at -inf
but now I find something else strange:
to fully see it you will need to dl from the stash my recent LED's
so there are two parts to this issue:
I would normally use one of the LED pngs as a button [or INV BUTTON] for
bypass... and until this version of the script that worked as expected...
But now when I try to drag in the parameter for Bypass, I get nothing
...so that is part one
Part two is that now the 'preview' in the list of possible knobs displays the png in the 'off condition'... so I really see almost nothing since the off state is virtually black...
I don't know what the solution would be cuz it is only a 2 frame png file
I know awhile back you set the default value for displaying the knob choices at near 50% and for most knobs that IS a big help...
..any way to solve this for simple 2 frame button pngs???
BTW... back aways, I thought the file names knobs were not showing... it was my own error... I did not have the LBX window open enough to see the 'CONTROLS' label at the top right... silly me, sorry for my mistake
|
Ok - will look into your LED as buttons. I could of course display last frame which I assume is your on position?
No worries about the mistake - It can get a bit cramped - and when editing - you do need the window quite large!
|
|
|
10-25-2016, 03:51 PM
|
#457
|
Human being with feelings
Join Date: Apr 2014
Posts: 4,171
|
Quote:
Originally Posted by hopi
lb0 ... just got the newest
confirmed it fixes the Cockos EQ gain knobs being stuck when at -inf
but now I find something else strange:
to fully see it you will need to dl from the stash my recent LED's
so there are two parts to this issue:
I would normally use one of the LED pngs as a button [or INV BUTTON] for
bypass... and until this version of the script that worked as expected...
But now when I try to drag in the parameter for Bypass, I get nothing
...so that is part one
Part two is that now the 'preview' in the list of possible knobs displays the png in the 'off condition'... so I really see almost nothing since the off state is virtually black...
I don't know what the solution would be cuz it is only a 2 frame png file
I know awhile back you set the default value for displaying the knob choices at near 50% and for most knobs that IS a big help...
..any way to solve this for simple 2 frame button pngs???
BTW... back aways, I thought the file names knobs were not showing... it was my own error... I did not have the LBX window open enough to see the 'CONTROLS' label at the top right... silly me, sorry for my mistake
|
Ok - change your LED .knb files to have frames=2 not frames=100 !! That should sort both your issues...
Lovely LEDs by the way - will be using those!!
|
|
|
10-25-2016, 03:51 PM
|
#458
|
Human being with feelings
Join Date: Oct 2008
Location: Right Hear
Posts: 15,618
|
I have to take all that back... reloaded and now it's working OK
no idea what the problem was before...
we can talk about the preview of the LED's later...
|
|
|
10-25-2016, 03:52 PM
|
#459
|
Human being with feelings
Join Date: Apr 2014
Posts: 4,171
|
Quote:
Originally Posted by Veto
What I'm wondering now is, if Reaper allows different names on FX-Browser and MCP, could that happen with JS or other FX's too?
Because then the JS part of the code would fail too
|
I suspect so. I'll try to think of a more robust parsing algo. I think it's easier enough not to change the name in the FX Browser... Or to change it back when required.
I will look into it further though - because I dislike having caveats when none should be necessary!!
|
|
|
10-25-2016, 03:54 PM
|
#460
|
Human being with feelings
Join Date: Apr 2014
Posts: 4,171
|
Quote:
Originally Posted by hopi
I have to take all that back... reloaded and now it's working OK
no idea what the problem was before...
we can talk about the preview of the LED's later...
|
Your updated .knb files had frames=100 not frames=2 - as per my last message
You may need to fix this in the stash...
|
|
|
10-25-2016, 03:54 PM
|
#461
|
Human being with feelings
Join Date: Oct 2008
Location: Right Hear
Posts: 15,618
|
No wait... I posted a link for the stash for colored LED's
red, green, blue, yellow, orange... and afaik the .knb files for them all do say 2 frames... did I miss that on one of them????
should be 30 px by 30 px by 2 frames for them all
|
|
|
10-25-2016, 03:57 PM
|
#462
|
Petit manitou
Join Date: Feb 2009
Location: Gémenos France
Posts: 7,347
|
Strange Click
I encounter a small problem; When I click on a knob, the value jumps forward.
C'est en "knob/slider... or fader
|
|
|
10-25-2016, 03:58 PM
|
#463
|
Human being with feelings
Join Date: Apr 2014
Posts: 4,171
|
Quote:
Originally Posted by timbralzoom
yes ReaEQ thingy is gone now!
also
i can't say how much i loved new learn function
now its very easy to define style for parameters knob/slider/button
...
just one click to one that already exist in the grid line
then move a parameter from vst done... learned parameter
will appear as last clicked form! magic!
..
testing parameters from all track goes so far so good!
|
Excellent - let me know how it all goes - hope to see a new video soon They are an awesome break from coding heh heh!
Have you been able to test the single state cycle buttons yet - you mentioned an issue yesterday - which required you to rebuild your test cycle buttons.
I can confirm it all works fine for me - so interested if it's now working for you?
Thanks,
|
|
|
10-25-2016, 03:59 PM
|
#464
|
Human being with feelings
Join Date: Apr 2014
Posts: 4,171
|
Quote:
Originally Posted by Vincent Sermonne
I encounter a small problem; When I click on a knob, the value jumps forward.
C'est en "knob/slider... or fader
|
Is this the very latest version (about an hour ago?) - think I fixed it... what plugin are you using? (not got video preview on screen at mo when writing this reply - apologies if obvious)
EDIT: If this is the very latest version - I will update my normalize/denormalize functions (some suggestions were offered yesterday)
|
|
|
10-25-2016, 04:27 PM
|
#465
|
Human being with feelings
Join Date: Mar 2007
Location: I'm in a barn
Posts: 4,467
|
Quote:
Originally Posted by lb0
Hmmm... my normalize, denormalize method working with threshold on ReaGate only gives you up to +6 on the slider - whereas the slider goes up to +12
I can only think this is a problem with the reported max value from the plugin - as i'm using the plugin's own min and max values to normalize!!
I think there might be a few issues with some of the ReaPlugs (good as they are). Probably can not do anything about these if the bugs are external...
Of course - I could be doing something wrong in my denormalize function - but it works perfectly for other parameters.
|
Oh man - good luck.
The threshold for ReaComp is actually tied to the users fader settings. (if the default has been changed) including the min and max values, and the shape of the faders is factored in as well. Some of that might be playing havoc on your normalization. This changes where the -inf point happens and yeah... good luck
you might need to break out that "Cadillac" variable_scale conversion function I posted to really nail it. You can factor in the scale of the parameter (like you might actually need to read the users fader settings from the reaper.ini !!!!! )
I may have this wrong, but with that function you can do...
Code:
function variable_scale(var,minval,maxval,tgtmin,tgtmax)
(tgtmin*(1-((var-(minval))/(maxval-minval))) + tgtmax*((var-(minval))/(maxval-minval));
);
//call it like...
var=variable_scale(var^scale,minval^scale,maxval^scale,tgtmin,tgtmax);
I hope that's right... might have it backwards or something. And it might not be necessary even if it is right.
I barely remember how that function actually works ha ha - I think I ended up brute forcing my way into it
actually cause I was trying to make a slider in a JS that would map properly to ReaComps threshold!
Last edited by James HE; 10-25-2016 at 04:33 PM.
|
|
|
10-25-2016, 04:32 PM
|
#466
|
Human being with feelings
Join Date: Apr 2014
Posts: 4,171
|
Quote:
Originally Posted by James HE
Oh man - good luck.
The threshold for ReaComp is actually tied to the users fader settings. (if the default has been changed) including the min and max values, and the shape of the faders is factored in as well. Some of that might be playing havoc on your normalization. This changes where the -inf point happens and yeah... good luck
you might need to break out that "Cadillac" variable_scale conversion function I posted to really nail it. You can factor in the scale of the parameter (like you might actually need to read it from the reaper.ini !!!!! )
I may have this wrong, but with that function you can do...
Code:
function variable_scale(var,minval,maxval,tgtmin,tgtmax)
(tgtmin*(1-((var-(minval))/(maxval-minval))) + tgtmax*((var-(minval))/(maxval-minval));
);
//call it like...
variable_scale(var^scale,minval^scale,maxval^scale,tgtmin,tgtmax);
I hope that's right... might have it backwards or something. And it might not be necessary even if it is right.
I barely remember how that function actually works ha ha - I think I ended up brute forcing my way into it
actually cause I was trying to make a slider in a JS that would map properly to ReaComps threshold!
|
Thanks James,
It's too late here for me to make head nor tails of that today - will pick up again tom. evening!!
EDIT: However - for now - I'm tempted to leave it (as long as I get no jumpy knobs - like Vincent demonstrated above - I'm hopeful he was running an earlier version before I switched to denormalizing my stored normalized values and using SetParam instead of SetParamNormalized). With my setup - I still get -inf to 6db on all the Rea* thresholds I've tested - which is probably enough for most people. Of course there are alternative plugins also - and I bet it's mainly the Rea* ones that get truly tied into Reaper. I should have full scale thresholds on all my other compressors - MJUC, Disto, Manic etc.
Further EDIT:
I see min and max for these parameters is 0 to 2 - whereas if I hardcode max to 4 - I get the full range for the control. I guess I could add min and max overrides on a control by control basis to deal with these cases - for a little extra CPU overhead. That would be quite easy to do.
Last edited by lb0; 10-25-2016 at 05:03 PM.
|
|
|
10-25-2016, 05:14 PM
|
#467
|
Human being with feelings
Join Date: Dec 2011
Posts: 2,161
|
The latest LUA version seems to be working well.
I just had a chance to test Hopi's new LED buttons. Setting to BUTTON/INV
allowed to set the proper state, and they work ... and looking good Thx Hopi !!
I do have an issue that I'm trying to solve.
I have a parameter on a plugin, it is a GAIN control [- 0 +]. Using either a Knob or Fader, set to the MID position, gives a -6.00 readout.
If the values are being derived directly from the plugin, maybe we'll need a 'display value OFFSET' to correct this ??? For those interested, this is NEBULA's main OUTPUT GAIN control. Important for setting output to the next plugin of the FXChain, maintaining UNITY.
|
|
|
10-25-2016, 08:18 PM
|
#468
|
Human being with feelings
Join Date: Oct 2008
Location: Right Hear
Posts: 15,618
|
RJH... plz see last two emails just sent to you ...might help with Neb
glad you like the LED's... tried many variation but think I'll stick with these for now.... I could generate other colors fairly easily if they are really needed.
Yes, it is funny button inv works right for some plugins and yet not for others... some seem to run their on\off states differently. Luckily there are only two choices... hahaha
|
|
|
10-25-2016, 08:52 PM
|
#469
|
Human being with feelings
Join Date: Dec 2011
Posts: 2,161
|
HOPI ... the email you sent is on the VU meters. Very interesting.
But the issue I'm having is with NEBULA's main OUTPUT slider [or knob].
When I drag the parameter in, I can definitely control its movement, but the readout in LBX does not correlate. Zero [null-mid]on the NEB OUTPUT will display -6 in LBX.
[in other news ... are you saying we can possible get Neb's VU to display in LBX ??? that would be surprising].
|
|
|
10-25-2016, 09:13 PM
|
#470
|
Human being with feelings
Join Date: Oct 2008
Location: Right Hear
Posts: 15,618
|
Ummm yes I do know the mail listed the internal Neb values for use in one of the VU Meters I made for one of the Neb Skins...
but the point is those ARE the values that Neb is putting out on the main gain that you are looking into and talking about...
Those values run from about -192 to 0.0 they are the same as in what I sent to you. In what I sent, there are 120 steps to almost the whole range of those gain values...
So what you see in LBX as the values, do match that set of values
If -6.0 appears as the 'mid' point, you can see the graph line of those values is not a line but a curve... how to say it better?
so a mid point in what LBX displays may well be -06.0.. because that is what Nebula is telling it. That number comes from Neb and is only being shown in LBX.
I can tell you that about -08.0 in what Neb values are is about 0 on the Meter... in otherwords, -08.0 in Neb's gain values is where OVERS will begin.... and though the Meter is made to show - and 0 and + above 0 that is not what Neb is sending out. Ok.. so in Neb's gain values, -05.0 pegs the meter needle all the way to top [right]
Is that helpful at all?
Last edited by hopi; 10-25-2016 at 09:24 PM.
|
|
|
10-25-2016, 09:26 PM
|
#471
|
Human being with feelings
Join Date: Oct 2008
Location: Right Hear
Posts: 15,618
|
RJH... just a PS if I did not say it in the email....
in that list of png needles I sent... png#84 is the needle that points at the 0 between the - and + values on the VU scale....
|
|
|
10-25-2016, 10:06 PM
|
#472
|
Human being with feelings
Join Date: Dec 2011
Posts: 2,161
|
Hopi ... ok ... I wouldn't have expected that type of connection to the main OUTPUT fader being tied to the meter display.
I always look at the main GUI window to see numeric values of INPUT/OUTPUT. and those would be the values I hoped to see in LBX. Well ... Nebula can be a strange beast for sure.
This being the case, then ... this complicates things. Well, at least the LBX slider in controlling the main slider, so that I can adjust the plugs OUTPUT. I guess I have to live with the -6 offset [call that the new ZERO], so if I need to lower 2dB, I fader it to -8.
|
|
|
10-25-2016, 10:22 PM
|
#473
|
Human being with feelings
Join Date: Oct 2008
Location: Right Hear
Posts: 15,618
|
yes... afaik that -08.0 should be zero or darn close
I can try an experiment in knobman and we'll see how it matches up
|
|
|
10-25-2016, 10:32 PM
|
#474
|
Human being with feelings
Join Date: Dec 2011
Posts: 2,161
|
in LBX ... the -6 display does show the NEB fader [and the Neb GUI value] as ZERO.
|
|
|
10-25-2016, 10:38 PM
|
#475
|
Human being with feelings
Join Date: Oct 2008
Location: Right Hear
Posts: 15,618
|
PS have to revise the experiment.. I forgot one thing
you can see it in LBX readout... try this
the smallest move you make from the Neb slider [do it in the Neb GUI but read it in LBX] will move the readout from -192 to about -50 [if you are very very delicate] about 46 is more likely
EDIT... hahaha was gonna try to make a list of numbers in knobman but total failure... again due to way it is scaled in Neb...
i suppose ...maybe it could be done frame at a time but not tonight...
Last edited by hopi; 10-25-2016 at 10:48 PM.
|
|
|
10-25-2016, 10:39 PM
|
#476
|
Human being with feelings
Join Date: Apr 2010
Location: Turkey/Istanbul
Posts: 1,820
|
Quote:
Originally Posted by lb0
Excellent - let me know how it all goes - hope to see a new video soon They are an awesome break from coding heh heh!
Have you been able to test the single state cycle buttons yet - you mentioned an issue yesterday - which required you to rebuild your test cycle buttons.
I can confirm it all works fine for me - so interested if it's now working for you?
Thanks,
|
OK- then....
grab a big cup of tea, find a comfortable chair and be patience!
https://www.youtube.com/watch?v=Dsdq...ature=youtu.be
...
i can't express how comfortable having all this functions in the Reaper!
you made some kind a "build your machines as you need!" possible..
imho. without dealing with dozens of interfaces & hundreds of parameters
(well, maybe dealing once) focusing to the sound is fantastic!
again again Thank you so much!
i hope you will have time and energy to add track parameters
and snapshot functions in some point,
otherwise all this instant magical sounds
will continue to lost forever...
serious mode on:
cycle buttons now works beautifully,
learn from all tracks function works great as in the video!
edit..
just in case
i couldn't follow the latest meter discussions,
still using my old one in the video.
|
|
|
10-25-2016, 10:52 PM
|
#477
|
Human being with feelings
Join Date: Jan 2008
Location: Vancouver, BC
Posts: 3,793
|
Quote:
Originally Posted by lb0
Thanks! I will need to ponder this - as my script obviously works across all tracks - that could be a lot of tracks to keep track of and monitor. Depends on the overhead I guess. I am assuming I can get access to the levels of each track of course (not investigated yet). I guess it could be an option - my main worry would be any latency involved in reinstating the bypass settings when audio comes back in - could I ensure it be quick enough? Can I get a lookahead value for the track audio?? dunno.
|
Thanks for pondering.
I assume there's some technical considerations which is why Cockos doesn't allow us to automatic the track FX bypass.
For what it's worth, I'd happily trade a bunch of added track latency for this feature, as I would generally enable it on tracks I'm not currently tweaking, or tracks with only a small amount of audio, but high CPU usage (not a big fan of item FX for this)...
__________________
FRs: v5 Media Explorer Requests, Global Quantization, Session View
Win10 Pro 64-bit, Reaper 6(x64), AMD 3950x, Aorus X570 Master, 64GB DDR4 3600, PowerColor Red Devil 5700XT, EVO 970 2TB, 10TB HD, Define R6
|
|
|
10-25-2016, 10:55 PM
|
#478
|
Human being with feelings
Join Date: Dec 2011
Posts: 2,161
|
Quote:
Originally Posted by hopi
PS have to revise the experiment.. I forgot one thing
you can see it in LBX readout... try this
the smallest move you make from the Neb slider [do it in the Neb GUI but read it in LBX] will move the readout from -192 to about -50 [if you are very very delicate] about 46 is more likely
EDIT... hahaha was gonna try to make a list of numbers in knobman but total failure... again due to way it is scaled in Neb...
i suppose ...maybe it could be done frame at a time but not tonight...
|
Hopi ... I don't have that happening at all.
Whether I move the LBX fader, or the Nebula fader ... they both are tracking together. No strange jumps.
The only 'problem' is the value displayed in the LBX display.
Check: are you sure that you are linking to the 'GAIN OUT' in the parameter list in LBX ?
|
|
|
10-25-2016, 10:57 PM
|
#479
|
Human being with feelings
Join Date: Oct 2008
Location: Right Hear
Posts: 15,618
|
shit... I have to stand corrected... LBX is NOT displaying quite the same numbers as the NEB GUI readout
so maybe something can be done with LBX to match it up...
I was fooled cuz they do both start at -192.6x
but as we increase the Neb upwards they don't match up
0.0000 in Neb GUI reads -6.021 in LBX display
Still we might get a knob to show the Neb values [or very close] but we'd have to know how many steps or really frames it would take and then what number should go in each of those frames...
OUCH!
|
|
|
10-25-2016, 11:03 PM
|
#480
|
Human being with feelings
Join Date: Dec 2011
Posts: 2,161
|
Hopi ... something else to check.
When I set up this fader, I think I adjusted the DEFAULT VAL [in LBX] to the 0 [mid point] of NEBULA.
If you CNTRL-CLK the LBX fader [or knob], the NEB value does go to 0.000 [LBX shows -6.xx i have rounded to 1 decimal place]
However, if you move the LBX fader to -6 ... then NEB does display 0.062 I can live with that.
---- edit ----
well NOW when I move the LBX slider to -6 [the mid point], Nebula is now show 0.000 .... but, sometimes it doesn't. it'll show 0.062
I don't know how many steps are in the LBX slider.
The key point ... the GAIN OUT should start with NEBULA being at 0.000 [default].
Last edited by RJHollins; 10-25-2016 at 11:08 PM.
|
|
|
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 11:58 PM.
|