afriend wrote: > Ok, one more thing. Using your example try this: > > in the web UI home menu, go to CS and create *2 different filter > _sets_*. > - Leave the *first* filter *set* empty or at least *don't* include a > rule to skip "Revolution #9". > - In the *second* filter *set* do *enable* filtering for "Revolution > #9". > - Then on that very same screen (home menu > CustomSkip) *click on the > _first_ filter -set-* to make it your *primary/default filter set* > (=always on, filtering on all playlists). The name of the active primary > filter set should be displayed at the top: *Active filter set:...* > > Then *in your SQLPlayList playlist* choose the *_second_*(!) filter set > (that should filter "Revolution #9") and save it. > > Testing: > > - add "White Album" to your client playlist (*without DPL, no dynamic > playlist*) and slowly skip forward to "Revolution #9." and see if it's > skipped. It shouldn't be because the primary filter doesn't have a rule > for this and the secondary filter set is not enabled. > > - then start your dynamic playlist that includes the "White Album". Now > "Revolution #9." should be skipped - *as long as DPL is active* - > because DPL/SQLPlayList enabled the secondary filter set when you > started your dynamic playlist. If I doubt verify that DPL is still > active/involved (as described in a previous post). > > So in short: *my testing shows that secondary filtering*, started and > stopped by DPL (as requested by my SQLPlayList dynamic playlist) *does > work as expected*. It makes no difference if you tell SQLPlayList to add > this code to your dynamic playlist definition that starts/stops your > selected (secondary) CS filter set or if you do this manually in a > custom dynamic playlist that use directly in DPL. > > The main difference between DPL v2 and v3 with CustomSkip is that DPLv2 > had some kind of legacy support for calling CS filters *before* adding > tracks to the current playlist to filter tracks whereas the enabled > secondary filter skips tracks at playtime. > Since one of my objectives was to disentangle the dependencies between > DPL and deprecated plugins I've removed this legacy support because #1 > you can filter out tracks in your playlist definition (recommended) and > #2 additionally you have the option to enable a (secondary) CustomSkip > filter set when you start your dynamic playlist. > If anything, the way forward would be to have CustomSkip skip not only > the -current- track at playtime but also check the -next x tracks- in > the client playlist against any (primary and secondary) filter. But > that's another story. > > MY ADVICE: SET THE MAX. NUMBER OF UNPLAYED TRACKS DPL ADDS TO A LOW > NUMBER SO DPL DOESN'T STOP TOO SOON AND DISABLE THE SECONDARY CS FILTER. > > I hope I could help and give a little insight in how this all works. I'm > afraid that's all I can do at this point. Good luck.
You are a genius. This method worked and it looks like I'm back in business. Thanks so much for all your help. ------------------------------------------------------------------------ nyindieguy's Profile: http://forums.slimdevices.com/member.php?userid=62092 View this thread: http://forums.slimdevices.com/showthread.php?t=115073 _______________________________________________ plugins mailing list plugins@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/plugins
