Page 8 of 28

Re: Export M3U/Playlists for Child Nodes 2.9 (2010-04-22)[MM2+3]

Posted: Wed May 19, 2010 12:45 pm
by Lowlander
ZvezdanD wrote:Which format you have selected in this add-on (ANSI, UTF-8)
I have ANSI selected in Export M3U's/Playlists. Take in account that this is an occasional failure that the NAP can't read the playlist. Rescanning the playlists on the NAS itself also seems to fix the issue.

Re: Export M3U/Playlists for Child Nodes 2.9 (2010-04-22)[MM2+3]

Posted: Wed May 19, 2010 12:50 pm
by Lowlander
ZvezdanD wrote:Well, this should go to the Bug Reports forum. It is not my fault that MM built-in SelectFolder dialog box doesn't support network drives for initial folder.
Added here: http://www.ventismedia.com/mantis/view.php?id=6368

Re: Export M3U/Playlists for Child Nodes 2.9 (2010-04-22)[MM2+3]

Posted: Wed May 19, 2010 2:28 pm
by ZvezdanD
Lowlander wrote:
ZvezdanD wrote:Which format you have selected in this add-on (ANSI, UTF-8)
I have ANSI selected in Export M3U's/Playlists. Take in account that this is an occasional failure that the NAP can't read the playlist. Rescanning the playlists on the NAS itself also seems to fix the issue.
Well, I really don't have any other idea what is a reason for that. Are you absolutely sure that you didn't have selected UTF-8 when this happened? Are you still getting incorrect playlists? Could you send me one for observation? How often you have automatic export? Maybe modification date and/or size of playlist files is not changed when this happens, so NAS cannot recognize that playlist is changed?

Re: Export M3U/Playlists for Child Nodes 2.9 (2010-04-22)[MM2+3]

Posted: Wed May 19, 2010 3:08 pm
by Lowlander
Playlist would be changed as it is a random subset of a larger number of tracks. They were set to be created on exit of MediaMonkey, which frequency depends on how often it crashes. No never modified the setting so UTF-8 wouldn't have been selected.

Did the filed bug reports capture the bugs correctly?

Re: Export M3U/Playlists for Child Nodes 2.9 (2010-04-22)[MM2+3]

Posted: Wed May 19, 2010 4:08 pm
by ZvezdanD
Lowlander wrote:They were set to be created on exit of MediaMonkey, which frequency depends on how often it crashes.
Maybe you should try to set automatic export during startup instead of shutdown.
Lowlander wrote:Did the filed bug reports capture the bugs correctly?
Yes.

Re: Export M3U/Playlists for Child Nodes 2.9 (2010-04-22)[MM2+3]

Posted: Wed May 19, 2010 4:11 pm
by Lowlander
ZvezdanD wrote:Maybe you should try to set automatic export during startup instead of shutdown.
I changed from startup as MediaMonkey wouldn't be available for use until the script finished, which in my case was taking too long for me. Now if the script would run after startup of MediaMonkey (ie I could start using MediaMonkey while the script runs) it would no longer be a problem for me.

Re: Export M3U/Playlists for Child Nodes 2.9 (2010-04-22)[MM2+3]

Posted: Thu May 20, 2010 2:02 am
by ZvezdanD
Lowlander wrote:I changed from startup as MediaMonkey wouldn't be available for use until the script finished, which in my case was taking too long for me. Now if the script would run after startup of MediaMonkey (ie I could start using MediaMonkey while the script runs) it would no longer be a problem for me.
You could try new release: v2.9.3 - 2010-05-20
* Fixed: automatic export on startup, now with 1 second delay to enable loading of main window.

Re: Export M3U/Playlists for Child Nodes 2.9 (2010-04-22)[MM2+3]

Posted: Thu May 20, 2010 12:40 pm
by nynaevelan
ZvezdanD wrote: * Fixed: automatic export on startup, now with 1 second delay to enable loading of main window.
Z:

What line would I change to increase this from 1 second to more of a time delay??

Re: Export M3U/Playlists for Child Nodes 2.9 (2010-04-22)[MM2+3]

Posted: Thu May 20, 2010 1:13 pm
by ZvezdanD
nynaevelan wrote:What line would I change to increase this from 1 second to more of a time delay??
Line 38, value is in milliseconds: Const iEXPORT_ONSTARTUP_DELAY_MS = 1000

Re: Export M3U/Playlists for Child Nodes 2.9 (2010-05-20)[MM2+3]

Posted: Fri May 21, 2010 5:34 am
by nynaevelan
Thanks, that helped alot. :D

Re: Export M3U/Playlists for Child Nodes 3.0 (2010-05-22)[MM2+3]

Posted: Sat May 22, 2010 11:50 am
by ZvezdanD
There is a new version: 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).

Re: Export M3U/Playlists for Child Nodes 3.0 (2010-05-22)[MM2+3]

Posted: Sat May 22, 2010 12:09 pm
by nynaevelan
ZvezdanD wrote:There is a new version: 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);
Is this an additional option or does it replace the previous method of using a directory structure??

Re: Export M3U/Playlists for Child Nodes 3.0 (2010-05-22)[MM2+3]

Posted: Sat May 22, 2010 5:02 pm
by ZvezdanD
nynaevelan wrote:Is this an additional option or does it replace the previous method of using a directory structure??
It is additional option. If it replaces existing method, I would not call it "Added: option", right? ;)

If you take a look at the screenshot of the new Options dialog box in the first post of this thread, you would see that there are still "Export to parent folders" and "Export to child folders" options, beside of this new "Export to single folder" option.

Re: Export M3U/Playlists for Child Nodes 3.0 (2010-05-22)[MM2+3]

Posted: Sat May 22, 2010 6:00 pm
by nynaevelan
Thanks for clarifying and excusing my laziness in looking for the answer myself. :)

Re: Export M3U/Playlists for Child Nodes 3.0 (2010-05-22)[MM2+3]

Posted: Sat May 22, 2010 6:12 pm
by nynaevelan
I have another question, and hopefully this is not something you have already covered: I have the auto function setup to export to parent folders on a daily basis, if I should run a manual export to a single folder, will that mess up the options on the auto export the next time it is run?