I'm not sure if this happened because of the microsoft windows update, or because of the recent VDJ update as I made the mistake of allowing them to happen right before my gig.
I was DJing with an SX3 that I've been using with no problems... however after this update... suddenly channel 2 is extremely muddy, like the bass is turned up, even when you turn the bass filter knob all the way down. I ended up having to use channels 1 and 4 for the night.
Second, and this was the real kicker.... any time you touch either the channel volume faders, or the crossfader... the music starts playing on any channel that has a song loaded into it and is not playing.
I had to put one hand on the platter to hold the song still, and with the other hand, adjust the volume/crossfader, and then hit the stop button....
I turned off every automatic setting I could find in the configuration and could not get it to stop doing this. Is there a setting I'm missing?
I tested my SX3 on my back up laptop when I got back from the gig (which is running windows 10 and an older version of VDJ), and the SX3 runs fine - so its not the SX3.
Plan is to reinstall the SX3 drivers and see if that fixes anything. Have to wait until I can unpack my trailer and access that laptop.
Any suggestions would be appreciated.
I was DJing with an SX3 that I've been using with no problems... however after this update... suddenly channel 2 is extremely muddy, like the bass is turned up, even when you turn the bass filter knob all the way down. I ended up having to use channels 1 and 4 for the night.
Second, and this was the real kicker.... any time you touch either the channel volume faders, or the crossfader... the music starts playing on any channel that has a song loaded into it and is not playing.
I had to put one hand on the platter to hold the song still, and with the other hand, adjust the volume/crossfader, and then hit the stop button....
I turned off every automatic setting I could find in the configuration and could not get it to stop doing this. Is there a setting I'm missing?
I tested my SX3 on my back up laptop when I got back from the gig (which is running windows 10 and an older version of VDJ), and the SX3 runs fine - so its not the SX3.
Plan is to reinstall the SX3 drivers and see if that fixes anything. Have to wait until I can unpack my trailer and access that laptop.
Any suggestions would be appreciated.
Posted Mon 05 May 25 @ 8:31 pm
I bet this is Dell Audio Maxx volume Pro, you'll find it in the control panel and you can turn off that disgusting Maxx mess.
Posted Tue 06 May 25 @ 10:36 am
Its actually an ASUS i9 gaming laptop...
Posted 22 hours ago
So AFAIK there has been no update that would cause what you are describing to be the default, with or without a controller.
Just some guesses:
Problem 1) sounds like you left an effect on for channel 2 that is changing how it sounds.
Check to see if any effect is visually on for any of the slots (6 slots total I think with skin6FxLayout enabled).
Also, VirtualDJ can enable effects without actually putting them in a slot (no immediate visual indication) - not sure if you do custom mappings at all but maybe check to see if that is the case as well.
Problem 2) sounds like you have faderStart enabled in some form:
Just some guesses:
Problem 1) sounds like you left an effect on for channel 2 that is changing how it sounds.
Check to see if any effect is visually on for any of the slots (6 slots total I think with skin6FxLayout enabled).
Also, VirtualDJ can enable effects without actually putting them in a slot (no immediate visual indication) - not sure if you do custom mappings at all but maybe check to see if that is the case as well.
Problem 2) sounds like you have faderStart enabled in some form:
- Check to see if faderStart is enabled in the VirtualDJ options, and if it is, disable it.
- Check to see that the DDJ-SX3 Settings Utility (outside VirtualDJ) has a fader start option, and if it does and it is enabled, disable it.
- The mapping of that controller, for VirtualDJ and Serato, allows for holding Shift down and moving the channel faders/the crossfader to allow for automatic playback start at the set cuepoint, so if you are holding shift and moving the faders, probably don't do that
- If you are using a custom mapping, try using the factory default mapping to see if the problem persists
Posted 21 hours ago