MAS
@mas wrote:
Tested forked-daapd now a bit. Had to manually create it’s /var/cache subdir and then it worked.
Differences noticed vs mt-daapd:
– Twice the memory usage
– 10x higher CPU load (relevant on small systems, less so on more powerful systems)
– scanning of database slightly, but insignificantly slower
– streaming works just the same
– no smart playlists 8-(
– no status/admin interfaceTranscoding not tested yet.
But seeing that no coder is in the moment really interested to develop either mt-daapd or forked-mtdappd it seems irrelevant anyway. Both would require for a new coder quite some initial work to put in. For mt-daapd it would be to understand the not so well structured old code. For the fork it would be working on interoperability between distributions and stripping down some libararies/dependencies.
That beeing said the case to revive the project rests for a while longer I guess.
It would seem that way. I have had lots of offers to help in the form of testing, and management of the forum. I don’t have a serious offer of any coders willing to move mt-daapd forward. If development is progressing on the other fork is it worth my time and money in getting this project up and running if the focus is on the other.
I am at a fork (pun) now and need to make some harsh decisions.
Do we really want to continue to get this project going, in that I need a team..?
Is it going to be worthwhile?
Are we really going to move this code forward or just maintain it?
Is it better to hang up mt-daapd and move to the new fork?
I need to move forward on this or move my time elsewhere. I have all the resources to manage this project and finance if needed but need some input from the people who use it and want to be involved.
I apologise for my absence but I have a seriously ill daughter due to an RTA
For the record my email address is working and have loads of responses but nothing concrete. My contact details are [email protected]
Andrew