foo_skip: skip tracks that match a specified search query, Was: [Request] Inactive Tracks Options

[Case]

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.

[Case]

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.

[EpicForever]

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.

This post has been edited by EpicForever: Mar 24 2013, 10:42

[Case]

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

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

[Speech]

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.

i chose source -> Other: and used this script

CODE

-1:00;$sub($cut(%length%,$sub($strchr(%length%,:),1)),1):$right(%length%,$strchr(%length%,:))-

Pattern is then the Tag Name

CODE

%skip%

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

%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 seconds
B 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:

CODE

-A;$div($sub(%length_seconds%,B),60):$mod($sub(%length_seconds%,B),60)-

or even (format in seconds):

CODE

-A;$sub(%length_seconds%,B)-

or the universal formula (if you want to format hours):

CODE

-A;$ifgreater($sub(%length_seconds%,B),3599,$div($sub(%length_seconds%,B),3600):$div($sub($mod(%length_seconds%,3600),B),60):$mod($sub(%length_seconds%,B),60),$div($sub(%length_seconds%,B),60):$mod($sub(%length_seconds%,B),60))-

Now it becomes a bit more difficult to follow this last code, but, for your understanding, the formula is
if(final position greater than 1 hour)
then (length-B)/3600 : ((length-B) mod 3600)/60 : (length-B) mod 60
else (length-B)/60 : (length-B) mod 60

This post has been edited by Speech: Mar 24 2013, 12:31

[EpicForever]

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

This post has been edited by EpicForever: Mar 24 2013, 12:44

[Case]

I seem to have trouble triggering such behavior. Can you try if this test version works any better?

[EpicForever]

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

[Case]

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.

[EpicForever]

Thanks, will check/test it within next week

[Nisto]

Paragraph edit: never mind, I missed the settings in the advanced section of fb2k, "skip even selected tracks"..

Also, am I supposed to have the DSP activated in order to utilize the SKIP tag? It doesn't seem to matter if I have it on or off; it still skips.

This post has been edited by Nisto: May 7 2013, 17:00

[marc2003]

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.

This post has been edited by marc2003: May 7 2013, 17:45