Se Connecter:     

Forum: General Discussion

Sujet: VDJ 2026 Teaser! - Page: 3
There's a place for everything, and decisions have been made.
VirtualDJ does not have a built in compressor. Period.
If you feel the need to use one (for whatever reason) then there are quite a few VST effects proven to work absolutely fine.
Some above have mentioned "Loudmax"
I can also say that for some special needs of mine I have also tested Thimeo Stereo Tool (which works fine as a VST effect) and that I also use Ozone 11 once per week.
Latency is and will always be an issue, because a good compressor / loudness maximizer needs to "look ahead" and therefore "cache" some audio.
It may not be much, but it is there and this won't change even if it was for VirtualDJ to create it's own "maximizer" and/or compressor.

Finally, on most modern controllers you should be far far away the range that the built in limiter kicks in.
Most modern controllers work with a headroom ranging from 6dbfs to 9dbfs
This means that for normal mixing it should be almost impossible to reach 0dbfs and hit the limiter.
Even "transients" are no more than +1 or +2 db extra.
Therefore there's plenty of room to spare.
 
Bren F wrote :

I was talking about a soft clipper on the master channel/bus (before the brick wall limiter), nowhere did anyone mention a compressor except for those who don't know what a soft clipper is and how it works.

It would only require a threshold setting to catch stray peaks caused by time stretching and transient build up while mixing.


A soft clipper is effectively a special case of compression having a lower ratio, attack time and threshold, and a faster release time 🤷🏾‍♂️.
It still is a subjective addition.

As for VSTs being a cop out - we'll agree to disagree here. IMO it adds flexibility to the software, and other platforms have seen the usefulness enough to incorporate it too.

VirtualDJ does have VSTs as a feature - all I was saying is that reporting the issue could help them to have better support of VSTs.
 
Bren F wrote :
groovindj wrote :
....but if you're using VDJ within limits (levels set correctly, watching meters etc) there shouldn't be any stray peaks or transient build up.


Master tempo engaged on one track causes peak surges, check your meters when it's engaged, now add another track when you're mixing for double trouble.

a soft clipper would smooth these peaks in a gentle manner, meaning the limiter in VDJ (or even the venues limiter) is less likely to trigger or if triggered they'd have less work to do.


As it's often the case with these things, theory is different than reallity.
All modern compressors, limiters and loudspeaker management units work with RMS based values, and not absolute peaks.
However, EVEN if they worked with peaks, the "peaks" you describe here (as a result of master tempo) are too narrow to be calculated. So, in reality there's no real difference.
BUT: Don't take my word for it.
Taste it with a real hardware compressor (an analog one would be the best case)
Set it's peakstop control at a value and watch how much the gain reduction changes between turning MT on and off,
In theory, you should see a significant change, right ? In reallity nothing happens.
Your track's dynamics are "far more important" for your compressor than the resonant peak of MT :P
 
PhantomDeejay wrote :

I can also say that for some special needs of mine I have also tested Thimeo Stereo Tool (which works fine as a VST effect) and that I also use Ozone 11 once per week.
Latency is and will always be an issue, because a good compressor / loudness maximizer needs to "look ahead" and therefore "cache" some audio.


Good to see that i am not the only one who tried out Ozone. If you dont mind my asking. In terms of the latency issue, How come NI were able to integrate it into their DJ software without latency? is it because they are the same company that makes the Plugin? ( Just thinking out Loud )
 
Bren F wrote :
groovindj wrote :
....but if you're using VDJ within limits (levels set correctly, watching meters etc) there shouldn't be any stray peaks or transient build up.


Master tempo engaged on one track causes peak surges, check your meters when it's engaged, now add another track when you're mixing for double trouble.

a soft clipper would smooth these peaks in a gentle manner, meaning the limiter in VDJ (or even the venues limiter) is less likely to trigger or if triggered they'd have less work to do.

Could you tell me the name of a song that with default settings causes so much transients that you can actually tell the difference in sound when playing it normally (so it touches the limiter) and when playing it with zeroDb at -3 or -6?
 
Chaksi wrote :
Good to see that i am not the only one who tried out Ozone. If you dont mind my asking. In terms of the latency issue, How come NI were able to integrate it into their DJ software without latency? is it because they are the same company that makes the Plugin? ( Just thinking out Loud )



Who said that it doesn't introduce latency ?
Have you tried to measure it and you found it zero ?

