DSM-G600, DNS-3xx and NSA-220 Hack Forum

Thank you for your quick response.  I suppose I must convert these AVIs to a different type.

7erl wrote:

@ boilerjt

Because you are really the expert on mediatomb, I would like to ask you to get my final problem solved:

I only stream *.m2ts files (renamed to *.m2t and mapped correctly to video/mpeg) from a CH3SNAS to my PS3.
Everything works phantastic, but I noticed, that I lack the file date and the movies total playtime listed below every title in the menues on the PS3. Only two dots (..) are listed below the movies. When running PS3 media server I can see the file date and movie play time below the movie titles.

How can I achieve the same on Mediatomb? Obviously there are two fields below the movie title that might be filled with some information. How can MT be forced to add this information from the file or how can I fill these fields manually?

Thanks in advance for your advice.

Regards
7erl

I have the same issue.   In my PC linux build of MediaTomb, the total runtime is shown and I have never seen a file date. I doubt MediaTomb even sends the file date.  In the PC build, MediaTomb uses the ffmpeg libraries to read the video information and send it within the PS3 menus.  I do not have the ffmpeg libs part of this NAS build because I could not build them.

Hi boilerjt

Could you tell me what I need to do to be able to stream mpeg-2 files from my DNS-323 d to my D-Link DSM-520.  File extension is mpg.

Thanks in adavance for your help.

perssinaasappel wrote:

Installed as per instructions with no problems. (Thanks boilerjt.)

Web based interface is working fine.
Browsing folders with the television set is working fine.
Problem is the build in upnp-av player from my television set is complaining: "not supported file". (And not playing the movie.)

If I use the build-in upnp-av server on my ch3snas, the same file playes with no problems on my television set.

Is there anything in the MediaTomb config file I missed or maybe something else I don't understand?
I never used MediaTomb before so any help is very appreciated. TIA

There are known issues with some of the DLNA compliant TVs and MediaTomb.  MediaTomb is not DLNA compliant (it contains some DLNA hacks for the PS3) and the new Sony and Samsung TVs require more than MediaTomb supports at this time.  There are people working on hacks as we speak trying to get these TVs working.  The issue with DLNA is that the specification is only available to DLNA members and it costs 10,000 USD a year for membership.  The MediaTomb developers do this as a hobby and cannot afford this, especially it being an open source free product.

Hello,

I'm using this version and it works really nice!! thank you. I created a nice import.js script that works perfectly for me.

I read there is also a import-dvd.js and this could read .iso dvd files.. For this to work we need:  libdvdnav and libdvdread? is this true and if so, are these libraries available for de dns-323?

Thx, boilerjt, I guess bad luck for me.
I'll try Twonky instead but I understand it's not free.
(Probably because they are a DLNA member.)

Edit: Just for the record, Twonky is working fine on my television set.

Last edited by perssinaasappel (2009-04-21 22:07:34)

Hello


I just succesfully started up mediatomb-0.12.0-SVN2017-static-dns323 for the first time

mnt/HD_a2/mediatomb12 # ./mediatomb.sh
2009-05-05 21:37:12    INFO: Loading configuration from: /mnt/HD_a2/mediatomb12/config/config.xml
2009-05-05 21:37:12    INFO: Checking configuration...
2009-05-05 21:37:13    INFO: Setting filesystem import charset to UTF-8
2009-05-05 21:37:13    INFO: Setting metadata import charset to UTF-8
2009-05-05 21:37:13    INFO: Setting playlist charset to UTF-8
2009-05-05 21:37:13    INFO: Configuration check succeeded.

