Save and recall track record arm states

[talustalus]

Well, we can save all kinds of states in Reaper (track selection, solo/mute etc).

But another really useful one would be Record-arm states (armed/unarmed) for the tracks.

Probably the most useful of all for anyone who is composing and recording jumping around numerous instruments/sound sources.

Simplified real-life Example: I'm recording synth into track 1. Now I want to record vocals into track 2. I could have a dedicated action/button for 'Synth' record state, and another one for 'Vocal' record state, and easily jump between them.

(In reality, my projects are more complex, if it was just the above scenario I could live with changing the arm states of two different tracks, but it's more).


Please can we see this happen?

Or, any script legends know how this can be achieved through lua?

[Coachz]

How do you want the actions to work ? Disable all arming and arm track with name Synth ? Then the other action disable all arming and arm track with name vocal ?

These two attached save/restore all armed states.

[talustalus]

Thanks.

I think I went off on a tangent with my examples.

The original intention was just to have slots where you could save the current arm states for all tracks in the project, not for specific track names. ie. Save/Recall state 1, state 2, state 3...

I'll try this files out, because I think they're what I was seeking


thank you!

[Coachz]

Here's an example of saving state.

https://forum.cockos.com/showpost.ph...4&postcount=12

[talustalus]

Originally Posted by Coachz

How do you want the actions to work ? Disable all arming and arm track with name Synth ? Then the other action disable all arming and arm track with name vocal ?

These two attached save/restore all armed states.

Man it works, thanks so much.

But when I use the 'restore arm state' script in a Cycle action I get this message.

'number expected, got nil'

My guess is because part of that cycle action creates a new track for me, and the script gets confused because the no. of tracks during the 'save arm state' process is different from the no. of tracks in the 'restore arm state' process.

EDIT: Yes - that's what it was. Nothing wrong with your script. I adjusted my cycle action order. Thanks a bunch dude!

[Coachz]

Originally Posted by talustalus

Man it works, thanks so much.

But when I use the 'restore arm state' script in a Cycle action I get this message.

'number expected, got nil'

My guess is because part of that cycle action creates a new track for me, and the script gets confused because the no. of tracks during the 'save arm state' process is different from the no. of tracks in the 'restore arm state' process.

That would be correct. What you can do is change the restore script to count the number of Records being returned and only iterate through that many track numbers. To do that you'll want to copy the restore section above the track loop to get a count of Records that are ready to be restored

[talustalus]

Thanks I'm grateful to ya

[talustalus]

Originally Posted by Coachz

That would be correct. What you can do is change the restore script to count the number of Records being returned and only iterate through that many track numbers. To do that you'll want to copy the restore section above the track loop to get a count of Records that are ready to be restored

I tried and failed... this is the error I get. I'm almost entirely sure it's because I've done something wrong in the coding, not being a coder and all that.

[Coachz]

Paste your code here in between

[CODE1]

[/CODE1]

Without the 1 and tell me what you want it to do. For example, do you want it to saved the armed state of all the current tracks by track number and then allow you to add as many tracks as you want and still restore the same state by the same track numbers ignoring the new tracks?

[talustalus]

Originally Posted by Coachz

Paste your code here in between

[CODE1]

[/CODE1]

Without the 1 and tell me what you want it to do. For example, do you want it to saved the armed state of all the current tracks by track number and then allow you to add as many tracks as you want and still restore the same state by the same track numbers ignoring the new tracks?

Appreciate it man but I take zero credit for 'my' code. This is 100% you. It works great.

Yes, I want it restore the same state per the pre-existing track states before the new tracks were created (so ignoring the new tracks as you said).

Sorry ://

[Coachz]

Originally Posted by talustalus

Appreciate it man but I take zero credit for 'my' code. This is 100% you. It works great.

Yes, I want it restore the same state per the pre-existing track states before the new tracks were created (so ignoring the new tracks as you said).

Sorry ://

Right so paste what you tried in code so we can see the problem. Did you try to modify my code at all?

[talustalus]

Originally Posted by Coachz

Right so paste what you tried in code so we can see the problem. Did you try to modify my code at all?

All I did was move your script around, trying to interpret "To do that you'll want to copy the restore section above the track loop to get a count of Records that are ready to be restored"

I just made a mess of it by moving things around really. (saved to a new script file then deleted it).

I have no understanding of the commands.

[Coachz]

try this

[talustalus]

Seems to work, except that I get this pop up after executing the action:

[talustalus]

Originally Posted by Coachz

try this

Actually, I tried it a few times. It re-arms based on the track *numbers* that were armed rather than the actual tracks. So if they moved as a result of adding new tracks, they won't be re-armed because they will have moved to what was a previously non-armed track number.

But, I think you've helped me enough, I'll just let this one go because I don't want you to put in any more time for me unless you see it useful for yourself as well.


Thanks for all your help.

[Coachz]

Originally Posted by talustalus

Actually, I tried it a few times. It re-arms based on the track *numbers* that were armed rather than the actual tracks. So if they moved as a result of adding new tracks, they won't be re-armed because they will have moved to what was a previously non-armed track number.

But, I think you've helped me enough, I'll just let this one go because I don't want you to put in any more time for me unless you see it useful for yourself as well.


Thanks for all your help.

I have no problem helping but how can you identify a track? Will they all be guaranteed unique names ? Not 2 tracks both named guitar ? Currently it stores the track number so it will only arm correctly if the new tracks are at the end of the current tracks. If you want to do it by name though you have to not change their names between saving and restoring and you can't have duplicates. See what I mean ?

[talustalus]

Originally Posted by Coachz

I have no problem helping but how can you identify a track? Will they all be guaranteed unique names ? Not 2 tracks both named guitar ? Currently it stores the track number so it will only arm correctly if the new tracks are at the end of the current tracks. If you want to do it by name though you have to not change their names between saving and restoring and you can't have duplicates. See what I mean ?

Totally understand. And yes the names will be unique and zero duplicates. I'm very stringent on my track naming which is why I thought up something like this being able to work for my work.

The only thing that changes between save and restore of arm states will be newly added tracks (but these new tracks will again always have unique names -- their names won't even be blank because I bring up the track rename immediately as a custom macro, so they shouldn't get in the way)

... and, the previously armed track names will not change from save to restore state.

[Coachz]

So it sound like storing and restoring them by name will work for you. I'll give it a go.

[Coachz]

Try this.

[talustalus]

Originally Posted by Coachz

Try this.

absolute perfection!

I'm really really grateful, thank you so much for taking the time. This is pure gold!!

[Coachz]

Originally Posted by talustalus

absolute perfection!

I'm really really grateful, thank you so much for taking the time. This is pure gold!!

excellent, glad to be of help for a change instead of a burden !

[talustalus]

Originally Posted by Coachz

excellent, glad to be of help for a change instead of a burden !

U kidding? Huge help

[Loulou92]

It's extremely useful . I can't recommend enough that you put it in Reapack, I feel lucky to have found your scripts, I suspect many others will want to use something like this and right now they could think it's not possible because it doesn't pop up in their action window.

Thank you for this. It saved my day !!

[Coachz]

Hopefully, clear reapack instructions are coming so it will be possible to have a reapack repo without needing git. One of the users is working on scripts to do it. Yay

[Loulou92]

I have no idea what you are talking about hahaha but it's a good thing I guess !! double yay then

[Coachz]

The idea is to be able to have a folder with scripts locally that are my reapack and not have to set up a full development environment to keep them up to date in the github repo.

[talustalus]

I reiterate again -- This has been a godsend, thanks Coachz!!

[Coachz]

Glad to help

It's the little things.....

https://genius.com/Alice-cooper-its-...-things-lyrics