01-02-2023, 05:44 PM | #1 |
Human being with feelings
Join Date: Nov 2020
Posts: 47
|
Script Failure After Operating System Update
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 |
01-03-2023, 09:31 AM | #2 |
Human being with feelings
Join Date: Dec 2012
Posts: 13,333
|
I'll take a look whether I can reimplement functionality.
|
01-03-2023, 10:15 AM | #3 |
Human being with feelings
Join Date: Nov 2020
Posts: 47
|
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 Last edited by keener3rd; 01-03-2023 at 10:53 AM. |
01-03-2023, 10:21 AM | #4 | |
Human being with feelings
Join Date: Dec 2012
Posts: 13,333
|
Quote:
|
|
01-03-2023, 10:30 AM | #5 |
Human being with feelings
Join Date: Nov 2020
Posts: 47
|
|
01-03-2023, 10:35 AM | #6 |
Human being with feelings
Join Date: Jul 2021
Location: Swiss Zürich
Posts: 813
|
|
01-03-2023, 10:55 AM | #7 |
Human being with feelings
Join Date: Nov 2020
Posts: 47
|
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!
|
01-04-2023, 01:42 PM | #8 | |
Human being with feelings
Join Date: Dec 2012
Posts: 13,333
|
Quote:
Also you didn't mention what is not working in that script. |
|
01-04-2023, 02:19 PM | #9 | |
Human being with feelings
Join Date: Nov 2020
Posts: 47
|
Quote:
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 |
|
01-04-2023, 05:33 PM | #10 | |
Human being with feelings
Join Date: Nov 2020
Posts: 47
|
Quote:
|
|
01-05-2023, 02:09 AM | #11 | |
Human being with feelings
Join Date: Dec 2012
Posts: 13,333
|
Quote:
|
|
01-05-2023, 05:02 AM | #12 |
Human being with feelings
Join Date: Dec 2012
Posts: 13,333
|
You can try instead toggle action:
Project tabs: Play stopped background projects with active project |
01-05-2023, 07:38 AM | #13 | |
Human being with feelings
Join Date: Nov 2020
Posts: 47
|
Quote:
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 |
|
01-05-2023, 07:53 AM | #14 |
Human being with feelings
Join Date: Dec 2012
Posts: 13,333
|
Here is a post that might be useful for you:
https://forum.cockos.com/showpost.ph...60&postcount=6 |
01-05-2023, 07:54 AM | #15 | |
Human being with feelings
Join Date: Dec 2012
Posts: 13,333
|
Quote:
Also what name does your marker with this script have? Perhaps I know a way how to change that to unify for all machines. |
|
01-05-2023, 08:02 AM | #16 |
Human being with feelings
Join Date: Dec 2012
Posts: 13,333
|
Here is a good solution (about reaper-kb):
https://forum.cockos.com/showpost.ph...71&postcount=4 Just name it same on both machines. |
01-05-2023, 09:48 AM | #17 | |
Human being with feelings
Join Date: Nov 2020
Posts: 47
|
Quote:
Thanks! |
|
01-05-2023, 09:56 AM | #18 | |
Human being with feelings
Join Date: Nov 2020
Posts: 47
|
Quote:
The Windows marker is !_RS5127f0364c49969dc2c9077a67211ccbe2b4d40d. Thanks again! Glen |
|
01-05-2023, 09:57 AM | #19 | |
Human being with feelings
Join Date: Nov 2020
Posts: 47
|
Quote:
|
|
01-05-2023, 10:00 AM | #20 | |
Human being with feelings
Join Date: Dec 2012
Posts: 13,333
|
Quote:
|
|
01-05-2023, 10:17 AM | #21 | |
Human being with feelings
Join Date: Nov 2020
Posts: 47
|
Quote:
Once again, I really appreciate your help!!! Glen |
|
01-05-2023, 10:18 AM | #22 |
Human being with feelings
Join Date: Dec 2012
Posts: 13,333
|
Cool!
|
01-07-2023, 12:06 PM | #23 |
Human being with feelings
Join Date: Nov 2020
Posts: 47
|
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. |
01-09-2023, 09:08 AM | #24 |
Human being with feelings
Join Date: Nov 2020
Posts: 47
|
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.. |
Thread Tools | |
Display Modes | |
|
|