As I said, plugins like Ozone (that need to "look ahead") will always introduce latency.
The bigger the look ahead window, the bigger the latency.
On the other hand, a simple compressor that just reacts on the incoming signal can be "latency-free" but we are not talking about simple compressors, are we ?
If you just want a simple compressor there are literally dozens that work fine as long as you like the sound they produce.
 
I keep seeing people upset that the upcoming VirtualDJ 2026 still won’t have fluid beatgrids.

But isn’t this basically the same as right-clicking a track, opening the BPM editor, choosing “Analyze for multiple BPM,” and letting VirtualDJ detect tempo changes automatically? Then when a track has varying BPM values, the software already shows the BPM varying and the beatgrid shifting during playback.

Is this not the same feature people are asking for? Because as far as I know, this has been available in VirtualDJ for a long time.
 
No it's definitely not the same! Are you aware of the system introduced by Algoriddim two years ago?

The user doesn't have to do anything (other than load the track). The analysis is very quick and accurately follows small continuous variations in the tempo of the track, displaying the BPM changes live.

The Atomix system looks for sudden jumps in tempo, from one to another, rather than gradual drifts that occur naturally with real drummers.
 
Loving the new virtual DJ 2026, couple of initial notes:
1. Could we be allowed to pre prepare files with lyric editor in bulk rather than one at a time
2. I assume the lyric editor has a max minute size?
3. Some songs bringing in Chinese symbols, having a find and replace would be helpful in the lyrics editor
4. Option to increase size of text in waveform for people with eyesight issues

Great update so many options from this
 
1) How "bulk" pre prepare would work ?
2) Lyrics extraction in general has a minimum and maximum length, yes
4) Currently it uses the same definition for "CUE" name display on the waveform. Therefore it would be possible to change the size by editing the skin.
 
Great offering guys, but not into karaoke, and vsts are the best thing about virtual dj so don't need the new fx and I'll be honest I cringe every time I see a DJ use 2 hands on pioneer gear to add the most minute amount of delay onto a track that you can barely hear as if they are doing something amazing!! So don't need any of those terrible pioneer effects when you have stuff like Turnado. So not much on offer for me this year.

Would love to see some audio editing in the sampler editor like pulling the sides in for a fade in and out of the sample like Cubase does to stop clicks on samples. Maybe a normalise function to to get the most volume from a sample as possible.
 
Just using the FXs on my laptop, I can definitely hear the difference in the sound. Everything is clean sounding. Ill test more when I get home tonight but I'm looking forward to what's next.
 
Been a long time coming Huey :)
 
Yes sir!! I'm happy with this!!
 
Klaus has just made a video covering the new stuff, and he's mentioned something that's not been posted here yet. Maybe he's been beta testing...

In the browser, if you go into Ideas/Filters/Duplicates there's an option to find dupes by AI audio signature.
 
PhantomDeejay wrote :
1) How "bulk" pre prepare would work ?
2) Lyrics extraction in general has a minimum and maximum length, yes
4) Currently it uses the same definition for "CUE" name display on the waveform. Therefore it would be possible to change the size by editing the skin.


Was thinking the way we can bulk analyze BPMs etc
 
groovindj wrote :
Klaus has just made a video covering the new stuff, and he's mentioned something that's not been posted here yet.

It's not the only thing that has been left out..
It's kind of an Easter Egg, but on Christmas!

The only "draw back" is that the track(s) must have been analyzed* with VirtualDJ 2026 for it to work.
That's why it's not advertised at this point.

*Version 2026 also calculates an "audio signature" now when stems are enabled.
You don't have to reanalyze your library by the traditional means of the word. Just loading a track on a deck will also force a calculation of the audio signature.
Therefore as you use VirtualDJ this filter will become more and more capable to detect real duplicates.
 
djspaceyuk wrote :

Was thinking the way we can bulk analyze BPMs etc

Remember, this is AI extraction. Therefore bulk processing (batch extracting lyrics from many songs) could easily overload the AI server. At least for now, the initial time period that all VirtualDJ users are going to try it.
 
Maybe a bunch of silly question but:

  • Are you guys running a centralized server for the AI lyrics?
  • If 1) is yes, was/is it feasible to run the LLM locally?


I don't know the details required to run the model (resource requirements) so those questions might be silly, but I'm wondering if the server is centrally run by you guys and can be overloaded even now, what would happen in future when more persons try to use it?

Please feel free to ignore if this is way off base in terms of what is actually happening.
 
PhantomDeejay wrote :
the track(s) must have been analyzed* with VirtualDJ 2026 for it to work


Ah that explains why it didn't seem to do very much. Thanks for the explanation.
 
57%