Differences
This shows you the differences between the selected revision and the current version of the page.
| howto:twonkyupnpserver 2011/02/07 21:43 | howto:twonkyupnpserver 2017/09/06 18:38 current | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== Installing Twonkymedia UPnP Server ====== | + | ====== Installing Twonkymedia UPnP Server ====== |
| - | This will allow proper UPnP serving to Playstation 3 & XBOX360 Consoles - something alot more interesting now they both support mpeg4 (Divx/Xvid) Codecs. UPnP is improved in 1.04 firmwares but this will add the feature to 1.03 Firmwares. | + | This will allow proper UPnP serving to Playstation 3 & XBOX360 Consoles - something a lot more interesting now that they both support mpeg4 (Divx/Xvid) Codecs. UPnP is improved in 1.04 firmwares but this will add the feature to 1.03 Firmwares. |
| This tutorial is originally from here - | This tutorial is originally from here - | ||
| [[http://boardsus.playstation.com/playstation/board/message?board.id=ps3media&thread.id=47398|PS3 Forums]] | [[http://boardsus.playstation.com/playstation/board/message?board.id=ps3media&thread.id=47398|PS3 Forums]] | ||
| - | TwonkyMedia isn't free, but it includes a 30-day trial. According to their website, it currently costs $39.95 for a TwonkyMedia license (version 4.4.x). Twonky don't provide telephone or email support for software installed on to a DNS-323, so make sure that it is working for you properly before buying the license key. | + | TwonkyMedia isn't free, but it includes a 30-day trial. According to their website, it currently costs $39.95 for a TwonkyMedia license (version 4.4.x). Twonky doesn't provide telephone or email support for software installed on a DNS-323, so make sure that it is working for you properly before buying the license key. |
| ===Which Version to Install?=== | ===Which Version to Install?=== | ||
| - | Twonky Server version 4.4.18 installs most easily and works well, but is no longer being updated for more recent UPnP clients or getting new features. Additionally it allows you to edit the navigation trees for example to include A-Z sorting of large music or video collections. | + | Twonky Server version 4.4.18 installs easily and works well, but is no longer being updated for more recent UPnP clients or getting new features. Additionally it allows you to edit the navigation trees for example to include A-Z sorting of large music or video collections. |
| Currently the latest version is 6.0.1, which can also install and run without problem, but requires some configuration changes after installation. Extending the navigation tree requires editing XML files, or at least replacing the default XML files with downloaded versions (eg from [[http://forum.qnap.com/viewtopic.php?f=177&t=29318&start=15|this QNAP forum post]]) | Currently the latest version is 6.0.1, which can also install and run without problem, but requires some configuration changes after installation. Extending the navigation tree requires editing XML files, or at least replacing the default XML files with downloaded versions (eg from [[http://forum.qnap.com/viewtopic.php?f=177&t=29318&start=15|this QNAP forum post]]) | ||
| Line 15: | Line 15: | ||
| Download links for 4.X, 5.X and 6.X versions of the software are available from this links on [[http://twonkyforum.com/viewtopic.php?f=16&t=7653|this page of the Twonky website]]. | Download links for 4.X, 5.X and 6.X versions of the software are available from this links on [[http://twonkyforum.com/viewtopic.php?f=16&t=7653|this page of the Twonky website]]. | ||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| Line 133: | Line 156: | ||
| Symlinks could be used to fix the problem instead, described here: | Symlinks could be used to fix the problem instead, described here: | ||
| - | [[http://forum.dsmg600.info/viewtopic.php?id=5288]] | + | [[http://dns323.kood.org/forum/viewtopic.php?id=5288]] |
| <file> | <file> | ||
| ## First create a directory for working files: | ## First create a directory for working files: | ||
| Line 150: | Line 173: | ||
| --------------------------------- | --------------------------------- | ||
| - | **Alternative method for installing Twonky 6.0.30** | ||
| - | (This alternative section - between the two groups of three parallel lines - was inserted by Briain on 07/02/2011) | ||
| - | |||
| - | I've just successfully updated a DNS-323 (Hardware Version B / D-Link FW 1.08) to Twonky 6.0.30 and have created an alternative starttwonky.sh file. It's based on adding the above recommended symlink to the starttwonky.sh file (as above), but in addition to the above, it first checks for the new directory and automatically creates it (and the log file) if not present. Basically, you can install Twonky 6.0.30, replace starttwonky.sh with the one below, reboot the D-Link and that's it done. I've tested it on a D-Link DNS323 (which has 32,000 FLAC files) and it all works well. | ||
| - | |||
| - | First install it as described above, but at the start of the installation process, remove the tick from the 'run it' box (so it doesn't start as soon as it's installed). Then copy the below script, paste it into Notepad++ and select EOL conversion to Unix format, then save it as starttwonky.sh | ||
| - | |||
| - | Copy this new starttwonky.sh to the D-Link and thus overwrite the one Twonky has created. You might have to Telnet into it and chmod 777 /mnt/HD_a2/starttwonky.sh (the existing Twonky created one) before you can drag and drop the new version onto the Volume_1 share. Once you have replaced it with the below version, reboot the D-Link and it will start Twonky using the revised script (then remember to set your media paths in the twonky config web page). | ||
| - | |||
| - | <file> | ||
| - | |||
| - | #!/bin/sh | ||
| - | # Twonky 6.0.30 replacement start-up script for D-Link DNS-323 NAS 07 February 2011 | ||
| - | # Creates directories and symlinks to move db and cache from /var and log from /tmp | ||
| - | # This protects NAS OS, prevents db rebuild at boot and loss of cache, settings etc | ||
| - | # If section creates files and directories first time Twonky (or NAS) is re-started | ||
| - | # Remainder is run on all subsequent reboots | ||
| - | |||
| - | /sbin/route add -net 224.0.0.0 netmask 240.0.0.0 dev egiga0 | ||
| - | |||
| - | if [ ! -f /mnt/HD_a2/twonky/sym_var ]; then | ||
| - | /bin/mkdir /mnt/HD_a2/twonky/sym_var | ||
| - | /bin/touch /mnt/HD_a2/twonky/TwonkyMediaServer-log.txt | ||
| - | /bin/chmod -R u+rwx,g+rwx,o+rwx /mnt/HD_a2/twonky/resources/views | ||
| - | fi | ||
| - | |||
| - | /bin/ln -s /mnt/HD_a2/twonky/sym_var /var/twonkymedia | ||
| - | /bin/ln -s /mnt/HD_a2/twonky/TwonkyMediaServer-log.txt /tmp | ||
| - | cd /mnt/HD_a2/twonky | ||
| - | /mnt/HD_a2/twonky/twonkymedia & | ||
| - | |||
| - | </file> | ||
| - | **Note 1** | + | ====== Twonky 6.0.31: Detailed installation instructions and downloadable replacement starttwonky.sh file ====== |
| - | Don't worry if you forget to disable the 'run after installation' tick-box option during the installation process. The D-Link will show its pink lights, but you can still Telnet into it, delete the Twonky created starttwonky.sh file then reboot the D-Link (Twonky will not start). You can then add the revised starttwonky.sh and reboot the D-Link (which will then work okay). | + | |
| - | **Note 2** | + | In case it helps anyone who is maybe a bit unsure of the exact procedure, I've written very comprehensive instructions (with several screen shots) and links to download a custom starttwonky.sh file which checks for (and if not present, automatically creates) the new directories for the database and cache, as well as moving the log file, then also creates the required symlinks. |
| - | Optionally, once you have unzipped the Twonky 6.0.30 installation files (and before running the installation process) you can (if you wish) change the trees at this stage (my latest custom versions are available [[http://forum.qnap.com/viewtopic.php?f=177&t=29318&start=15|here on the Qnap forum]]). If you do not wish to do that at this stage, you can still change them later (without having to use Telnet) as the above script changes the permissions in the /twonky/resources/views directory (so the trees can also be changed by simply dragging and dropping them using Windows Explorer at a later date). After any tree changes, remember to perform a full Twonky database rebuild to pick up the new music menu. | + | |
| - | **General Notes** | + | To see these instructions for installing Twonky 6.0.31 on a D-Link DNS 323 and obtain the files: [[http://forums.linn.co.uk/bb/showthread.php?tid=10063|click here]]. There are also links to my custom tree packs and an optional alternative clients.db file (which defaults to the full resolution art setting for control points that don't set Twonky automatically; Kinsky Desktop and Konduktor being two examples of CP's that don't advertise themselves in the user agent field). |
| - | Twonky will be slow the first time you browse album covers on your control point (it has to cache the images). It also seems to be very slow for the first few times you navigate the menu, but it soon settles down and runs very quickly. It doesn't fully rebuild the database when you restart the NAS, but it does rescan the contents (so it can take a while for large music libraries). The Media Receivers section in the Twonky config page can be set to suit your devices. If using a control point which can resize album art itself, it's best to select 'AssetControl DS Control Point' or 'Linn DS Control Point' against the MAC/IP address of your control point as this will make Twonky send full resolution art to the control point. That also speeds up the first art caching operation (after a database rebuild) as Twonky caches the full sized images (and thus doesn't have to use CPU to resize them). The 'Generic Media Receiver' entry resizes all images to 160 x 160 pixels (and will thus be slower when first browsing covers). Note that you will have to reset these 'media receiver' entries after performing a full database rebuild (a database rebuild resets them to 'Generic Media Receiver') though any custom set ones survive all rescans and reboots okay. Note that certain CP software (like Songbook or Chorus DS for the iPhone/iPad/iPod Touch) will set the media receivers entries automatically (so you don't have to bother setting them yourself). | + | |
| --------------------------------- | --------------------------------- | ||
