nynaevelan wrote:I don't think I would be the best person to write up an explanation since I am not 100% sure what I am doing.
Maybe my description was not very clear, so here is one example. Let say that I selected some tree node and as a result I got the tracklist with 10 tracks. After that I unselected all tracks in the tracklist and entered the RegExp dialog box. Let say that I choose some preset which could modify 3 tracks of those 10. Now, I have two possibilities:
1. if I choose Select to replace
, after closing RegExp dialog box I would get the tracklist which will contain 10 visible tracks and 3 of them will be selected;
2. if I choose Keep to replace
, after closing dialog box I would get the tracklist which will contain only 3 tracks, those which content needs to be replaced - other 7 tracks will be removed from the tracklist.
If you need some better explanation, please let me know.
nynaevelan wrote:It's not too bad because the user has the option to get rid of presets which he/she would not be using.
Yeah, you are right - I could add them some more and users could remove unwanted presets, but I still don't know what could be useful for users, so please give me some idea and tell me what you want to see with the next version.
nynaevelan wrote:I tried looking at one of the tutorials but it was all a foreign language to me.
Yes, I know, it was same to me. But, you don't need to use all RegExp possibilities from the begin. You could learn step by step, from simplest one to the more difficult. Here is a simplest example: if you want to find all artist which contain prefixes The, A and An, you should write The|A|An
(note the character "|" between options). Now, if you want to find all artists which contain mentioned prefixes, but only if they are on the begin of the artist name, you should add the character "^" on the begin of the expression, like this ^(The|A|An)
(in this case you need to enclose those options, i.e. prefixes within braces). Isn't that so nice? With just few characters you could find exactly all what you want with a single step.
By the way, I've got your file, thank you very much. There is a SQLite error with it "Expression tree is too large (maximum depth 1000)" which is obviously a consequence of too many selected tracks. Well, in fact it is consequence of too many tracks which would not be modified, especially when there is a random order between them (ideally, they should be consecutive as much as possible to be able for script to use fewer BETWEEN keywords). I could try to resolve this, but I think it would slow down an execution of this option (Select to replace
). Thanks again.