Compiling Mediatomb with JS support

[Diego Diaz]

Hello,

Recently, I've been trying to add playlists to Mediatomb (installed via Alt-F packages) but it doesn't seem to work. I've tried both .m3u and .pls formats through the web UI with no success (unfortunately that UI is pretty quite when it comes to reporting errors). Then, I learnt one can also add content via command-line, which would provide more debugging information in case of errors. After doing that (e.g. mediatomb -D -a <absolute path to playlist file>) I'm getting a warning:

WARNING: Playlist <playlist file> will not be parsed: MediaTomb was compiled without JS support!

JS = Javascript. After googling that issue, it seems one needs to install libjs first, then download mediatomb's source-code, edit a few things to enable Javascript and compile it again. Has anyone done this in Alt-F before? At least installing libjs?

Thanks,

Diego

[Joao Cardoso]

Building SpiderMonkey libjs does not seems to be an easy task, not in my immediate plans (but you can anyway open an request-issue).

 

Thanks,

Diego

[Eric Wick]

There is a matching mediatomb package that have js support, i have used it half a year on d-link plain plus ffp.

http://forum.dsmg600.info/p21857-Yesterday-16%3A47%3A33.html

But it is a pain, cause mediatomb with scripting is heavy overbloatet. Full rescan of my 18000 files took full 3 days and nights, while rescan the whole dns-323 is unusable and busy. Now i am happy with minidlna from the alt-f package base, it rescan fu in one hour.

Eric

[Joao Cardoso]

On Thursday, August 2, 2012 8:32:41 PM UTC+1, Eric Wick wrote:

There is a matching mediatomb package that have js support, i have used it half a year on d-link plain plus ffp.

http://forum.dsmg600.info/p21857-Yesterday-16%3A47%3A33.html

But it is a pain, cause mediatomb with scripting is heavy overbloatet.

But only if using js? Or will its performance suffer even when not using it?

Mediatomb is already bloated, and if adding js support makes it perform worse I will not provide js.

The link above indicates a fully static executable, it should be *huge*!.

SpyderMonkey is the js engine used by Firefox, it has to be overkill for our small box.

[Eric Wick]

Without js the mediatomb is a bit faster, but took around 24 hours for a rescan. Yes the binary is really bloated and exhaust all memory of the dns 323. It's not a good idea to use mediatomb with inotify, mostly this result to a 24/7 rescanning box that will never be usable for any further function.
There is also a mediatomb script that ignores tags and read the filesystem tree, it need js but took around 3 hours.

Eric