Revision history for IDfile


Revision [830]

Last edited on 2015-05-28 23:19:55 by AdminUser
Additions:
If your target is limited to a maximum number of items it can manage, you can use this to give a warning if the maximum is exceeded. If the anaylisis is finished and there would be more than// ""MaxItemsOnTarget""// on the target, you will be promptet to continue. If there is no maximum just enter 0 or comment that line.
Deletions:
If your target is limited to a maximum number of items it can manage you can use this to give a warning if the maximum is exceeded. If the anaylisis is finished and there would be more than// ""MaxItemsOnTarget""// on the target, you will be promptet to continue. If there is no maximum just enter 0 or comment that line.


Revision [829]

Edited on 2015-05-28 23:14:38 by AdminUser
Additions:
Contains all allowed characters for the paths on your target as RegExp expression. So any file/folder will get filtred and all characters which are **not **whitelisted here will be omited.
||""WhiteListChrs""||no||no||1||none||ok||
Deletions:
Contains all allowed characters for the paths on your target as RegExp expression. So any file/folder will get filtred and all characters which are not listed here will be omited.
||""WhiteListChrs""||no||yes||1||none||ok||


Revision [824]

Edited on 2015-05-03 13:00:20 by AdminUser
Additions:
__Useful Scenario__: You could have prefixes in foobar2000 in your playlist-names and use //""PLselectRegEx""// to control which playlists to sync to a target. But you don't want to show the playlist-prefix on the targets. To achieve this, you will do search&replaces with //""PLfileNameRegExRepl""// (simply replace the prefixes with //nothing //).
Deletions:
__Useful Scenario__: You could have prefixes in foobar2000 in your playlist-names and use //""PLRegExInclude""// and/or //""PLRegExExclude""//, to control which playlists will be on what targets. But you don't want to show this playlist-prefixes on your targets. To achieve this, you will do search&replaces with //""PLfileNameRegExRepl""// (simply replace the prefixes with //nothing //).


Revision [819]

