I am currently working on static packages of MediaTomb that can be used as an addon to the existing firmware of various NAS devices. The idea is, that once you have telnet access to your NAS you can simply use the precompiled static binary without any need to reflash the unit with some custom firmware and without having to worry about dependencies - those packages should run on existing vendor firmware.
Unfortunately I do not have much devices to test with, so will I rely on your feedback.
If you have a NAS, be it an Iomega unit, a WD MyBook, or anything else, or a router like the WL500g and if you are willing to test the static packages - please drop me a mail to: jin at mediatomb dot cc
Once we are sure that the packages work I will make them available for download for everyone.
Would it be possible, in the future, for the main app to become compilable without having to worry about dependencies ?
Is this something allready planned for to do at some time or would it be impossible ?
this is not planned and will not be done. Of course one could create a source tree where all libraries are pulled in and adapt the build environment accordingly, but I do not think that there is any point in doing that.
I am running the static build package on a WL500GP. It appears to run correctly, but it uses 100% of the CPU, even after finishing indexing. Also, indexing in itself takes forever (it has been running 4 days now but will possibly stop today).
I build packages for this device now-and-then, such as custom code I have written, or incorporating other packages into the buildroot, so if I could have some form of instructions on how the static package was built, I may be in a posistion to help debug this issue myself.
I think MT is already part of FreeNAS, however I can't say what version. DirectTV - is it the HR20 stuff? If yes, you'll need latest SVN. Btw I won't be doing static packages for FreeNAS, I think it targets x86 anyway.
There are some known problems with static packages on the MyBook (and on all Marvell Orion based boards), unfortunately this needs some heavy debugging, tests on user level have already been done but at this point I need to dig in - which I can not do due to the lack of this hardware. You can still use the Optware stuff for the MyBook though, that will work.
Yes, I'm talking about the HR20 stuff. But the FreeNAS package is 0.10.0 so I'm looking at getting it upgraded to the one that supports the HR20. Any possibility of releasing a 12??? version soon or do I need to just bite the bullet and go the SVN route? Currently I'm having issues where it's needing a version of a compenet that it appears that I have but it's not recognizing it (need to brush up on my unix!)
On the MyBook are the issues with using static packages or with running MediaTomb on this hardware? All I'm planing on using it for it to server music and photos to the HR20 (I'm assuming trying to transcode video is beyond the CPU of the MyBook). When (thinking positive) I get this all working I'll post a writeup of what I did to get it going.
I can't really say anything about FreeNAS, I only know that it is based on FreeBSD and since our stuff works for FreeBSD - you should be able to compile SVN if you get a build environment and all dependencies.
By saying "soon" we have been wrong a number of times in the past, so there is no release date. Yes, it is planned "soon", but that can be as soon as 2 weeks or a month and a half, I wouldn't wait.
Regarding the MyBook: the problem is only with my static builds, I do not think that this is directly related to the hardware, but probably to something in the kernel, I really do not know. Users reported that they were able to run the server, but it did not bind to any network interface and SSDP did not work.
Again, it works with the Optware packages, the problem is only in my static build.
Btw, from what I read - photos on the HR20 is no fun at all, it seems to be displaying thumbnail resources instead of the correct images, that needs to be fixed in the HR20 firmware.
The HR2x seems to have 2 issues with photos. The first is with high resolution photos in which it seems to timeout displaying the image, then it displays the second image available which is the thumbnail. The second issue is it has problems with some EXIF metadata in the photo file and it gives an "Unable to display..." message. There is a transcoding procedure for these issues posted in the wiki.
on a AVM FRITZ!Box Fon WLAN 7270 (ADSL Router) and it works perfectly together with my PS3. Streaming of HD material (wmv + divx) from a USB attached WD Passport Drive works like a charm.
Hi, I have a Giganas 35HD-DUAL-NAS-E and an Acer AT37050-MGW. I've successfully installed the static armv4 build and the TV sees it and can drill down to various levels. This is my first experience of mediatomb so I don't really know what to expect but the TVs media gateway crashes whenever I try to access any content. I have to cycle the TV to get back in. The mediatomb still seems to be indexing - I don't know if this will affect the ability to access media. I guess I'll try again when it's finished. Thanks.
Last time I tried with the ACER TV it worked; basically - check if there is a firmware upgrade available, if not complain @ their support line, with some luck they might fix it.
Another possibility (which of course makes me less happy ;) - we could compare the XML with servers that work with this device and see if we can add something to work around the bugs in the TV's firmware.
Gegarding indexing: well..unfrotunately that's indeed not so fast, the upcoming 0.12 release will have some improvements regarding import speed, but especially on smaller/slower devices import can take quite some time :>
Well, I just need to find the time to recompile it for mips2, as you know I fixed the issue for mips32... I'll try to do it soon :)
Regarding the initial scan and the playlists: I think this is a known bug which has been submitted to the bugtracker (please check if it is really the case, if not submit it), I will have to look at this for the 0.12 release.
Thanks for the offer for logs/etc, but the issue has been fixed, it's just that I was not aware that people had the same problem on other devices. (Well, the issue would have happened on any device without a realtime clock, but I was too lazy to rebuild it with the fix for all archs since I only had complaints from mips32el package users ;) I'll see that I build a mips2el package for you soon.