Script Failure After Operating System Update

[keener3rd]

Hello,

I'm using the ARM version of Reaper on a MacBook Pro and everything was working perfectly until the Ventura update. I've been using a script a forum member shared (attached), which kills everything running in any project tabs that aren't the active tab, but the script hasn't worked since the operating system update.

Has anyone else run into a similar issue with scripts no longer working? If not, are there any other scripts out there that can perform the same function?

Thanks!
Glen

[vitalker]

I'll take a look whether I can reimplement functionality.

[keener3rd]

I'll take a look whether I can reimplement functionality.

Thank you very much! If it helps, the context is that we put each song into a project tab and have lights, backing tracks, video, vocal cues and guitar pedal changes set up. There are markers in each file that make the next tab active when we finish a song and a marker with the command ID for that script that would stop anything in another tab at the beginning of each song. Screen shots attached if that helps.

Thanks again!
Glen

[vitalker]

Thank you very much! If it helps, the context is that we put each song into a project tab and have lights, backing tracks, video, vocal cues and guitar pedal changes set up. There are markers in each file that make the next tab active when we finish a song and a marker with the command ID for that script that would stop anything in another tab at the beginning of each song. Screen shots attached if that helps.

Thanks again!
Glen

Okay, thanks for the info. The screenshots show just first track. I don't know how it may help me. :)

[keener3rd]

Okay, thanks for the info. The screenshots show just first track. I don't know how it may help me. :)

Whoops! My first attempt at screen shots on a Mac...and it was an epic fail. 😂 I’ll update them in a few.

[Wallaby]

Whoops! My first attempt at screen shots on a Mac...and it was an epic fail. 😂 I’ll update them in a few.

Command + Shift + 4
Screenshot of selected area with mouse click and hold and drag a diagonal, release the mouse makes the screenshot, onto desktop.

[keener3rd]

Command + Shift + 4
Screenshot of selected area with mouse click and hold and drag a diagonal, release the mouse makes the screenshot, onto desktop.

Thanks! My issue turned out to be that the resolution was way too large, so I just reduced it and the images were updated successfully. Always learning something new on the Mac! :)

[vitalker]

Thanks! My issue turned out to be that the resolution was way too large, so I just reduced it and the images were updated successfully. Always learning something new on the Mac! :)
Actually on new screenshots you are showing what you described in the first post. :)

Also you didn't mention what is not working in that script.

[keener3rd]

Actually on new screenshots you are showing what you described in the first post. :)

Also you didn't mention what is not working in that script.

Right. I just wanted to provide the visual of how we are doing everything in case I didn't articulate it well enough. :)

The Marker at the end of each song does make the next tab active as expected. When kicking off the song on the active tab, the script used to kill everything on the previous tab when the cursor hit the Marker. Unfortunately, now the script will stop the cursor, but it doesn't kill the signal for the stage lights (DMXIS track) from the previous tab.

Our backup machine is a Windows laptop and we share the .rpp files via a google drive. The scripts works on the Windows machine without issue.

Thanks again!
Glen

[keener3rd]

Right. I just wanted to provide the visual of how we are doing everything in case I didn't articulate it well enough. :)

The Marker at the end of each song does make the next tab active as expected. When kicking off the song on the active tab, the script used to kill everything on the previous tab when the cursor hit the Marker. Unfortunately, now the script will stop the cursor, but it doesn't kill the signal for the stage lights (DMXIS track) from the previous tab.

Our backup machine is a Windows laptop and we share the .rpp files via a google drive. The scripts works on the Windows machine without issue.

Thanks again!
Glen

Quick update. The script no longer stops the cursor. I thought it did based on some testing a few days ago, but realized our click track ends naturally and not due to the cursor. So basically, the script has just completely stopped working. Sorry for the misunderstanding!

[vitalker]

