Errors reading WMA tags (1 Viewer)

[Doron]

Thanks hwahrmann. I did not mean to blame MP. By saying that MP does it I did not mean it does it directly.
Is there any way to report Microsoft about this problem?

 

[hwahrmann]

Maybe you can talk to them via the support forum.
but i'm sure there must be tons of similar questions in Windows Media Player forums.

 

[samundsen]

Please note, that nothing has changed in the WMA Tagreader since a while now.
You should see error messages in the Configuration.lg, wheile scanning the db, if something went wrong.
We're using the native COM methods supplied by WMP.

The problem with Monitoring is known.
This has to do with a problem in sqlite, the database executable.
The new version produces this error, we need it however to be Vista compatible.
we need to wait on a new version of sqlite being released.

Just a quick follow up regarding the monitoring problem. Has this been resolved yet? I currently have to rescan for new music manually every time I add a new CD, which is somewhat of a pain.....

 

[hwahrmann]

well, yes and no.
i sometimes still get double entries, but not as much as previously.
so it is not 100% solved yet.

 

[Koudijs]

I discovered that the wma tag problem is caused by MediaPortal.
The good news is that it looks like I have it working now!

In the WmaTag.cs file I removed the Close() calls at line 578, 607 and 614.
These calls caused the exception 0xC00D0018 which means that there was an error writing to the file:

NS_E_FILE_WRITE 0xC00D0018L Error writing to a file.

I also read in the Microsoft documentation that the remaing Flush() calls still take care of closing the file.

With this change I get the tag information in the lower left corner instead of the filename that was displayed previously (see image). This also means that I now get artist and album information on my external display (my main reason for diving into this problem).

As an extra test I changed the attributes of my files to read-only and after that rescanned the database, this worked without problems. So also a read-only network share should work.

Helmut will you take a look at the code and commit the change if you agree with it?


Regards,
Jan

 

[hwahrmann]

Koudijs,

wow. thanks for testing that out.
i'll have a look at it later today and will do the commit, when it works for me.

thanks again,

Helmut

 

[zag2me]

I still dont understand why anyone would actually use this codec but well done for looking at it anyway.

 

[hwahrmann]

I still dont understand why anyone would actually use this codec but well done for looking at it anyway.

me too. This was probably not raisng my motivation for fixing it.
Anyway, it looks like Jan has fixed it.
i've just finished my testing and will commit soon.

 

[hwahrmann]

I also read in the Microsoft documentation that the remaing Flush() calls still take care of closing the file.

hehe very interesting.
the documentation says:
-----
IWMMetadataEditor::Flush
The Flush method closes the open file, saving any changes.
-----

IWMMetadataEditor::Close
The Close method closes the open file without saving any changes.

-----

So i would suspect that the Flush method, which saves changes to the file would cause the Wirite exception, but it is really the Close, which, as per documentation shouldn't write to the file.
Funny.

anyhow the changes are commited.

thx again Jan

 

[Koudijs]

I have ripped 100+ albums in the wma lossless format. I used this format because it was the only lossless format supported by the application I used at that time for streaming my music. Later on I switched to an HTPC with MediaPortal and kept my files. If I had to do it again I would switch to FLAC.