Thanks for the comments, I'll look into using mmpython
and making the rip code an item plugin.
Regarding the config parameters, and plugin
activation. What would really be nice is a "setup"
module that knows about all the plugins and lets you
just click a checkbox for the ones you want and lets
you enter in any parameters associated with that
particular plugin and then saves this off as
local_conf.py.
Activating a plugin and setting any config parameters
would then be pretty straightfoward. In this case we
could include all the args in the plugin activation
command and not worry about the plugin activation
command being user friendly since the user wouldn't
have to ever look at local_conf.py anymore since
freevo could format it all for them.
Regards,
Rich
--- Dirk Meyer <[EMAIL PROTECTED]> wrote:
> Rich C wrote:
> > Hello Gents,
>
> Hi
>
> > I've got a plugin for CD ripping to .mp3 and .wav
> > available.
>
> Great. That's on our todo list for some time now.
>
> > I've yet to test it out with the latest CVS, the
> last
> > time I checked out was June 2 (ancient in Freevo
> time,
> > I'll probably check out latest this weekend).
> > Hopefully someone can check it out and see if they
> > have any problems or suggestions.
>
> I haven't tried it yet, but read the source. Some
> suggestions:
>
> Maybe you shouldn't add the ripper to the main menu,
> maybe an item
> plugin is the better way. Pressing ENTER on an audio
> cd will give you
> the item ('rip to harddisc'). See cover_search.py
> for an example of an
> item plugin for audiocds.
>
> Since some days (two to be specific) Freevo has
> experimental support
> for mmpython. With that you can do this easier. You
> can identify an
> audio cd by item.type == 'audiocd'. You also have
> item.info.tracks with
> information about all tracks (and all CDDB data in
> it, you don't need
> to call CDDB yourself).
>
> How to use the mmpython support:
>
> Install the cvs version from
> www.sf.net/projects/mmpython and then run
> the script in WIP/Dischi in the current Freevo cvs
> to update some
> files to work with mmpython.
>
> > CD RIP Path and NAME Preferences:
> > CD_RIP_PN_PREF = '%(artist)s/%(album)s/%(song)s'
> > CD_RIP_PN_PREF =
> > '%(artist)s/%(album)s/%(artist)s-%(song)s'
> >
> > Lame .mp3 encoding options:
> > CD_RIP_LAME_OPTS = '--vbr-new'
> >
> > Lame .mp3 ID3 tagging options:
> > CD_RIP_ID3_TAG_OPTS = '--tt %(song)s --ta
> %(artist)s
> > --tl %(album)s --tn %(track)s'
> >
>
> Question to everyone: how should we deal with plugin
> options? Should
> we place them into freevo_config.py even when some
> people don't need
> them? Even when the plugin is not active as default?
> Or should we make
> it a long parameter list like
>
> plugin.activate('name',
> args=('%(artist)s/%(album)s/%(song)s', ...))
>
> Or should we make it like now: a plugin description
> should also
> contain a list of variables the plugin needs? How to
> print this
> information to the user?
>
>
> Dischi
>
> --
> while(!asleep)
> sheep++;
>
>
>
-------------------------------------------------------
> This SF.Net email is sponsored by: INetU
> Attention Web Developers & Consultants: Become An
> INetU Hosting Partner.
> Refer Dedicated Servers. We Manage Them. You Get 10%
> Monthly Commission!
> INetU Dedicated Managed Hosting
> http://www.inetu.net/partner/index.php
> _______________________________________________
> Freevo-devel mailing list
> [EMAIL PROTECTED]
>
https://lists.sourceforge.net/lists/listinfo/freevo-devel
__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com
-------------------------------------------------------
This SF.Net email is sponsored by: INetU
Attention Web Developers & Consultants: Become An INetU Hosting Partner.
Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
_______________________________________________
Freevo-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freevo-devel
