Print

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

[robydago]

Can anyone confirm that when manually changing tags of a stack MC should propagate those changes to *all* files that are stacked together? I mean: tags inside the physical files and not just in the MC db, right?

My MC setup isn't doing that.

In Standard View with List Style set to Details:

• I select two files and I stack them
• MC creates the stack and collapse it so that only the top of the stack file is visible
• While the stack is still not expanded, I change the value of a tag of the stack
• I expand the stack and, as expected, I see that both files have the tag updated to whatever I changed it to in the previous step
• In Windows Explorer, I check the tags inside both files: only the top of the stack file has been actually updated by MC; the other file still has the original tag value.  

Running MC17.0.160 on Windows 7 64-bit

[robydago]

bump

[Alex B]

You are correct. I tested this with a collapsed stack of an audio file in eight different formats. The library data changed in all files, but the file tag changed only in the top file.

I rarely use stacks and I don't know if this is by design or if it is a bug.

[sherbs]

Does it work if you make the changes before stacking and then use Clean File Properties on the stack?

[robydago]

@sherbs

can you clarify better what you mean?

that was a test to check specifically if, by changing a tag on a collapsed stack, MC would change tags on all files in that stack, updating them in both the MC db and inside the actual files.

so, sorry but I don't get the point of making any changes  *before* stacking

[robydago]

@AlexB

Thanks for the confirmation.

I rarely use stacks and I don't know if this is by design or if it is a bug.

Couldn't be by design I guess (at least doesn't make any sense to me)
What is supposed to happen when an import is run afterwards? I tried and, except for the top of the stack file, all changed files in MC are reverted to the "old" tag value (i.e. MC has read the tags form the files and updated the library)

[sherbs]

can you clarify better what you mean?

It's the system I use to transfer tags whenever I update a file to a better version. Just stack the files (with the old one on top) and run Clean File Porperties on the stack. Tags are transferred to the new file and show up in Foobar. Just thought the same might work if you, instead of stacking and then changing the top file, make your changes to what will be the top file, then stack them and run CFP. All the tags in the top file will now be copied to the file underneath.

[robydago]

sherbs,

just tried your trick; it doesn't seem to work in my usage scenario.
I just added a singular trailing character to one tag value in the top of the stack file *before stacking* and it didn't  get replicated to the other file, not even in the MC db, let alone the file itself.

[sherbs]

A bit obvious, but that tag field was checked in the CFP dialog, yes?

[robydago]

Yep, it was selected.

I think that the first time I run CFP while the the stack was expanded.
I just tried with the stack collapsed and MC did change the tag in the "hidden" file.

But still only in the MC db: the file itself has the old tag value and when I
run auto-import in MC, the MC db gets the old value back.