Edited on 2015-05-03 12:26:58 by AdminUser [Version 0.9.8]
Additions:
**__Comments in configuration files__**
**__Below sections each contain a table with following information:__**
=====General sections=====
====""MaxSizeOnTarget""====
You may want to limit the total size of items on the target. You can do so by useing //""MaxSizeOnTarget""//. When the anaylisis is finished and more space would be required, you will be prompted to continue.
||""MaxSizeOnTarget""||yes||no||1||none||ok||
||(x:6)%%'simply specify the maximum size of all items in MB, that should be allowed on target.
MaxSizeOnTarget=4000%%||
=====Media Library =====
=====Playlists=====
====""PLselectRegEx""====
(Replaces former configuration sections ""PLRegExExclude"" and ""PLRegExInclude"")
Allows you to include and exclude playlists.
Each playlist in your ""foobar2000"" will be checked against the configured regular expression.
||""PLselectRegEx""||no||no||1||none||ok||
' will only include lists which start with '_'
PLselectRegEx=^(?=.*(?:^_|nothing|nothing))(?!.*(?:nothing|nothing|nothing))
' will include all playlists but exclude 'pop' and 'popular'
PLselectRegEx=^(?=.*(?:.*|nothing|nothing))(?!.*(?:pop|nothing|nothing))
' will include all playlists but exclude 'pop' but not 'popular'
PLselectRegEx=^(?=.*(?:.*|nothing|nothing))(?!.*(?:$pop$|nothing|nothing))
====""PLfileDir""====
Leave empty for root folder.
||""PLfileDir""||no||no||1||none||ok||
||(x:6)%%PLfileDir=Playlists%%||
====""PLfileFormat""====
Defines the format of your playlist-files (files, that contain a list of elements).
||""PLfileFormat""||yes||no||2||none||ok}}||
||(x:6)%%' will create simple, ANSI-based m3u-files
PLfileFormat=m3u,ANSI
' will create extented, Unicode-based m3u-files
PLfileFormat=M3Uext,Unicode%%||
|=|Parameter|=|value|=|meaning||
||(y:4)1||(x:2)__Defines the playlist-file-format__:||
||M3U||simple format (paths only)||
||M3Uext||extented format. Read about it ([[http://en.wikipedia.org/wiki/M3U|explained here]]). To customize the format of the title-display see //""PLfileTitleFormat""// below.||
||...||other formats like PLS may follow - if anybody nees that let me know.||
||(y:3)2||(x:2)__Defines the codepage inside playlist-files__:||
||ANSI||Use codepage ANSI inside playlist-files||
||UNICODE||Use Unicode (exact codepage is "UCS-2 little endian")||
====""PLfileTitleFormat""====
will define the display-format (used by some players) for playlist-elements. Only **extented M3U playlists** do support that! If omited, default is ''[%Artist% - ][%Title%]''.
Additional format //""%_TrackNumber%""// and //""%_PlaylistName%""// must only used here!
||""PLfileTitleFormat""||yes||no||1||none||ok||
||(x:6)%%PLfileTitleFormat=This is track %_TrackNumber% in playlist %_PlaylistName%, [Artist: %Artist%][, Title: %Title%]%%||
====""PLfileNameRegExRepl""====
will enable you to influence the playlist-__filenames__ (M3U-files) on the target, with one or more search&replace operations. This function does only influence the **filenames** of M3U-files, not the items inside! Again, a RegEx expression is used for this job.
__Useful Scenario__: You could have prefixes in foobar2000 in your playlist-names and use //""PLRegExInclude""// and/or //""PLRegExExclude""//, to control which playlists will be on what targets. But you don't want to show this playlist-prefixes on your targets. To achieve this, you will do search&replaces with //""PLfileNameRegExRepl""// (simply replace the prefixes with //nothing //).
Example below: A playlist with name ''""FoobarSync Tutorial""'' in foobar2000 would have the filename ''""Test Run.m3u""'' on the target but a playlist with name 'Tutorial #2' would not get changed.
||""PLfileNameRegExRepl""||yes||yes||2||*||ok||
||(x:6)%%' \\ regular expression !
PLfileNameRegExRepl=FoobarSync*Test
PLfileNameRegExRepl=Tutorial$*Run%%||
====""PLitemRegExRepl""====
Gives you the power to do one or more search&replace operations with the **file-paths** __inside__ your m3u-files on the target. Again, a RegEx expression is used for this job.
||""PLitemRegExRepl""||yes||yes||2||*||ok||
PLitemRegExRepl=tmpfolder\\external_sd*\storage\sdcard1\synced
PLitemRegExRepl=\\*/%%||
Deletions:
=====Purpose of configuration files=====
=====Using Comments in configuration files=====
=====Configuration File Sections=====
Below explanations each contain a table with following information:
====""PLRegExExclude""====
By default any playlist in your ""foobar2000"" will get sychronized to your target (if you specified option 'P' in parameter 'Tasks' - see [[CLI|command line parameters]]. This section gives you the chance to __**ex**clude__ playlists.
Each playlist in your ""foobar2000"" will be checked against the comma-seperated list of RegExp search-patterns. Please note that the script will add an asterix in front of and at the end of every playlist name. Therefore the below example will exclude any playlist, that starts with '#' and any playlist which contains 'SQL'. It will exclude playlist 'Rock' but will not exclude 'Good Rock'.
||""PLRegExExclude""||yes||no||1||<comma>||ok||
||(x:6)%%PLRegExExclude=\*#,SQL,\*UPnP,\*Rock,\*tmp%%||
====""PLRegExInclude""====
This section gives you the chance to __**in**clude__ playlists. This is done __after__ //""PLRegExExclude""//. Each playlist in your ""foobar2000"" will be checked against this comma-seperated list of RegExp search-patterns. Please note that the script will add an asterix in front of and at the end of every playlist name; same as above with //""PLRegExExclude""//.
Useful scenario: **Ex**clude all playlists with //""PLRegExExclude""// and choose only specific playlists to sync with //""PLRegExInclude""//.
Below example will include playlist 'Rock', even it it was excluded before by matching a RegExp search of section //""PLRegExExclude""//.
||""PLRegExInclude""||yes||no||1||<comma>||ok||
||(x:6)%%PLRegExInclude=\*Rock\*%%||
>>[! $meta(genre,1)]\Test funktioniert? Beim %Title% wird \ entfernt??>>
MLSyncTargetDir=[! $meta(genre,2)]
MLSyncTargetDir=[! $meta(genre,3)]
====""PlaylistDir""====
'\' means root folder.
||""PlaylistDir""||no||no||1||none||ok||
||(x:6)%%PlaylistDir=Playlists%%||
====""PlayListFormat""====
Defines the format of your playlist-files (m3u).
0 = simple format (default, paths only)
1 = extendet format ([[http://en.wikipedia.org/wiki/M3U|definition here]])
||""PlayListFormat""||yes||no||1||none||ok}}||
||(x:6)%%PlayListFormat=0%%||
====""PLregExRepl""====
Gives you the power to do one or more search&replace operations with the file-paths __inside__ your m3u-files on the target. Again, a RegEx expression is used for this job.
||""PLregExRepl""||yes||yes||2||*||ok||
PLregExRepl=tmpfolder\\external_sd*\storage\sdcard1\synced
PLregExRepl=\\*/%%||


Revision [744]

Edited on 2015-04-18 10:27:36 by AdminUser [Version 0.9.5]
Additions:
====""MaxItemsOnTarget""====
If your target is limited to a maximum number of items it can manage you can use this to give a warning if the maximum is exceeded. If the anaylisis is finished and there would be more than// ""MaxItemsOnTarget""// on the target, you will be promptet to continue. If there is no maximum just enter 0 or comment that line.
||""MaxItemsOnTarget""||yes||no||1||none||ok||
||(x:6)%%MaxItemsOnTarget=1000%%||
====""ReserveFreeSpace""====
You may want to reserve a given amount of free space on the target for other stuff then audio. You can do so by useing //""ReserveFreeSpace""//. When the anaylisis is finished and the estimation would cause less free space after sync, you will be prompted to continue.
||""ReserveFreeSpace""||yes||no||1||none||{{color c="green" text="new, ok"}}||
ReserveFreeSpace=1000%%||
Gives you the power to do one or more search&replace operations with the file-paths __inside__ your m3u-files on the target. Again, a RegEx expression is used for this job.
If your target device is based on Android or Linux, you MUST convert the Windows-like paths to Linux/Unix-conform paths before your target can play any playlist. Example below shows how to do so: First it replaces ''tmpfolder\external_sd'' with ''\storage\sdcard1\synced'' and then replaces all '\' with '/'. As result, a file path could look like this: ''/storage/sdcard1/synced/Pop/an title.mp3''
||(x:6)%%' \\ because it's a regular expression !
PLregExRepl=tmpfolder\\external_sd*\storage\sdcard1\synced
ConvertFormats=Vorbis_Q2*OGG*-vn -c:a libvorbis -ac 2 -ab 96k*96*_q2
||(x:6)%%preCMD=attrib "%1\%2\*.*" -h%*%&%%||
Deletions:
====""MaxTitles""====
If your target is limited to a maximum number of items it can manage you can use this to give a warning if the maximum is exceeded. If the anaylisis is finished and there would be more than// ""MaxTitles""// on the target, you will be promptet to continue. If there is no maximum just enter 0 or comment that line.
||""MaxTitles""||yes||no||1||none||ok||
||(x:6)%%MaxTitles=1000%%||
====""MinSpace""====
You may want to preserve a given amount of free space on the target for other stuff then audio. You can do so by useing //""MinSpace""//. When the anaylisis is finished and the estimation would cause less free space after sync, you will be prompted to continue.
||""MinSpace""||yes||no||1||none||{{color c="green" text="new, ok"}}||
MinSpace=1000%%||
Gives you the power to modify the filepaths inside the m3u-files on your target with a RegExp search&replace pattern.
If your playing device is Android or Linux you will need it because direct sync to the target is not supported. Therefore you will first sync to a folder on your windows-PC and afterwards sync via samba to the playing device. As result the paths in your M3U-files need to be adjusted to the final paths on your playing device.
Below example replaces a part of the path and changes '\' to '/'
If you sync to Linux-targets this will be useful for you - be sure to read [[Linux|this first]]!
||(x:6)%%PLregExRepl=tmpfolder\\external_sd*\storage\sdcard1\synced
ConvertFormats=###*OGG*-vn -c:a libvorbis -ac 2 -ab 96k*96*_q2
||(x:6)%%preCMD="attrib "%1\%2\*.*" -h%*%&%%||


Revision [650]

The oldest known version of this page was created on 2015-04-11 13:28:58 by AdminUser [Version 0.9.5]
Valid XHTML :: Valid CSS: :: Powered by WikkaWiki