Originally Posted By: bluage
Dear Noel96...

Well, I tried-out your suggestion, and do you know that it worked?!

I would not have thought to do that because I was reasonably assured that my computer was fast enough to handle most, if not all, of the digital music-making tasks I threw at it.

Nonetheless, your persistence at getting to the bottom of the problem is exemplary and inspiring. Thank you for your help.

Sincerely,

bluage


Hi Bluage,

I, too, would have thought that your computer was fast enough. That being said, though, your composition zooms along at a fair old pace, and that might be part of the problem.

Let me explain ...

When "Fast generation" of Realtracks is enabled, BIAB generates the first few bars of each track and then the song starts playing. The remaining bars of the tracks are completed as a background process while the song plays. This requires are fair bit of computer horse-power.

When "Fast generation" is disabled, the tracks are fully completed before playback begins. This is why it's necessary to wait longer for the song to start.

Thinking about the above made we wonder if maybe the buffer used for "Fast generation" is based on a number of bars. For example, let's say that 8 bars of each Realtrack is generated before the song starts. At a tempo of 100 bpm, this is a reasonable amount of time. When, however, the tempo becomes 200 bpm, the time is halved. If the style used is a waltz, then because there are three beats in a bar, 8 bars will pass even quicker. Under these circumstances, it might be that the buffer is not sufficient and playback completes before the tracks are completed. This would also explain the "Hour glass" cursor that shows the computer is 'thinking'.

I pass these thoughts on for what they are worth. I'm glad you've got it all happening!

All the best,
Noel

MY SONGS...
Audiophile BIAB 2025