Hmmm. That's the old strip file format - but it should still load. Would you mind sending me the strip file (I'll PM you my email) and I'll try to see what's going on.

Is this a strip file downloaded from the net? Or one you have created?

Actually that error line number is messed up - (unless you're running a version of the script from nearly a year ago!) There's one single call to that function in the whole code - and it resides ~line 16402.

EDIT2: Also - there's specific checks already around that call to prevent exactly that error... It shouldn't be possible with the latest code.

Can you give me a little more info as to exactly what you were doing to trigger the error - and whether you are using latest version of the script? Thanks

Hmmm. That's the old strip file format - but it should still load. Would you mind sending me the strip file (I'll PM you my email) and I'll try to see what's going on.

Is this a strip file downloaded from the net? Or one you have created?

Actually that error line number is messed up - (unless you're running a version of the script from nearly a year ago!) There's one single call to that function in the whole code - and it resides ~line 16402.

EDIT2: Also - there's specific checks already around that call to prevent exactly that error... It shouldn't be possible with the latest code.

Can you give me a little more info as to exactly what you were doing to trigger the error - and whether you are using latest version of the script? Thanks

Ah - it's indeed the old version, sorry! Let me try it again (selfmade script btw)!
EDIT: Actually I downloaded the whole github directory via "Clone or download" in the upper right corner, and it ended up with the 2016 version. I didn't know that I had to download the separate files.

EDIT2: Now with the latest version I get the following error
LBX Stripper.lua:7: unexpected symbol near '<'

EDIT3: This is super weird - how to effectively download??? I had to open the file within github and copy the content to the .lua script. But now the resources are still corrupt?!?!?

EDIT4: So I have to open each single file within github (RAW) and copy its contents. WORKING!!! Thanks!

Ah - it's indeed the old version, sorry! Let me try it again (selfmade script btw)!
EDIT: Actually I downloaded the whole github directory via "Clone or download" in the upper right corner, and it ended up with the 2016 version. I didn't know that I had to download the separate files.

aha - I thought there was something strange going on there.

Sorry it's a bit of a pain to download. When versions are a little more stable (as in - not in beta) - I'll probably try to make things much easier. But for now - it's as is.

Anyway - be sure to download the RAW versions of files from Github as github has a habit of corrupting files when downloaded using the download buttons causing the script to fail when starting it.

The main files you need are the LBX Stripper.lua file (the main script). And the LBXCS_resources.zip file (resources).

Create a folder in Reaper/Scripts folder called LBX. Place the lua file and unzip the contents of the zip file into the LBX folder - be sure to keep the folder structure.

Ah - it's indeed the old version, sorry! Let me try it again (selfmade script btw)!
EDIT: Actually I downloaded the whole github directory via "Clone or download" in the upper right corner, and it ended up with the 2016 version. I didn't know that I had to download the separate files.

EDIT2: Now with the latest version I get the following errorLBX Stripper.lua:7: unexpected symbol near '<'

Yep - please download the .lua file as RAW version.

When you open the file as RAW - it will show you the code text in your browser. You can either right-click and Save Page As... option, or simply copy the text into a text file and save as LBX Stripper.lua.

The first option (right-click Save Page As) takes me about 10 seconds to get the latest version...

When you open the file as RAW - it will show you the code text in your browser. You can either right-click and Save Page As... option, or simply copy the text into a text file and save as LBX Stripper.lua.

The first option (right-click Save Page As) takes me about 10 seconds to get the latest version...

New update - you can now remove cleanly the modulators from take switchers.

Please also note - I cannot guarantee backwards compatibility with this version with respect to modulators and take switchers.

Reason being - I've revamped the way mods work with take switchers. There's a new take switcher mode - so select take switcher mode when mod is assigned to a take switcher control. Then right-click the Take Switch Mode button - this correctly sets the min and max values. You can then simply click on randomize or drag the bars - and it should all work nicely and easily. If you change the number of takes in the item - simply increase the max value accordingly - or right-click the mode button again.

This way it should all work nicely and as you'd expect.

I've also done some work on some 'invisible' features (nothing too exciting - mainly cosmetic). Not ready yet - but hopefully you shouldn't notice anything and all should work as before.

plans ?
well...update says something else
i even able to assign same Modulator to two different Take Switchers in different Snapshots successfully!!
but..then..

also switching tracks from Stripper's browser while take modulation:
LBX\LBX Stripper.lua:7722: attempt to index a nil value (local 'ctl')

ill continue to push harder..

Have fixed (partially) - the mode change button. It still will say bad string - but that's only because the saved modulators in the snapshot don't contain the mode parameter. But you can now switch the mode - and resave the snapshot if it bothers you.

Second issue - I haven't been able to repeat yet. Can you give me any extra details?

Have fixed (partially) - the mode change button. It still will say bad string - but that's only because the saved modulators in the snapshot don't contain the mode parameter. But you can now switch the mode - and resave the snapshot if it bothers you.

Second issue - I haven't been able to repeat yet. Can you give me any extra details?

EDIT:
i am not sure but i think we need a "block/not allow" function, avoid to assign same modulator more than one Take switcher..in the same snapshot.
&
if make sense any
after (i think) first <bad string> all 32 modulators starts to shows bad string..

EDIT:
i am not sure but i think we need a "block/not allow" function, avoid to assign same modulator more than one Take switcher..in the same snapshot.
&
if make sense any
after (i think) first <bad string> all 32 modulators starts to shows bad string..

I'm not sure that's the issue - the issue I think was simply I forgot to save the mode setting in the snapshots. So it captures and stores them - until you restart the script - then it's forgotten the setting.

I'm not sure that's the issue - the issue I think was simply I forgot to save the mode setting in the snapshots. So it captures and stores them - until you restart the script - then it's forgotten the setting.

Have updated to fix this issue - hopefully

yes! all ok now

ah! my fault, i wasn't pointing the issue ..
just a warning might be good ..something like..
do not assign same modulator more than one Strip Switchers!
if the switchers in same page/track/strip no problem..(can easily realize - find the problem i mean)
but might cause confusion if in different track/strip.
..
or am i just confusing - complicating things unnecessarily?

ah! my fault, i wasn't pointing the issue ..
just a warning might be good ..something like..
do not assign same modulator more than one Strip Switchers!
if the switchers in same page/track/strip no problem..(can easily realize - find the problem i mean)
but might cause confusion if in different track/strip.
..
or am i just confusing - complicating things unnecessarily?

No - I don't think you need to worry. There's no problem assigning to different take switchers - even on different tracks. The problem was with the graphics updating routines - when the track changes - it tried to mark a non-existent control for update (causing the error). Now it first checks the strip and page are correct before marking the control for update. If the control is not visible (ie. on a different strip) - then it doesn't need to update the controls graphic...

Anyway - thanks as always for finding these bugs

EDIT: To be clear - you CAN assign modulator to more than one take switcher at once - it should work just fine

No - I don't think you need to worry. There's no problem assigning to different take switchers - even on different tracks. The problem was with the graphics updating routines - when the track changes - it tried to mark a non-existent control for update (causing the error). Now it first checks the strip and page are correct before marking the control for update. If the control is not visible (ie. on a different strip) - then it doesn't need to update the controls graphic...

Anyway - thanks as always for finding these bugs

EDIT: To be clear - you CAN assign modulator to more than one take switcher at once - it should work just fine

that's why i am here (being your headache)

ehamm..
Modulators CAN assign more than one Take Switchers.. OK..
but what if one has 100 and other 400 takes?
or you saying "just let the Randomness lead you"

Your testing is very much appreciated - as you can tell - I don't have a lot of free time and end up adding code during breaks and in the evening. Quite often clearly without testing thoroughly enough

If a take has 100 and another 400 - and you assign a modulator to it - if the modulator sets say 150 - then both will be put on TAKE 150 - except the smaller set will show an empty take. No bother - just this is what happens. I could use the modulus of the number to ensure a valid take is accepted - but this would be completely unpredicatable if ever you add more takes to an item. So best leave it working as is.

New update - hopefully fixes randomizing issues - no idea why they were cropping up though - seems maybe the data had got slightly squiffy - so restarting at least partially fixed it. Had you been deleting controls?

EDIT:

Subsets recalling for take switchers seems buggy - looking into...

EDIT2:

Fixed error which prevented take switchers being included when capturing snapshot data!! doh!! I've really had a nightmare with this one

Still - they are all really small trivial fixes - so nothing major to fix yet

EDIT:
PAGE / Clone to Subset (ctls only) drops the Take Switchers.. have to LEARN them manually in new Subset.
Subset clone is fine.

EDIT2:
and a Q.
i hope i can explain well..
Take Switchers
working absolutely great with the one shot drums (Sampler-Kontakt in my case) and wave loops
but when it comes to synths sample based or vsti synths...
no matter automate or manually switching, i get stuck notes most of the time ..
and i just found
"Send all notes off to all MIDI outputs/plug-ins [F3]" action ..it works great so far i tested..
...
even might be stupid one but worth to try anyway
here is the question

EDIT:
PAGE / Clone to Subset (ctls only) drops the Take Switchers.. have to LEARN them manually in new Subset.
Subset clone is fine.

EDIT2:
and a Q.
i hope i can explain well..
Take Switchers
working absolutely great with the one shot drums (Sampler-Kontakt in my case) and wave loops
but when it comes to synths sample based or vsti synths...
no matter automate or manually switching, i get stuck notes most of the time ..
and i just found
"Send all notes off to all MIDI outputs/plug-ins [F3]" action ..it works great so far i tested..
...
even might be stupid one but worth to try anyway
here is the question

Hi Arthur,
is this with latest version? line number doesn't make sense to me and cannot easily work out where the error occurs exactly. Would you mind trying with the latest version and let me know the line number of the error. Thanks.

Even better might be to send me the offending 'nil' strip file - and i'll test it here.