The general consensus is "Go ahead and fork the project." Some responses have
been a bit negative, others quite supportive. This is fine by me.
To clarify, _YES_, I do plan on going an extremely different direction; one
which is targeted at an American audience using a definitive set of supported
hardware. This is something several respondents made point of; to wit: Freevo
supports so much hardware that it doesn't support any of them well.
I feel I have overcome the audio problems that MANY users would have. However,
I can't say I have all those problems solved but I do have 2-, 4-, 6- and
8-channel audio in a fully functional state. The should have been made
available some time ago. The next step is to add _capability_ detection to the
mixer and code to alter the _system_ to make use of them.
I have also recently added a _complete_ numeric input for channel changing.
This is primarily an NTSC thing due to the way the channels are numbered as
NTSC channels do not contain alpha characters.
I don't want put this fork of the project on a CD and require the user to spend
an enormous amount of time configuring several things. This is where my
concept of the config file turns quite drastically away from the 2.0 branch's
concept. The config is Python code and I intend to take full advantage of that
fact.
I will stay in touch with the Freevo group and send solutions I have come up
with where I feel they are appropriate.
Thanks to everyone!
Michael
Duncan Webb <[EMAIL PROTECTED]> wrote: Michael Beal wrote:
> I've thought this through for quite some time. I have many reasons for
> wanting to go in a different direction. I will state that none of my
> reasons are because of anything personal against anyone on the lists.
> There are development goals I'd like to persue with the now deprecated
> 1.6 code that I do not feel are currently being pursued. I also do not
> feel that my development goals will fit with the majority of the current
> developers on this list. I can safely say that the current version
> running on my system is very far from the original 1.6.2 package I
> installed.
Hi Micheal,
1.6.2 is not deprecated, just that only bug fixes are going in there and
no new features. This means that it should be stable and safe to upgrade
to the next higher version.
1.7.x is where the new stuff goes and when I release 1.7.0, may be soon
then I will adopt the same strategy and freeze new features in the 1.7
branch and only apply bug fixes, new features go in to the rel-1 branch.
One of the nice features of the plug-in architecture of freevo is that
you can add anything without affecting most users and it is your choice
to use them or not.
Cheers,
Duncan
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Freevo-devel mailing list
Freevo-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freevo-devel
---------------------------------
Bored stiff? Loosen up...
Download and play hundreds of games for free on Yahoo! Games.
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Freevo-devel mailing list
Freevo-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freevo-devel
