LBX Stripper - create custom channel strips

[lb0]

Originally Posted by timbralzoom

060:
LBX Stripper.lua:53752: ')' expected near <eof>

That makes absolutely no sense to me. Can you try and redownload and check again...

Does it run at all?

[timbralzoom]

Originally Posted by lb0

That makes absolutely no sense to me. Can you try and redownload and check again...

Does it run at all?

wow good catch!
re downloaded and it worked!
strange, never happened before..
i think now on i have to wait a little before the copy codes

EDIT:
v..060
button belongs to Axis 1 and controlling other Axis 2,3,4
main plugin controls doesn't fade (visually) but others fine:

(you'll see some multiple clicks they just my mistakes)
[/url]

[lb0]

Originally Posted by timbralzoom

wow good catch!
re downloaded and it worked!
strange, never happened before..
i think now on i have to wait a little before the copy codes

Phew!!

Think I've fixed all the snapshot issues in the latest

[timbralzoom]

quick test
seems controls fade issue same in the v061 too

EDIT:
sorry.. Controls Fade in the Offline state was OK
but seems Bypass still same (in v061)


just in case .. same gif as above (recorded in 060)
[/url]

-motto-

[lb0]

Originally Posted by timbralzoom

quick test
seems controls fade issue same in the v061 too

Sorry - was testing mainly snapshot captures and the additional fx added by right-click menu - forgot the single/original plugin use case.

Could you try 0062?

Now I'm off to bed. If still a problem - will look into another day

[timbralzoom]

Originally Posted by lb0

Sorry - was testing mainly snapshot captures and the additional fx added by right-click menu - forgot the single/original plugin use case.

Could you try 0062?

Now I'm off to bed. If still a problem - will look into another day

all my findings are fine now in 062 !

Thank you & goodnight!

[lb0]

Originally Posted by timbralzoom

all my findings are fine now in 062 !

Thank you & goodnight!

Thanks for testing

[RJHollins]

Go get some sleep .... you Animal !!!

[Arthur McArthur]

Thank you Leon!!! I'm just starting to test them and they look wonderful. The Strip Switcher buttons are working beautifully. A few issues with O/B/W controls: I can't seem to select them in Snapshot Learn Controls (though they do respond to page snapshots)

Also, I think I found the oddity you mentioned with recalling snapshots for plugins with O/B/W and Bypass controls for the same plugin: https://imgur.com/a/AhAFW . It looks to me like the parameters are getting saved correctly, the snapshot just needs to be clicked twice. This is something I've noticed before when recalling parameters from fx at the same time as recalling a preset via prog change control: the preset loads after the param controls so the values get overwritten until the snapshot gets double-clicked. For these cases, what do you think about a "double trigger" snapshot mode where, on changing snapshots, it would load the values again after *x time interval*?

[lb0]

Originally Posted by Arthur McArthur

Thank you Leon!!! I'm just starting to test them and they look wonderful. The Strip Switcher buttons are working beautifully. A few issues with O/B/W controls: I can't seem to select them in Snapshot Learn Controls (though they do respond to page snapshots)

Also, I think I found the oddity you mentioned with recalling snapshots for plugins with O/B/W and Bypass controls for the same plugin: https://imgur.com/a/AhAFW . It looks to me like the parameters are getting saved correctly, the snapshot just needs to be clicked twice. This is something I've noticed before when recalling parameters from fx at the same time as recalling a preset via prog change control: the preset loads after the param controls so the values get overwritten until the snapshot gets double-clicked. For these cases, what do you think about a "double trigger" snapshot mode where, on changing snapshots, it would load the values again after *x time interval*?

Have updated so new controls can be learned.

I thought I'd definitely fixed the control updating in the final version last night. but maybe not quite. It is difficult to cover all bases. Will look into when I get more time. But in the meantime - I'm pretty sure it's perfectly usable.

For things like program changes - yes - maybe an optional (per snapshot set) double-trigger option.

EDIT: Please note also - at the moment - Randomize will ignore the new control also - will need to look into this if required...

[RJHollins]

will test too ....

but can I say ...... how GREAT having the UPDATE function in SETTINGS is !

[lb0]

Originally Posted by RJHollins

will test too ....

but can I say ...... how GREAT having the UPDATE function in SETTINGS is !

Thank you (for testing) .

Yeah - the update function should help with the constant small fixes that get released.

[Arthur McArthur]

Originally Posted by lb0

Have updated so new controls can be learned.

I thought I'd definitely fixed the control updating in the final version last night. but maybe not quite. It is difficult to cover all bases. Will look into when I get more time. But in the meantime - I'm pretty sure it's perfectly usable.

For things like program changes - yes - maybe an optional (per snapshot set) double-trigger option.

EDIT: Please note also - at the moment - Randomize will ignore the new control also - will need to look into this if required...

Great, the O/B/W are working now with snapshots, thanks. Personally, I don't need the randomize functionality for them (I'm only randomizing wet buttons for a handful of controls, which I'm happy to keep)

One odd thing- My arrow keys seem to have stopped moving controls, is there a setting I may have accidentally activated?

And thanks again for the strip switcher buttons, they're making navigating and setting up AHK image search functions a whole lot easier!

[lb0]

Originally Posted by Arthur McArthur

Great, the O/B/W are working now with snapshots, thanks. Personally, I don't need the randomize functionality for them (I'm only randomizing wet buttons for a handful of controls, which I'm happy to keep)

One odd thing- My arrow keys seem to have stopped moving controls, is there a setting I may have accidentally activated?

And thanks again for the strip switcher buttons, they're making navigating and setting up AHK image search functions a whole lot easier!

In advanced - there is a 'disable key input when surface locked' option. Could it be that?

I've had some wierdness in that keycode for my number pad * is the same as the keycode for shift+ one of the number keys. Means I have to be really careful how I assign stuff. I think someone else mentioned that pressing a certain key was triggering something else entirely. Will keep an eye on.

EDIT - actually - in my case - it was shift+8 which happens to be the * !! haha - serves me right for coding in the dark! Shame it doesn't properly distinguish between numpad and other key - although I can detect status for shift... anyway - I digress.

Just to confirm - arrow keys are working ok for me.

[Arthur McArthur]

Originally Posted by lb0

In advanced - there is a 'disable key input when surface locked' option. Could it be that?

That's exactly what it was (facepalm), thanks!

[lb0]

Originally Posted by Arthur McArthur

That's exactly what it was (facepalm), thanks!

haha - there's a reason I 'hid' some settings away in the Advanced section

Perhaps I should rename it to the 'Do not mess with unless you really need to - Bad things may lie beyond' section?

[Arthur McArthur]

haha! yes a "HERE BE DRAGONS" sign would be appropriate I think!

[ThrashJazzAssassin]

Found something - very reproducable
Changing faderbox-only snapshot
strip here https://stash.reaper.fm/33325/Zebra2...napshots.strip
Update - I resaved the strip and it's not crashing, but faderbox assignments are gone

[lb0]

Originally Posted by ThrashJazzAssassin

Found something - very reproducable
Changing faderbox-only snapshot
strip here https://stash.reaper.fm/33325/Zebra2...napshots.strip
Update - I resaved the strip and it's not crashing, but faderbox assignments are gone

Thanks TJA for report. Will look into (although I do not have zebra - will still try it out) - what version of Stripper?

[ThrashJazzAssassin]

Originally Posted by lb0

Thanks TJA for report. Will look into (although I do not have zebra - will still try it out) - what version of Stripper?

Version 0.94.0066

Thank you.

It's very reproducible, but only with that particular strip so far. If you don't have the plugins will it make it harder for you to look in to? I could try and find the same bug with cockos plugs if you think that would help.

[lb0]

Originally Posted by ThrashJazzAssassin

Version 0.94.0066

Thank you.

It's very reproducible, but only with that particular strip so far. If you don't have the plugins will it make it harder for you to look in to? I could try and find the same bug with cockos plugs if you think that would help.

I think it will help - I'm not getting the error here - and it's not yet obvious to me why it's happening.

Will look into more tomorrow.

[timbralzoom]

April 12
with a few more
https://forum.cockos.com/showpost.ph...postcount=2068
Have Fun!

[RJHollins]

As always ..... Thanks T !!

will check them out

[timbralzoom]

Enjoy RJ! as always
...

Update 2018 - 10

https://drive.google.com/open?id=1HI...yE7D2YDVhxvXZw

i remove Gfx/BG images .. now moving them in the strips much easier.

[lb0]

Originally Posted by timbralzoom

Stack Rack Share Strips

Thanks Timbral!! Will be very useful.

[timbralzoom]

Originally Posted by lb0

Thanks Timbral!! Will be very useful.

i hope so! (<-- sneaky hihi smile)
but be prepare for the new headaches if they get popular..
hint: access hidden controls directly in Modulator window
via Stripper -extended?- Learn (even maybe for the Faders too)
..
joking apart,
i am planning to update/edit the same post in time..
to keep all my shared strips easily findable in same post.

[lb0]

Originally Posted by timbralzoom

i hope so! (<-- sneaky hihi smile)
but be prepare for the new headaches if they get popular..
hint: access hidden controls directly in Modulator window
via Stripper -extended?- Learn (even maybe for the Faders too)
..
joking apart,
i am planning to update/edit the same post in time..
to keep all my shared strips easily findable in same post.

Let me know details and I'll look into

Will add link to post in first post.

[timbralzoom]

Originally Posted by lb0

Let me know details and I'll look into

Will add link to post in first post.

Thanks! now i can continue to update same post
..
details! .. yay!

ehamm..
for example for this kind stack controls / hidden storage type strips
would amazing to have something like Learn function in the Modulator window
press to Modulator Learn button & tweak parameter from plugin GUI
(even maybe see the parameter name somewhere in Modulator window)
press to OK or Learn button again
walaa! ..

[ThrashJazzAssassin]

Same report as before, but with ReaComp. Trying to change a fader-only snapshot. Hope this helps.

https://stash.reaper.fm/33355/comptest.strip

LBX Stripper.lua:56944: attempt to index a nil value (field '?')

[timbralzoom]

no error but

[lb0]

Originally Posted by ThrashJazzAssassin

Same report as before, but with ReaComp. Trying to change a fader-only snapshot. Hope this helps.

https://stash.reaper.fm/33355/comptest.strip

LBX Stripper.lua:56944: attempt to index a nil value (field '?')

Yep - error repeated - will look into - thanks.

[lb0]

Originally Posted by timbralzoom

no error but

I had that - but have you got __LBX_CTL track. When I added the CTL track and then dragged in the strip - i got the error.

[timbralzoom]

Originally Posted by lb0

I had that - but have you got __LBX_CTL track. When I added the CTL track and then dragged in the strip - i got the error.

oops!
yes can confirm same 56944 error with __LBX_CTL track.


EDIT:
added Rea Pitch Design Strip
https://forum.cockos.com/showpost.ph...postcount=4922

[ThrashJazzAssassin]

Thanks for looking in to!

Just found ALT+Right drag on a strip and adding Shift removes snapping

[lb0]

Originally Posted by ThrashJazzAssassin

Thanks for looking in to!

Just found ALT+Right drag on a strip and adding Shift removes snapping

haha - been there a while - but secret!! shhh

EDIT: I know exactly what's going on with the error - will fix - but a little busy at the moment.

[ThrashJazzAssassin]

Great news.

Some new sharestrips here https://github.com/ThrashJazzAssassin/LBX-Strips

[lb0]

Originally Posted by ThrashJazzAssassin

Great news.

Some new sharestrips here https://github.com/ThrashJazzAssassin/LBX-Strips

Great stuff - thank you! I have a number of these plugins so will check them out when I've finished fixing things

[lb0]

Originally Posted by ThrashJazzAssassin

Great news.
[/url]

Hopefully the update will fix this problem.

Works fine for your Zebra strip (which I think I was originally testing wrong - without a CTL track - I'm an idiot!).

The other strip - also works in that it doesn't cause a crash - but also as none of the learned controls in the faderbox subset actually exist in the saved strip data - then they simply get deleted. I've no idea how this has happened, and haven't been able to repeat here. The control id's for the subset simply do not match up with any in the strip. Do you ever use the Tools->Regenerate ID option - this is the only way I can think this might have happened, and is likely to cause these symptoms.

Also in the update - a few other fixes.

There is also a new control in Tracks->Other Controls. Param Update Control is used like a macro control in that it learns certain types of controls from the strip. On clicking it (it should be a button type) - it simply will resend the current value held by the control to the plugin/midi out etc... This has been a very specific request - so not sure how useful it will be unless you need this exact functionality.

It isn't quite complete however - as it doesn't work with all controls that are required yet...

And another kind of biggy to keep in mind with this update is that certain things about the way control values are read in and displayed have changed. This was to make the non-monitored controls react better under certain circumstances. The changes have potential to affect performance if I have got something wrong - but I don't think it will generally. Normal monitored controls should work as before.

Please let me know if you notice anything strange going on, performance wise, or anything else - it might be because of these changes - and I'll need to investigate.

Cheers

[timbralzoom]

just tried with "comptest" strip and can confirm seems no more 56944 error.
(yep .. didn't forgot the __LBX_CTL this time )

[lb0]

Originally Posted by timbralzoom

just tried with "comptest" strip and can confirm seems no more 56944 error.
(yep .. didn't forgot the __LBX_CTL this time )

Be good to see if some of your big strips work well with the latest. Yours and Arthur's are the usual best stress test applications.

I've had your UGG LT running fine with no noticeable difference - but it's definitely those with unmonitored controls too that are important to check. I'm confident though that the changes should be pretty transparent.

Oh - and thanks for checking