Difference between revisions of "Toolbox"

From LinnDocs
Jump to: navigation, search
 
(10 intermediate revisions by 2 users not shown)
Line 1: Line 1:
This page contains information on and links to software tools you may find useful for editing metadata, creating playlists, converting media, etc.
+
== Playlist Creation with Twonky Media Server <br> ==
 
 
These are the best of the basics:
 
 
 
* Metadata editor http://www.mp3tag.de/en/
 
* Metadata editor for Mac http://sbooth.org/Max/
 
* Metadata viewer Windows Explorer plugin http://www.softpointer.com/AudioShell.htm
 
* Batch encoders http://www.foobar2000.org/ http://mediacoder.sourceforge.net/
 
* Media library management and tag editor http://www.mediamonkey.com/
 
 
 
 
 
 
 
<br>
 
 
 
== Transcoding ==
 
 
 
Most digital media collections are populated with media of many different formats.&nbsp; Sometimes you'll need to convert audio from one format to another for playback on portable devices, various media streamers, or specialist computer media applications.&nbsp; The following applications provide excellent batch transcoding features.<br>
 
 
 
=== Foobar2000 ===
 
 
 
http://www.foobar2000.org/ <br>
 
 
 
Foobar provides very easy to use batch transcoding feature.&nbsp; This allows you to select a directory of music and a target codec, and it will go and automatically re-encode the entire directory.&nbsp;
 
 
 
The interface is basic, and it has support for a wide range of media formats.<br>
 
 
 
=== dbPowerAmp ===
 
 
 
http://www.dbpoweramp.com/dmc.htm<br>
 
 
 
dbPowerAmp is a commercial media mangement tool providing accurate ripping and metadata and library management.&nbsp; The it contains a batch transcoding feature, but it is not as easy to use as foobar.<br>
 
 
 
=== mediacoder ===
 
 
 
http://mediacoder.sourceforge.net/<br>
 
 
 
== <br>Playlist Creation ==
 
 
 
=== Playlist Creation with Twonky Media Server <br> ===
 
 
 
In order to successfully create playlists for use in Twonky Media, here are some tips:
 
  
 
* 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.
* Twonky is agnostic to "\" or "/" dir separators, however it cannot "fix" mappings between diffferent views of the same file system.&nbsp; For example a media library on a NAS with Twonky installed will have a "Linux view" that is used directly by Twonky.&nbsp; The same files will also be available over a SAMBA view (on Windows clients).&nbsp; The Samba view is where the Playlist creation tool will run, but Twonky must use the "Linux view".&nbsp; This will effect playlists with absolute paths are used.
+
* Twonky is agnostic to "\" or "/" dir separators, however it cannot "fix" mappings between diffferent views of the same file system.&nbsp; For example a media library on a NAS with Twonky installed will have a "Linux view" that is used directly by Twonky.&nbsp; The same files will also be available over a SAMBA view (on Windows clients).&nbsp; The Samba view is where the Playlist creation tool will run, but Twonky must use the "Linux view".&nbsp; This will effect playlists with absolute paths are used<br>
  
 
Most playlist creating tools default to producing playlists with absolute links to items.
 
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.
 
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.
 
+
<br>  
<br>
 
 
 
 
== <br>Playlist creation tools ==
 
== <br>Playlist creation tools ==
  
 
The following table lists the behaviours of common playlist creation tools
 
The following table lists the behaviours of common playlist creation tools
 +
 +
Ensure that the Playlist is saved as a '''.M3U'''file 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
  
 
<br>
 
<br>
Line 82: Line 42:
 
| as above
 
| as above
 
|-
 
|-
| MEDIAMONKEY
+
| [http://www.mediamonkey.com/ MEDIAMONKEY]
 
| M3U
 
| M3U
| local files relative, (I'm guessing relative to Playlist location...)
+
| 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<br>
 
|-
 
|-
 
| MP3TAG
 
| MP3TAG
Line 90: Line 50:
 
| fully qualified drive and path for local files
 
| fully qualified drive and path for local files
 
|}
 
|}
 
== More tools ==
 
 
* Album art aggregator (find missing album art for your digital music collection) http://team.thenexusnet.com/nexus/AAA/
 
* Ripcaster&nbsp;(contains links to various useful&nbsp;tools) https://www.ripcaster.co.uk/node/120
 
* Tag and rename (multi-format tagging tool) http://www.softpointer.com/tr.htm
 

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