Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[risingdamp]

I have this rule in a view scheme:

Code: [Select]

-[MD5TextHash]=[] ~dup=[MD5TextHash] [Duplicate]=[]
I always thought that modifiers (like dup) were executed in order in a VS rule.  This means that the 'dup' modifier should be executed first.  I'm expecting the above to find all tracks where there are duplicated MD5TextHash values and then from that list remove any where my custom field called duplicate is not blank.  However, it appears to be executing the ~dup modifier after removing files where Duplicate=blank.

Is this a bug?

[Matt]

Post-processors (things that start with a ~) are executed after search tokens. (in the order they appear in the string)

[risingdamp]

Thanks.  That explains it.  I guess I'll just have to include [Duplicate] as an item in the scheme and then select 'unassigned' each time.  Unless there's another way?