that'll work.
You'll need the full treepath of the playlist only if the playlist names are not unique. For example, I have a playlist called "Dylan" and another called "Dylan Covers".
If I want to use these in areas where MC does not provide the "playlistid" value for us, I need to use the exact treepath, as simply saying [playlist]=dylan will pull results from both lists.
Also remember that when used like this with square brackets, the search becomes case sensitive... [playlist]=[audio\dylan] and [playlist]=[Audio\Dylan] are not the same.
If the playlist names are unique, you can write the ~mix string a lot more quickly like so:
~mix=1000,20%,{p=playlistA},30%,{p=playlistB},50%,{p=playlistC}Wrapping each search in curly braces is not essential with this particular ~mix, but I feel it's a good habit to get into when writing these things as when the day comes that you have a search string in there that contains a comma for example, you will need those curly braces, and if you use them all the time any way, it's one less thing to worry about
-marko.