Export M3U/Playlists for Child Nodes 3.3 (2010-07-13)[MM2+3]

[ZvezdanD]

Description:
This add-on is for use with MediaMonkey v2.x or v3.x. It has two operation modes, manual and automatic. In the manual mode it allows batch export of .m3u files or creating of playlists for each child node of the node selected in the tree panel. For example, if you select the Playlists node, you would export .m3u files for all playlists in the Library. This works with almost all nodes, even the Magic Nodes. In the automatic mode this add-on periodically saves specified playlist node and/or its sub-nodes from the Playlists branch.

M3U files/playlists are saved in a hierarchically organized folders within the specified parent folder, using the same structure as sub-nodes of the selected node, or could be saved in single folder using specified string as separator. M3U files could be saved in ANSI, UTF-8 or Unicode, in simple or extended .m3u format. Track paths could be URL encoded and stored absolute or relative to the .m3u file path using Windows "\" or Unix "/" folder separator. If the relative path option is turned off, the paths stored in .m3u files would be same as they are in the Path field of the database, but could be also replaced with the user-defined replacement, e.g. "c:\Documents and Settings\" could be replaced with "e:\My Mysic\".

Paths that you want to replace could be specified using Regular expressions, e.g. "^.+\\(?=[^\\]+\.[^\.\\]+$)" is the expression which represents any full path, excluding the filename and the extension. So, using that expression, if you leave the with: text box empty, all folders would be removed from paths, saving only filenames and extensions into .m3u files. Or you could enter "e:\Playlists\" and all folders would be replaced with that single one.

This add-on also allows copying of audio files and export of selected tracks only.

Download:
http://solair.eunet.rs/~zvezdand/Export ... bNodes.htm



What is new:
v3.3 - 2010-07-13
* Added: Export As .m3u Playlist command to the main tracklist and Now Playing context menu which allows export of selected tracks only.

v3.2 - 2010-07-02
* Changed: Unix folder separator option to Unix .m3u file format; a .m3u files would have both the "/" as a separator and a new line without a carriage return when this option is turned on.

v3.1 - 2010-06-21
* Added: Export M3Us & Copy Files for Child Nodes command which allows copying of audio files beside of exported .m3u files.

v3.0.1 - 2010-05-23
* Fixed: error with URL paths in .m3u files and ANSI/Unicode formats.

