Some thoughts about mpl files.
Playing around with MPL playlists I found out that these files would a nice alternative
for MJ database backup. The nice thing about it is that you can save all the data from the database
for a only subset of your library. This is a nice way to split a library.
This is nearly perfect for that purpose with the exception of two things :
1/ The fields year and date are not currently saved in mpl playlists (8.0.203)
2/ It would be great to save the media and image file name with their relative paths.
(relative to the location of the .MPL file)
What would be the benefits of such modified mpl files ?
1/ They could act as a replacement or a complement for any tagging system.
2/ This would work for any media format that MJ supports.
3/ mpl are editable outside MJ with a simple text editor (xml)
4/ Instead of importing your file types (mp3, mpc, ape) you would instead only
import mpl files which is much faster.
5/ If you burn a cd-rom archive with your media files along with the corresponding mpl file
you simply copy all the cd-rom directory tree to one of your HDD and import the mpl.
6/ By 'relativizing' media and image file paths you could simply drag and drop complete
directory trees or sub-trees from one HDD to another, provided you have created a mpl file
at the root of those trees. You can then simply split & merge sub libraries.
I really think that mpl files are more than just a playlist format.
what do you think ?
Author
Topic: A perspective for MPL files (Read 839 times)