Sign In:     

Forum: VirtualDJ Technical Support

Topic: Legacy Echo's Name?
with the awesome new features of VDJ 2026, I find that some of my previous scripts are not working.

for example:
effect_active 3 'echo' on
now does not work, with VDJ 2026 build 8945 but works, if I use an older build 8909.

I assume its because maybe the legacy "echo" goes by a different scripting name now.
If so how does one reference the legacy "echo" with script?


Is there list of the naming conventions of similarly named effects?






Note: I do have the legacy "echo" effect, in slot 3.
(not the new echo, with the same name, which has different parameters)

Legacy echo:



New Echo:
 
Posted Tue 09 Dec 25 @ 5:21 am
Did you select the "legacy" effect list on slot 3?
 
Thanks for the quick reply.

yes have selected the Legacy "echo" for slot 3.

testing with custom button script on deck 2:
effect_active 3 'echo' on ? effect_active 3 'echo' off : effect_active 3 'echo' on

the above script works great for build 8909.... but does NOT work with 2026's build 8945.

Note: the above script on build 8945 does indeed turn on and off the NEW echo, which can be selected either from either the "Default" list or the Full List.
I wish to use the Legacy Echo, selected from the Legacy List.

How do I script the "Legacy echo" in VDJ 2026? I like the "Mute Source" of the legacy echo, seems not to be there on the NEW Echo.

Can you test to see if it works for you, and maybe its only my system that is having this issue, for some reason?





PS for me the New Echo does not produce any "echo".. can you check that the New Echo is working as expected?
 
update: the above custom button script on deck 2, does do something.. but its unclear what it does since it does not enable the Echo on slot 3. (which if the echo is enabled manually, the legacy echo works perfectly, how can one enable the legacy echo with script)

and, using the script effect_active 3 'echo' on seems to decrease the volume a bit, but it definitely is not an echo effect, and does NOT enable the Legacy echo on slot 3.

Is there any other Option that should be checked?

Note: Parameters for the legacy echo are set as pictured above.
 
Would love if someone could verify, on another setup that the "legacy echo" cannot be enabled with a script b;y someone using VDJ 2026, build 8945.


3 easy steps:

1) Select the legacy echo in say, the FX slot, 3

2) copy this script to a custom button on the same deck:
effect_active 3 'echo' on ? effect_active 3 'echo' off : effect_active 3 'echo' on

3) click the custom button, which should turn the Legacy echo ON and OFF.


would love to know if it is only my setup that is having the issue.



Note: for me, the above works perfectly if the New Echo is in slot 3, but cannot get the Legacy echo to work with build 8945.


PS have troubleshot my setup by starting with new settings.xml.
Legacy echo, still cannot be enabled with script.
 
Thanks everyone for the help

I have tested on a entirely different computer and setup. And get the same results.

I will wait for this needed tweak, before fully implementing VDJ 2026.
 
Tested

effect_list 3 Legacy & effect_active 3 echo

Still switches new echo on, despite legacy being on slot.
Second press does nothing [new stays on]

Similar story with
effect_list 5 Legacy & effect_active 5 cut
switches on new, 2nd press = nothing

As I said before this common name is a bit of a mess and while new can replace legacy, having 2 cut effects is more interesting.
 
thanks Locodog for the info and confirming.

Yes and not to complicate things (hence why not mentioned), is that manually enabling "Legacy echo" does indeed, light the custom button, ( ie indicating that effect_active 3 'echo' is TRUE but the script does not work).
So strange.

I would use the new echo but it appears that the new echo does not have "Mute Source".

Is there a work around with the New Echo?
(which at this time is the only echo that can be enabled via script)

PS also currently I cannot get the New echo to sound anything like an echo effect. What am I missing?
 
Echo works fine here.
Can you please close VirtualDJ, open VirtualDJ folder, then plugins64 folder and delete any "native_Echo" ini files present ?
Or at least try to set the settings as per the pic below:
 
IIDEEJAYII wrote :

New Echo:



I don't know how you end up with such settings, but yes, they are completely messed..
1) Feedback (slider 3) should be more than 0% in order to sustain some kind of echo
2) Filter (slider 4) should be at the middle. Currently it sits at full highpass (as resonant filter, not to be confused with lowpass and highpass sliders 5 & 6)

Try this on a custom button in order to reset the effect without the need to delete the ini files
effect_select 3 'echo' & effect_slider_reset 3 3 & effect_slider_reset 3 4 & effect_slider_reset 3 5 & effect_slider_reset 3 6 & effect_active 3
 
Thanks Phantom!

Appears that my scripting for the echo parameter sliders (for the Legacy echo) made the New Echo not work, by setting slider 4 to 100% (since w legacy echo slider 4 was Highpass and wanted 100% ) and New Echo slider 4 is Filter which if set to 100% cuts everything. Yes New Echo needs to be at 50% (OFF) to work.

Thanks for the catch.

The new echo would work, if I could find a way to "Mute Source", as in the Legacy echo.

Is there a way to Mute Source with the New Echo?


PS would love to just continuing using the Legacy echo if/when it can be enabled by script, so my scripting is not broken with VDJ 2026.

and to be clear, you cannot get the legacy echo to activate with script in VDJ 2026, right ?
 
I don't know how you use Echo, but if you want to kill source at activation (and therefore have only echoes going on) why don't you try to use "Echo Out" instead ?

As for the problem with activating legacy 'echo' via script my guess is that the devs will take a look at it.
 
As a temporary solution you can use this script:
effect_list 3 'Legacy' & effect_select 3 'echo' & effect_active 3
 
edit note, the L of legacy still needs to be capitalised.
 
Thank you so much! Phantom and Locodog

Note for Devs:

Its effect_active 3 'echo' that is misbehaving in build 8945.
for some reason adding the 'echo' to the effect_active verb, causes the issue, of activating/deactivating only the New Echo, whether it is currently in slot 3 or not.

effect_active 3 will indeed function as expected,
(activating/deactivating what ever FX effect, has been selected in slot 3, Legacy or New)

again effect_active 3 'echo' will (in build 8945) always activate the New echo even if it is NOT in slot 3,
and NOT activate the Legacy echo which is actually in slot 3.

so the minimum change needed in my scripts is replace
effect_active 3 'echo'
with
select 3 'echo' & effect_active 3

(assumes I have the Legacy FX list selected)

and as Phantom has brilliantly mentioned, is even better as it specifies all.
effect_list 3 'Legacy' & effect_select 3 'echo' & effect_active 3

Again huge thanks for the assistance!!!



PS the only minor issue of adding the effect_list 3 'Legacy' to every FX script, is, since the FX is called by scripts, and if diff FX effects are scripted quickly, (faster then 2 sec) then all one may see is "Legacy" displayed in slot 3, instead of the actual FX active at the moment from the pads/buttons.
It is more satisfying to get instant feedback as to which FX is active, without a 2 sec delay.
(just a personal feeling)
Will attempt to add effect_list 3 'Legacy' only when needed.