Skip to main content

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: WMPTSE (Read 309736 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

WMPTSE

Reply #275
Quote
- specific WMP11 library
- internal support for album art (including exposition of embedded artwork data in WMP album art)
- write support for MPEG4 tagging (will add month of developpement)


I'll bet you that everyone who's interested in WMPTSE will be on WMP11 almost as soon as it's released.

WMPTSE

Reply #276
Quote


- specific WMP11 library
- internal support for album art (including exposition of embedded artwork data in WMP album art)
- write support for MPEG4 tagging (will add month of developpement)


I'll bet you that everyone who's interested in WMPTSE will be on WMP11 almost as soon as it's released.


Interdemiate results (4 votes):

4 votes - specific WMP11 library
2 votes - internal support for album art
2 votes - ReleasedDate and generally 'date support'
1 vote - write support for MPEG4 tagging
1 vote - AIFF+ID3 support
0 vote - FairPlay tools support
0 vote - iXML support [proposal about to be suppressed]
0 vote - Vorbis write support

I guess i'll have to wait for the WMP11 release before releasing WMPTSE 2.0....

After reading a bunch of documentation on AIFF/iXML tagging, i'm limiting the developpement to specific iTunes AIFF tagging technology. I believe the pro "RIFF chunks"/iXML/BWF part should not be developped freely. When you make money with the work of others, you have to share

I could propose one feature more, but i'm very sceptic about performance issues on this one :
- be able to specify your own Tagging Translation Scheme (the "ALBUMARTIST" => "WM/AlbumArtist" function).

There's two way to properly handle that :
1) let the user free of everything and make it optional (hence the default "inactive option" scheme will be the old one)
2) let the user choose "additional" tagging scheme and always prioritize the 'old' scheme as default "first option"

Is it usefull and are user ready to pay the performance price (dynamic branching replacing static branching), let me know...

Make your opinion count

MaB_fr

WMPTSE

Reply #277
Ok, so after some debugging, i finally found the iTunes 7.x problem...The bug in the MPEG4 parser is now repaired and all files tagged with iTunes should now work.

Also, i've reactivated the "Read tag on browse" handler.

See WMPTSE 1.1.1 :

Website
Direct Download

If it doesn't work, let me know...


MaB_fr

WMPTSE

Reply #278
Ok, so after some debugging, i finally found the iTunes 7.x problem...The bug in the MPEG4 parser is now repaired and all files tagged with iTunes should now work.

MaB_fr
So far, so good... aART is happily parsed now.



WMPTSE

Reply #281
Just tried WMPTagSupportExtender v1.1.1 in WMP 11 final version, on XP Pro sp2 english.
Machine is 2,4 Ghz P4, 2GB RAM.
WMP 11 memory usage is pretty constant around 64 MB.

When adding my ogg files (8000 out of 18000 music files), scanning takes forever.
100% cpu usage for several hours, it's actually not done yet, going on third hour now and only 50% done.
It seems like it is getting slower and slower, like this was a x^2 kind of problem.

I know this plugin isn't native to WMP 11, just wanted to mention it, and say that a native version would be appriciated 

Cheers

WMPTSE

Reply #282
Just tried WMPTagSupportExtender v1.1.1 in WMP 11 final version, on XP Pro sp2 english.
Machine is 2,4 Ghz P4, 2GB RAM.
WMP 11 memory usage is pretty constant around 64 MB.

When adding my ogg files (8000 out of 18000 music files), scanning takes forever.
100% cpu usage for several hours, it's actually not done yet, going on third hour now and only 50% done.
It seems like it is getting slower and slower, like this was a x^2 kind of problem.

I know this plugin isn't native to WMP 11, just wanted to mention it, and say that a native version would be appriciated 

Cheers


As said earlier, always prefer to "Monitor Folders" as opposed to "Scan files" on large amount of WMPTSE compatible files...

