Print

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

[mark_h]

I have a smartlist which show duplicate tracks in my library based around:

~dup=[artist],[name]

and a bunch of other rules.

But one thing this doesn't handle is artists with articles, eg "The Hollies" and "Hollies".  I'd like to catch duplicate tracks and handle missing articles.  So I created calculated fields to remove articles, eg

~dup=[artist (no articles)],[name (no articles)]

I am allowed to create the smartilist (although I am forced to restart MC in order for the wizard to see the calculated fields after I create them) but it doesn't function as expected and returns lots of nonsense data.

So it seems ~dup doesn't work with calculated fields?

Mark

[Matt]

We'll take a look.  I can't think of any reason why it wouldn't work.

[eba]

I've just done a quick test on this as I have quite a few custom audio fields, both calculated and non calculated.

From what I can see it appears it doesn't like fields with parentheses.

i.e. I have a field called Song Name (Auto), which contains exactly the same as the standard Name field.
Creating a smartlist to show the dupes of this doesn't work, whereas the standard name field does.
I tried creating a field called TestName, with the same formula as Song Name (Auto), and this did work.

It doesn't work with fields with parentheses regardless of whether it is a calculated or user data field.

It does however work with any fields from the search box...

Hope that helps
Ben.

[Matt]

Try putting a slash (/) in front of the parenthesis.  You need to "escape" some search characters since they have special meaning otherwise.

[eba]

Am just using the Smartlist wizard to do it, so have no choice as to putting escape characters in (is there a way to do smartlists manually?), but it appears to be doing so as it sets the Notes complete with / before each parenthesis.

Actually the escape characters seem to be the problem as with the search box I do it manually and don't include them, and it works.  If I use the search wizard however it puts / before each parenthesis and doesn't work.

EDIT: I think the need to escape characters doesn't apply within a field name?  But the wizard seems to put them in anyway, thus causing the problem.

[mark_h]

Removing the parentheses works for me too!

Mark