Sign In:     

Forum: Wishes and new features

Topic: ​Keep effect tail when loading a new track
Hey VDJ community,
​I want to talk about what happens to effect tails when loading a new track.
​Right now, if I have an effect (like a reverb or echo) going on an outgoing track, and I load a brand-new track onto that same deck while the effect tail is still fading, the tail gets cut off instantly.
​In a smooth mixing workflow, you often want to load up your next track quickly while letting the previous track's effect tail keep ringing out naturally. Is there a way or a plan to allow effect tails to persist and fade out natively on a deck even after a new track is loaded into it?
 
Posted Wed 30 Sep 26 @ 6:46 pm
Setting: resetFXOnLoad to no
 
I see what you mean, and resetFXOnLoad is actually a useful feature because it keeps a new track from accidentally starting with the effect still switched on. So we definitely need to keep that.
​But that's a bit different from what I'm talking about. Think about how Smart Press works: if you press and hold an effect button for a longer time, the effect stays on while you hold it, and the moment you let go, the effect deactivates itself—but the tail stays ringing out.
​That's what I mean. Even with resetFXOnLoad doing its job to keep the new track clean, that generated effect tail should stay right there and keep fading out naturally when you load a new track onto the deck instead of being cut off instantly
 
That should work if fxProcessing = post though with effects where that makes sense (e.g. echo). I do this all the time with my S11 and its paddles, or my FLX10 and its button based activation.

Activated as a Pad FX however, it won't have a tail.
 
Hey @DJ VINYLTOUCH, thanks for the reply! Since you mentioned you use an FLX10 too, maybe you can relate to this.
​I already have Post-Fader active in my settings, and I use button-based activation just like you describe. The issue I'm talking about isn't about regular fader cuts—it specifically happens the exact moment a new track is loaded into that deck.

​Even with post-fader on, loading a brand-new track onto that same deck instantly cuts off the existing effect tail from the previous song. Even if resetFXOnLoad should reset the effect controls for the incoming track, the audio tail from the outgoing song shouldn't instantly cut off—it should still be allowed to ring out naturally. That's why I'm hoping for a way to let those specific effect tails persist on the deck even when a new track is loaded in.
 
Zeusmatic wrote :
Even if resetFXOnLoad should reset the effect controls for the incoming track, the audio tail from the outgoing song shouldn't instantly cut off—it should still be allowed to ring out naturally.

Why do you think that?

That being = yes means you are telling the software to reset FX state on load of a new track, which would imply the effect should be switched off.
If you want the trail to stay on load, that should be set to no as stated earlier, along with fxProcessing = Post fader.
 
I see what you mean. The issue is I actually want the effect to switch off when a new track loads so the incoming track starts completely fresh without any lingering filters or echoes.
​My point is that right now, resetFXOnLoad acts like an all-or-nothing switch. It kills the effect controls (which I want), but it also brutally cuts off the audio buffer of the previous track, killing the tail instantly.
​What I'm looking for is a feature or a refined setting that acts like reset-on-load for the controls, but leaves the outgoing effect tail active so it can ring out naturally. That way you get a clean track start without sacrificing a smooth transition.
 
Why do you need to load a new track on the same deck as the one currently playing? The software supports multiple decks? (up to 99)
 
'upto' hasn't applied in a very long time [since v8], you can have as many as you want, the only limit being the memory use of the tracks uncompressed.
 
@Zeusmatic You want to write your own procedure for resetting fx onsongload then.
 
1) Change the "resetFXOnLoad" setting to no
2) Open your keyboard mapper, find the <ONSONGLOAD> key and add this action: effects_used 'deck' ? wait 4000ms & effect_disable_all : nothing

This will delay the effects deactivation for 4 seconds so that trailing has more time to die naturally.
You can adjust the time if you wish.
 
Huge thanks for this, @PHANTOMDEEJAY! This is actually a brilliant workaround. Setting it to delay the effect disable gives me exactly the balance I was looking for—keeping the tail alive while still clearing the effect automatically. Appreciate you sharing the exact script lines for the mapper!