I have read on the WavPack site, that WavPack accepts wildcards... I would like to know if it also applyes for tagging ? In fb2k CLIencoder i tryed to encode an image file with this command line and it didn't work :
-h -m -w "cuesheet=@*.cue" -w "log=@*.log" - %d
Unfortunately, WavPack will not (as you found) accept wildcards in the tag file fields. It probably would not be that hard to put in; I'll consider it for 4.3 (of course, it will have to abort with an error if more than one file match the wildcard).
Nice idea. Could be very useful for transcoding. If it's easy/bloat-free to implement it's got my vote.
I only discovered recently that Diskwriter (or Converter) won't process TAGZ in the command line. Otherwise, until WavPack 4.3 (if implemented), you could have used something like:
-w "CUESHEET=@$substr(%_path%,1,$strrchr(%_path%,\))CDImage.wv.cue" -w "LOG=@$substr(%_path%,1,$strrchr(%_path%,\))$replace(%album%,\, ,/, ,<, ,>, ,:, ,*, ,?, ,", ,|, ).log"
With regard to using "@*.<ext>": Wouldn't that potentially, under normal/current conventions, look for a file in the same folder as WavPack? I guess it would have to be implemented so that the path to the source would be used as the folder to search? Something to consider (as if you haven't already!).
Another reason is that bryant seems like a really nice guy, and really seems to care about his users...
I agree. One of the various reasons I intend to switch to WavPack (when I get my external hard drive which should be in the next month or so) is David's active participation and respose to users' requests . That said, I hope you're not insinuating that Josh is an uncaring b*stard?