Export M3Us/Playlists for Child Nodes 3.6 (2012-01-09)[MM2+]

[MM3 monkey]

ZvezdanD, I've uninstalled this script for now.

Can I delete the [ExportM3UsForChildNodes] section in MediaMonkey.ini? I'm using MM4.

[ZvezdanD]

ZvezdanD, I've uninstalled this script for now.

Can I delete the [ExportM3UsForChildNodes] section in MediaMonkey.ini? I'm using MM4.

Yes, if you don't want to use this add-on anymore or you don't mind to enter again the same settings if you decide to install it again. You already had that choice during the uninstall when the add-on asked if you want to remove the settings from the .ini file as well. Although, I don't know how much those 10-20 additional lines in the .ini file could change things. Do you expect that the program would run faster after you remove those lines?

[MM3 monkey]

I just want to get my MM4 as near to a clean install as possible. Thanks ... and thanks for all the great scripts and quick, full answers and help etc. etc.

[Guest]

Hello,

In reference to this topic,

http://www.mediamonkey.com/forum/viewtopic.php?f=4&t=60769

I can't seem to get this add-on working with the latest build of MM4.

Will it be possible for the options dialog box be integrated with the Option dialog box from MM4?

Thanks.

[nynaevelan]

You have not said here or in the referenced thread what trouble you are having getting the script to work for you in MM4.. I can state that this script does indeed work with both MM3 and 4. Perhaps if you state what you have done and what you are trying to accomplish someone will be able to assist you in getting it up and running.

Nyn

[monkeyfan1970]

You have not said here or in the referenced thread what trouble you are having getting the script to work for you in MM4.. I can state that this script does indeed work with both MM3 and 4. Perhaps if you state what you have done and what you are trying to accomplish someone will be able to assist you in getting it up and running.
Nyn

Hello,

Thanks for the reply. My apologies! I manage to get the add-on working!

Will it be possible for the options dialog box be integrated with the Option dialog box from MM4?

My apologies again! The settings are neatly integrated in the Options dialog box!

Now I have a new set of problem

Here is the task I am trying to achieve.

I have E:/Music/Playlist. Where all my playlist are located. I have also added the playlist in my watch folders. Now evey time I launch MM, all my playlist are listed in "Imported Playlists" sub-node.

I have installed this addon and I have specified the folder that the script to auto export on shutdown - "E:/Music/Playlist".

Now every time I launch MM, there are new sets of duplicates of the playlists. And there is also a "Imported playlists -" prefix in the name of .m3u files. How can I remove it?

How can I set this script to always overwrite the playlist in the folder and when launch of MM, there are no duplicates in playlists node?

Thanks.

[nynaevelan]

Now I have a new set of problem

Here is the task I am trying to achieve.

I have E:/Music/Playlist. Where all my playlist are located. I have also added the playlist in my watch folders. Now every time I launch MM, all my playlist are listed in "Imported Playlists" sub-node.

These are being imported by MM because you have this folder being monitored by MM. First why are you exporting the playlists out of MM and then using MM to watch and import them back into the db?? If they are already in the db why do you want them as a part of your monitored folders??

Now every time I launch MM, there are new sets of duplicates of the playlists. And there is also a "Imported playlists -" prefix in the name of .m3u files. How can I remove it?

How can I set this script to always overwrite the playlist in the folder and when launch of MM, there are no duplicates in playlists node?

Thanks.

If your location for your exported playlists has not changed, they should be exporting to the same location, as far as I know there isn't a way for the script to avoid what is imported because it is MM that is importing the playlists back into MM. But keep in mind, the next time the export is run, it will export all the existing playlists which will include the duplicates as well and you will end of with duplicates of duplicates before long.

[monkeyfan1970]

These are being imported by MM because you have this folder being monitored by MM. First why are you exporting the playlists out of MM and then using MM to watch and import them back into the db?? If they are already in the db why do you want them as a part of your monitored folders??

Thanks for your reply.

Why would I want to do that? Simple. I always want to have the latest physical [not really physical ] .m3u version of my playlist in the folder E:/Music/Playlist exported automatically. And I also want MM to watch that playlist folder to load from.

