Thecus N5200Pro

[BramWithaar]

let's use that ;-).
In comparing the original squeezecenter code to the Module i could only find a handful of changes, and some added files. I'll try again this weekend, post the results and errors, and see how it works out.

Right now i'm trying a different approach. i've created a chroot environment, and installed squeezecenter in there. The thecus can run a chrooted debian environment. I don't know yet if it's possible to boot into it and start squeezecenter at device startup. At the moment i'm stuck at connecting to squeezecenter.

[egd]

look forward to seeing your findings.

[mherger]

> look forward to seeing your findings.

So am I. I'm particulary interested in what needed to be patched in the SC code. We've reworked parts of 7.3 to simplify adding OS/system specific code. Your findings might help us further improving this. The goal of that work was to make patching SC unnecessery, but give NAS devs a means to include their own code easily.

--

Michael

[Shredder]

Thanks for all the work on this.

[mcknej01]

Just thought I would add my name as another who is eagerly awaiting a Squeezecenter update for my Thecus box (Andreas - where are you?).

[iletunic]

Hello everyone,

since omega stopped updating the Thecus module, I decided to take over. New version is available through the onbeat.dk module page. Please let me know if there are any problems.

Enjoy.

[mherger]

> since omega stopped updating the Thecus module, I decided to take over.

Great news! This will make many users happy.

One question: I tried to understand what parts of SC you had to patch. Could you please tell me a bit more about it? I think it would be great if it was possible to separate your package as much from the SC distribution as possible. I've added a way to customize SC for a OS' needs in 7.3. Some of your patches might be obsolete using a Slim::Utils::OS::Custom.pm file (eg. the scanner patch). Others might require more changes to OSDetect, which I'd be happy to add (if reasonable).

See http://forums.slimdevices.com/showthread.php?t=52365

--

Michael

[mherger]

> Some of your patches might be obsolete using a Slim::Utils::OS::Custom.pm file (eg. the scanner patch).

I've started a wiki page documenting this module:
http://wiki.slimdevices.com/index.ph...ls::OS::Custom

--

Michael

[iletunic]

> since omega stopped updating the Thecus module, I decided to take over.

Great news! This will make many users happy.

One question: I tried to understand what parts of SC you had to patch. Could you please tell me a bit more about it? I think it would be great if it was possible to separate your package as much from the SC distribution as possible. I've added a way to customize SC for a OS' needs in 7.3. Some of your patches might be obsolete using a Slim::Utils::OS::Custom.pm file (eg. the scanner patch). Others might require more changes to OSDetect, which I'd be happy to add (if reasonable).

I'll check the module... There isn't much that needs to be done to the actual server source. Scanner patch is nothing more than a custom path for the perl binary, and an extra entry to the LD_LIBRARY_PATH. ffmpeg is also used in several places in convert.conf. Other than that, it's just a regular server source package, with modules compiled using non-threaded perl.

[egd]

I'll check the module... There isn't much that needs to be done to the actual server source. Scanner patch is nothing more than a custom path for the perl binary, and an extra entry to the LD_LIBRARY_PATH. ffmpeg is also used in several places in convert.conf. Other than that, it's just a regular server source package, with modules compiled using non-threaded perl.

iletunic, many thanks for taking the time to do this. Myself (and I suspect a few others) are interested in turning this into a community development such that we are able to patch/rebuild etc. whenever the whim strikes, an annoying bug is dealt with or a major release occurs. To this end, I'd appreciate your thoughts re 1) whether you'd be interested in facilitating this and 2) how this could best be set up.

Once again, many thanks - I'll finally be able to use the Controller (or at least try to) on my full library.