[...]Note that this does not allow editing the metadata tags directly from winamp (alt+3) unless there's a plugin that implements this through that API.[...]

Quote from: bryant on 2007-11-19 02:41:47

[...]Note that this does not allow editing the metadata tags directly from winamp (alt+3) unless there's a plugin that implements this through that API.[...]

Benski, one of you WA guys mabbe?

extern "C"
{
    // return 1 if you want winamp to show it's own file info dialogue, 0 if you want to show your own (via In_Module.InfoBox)
    // if returning 1, remember to implement winampGetExtendedFileInfo("formatinformation")!
    __declspec(dllexport) int winampUseUnifiedFileInfoDlg(const wchar_t * fn)
    {
        return 1;
    }
}

I'm not sure exactly what this buys (other than the ability to write calculated Replaygain info, which is how I tested it) but I'm sure there are plugins that do this.

Add this block of code somewhere in your program.  It will cause Winamp 5.5+ to do tag editing through your plugin's metadata interface.

Code: [Select]

extern "C"
{
    // return 1 if you want winamp to show it's own file info dialogue, 0 if you want to show your own (via In_Module.InfoBox)
    // if returning 1, remember to implement winampGetExtendedFileInfo("formatinformation")!
    __declspec(dllexport) int winampUseUnifiedFileInfoDlg(const wchar_t * fn)
    {
        return 1;
    }
}

Quote from: bryant on 2007-11-19 02:41:47

I'm not sure exactly what this buys (other than the ability to write calculated Replaygain info, which is how I tested it) but I'm sure there are plugins that do this.

It buys you two features:
1) Ctrl+E metadata editing in the media library will sync up changes to the file
2) The Auto-tagger included in 5.5+ will write back to the tags (auto-tagger also requires the "extended read" API which you've already implemented).

Maybe a few other things, but nothing I can think of off the top of my head.

[...]
Now, DARcode, you can edit your tags in winamp!! 
David

The updated version is here:

http://www.wavpack.com/winamp_alpha6.zip

the option "use correction files" in plugin configuration is used both in playback and transcoding. It makes sense to split them - i.e. do not use wvc-files during playback but do use in time of format conversion

just want to remind that the performance issue with access to files stored on Windows network shared folders is still there. Previously it affected just Medialy Library re-scan. With new features it appears in new places
1) "file info" dialog with track metadata takes about 5-10 seconds to open
2) format conversion is slowed about twice

thanks

Quote from: mkuzmin on 2007-12-07 18:00:15

just want to remind that the performance issue with access to files stored on Windows network shared folders is still there. Previously it affected just Medialy Library re-scan. With new features it appears in new places
1) "file info" dialog with track metadata takes about 5-10 seconds to open
2) format conversion is slowed about twice

thanks

Okay, I think I know what's going on here. Winamp does quite a bit of metadata reading on the same file, and I think some of the plugins keep the last file open so they can retrieve the information more quickly. I'm rather swamped right now, but I might be able to try this in the next week or two.

Thanks for letting me know about this. 

[...]2 benski: is it possible to include wavpack plugin to future winamp versions as a standard component ?

Well, it turns out I had time to try something on this today! This should perform media library operations much faster than before, and I also changed the transcoding API to always use correction files. This involved changes that could potentially lead to nasty bugs, so (as usual) all testing is appreciated. Thanks! 

Quote from: bryant on 2007-12-10 03:24:31

Well, it turns out I had time to try something on this today! This should perform media library operations much faster than before, and I also changed the transcoding API to always use correction files. This involved changes that could potentially lead to nasty bugs, so (as usual) all testing is appreciated. Thanks! 

Thanks a lot! Everything works fine so far.
Your dedication and speed of response is really amazing!

Hi bryant
When will you release the final version?

Thanks bryant.
Please place the latest version in the first post.