Originally Posted by JosV
Okay, thanks for all your answers. I appreciate it very much.
Partial regeneration is what I'll try next!
Question remains though: why won't BiaB simply play exactly the A chord as entered. If I wanted an 7th chord I would have put an A7. I doesn't seem logical to me.

Regards, Jos
Hi Jos,
This is what I mean by "mapping". I don't know if PG Music use this terminology. It's simply a word that does the job for me.

What happens with Realtracks, is that the performer plays a predetermined sequence of chords across a number of keys and creates a number of audio track. If you go to the \bb\Realtracks folder and have a listen to some of the audio files, you'll hear what I mean.

After this is done, PG Music map where in the audio specific chords occur. These time-based audio coordinates are then used by BIAB when it reads the chordsheet and dices and splices chords together to create a backing track. In the original audio, it's possible that sometimes the mapping that exists for an A chord also includes an A7. This means that when you generate a song, sometimes you get A and sometimes you get A7. When PG Music know about this error, they can redefine/re-map the time coordinates so that A7 is no longer present in the A-chord section.

This is why freezing all the song file tracks when the error is present, and then sending a copy of the frozen-track file to PG Music is the first step in correcting the mistake. Because the file is frozen, when PG Music generate it, they will get the same error that is present in the file. So if you tell them which bars to listen to, they will hear the same thing as you. PG Music will then know what the problem is and they will correct it with an adjusted interpretation of the Realtrack's audio. Ultimately, this will be sent to users when BIAB is updated.

I hope this helps explain things.
--Noel

MY SONGS...
Audiophile BIAB 2025