tempo

Hi,

anybody know why tempo changes slip back when a sequence is reloaded?

For example if I have a tempo change from 120 to 130 bpm in a song and save it off and come back to it another day - when I reload the tempo will be randomly out to say 119.8 to 129.6 bpm and not the origional 12o to 130.

This is a serious problem as how can you sample / sequence when time slips!!!

Also, any idea why when adding bars to a song the tempo track isnt auto update to represent this - this is also very annoying as with new bars added or subtracted all the tempo cha nges from previous are now out of time!!

Help,

Ta,

Alex

alfonce wrote:Hi,

anybody know why tempo changes slip back when a sequence is reloaded?

For example if I have a tempo change from 120 to 130 bpm in a song and save it off and come back to it another day - when I reload the tempo will be randomly out to say 119.8 to 129.6 bpm and not the origional 12o to 130.

This is a serious problem as how can you sample / sequence when time slips!!!

Also, any idea why when adding bars to a song the tempo track isnt auto update to represent this - this is also very annoying as with new bars added or subtracted all the tempo cha nges from previous are now out of time!!

Help,

Ta,

Alex

I have questions on how did you save the sequence and program the sequence?

Did you make tempo changes within one long sequence?


Did you make separate sequences with different tempos?

Did you close the window when you made changes within the Tempo change window?

Did you save as all sequences and songs?

I haven`t had the tempo problems you mention so I`m backtracking with questions to see what may have gonna wrong.


As far as inserting empty bars that makes since cuz tempo changes affect a selected region which you the user have to set. Music theory is by measures and bars yes, but the sequence is a midi edit within a selected region in time not a absolute measurement, so if the region of time wasn`t selected then no tempo change event would have been inserted.


Good luck and I`ll see what answers to come up with?


Alot of times it is something quite simple.

Hi,
I also have the same problem that tempo changes slip back when reloading a sequence!
At every saving/loading procedure, there's a slip back about 0.1 to 0.2 bpm. So if I edit a sequence 5 times and save/load it, there may be a tempo change of about 1 bpm!!! For example, once I have synchronized a sample with the sequenze-tempo it doesn't match after reloading.
(Sorry for my bad english)

Stefan

These are old threads, probably had an earlier os. Are you the latest os?

OS is 1.71

I have three MPC-4000, each of them produces the same problem.

It's reproduceable. Please test it out:

I have one Sequence in RAM, about 4 bars long. Now make Tempo-Changes in the bpm-Window:

For example:
Original Tempo: 120bpm
1/1/0: 120.0 bpm
Insert 3 Tempo Changes:
2/1/0: 110.0 bpm
3/1/0: 100.0 bpm
4/1/0: 90.0 bpm

Now save this Sequence and reload it (you can also power off the MPC and load the Test-Sequence)

Now, opening the Tempo-Change-Window it show's:
1/1/0: 120.0 bpm
2/1/0: 109.9 bpm
3/1/0: 99.9 bpm
4/1/0: 89.9 bpm

after saving this sequence and reload it (even with another name) the Tempo-Window now shows:
1/1/0: 120.0 bpm
2/1/0: 109.8 bpm
3/1/0: 99.8 bpm
4/1/0: 89.8 bpm

and so on...

Any idea?

perhaps time to change the small battery inside the machines?

White 4k w/ 1.7.1 add tempo changes (4 bars/4 tempos) save entire memory switch off then back on reload everything and the tempo changes are correct.

If you really have 3 different 4k's and they all do it then it's something that you are doing to cause it.

Thank you for your feedback!

Yes, there are three 4k's, two white, one blue! All with 512MB Mutec Ram. No crash since 8 years! No problems ever!

Change the batteries? I will do it! Does anyone know the type of it, so I could buy some before opening the MPC?

This problem makes me going crazy!

Tomorrow, I'm on stage with the machine, so I will try it with another AC-power. Maybe bad AC at home? But I use a Furman!

Are there any Global/Internal settings I could do wrong?

I will try to save the "entire memory". Now, I only saved "Sequence"

I would highly doubt the battery.
There is nothing about what you are doing that would be dependent on the battery since you are actually talking about saving and then reloading.

Then there is the aspect of 3 different machines doing it.

Here's an idea, make a sequence that then save it and upload it to a file host so that we can download it and load it to see if it slips.