LBX Stripper - create custom channel strips

[lb0]

Originally Posted by PitchSlap

The attachment worked. Thanks!

Glad you got it working - but did you try the raw version? - that should definitely work ok (or at least - if that doesn't work - then I've made a serious error!).

[Sexan]

still nothing (but little different,now many buttons are corrupted,before was just one)

Script is loading some elements from "Graphics" folder as you can see on MCP strip some buttons are backgounds which I use on other scripts
I really do not know whats going on and why. Will try on other computer

[lb0]

Originally Posted by Sexan

still nothing (but little different,now many buttons are corrupted,before was just one)

Script is loading some elements from "Graphics" folder as you can see on MCP strip some buttons are backgounds which I use on other scripts
I really do not know whats going on and why. Will try on other computer

ah nuts! will keep thinking

on a new project can you describe exactly step by step - what you do to end up with this... thanks

[Sexan]

Btw is the script supposed to save strips with the project? Tried to save one project with the strips but when opening the project there are no strips

ok I will make licecap now

[lb0]

Originally Posted by Sexan

Btw is the script supposed to save strips with the project? Tried to save one project with the strips but when opening the project there are no strips

ok I will make licecap now

ok - yeah- big problems so advise no one to stick to the update for the moment. just working out what's gone wrong...

EDIT - seems master track only isn't saving with project :/

EDIT - is saving - not recalling...

[Sexan]

This is new project (Reaper fresh open)

[lb0]

Originally Posted by lb0

ok - yeah- big problems so advise no one to stick to the update for the moment. just working out what's gone wrong...

EDIT - seems master track only isn't saving with project :/

EDIT - is saving - not recalling...

Well - found something interesting that I've not noticed before...

The Master track GUID is not recalled each time you load a project. (at least in v5.27). In fact - it's not even stored in the rpp file.

I've been wondering why the master controls will not recall at all - and it seems the master track guid changes each time you open reaper - and then stays fixed - no matter what project I subsequently load.

Now I dare say this may not have mattered in the past - but I've obviously added improved checking - which is affected by this. :/

Will look into seeing what I can do to fix...

EDIT: getting there with a fix for this - got them recalling ok - now to fix the control links as these get dropped...

[lb0]

Ok - new update... lets forget the last one as it all went horribly wrong

Anyway - master channel controls should now all recall and respond correctly !!
(apart from the mute and solo controls which will mute and solo - but not unmute and unsolo from the strip - i will look into this! - only happens on master)

Sexan - Sorry not had a chance tonight to look further into the issue you're having. Has anyone else had a similar issue to Sexan with saved strips recalling initially with some incorrect graphics. I have his files here - and have tried to repeat the problem - but no luck thus far...

I would recommend anyone who downloaded the update from earlier this evening to update to this new version!!

[timbralzoom]

hmm,

..Roaming\REAPER\Scripts\LBX\LBX Stripper.lua:7359: attempt to index a number value (local 'track')

i just get this message..
was trying to collect Track Parameters, Mute & Solo from tracks via using track list...
dragging from selected track was ok but next track gives this error instantly when i drag one of them..

edit.
seems also other parameters have this

[RJHollins]

Originally Posted by Sexan

Can the same behaviour be achieved with multiple buttons (ratio)? Assigning single value to a each button ? I've tried to play with that but with no success, when clicking on 1 all other buttons activate

Something like 'Radio' buttons ??

[lb0]

Originally Posted by timbralzoom

hmm,

..Roaming\REAPER\Scripts\LBX\LBX Stripper.lua:7359: attempt to index a number value (local 'track')

i just get this message..
was trying to collect Track Parameters, Mute & Solo from tracks via using track list...
dragging from selected track was ok but next track gives this error instantly when i drag one of them..

edit.
seems also other parameters have this

ok thanks - will look into. All because I found a much quicker way to check things - didn't realise it would break stuff!!

Should be fixed now. Sorry 'bout that!

[Sexan]

