In this post I'm requesting a new feature: Weighted random playback. If foo_skip also could deal with values between 0 (never skip) and 1 (skip always) which represent a "skip probability" this plugin could provide the requested functionality. As there any chance that the author of this plugin could code that?

In this post I'm requesting a new feature: Weighted random playback. If foo_skip also could deal with values between 0 (never skip) and 1 (skip always) which represent a "skip probability" this plugin could provide the requested functionality. As there any chance that the author of this plugin could code that?

In this post I'm requesting a new feature: Weighted random playback. If foo_skip also could deal with values between 0 (never skip) and 1 (skip always) which represent a "skip probability" this plugin could provide the requested functionality. As there any chance that the author of this plugin could code that?

How would one go about adapting the "$ifgreater($rand(100),80,1,0)" to make it only skip a percentage of skip tag'd songs.

That code would skip 80/100 (i.e. 80%) of the time. If you want to customise the skip percentage, you can change the numbers. For example, if you have a tag called "skip" that contains an integer between 0 and 100, which denotes the probability that you want to skip, you can put %skip% instead of 80, i.e.$ifgreater($rand(100),%skip%,1,0).

-------------------------------------------------------------

Dear kdx, maker of this very useful plugin! I'm wondering, would it be possible to recognise tracks from the "enqueue" queue and never skip them?

(I've tried three times posting this, it looks fine on the preview but always ends up in my previous post... Hopefully this time it won't!)

If playback mode is set to repeat the playlist and the playlist contains only skipped items, foo_skip should STOP playback. What it does currently is get stuck in an infinite loop, constantly printing to the console "skipping: file://X.mp3".

Here's an example scenario to illustrate this bug:1. Set playback mode to "Repeat (playlist)"2. Start playing a playlist which contains a single song.2. During playback, mark the song to be skipped.3. When the song finishes playing, foo_skip will get stuck in an infinite loop (check the console).

Let's see if someone can help me. Problem: when I have 2 files from the same album (one .cue and another .mp3), they both go to the library of foobar. So basically you have two times the same album. I want to have only the cue file. I installed foo_skip hoping that this dll would solve my problem (I put a SKIP tag in the big files). But, when you play a file from the .cue file, they inherit the properties of the .mp3 file. So, all the songs in the .cue file stay with "SKIP = 1" value.How do you do with your library in this case? Do you use another component?With lossless files I dont have this problem, because I put the .cue file inside the tag "cuesheet" of the big files. But with mp3 files, you cannot do this.

Maybe i can calculate hotness for every track in playlist with... hmmm... columns_ui or something. And then skip tracks using %hotness%

Does it work with $get_global(hotness) as suggested at the top of the hotness thread? Otherwise, you could I suppose put the whole hotness code on one line into the skip control (get rid of anything that is comments, i.e. anything to the right ot // including that symbol).

1 star = 20% to pick the track.If there is SKIP tag present, it will always skip that track.The bold number is the probability rate in % for track that don't have rating. Change to 0 will make it skip all track that don't have rating.

Foobar2k config file: saves all info fields in foobar's configuration file. Reasonable loading time, fast reading of info, fast writing of info. This is also insecure, you will lose all changes since the last config file saving if foobar crashes or something.

Text file (foobar2kdir\custominfo.txt): Utf-8 encoded text file (which shouldn't be modified though). Slow loading, fast reading of info, fast writing of info. This is also insecure, changes are not written to disk until you exit foobar.

SQLite database (foobar2kdir\custominfo_sqlite.db): Slow loading, fast reading of info, slow writing of info. Changes are immediately written to disk which is why I personally recommend this option.

In fact, couldn't these two plugins be used in conjunction? Use 'Custom Info' to store a rating of 1-5, output it as %rating%, then use that with foo skip?