Allow arbitrary encoders

[GoogleCodeExporter]

What version of rubyripper are you using? On what operating system? Are you
using the gtk2 or the commandline interface?

0.4.1-gtk, Ubuntu 7.04

This isn't a bug as much as a feature request.  Would it be possibly to
allow for multiple arbitrary encoders in the codec section?  Right now, I
have locally-compiled versions of flac and lame and I use them rather than
the system-wide ones.  KAudioCreator allows for either customization of
codec paths or addition of different arbitrary codecs.

Obvious, RubyRipper is much better and I want to use it instead :-)

Original issue reported on code.google.com by heliolo...@gmail.com on 2 Jul 2007 at 6:56

[GoogleCodeExporter]

It seems to me like a bit of luxury, but I'll see what I can do. It won't have 
top 
priority. Patches are always welcome ofcourse ;)

Just out of curiosity, why have two different versions of flac and lame 
installed?

Original comment by rubyripp...@gmail.com on 2 Jul 2007 at 8:04

• Changed state: Accepted

[GoogleCodeExporter]

Ubuntu won't get flac 1.1.4 and lame 3.97 until Gutsy. 

Original comment by heliolo...@gmail.com on 2 Jul 2007 at 8:35

[GoogleCodeExporter]

I see. Any suggestions how to show the option to the user?

Original comment by rubyripp...@gmail.com on 2 Jul 2007 at 8:42

[GoogleCodeExporter]

Perhaps this task would fit in the "other" section under codecs already?  Not 
sure if
that's supposed to be a path to an encoder or is just left there for future use.

Original comment by geniuswe...@gmail.com on 11 Jul 2007 at 7:14

[GoogleCodeExporter]

The other option is there to offer an extra choice of a custom encoder. So yes, 
for 
the meantime this could be a solution for the problem. Good thinking!

Original comment by rubyripp...@gmail.com on 11 Jul 2007 at 9:38

[GoogleCodeExporter]

If it helps someone, I use the following in the 'other' section for AAC encoding
using FAAC:

faac -w --artist '%a' --title '%t' --genre '%g' --album '%b' --track %n --year 
'%y'
-o '%o' %i

so it should definitely be possible to use that section for this - the only 
minor
problem is that it renames the file as '01-songname.undefined' (the songs need 
to be
manually renamed afterwards).

Original comment by nick.cu...@gmail.com on 2 Oct 2007 at 1:00

[GoogleCodeExporter]

Can anyone test if the current implementation works? (revision 149). For the 
extension to work use "%o".extension

I've tested myself with:
faac -w --artist "%a" --title "%t" --genre "%g" --album "%b" --track %n --year 
"%y" %i -o "%o".aac

Please report any errors. If none are found within a week, this issue will be 
closed. As already pointed out, a custom lame is also possible. Just 
use /wherever/lame "%i" %o".mp3

Original comment by rubyripp...@gmail.com on 4 Oct 2007 at 7:44

• Changed state: Started

[GoogleCodeExporter]

No news = good news. Issue fixed.

Original comment by rubyripp...@gmail.com on 12 Oct 2007 at 2:42

• Changed state: Fixed