Tested everything on main machine (deleted reaper,fresh install 5.29, 5.28, 5.27 both x64 and x32 and normal and portable installation and still same issues. Will now test on my laptop, but strips are still not saving with the project,upon opening the saved project the script window is empty (there are no strips I've added to tracks). I'm on W10 x64 don't know whats wrong but something is definitely wrong on my end because non of the users experience the problems I have.

[lb0]

Originally Posted by RJHollins

Something like 'Radio' buttons ??

Yes - exactly. I'll look into adding something like this.

[lb0]

Originally Posted by Sexan

Tested everything on main machine (deleted reaper,fresh install 5.29, 5.28, 5.27 both x64 and x32 and normal and portable installation and still same issues. Will now test on my laptop, but strips are still not saving with the project,upon opening the saved project the script window is empty (there are no strips I've added to tracks). I'm on W10 x64 don't know whats wrong but something is definitely wrong on my end because non of the users experience the problems I have.

hmmm - really odd. can you once again post me your rpp file (that isn't recalling). I'd like to see if you have any lbx data in there.

If you haven't got one - can you drag in some controls/strips onto both master and normal tracks. Hit the SAVE button on LBX (top bar) - then save .rpp file and send to me.

Thanks,
Leon.

[lb0]

Originally Posted by Sexan

Tested everything on main machine (deleted reaper,fresh install 5.29, 5.28, 5.27 both x64 and x32 and normal and portable installation and still same issues. Will now test on my laptop, but strips are still not saving with the project,upon opening the saved project the script window is empty (there are no strips I've added to tracks). I'm on W10 x64 don't know whats wrong but something is definitely wrong on my end because non of the users experience the problems I have.

I am assuming you're using the latest update and not the broken one from last evening... that one would not recall anything from the master track - which should be fixed now.

[Sexan]

Yes I'm using the latest update.

Well little progress! on laptop its saving with project and when recalling the project again strips are there yey! and when opening saved project the graphics are not corrupted on first load double yey! (this still happens on blank project).
Would you consider implementing saving on script close, reaper.atexit ? It will eliminate the need for always clicking on save button

Edit: It seems if there is any saved project with the script there is no corrupted graphics (regardless which strip was loaded) on first load, but on every blank non saved project it happens

Edit2 : Well the problem arises when the track which has strip is deleted then graphic corruption kicks in (even in saved projects). If the track which has some strip data is there you can add whatever you want and everything is ok

Edit3: Saving works on main machine also (my bad)

Where can I insert DBG string to see whats happening when strip is loaded ?

[lb0]

Originally Posted by Sexan

Yes I'm using the latest update.

Well little progress! on laptop its saving with project and when recalling the project again strips are there yey! and when opening saved project the graphics are not corrupted on first load double yey! (this still happens on blank project).
Would you consider implementing saving on script close, reaper.atexit ? It will eliminate the need for always clicking on save button

Edit: It seems if there is any saved project with the script there is no corrupted graphics (regardless which strip was loaded) on first load, but on every blank non saved project it happens

Edit2 : Well the problem arises when the track which has strip is deleted then graphic corruption kicks in (even in saved projects). If the track which has some strip data is there you can add whatever you want and everything is ok

Edit3: Saving works on main machine also (my bad)

Where can I insert DBG string to see whats happening when strip is loaded ?

Ah - I think I may know what's happening here. I tried to make some performance improvements so it only saves the strips which have been edited when you exit edit mode (which is when it saves the data).

There's a reasonable chance that if you have added tracks with the stripper open - it will miss saving some of the data - which means it may not recall correctly - will look into. Not sure though - as I thought I had this covered.

However - hitting the SAVE button or **closing the script window (atexit)** - it should definitely save all the data. Are you saving the project before closing the script window? Thing is - when you close reaper - it prompts and saves the project *before* the script can run its atexit code - so it won't save any data in this case. Not found a decent workaround for this yet.

I'll look into to see if there's a problem here...

In the meantime - either close the script window or hit SAVE button - before closing reaper.

[Sexan]

Yeah I've save project before exiting (it works now,did not before...I will set my computer on fire soon)

[lb0]

Originally Posted by Sexan

Yes I'm using the latest update.

Well little progress! on laptop its saving with project and when recalling the project again strips are there yey! and when opening saved project the graphics are not corrupted on first load double yey! (this still happens on blank project).
Would you consider implementing saving on script close, reaper.atexit ? It will eliminate the need for always clicking on save button

Edit: It seems if there is any saved project with the script there is no corrupted graphics (regardless which strip was loaded) on first load, but on every blank non saved project it happens

Edit2 : Well the problem arises when the track which has strip is deleted then graphic corruption kicks in (even in saved projects). If the track which has some strip data is there you can add whatever you want and everything is ok

Edit3: Saving works on main machine also (my bad)

Where can I insert DBG string to see whats happening when strip is loaded ?

Ok - new update.

It now saves the strip count when saving single strips when exiting edit mode.

This would have caused strips not being loaded properly if you exited edit mode and then saved the project.

So the main thing to remember now is you must always exit edit mode - or close the script window/hit save button to save before saving the project.

Would you mind doing exactly as before - and seeing what happens...

Let me also know what's happening with the gfx again.

Thanks,
L.

[timbralzoom]

ok... here is a little bit nerdy one
introducing the Reaper Multichannel Native Gate Fx Sequencer
well..just two fx for testing purpose at this moment..
also 8 Channel router/mixer(s) needs replacement because of loading time..
still working on it, ill share when it finish.

anyway i hope you like it.

https://www.youtube.com/watch?v=8kyNkqqbOXQ

[lb0]

Originally Posted by timbralzoom

ok... here is a little bit nerdy one
introducing the Reaper Multichannel Native Gate Fx Sequencer
well..just two fx for testing purpose at this moment..
also 8 Channel router/mixer(s) needs replacement because of loading time..
still working on it, ill share when it finish.

anyway i hope you like it.

https://www.youtube.com/watch?v=8kyNkqqbOXQ

wow - my mind is well and truly boggled!!

That's impressive

[timbralzoom]

Originally Posted by lb0

wow - my mind is well and truly boggled!!

That's impressive

Thank you, thanks to your hard work!
i believe it will be very useful one at the end,
cost a whole night and 6 cup of tea ...
now have to go for a demo voice recording session...
pillows calling badly but ..money first!

[lb0]

Originally Posted by timbralzoom

Thank you, thanks to your hard work!
i believe it will be very useful one at the end,
cost a whole night and 6 cup of tea ...
now have to go for a demo voice recording session...
pillows calling badly but ..money first!

Good luck with today then... hope the caffeine keeps you going long enough before you crash!! !

[Vincent Sermonne]

...cent\AppData\Roaming\REAPER\Scripts\LBX\LBX Stripper.lua:7377: attempt to index a number value (local 'track')

with the last one when I switch to another track

[lb0]

Originally Posted by Vincent Sermonne

...cent\AppData\Roaming\REAPER\Scripts\LBX\LBX Stripper.lua:7377: attempt to index a number value (local 'track')

with the last one when I switch to another track

Sorry - fixed

Very odd - as I had already fixed that error this morning. not sure how it got reverted...

[Vincent Sermonne]

Originally Posted by lb0

Sorry - fixed

Very odd - as I had already fixed that error this morning. not sure how it got reverted...

thank's ! super fast

[lb0]

Originally Posted by Sexan

Yeah I've save project before exiting (it works now,did not before...I will set my computer on fire soon)

Ok - but if you save the reaper project before my script has saved data to the project - it won't recall correctly...

Anyway - do you feel it's working ok now ?

Another annoying thing I've noticed particularly with your MCP panels. Where you use an action button (last touched track - routing/fx etc) - if you change track from within my script - using the track list - it will not bring up the correct track number. This is because I have not worked out a way to set the last touched track from within my script. So it works fine if you use the follow selected track option - and only change track by clicking in the mixer (which I'm guessing you're happy with - if using as an inspector).

But - if you change track within the script - it opens the routing/fx for the last track selected from within the MCP or TCP... :/

If I work out a way to touch the track - then I'll fix this - but so far no luck.


EDIT - are you still experiencing graphic glitches?

[lb0]

Originally Posted by Sexan

Yes I'm using the latest update.

Well little progress! on laptop its saving with project and when recalling the project again strips are there yey! and when opening saved project the graphics are not corrupted on first load double yey! (this still happens on blank project).
Would you consider implementing saving on script close, reaper.atexit ? It will eliminate the need for always clicking on save button

Edit: It seems if there is any saved project with the script there is no corrupted graphics (regardless which strip was loaded) on first load, but on every blank non saved project it happens

Edit2 : Well the problem arises when the track which has strip is deleted then graphic corruption kicks in (even in saved projects). If the track which has some strip data is there you can add whatever you want and everything is ok

Edit3: Saving works on main machine also (my bad)

Where can I insert DBG string to see whats happening when strip is loaded ?

To answer your final Q - the function LoadData() is where all data is loaded when script is opened.

I'll try deleting some tracks with strips on to see if I can repeat your gfx glitches.

[lb0]

Originally Posted by Sexan

Yeah I've save project before exiting (it works now,did not before...I will set my computer on fire soon)

Hey Sexan,

found another bug with the strip import - when generating the strip preview - I was indexing the ctl_files table from 1 - when it actually starts at 0 - so if for some reason your computer was enumerating the files in a different order to mine - at least one of the controls would load/display incorrectly (if enumerated at position 0) - until you restarted the strip which used different code (in LoadData ) which was indexing from 0.

Please can you see if the new update fixes your problem?

[Vincent Sermonne]

On the forum I saw that a script allows a peak / RMS meter without having to use a js, it uses the meter of the track. Is this possible? The JS problem is that it gives what gets into the track and not what comes out after the fader

[lb0]

Originally Posted by Vincent Sermonne

On the forum I saw that a script allows a peak / RMS meter without having to use a js, it uses the meter of the track. Is this possible? The JS problem is that it gives what gets into the track and not what comes out after the fader

The problem I have with this is that it internalizes the complex (ish) maths involved into my script runloop - for every track. This will likely impair the efficiency of my code somewhat - and may make busy strips laggy.

I could allow only currently selected track to be processed - but this would not be so useful for some strips where you want to see multiple track levels at once.

I did see and briefly analyse the code for an example that was posted a few pages back... but the code looked like several hundred lines compressed into 3 lines (ie. layed out horizontally) - so I gave up trying to understand it!! Nobody writes code like this - so I can't understand why they formatted it this way. Other than to suggest - look what I can fit into 3 lines!!

Anyway - I'd be concerned about the extra cpu overhead this would cause my script - having it run externally in a JS moves that processing away from my script (into a faster language JSFX) - and potentially onto another CPU core (i don't really know for sure).

If I could get some human readable code - and just the bits that are required (the posted example had lots of graphical bells and whistles that were quite simply a bit bonkers for its requirements IMO!!) - then I would consider adding it into a sidebar (or maybe a control on the grid) for the currently selected track...

I understand your issue with the JSFX version being pre-fader - but you can overcome this by placing all of your tracks in its own parent folder and put the JSFX meter in the parent folder - thus making it post-fader for the child folder.

[Vincent Sermonne]

Originally Posted by lb0

I understand your issue with the JSFX version being pre-fader - but you can overcome this by placing all of your tracks in its own parent folder and put the JSFX meter in the parent folder - thus making it post-fader for the child folder.

Yes I know we had already spoken, but, in my project, this make double the number of the tracks. 26 tracks only for a virtual drum, it's too much for the workflow. Well, It will be without meter for me. In reality it's more for the esthetic thing. Thank you for your answer Leon !
.

[lb0]

Originally Posted by Vincent Sermonne

Yes I know we had already spoken, but, in my project, this make double the number of the tracks. 26 tracks only for a virtual drum, it's too much for the workflow. Well, It will be without meter for me. In reality it's more for the esthetic thing. Thank you for your answer Leon !
.

Well - if the maths is actually pretty simple underneath the bloated extras - I could consider adding it somehow... difficult to really tell how complex the maths is with the way the code is formatted.

I'll consider trying to decipher it...

[Arthur McArthur]

Got a few questions:

Is there a way to make a knob that moves in increments of 1 unless shift or control is held? Trying to make a functional pitch shift knob for ReaSamplomatic

Is it possible to make offline fx look like they're actually offline? For now it lights all the bypass buttons up. Would be cool to have them greyed out.

Could you make a version of the snapshot change button that doesn't open the snapshots window? I'd like to have a small button/ buttons that just switches the "presets" without opening the window.

[Sexan]

IT IS FIXED!!!!!!!!!!!!!!!!!!!! THANK YOU!!!!!!!!!!!!!!!!!!
Regarding that meter script (that I've posted) I will make your job easier I will format it properly and post somewhere

[lb0]

Originally Posted by Arthur McArthur

Got a few questions:

Is there a way to make a knob that moves in increments of 1 unless shift or control is held? Trying to make a functional pitch shift knob for ReaSamplomatic

Is it possible to make offline fx look like they're actually offline? For now it lights all the bypass buttons up. Would be cool to have them greyed out.

Could you make a version of the snapshot change button that doesn't open the snapshots window? I'd like to have a small button/ buttons that just switches the "presets" without opening the window.

1. Not easily - the values I have to work with are all between 0 and 1 (normalised). Therefore - an increment of 1 might be say 0.00001122342 (ie. a tiny fraction of 1). There's no way for a particular parameter of me knowing exactly what value would increment that parameter by 1 (or whatever you require).

You could manually set up a cycle control (draggable) - but would be quite difficult I reckon to get each position set to exactly the right amount...

Will have to think on this.

2. If the bypass button is on the grid - and you click it - the fx controls should go semi-transparent. Is this what you mean? Or is it simply the button state you want to be lit for on - and grey for off? In which case you can switch the polarity of the button controls by using the 'button inv' instead.

3. I could add an option to prevent opening the snapshots window from the grid control. But it will only open the window if you click on the top half. If you click on the bottom half it will drop down the list, and if you click on the left/right tabs it will cycle the presets. Do you want to be able to disable the dropdown bit? or the opening snapshots window? Or both?

[lb0]

Originally Posted by Sexan

IT IS FIXED!!!!!!!!!!!!!!!!!!!! THANK YOU!!!!!!!!!!!!!!!!!!
Regarding that meter script (that I've posted) I will make your job easier I will format it properly and post somewhere

The graphics bit?? YAY!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!1!!!!

Sorry - my bad all along - a simple start from 1 error!! grrr...

Anyway - best of luck with formatting the code - I started and gave up after 20 minutes - it was already 600 lines long - and still had 28000 character columns left to do.

You may have some luck if you try to automate it a bit - perhaps adding new line on ';' which is used a lot (but not always) to separate code statements.

Like I said - doing it manually - it'll prob. take best part of an hour. And there's lots and lots of code in there - so unless I can remove most of it (it's just bells and whistles) - it won't be much use for my script.

But then - yeah - how complex can the actual algorithm be??? The JSFX code is pretty short for TBPro's meters...

[Sexan]

Yeah!!!
There is a lot of "matrix" graphics etc also there is some repeating lines with his other plugins (assume that is graphics)

Edit: I think its probably the best to leave this script alone, after searching this forum a little I saw that author closed sourced all of his scripts.
Maybe Schwa or Justin can show us some simple example of peak/vu meter

[Sexan]

well this is what I've found regarding lua meter a code from SPK77
this is peak meter

local log10 = function(x) return math.log(x, 10) end

function get_peak_info()
  peak_info_channel_1 = reaper.Track_GetPeakInfo(reaper.GetSelectedTrack(0,0), 0)
  peak_info_channel_2 = reaper.Track_GetPeakInfo(reaper.GetSelectedTrack(0,0), 1)
  peak_info_dB_ch_1 = 20*log10(peak_info_channel_1)
  peak_info_dB_ch_2 = 20*log10(peak_info_channel_2)
  reaper.defer(get_peak_info)
end

get_peak_info()

[lb0]

Originally Posted by Sexan

well this is what I've found regarding lua meter a code from SPK77
this is peak meter

local log10 = function(x) return math.log(x, 10) end

function get_peak_info()
  peak_info_channel_1 = reaper.Track_GetPeakInfo(reaper.GetSelectedTrack(0,0), 0)
  peak_info_channel_2 = reaper.Track_GetPeakInfo(reaper.GetSelectedTrack(0,0), 1)
  peak_info_dB_ch_1 = 20*log10(peak_info_channel_1)
  peak_info_dB_ch_2 = 20*log10(peak_info_channel_2)
  reaper.defer(get_peak_info)
end

get_peak_info()

That's actually pretty useful. Give's a readout in dB though - which I would need to normalise and somehow make linear to select a linear control frame (it's been 20 years since I've done this sort of maths)... Any ideas anyone? Actually - it may not need to be made linear - if we take just the portion below 0dB (EDIT - and above -100) - ie. limit betweeen -100 & 0 - then the top 10% would be first -10dB to 0dB, next 10% would be -20 to -10dB etc. which is pretty common to a lot of peak meters?? Maybe set a lower limit around -60dB (like many reaper meters) then you get even better resolution at the top...

It's quick also it seems - I've run around 50 and it's barely noticeable inserted in my run loop. Admittedly most of the tracks are silent - but depending on optimisations - it should still be running through the maths algorithm...

Will play later with this...