Tempo problem in build 299- can you replicate?

PG Music Home

Hi:

I have BIAB 2010, build 299 and all the latest RTs and RDs.

I'm having a tempo problem that I think might be a bug and I want to see if anyone can duplicate this scenario:

I have a song with a tempo of, say, 100. I keep that tempo until the last few measures where I slow the tempo down using F5, to say 90 and then to 85.

The song will play fine and the tempo will slow down as it is supposed to.

BUT, when I hit play or regenerate, the song starts playing at the 85 bpm it was last playing at, not the 100 bpm that was saved with the song.

I have used this technique is many songs before and BIAB has never acted this way before.

This seems to occur with all RT or midi songs.

Can anyone with build 299 replicate this behavior?

Thanks.

John

Hi John,

I just made an 8-bar song at 110 bpm and slowed it down at bar 7 to 60 bpm. When I replayed, or generated, it started again at 110 bpm. Do you have any frozen tracks present? That might be causing this problem. (I always monitor the Soloist track because it automatically freezes when I save.)

Regards,
Noel

Noel:

No, I don't have any frozen tracks.

I just tried an 8 bar song at 100 bpm and slowed it down to 80 at bar 7.

After it played through, I clicked on "play" and the song regenerated but this time at 80 bpm.

Do you have build 299 ?

Thanks.

John

Hi John,

Yes, I have build #299. I cannot work out what might be causing your problem. If I had this problem, I'd try re-installing build #299 update. If that didn't solve the problem, I'd go Opt >> Return to factory settings. Sometimes something seems to get tweaked in the program and returning to factory defaults is the only way out.

Regards,
Noel

Hi John,

I noticed the same bug.
As a workaround try pressing F5 in the first bar and set tempo to the normal song tempo of 100.
So BIAB will start the song allways with correct tempo.

PGMusic should fix that bug with the next update.

Ralf

This can happen if you don't wait for BIAB to actually finish the song before hitting play again. Wait a few seconds after the song ends before hitting play and see what happens. Also, what happens if you hit Replay instead?

Ralfboe, Yes, using F5 to put a tempo in the first measure is a workaround until this is fixed. good idea.

BarryKJ: It doesn't matter if I wait for the song to finish or not, or if I use play or replay, the song always starts again at the slower tempo.

BIAB never used to behave this way before.

John

Works just as it should here.

Do you have build 298 around to revert back to and check that particular song with that build? It shouldn't cause any trouble to go backwards - I've done it before without issue. At least that would isolate it to build 299 and not some other tweak or file corruption.
Good luck.

Quote:

Works just as it should here.

No bug it works fine.

Silvertones:

Do you also have build 299?

I'm wondering why some people are having this problem and some aren't.

Thanks.

John

Yes I do have 299.
Have you done a return to factory settings? I know everyone hates that but that's what it takes in a lot of circumstances. Even during Beta we find ourselves reminding each other of that .

Silvertones:

I returned to factory settings and it still has the problem.

Noel and Silvertones:
Are you folks on XP or Windows 7 ?

Ralfboe: are you on XP or Windows 7?

I talked to tech support and they did not have a problem with a windows 7
computer.

I am on XP.

Thanks.

John

XP SP3
I've tried and tried to replicate for you but can't get it to do it.

I'm on Windows 7 (both 32 and 64-bit)

Ralf

I'm starting to see a bit of trend with this tempo problem.

An all-midi songs does not seem to have a problem when I change the tempo at the end of song. But as soon as I add either a RealTrack or RealDrums to an all-midi song, the tempo problem appears.

The next time I play or regenerate, it starts playing at the slower tempo of the song's end.

I also opened up a couple of BIAB demo songs that have both midi and RTs and RDs. Those songs also had the tempo problem. But as soon as I eliminate the RT and force midi drums instead of RDs, the tempo problem disappears.

The tempo slows down at the end, but then will again play at the correct tempo if I play it again.

Adding a RT or RD definitely causes the problem but I don't know what this means exactly.

John

Hi John,

I have managed to replicate what might be related to the behavior you are experiencing. Here's what I did...

create an 8-bar song
set the tempo to 140, key C, choose and all-MIDI style
set the tempo of bar 7 to 80
leave the number of choruses set to the BIAB default of 3

Now, when the song repeats and enters the second chorus, it plays at the slower tempo. I'd imagine that this is by design because choruses 1 and 2 are independent of each other and chorus 1 leads into chorus 2.

The difference between my behavior and what you have experienced, is that when I regenerate (with all tracks unfrozen), the song will once again play at 140. I note that for you, this has not been the case. How many choruses do you have your song set to?

I posted this just in case it helps with your investigation.
Noel

P.S. I use Vista 32-bit and have no issues with the tempo in the way that you've describe.

I tried it with 4 RTs and RD and couldn't make it mess up.

Hello,

I can't duplicate this problem. Perhaps you could send a song that it happens with to support @pgmusic.com. If you do this, please refer to this forum thread in your email.

Noel:

THe length of the song doesn't seem to matter.
For testing I have simply done an 8-measure song at 120 bpm and the slowed the tempo to 115 at measure 6 and 110 at measure 8.
An all midi song wil play and change tempo and then as soon as it stops the tempo reverts to 120.

A song that has either a RT or a RD will play through, slow down as it is supposed to and then stay at the slower tempo. When I play the song again it then starts out at the slower tempo. -- Thanks for trying your experiment.

Andrew:

I have sent some songs to Rob at tech support.
I have delected intrface.bbw and mysetup.dk and started over and also rebuilt the realtracks and reinstalled build 299 and it still does this behavior.

Thanks.

John

Andrew:

I got to thinking that the problem always appears when there is a RT or RD present and wondered if the audio driver might be causing the problem.

I have an M-Audio 2496 and have used ASIO (always on) for years with no problem.

As an experiment, I switched to MME drivers and the tempo problem stopped.

My song slowed down near the end as it supposed to and then when the song stopped, the tempo reset to the original tempo.

I don't know what this tells you.
Why would MME drivers allow BIAB to reset the tempo but the m-audio ASIO drivers cause this problem. I've never had a problem with ASIO before.

Thanks.

John

...

Dang, silvertones, okay. We get it. You aren't having the problem at your end.

But this fellow obviously IS having the problem, so let's pitch in and try to HELP solve it, 'K?

--Mac

Mac has suggested that I look at what midi output I'm using and I think he's on to something.

I was using Delta AP midi to an external synth when having problem with the tempo not resetting.

When I switched to the the internal VSTi synth (with the box checked for "route midi thru to midi driver") the tempo problem stopped. Now I can slow down the tempo of a song at the end and the tempo will reset at the end to the original file tempo.

I would never have thought of this as a solution, especially since I had tried all-midi songs playing through my external synth and was not having the tempo reset problem.

Thanks, Mac for a good idea.

John

I think this may be a bug.

A bug that only shows when using a *hardware* MIDI output in BiaB...

Software synth, like the DXi, it does not show up.

Hardware output to synth, it shows up.

John, be sure to send an email to PGMUSIC DEVELOPMENT directly with this important piece of information -- and a link to this thread also.

--Mac