Michael Beal wrote: > I feel that Freevo has become overly complicated and needs to be > streamlined.
That is what Freevo 2.0 is doing. Freevo 1.x is very complex with too many dependencies and modules accessing some stuff from others. Like you wrote before, some plugins access internal stuff of the mixer. To avoid that we moved many parts out of Freevo into the kaa media repository. Each module in there is easier to maintain and the dependencies are clear. > As I see it, the most complicated part of Freevo should be the GTK > interface. I don't see much hope for Freevo 1.x to get an easy config app. It is just because that we use python code as config file. To keep it simple, we have kaa.config for 2.0 and it should be easy to write a config gui for it. > Nothing else needs be as complex. Yes and no. As you wrote, you don't need audio recoding. I have the CPU power, use digital audio out and getting non AC3/DTS 6 channel output is a nice feature for me. Dischi -- "We're back to the times when men were men and wrote their own device drivers" -- Linus Torvalds
pgp4TUOvPECYn.pgp
Description: PGP signature
------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________ Freevo-devel mailing list Freevo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freevo-devel