just to complete and perhaps this is helpful.
Just tested in a different way. Usually I am using my folders to navigate through my collection. The whole issue seems to be dependent to this view. When I use the interpret-Album view from the database then it does not appear. Probably that's what the difference of what I am doing. And again, this is only happens with wma files.
looxer
Back to MM2 - WMA Tagging issue [FIXED via MS Update]
Moderator: Gurus
-
kugel.
Database not updated in My Computer view
Looxer,
Now I understand! The problem is that when updating tracks in the My Computer node, the DB isn't updated if the tracks happen to be in the DB.
Thx for the clarification (and yes--this is common to all formats, but doesn't mean that we won't be looking at any tagging issues with a particular format that are covered in another thread).
-Rusty
Now I understand! The problem is that when updating tracks in the My Computer node, the DB isn't updated if the tracks happen to be in the DB.
Thx for the clarification (and yes--this is common to all formats, but doesn't mean that we won't be looking at any tagging issues with a particular format that are covered in another thread).
-Rusty
Database not updated in My Computer View
After internal discussions, we've concluded that the current behaviour makes the most sense. The reason being:
-The My Computer node displays only Tagged information (not info from the DB)
-If we changed the behavior to trigger a db update, the user performing edits via this node will end up modifying fields that they cannot even see.
-If you still prefer that behavior (for the DB to be updated based on info in the tag) in response to such changes, you can just enable the File Monitor for the folder in question.
-Alternatively, you can use the Locations node to modify tracks that are in the db.
I'm open to feedback on this, so please comment if you have opinions one way or the other.
-Rusty
-The My Computer node displays only Tagged information (not info from the DB)
-If we changed the behavior to trigger a db update, the user performing edits via this node will end up modifying fields that they cannot even see.
-If you still prefer that behavior (for the DB to be updated based on info in the tag) in response to such changes, you can just enable the File Monitor for the folder in question.
-Alternatively, you can use the Locations node to modify tracks that are in the db.
I'm open to feedback on this, so please comment if you have opinions one way or the other.
-Rusty
-
looxer
Back to MM2
Hi Rusty,
thank you for your response and discussing the issue.
First of all I would like to say that this behavior is new in MM3. It really works differently in MM2 - for me in MM2 as expected.
When I add new albums I usually load them into a temporary folder. This way I can very easy locate the new ones.
When I have loaded -lets they 2 new albums- then I start to tag them. That's why I do this in my documents without file monitor. It would take a while until the file monitor would really add them to the db. Thus I would not do this in any other folder.
Once I have tagged the new albums I use to copy them to my library. From here on I could use the locations node but unfortunately not for the temporary folder as this is a great way to organize new albums. (unless I wanted to wait until the file monitor would have added the new albums)
I understand that my problem and the way how I organize my music is not a common way but everybody who uses the "my documents" folder for tagging would be very confused.
Honestly I do not understand why this "works as designed". ( Iam from the software industry and sometimes I am in similar discussions with my customers) So it might have internal reasons for you guys but it is definitely not what a user would expect.
thank you for your response and discussing the issue.
First of all I would like to say that this behavior is new in MM3. It really works differently in MM2 - for me in MM2 as expected.
When I add new albums I usually load them into a temporary folder. This way I can very easy locate the new ones.
When I have loaded -lets they 2 new albums- then I start to tag them. That's why I do this in my documents without file monitor. It would take a while until the file monitor would really add them to the db. Thus I would not do this in any other folder.
Once I have tagged the new albums I use to copy them to my library. From here on I could use the locations node but unfortunately not for the temporary folder as this is a great way to organize new albums. (unless I wanted to wait until the file monitor would have added the new albums)
I understand that my problem and the way how I organize my music is not a common way but everybody who uses the "my documents" folder for tagging would be very confused.
Honestly I do not understand why this "works as designed". ( Iam from the software industry and sometimes I am in similar discussions with my customers) So it might have internal reasons for you guys but it is definitely not what a user would expect.
-
looxer
Back to MM2
one more question:
if it works as designed why is it then working for MP3s but not for WMAs ? this is confusing me as well.
if it works as designed why is it then working for MP3s but not for WMAs ? this is confusing me as well.
mp3 vs wma
looxer,
My experience is that this works identically for MP3 and WMA tracks or any other format.
note: we probably won't change this for 3.0, but I'm listening to what you and other customers are telling us. If this is the wrong decision, we'll change it.
-Rusty
My experience is that this works identically for MP3 and WMA tracks or any other format.
note: we probably won't change this for 3.0, but I'm listening to what you and other customers are telling us. If this is the wrong decision, we'll change it.
-Rusty
-
looxer
Back to MM2
Rusty,
it's strange. When I go via "My Computer" navigate to any mp3 or ogg I can change i.e. the titel field. Go to a different node come back and I still see the change.
If I do the same thing with a wma track the change is gone. (When I then go into properties I can see the change as described above)
it's strange. When I go via "My Computer" navigate to any mp3 or ogg I can change i.e. the titel field. Go to a different node come back and I still see the change.
If I do the same thing with a wma track the change is gone. (When I then go into properties I can see the change as described above)
'My Computer' misinformation
Upon further investigation, I'm guilty of providing some misinformation here. The code actually does what you think it should do. i.e.
1. My Computer node shows track values as they are stored in tags, DB isn't taken into account.
2. However, when Edits to tracks via the My Computer node (either in Properties dialog or in-place edits) are done, the Properties of a particular track are read from DB and shown, and the changes are confirmed, both the Tags and the DB are updated.
So the only question is why isn't this happening to WMA tracks in your case (on my machine this is what is occuring).
-Rusty
1. My Computer node shows track values as they are stored in tags, DB isn't taken into account.
2. However, when Edits to tracks via the My Computer node (either in Properties dialog or in-place edits) are done, the Properties of a particular track are read from DB and shown, and the changes are confirmed, both the Tags and the DB are updated.
So the only question is why isn't this happening to WMA tracks in your case (on my machine this is what is occuring).
-Rusty
-
looxer
Back to MM2
what can I do to prove this ?
I have tried to be very certain about the issue and converted an ogg file into a wma track.
When I change the new wma track (i.e. title) the same issue occurs.
One more thing I found out:
When I have changed a field goto another node come back the change is not visible in the list. But when I press delete the usual pop up comes up "Do you really want to...." At this point I can see the changes I have made.
I can repeat this at any time.
I have tried to be very certain about the issue and converted an ogg file into a wma track.
When I change the new wma track (i.e. title) the same issue occurs.
One more thing I found out:
When I have changed a field goto another node come back the change is not visible in the list. But when I press delete the usual pop up comes up "Do you really want to...." At this point I can see the changes I have made.
I can repeat this at any time.
WMA Tagging problem
Looxer,
Perhaps try:
1) Recording a screencast of you triggering the problem. Perhaps this will reveal something that I'm overlooking or not understanding correctly (fyi, I use the free app 'camstudio' for this).
2) Record the exact same set of steps with MM 2.0 and show the problem not occurring.
Please do it asap so that if a fix is needed, we can get it into RC6. Thx.
-Rusty
Perhaps try:
1) Recording a screencast of you triggering the problem. Perhaps this will reveal something that I'm overlooking or not understanding correctly (fyi, I use the free app 'camstudio' for this).
2) Record the exact same set of steps with MM 2.0 and show the problem not occurring.
Please do it asap so that if a fix is needed, we can get it into RC6. Thx.
-Rusty
-
looxer
Back to MM2
Hi Rusty,
thx for the proposal. I will first record the issue with MM3. I have deinstalled MM2 at the moment. Believe me it works there. If you really would like to see I can install it once again. just a bit of work.
I will send the avi-file to support@mediamonkey.com - correct ?
looxer
thx for the proposal. I will first record the issue with MM3. I have deinstalled MM2 at the moment. Believe me it works there. If you really would like to see I can install it once again. just a bit of work.
I will send the avi-file to support@mediamonkey.com - correct ?
looxer
WMA Tagging problem
According to looxer, this issue was resolved once Windows Media Components were refreshed via:
http://www.mediamonkey.com/sw/WMFDist11 ... 86-ENU.exe
-Rusty
http://www.mediamonkey.com/sw/WMFDist11 ... 86-ENU.exe
-Rusty
-
looxer
WMA Tagging Problem
confirmed.
everything works as it should. It was a surprise as the tagging issue did not occur in MM2.
Thank you very much for the big help
looxer
everything works as it should. It was a surprise as the tagging issue did not occur in MM2.
Thank you very much for the big help
looxer