No WMP plug-in are "native" (if only i could read the WMP source code....), but WMPTSE is also a HACK.
It means it diverts some WMP features to be able to do is job...
I've choosen a "cpu intensive" hack as opposed to a "memory wasting" one. That's one of my developer choices (i think it's better because it makes monitored folder refreshing smooth...).
Feel free to grab the source and try the other way if you prefers it

Yes, i could develop a WMP11 "new plug-in API" WMPTSE.
But i've not decided yet if i do it or not...

I'm pessimistic about the 'lock-in' possibilities offered for Microsoft in WMP11...(mostly the transcode/rip/sync part)
I'm testing WMP11 release right now, i will make my decision this month...

So be in touch for some news...

MaB_fr

P.S. : on a side note, for those who really prefer to use "Scan Files" (or "Add..." button), you will divide the parsing time by three and more (in fact the browsing is shrinked down from x^2 to ~x) by unchecking the "Add Files previously deleted from Media Library" and the "Add volume leveling values" (not so much overhead less, but less, is less)

WMPTSE

Reply #283
Great tool! I can listen to FLAC files from Media Center now, with tagging support!

One quibble... My FLACs are all tagged with an "Artist" tag (what tag.exe uses), but your parser only (apparently) reads an "Album Artist" field. Could you have it fail over to plain ol' "Artist" if no album artist is listed? Right now the artist is always listed as simply "unknown". Also, Tag.exe stores the year in a "DATE" tag, but I believe that again you are looking for a "YEAR" tag. A fail-over here would also be nice, since a lot of people use tag.exe for flac files.

Should be a simple enough feature request, no?

WMPTSE

Reply #284
Great tool! I can listen to FLAC files from Media Center now, with tagging support!

One quibble... My FLACs are all tagged with an "Artist" tag (what tag.exe uses), but your parser only (apparently) reads an "Album Artist" field. Could you have it fail over to plain ol' "Artist" if no album artist is listed? Right now the artist is always listed as simply "unknown". Also, Tag.exe stores the year in a "DATE" tag, but I believe that again you are looking for a "YEAR" tag. A fail-over here would also be nice, since a lot of people use tag.exe for flac files.

Should be a simple enough feature request, no?


As i am bouddha or may be one of his toes, i will not ask you to re-read the forum thread where we treated these questions already

For your own new user pleasure, i will summarize the issues... 

WMPTSE (so 'I') will not support every non-standard/unspecified/weird/proprietary/alien/non-aristotelician tag politics... It is a proposed 2.0 feature to give users the choice to specify it themself. The specification is not close, so i guess you just vote for one of the submitted features... 

The good thing is you get the source code. So, you're able to modify WMPTSE with the FLAC tag parsing you prefer (if you really need it)...

Maybe i should open a new thread to expose and synthetise the "state of art" about WMPTSE...
Maybe new user could dig this 12 page thread....

I know, i'm lazy too .... 

MaB_fr

P.S. : source upload done...in all flavors

WMPTSE

Reply #285
Well i tried downloading and building your source code, but it won't work (I had to convert to VS2005, if that's the problem). I'm confused as to why there are 3 different solutions... Am I supposed to build them in a certain order? I'm getting:

Code: [Select]
Error    6    fatal error LNK1181: cannot open input file 'c:\Documents.obj'    FLACTagSupport


...when i try to build the TagSupport solution (I assume the TagSupportExtender solution needs the output from this solution... why don't you put them all together?)

Oh well, I guess i'll have to wait for another version then.

WMPTSE

Reply #286
Jebus, my FLAC files with "ARTIST" imports fine into WMP with WMPTSE.  Are you sure it's saying "Unknown"?  All appear under (Contributing) Artist for me, as designed.

Or are you talking about "Album Artist" (WM/AlbumArtist) in WMP?  That's populated using "ALBUMARTIST" tags in FLAC currently.  Remember, Album Artist and Artist aren't the same field.

MaB_fr, I think you might want to populate WM/AlbumArtist with the same entry as Artist if Album Artist tags don't exist... I think that might save some folks time.  I think that's how it works in WMP for WMA and MP3 natively, at least for browsing.  (Maybe I need to re-test this... Hmmm...)

WMPTSE

Reply #287
Well i tried downloading and building your source code, but it won't work (I had to convert to VS2005, if that's the problem). I'm confused as to why there are 3 different solutions... Am I supposed to build them in a certain order? I'm getting:

Code: [Select]
Error    6    fatal error LNK1181: cannot open input file 'c:\Documents.obj'    FLACTagSupport