I understand that MM keeps the playlist in it's DB and I also realise how MM treats it's playlists. I don't really like the way it treats music files and playlist files differently in the watch folder. Example : I configure MM to watch E:/Music and E:/Music/Playlist. If there are 10 songs in E:/Music/ MM loads them and if I delete them, the songs also are removed from MM. But for Playlist it is different. I placed 10 playlist in E:/Music/Playlist and MM lists them in "Imported Playlists" sub-node [I am fine with that] but when I delete the playlist from E:/Music/Playlist , the playlist are still listed in the "Imported Playlists" sub-node. I believe that there should be an option for this for users who want playlist not stored in DB permanently. MM also ignores the unique filename/playlist name of .m3u files. It should technically overwrite the playlist with the same name. I will request this in the wish list section. I think if this behavior is implemented, there will not be any duplicates.

Please share your thoughts.

Thanks.

[ZvezdanD]

I always want to have the latest physical [not really physical ] .m3u version of my playlist in the folder E:/Music/Playlist exported automatically. And I also want MM to watch that playlist folder to load from.

If I understand correctly, you could do that with this add-on without duplicating playlists. I think that you should specify "Imported Playlists" in the From field and E:/Music/Playlist in the To field. The Export selected node too option should be turned off in your case.

[monkeyfan1970]

If I understand correctly, you could do that with this add-on without duplicating playlists. I think that you should specify "Imported Playlists" in the From field and E:/Music/Playlist in the To field. The Export selected node too option should be turned off in your case.

Hello,

Thanks for sharing.

But there will still be duplication if I create a playlist in MM and if the script exports it to E:/Music/Playlist on shutdown. When I relaunch MM there will be two playlists.

I have yet to find a work-around.

Thanks.

[ZvezdanD]

there will still be duplication if I create a playlist in MM and if the script exports it to E:/Music/Playlist on shutdown. When I relaunch MM there will be two playlists.

You are right. It seems to me as the program bug. I don't understand why MM creates the new playlist with the same name as the manually created playlist in the "Imported Playlists" folder. Anyway, I think that the workaround exists, but it is too complicated:
- create playlist anywhere (not necessarily in the "Imported Playlists" folder);
- export it manually to the E:/Music/Playlist folder;
- remove that playlist (if you created it in the "Imported Playlists" folder);
- use Add/Rescan Tracks to the Library option with selected E:/Music/Playlist folder and selected .m3u extension.

You should do that only when you want to create new m3u files, but not when you modify some of them.

[monkeyfan1970]

You are right. It seems to me as the program bug. I don't understand why MM creates the new playlist with the same name as the manually created playlist in the "Imported Playlists" folder. Anyway, I think that the workaround exists, but it is too complicated:
- create playlist anywhere (not necessarily in the "Imported Playlists" folder);
- export it manually to the E:/Music/Playlist folder;
- remove that playlist (if you created it in the "Imported Playlists" folder);
- use Add/Rescan Tracks to the Library option with selected E:/Music/Playlist folder and selected .m3u extension.

You should do that only when you want to create new m3u files, but not when you modify some of them.

Thanks for the workaround! I have tried this method before. But it is not really automated when you have to perform these steps manually.

Actually I try to explain this duplication problem in these thread but the developer feels it is not important to rectify it.

Option to allow MM not to store playlist permanently in DB.

I hope the developer solves this problem.

Thanks.

[ZvezdanD]

I have tried this method before. But it is not really automated when you have to perform these steps manually.

As I said, only the newly created playlists requires their manual export, but the modification of m3u files would be automatically executed using this add-on. You need to create the playlists manually anyway, so I don't see these few additional steps as a big problem.

You don't need to manually export newly created playlists one by one - you could create bunch of playlists stored in some temporary folder in the Playlists branch, then manually export them all at once using this add-on, and after that you could apply Add/Rescan option or just restart the program which would automatically import newly created m3u files on the start-up.

[Thorden]

Hi, and thanks for this wonderful extension!

I have one major problem using it, guess it's a bug:
I need to replace the M3U entries from the native format: \\<server name>\<share>\<artist>\<album>\<title>
to: <artist>\<album>\<title>

Now, this should be easy, just replace \\<server name>\<share>\ with nothing, right?
Yes, that works just fine. Until I start MM over again, then the "with:" field changes from blank to the default of \Playlists\

So when doing automatic exports, all playlists are overwritten with references to a non existing path (\Playlists\).

I absolutely need the <artist>\<album>\<title> format just like that, it's the only way both Squeezebox server and Synology Audio Station will work correctly with playlists. They both run on different NAS boxes.

Thanks!

[ZvezdanD]

I have one major problem using it, guess it's a bug

Thanks for the report. There is the new release, v3.5.3 - 2011-10-26:
* Fixed: empty string specified in Options box (e.g. with: text box) replaced with default value after restart;
* Fixed: From text box for auto-export in Options box now accepts manually entered nested playlists using "\" as separator.