Here is what I have done to fix my issue, I deleted everything in 3 of my 4 collections and I have had to re-add them to get the rules to work.

I don't understand why the rules wouldnt work on "watched" folders.

Seems rules only work on in-coming new files.

Interesting.

If I want to add something new... I go to file add/rescan files.

As far as collections, I should be able to drag and drop from one collection to the next but it seems I cant. I put in a feature request in that forum, not sure if that will happen or not.

So, say you have some tracks you want to add to H:\, when you add them,
do you add them in various ways: ripping, right-click add/scan, outside, etc to just "H:\' or "H:\Users\"user1"\Music\<Album Artist>\(<Year>) <Album>\<Artist> - <Album> - <Track#> - <Title>" ?

If there was a way to "turn on" a newly created rule and have it run against a directory that would be great!!

It seems new rules only work against files that are added to a directory after that rule is created. Please correct me if I am wrong but thats how it seems rules work.

To solve this, it would be great to have a command to allow that rule to be run against said directory or collection after the rule is created.

Again, maybe I am naive and I havent figured it out... but for the life of me I cannot figure out how to run a new rule against something thats already in the library.

What I have had to do is remove my files from my library and create the rule, then add them back into the collection/library. This seems VERY clunky

Hey guys!

So MMFrLife helped me set up my collections based on different directories so that they dont cross-pollinate. I have now have 4 individual collections in discreet silos for lack of a better phrase. (HUGE Thanks to MMFrLife!!)

What I am curious about now is how to set up auto-organize rules for each directory?

I have the rules set up for the way I want them but they arent "auto-organizing" anything.

Here is how I have the rules set up: C:\Users\"user1"\Music\<Album Artist>\(<Year>) <Album>\<Artist> - <Album> - <Track#> - <Title> (note... "user1" edited so no names show)

I have each subsequent rule set up but changed the directory per user.

I also have each directory being "watched" and "scan at start-up". Yet, when it scans at startup it doesn't organize... it just scans.

I do not want the rules to create any cross over into any of the other collections and I want everything to stay discreet or each "silo" as it were. In other words, I do NOT want anything from my "H" collection to show up n my "C" collection and so on.

I am happy to take screenshots if someone can teach me how to post them if necessary?

In the end, I want the program to work in the background like it used to in "MY MUSIC" before I created the other 3 collections to where it organized based on the rule above. I have had that rule in place for about the past 5 years. However since i had t change my music collection to be based on a directory verses the "out of the box" objects that MMonkey sets it up using when installing (my music) etc.

Any and ALL help would be greatly appreciated!

MMFrLife wrote:Are you trying to add to C:\ inside MM (My Computer node) or outside of MM?

I went into "C"'s collection and went to file/ "add/re-scan" and went to a folder that is covered in the "H" collection and tried to add it to my "C" collection. I am not trying to drag/drop from one to the other if that's what you mean... it wont let me.

MMFrLife wrote:So, you changed C:\'s collection Value to C:\My Music?

Yes I changed C:\'s collection value to C:\My Music. That is what I had to change to make the "H" not cross pollinate into "C"'s collection. I wonder if change it back, will I be able to add/re-scan a folder in another collection to make it add to the "C"?

I let it run all night and I now have about 48K files in my "C" collection (which is what it was and that's good) I also now have about 46K files in my "H" collection which did not cross-pollinate into "C"!!

To answer your earlier question about options for rules, the first option I can use is by collection so I think it will keep "silos" for each collection per rule. I am going to have 4 collections by the time this is all done. I have 2 other collections to populate before I start to figure out the auto-organize rules/watch folders.

I also have found out that the "entire library" node is awesome!! I can sort by anything I want to see my 2 collections (so far) populated. So so so so awesome!!

Hdhntr23 wrote:When I try to add files to my main C collection they do NOT get added. What Ive done is changed the main C collection from all of the criteria that comes "stock" and changed it to see only the C criteria like you had me set up the other collection.

Are you trying to add to C:\ inside MM (My Computer node) or outside of MM?
So, you changed C:\'s collection Value to C:\My Music?

Im not necessarily worried about rules right now, Im mostly worried about getting these files into my dbase. Once I have that completed I will worry about rules/auto-org.

In meantime here is my latest update.

I have created several collections and files are able to be brought into a specific collection by itself without going into my MAIN collection on drive C

HOWEVER...

When I try to add files to my main C collection they do NOT get added.

Weird stuff.

What Ive done is changed the main C collection from all of the criteria that comes "stock" and changed it to see only the C criteria like you had me set up the other collection.

This is maddening but I do think I or WE have made serious progress I just need to figure out the C issue now.

Thoughts?

Do you have auto-org rule something like

check collection - "hyz"
H:\xyz\<Album Artist>\<Track#> <Title>.<Extension>

Maybe someone else can help, but I think, to do what you want, there first needs to be something unique about the files you want to isolate to "H".
I'm not sure, but I don't think you can move by rule, "path identified" files, to more that one place at a time; at least, I don't think so initially.

Right so... its adding the songs to BOTH the C and the H collections.

Sigh.

Should I set up my "C" collection the same way? Have it point only to my music on C vs all of the other criteria its set to? Is THAT the problem now that I have added the "H" collection? Is that why C is picking up the H stuff now?

Thanks

Now that its working, I wonder what's going to happen once I turn the auto-org rules back on?

I wonder if they will work for each collection as I have them set up?

I rules set up for each collection to sort by album artist... Ill spare you the rules but I have them set up per collection. I wonder when I turn them will they start to work as they should again.

Same question goes for "watching" folders... wonder what happens when I turn those back on?

Guess we will find out!

Hdhntr23 wrote:I just did a test without my auto org rules just now and did another test and it worked!!

Glad it Worked ! The tree nodes don't determine whether it would work right or not.
As long as the collection is configured properly and your adding the files to the "proper" target, you should be able to add the files
by Add or Auto-Org rules and have them show up by themselves and not with other files from other locations.

New collection is setup as follows:

I have it set to match ALL of the following criteria:

property: path/filename
condition: contains
value: (H:\"xyz")

tree nodes: (although I have a strong feeling this doesnt matter)
location
title
artist and album artist
album artist
album
genre
year
files to edit

I just did a test without my auto org rules just now and did another test and it worked!!

Hdhntr23 wrote:Hahahah yes Mmrflife!

1) "in" the new collection
2) file/add-rescan files
3) pulled from new "H" directory that the collection is pointing to as you mentioned above
4) went and opened the "C" collection and noticed the folder that I just brought in had come into C/my music

Make sure you are scanning to the "H" target.
Can you provide the complete path of the "H" folder target and the "My Music" path?
Also, show the criteria you used in the "H" path collection.

Hahahah yes Mmrflife!

1) "in" the new collection
2) file/add-rescan files
3) pulled from new "H" directory that the collection is pointing to as you mentioned above
4) went and opened the "C" collection and noticed the folder that I just brought in had come into C/my music

New collection is setup as follows:

I have it set to match ALL of the following criteria:

property: path/filename
condition: contains
value: (H:\"xyz")

tree nodes: (although I have a strong feeling this doesnt matter)
location
title
artist and album artist
album artist
album
genre
year
files to edit