Difference between revisions of "Toolbox"
(→More tools) |
|||
| (3 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | + | == Playlist Creation with Twonky Media Server <br> == | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
* Twonky assumes that playlists that are scanned contain links that are ''indexed from the location of the playlist''. This makes Twonky sensitive to where you up load any playlists with relative references. | * Twonky assumes that playlists that are scanned contain links that are ''indexed from the location of the playlist''. This makes Twonky sensitive to where you up load any playlists with relative references. | ||
| Line 67: | Line 50: | ||
| fully qualified drive and path for local files | | fully qualified drive and path for local files | ||
|} | |} | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
Latest revision as of 10:59, 10 August 2010
Playlist Creation with Twonky Media Server
- Twonky assumes that playlists that are scanned contain links that are indexed from the location of the playlist. This makes Twonky sensitive to where you up load any playlists with relative references.
- Twonky is agnostic to "\" or "/" dir separators, however it cannot "fix" mappings between diffferent views of the same file system. For example a media library on a NAS with Twonky installed will have a "Linux view" that is used directly by Twonky. The same files will also be available over a SAMBA view (on Windows clients). The Samba view is where the Playlist creation tool will run, but Twonky must use the "Linux view". This will effect playlists with absolute paths are used
Most playlist creating tools default to producing playlists with absolute links to items.
Those playlist tools that do allow relative paths, default to absolute paths. Out of the ones listed here, only Media Monkey defaults to relative paths.
Playlist creation tools
The following table lists the behaviours of common playlist creation tools
Ensure that the Playlist is saved as a .M3Ufile and is saved in the same root folder as the Music. The playlist file will have to be scanned by the UPnP server software (such as Twonky), before it is displayed on the GUI
| Application | Playlist Types | Comments |
| WINAMP | M3U | Creates playlists at global root for UNC paths. All items fully qualified drive and path for local files, "export" functionality in sub menu |
| WINAMP | PLS | As M3U above, No options |
| WMP11 | WPL | global root for UNC paths, automatic export to "my documents/my music/my playlists" not settable |
| MUSICIP | XSPF | global root for UNC paths, fully qualified drive and path for local files, "export" functionality in sub menu, "linking" application playlist with on disk playlist, "Use Relative Paths" OFF by default, "Use Extended M3u" |
| MUSICIP | M3U | as above |
| MEDIAMONKEY | M3U | local files relative, (I'm guessing relative to Playlist location...). Create the Playlist within the MediaMonkey app, then save as a .M3U playlist WITHIN the NAS |
| MP3TAG | M3U | fully qualified drive and path for local files |