Due to the information from this posting here ( http://dns323.kood.org/forum/viewtopic. … 896#p22896 )

Rival wrote:

With default settings Mediatomb couldn't handle the Hungarian accentuated characters (like íéáőúűöüó) well, it just showed a question mark and cut the word (ex. "Demjén Ferenc" = "Demj?"). So I added/modified the following lines in config.xml:

<filesystem-charset>UTF-8</filesystem-charset>
<metadata-charset>UTF-8</metadata-charset>
<playlist-charset>UTF-8</playlist-charset>
<scripting script-charset="UTF-8">
<...>

Mediatomb now imports and shares file names/mp3 tags well.

I have included the 4 lines into the config file to have German Umlauts recognised correctly.

However, I still have a small bt annoying issue with my Phillips MCi300:

For some reasons the file name is truncated/incomplete...the display leaves away the filename after about 25 letters.

For example...
04 - Air - Kelly, watch the stars.mp3
becomes
04 - Air - Kelly, watch th

in the display. Those things seem to be random, that means, sometimes I get the full filename, sometime I get a truncated filename.

1.) Can anyone confirm this or provide a workaround?
2.) Is there a way to increase the maximum number of letters that are transmitted to the client?
3.) How can I figure out if this is a Mediatomb-bug or an issue with my streaming client?

Any hints greatly appreciated.

Last edited by rori (2009-05-05 23:51:58)

boilerjt wrote:

boomshanker wrote:

Hi boilerjt

Could you tell me what I need to do to be able to stream mpeg-2 files from my DNS-323 d to my D-Link DSM-520.  File extension is mpg.

Thanks in adavance for your help.

Sorry for the delay... I somehow missed your post.  Try adding this to config.xml in the mappings:

<map from="mpg" to="video/mpeg"/>

I finally had the chance to try, and your suggestion worked... Thank you.

This works for me:

place this in <mimetype-profile-mappings>

<transcode mimetype="application/ogg" using="oggwav"/>

place this in <profiles>

 
<profile name="oggwav" enabled="yes" type="external">
     <mimetype>audio/wav</mimetype>
     <accept-url>no</accept-url>
     <first-resource>yes</first-resource>
     <accept-ogg-theora>no</accept-ogg-theora>
     <agent command="oggdec" arguments="-o %out %in"/>
     <buffer size="1048576" chunk-size="131072" fill-size="262144"/>
</profile>

This should work if your device will accept audio/wav.  If it doesn't work with audio/wav and needs LPCM (audio/L16), I haven't figured it out yet.  I am using the oggdec that comes with the firefly build and it appears to be an old version(1.20).  I don't think it has the parameters (endianness, signedness, etc) to correctly format an LPCM stream.

rori wrote:

Sorry for keeping up lots of questions.

I am still battling with ogg support. I have been reading a lot and tried to adapt my config.xml but still without success for the ogg-files.

As far as I can see the standard ogg-transcoding-application in the this build from  svn-2017 is ogg123 and/or vlc (in the standard config.xml that  is created during the first startup)

Code:

<transcoding enabled="yes">                                                   
    <mimetype-profile-mappings>                                                 
      <transcode mimetype="video/x-flv" using="vlcmpeg"/>                       
      <transcode mimetype="application/ogg" using="vlcmpeg"/>                   
      <transcode mimetype="application/ogg" using="oggflac2raw"/>               
      <transcode mimetype="audio/x-flac" using="oggflac2raw"/>                  
    </mimetype-profile-mappings>                                                
    <profiles>                                                                  
      <profile name="oggflac2raw" enabled="no" type="external">                 
        <mimetype>audio/L16</mimetype>                                          
        <accept-url>no</accept-url>                                             
        <first-resource>yes</first-resource>                                    
        <accept-ogg-theora>no</accept-ogg-theora>                               
        <agent command="ogg123" arguments="-d raw -o byteorder:big -f %out %in"/
        <buffer size="1048576" chunk-size="131072" fill-size="262144"/>         
      </profile>                                                                
      <profile name="vlcmpeg" enabled="no" type="external">                     
        <mimetype>video/mpeg</mimetype>                                         
        <accept-url>yes</accept-url>                                            
        <first-resource>yes</first-resource>                                    
        <accept-ogg-theora>yes</accept-ogg-theora>                              
        <agent command="vlc" arguments="-I dummy %in --sout #transcode{venc=ffmp
        <buffer size="14400000" chunk-size="512000" fill-size="120000"/>        
      </profile>                                                                
    </profiles>                                                                 
  </transcoding>

Unfortunately both the vlc and the ogg123 application are unknown after installing the additional packages from post#1.