...when i try to build the TagSupport solution (I assume the TagSupportExtender solution needs the output from this solution... why don't you put them all together?)

Oh well, I guess i'll have to wait for another version then.


If you're interested in WMPTSE development, here is the explanation.
There's different flavor of source because i think there's different needs...

*.src.full.rar -> all the source and project file complete with Plug-in, Tag Support and WMPTSE API Wizard
*.src.build.rar -> only the VS makefile and project solution
*.src.code.rar -> only the source code
*.src.TagSupport.full.rar -> all the TagSupport DLL source and project file

and so on...

TagSupport.full.rar will be what you need if you want to customize the FLAC tag support DLL and its parsing...

With VS 2005 you'll just have to open "/Build/TagSupport.sln". Go directly to the FLAC project. And modify "FLACTagSupport.c" as you want it...

To debug, you'll have to make WMPTSE load the debug dll instead of the installed one (by editing the registry key HKLM\Sofware\piP0ol\WMPTSE\<taggingformat>\<filetypetodebug>)


For the rest, you should try the grommet's questions...

grommet > Conditional populating of different entry will not be a good idea. At least, performance wise...


MaB_fr

WMPTSE

Reply #288
I'm still getting the error:

Code: [Select]
Error    1    fatal error LNK1181: cannot open input file 'c:\Documents.obj'    FLACTagSupport


When I follow those instructions. Sorry, i've never worked with C projects in VS before (only used managed code myself) and I don't know what the problem is.

WMPTSE

Reply #289
I'm still getting the error:

Code: [Select]
Error    1    fatal error LNK1181: cannot open input file 'c:\Documents.obj'    FLACTagSupport


When I follow those instructions. Sorry, i've never worked with C projects in VS before (only used managed code myself) and I don't know what the problem is.


The problem is during the link process. It seems like you've unrared the files in something like "C:\Document and Setting\<Name>" folder (a good guess may be your "My Documents" folder) and the linker does not add the necessary quote to the path. Hence the file to link that should be "C:\Doc and Set\<Name>\Myfile.obj" becomes C:\Doc.obj...

Two solution for this :
1) modify the path to object (.obj) files in the VS project properties (right click on the project, "Properties", then "Linker > Input").
2) change the folder to something "without quote" compliant

I must add, that FLACTagSupport is dependent of libFlac. libFlac is part of the FLAC package and you will find it Here

You'll have to properly compile the library libFlac in "static" mode. And copy the resulting "libFLAC_static.lib" in the source folder "<Where you unrared your files>\Src\FLAC\libFLAC".

Don't forget that you'll need a tiny amount of C knowledge to be able to properly modify the FLACTagSupport.c file...If you never had to modify a C source code before, may be it is not a good idea to do so...

On a completely different subject, I've added a wiki entry about WMPTSE in the HA wiki (i know, i'm not supposed to do so, but if somebody doesn't start, nobody will...). I you have some time to lose, or have the necessary right and want to add some info, you'll find it Here


MaB_fr

WMPTSE

Reply #290

I'm still getting the error:

Code: [Select]
Error    1    fatal error LNK1181: cannot open input file 'c:\Documents.obj'    FLACTagSupport


When I follow those instructions. Sorry, i've never worked with C projects in VS before (only used managed code myself) and I don't know what the problem is.


The problem is during the link process. It seems like you've unrared the files in something like "C:\Document and Setting\<Name>" folder (a good guess may be your "My Documents" folder) and the linker does not add the necessary quote to the path. Hence the file to link that should be "C:\Doc and Set\<Name>\Myfile.obj" becomes C:\Doc.obj...

Two solution for this :
1) modify the path to object (.obj) files in the VS project properties (right click on the project, "Properties", then "Linker > Input").
2) change the folder to something "without quote" compliant

I must add, that FLACTagSupport is dependent of libFlac. libFlac is part of the FLAC package and you will find it Here

You'll have to properly compile the library libFlac in "static" mode. And copy the resulting "libFLAC_static.lib" in the source folder "<Where you unrared your files>\Src\FLAC\libFLAC".

Don't forget that you'll need a tiny amount of C knowledge to be able to properly modify the FLACTagSupport.c file...If you never had to modify a C source code before, may be it is not a good idea to do so...

On a completely different subject, I've added a wiki entry about WMPTSE in the HA wiki (i know, i'm not supposed to do so, but if somebody doesn't start, nobody will...). I you have some time to lose, or have the necessary right and want to add some info, you'll find it Here


MaB_fr


I know C quite well, I've just always written C in Linux so I'm more familiar with makefiles. Already got the modifications I wanted, I just can't compile it! I'll try these tips when I get home - thanks!

