Bugzilla – Bug 358
WMA transcoding selection isn't sticky
Last modified: 2011-03-16 04:39:09 UTC
If the server doesn't find the wmadec program on the server machine during startup, WMA decoding is turned off in File Types, even though it was turned on when the server was last running. Linux doesn't have wmadec, and my WMA rules are overridden in slimserver-convert.conf (using ffmpeg). Apparently, the decision to turn WMA transcoding off happens before the alternative *-convert.conf files are read.
Kevin, is this not dealt with in your checkin for bug 343? Seems like moving the checkBin out of the parsing loop will deal with the early disabling of settings.
Unfortunately, its not that easy. I hoped it might, but it doesn't actually fix anything. Moving the section for checkBin allowed me to have it split off from other code so that I can hopefully get better code-reuse. The routine still checks each profile one at a time, so the first failure causes the profile to disable even if there is one later that does work. One option is to make a hash of arrays so users can choose which conversion to use. Another is to add the decoder to the hash key so that each is still unique. The option that I'm hoping will work is to simply check for duplicates and enable if any one of the dupes works. Option 1 or 2 would probably be better long term, but partly falls into feature enhancement and would require changes to several modules.
Vidur's conversion patch of Tue, 08 Jun 2004 23:01:09 -0700 appears to fix this. Since this also appears to dupe bug 343, I'll mark this one as such. *** This bug has been marked as a duplicate of 343 ***
Routine bug db maintenance; removing old versions which cause confusion. I apologize for the inconvenience.