I have tried I tried to replace "ogg123" with "oggdec" but without success.

Who has successfully managed to use oggdec within SVN2017 and can come up with a working config.xml?

If your devices will not play ogg natively, a transcoder will be needed for MediaTomb.  I am using Delekhan's oggdec to transcode ogg to wav and it works great with my DirecTV HR20.   I looked at Delekhan's firefly configuration files and he is using the same oggdec command line as I am and streaming the wav file.  If this version of firefly works for you, then I assume this older oggdec should work as well.  One easy thing you can do is to replace the audio/wav mimetype with audio/x-wav and see if this will work.

Transcoding on the DNS-323 is tricky because the transcoding apps must support fixed point (integer math) because the NAS does not have a floating point unit.  Almost every transcoding app uses floating point and will not work.  Don't bother with vlc as it is a resource hog and was probably not compiled with a fixed point ogg decoder.  I have not tried ogg123 and I'm not sure there is a fixed point version around.

If this doesn't work, open up the MediaTomb WebUI and select an ogg song in the database.  Click on the edit icon (pencil and paper) and verify that the mimetype is application/ogg.

rori wrote:

Thanks for the hint and good advice.

Unfortunaly neither my Roku Soundbridge nor my Philips MCi300 can play ogg using this Mediatomb-settings.

Does that mean, that both players require LPCM (audio/L16) support that you have mentioned?

I can still playback my ogg-files via Firefly Mediaserver/Roku Soundbridge but  I would really like to get rid of Firefly (no longer maintained) and finally switch to mediatomb completely.

What - in your opinion - would be required to enable LPCM (audio/L16)-support for Mediatomb and who could possibly provide this?

Would that be Delekhan ( this thread: http://dns323.kood.org/forum/t1897-Firefly-package-(with-flac).html ) or
fonz to include ogg123 and vlc as additional fun_plug packages or
jin as the mediatomb-developer to do some IT-magic?

Last edited by boilerjt (2009-05-13 22:40:34)

Hello boilerjt,

thanks to your advice I was able to get a little further.

I have changed the mimetype for wav-files to audio/x-wav (succesfull playback of a wav-testfile has confirmed the need af the alternative setting) and I have ensured that the application/ogg is correct in the frontend.

But I still can not playback ogg-files in transcoded mode.

Some output from my console:

1.) Enabling special characters

/mnt/HD_a2/mediatomb12 # ./mediatomb.sh 
2009-05-25 19:01:46    INFO: Loading configuration from: /mnt/HD_a2/mediatomb12/config/config.xml
2009-05-25 19:01:46    INFO: Checking configuration...
2009-05-25 19:01:46    INFO: Setting filesystem import charset to UTF-8
2009-05-25 19:01:46    INFO: Setting metadata import charset to UTF-8
2009-05-25 19:01:46    INFO: Setting playlist charset to UTF-8
2009-05-25 19:01:46    INFO: Configuration check succeeded.

2.) Requesting an ogg-file from clients
3.) Client refuses to play the ogg-file

BUT: It seems that transcoding starts up perfectly due to the output in "ps" in telnet-mode.

