[HowTo] Setup MediaTomb (mediaserver) on WL-500gP and WL-500W

[Nixblicker]

Hello guys,

I still stick with my good old WL500W, and am still very much satisfied with it.
But after my Twonky media server license expired, I had to find an alternative to stream my videos to my beamer.

So I gave mediatomb a try, and ended up installing the static optware version from http://mediatomb.cc/pages/download#optware.

After the fiddling with sqlite and such it seemed to work. But wait, it does only display my audio files in the tree I gave the ui to search for media.
There it also only displays an Audio subfolder in "Database", no Video listing at all.
Files I wished it would find are regular avi and such. Nothing special.

What the heck - tried googling, but nobody ever seems to have had this problem. Cannot find anything unusual also in the default config.xml that would make it exclude something.

Any ideas someone?

Cheers,
Nix

[!gm]

When I used the wl-500gP with mediatomb in the back-days, I wasn't satisfied at all. The indexing of video worked, but i took ages. You may run mediatomb with -D and -l {logfile} options while doing a rescan so we're may be able to understand whats wrong there.

I suggest using minidlna there is no hazzle when importing video. You loose transcoding-ability but in my eyes this is useless on a soho-router anyway.

[Nixblicker]

Thank you very much for your suggestions, !gm

I did include the -l option in the startup script and afterwards rescanned the db.
Here is the output

mediatomb.log.tar.gz

Sorry for the compression - it did'nt let me upload the plain text log.

On my first look it seems to be a problem with the character encoding.
But have a look if you don't mind.

Cheers,
Nix

When I used the wl-500gP with mediatomb in the back-days, I wasn't satisfied at all. The indexing of video worked, but i took ages. You may run mediatomb with -D and -l {logfile} options while doing a rescan so we're may be able to understand whats wrong there.

I suggest using minidlna there is no hazzle when importing video. You loose transcoding-ability but in my eyes this is useless on a soho-router anyway.

[Nixblicker]

Hello,

here are some lines from the config.xml, showing that utf-8 should be loaded.

<?xml version="1.0" encoding="UTF-8"?>
...
<scripting script-charset="UTF-8">

But in the log it says the following:

2012-12-20 18:23:47    INFO: Checking configuration...
2012-12-20 18:23:47    INFO: Setting filesystem import charset to ASCII
2012-12-20 18:23:47    INFO: Setting metadata import charset to ASCII
2012-12-20 18:23:47    INFO: Setting playlist charset to ASCII
2012-12-20 18:23:47    INFO: Configuration check succeeded.

Seems it is the crooked charset problem once again... Dohhh
The Environment Variable LANG is not set in the basic shell of the box. Would have no idea how to set it permanently, if it helps at all...

Tried to set the encoding with "export LANG=en_UK.UTF-8" at the top of the startup script - no success.
Still importing in stupid ASCII.

Cheers

[!gm]

Sorry for the compression - it did'nt let me upload the plain text log.

no problem

what about

<filesystem-charset>ISO-8859-1</filesystem-charset>
<metadata-charset>ISO-8859-1</metadata-charset>

... if you haven't googled this by yourself

[Nixblicker]

Ähem,

no I haven't .

I'll try that - but as the system is capable of utf I thought i should stick to it in MT.
Do you think its not properly built in the static version?

Well, whatever - will report back when I tried it.

UPDATE:

Inserted the above option in config.xml, but still no luck. The log still tells me files are imported in ASCII.

Is it possibly hardcoded?


Thx again for the tip,
Nix

[Nixblicker]

The documentation of the above config options states

Optional

Default: if nl_langinfo() function is present, this setting will be auto detected based on your system locale, else set to ISO-8859-1

Defines the charset of the filesystem. For example, if you have file names in Cyrillic KOI8-R encoding, then you should specify that here. The server uses UTF-8 internally, this import parameter will help you to correctly import your data.

So if i read it correct, this setting is something like a fallback value, if no charset is detected by the ominous nl_langinfo() function.

Do you by any chance know what this function is and if it is present?

Cheers,
Nix

[!gm]

ahhhhh me is stupid....

set it to UTF-8

<filesystem-charset>UTF-8</filesystem-charset>
<metadata-charset>UTF-8</metadata-charset>

as that function seems not to work...

[Nixblicker]

Well, that change of the option also doesn't.

Still importing in ASCII so it seems. At least the log claims to do so.

But actually this doesn't seem to be the base of the problem. Even if a just select a subfolder guaranteed not to have charset encoding problems, there is no video file added to the database. No Video subfolder created in the ui etc.

Darn, I'm out of ideas here.
Probably I should give minidlna a try.

Thx anyway !gm!