Quick update. The script no longer stops the cursor. I thought it did based on some testing a few days ago, but realized our click track ends naturally and not due to the cursor. So basically, the script has just completely stopped working. Sorry for the misunderstanding!
Actually I am still thinking what can cause this behavior. Do you know that you have to put marker a little bit before the project ends (let's say, 1/128 before). Did you test same projects on both machines?

[vitalker]

You can try instead toggle action:
Project tabs: Play stopped background projects with active project

[keener3rd]

Actually I am still thinking what can cause this behavior. Do you know that you have to put marker a little bit before the project ends (let's say, 1/128 before). Did you test same projects on both machines?

Yes on both accounts. My guitarist typically updates the files on his Win laptop and then I copy them over to the Mac. We've been using this setup (a Mac and a Win laptop) for a little over a year and it's worked flawlessly for our practices and gigs. Before getting the Mac, we used the same approach with two Windows laptops for a few years.

Depending on whether the gig is two or three sets, I'll save a list of open projects as a set list, so that will contain anywhere from 15 - 25 project tabs (one for each song).

The command ID for the "kill" script is different on the Mac than the command ID for the Windows laptop, so we have one marker with the Mac command ID and one with the Win command ID in each project.

After typing that out, I decided to delete the marker with the Win "kill" command ID, test the "kill" script...and it worked! I still need to test this out at our practice space with the stage lights, TVs, etc. hooked up, but this may be the path forward. If so, my hope is that I can take the me2beats script on the Mac, import that on the Win laptop and have them both utilize the same command ID.

I'm hoping to get this tested in the next few days, so I'll provide an update as soon as I can.

Thanks!
Glen

[vitalker]

Here is a post that might be useful for you:
https://forum.cockos.com/showpost.php?p=1879260&postcount=6

[vitalker]

You can try instead toggle action:
Project tabs: Play stopped background projects with active project
Did you try this method?
Also what name does your marker with this script have? Perhaps I know a way how to change that to unify for all machines.

[vitalker]

Here is a good solution (about reaper-kb):
https://forum.cockos.com/showpost.php?p=1978871&postcount=4

Just name it same on both machines.

[keener3rd]

Here is a post that might be useful for you:
https://forum.cockos.com/showpost.php?p=1879260&postcount=6

Good to know! Mine is in Scripts -> Custom Scripts, so I'll check on the Win machine and get those set to the same location.

Thanks!

[keener3rd]

Did you try this method?
Also what name does your marker with this script have? Perhaps I know a way how to change that to unify for all machines.

I haven't tried that method yet, but I am al little confused on how playing the stopped projects would help. If I have the previous project running and I go to start the next project, wouldn't that start all of the other stopped projects in addition to the one I need started?

The Windows marker is !_RS5127f0364c49969dc2c9077a67211ccbe2b4d40d.

Thanks again!
Glen

[keener3rd]

Here is a good solution (about reaper-kb):
https://forum.cockos.com/showpost.php?p=1978871&postcount=4

Just name it same on both machines.

I can attempt to pull this off in the next few days when we get together for testing. :)

[vitalker]

I haven't tried that method yet, but I am al little confused on how playing the stopped projects would help. If I have the previous project running and I go to start the next project, wouldn't that start all of the other stopped projects in addition to the one I need started?

The Windows marker is !_RS5127f0364c49969dc2c9077a67211ccbe2b4d40d.

Thanks again!
Glen
Okay, then use what Ada Mespotine wrote. That toggle won't run anything, it's just turning On/off this ability. Just try.

[keener3rd]

Good to know! Mine is in Scripts -> Custom Scripts, so I'll check on the Win machine and get those set to the same location.

Thanks!

I just moved the Mac script to the same location as the Win script and the command IDs now match! I deleted the Marker with the previous Mac command ID, ran a quick test on the Mac and it was successful. I think this will resolve our issue once and for all and make maintenance easier going forward, so I’ll report back after this weekend’s testing. 🤞🏻

Once again, I really appreciate your help!!!
Glen

[vitalker]

Cool!

[keener3rd]

Been testing and troubleshooting for the last few hours and, although the script is stopping the all non-midi tracks on the previous project tab, it is not stopping the midi note associated with the lights from that tab. 😕

It’s weird because there are no issues with the lights starting up. The problem is that, with the kill script failing, the lights from the previous song overlap with the lights for the current song until the previous midi light track completes. The reason we have the lights extend at the end of songs is so all of the stage lights don’t go dark between songs. I’m stumped because, as I said earlier, this all previously worked flawlessly.

[keener3rd]

Looks like we’ve at least found a workaround. If we add a very quick all lights on white signal at the start of the file (so quick that it isn’t seen), that to kills the midi signal from the previous tab and the lights work as expected for the current tab.

With our previous setup, the lights would go dark for a split-second between when the kill script stopped the light track from the previous tab and the light track for the current tab started. The workaround we found means we’ll need to update all of our reaper files, but it does result in the same user experience we had before the script issue on my Mac..