/mnt/HD_a2/mediatomb12 # ps
PID   USER     COMMAND
    1 root     init                                
    2 root     [ksoftirqd/0]
    3 root     [events/0]
    4 root     [khelper]
    5 root     [kthread]
   11 root     [kblockd/0]
   14 root     [khubd]
   49 root     [pdflush]
   50 root     [pdflush]
   52 root     [aio/0]
   51 root     [kswapd0]
  190 root     [scsi_eh_0]
  191 root     [scsi_eh_1]
  192 root     [scsi_eh_2]
  193 root     [scsi_eh_3]
  204 root     [mtdblockd]
  218 root     [kcryptd/0]
  219 root     [kmirrord/0]
  230 root     [loop0]
 1282 root     atd 
 1366 root     [md0_raid1]
 1554 root     chkbutton 
 1578 root     /web/webs 
 1584 root     fancontrol 
 1619 root     /usr/sbin/samba/smbd -D 
 1623 root     /usr/sbin/samba/nmbd -D 
 1627 root     /usr/sbin/samba/smbd -D 
 1629 root     op_server 3 3 3 
 1635 root     -sh 
 1638 root     check_hotplug 
 1713 root     lpd Waiting
 1743 root     crond 
 1811 root     /ffp/sbin/telnetd -l /ffp/bin/sh 
 1822 root     /ffp/sbin/mt-daapd 
 1823 root     /ffp/sbin/mt-daapd 
 1825 root     /ffp/sbin/mt-daapd 
 1844 root     /ffp/sbin/mt-daapd 
 1882 root     /usr/sbin/samba/smbd -D 
 1945 root     /ffp/bin/sh 
 2006 root     /mnt/HD_a2/mediatomb12/usr/bin/mediatomb -m /mnt/HD_a2/mediatomb12 -f config -d 
 2007 root     /mnt/HD_a2/mediatomb12/usr/bin/mediatomb -m /mnt/HD_a2/mediatomb12 -f config -d 
 2008 root     /mnt/HD_a2/mediatomb12/usr/bin/mediatomb -m /mnt/HD_a2/mediatomb12 -f config -d 
 2011 root     /mnt/HD_a2/mediatomb12/usr/bin/mediatomb -m /mnt/HD_a2/mediatomb12 -f config -d 
 2013 root     /mnt/HD_a2/mediatomb12/usr/bin/mediatomb -m /mnt/HD_a2/mediatomb12 -f config -d 
 2014 root     /mnt/HD_a2/mediatomb12/usr/bin/mediatomb -m /mnt/HD_a2/mediatomb12 -f config -d 
 2015 root     /mnt/HD_a2/mediatomb12/usr/bin/mediatomb -m /mnt/HD_a2/mediatomb12 -f config -d 
 2016 root     /mnt/HD_a2/mediatomb12/usr/bin/mediatomb -m /mnt/HD_a2/mediatomb12 -f config -d 
 2017 root     /mnt/HD_a2/mediatomb12/usr/bin/mediatomb -m /mnt/HD_a2/mediatomb12 -f config -d 
 2018 root     /mnt/HD_a2/mediatomb12/usr/bin/mediatomb -m /mnt/HD_a2/mediatomb12 -f config -d 
 2023 root     /mnt/HD_a2/mediatomb12/usr/bin/mediatomb -m /mnt/HD_a2/mediatomb12 -f config -d 
 2024 root     /mnt/HD_a2/mediatomb12/usr/bin/mediatomb -m /mnt/HD_a2/mediatomb12 -f config -d 
 2025 root     /mnt/HD_a2/mediatomb12/usr/bin/mediatomb -m /mnt/HD_a2/mediatomb12 -f config -d 
 2108 root     oggdec -o /tmp/mt_transcode_IQXDUU /mnt/HD_a2/MP3/Test-Verzeichnis/OGG/Air - [1999] - Premiers Symptômes/07 - G
 2109 root     /mnt/HD_a2/mediatomb12/usr/bin/mediatomb -m /mnt/HD_a2/mediatomb12 -f config -d 
 2114 root     ps

Obviously PID 2108 is started successfully and it runs through all the files in the directory.

Sometime I see two ogg-files being transcoded simulatanously, but I never get playback on my client.

If I manually decode an ogg-file, and place the wav-output in the same directory, I can play the wave-file (of course) but also the ogg-file (which is due to the fact that the wave-file is present in the directory). As soon as I delete the wav-file, ogg-playback is impossible again.

Do I have to adjust the cache-settings in the config-file???

Thanks for your time, patience and good advice :-)

Last edited by rori (2009-05-25 20:29:04)

Hello, I'm a totally computer user nerd. I just got a dns-323 in order to serve mkv files to my popcorn but I found a lot of troube. Finally i arrived at this wonderfull forum and I found what it seems a pretty good solution, mediatomb.
I tried to install following the instructions at the first post, but I'm not able to enter mediatomb directory, it says permission denied. I try to delete the directory with the ftp connection but also appears the permission denied message.

It's because I did not login as a root user via ssh?
Thank you very much for all the good things you people do here, and please forgive my bad english.

cheers from barcelona