"$strstr(%_path%,'A:\YOUR PATH\')" GREATER 0 AND NOT %last_played% PRESENT

("$strstr(%_path%,'A:\YOUR PATHA\')" GREATER 0 OR "$strstr(%_path%,'B:\YOUR PATHB\')" GREATER 0) AND NOT %last_played% PRESENT

Code: [Select]

"$strstr(%_path%,'A:\YOUR PATH\')" GREATER 0 AND NOT %last_played% PRESENT

Code: [Select]

("$strstr(%_path%,'A:\YOUR PATHA\')" GREATER 0 OR "$strstr(%_path%,'B:\YOUR PATHB\')" GREATER 0) AND NOT %last_played% PRESENT

The skip thing can not be done

%skip_count% MISSING

("$strstr(%_path%,'A:\YOUR PATHA\')" GREATER 0 OR "$strstr(%_path%,'B:\YOUR PATHB\')" GREATER 0) AND (NOT %last_played% PRESENT OR NOT %skip_count% PRESENT)

not the user skipping tracks on demand (?).  So we are at the same point for those.

link next track button to an action which increases the skipping count too.

'use strict';

/* 
	Add Skip Tag From Playback v 1.1 23/06/21
	Adds a 'SKIP' tag using current playback. Meant to be used along Skip Track (foo_skip) component.
	Has an intelligent switch which sets behavior according to playback time:
		- If time > half track length -> Track will play as usually up to the 'SKIP' time, where it jumps to next track.
		- If time < half track length -> Track will play from 'SKIP' time to the end.
	This is a workaround for using %playback_time% for tagging, since %playback_time% does not work within masstagger scripts.
 */

function skipTagFromPlayback(selItem = new FbMetadbHandleList(fb.GetNowPlaying())) {
	if (typeof selItem !== 'undefined' && selItem !== null) {
		const countItems = selItem.Count;
		if (countItems === 0) {
			console.log('No tracks selected.');
			return;
		}
		if (countItems > 1) {
			console.log('More than 1 track selected, playback time can only be used for one track at once.');
			return;
		}
	} else {return;}
	const currentPlayback = fb.PlaybackTime * 1000;
	const time = new Date(currentPlayback).toUTCString().substr(20,5) + '.00'; // doesn't care about ms
	const bEnd = currentPlayback > selItem[0].Length * 1000 / 2 ? true : false; // skips from start or end
	selItem.UpdateFileInfoFromJSON(JSON.stringify([{'SKIP' : (bEnd ? '' : '-') + time}]));
	console.log('Adding SKIP tag to current track: ' + time + (bEnd ? ' (skips end)' : ' (skips start)'));
	return time;
}

With that and my query at top, it would work exactly as you want.

Do agree with your thoughts some times, and that's why I'm releasing my own scripts hahaha

Quote

With that and my query at top, it would work exactly as you want.

Amazing!!!  Thanks you so much!!!

Quote

Do agree with your thoughts some times, and that's why I'm releasing my own scripts hahaha

:thumbs:  :thumbs:
One question could for example the playback component have subcomponents, perhaps it would be simpler say add a subcomponent for  behaviour of skipped tracks? I also ask because I'm learning full-stack JS so in the future I hope to be able to release tweak code my own components.

function onDspPresetChanged() {
	if (typeof exportDSP !== 'undefined') {
		if (!exportDSP()) {console.log('Error saving DSP entries for http Control integration.')}
	}
}
if (typeof on_dsp_preset_changed !== 'undefined') {
	const oldFunc = on_dsp_preset_changed;
	on_dsp_preset_changed = function() {
		oldFunc();
		onDspPresetChanged();
	}
} else {var on_dsp_preset_changed = onDspPresetChanged;}

Next release of Playlist Tools will have a configurable SMP main menu which also allows you to pre-load your own scripts and assign them to a menu entry -thus resolving the conflict problem-, so all that part would not be required anymore. You sill have to code the tag update/next script though.

here each coder writes its own things not caring so much about compatibility/integration with other plugins.

Ohh okey! sorry ^^!!
I will install it and try it out to better get understand it. Thanks

Edit:

Quote

here each coder writes its own things not caring so much about compatibility/integration with other plugins.

But then isn't there extra code work?

and you got no documentation at all. That's the missing part around this community in my opinion.

SMP is not wordpress, so the community is not big enough for asking interoperability of scripts for sure...

On my todo list is planned to release also the map framework (which should also allow arbitrary cloud tags), and the button framework I use. This is just an example of the map being used for a world map or a cloud tag (same framework)

Quote

SMP is not wordpress, so the community is not big enough for asking interoperability of scripts for sure...

Understood. Question ideally should stuff like a menu framework can be defined in the SDK? I know very little about it actually.. so I'm wondering from my ignorance.