hi!
I've put the wavpack filter to the cool pro directory.
It's saving wavpack files fine : they play OK with winamp.
The problem is when I want to load back the *.wv files in cool pro :
they appear as awful white noise !
Please help !

Are you using the latest filter from here? (it's the Audition filter)

Yes i'm using this one. (I also tried an older version with no luck).
I really don't understand why it doesn't decode wavpack files, although
it encodes them well !

works here ™

There was a problem like this, but it had to do with opening WavPack files by drag/drop instead of opening from the menu, and it was only with pre-4.0 WavPack files. If you are sure that you have cool_wv4.flt installed and that's the one you are saving with (if you have both installed you will see both in the "save as..." dialog), then I'm not sure. You could use the command-line unpacker (with -s) to verify that you are creating version 4 files.

Hope this helps...

OK, you're right ! Works fine on saving and loading 4.0 wavapack files.
This happens with pre-4.0 files used in multitrack *.ses sessions.
Maybe I should convert those old wv files to 4.0 ?

hey, now it works fine even with old (3.0) wavepack !
Something magical happened. It seems that opening just
one file with the menu instead of drap and drop fixed the problem...
Thanks !

Hmm. I wouldn't be too sure about that; I never really figured out what caused it come and go.

If it happens again and your old files are lossless, then it sure wouldn't hurt to convert them to 4.0. Of course, if they're lossy then it might be better to leave them alone.

Anyway, glad you got it going!

I have a problem too with cool pro.
The administrator can use the WV filter.
But the regular user can not.

The file cool_wv4.flt has the same acces rights than tta, flac and other filters of the same kind.

Why ?

The cool folder should be writeable ?

Hm, I have not heard of this problem. The filter does not try to write any files, so I'm not sure what it could be.

I would suggest moving the filter so Cooledit can't find it and running Cooledit (and verifying that it's gone), then move the filter back and run Cooledit again to re-initialize the filter. I have found that this sometimes fixes odd behavior. You might try re-initializing the filter in user mode (or whatever was opposite of what you did before).

I have posted the previous version of the filter here. Perhaps there is something strange about the new version (it's built with VC8 instead of VC6).

BTW, how does it fail? Does WavPack not show up in the pulldown filetype menus, or does the filter fail when trying to load or store files?

Hope something here helps...

David

Thank you very much Bryant!

The problem was that WavPack did not show up in the pulldown filetype menus.
I did just what you said :

1. Admin removes cool_wv4.flt
2. User launches Cooledit
3. User exits Cooledit
4. Admin put back cool_wv4.flt
5. User launches Cooledit and enjoys Wavpack filter !

Thank you very much, you're so smart!

EDIT 2007.2.27 12:57: Thank you for thanking me thanking you

Thanks for letting me know this worked out and I'm glad I could help!