ReaNamer (track-item-region renaming utility) [amagalma & gianfini]

[amagalma]

[/i]The v1 and v2 scripts were removed from ReaPack and are now replaced by:

amagalma_gianfini_ReaNamer (track-item-region renaming utility)
(which is in essence: "amagalma_gianfini_Track-Item Name Manipulation - UNDO" v3)



- Manipulate track/item/region names (prefix/suffix, trim start/end, keep, clear, uppercase/lowercase, swap case/capitalize/titlecase, replace, strip leading & trailing whitespaces).
- Mode (tracks or items) is automatically chosen when the script starts. Then to change mode click on appropriate button.
- When satisfied with the modifications (which can be previewed in the list), COMMIT button writes the values to tracks/items/regions and creates an Undo point in Reaper's Undo History
- Requires SWS Extension

Key Shortcuts:

• Esc to close script

• Ctrl+T for Tracks mode
• Ctrl+R for Regions mode
• Ctrl+I for Items mode
• Ctrl+Enter Commit
• Ctrl+Z for Undo
• Ctrl+Shift+Z for Redo

• Alt+A for swAp case
• Alt+C for Clear
• Alt+E for trim End
• Alt+K for Keep
• Alt+L for Lowercase
• Alt+N for Number
• Alt+P for Prefix
• Alt+R for Replace
• Alt+S for trim Start
• Alt+T for Titlecase
• Alt+U for Uppercase
• Alt+W for strip Whitespaces
• Alt+X for suffiX
• Alt+Z for capitaliZe

Hello!

A new little script, inspired by spk77's python script: Manipulate track names

For the creation of the buttons and the mouse handling I have used spk77's code and I have used a Lokasenna function too. So, big thanks to both of them!

The script is here:
Track name manipulation

I would like some help from more experienced users: at the moment the script does not create any undo points. I would like undo points to be created under these two circumstances:
a) when the user exits the program
b) if the user changes track selection

How could this be accomplished?

EDIT: See post #4 for the final version


You may now find amagalma_Track Name Manipulation and amagalma_Item Name Manipulation in ReaPack.

Both scripts got replaced by the script amagalma_Track-Item Name Manipulation

[Lokasenna]

I haven't tried it, but you could do:

1) reaper.Undo_BeginBlock() when the script starts.

2) A function to see if the track selection has changed*, and then the following in Main():

if did_tracks_change then
  reaper.Undo_EndBlock("Track name manipulator", 0)
  reaper.Undo_BeginBlock()
end

3) reaper.Undo_EndBlock() as an else section for when gfx.getchar comes back as -1.

----------

* I had to do this in my "track selection follows item selection" script. Here's (I think) all you need:

local num_tracks
local sel_tracks = {}

-- *Very* limited for error checking, types, etc
-- Only use it if you know your tables will work
local function compare_tables(t1, t2)
  if #t1 ~= #t2 then return false end
  for k, v in pairs(t1) do
    if v ~= t2[k] then return false end
  end
  return true
end


-- In Main()

	-- Get the number of selected tracks
	num_tracks = reaper.CountSelectedTracks( 0 )

	-- Grab their MediaTracks into a table
	local cur_tracks = {}
	for i = 1, num_tracks do
		cur_tracks[i] = reaper.GetSelectedTrack( 0, i - 1)
	end

	-- See if the current and stored track selections match
	if not compare_tables(sel_tracks, cur_tracks) then

		-- User changed the track selection
		sel_tracks = cur_tracks

		reaper.Undo_EndBlock("Track name manipulator", 0)
		reaper.Undo_BeginBlock()
		
	end

Checking all of the tracks on every loop might be pretty rough for the script's CPU usage, so you may want to use a timing function to only run that block every 500ms or something.

[amagalma]

Thank you Lokasenna for your help!

3) reaper.Undo_OnStateChangeEx("Track name manipulation", 1, -1) without a reaper.Undo_BeginBlock() seems to do the trick better. Making-an-Undo-point-when-exiting "problem" solved!

I am going to try what you suggest for the track selection change undo creation point "problem".

Edit: Hmm.. I can't get it to work properly.. I get "reascript: Run" in the Undo list instead of named Undos...
Edit2: I am getting there.. I had to avoid UndoBegin... I'll update in a bit the code..

[amagalma]

Manipulate track names (prefix, suffix, trim start, trim end, uppercase, lowercase, swap case, capitalize, titlecase, replace, strip leading & trailing whitespaces).

