Bugzilla – Bug 10382
Possible changes to convert.conf
Last modified: 2009-06-17 09:36:02 UTC
From bug 10335. Steven said: Looks to me like a couple of the lines in convert.conf can be cleaned up. I suggest the following: Change: mov mp3 * * # FRB:{BITRATE=-B %B} [mov123] $FILE$ | [lame] --resample 44100 --silent -q $QUALITY$ $RESAMPLE$-v $BITRATE$ -r --big-endian - - To: mov mp3 * * # FRB:{BITRATE=-B %B}D:{RESAMPLE=--resample %D} [mov123] $FILE$ | [lame] --silent -q $QUALITY$ $RESAMPLE$ -v $BITRATE$ -r --big-endian - - Change: ape mp3 * * # FB:{BITRATE=-B %B}D:{RESAMPLE=--resample %D} [mac] $FILE$ - -d | [lame] --resample 44100 $-x$ --silent -q $QUALITY$ $RESAMPLE$ -v $BITRATE$ - - To: # FB:{BITRATE=-B %B}D:{RESAMPLE=--resample %D} [mac] $FILE$ - -d | [lame] --silent -q $QUALITY$ $RESAMPLE$ -v $BITRATE$ - - Alan, what do you think?
Since LAME produces 128kbps CBR mp3 by default, I would suggest the following would be more consistent: BITRATE=-v -B %B A couple others: I would suggest using the long versions of all Flac options, which are more self-documenting. Instead of -dcs use --decode --stdout --silent (or --totally-silent) There are a number of redundant -s (--silent) options used along with --totally-silent. For example wma flc * * # F:{PATH=%f}R:{PATH=%F} [wmadec] -w $PATH$ | [flac] -cs --totally-silent --compression-level-0 - In this case -cs means "--stdout --silent", but --totally-silent supersedes the --silent option. So all the "-cs --totally-silent" could be changed to: --stdout --totally-silent Another inconsistency with respect to Flac options, is the use of = signs for option values: flc wav * * # FT:{START=--skip=%t}U:{END=--until=%v} [flac] -dcs --force-raw-format --endian=little --sign=signed $START$ $END$ -- $FILE$ vs.: mov flc * * # FR [mov123] $FILE$ | [flac] -cs --totally-silent --compression-level-0 --endian big --sign signed --channels 2 --bps 16 --sample-rate 44100 -
I have fixed up the mov mp3 rule in a slightly different way. I do not really know what to do with the ape mp3 one.
Fixed in other changes for 7.3.2 and 7.4
Verified fixed with SqueezeCenter Version: 7.3.3 - 26228
This bug has been fixed in the 7.3.3 release version of SqueezeCenter! If you haven't already. please download the new version from http://www.logitechsqueezebox.com/support/download-squeezecenter.html If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.