The User Permission Window allows setting renaming options.

Here you see the User Permission window. It opens right before the original file cleaning is begun.

The window allows you to configure the cleaning process. In the copy dir list (1) you see all directories whose files will be copied to their new location and in the move dir list (2) you see the dirs whose files will be all moved. If you want to change the move- or copy state now then mark one or more directories, right-click and select ‘move instead of copy’ (or vice versa).

Changing copy- to move dirs is ingenious if you then can save disk space (if you got a corresponding warning message before). You are shown the required and available space between the boxes (3), together with a colored rectangle. If the rectangle is green then everything’s ok, if it’s blinking in red then you have too few space left on the target drive (settable in step 8). Then you should transform copy- into move dirs or free up space on the disk where your new collection will be located on or you abort the renaming process and change the output drive (step 8).

Below the move dir list there are two check boxes (4) you’ve already seen in step 8, one defines if (completely) empty source dirs are to be deleted and the other sets if a logfile is created. The preferred chose of the beta testers is to enable both, you should do that, too.

In frame (5) there are the options for the ID3v2.3 TAG writing. As you already know, Toricxs reads in the v1 AND v2 TAG and the file name data and decides which of the three sources will serve as further v1 and v2.3 TAG and as file name (the decision is made for every TAG item, not just for the TAG in general). Between reading and writing, Toricxs will just save TAG data with a max. length of 90 chars. That means ever TAG item’s length is limited to 90 chars (year name: 4 chars), where the v2 TAG items can have (in Toricxs) a length up to 16777215 chars. So it could have happened that e.g. a long song name was for inner use truncated to 90 chars, although the original song name was longer than 90 chars.

If you want to avoid that a long song (artist etc.) name is overwritten by the shortened, but formatted form then select ‘v1 to v2 only if v1 not at max length’. Then an v2 TAG item will only be written if the related formatted v1 form does not have 90 (or originally more than 90) chars.

If you don’t want to overwrite any v2 TAG at all (for what reason ever) then choose the option ‘v1 to v2 for undefined v2 TAG items’, otherwise choose ‘v1 to v2 for all TAG items’ for always overwriting any v2 TAG by the formatted v1 form (which could have originally been the v2 TAG as well).

If a v2 TAG item was not written then you can make it look good anyway through formatting it concerning the options of step 3 (in the same way the TAG data was formatted in step 4). Therefore enable ‘format non-overwritten v2 TAG items’.

Ok that all sounds confusing, but that’s no problem, if you don’t know what to choose then just do it like visible in the screen shot at top of this page.

When having made all settings then confirm beginning the cleaning process through pressing the ‘Ok’-button (6). If there’s too few disk space existing or any other problem appeared then abort the cleaning process through pressing the ‘No’-button (7).