Sign In:     

Forum: General Discussion

Topic: FIlter Folders - Complex Operations & Wild Cards - Page: 3

This topic is old and might contain outdated or incorrect information.

If you'd used an actual year in the year field, you could have shortened that to:

year = 1965 and genre contains slow

If you placed the chart position in (e.g.) Field1 then you could simply sort the listed results by clicking the top of the Field1 column.

You don't even necessarily have to create a filter folder. For instance I can simply type in 1965 ballad to the search box and bring up anything from 1965 that I've tagged as a ballad.

If I had added the text "top10" to the tags of any songs that reached 10-1, then a search for 1965 top10 would display them.
 
Mr. GroovinDJ: I appreciate your advice and help, however telling me over and over now what I should've done before there were such things as tagging, is not a productive approach.

I get it.

I'm different.

Thank you.
 
Cap Capello wrote :
Thanks for all the reads and comments. No umbrage of any was taken even though a couple did get a little personal. While I am just one person, perhaps consider that I am the only person who has brought it to the forefront for exactly the reasons shot at me.

Losing historical data since version 3.0 will be the sacrifice if a collection wide renaming is needed. Losing queue points is at the bottom of the priority list.


Not so for many users who face this challenge,

I've also looked into this issue a while back and know this is a big problem not only for you, but everyone else, myself included who may need to update many file names for what ever reason, this holds true no matter how small the change in the file name is..

My point was to engage in this conversation relating to this one core issue which is how can we update many file names without losing file database information, I've made a suggestion that will meet this challenge, lets hope the AotoMix Gods are listening...
 
You got it, Joey. I'm with you, at least with moral support, being way behind you in understanding the "what if's" just yet.

Thank you for your input.
 
Cap Capello wrote :

How simple is adding a wild card feature? Do we know of any other search program that doesn't employ wild cards? I'm not complaining. It is what it is... it just could be better..


As was mentioned, even the VIP members dont know exactly whats going to be included in VDJ 8,
having wildcards might be on the books, it might not..

the good news, its amazing how many suggestions from users having ended up being incorporated in the program..
I was just browsing last week a very old thread where I was specifically asking for a bunch of features I wanted to see incorporated.. I was actually a little shocked when I realized EVERY SINGLE ONE of those wishes had been incorporated!

the bad news.. some of those "wishes" took only months, some took YEARS..

but here is the process :-)

first.. if you want any new features added, you must first post in the "wishes" forum..
http://www.virtualdj.com/forums/155084/Wishes_and_new_features/Browser_related_wishes_and_new_features.html

2nd.. if your idea is super awesome, it might just take off on its own.. Myself I used to try and get others 'on board' with the idea, explaining to them how they too would benefit from it..

3rd.. the "wishes" are not ignored but how they are 'prioritized' depends on how easy they are to implement and # of users that want it.. IE: sometimes you just gotta be patient :-)
(and sometimes you get pleasantly surprised)
 
Thanks for the link, Hippydog. Just went out on the ledge and posted a requested feature.
 
This should do what you want for your example:

genre is "old skool" and extension is "mp4" and (year > 8000 and year< 9000) and (year ends with "01" or year ends with "02" or year ends with "03" or year ends with "04" or year ends with "05" or year ends with "06" or year ends with "07" or year ends with "08" or year ends with "09")

Too bad there is no 'modulus' (i.e., '%') operator for the year or else it could be simplified as:

genre is "old skool" and extension is "mp4" and (year > 8000 and year< 9000) and (year % 100 < 10)

Hope this helps,
-Frd
 
Cap Capello wrote :
OOPS. Spoke a bit too soon. Question. How would I do a filter folder for only songs which reached 01 regardless of the year?


Hmmm... The first problem was easy to solve, but this becomes more complicated and for once I'm with you on this ;-)

Looking at the filter folder page in the wiki http://www.virtualdj.com/wiki/FilterExamples.html I noticed that the track number was not a supported verb.

As you don't use the track number in your nomenclature, this would have been ideal...

A few of us have campaigned for disk number to also be recognised by the database - mainly for karaoke, so here's to hoping that disc makes it in to v8 for the database and track and disk make it in to the filter folder verb list.

Cheers,

Roy
 
GadgetMan wrote :
A few of us have campaigned for disk number to also be recognised by the database - mainly for karaoke, so here's to hoping that disc makes it in to v8 for the database and track and disk make it in to the filter folder verb list.

Cheers,

Roy


Hey Roy, you can use the "composer" field for karaoke Mfg right now..
 
Cap Capello wrote :
OOPS. Spoke a bit too soon. Question. How would I do a filter folder for only songs which reached 01 regardless of the year?


That's even easier:

year ends with "01"
 
FRD1963 : Thank you for your examples. Unfortunately the first and primary one:

Quote :
genre is "old skool" and extension is "mp4" and (year > 8000 and year< 9000) and (year ends with "01" or year ends with "02" or year ends with "03" or year ends with "04" or year ends with "05" or year ends with "06" or year ends with "07" or year ends with "08" or year ends with "09")


doesn't get by the syntax window. I think in the year field, it must begin with a 1 or a 2.

I see where you're going with this and I'm going to play a bit with it to see if, by some stroke of incredible dumb luck, the syntax issue is located.

Unfortunately with the way the syntax window is presented, if there are two errors, you'll never know which it is without major trial and error. Three errors? Fuggedaboutit!
 
The parser must be assuming year to start with a 1 or 2 which makes sense if it's going to be strictly used as a year, but probably doesn't add much value except for slightly less memory consumption (store 1 byte vs 2 bytes per song in memory.)
I didn't actually try this but will tonight and see, instead of guessing. I like challenges like this, so rest assured we will figure something out ;)
 
Thank you for taking the challenge.

To give you an idea of my level of expertise, what's a parser and how many volts does it take?
 
FRD1963 : Any luck?
 
Bumpiddy-bump!
 
Apparently now a dead thread. Done checking in on this. Anyone with ideas or additional help thoughts:

capcapello@gmail.com.

Thanks to all for great ideas.
 
I have completely resolved the issue by assigning YEAR data into COMMENT field. Now I can have oodles of data without restriction.

For example, a country song missed hitting the pop charts but hit the top 10 in country.

So, in the comment field, it's 8809cw , meaning in 1988 it reached #9 on the country charts. The year field has been completely discarded.

SUCCESS for what I want.
 


(Old topics and forums are automatically closed)