I'm not aware of a tag that changes constantly that doesn't depend on the song.

For skipping purposes this component has field $rand() that changes every time track is played. I made it get only one value within the query so you can use it with multiple evaluations without requiring $puts and $get.

Yes. I use "Dynamic DSP", "Skip Silence", often "Convert 5.1 to stereo", "Convert mono to stereo", and rarely, but it's present in DSP chain nearly all the time, "Playback Rate Shift" from mudlord's "foo_dsp_effect".

I think you misunderstood. There is a DSP called "Skip Track" that prevents you from hearing parts of tracks that are about to be skipped. It should be the last DSP in the DSP chain.

Yeah... I thought you are talking about DSPs that are slowing down foo_skip work... So, "Skip Track DSP" is configured by the same settings in Advanced Preferences as "Playback \ Skip tracks" option?

EDIT:Yeah, now it works great

EDIT2:After some longer time I must say not exactly... When I change tracks manually, then yes, everything works OK. Even 6 skips are perfectly quiet. But when tracks are changing automatically I can hear for example 3 "pops" lasting long enough to hear the melody before track is skipped. I am still talking about opening .cue referenced tracks from long MP3 and M4A files.

A useful Tip for users of this component: I often listen to full length DJ Tracks which usually have a long intros and outros for syncing mixing and transitions. When i listen to such tracks i normally want to skip the first and the last Minute of the track.

Setting the Skip Tag for the first Minute is no problem with this component. Setting the last Minute is the trickier Part because you have to calculate the Time one Minute (or whatever you want to skip)

i solved this with the "Automatically fill values..." Tool in the Tag editor Window.

With this examples foo_skip skips the first and last minute of each chosen (tagged) track

QUOTE (marc2003 @ Mar 23 2013, 15:38)

%length_seconds% might make your life easier.

Thank you for your suggestion!I also noticed that this component accepts positions such as 61:1 or 3661.With all this new information, now the code is much simpler.

A is the duration you want to skip at the beginning. Format in minutes or in secondsB is the duration you want to skip at the end. Format in seconds (example: 151). Make sure it's shorter than your track length.recommended formula:

I recalled other problematic thing - it skips even files from playback queue...

Fixed. Now it respects the "Skip even manually selected tracks" setting.

Thanks for fixing it Case.

Just to summarize my experience with cue sheets and Skip Tracks DSP:I've created playlist where there was only one playable track, and 12 which all were matching skip pattern and all were entries of one cue sheet. Playback mode was set to "Shuffle". When playable track finished playing (automatically, because it has ended) there were multiple skips, one-by-one before playable track was played again. Results are:1. when file referenced in .cue is .m4a (iTunes AAC/LC) there could be up to 3 glitches, mostly 2, when tracks are skipped multiple times. Next skips are all OK.2. when refeneced file is .mp3, then only one glitch occurs, at first skip. Rest of skips is perfectly quiet.3. when referenced file is .flac then everything is perfect, nevermind whether I use DSP in chain or just item from Playback menu (without DSP in chain).

Looks like it is very specific to the encoding of files, and thus maybe this can never be fixed. And this only applies to .cue file referenced tracks, where stream is accessed not from the begining, but somewhere in the middle, and additionally it applies only to first skips in such scenario. Just for the information

Sorry for the delay. Yes it works better - when I got series of skips, there is always only one glitch (at first skip) with .m4a tracks from .cue, and it doesn't happen with every track referenced from that particular .cue. Additionally it is noticeably shorter. Currently it is hard to determine the pitch of sound and actual content of this glitch (I can't guess what track was shuffled and skipped). Glitch seems to be longer when I play manually one of the .cue referenced tracks, and then next file that is shuffled is also one of .cue tracks - but it can be only my imagination. Situation with .mp3 tracks from .cue files doesn't changed so much. Possibly glitch is shorter, (if it isn't my imagination only), but it occurs. FLAC tracks from .cue files play as they were playing before - properly

I managed to reproduce the glitching with the help of CPU Speed Adjuster. I tweaked some safety limits in the DSP part and now even with all cores fully stressed with slow.exe I heard no more glitching with cue+m4a. Updated version can be found here.

Track skipping has a few milliseconds of delay before activating which may allow beginning of gapless tracks to be heard. If you wish to have perfect glitchless skipping please add Skip Track as the last DSP in the DSP chain.

If you just want to skip silence you could use the Skip Silence DSP. But I might consider adding a new field for defining tracks that are always skipped in place of the "Skip even manually selected tracks" checkbox.

As of the current foo_skip 1.7.8, if you check the "even manually selected tracks" box and manually click PLAY on a track that its SKIP tag has "skip-timecodes", the track is totally skipped (not just the "marked" parts) !!

Part 2 (a question):As of the current foo_skip 1.7.8, if you check the "even manually selected tracks" box and manually click PLAY on a track that its SKIP tag has "skip-timecodes", the track is totally skipped (not just the "marked" parts) !!Case, Is this the way you intended it to work ?

Oh No. Again I made a mistake and I don't know what to say. My part-2 question is false.(I've tested on tracks that have both skip-timecodes and are 1-starred...)I'm deeply sorry...

I've just given your component a try. I must have missed something, because nothing seems to happen, both with manually selected and automatically selected tracks. The Skip track component shows up in my components list though. Additionally I've added the Skip track DSP in the Active DSPs' list. Editing the tag scheme in Advanced options didn't fix anything (I'd rather skip tracks that I rated "-1", but these tracks are still playing normally as they would without the component). Is there anything else I should do? Thx for your help.

I have a kind of request. Is it possible to let this component have a list of skip patterns so we can switch between them? I think about exactly the same thing as for Media Library exclusions list or files sorting patterns list or excluded file types list. At least 5 entries would be nice. I think it would require moving its config from Advanced Preferences to Tools section - this would be also more convenient for user.

In addition: I have performed many tests against problem that I reported last time (silent played first 16 seconds in manually selected files that are matching skipping pattern) and I can confirm that with v 1.7.8b problem was permanently eliminated.

Well, in addition to my request I got a bug report. I wanted to try the difference between both ReplayGain modes (track and album). I opened Properties dialog and went to ReplayGain. After changing it the sound just disappeared. I tried it several times and I found the reason. It was tested on track that was tagged to be normally skipped when I listen to my music randomly (custom tag "KEYWORDS" filled with value "skip". After tag value was removed there was no problem... When tag was filled again with value "skip" then problem came back. The funny thing - after 16 seconds (same as previously) the sound just comes back. The question is - is it just side effect of using such option and we should just bear with it or is this a real bug and this should be fixed? In general it isn't frequent situation that someone plays manually tracks that should be skipped and switches RG modes while track is played.

That's definitely a bug. I'll see if I can simplify the logic to eliminate such issues. I wanted to comment so you know I have acknowledged the problem as it will take some time before I'll start working on it.

When I click on playlist item to play then it often starts to play after 6-30 seconds delay. But if I select same file again, then it plays immediately. It worth to note that all my tracks are separate .flac files. Looks like some caching issue to me..Is there any way to get 1.7.4 version? I don't recall such behavior happening last year.

SkipTrack query:

CODE

(%rating% IS 1 OR %last_played% DURING LAST 240 HOURS) AND (NOT %rating% IS 5)