v3.0 - 2010-05-22
* Added: option to export all .m3u files to single folder using specified string as separator between node names in .m3u filenames (e.g. e:\Playlists\Rock - Pink Floyd - Dark Side of the Moon.m3u, using " - " as separator);
* Added: option to store URL encoded paths in .m3u files (e.g. file:///C:/Temp/%D0%97%D0%B2%D0%B5%D0%B7%D0%B4%D0%B0%D0%BD.mp3).

v2.9.3 - 2010-05-20
* Fixed: automatic export on startup, now with 1 second delay to enable loading of main window.

v2.9.2 - 2010-04-22
* Fixed: export with First level and Last level of nodes only options for the All nodes in Location and My Computer branches.

v2.9.1 - 2010-04-20
* Fixed: error when the Create playlists for child nodes sub-menu is displayed if the last created playlist doesn't exist, e.g. if you start MM with another database file.

v2.9 - 2010-04-05
* Added: option to save .m3u files/create playlists for the last (deepest) level of nodes only;
* Added: option to save paths in .m3u files using Unix separator ("/") instead of Windows ("\");
* Improved: speed of displaying menu with playlists if there are many of them;
* Changed: the list of playlists in the Options dialog box is now limited to playlists on the first level because the large number of nested playlists have slowed down its display; if you need to specify some nested playlist, you could still write it using "\" as a separator between nested levels.

v2.8 - 2009-08-25
- Added: option to save .m3u files in child folders, i.e. one level more in depth (until now they are saved to parent folders only).

v2.7 - 2009-07-08
- Added: option to replace folders in .m3u files with specified string;
- Added: option to remove Byte-order mark (BOM) from the begin of UTF-8 files.

v2.6.1 - 2009-04-21
- Fixed: error with Options sheet and playlists with duplicated names.

v2.6 - 2009-04-20
- Added: option to create a new dated folder once in a day.

v2.5 - 2009-04-20
- Added: option for an automatic export on startup;
- Added: option to create a new folder with a date/time in its name for every auto-export.

v2.4 - 2009-04-19
- Added: option to automatically export specified playlists on shutdown or periodically with customizable time interval.

v2.3 - 2009-04-17
- Added: option to exclude AutoPlaylists from export.

v2.2 - 2009-04-16
- Added: option to save .m3u files in simple or extended format;
- Improved: speed when export nodes from Playlists branch.

v2.1 - 2009-02-25
- Added: option to save .m3u files as ANSI, UTF-8 or Unicode.

v2.0 - 2009-02-12
- Added: possibility to create playlists in the Playlists node in similar way as export of .m3u files.

v1.4 - 2009-01-24
- Improved: speed with MM 3.1.0.1218 and up, especially for empty nodes/folders.

v1.3 - 2009-01-10
- Added: option to export the playlist for the parent (selected) node (beside of child nodes);
- Added: option to exclude unavailable tracks from export;
- Improved: speed and work with the All nodes from My Computer and Location branch;
- Fixed: relative paths;
- Fixed: playlist filenames for some Magic Nodes, e.g. Album Artist with Album (MN v2.0 or up required).

v1.2.1 - 2008-11-29
- Fixed: export when turned on the Regular expressions option and turned off the Skip for folders option.

v1.2 - 2008-11-29
- Added: an option to store track paths relative to the playlist path (default setting as it is in MM);
- Added: an option to skip export of playlists for specified nodes/folders (e.g. DiscXX for multi-CD);
- Added: an option to use Regular expressions for specifying nodes/folders;
- Added: an option to exclude files with specified extensions from export;
- Added: skipping of All node (even for Magic Nodes) and playlist files from My Computer branch from export;
- Fixed: unresponsive program with 100% CPU when trying to export an empty node/folder (e.g. in My Computer node).

v1.1 - 2008-11-28
- Added: an option to recursively scan all sub-levels of the selected node (default setting), playlists are stored in a hierarchically organized folder structure, same as with the selected node.

v1.0 - 2008-11-27
- First public version.

Installation:

• For MediaMonkey 3.x - just double-click on the ExportM3UsForSubNodes.mmip file; if you are on Vista make sure you have MM3 set to "Run as Administrator"; if you downloaded the installation package with IE7 and it changed its extension to a .zip, you should first change it back to a .mmip.
• For MediaMonkey 2.x - rename a .mmip extension to a .zip, extract the ExportM3UsForSubNodes.vbs file to the MediaMonkey's "Scripts\Auto" folder and restart MM program.

Usage:
Select a node whose child nodes you want to export playlists, then:
- choose Export M3Us for Child Nodes... command from the File menu or the context menu of the tree panel if you want to export .m3u files; after that you should specify the parent destination folder on the disk;

- choose Export M3Us & Copy Files for Child Nodes... command from the File menu or the context menu of the tree panel if you want to export .m3u files and to copy audio files; after that you should specify the parent destination folder on the disk;

- choose Create Playlists for Child Nodes command from the File menu or the context menu of the tree panel if you want to create playlists that would be stored in the Playlists branch; after that you should specify the parent playlist node.

If you want to export just selected tracks, choose Export As .m3u Playlist... from the context menu of the main tracklist or Now Playing panel.

Add-on settings are in the Tools / Options dialog box within Export M3Us/Playlists tab.

Limitations:
Refreshing of the tracklist panel works very strange in MediaMonkey 2.x and because of that the user needs to click on the confirmation dialog after every generated playlist, i.e. for every sub-node. This confirmation dialog is not needed with MM 3.x, but speed and reliability are much better if you have installed MM 3.1.0.1218 or up. Nodes within the Playlist branch don't have such limitation, only regular nodes.

[nynaevelan]

ZvezdanD:

This script has some great potential but I am running into a problem for nodes which have alot of child nodes. I tried it on a node which had 3 children and each of them had 250 children. It exported the three children but not playlists for the 250 children of each node. I tried it on one of the 3 children and it did export the 250 child nodes as playlists. It seems to only process the first child node and none of the child nodes after. This is something that I would enjoy using but I do not have many nodes which I would export which only have one level. I can think of some instances where I wouldn't want it to export the children but also instances when I would. Is it possible to have an option to export just the top level or all existing levels? And if you can add it, can the exports be in the same folder structure as they exist in the node?

Nyn

[ZvezdanD]

Well, I though about a possibility to recursively go into all sub-levels of selected branch, but in that case I don't know where to store playlists. It could work if all tracks from some node are in the same folder, e.g. if I have one artist on the first level and its albums on the second level, so I could write playlists for each album into corresponding folders. But where to save playlist file if its node contain tracks from many folders? For example, I have the Year node which contain sub-nodes from many years, and each year contain tracks from different folders... In that case nodes don't have same folder structure as you mentioned.

[nynaevelan]

I guess that would apply if you are savng the playlists in the same folder as the tracks. But here I have my playlists saved in a separate folder, so the only structure which I would want is the same as the node(s) in MM. But if you are saving them in the same directory as the track, how about saving it in the first location that the tracks exists in. But if you are saving them in multiple locations, wouldn't this make using them more difficult since you would have to look in many locations for the playlists?

Nyn

[ZvezdanD]

Actually, I prefer to store playlists within parent folders of contained tracks. Here is an example how I have organized tracks: <Genre>\<Artist>\<Album>. So, if I select Pink Floyd node which contain nodes "The Piper at the Gates of Dawn", "A Saucerful of Secrets", "More", ... I could store each playlist into folder with contained audio tracks, just because each album has corresponding folder, i.e. connection is unique and unambiguous. But, now if I have Year node which contain nodes 1967, 1968, 1969, ... they could contain tracks from many artists and albums beside of Pink Floyd, and because I don't have folder level for the Year I don't know where to store playlists for corresponding years.

If I understand correctly your suggestion, I could have audio tracks for example in d:\My Music\Rock\Pink Floyd\The Piper at the Gates of Dawn, d:\My Music\Rock\Pink Floyd\A Saucerful of Secrets ..., and playlists into some another location, for example e:\My Playlists\Rock\Pink Floyd\The Piper at the Gates of Dawn, e:\My Playlists\Rock\Pink Floyd\A Saucerful of Secrets, ... Well, I don't see a point to put playlists into some new folder structure into some another location which is not connected with audio tracks when I already have same folder structure with audio tracks. When I have playlists organized into folders and their sub-folders, it doesn't matter if they are stored into d:\My Music\... or e:\My Playlists\..., right?

Anyway, I could add a possibility to this script to recursively store all playlists into location(s) wherever you want, but you should explain me exactly where this should be done because I don't have any idea. This solution should be general and it should work for every possible situation with different nodes, not only Artist and Album, but also Year, Conductor, Classification, custom created nodes...

[ZvezdanD]

By the way, i have one stupid question. Is it correctly to say "Child Nodes" or "Children Nodes"? You know, my English is not very well.

[nynaevelan]

I'm a native English speaker but don't quote me on correct grammar, but I think Child Nodes is the correct term.

Here is how mine is stored, I have my tracks stored in folders by Genre and that is it. But my playlists are stored in a separate folder based on how the playlists are stored in MM (...\My Playlists\...). Because I use my playlists between many computers I do not want them scattered all over, just one parent folder for me to grab up and be on the go. To use this script as I use the other Export M3U scripts I need for it to be able to maintain the node structure as it is in MM, that way when I use the import M3U feature of DEISync, I can have the file structure whether I have the custom node installed or not. Here is a pic of part of my file structure to give you an idea of what I need. BTW my playlists have a more structured hierarchy than my tracks, once again I need simplicity there to make it easier to move the tracks back and forth on my player and to use the Custom Report script to run reports comparing data between my player and MM.



Nyn

[ZvezdanD]

OK, I will try to add recursion, but I am now just wondering what about a path? It is currently stored in absolute form, i.e. d:\My Music\Rock\ When you transfer your playlists to some another computer it could not have same drive letters, nor root folders. How about portable players, which kind of path they should have? Maybe I should store relative path to files, e.g. ..\Rock\.

[nynaevelan]

Personally I prefer absolute paths and yes I have all my computers setup to use the same path to ensure minimal problems, but I think to cater to a wider audience relative paths might be best. And the path on my player is different but the script shouldn't have to worry about that because my syncing is based on the playlists within MM and MM will make the necessary changes when syncing to the player(s).

BTW, I am sorry for taking the focus away from your original intent.

Nyn

[ZvezdanD]

You should not be sorry. This is exactly my intent, since I already planed such thing for the next version.

[ZvezdanD]

There is a new version of the script.

[nynaevelan]

Thanks for the quick update and it is quicker now also. Thanks for adding another script to my arsenal.

Nyn

[ZvezdanD]

I am not sure about the speed increase, but the script intentionally is slowing down its execution with one loop because it need to wait for MM to refresh tracklist when node is changed. This is a main reason why things could go wrong, since MM don't expose necessary event for detection when the tracklist is finished with refreshing. I tried to do my best to eliminate unneeded results, but there is some small possibility that sometimes script could not detect that tracklist has any track because MM is not fast enough to refresh it and in that case playlist wouldn't be created at all. So, I recommend to check a result of the script execution, at least in the begin.

By the way, there is a new version of the script (1.2) with some additions and removed one critical bug.

[nynaevelan]

ZvezDanD:

Version 1.2 does not seem to be working for me, it doesn't export any playlists. Here are my settings:



Nyn

[ZvezdanD]

Sorry. There is a fixed version. Thanks for the report.