WMPTSE

Reply #291
argh... okay I fixed the missing quotes in the linker path, but now I get:

Code: [Select]
Error    2    Command line error D8022 : cannot open 'c:\Documents and Settings\Jeremy\My Documents\Visual Studio 2005\Projects\Build\Release\Temp\RSP00007F17404564.rsp'    cl

WMPTSE

Reply #292
argh... okay I fixed the missing quotes in the linker path, but now I get:

Code: [Select]
Error    2    Command line error D8022 : cannot open 'c:\Documents and Settings\Jeremy\My Documents\Visual Studio 2005\Projects\Build\Release\Temp\RSP00007F17404564.rsp'    cl


Hum....rsp files generation should be a C# compiler only option....
http://msdn2.microsoft.com/en-us/library/8...s6c(VS.80).aspx

Why the hell did the Visual makefile translator wizard activate this...?

You will have to disable it....i do not possess Visual Studio 2005, so i'm not able to show you how to do it, but it should be easy...

Keep me informed...

MaB_fr

WMPTSE

Reply #293
can i confirm that people have this working in WMP11?

i've recently re-installed windows and upgraded to wmp11 this week and just got the latest wmptse as well yet i can't seem to get it to read the tags

i had this trouble with wmp10 but i've checked through the solutions for that and the reg entries already exist

any ideas?

WMPTSE

Reply #294
can i confirm that people have this working in WMP11?

i've recently re-installed windows and upgraded to wmp11 this week and just got the latest wmptse as well yet i can't seem to get it to read the tags

i had this trouble with wmp10 but i've checked through the solutions for that and the reg entries already exist

any ideas?


Aye, working fine here on XP media center edition 2005 with WMP11.

WMPTSE

Reply #295
It's working fine on Vista RTM.

Source builds happily as well (VS 2005) as I've just changed FLACTagSupport to use Artist instead of AlbumArtist. Works a treat.

Now actually playing FLAC files is a different matter as WMP is crashing when using illiminable.

Would love RIFF support for AVI files btw :-)

WMPTSE

Reply #296
It's working fine on Vista RTM.

Source builds happily as well (VS 2005) as I've just changed FLACTagSupport to use Artist instead of AlbumArtist. Works a treat.

Now actually playing FLAC files is a different matter as WMP is crashing when using illiminable.

Would love RIFF support for AVI files btw :-)


So, it will be two for RIFF support...

MaB_fr

WMPTSE

Reply #297
So, it will be two for RIFF support...

MaB_fr


I've been contemplating giving it a go myself using abcAVI to cover off most of it, but my C++ is rather rusty. The original code for this is in Delphi, so it should be possible to just wrap the binary.

I've haven't gone through your code in any detail, but is there anything core about WMPTSE that would need to change to support avi RIFF or does it just need another TagSupport dll?

WMPTSE

Reply #298


So, it will be two for RIFF support...

MaB_fr


I've been contemplating giving it a go myself using abcAVI to cover off most of it, but my C++ is rather rusty. The original code for this is in Delphi, so it should be possible to just wrap the binary.

I've haven't gone through your code in any detail, but is there anything core about WMPTSE that would need to change to support avi RIFF or does it just need another TagSupport dll?


It depends on what do you intend to do with "avi RIFF" chunks...

At this time, WMPTSE handles "text" tag only. You can't have dates, pictures, or anything else...Just simple text.

If it's OK for you, then, yes, a simple Tag Support DLL will be good.
And you don't even need to put a "write tag" code in it if you just need to read the data in the avi file...
Simply left the Write function return TRUE;.

No C++ abillity are needed !!!
Tag support DLL are simple Win32 C only binaries.
No fancy object of my own, no Interface to implement and Manager to register to. A Delphi guy should have no problem with it. Maybe with the exception of pointer handling. But if you write a buggy code which do the trick, it should be no problem to debug it on sight (if it's not too ugly or obsfucated )

Just two function to export, a registry entry and you're good to go...

See The new Wiki documentation to learn more...

I'm here if you need more explanation...

MaB_fr

WMPTSE

Reply #299
anyone got any tips for using this with wmp11?

i seem to have two states of operation

if it recognises the information like album track and artist it takes away my time information and progress bar and still doesn't send the artist info to MSN messenger

but if i turn it off and open/add files then i just get file name but i do get my progress bar and track length

any ideas?