danielsr2006
Ok. I dont mean to bother you guys but Im new to djing and new to computers. It seems like you have to damnthere be a tech if you want to go digital. I was curious if this was normal.
I get probly 1 of 4 songs that spike cpu up to 95%. The other times it only gets to about 65%. So is it some songs ok or should I be concerned? I dont have any noticeable popping or any other problems. After songs are already loaded it stay about 20 to 35%. I wont mess with settings if thats ok.
Specs: Windows 7;Dual core 2.50 GHz;4 gig ram; 64 bit
Performance:Auto safe mode; optimize for quality;fast stretching; quality resizing; quality resampling; and Dark Default HD skin
I dont remember what setting I changed couple of weeks ago but it killed latency for scratching. Im not a scratcher but id be nice to have just in case.(wouldnt sacrifice scratching for good performance) I wanted to know if these settings are ok because Im keeping my fingers crossed cause Im competing against two other djs for a residency at a local bar. I only had one real gig but it was before the rmx so it was with cheap cd players. Any advice or suggestions on these settings would be greatly appreciated!!!
Thank You!! Daniel:-)
I get probly 1 of 4 songs that spike cpu up to 95%. The other times it only gets to about 65%. So is it some songs ok or should I be concerned? I dont have any noticeable popping or any other problems. After songs are already loaded it stay about 20 to 35%. I wont mess with settings if thats ok.
Specs: Windows 7;Dual core 2.50 GHz;4 gig ram; 64 bit
Performance:Auto safe mode; optimize for quality;fast stretching; quality resizing; quality resampling; and Dark Default HD skin
I dont remember what setting I changed couple of weeks ago but it killed latency for scratching. Im not a scratcher but id be nice to have just in case.(wouldnt sacrifice scratching for good performance) I wanted to know if these settings are ok because Im keeping my fingers crossed cause Im competing against two other djs for a residency at a local bar. I only had one real gig but it was before the rmx so it was with cheap cd players. Any advice or suggestions on these settings would be greatly appreciated!!!
Thank You!! Daniel:-)
Posté Wed 31 Aug 11 @ 12:52 am
Support staff
High CPU usage while loading songs is normal. VirtualDJ will use all spare CPU to load and analyse the song as fast as possible. This should not cause any audio issues unless there are other performance issues with your computer.
NOTE: Quality resampling will result in slower loading of 48Hz videos.
For optimal scratch performance, an low latency capable ASIO sound card is required with the buffer set as low as your comptuer can handle without experiencing sound break-up, stuttering, etc. The buffer size is changed via CONFIG -> Sound Setup -> ASIO Config. If you are unable to set a low enough buffer size, please see http://www.virtualdj.com/wiki/Common%20PC%20Performance%20Issues.html
NOTE: Quality resampling will result in slower loading of 48Hz videos.
For optimal scratch performance, an low latency capable ASIO sound card is required with the buffer set as low as your comptuer can handle without experiencing sound break-up, stuttering, etc. The buffer size is changed via CONFIG -> Sound Setup -> ASIO Config. If you are unable to set a low enough buffer size, please see http://www.virtualdj.com/wiki/Common%20PC%20Performance%20Issues.html
Posté Wed 31 Aug 11 @ 10:06 am
danielsr2006
Support staff wrote :
High CPU usage while loading songs is normal. VirtualDJ will use all spare CPU to load and analyse the song as fast as possible. This should not cause any audio issues unless there are other performance issues with your computer.
NOTE: Quality resampling will result in slower loading of 48Hz videos.
For optimal scratch performance, an low latency capable ASIO sound card is required with the buffer set as low as your comptuer can handle without experiencing sound break-up, stuttering, etc. The buffer size is changed via CONFIG -> Sound Setup -> ASIO Config. If you are unable to set a low enough buffer size, please see http://www.virtualdj.com/wiki/Common%20PC%20Performance%20Issues.html
NOTE: Quality resampling will result in slower loading of 48Hz videos.
For optimal scratch performance, an low latency capable ASIO sound card is required with the buffer set as low as your comptuer can handle without experiencing sound break-up, stuttering, etc. The buffer size is changed via CONFIG -> Sound Setup -> ASIO Config. If you are unable to set a low enough buffer size, please see http://www.virtualdj.com/wiki/Common%20PC%20Performance%20Issues.html
Allright teamer. Thank you for the response. I forgot to say, I dont do videos or anything fancy like that. I have HP dv7. I just downloaded dpc latency checker....I had reallly bad red high spikes until I disabeld wifi. I new to disable wifi when bein on vdj from reading other posts. sometimes I just need dumbed down explanations unfortunately,sorry. So when I disababled wifi all cpu stayed well under 500 us!!! So does that mean that even though I get high spikes when loading a nonvid track and get spike in red it still ok since I dont have any noticeable sound distortion? Thanks ahead for any response in help. Like i stated, competing against two non vdj users. I tried misconfig and to disable nonneeded stuff but for some reason it says something like unable, or something silly.
Thank for Virtual Dj Support!!! Daniel :-)
Posté Thu 01 Sep 11 @ 3:33 am
ianmelville
Have you scanned all you music for BPM / KEY and all that good stuff, or are you just playing songs for the first time.
If you have not scanned and are playing for the first time VDJ will be analyzing the song when it loads (bpm,key, and so on), so it will use more CPU.
A good working practice is to scan all your music first before playing tracks.
Hope this helps
If you have not scanned and are playing for the first time VDJ will be analyzing the song when it loads (bpm,key, and so on), so it will use more CPU.
A good working practice is to scan all your music first before playing tracks.
Hope this helps
Posté Thu 01 Sep 11 @ 3:43 am
danielsr2006
ianmelville wrote :
Have you scanned all you music for BPM / KEY and all that good stuff, or are you just playing songs for the first time.
If you have not scanned and are playing for the first time VDJ will be analyzing the song when it loads (bpm,key, and so on), so it will use more CPU.
A good working practice is to scan all your music first before playing tracks.
Hope this helps
If you have not scanned and are playing for the first time VDJ will be analyzing the song when it loads (bpm,key, and so on), so it will use more CPU.
A good working practice is to scan all your music first before playing tracks.
Hope this helps
Yes they have all been scanned. I feel like Ive tried all basic things that I comprehend. I guess the only thing Im not understanding Is if its normal for some songs to load high cpu like in the red about 97% and other tracks about 60% max. I havent noticed any distortion problems in either cpu loading %. I just wanna make sure I have a good running system to handle those long hours, in case I get that residency(Im praying for).
Thanks for response: Daniel :-)
Posté Thu 01 Sep 11 @ 4:37 am
Support staff
If you mean that you get a spike in the red in the CPU usage bar at the top of the screen, then this is not a problem and is normal when loading a song.
If you mean that you get a red spike in DPC latency checker, then you have other performance issues with your computer. However, high DPC latency spikes will only normally be a problem if you are using low latency ASIO drivers. Normal Windows sound (WDM) will not normally be affected. Low latency ASIO is only important if you are scratching.
If you mean that you get a red spike in DPC latency checker, then you have other performance issues with your computer. However, high DPC latency spikes will only normally be a problem if you are using low latency ASIO drivers. Normal Windows sound (WDM) will not normally be affected. Low latency ASIO is only important if you are scratching.
Posté Thu 01 Sep 11 @ 7:49 am
danielsr2006
Support staff wrote :
If you mean that you get a spike in the red in the CPU usage bar at the top of the screen, then this is not a problem and is normal when loading a song.
If you mean that you get a red spike in DPC latency checker, then you have other performance issues with your computer. However, high DPC latency spikes will only normally be a problem if you are using low latency ASIO drivers. Normal Windows sound (WDM) will not normally be affected. Low latency ASIO is only important if you are scratching.
If you mean that you get a red spike in DPC latency checker, then you have other performance issues with your computer. However, high DPC latency spikes will only normally be a problem if you are using low latency ASIO drivers. Normal Windows sound (WDM) will not normally be affected. Low latency ASIO is only important if you are scratching.
See there it is! after reading other posts I did not know there was a difference between the cpu it showed in youre skin vs what youre computer is doing in the background. I thought they coincided with each other exactly. I feel so stupid now. Now I feel confident in my system now.
Thanks so much! Daniel
Posté Thu 01 Sep 11 @ 1:11 pm
Support staff
The CPU meter does show what your computer is doing at any given time, but it is an average over a given time period (I.e: It will be high when loading a song due to VirtualDJ processing it to show the waveform, etc. and scanning it for BPM/key/gain if it's the first time that you're loading it.)
Too many background processes can cause increased CPU usage, but this will only normally be a problem if you are running multiple programs at once or there is unnecessary software running in the background ('bloatware'.)
High DPC latency spikes are a different matter - It means that a driver (E.g: WiFi) momentarily ties up the CPU too long to make low latency audio processing possible. The time is normally too short to have any effect on WDM audio due its larger buffer size. For a more detailed explanation, see http://www.thesycon.de/deu/latency_check.shtml - However, because you are not using ASIO, this doesn't really matter.
Too many background processes can cause increased CPU usage, but this will only normally be a problem if you are running multiple programs at once or there is unnecessary software running in the background ('bloatware'.)
High DPC latency spikes are a different matter - It means that a driver (E.g: WiFi) momentarily ties up the CPU too long to make low latency audio processing possible. The time is normally too short to have any effect on WDM audio due its larger buffer size. For a more detailed explanation, see http://www.thesycon.de/deu/latency_check.shtml - However, because you are not using ASIO, this doesn't really matter.
Posté Thu 01 Sep 11 @ 6:42 pm