Sign In:     

Forum: Old versions

Topic: VDJ 6.0.5 incorrect BPM counter [TIMECODE]

This topic is old and might contain outdated or incorrect information.

I've installed v6.0.5 this Saturday, and immediately I found that the BPM calculated on the main screen was wrong. Comparing the v6.0.4 where the counter was strangely waving upside-down with +/- 0.05% now I got it all wrong! At the moment I am playing at 0% a 128bpm track which now shows at 128.38. Sometimes after a while it changes to other value. I will have to get back to 6.0.4 :) Setup is a Sony Vaio Laptop VGN-FW21E, Windows Vista, Maya USB, Timecode CD.
 
Posted Mon 28 Dec 09 @ 4:27 pm
me also, no timecode

many tracks now have wrong bmp, and have to bpm tap way more often now, even on tracks that used to be fine
 
DJ Mecho wrote :
I've installed v6.0.5 this Saturday, and immediately I found that the BPM calculated on the main screen was wrong. Comparing the v6.0.4 where the counter was strangely waving upside-down with +/- 0.05% now I got it all wrong! At the moment I am playing at 0% a 128bpm track which now shows at 128.38. Sometimes after a while it changes to other value. I will have to get back to 6.0.4 :) Setup is a Sony Vaio Laptop VGN-FW21E, Windows Vista, Maya USB, Timecode CD.


Set the pitch sensitivity on the timecode debug @ 0.50 %.
 
well, i am trying this right now. until v6.0.4 everything was smooth with upgrades. the result now is a bit better response from the pitch control, but it's not what i am expecting. actually again, it is not correct most of the time. example: now i'm playing a 128bpm track with 0%. when i set it to +0.8% it should become around 129bpm.. but sometimes it 128.85, sometimes is 129.03. and stays still till i move the pitch again. i think there's a big change in the timecode engine ;)
 
ops, what i forgot to mention, and it is very important is that this is bpm displayed that is wrong. otherwise the players are synced at the same bpm :) i mean if it shows wrong, it plays correctly ;)
 
Did you at least tried what I suggested??

Let us know if you did, so we can try to help you some more.......

Just play around with the pitch sensitivity around the 35% to 50% range. This is the only workaround for now until the next update.
 
yes, i did that setting at the Debug screen, now it is 0.5% sensitivity and is relatively ok for me ;) thank u!
 


(Old topics and forums are automatically closed)