Komerad
I found that the pitch faders dont respond very well to virtualdj.
On the controller i see the led going out when leaving 0% position.
But in virtualdj nothing happens. I need to move them forth and back to "wake them up".
But when they get through it sounds awful.
What needs to be done to have pitch control react on every small move?
Extra question there is a little delay on all the faders (jogweels respond instantly) wich makes cutting more or less of a gamble how to solve this?
On the controller i see the led going out when leaving 0% position.
But in virtualdj nothing happens. I need to move them forth and back to "wake them up".
But when they get through it sounds awful.
What needs to be done to have pitch control react on every small move?
Extra question there is a little delay on all the faders (jogweels respond instantly) wich makes cutting more or less of a gamble how to solve this?
Posté Mon 28 May 12 @ 3:06 pm
djranes
Most controllers if not all are pre-mapped like that as a software safety to avoid accidentally jump off of pitch if the slider is touched in a huge margin by mistake.
Re-map the pitch slider to "pitch_relative" if you want to have an instant movement between your controller and the software.
As for the delays with the software response to the controller's command, it may have something to do with the soundcard latency setting. The higher latency is set the less responsive your software is. As much as possible, keep your latency set as low as your system can possibly handle without any glitch with the audio output.
Re-map the pitch slider to "pitch_relative" if you want to have an instant movement between your controller and the software.
As for the delays with the software response to the controller's command, it may have something to do with the soundcard latency setting. The higher latency is set the less responsive your software is. As much as possible, keep your latency set as low as your system can possibly handle without any glitch with the audio output.
Posté Mon 28 May 12 @ 4:37 pm
Support staff
Please see our FAQ pages:
http://www.virtualdj.com/wiki/Soft%20Take-over%20or%20Non-MIDI%20Mixer.html
Also, make sure that your system is optimised for low latency audio:
http://www.virtualdj.com/wiki/Performance%20Issues.html
http://www.virtualdj.com/wiki/Soft%20Take-over%20or%20Non-MIDI%20Mixer.html
Also, make sure that your system is optimised for low latency audio:
http://www.virtualdj.com/wiki/Performance%20Issues.html
Posté Tue 29 May 12 @ 4:22 am
Komerad
Thank you for the respons, remapped the pitch fader and it is responding well now.
I gues the latency thing is trial and error i will look into that when i got some more time.
(Still recovering from a weekend with to much party and to few sleep.)
I gues the latency thing is trial and error i will look into that when i got some more time.
(Still recovering from a weekend with to much party and to few sleep.)
Posté Tue 29 May 12 @ 11:22 am
Komerad
Got another question (onn how to use latencymon)
Without running virtualdj it says my system is suitable, with virtualdj it aint.
Am i to run this monitor with or without running virtualdj?
(Must say the difference in barsize is huge with vdj running)
Laptop : i7-2670QM@2.20 with 8Gb ram
Without running virtualdj it says my system is suitable, with virtualdj it aint.
Am i to run this monitor with or without running virtualdj?
(Must say the difference in barsize is huge with vdj running)
Laptop : i7-2670QM@2.20 with 8Gb ram
Posté Tue 29 May 12 @ 1:39 pm
Support staff
You should check both with VirtualDJ loaded and not loaded.
If it's OK when VirtualDJ is not loaded but when VirtualDJ is running it increases significantly, then this means that something is not configured correctly in VirtualDJ.
This could be because you have either resized or maximised the skin - On some systems this can cause excessive CPU usage depending on your graphic card's capabilities. Make sure that you either use the skin at its correct native size or download a custom skin that matches your screen size from http://www.virtualdj.com/addons/skins.html
Please see: http://www.virtualdj.com/wiki/Performance%20Issues.html
Also, make sure that you have the latest drivers and firmware for the VCI-400 installed - Please see: http://www.virtualdj.com/wiki/VCI-400.html
NOTE: The lower the latency setting you choose in CONFIG -> Sound Setup -> ASIO Config, the more CPU will be required
If it's OK when VirtualDJ is not loaded but when VirtualDJ is running it increases significantly, then this means that something is not configured correctly in VirtualDJ.
This could be because you have either resized or maximised the skin - On some systems this can cause excessive CPU usage depending on your graphic card's capabilities. Make sure that you either use the skin at its correct native size or download a custom skin that matches your screen size from http://www.virtualdj.com/addons/skins.html
Please see: http://www.virtualdj.com/wiki/Performance%20Issues.html
Also, make sure that you have the latest drivers and firmware for the VCI-400 installed - Please see: http://www.virtualdj.com/wiki/VCI-400.html
NOTE: The lower the latency setting you choose in CONFIG -> Sound Setup -> ASIO Config, the more CPU will be required
Posté Wed 30 May 12 @ 6:04 am