Page 1 of 1

From time to time will not calculate proper BPM

PostPosted: 12 Jan 2009, 11:09
by Grant Carlisle
From time to time, i have had a 130 bpm track come up as 100-106 BPM. This is not a problem as far mixing goes, I can beat match without a BPM counter however, when looping the wrong Calculated BPM track it will not loop seemlessly, this is a problem as a lot of my mixing is done by caring the last track into the next track in a loop for as long as harmonically possible. Is there a way to go back and have the program recalculate the BPM. I have noticed once the program has done the calculation once it will never recalculate on it's own, even when shutting down and restarting. the only way around this i have found is re-installing the program and this is a pain in the ass.

No big deal just looking for a hint. :mrgreen:
Furthermore this is a very isolated issue.

Re: From time to time will not calculate proper BPM

PostPosted: 12 Jan 2009, 11:48
by gakto2009
heay grant..

can you post me a config file so i can have a look at something please.

Sometimes the auto bpm feature cannot accurately determine the actual bpm of a track for many reasons, more often than not however it does get it correct. Some of the factors that can interrupt the process is, a poor quality track, bad encoding of the track, heavy bass (deliberately produced this way) etc.

I can’t say for sure because my demo version of home 7 has expired, however I’m sure that if you right click a song in your media base there is an option to analyse the bpm manually. With this option you will be able to work out the bpm by tapping the space bar in time with the song or by an interval of 16 beats chosen by yourself.

Hope this helps,
Regards,
Bryan.

P.s.
I have noticed once the program has done the calculation once it will never recalculate on it's own


Right click the song in the media base, select "analyse BPM/Peak/Gain/Duration automatically".

Ctrl+A (to select all your songs in the media base) and following this will re analyse your full media base.

Re: From time to time will not calculate proper BPM

PostPosted: 12 Jan 2009, 22:42
by Grant Carlisle
Config Report:
Config 2009/01/12 15:38

OS=Microsoft Windows XP Service Pack 2 build=2600 processor=PROCESSOR_IDENTIFIER=x86 Family 6 Model 13 Stepping 8, GenuineIntel
MixVibes HOME version=7.043 DLL langage=US version=7.040

System Setting
--------------------
Load in Ram Channel1= Yes Channel2= Yes
Load memory time limit=13 Load time=normal
Low gui priority=No Equalization bypass=No
MultiInstance=No

General Setting
--------------------
Nb Mixer Channels=2 Nb Samples=16
Windows Caption=No Theme=0
TAG V1=Yes TAG V2=Yes

Mix Setting
--------------------
AutoCue=Yes AutoGain=Yes AutoBpm at Load=Yes
Display Pitch=Yes Auto Match at load=No
Bpm Range min=120 max=150
Loop in bar boundaries=Yes Security=No History=No
Compressor=No Limiter=No

Sound Configuration
--------------------
Nb Sound=2 Nb Mixer=0



should be here

Re: From time to time will not calculate proper BPM

PostPosted: 12 Jan 2009, 22:50
by gakto2009
Mix Setting
--------------------
AutoCue=Yes AutoGain=Yes AutoBpm at Load=Yes
Display Pitch=Yes Auto Match at load=No
Bpm Range min=120 max=150
Loop in bar boundaries=Yes Security=No History=No
Compressor=No Limiter=No


I wanted to have alook at your BPM range, you have it set fine to read BPM of 130.

you can set the BPM's manualy and save the information to the tags... so you only have to do it once.

happens to us all friend, its not a bug.

regards,
Bryan

Re: From time to time will not calculate proper BPM

PostPosted: 12 Jan 2009, 23:29
by Grant Carlisle
gakto2009 wrote:
Mix Setting
--------------------
AutoCue=Yes AutoGain=Yes AutoBpm at Load=Yes
Display Pitch=Yes Auto Match at load=No
Bpm Range min=120 max=150
Loop in bar boundaries=Yes Security=No History=No
Compressor=No Limiter=No


I wanted to have alook at your BPM range, you have it set fine to read BPM of 130.

you can set the BPM's manualy and save the information to the tags... so you only have to do it once.

happens to us all friend, its not a bug.

regards,
Bryan


Yeah I reconfigured the range last night after i posted this. It hasn't done it since, so...... :)