#90 update4114.sql (CVS) causes problems with bladeenc
This may or may not be an issue, it could be caused by
the user (me), but I noticed two things after upgrading
to the latest CVS code today.
1. The database updates included in update4114.sql did
not make it in to my database. All subsequent
updatexxxx files *did* make it -- I checked each and
every one of them manually. I was interested in using
ImageMagick for coverart processing, and found that the
variable I needed is in this file.
2. Looking at the changes in update4114.sql, none of
them seemed to be harmful, so I applied them all to my
database.
3. Shortly after, all my pending rips bombed during
the conversion process. After adding several print
statements, I found the culprit, from update4114.sql:
INSERT INTO settings VALUES ('ENCODEPARAM','Extra
parameter to send to the lame encoder.', 'text',
'--r3mix', 40011);
The parameter --r3mix was being passed to bladeenc, and
bladeenc wasn't too happy about it.
I went to Global administration and deleted this
parameter, which fixed the issue for me.
Issue 1: Why wasn't update4114.sql processed?
Issue 2: The description text in the above parameter
should indicate somehow that if you're not using lame,
this parameter should be blank.
Just getting started with the release version
yesterday, moved to CVS today...