Undo points are created only if track names have been changed when you close the script or if track names have been changed when you change track selection.

Track Names Manipulation

available in ReaPack

[Gianfini]

Great Job! That was strongly needed.

To make it really good there are few missing points I suggest

Basic version
- UNDO is key here, a small error and you get lots of tracks modified, and cannot get back to clean version
- There should be an option to add progressive numbering (in the beginning or at the end after suffix). It should have the number of digit option, start number, whether using numbers or letters

Advanced version (name building mode)
- possibility to build the naming from scratch, adding prefix, suffix, fixed text, progressive numbering and possibility to use old name as wildcard, building a mockup and committing all changes at once at the end. Preview of first 3-5 tracks should be available to see what you get.
For example Prefix=Snare, Suffix =" - mic ", Progressive numbering two digits, $track at the end: could result in "Snare - mic 01 AKG" "Snare - mic 02 SM57" "Snare - mic 03 SM58" (where AKG, SM57, SM58 were the original track names).
- possibility to add other wildcard in the building mode such as $item_name (first item), $channel_number, etc.

g

[amagalma]

Thanks!

Undo is already implemented. If you make a mistake just close the script and undo the last action!

I'll add at some point the progressive numbering. done!

For the rest, although they are very cool ideas, I do not have the time/knowledge to implement...

Edit: I added the progressive numbering ability. The update should be available later in ReaPack

[Gianfini]

Originally Posted by amagalma

Thanks!

Undo is already implemented. If you make a mistake just close the script and undo the last action!

I'll add at some point the progressive numbering. done!

For the rest, although they are very cool ideas, I do not have the time/knowledge to implement...

Edit: I added the progressive numbering ability. The update should be available later in ReaPack

thanks!

[amagalma]

In ReaPack you may now find amagalma_Item Name Manipulation, the sister script that deals with item names.

[amagalma]

Both scripts got replaced by the script amagalma_Track-Item Name Manipulation

[hopi]

handy thanks much!

[amagalma]

You're welcome

[amagalma]

Update: v1.1 (2017-07-28)

- Fixed crash when dealing with empty items
- Changed color scheme
- Added Clear button (clears all names)
- Added Keep button (trims names and keeps only the number of characters defined)

[nofish]

Just a "first usage" report.

Got a project for mixing where all tracks are named "Songtitle - ..." which I find redundant seeing on the tracknames (when importing and Reaper autonames the tracks according to the filenames) and the items.

Fired up your script, "Replace" "Songtitle -" with nothing, bam, gone.

Until now I used Batch rename utility for such tasks but being able to do it directly in Reaper is nice.

Very useful script, thank you.

[amagalma]

You are welcome!

Check v2 co-authored by Gianfini and me, it has some extra functionality and looks a lot better!

[amagalma]

This script was removed from ReaPack and is now replaced by:
amagalma_gianfini_ReaNamer (track-item-region renaming utility)

changelog:
Replaces "amagalma_gianfini_Track-Item Name Manipulation - UNDO"
- add: Region name support
- fix: crash when clicking on empty list
- fix: Down button could be pressed past last list item
- fix: changes in number of list items are correctly shown (no more 'nil' names)
- change: moved help text to the bottom
- change: improved how list items show

[sinkmusic]

Thank you, Amagalma, this look like a vvery handy script!

Do you think it would be possible to have such features as :
- REGIONS : something a bit like Reanoir : "change all the regions in time selection using random colors", "change all the regions in the time selection using shades from the selected color";
- REGIONS : rename region using track name (when a region is selected, as well as a track, obviously);

[amagalma]

Originally Posted by sinkmusic

Thank you, Amagalma, this look like a vvery handy script!

Do you think it would be possible to have such features as :
- REGIONS : something a bit like Reanoir : "change all the regions in time selection using random colors", "change all the regions in the time selection using shades from the selected color";
- REGIONS : rename region using track name (when a region is selected, as well as a track, obviously);

The first FR would be a FR for ReaNoir, which may happen sometime in the future. This utility deals with names, not colors.


The second FR, I don't see how this would work, nor I can see its usefulness.. Sorry!

[sinkmusic]

Originally Posted by amagalma

The first FR would be a FR for ReaNoir, which may happen sometime in the future. This utility deals with names, not colors.

Yes, Reannoir is amazing, i use it often
Should I duplicate the FR in the dedicated thread?

Originally Posted by amagalma

