dashashugaeva
Hi. There is one very annoying problem: If I load a song and quickly press some hot cue button (usually I mark "hot cue 1" point from which I start the track) then quite often the track starts playing not from this point, but from a random place. Even worse, sometimes at the moment of this error a very loud bzzzz sound appears for a split second and all this goes to the master section during the disco. As a result, I have to wait a few seconds after loading a new track each time and only then press hot cue for the first time, this partially solved the problem. But at the same time, when I started using eq with "easy remix option", the problem only worsened and sometimes the bzzzz sound appears when pressing hot cue even if 5-10 seconds have passed since loading the track. My computer is not very powerful, windows 10, intel i5 gen 10, 16 gb RAM, 512 ssd and no separate video card. Previously, when loading a new track on a track, the CPU load increased by 100% for several seconds, apparently due to the stems function. I thought that this could provoke the problem. I set the StemsRealTimeSeparation to "fully disabled" and now the CPU does not load on new tracks and I use only precomputed stems 2.0 for some tracks. But the problem still appears, several times per evening. In the end, I returned eq standard mode again and wait for some time before pressing hot cue on the loaded track. This problem is very annoying and I do not know if it can be somehow solved and if anyone else encounters this?
Posted Sun 20 Oct 24 @ 9:20 pm
wickedmix
sounds like you might want to adjust the AutoCue setting in options to cue so it always loads to the first cue you have set
Posted Sun 20 Oct 24 @ 11:33 pm
PhantomDeejay
And most probably you need to turn off smart_cue as well
Posted Mon 21 Oct 24 @ 6:16 am
gegenava
I have absolutely the same problem!!
If I quickly press any hot cue after loading a track, sometimes it causes a short freeze in the sound. This started after I started using stems 2.0 with EZremix equalizer. Eventually I had to completely abandon stems, although I have 25 gb of precomputed stems. I tried different settings from the performance section, i set stems to fully disable and used only precomputed stems, it did not help. And the problem only appears the first time I press any hot cue after loading a song.
My laptop has intel i5 1135 g7, 16 gb ram, 2 tb ssd and windows 11. I have tried even to reinstall windows and a clean installation of virtual dj.
If I quickly press any hot cue after loading a track, sometimes it causes a short freeze in the sound. This started after I started using stems 2.0 with EZremix equalizer. Eventually I had to completely abandon stems, although I have 25 gb of precomputed stems. I tried different settings from the performance section, i set stems to fully disable and used only precomputed stems, it did not help. And the problem only appears the first time I press any hot cue after loading a song.
My laptop has intel i5 1135 g7, 16 gb ram, 2 tb ssd and windows 11. I have tried even to reinstall windows and a clean installation of virtual dj.
Posted Mon 21 Oct 24 @ 2:39 pm
gegenava
wickedmix wrote :
sounds like you might want to adjust the AutoCue setting in options to cue so it always loads to the first cue you have set
Thanks for this idea, I will try it.
PhantomDeejay wrote :
And most probably you need to turn off smart_cue as well
I don't use smart cue.
Posted Mon 21 Oct 24 @ 2:40 pm
dashashugaeva
wickedmix wrote :
sounds like you might want to adjust the AutoCue setting in options to cue so it always loads to the first cue you have set
Unfortunately setting "AutoCue loads to the first cue" did not help either. Sometimes its starts to sound from random place of track or even there is just silence, untill i push hote cue or stop/start track again. So, there is one more people here with the same problem, I think it can be virtual djs bug?
P.s. Never use smart cue too
Posted Thu 24 Oct 24 @ 8:13 pm
PhantomDeejay
Do you have SLIP mode enabled ? Do you use SLIP at all ?
Which controller do you use ?
Which controller do you use ?
Posted Thu 24 Oct 24 @ 11:17 pm
gegenava
PhantomDeejay wrote :
Do you have SLIP mode enabled ? Do you use SLIP at all ?
Which controller do you use ?
Which controller do you use ?
Hello. I don't use slip mode
I recorded a video of this happening.
https://vimeo.com/1024005030?share=copy
I was sitting at home, going through my music library, and listening to different tracks, loading them one by one onto the deck. And periodically, once every 30-50 tracks, a track would start playing from a random place, or there would be silence, or, as in the case in the video, instead of music there would be a high-frequency squeak. As soon as I press any hot cue, pause/play, or even sync button, the track would start playing normally. In the video, I simply clicked the mouse in another place on the track and the music would start playing normally. Then I went back to the beginning of the track to show that the problem was not in the audio file. When I reloaded this track, there was no problem playing. All this happens completely randomly, I do not change any modes or settings. And this happens with any controllers I work with (pioneer sr2, rr, XZ, 400) and even at home without a controller, with only a computer, as in the example in the video.
Posted Mon 28 Oct 24 @ 3:21 pm
gegenava
And, by the way, I often use aimp player to quickly listen to some track, and in aimp there is never such a problem, so thats whyI think it is a software bug of virtual dj.
Another example of this bug. I press sync and the sound appears immediately.
https://vimeo.com/1024062335?share=copy
If you need any additional information, I am ready to provide everything I can to find out what is causing the problem.
Another example of this bug. I press sync and the sound appears immediately.
https://vimeo.com/1024062335?share=copy
If you need any additional information, I am ready to provide everything I can to find out what is causing the problem.
Posted Mon 28 Oct 24 @ 5:24 pm
dashashugaeva
PhantomDeejay wrote :
Do you have SLIP mode enabled ? Do you use SLIP at all ?
Which controller do you use ?
Which controller do you use ?
I don't use Slip mode. My controller is DDJ 400, but the problem occurs without a controller.
Posted Mon 28 Oct 24 @ 7:46 pm
dashashugaeva
gegenava wrote :
Hello. I don't use slip mode
I recorded a video of this happening.
https://vimeo.com/1024005030?share=copy
I was sitting at home, going through my music library, and listening to different tracks, loading them one by one onto the deck. And periodically, once every 30-50 tracks, a track would start playing from a random place, or there would be silence, or, as in the case in the video, instead of music there would be a high-frequency squeak. As soon as I press any hot cue, pause/play, or even sync button, the track would start playing normally. In the video, I simply clicked the mouse in another place on the track and the music would start playing normally. Then I went back to the beginning of the track to show that the problem was not in the audio file. When I reloaded this track, there was no problem playing. All this happens completely randomly, I do not change any modes or settings. And this happens with any controllers I work with (pioneer sr2, rr, XZ, 400) and even at home without a controller, with only a computer, as in the example in the video.
Hello. I don't use slip mode
I recorded a video of this happening.
https://vimeo.com/1024005030?share=copy
I was sitting at home, going through my music library, and listening to different tracks, loading them one by one onto the deck. And periodically, once every 30-50 tracks, a track would start playing from a random place, or there would be silence, or, as in the case in the video, instead of music there would be a high-frequency squeak. As soon as I press any hot cue, pause/play, or even sync button, the track would start playing normally. In the video, I simply clicked the mouse in another place on the track and the music would start playing normally. Then I went back to the beginning of the track to show that the problem was not in the audio file. When I reloaded this track, there was no problem playing. All this happens completely randomly, I do not change any modes or settings. And this happens with any controllers I work with (pioneer sr2, rr, XZ, 400) and even at home without a controller, with only a computer, as in the example in the video.
Yea, same problem as me
Posted Mon 28 Oct 24 @ 7:48 pm
dashashugaeva
I think I've found the cause of the problem. In the settings of hot cue page I had macros like:
does hot_cue 7 exist? hot_cue 7: hot_cue 7 and cue_color 7 "green"
almost on all pads. I did this to change the default hot cues colors to the ones I wanted. And it seemed that it was these macros that led to the problem. At least this morning I reset the page hotcues, and throughout the whole day the problem never arose, although today I sorted out a lot of music.
Now I want to understand, the program somehow works incorrectly with these macros, is this some kind of bug? Can it be fixed in updates? Or is the macro itself written incorrectly? (although it works as I need)
Because I really need these macros, they save a lot of time for me.
does hot_cue 7 exist? hot_cue 7: hot_cue 7 and cue_color 7 "green"
almost on all pads. I did this to change the default hot cues colors to the ones I wanted. And it seemed that it was these macros that led to the problem. At least this morning I reset the page hotcues, and throughout the whole day the problem never arose, although today I sorted out a lot of music.
Now I want to understand, the program somehow works incorrectly with these macros, is this some kind of bug? Can it be fixed in updates? Or is the macro itself written incorrectly? (although it works as I need)
Because I really need these macros, they save a lot of time for me.
Posted Thu 31 Oct 24 @ 1:58 am
PhantomDeejay
user27722633 wrote :
does hot_cue 7 exist? hot_cue 7: hot_cue 7 and cue_color 7 "green"
If that's literaly the script you were using, then it has a ton of syntax errors.
The correct script syntax should be has_cue 7 ? hot_cue 7 : hot_cue 7 & cue_color 7 'green'
So, check your syntax and make sure that no mistakes exist on ANY pad.
In theory a script like this should not produce the unwanted results you described, UNLESS it has wrong syntax, and the program "understands" something different than intended..
Posted Thu 31 Oct 24 @ 8:05 am
dashashugaeva
PhantomDeejay wrote :
If that's literaly the script you were using, then it has a ton of syntax errors.
The correct script syntax should be has_cue 7 ? hot_cue 7 : hot_cue 7 & cue_color 7 'green'
So, check your syntax and make sure that no mistakes exist on ANY pad.
In theory a script like this should not produce the unwanted results you described, UNLESS it has wrong syntax, and the program "understands" something different than intended..
user27722633 wrote :
does hot_cue 7 exist? hot_cue 7: hot_cue 7 and cue_color 7 "green"
If that's literaly the script you were using, then it has a ton of syntax errors.
The correct script syntax should be has_cue 7 ? hot_cue 7 : hot_cue 7 & cue_color 7 'green'
So, check your syntax and make sure that no mistakes exist on ANY pad.
In theory a script like this should not produce the unwanted results you described, UNLESS it has wrong syntax, and the program "understands" something different than intended..
Thank you very much for help! I hope the incorrect syntax was causing the problems, I will check it today.
Posted Thu 31 Oct 24 @ 2:30 pm
gegenava
user27722633 wrote :
Thank you very much for help! I hope the incorrect syntax was causing the problems, I will check it today.
PhantomDeejay wrote :
If that's literaly the script you were using, then it has a ton of syntax errors.
The correct script syntax should be has_cue 7 ? hot_cue 7 : hot_cue 7 & cue_color 7 'green'
So, check your syntax and make sure that no mistakes exist on ANY pad.
In theory a script like this should not produce the unwanted results you described, UNLESS it has wrong syntax, and the program "understands" something different than intended..
user27722633 wrote :
does hot_cue 7 exist? hot_cue 7: hot_cue 7 and cue_color 7 "green"
If that's literaly the script you were using, then it has a ton of syntax errors.
The correct script syntax should be has_cue 7 ? hot_cue 7 : hot_cue 7 & cue_color 7 'green'
So, check your syntax and make sure that no mistakes exist on ANY pad.
In theory a script like this should not produce the unwanted results you described, UNLESS it has wrong syntax, and the program "understands" something different than intended..
Thank you very much for help! I hope the incorrect syntax was causing the problems, I will check it today.
I don't think the cause of problem is wrong script, because I don't use scripts on hot cue page, but i have the same problem with "bzzzz" sound sometimes, and start song from random place etc.
Posted Fri 01 Nov 24 @ 4:12 am
dashashugaeva
Unfortunately, the problem remains. Just in case, I deleted all the scripts from the hot cue page, turned on eq Ez remix mode and almost immediately caught the sound "bzzzzzzz" in the main output when pressing the hot cue button on one of the tracks ((. I don't know what else the problem could be. When turning on eq in normal mode, the problem with the sound bzzzzz does not appear.
And at home I have never heard the sound "bzzzzz", it only happened at work, with the controller connected. But the controller is not to blame either, since I work with different controllers and this problem happened with all of them.
And at home I have never heard the sound "bzzzzz", it only happened at work, with the controller connected. But the controller is not to blame either, since I work with different controllers and this problem happened with all of them.
Posted Fri 01 Nov 24 @ 9:50 pm
gegenava
Yesterday i got "bzzzzz" sound even not using Ezremix Eq, when just pushed play button after loading new song on deck. I checked "systemreport session" file in virtual dj folder and there is such a line there
-- Audio Error Log --
-- Audio High Cpu Log --
[23:55] asio://87785D2C-02E7-4E71-A45E557E5693282B (DDJ-SR2 ASIO) : Peak cpu: 4840.92% (1x)
23.55 - is exactly the time when the problem occurred. Maybe this information will somehow help to understand the cause of the problem?
-- Audio Error Log --
-- Audio High Cpu Log --
[23:55] asio://87785D2C-02E7-4E71-A45E557E5693282B (DDJ-SR2 ASIO) : Peak cpu: 4840.92% (1x)
23.55 - is exactly the time when the problem occurred. Maybe this information will somehow help to understand the cause of the problem?
Posted Sun 03 Nov 24 @ 4:26 pm
PhantomDeejay
Do you use realtime stems, or prepared ones ?
Is stems separation (in case of realtime) done via GPU or CPU ?
Also please download and run Latencymon (Latency monitor)
Leave it running in the background, until you can reproduce the issue.
Once that happens, check what Latencymon is saying, and let us know.
We are looking at a potentional driver missbehaving on your system and locking up the audio thread which should not be affected by stems nor report such a high value.
Is stems separation (in case of realtime) done via GPU or CPU ?
Also please download and run Latencymon (Latency monitor)
Leave it running in the background, until you can reproduce the issue.
Once that happens, check what Latencymon is saying, and let us know.
We are looking at a potentional driver missbehaving on your system and locking up the audio thread which should not be affected by stems nor report such a high value.
Posted Mon 04 Nov 24 @ 9:22 am
gegenava
PhantomDeejay wrote :
Do you use realtime stems, or prepared ones ?
Is stems separation (in case of realtime) done via GPU or CPU ?
Also please download and run Latencymon (Latency monitor)
Leave it running in the background, until you can reproduce the issue.
Once that happens, check what Latencymon is saying, and let us know.
We are looking at a potentional driver missbehaving on your system and locking up the audio thread which should not be affected by stems nor report such a high value.
Is stems separation (in case of realtime) done via GPU or CPU ?
Also please download and run Latencymon (Latency monitor)
Leave it running in the background, until you can reproduce the issue.
Once that happens, check what Latencymon is saying, and let us know.
We are looking at a potentional driver missbehaving on your system and locking up the audio thread which should not be affected by stems nor report such a high value.
I have stems option fully disabled, and sometimes i use precomputed stems only. Ok, i will run latencymon next time, when i work with dj controller, thank you
Posted Mon 04 Nov 24 @ 2:59 pm