Accesso rapido:  

Forum: Wishes and new features

Topic: Script query for Stems Separation COMPLETED for a loaded track
add scripting capability to query when Stems processing has completed.

Could be added to:
Manual wrote :
has_stems Return true if the track has stems available. Can also be called with 'has_stems "2.0"' to check for new engine, or 'has_stems "ready"' to check if stems are ready at the current playing position

with something like:
has_stems "done" to check if stems processing has completed

currently one could goto end of track and query 'has_stems "ready"


PS maybe that is already possible with:
Manual wrote :
has_stems Return true if the track has stems available.

(do not know how, or if that is working)
 

Inviato Fri 18 Nov 22 @ 1:45 am
What do you want to achieve ?
Keep in mind that the new Stems 2.0 engine always separates / gives priority to the point you are located inside the track first.
If you load a track and jump to a hotcue near the end, the decoding will also "jump" and keep separating from the hotcue onwards.
This means that you don't have to wait for the entire track to separate before you can start using the track.
And that's what has_stems "ready" reports. If the stems are ready on the point you are located, because that's what really matters now.
 

Inviato Fri 18 Nov 22 @ 8:44 am
Thank you Phantom... another pearl if info !

I was assuming the Stems separation was similar to the BPM, Key and Gain initial Analysis, done from beginning to end.
So cool that it is adaptive, since many times, one is not playing from the start, and no need to do stems separation, for online tracks sections, that cannot be saved, or will be played.

PhantomDeejay wrote :
What do you want to achieve ?

And was wanting an indicator to tell me when I could use the stems..(ie when the stems prep was completed) since the EQ stems knobs become, or are, the traditional Frequency EQs, until the stems are computed at that track position.
(found this out when VDJ would not allow me to uncheck the "Don't use GPU', forcing CPU to do it all, had to do a system restore to be able to uncheck it, and don't know if that is a planned feature, but scary, and wanted to be ready for slower CPU stems prep, if it happened again)


PhantomDeejay wrote :
Keep in mind that the new Stems 2.0 engine always separates / gives priority to the point you are located inside the track first.
If you load a track and jump to a hotcue near the end, the decoding will also "jump" and keep separating from the hotcue onwards.

1) Would you suggest, creating an ONSONGLOAD script to jump to the point you wish to start playing from?

2) Does it give priority to the track playing on deck 1, if there are also newly loaded tracks on deck 2 and maybe additionally decks 3 & 4?
Would this slow down deck 1's stem prep?
Any thoughts and suggestions for best use/operation?



So lovin the new Stems 2.0 ! ! and much to learn .. again thanks !
 

Inviato Fri 18 Nov 22 @ 9:20 am
Why use "ONSONGLOAD" ?
You can set autoCue setting to "cue" or "cue/skip silence"
This way when you load a track it will "jump" to hotcue 1 if it exists, or to the start of the audio of the song if it doesn't.

Then it's just a matter of placing hotcue 1 to the place you usually want to start playing your track.

As for priority:
When you load a second deck it will split the separation speed between the two decks.
If your machine is capable to do realtime stems separation then it should not really matter.
You'll get "half" separation speed for each deck, but since it's faster than realtime, you don't need to worry about it.

Finally, the checkmark on Stems 2.0 pad page, shows exactly what you're after. When the deck is ready to use stems at the location you are inside the track.
 

Inviato Fri 18 Nov 22 @ 11:33 am