The second FR, I don't see how this would work, nor I can see its usefulness.. Sorry!

It can be useful depending on your process.
For instance, when you record, you can give the recording the track name (so your audio file have the track name, and can't have the region name).
But later in the production stage, if you need to share stems, you may need to have your stems rendered according to the project region (as tracks can be in a folder, or for whatever reason), so it could be useful to get the original track name and have it written in the region (if that makes sense).

[amagalma]

Originally Posted by sinkmusic

Yes, Reannoir is amazing, i use it often
Should I duplicate the FR in the dedicated thread?

No need to.. it has been requested a few times and it has been on my plans for a long time

It can be useful depending on your process.
For instance, when you record, you can give the recording the track name (so your audio file have the track name, and can't have the region name).
But later in the production stage, if you need to share stems, you may need to have your stems rendered according to the project region (as tracks can be in a folder, or for whatever reason), so it could be useful to get the original track name and have it written in the region (if that makes sense).

You can create regions from items ("Markers: Insert separate regions for each selected item") .. I still don't get it...

[sinkmusic]

Originally Posted by amagalma

No need to.. it has been requested a few times and it has been on my plans for a long time

Thanks!

Originally Posted by amagalma

You can create regions from items ("Markers: Insert separate regions for each selected item") .. I still don't get it...

Argh, sorry if i was unclear. It's a workflow thing, quite hard to explain... It depends on the way you record, the way you manage your items,the amount of samples you have and how you need to have your items in the end.

For instance : i record an item. It's a 10 minutes session with 200 short sounds on it. The item name is inherited from the instrument I recorded (for instance "Moog").
I put this item on a new track, which will have for name the kind of sound i recorded (for instance "bass").
Now i slice my session into hundreds of singles samples or snippets, depending on the timbre or note of the sounds (for instance "high resonance", "sub enabled", "square+saw", "C, D, E", etc).
My goal now would be to export each slices using the Region render matrix with such a string : "trackname_itemname_regionname01.wav".


I wish I could easily convert the markers into regions (because When I record, it's easy to drop markers on the fly during the recording, not regions).
I also wish I could give a region the name from a track (because sometimes you just change your mind, or also because sometimes when working with several group/sub folders, you realize it would be easier to have a region with a good name instead of too many sub-folders. In such a situation, I wish I could grab and item, and the script would get the name (where the item is) and give the track name to the region (where the item is, obvisouly).
I don't know if it sounds confuse or if that makes sense

[amagalma]

This is not a job that would be suited to this utility.

However, I have uploaded to ReaPack two actions for you:

amagalma_Rename region at edit cursor after the first selected item

amagalma_Rename region at edit cursor after the first selected track

[sinkmusic]

Originally Posted by amagalma

This is not a job that would be suited to this utility.

However, I have uploaded to ReaPack two actions for you:

amagalma_Rename region at edit cursor after the first selected item

amagalma_Rename region at edit cursor after the first selected track

Wonderful, thank you so much!

[Gianfini]

Hi, now i'm getting (track-item-region renaming utility).lua:1445: attempt to perform bitwise operation on a string value (field '?')

at each Commit

Only when in TRACK mode

g

[amagalma]

Originally Posted by Gianfini

Hi, now i'm getting (track-item-region renaming utility).lua:1445: attempt to perform bitwise operation on a string value (field '?')

at each Commit

Only when in TRACK mode

g

In my system, Lua automatically casts the string to number, so the bitwise operation works.. Maybe it doesn't work in all systems? No idea! Anyway, I added a tonumber(), in order to force manually the casting, so it will work always.. Uploading v1.02..

[Gianfini]

Originally Posted by amagalma

In my system, Lua automatically casts the string to number, so the bitwise operation works.. Maybe it doesn't work in all systems? No idea! Anyway, I added a tonumber(), in order to force manually the casting, so it will work always.. Uploading v1.02..

thanks I'll test it anyway on my Mac at home tonight and let you know

g

[Gianfini]

still

1446: attempt to perform bitwise operation on a nil value

Only in TRACK MODE

I'm currently testing on a PORTABLE INSTALL. Could that be the problem? will switch soon to fixed install and test it again

g

[amagalma]

Originally Posted by Gianfini

still

1446: attempt to perform bitwise operation on a nil value

Only in TRACK MODE

I'm currently testing on a PORTABLE INSTALL. Could that be the problem? will switch soon to fixed install and test it again

g

Hmm.. then it seems like BR_Win32_GetPrivateProfileString is not working correctly or for some reason the keys are named differently on your system!?.. What platform are you on? Mac?


Please, try this script and tell me what you see:

flag = ({reaper.BR_Win32_GetPrivateProfileString( "trackmgr", "flags", "", reaper.get_ini_file() )})[2]
_, flag2 = reaper.BR_Win32_GetPrivateProfileString( "trackmgr", "flags", "", reaper.get_ini_file() )
reaper.ShowConsoleMsg(string.format("flag1: %s    flag2: %s\n", flag, flag2))

[amagalma]

Furthermore, run action "Show REAPER resource path in explorer" and then open your reaper.ini and do a search for "[trackmgr]". Post all things under it until the next []. Thanks!

[Gianfini]

Originally Posted by amagalma

Furthermore, run action "Show REAPER resource path in explorer" and then open your reaper.ini and do a search for "[trackmgr]". Post all things under it until the next []. Thanks!

Here it is

[trackmgr]
wnd_vis=0
wnd_left=726
wnd_top=336
wnd_width=468
wnd_height=367


remember: it's a portable install

[Gianfini]

Originally Posted by amagalma

Hmm.. then it seems like BR_Win32_GetPrivateProfileString is not working correctly or for some reason the keys are named differently on your system!?.. What platform are you on? Mac?


Please, try this script and tell me what you see:

flag = ({reaper.BR_Win32_GetPrivateProfileString( "trackmgr", "flags", "", reaper.get_ini_file() )})[2]
_, flag2 = reaper.BR_Win32_GetPrivateProfileString( "trackmgr", "flags", "", reaper.get_ini_file() )
reaper.ShowConsoleMsg(string.format("flag1: %s    flag2: %s\n", flag, flag2))

Here is what comes out with your script (see attachment)

[amagalma]

Ok, just checked with a portable install. The [trackmgr] entry is created once you open the Track Manager and the flags entry is created once you change options.

v1.03 changelog
- fix: crash when commiting changes in Track mode for portable installs
- add: show pop-up if SWS is not installed

Should be ok now

[Gianfini]

Originally Posted by amagalma

Ok, just checked with a portable install. The [trackmgr] entry is created once you open the Track Manager and the flags entry is created once you change options.

v1.03 changelog
- fix: crash when commiting changes in Track mode for portable installs
- add: show pop-up if SWS is not installed

Should be ok now

Works now!

that was not easy!

thanks

[vanhaze]

Guys, i get this error when synchronizing packages in ReaPack:

ReaTeam Scripts/Various/ReaNamer (track-item-region renaming utility) v1.03:
Conflict: Scripts/ReaTeam Scripts/Various/amagalma_Track-Item Name Manipulation Replace Help.lua is already owned by another package

Any clue ?

OSX 10.15.7, Latest Reaper dev release.

[lexaproductions]

Originally Posted by vanhaze

Guys, i get this error when synchronizing packages in ReaPack:

ReaTeam Scripts/Various/ReaNamer (track-item-region renaming utility) v1.03:
Conflict: Scripts/ReaTeam Scripts/Various/amagalma_Track-Item Name Manipulation Replace Help.lua is already owned by another package

Any clue ?

OSX 10.15.7, Latest Reaper dev release.

yup me too
On mac as well

[amagalma]

v1.08 changelog:
- add: ability to specify separator when numbering
- add: ability to match case or not in pattern replacement
- change: in Replace mode from now on there is no need to escape commas
- change: name of provided help file for the Replace
- change: updated help file for the Replace

[amagalma]

Originally Posted by amagalma

- change: name of provided help file for the Replace

@vanhaze & @lexaproductions: I think now it should be ok

[lexaproductions]

Great thanks.
Could you consider linking Ctl-Enter to commit/close? To be able to close the script without the mouse?

[vanhaze]

Originally Posted by amagalma

@vanhaze & @lexaproductions: I think now it should be ok

Yes, it is, thx a bunch !!

[amagalma]

v1.10 changelog:
- add: focus is returned back to script after a GetUserInputs dialog
- add: Ctrl+Enter to Commit
- add: T key for Tracks mode, R key for Regions mode, I key for Items mode

If anyone has any other ideas regarding key shortcuts, I listen

[lexaproductions]

Oh wow thanks!

I wouldn’t mind being able to choose each renaming modes with Alt-[LETTER]
Alt-R for replace
Alt-A for Append
Etc...