EAC - Wavpack Guides - Tag Error Options

[flebber]

HI I am reading different guides such as http://wiki.hydrogenaudio.org/index.php?ti...Lossless_Backup

However the EAC command line parameters appear to be incorrect.

CODE

-h -w "Artist=%a" -w "Title=%t" -w "Album=%g" -w "Year=%y" -w "Track=%n" -w "Genre=%m" %s %d

Every time I try and use it it returns a 'Invalid tag replacement' error.

Is anyone using EAC to rip Wavpack? Have you got a work set of command line parameters to use?

[pdq]

Tell us which version of EAC you are using. The parameters have changed.

[flebber]

Tell us which version of EAC you are using. The parameters have changed.

v 1.0 beta 3 I believe that's the latest one.

[DARcode]

http://wiki.hydrogenaudio.org/index.php?ti...#Important_note

[pdq]

It really is time to update the wiki. The important note should instead be saying "This guide is for EAC version x.xx or later. If you have an older version then please update."

[flebber]

So this would be equivalent wavpack line for latest EAC?

CODE

-h -w "%artist%" --tt "%title%" --tl "%albumtitle%" --tg "%genre%" --ty "%year%" --tn "%tracknr%" --tc "%comment%" %source% %dest%

[bryant]

No, I think it would be more like this (but I have not tried it):

CODE

-h -w "Artist=%artist%" -w "Title=%title%" -w "Album=%albumtitle%" -w "Year=%year%" -w "Track=%tracknr%" -w "Genre=%genre%" %source% %dest%

[db1989]

flebber, your latest command-line uses the tagging parameters (except for the %artist%) of LAME, not WavPack. Was there something on the Knowledgebase that confused you and led to this mistake?

bryant’s correction uses the correct format, i.e. the same one as your original command-line. (Of course, he has updated the placeholders to match new versions of EAC.)

Speaking of placeholders: Here’s one I made earlier. Edit: Which I have just added to the two articles linked earlier.

This post has been edited by db1989: Feb 17 2012, 22:23

[flebber]

Thank you when I get home will try. Should I use -hh -l wavpack options if I have the time for the encoding ?

[flebber]

Thank you when I get home will try. Should I use -hh -l wavpack options if I have the time for the encoding ?

Am using

CODE

-hh -l -w "Artist=%artist%" -w "Title=%title%" -w "Album=%albumtitle%" -w "Year=%year%" -w "Track=%tracknr%" -w "Genre=%genre%" %source% %dest%

and it seems to be working well. thanks again.

[DARcode]

[...]Should I use -hh -l wavpack options if I have the time for the encoding ?

If enconding time is not an issue for you I'd strongly suggest to consider the "-x" switch too:

-x[n] = extra encode processing (optional n = 1-6, 1 = default)

Like pre-4.0 versions of WavPack (and many other compressors), WavPack 4.60 normally works "symmetrically" in that encoding and decoding operate at about the same rate (regardless of the mode used). However, WavPack has an option to work "asymmetrically", so that extra processing can be done during encoding to provide better compression, but with NO corresponding cost to decoding performance!

This is enabled with the -x option and provides an average improvement in CD music compression of about 1% in "fast" mode, about 0.5% in the normal mode, and still less in the higher modes. Because the standard compression parameters are optimized for "normal" CD music audio, this option works best with "non-standard" audio (synthesized sounds, non-standard sampling rates, etc.) where it can often achieve enormous gains. The default level (n=1) provides a decent improvement with little cost in encoding speed and is recommended for all but the most time critical encoding. Higher levels provide some marginal improvement with an increasing cost of encoding speed. The highest levels (n = 4-6) are extremely slow but can provide significant improvement in special situations (i.e. synthesized sounds).

From http://www.wavpack.com/wavpack_doc.html#wavpack