<< I wonder, why PG Music doesn't give this reference chord sheet of each RealTrack to its users? The size is very small. With this reference chord mapping chart, it is 100% accurate because Brent Mason recorded the whole track based on it. If BiaB starts to generate sour notes or inconsistent octaves on any RealTracks, a user with this chord chart can simply drag the source wma to his DAW, quickly find the chord he needs, cut it out, and get it done.

I truly hope, there's a way of achieving this. >>

I can't speak for PGMusic and I'm not affiliated with them in any way, however, I've studied the BIAB production process, demos, and forum discussions to surmise the following.

The fact there are sour notes by top grade session players who obviously didn't play sour notes is a big clue to what's going on. What users presume are sour notes that somehow made it through the PGMusic developers, engineers and quality control that's certainly in place is a major clue that sour notes are 'out of place' rather than wrong. The Bt, ST2 and XT2 files exist for the BIAB algorithm and I presume are proprietary information that work in conjunction with WAV instructions. The decoded text files I've seen presented to capture chords and decode progressions have never contained any of the advanced processing that's in BIAB generated tracks. The fact that BIAB has a tool to correct sour notes is also a clue the issue is related to the algorithm selection process and not poorly played notes or chords.

It's my thought that users who generate tracks and export out to DAW's as quickly as possible are getting the rawest and most elementary track that BIAB can produce and users lose 100% of most advance features BIAB is capable of producing the moment they export or generate tracks from the main program, Plug-in or RealBand.

It's not possible to quickly find the best possible replacement for a sour note that's a better choice than BIAB can do it for several reasons.

First, as Jim Fogle displayed, there are normally multiple audio recordings for a RealTrack. However, BIAB can search and select audio from multiple RealTracks other than the one displayed in the Mixer. Users may or may not know of the RealTrack Medley Maker that provides 10 additional slots for any other RealTrack to be merged with the main RealTrack displayed in the BIAB Mixer. This feature is available for the seven original Legacy Tracks. Therefore, BIAB can generate up to 77 separate RealTracks in a single render and can manipulate how these 77 slots will play out in the BIAB Chord Chart in 8-10 different ways. By various bar counts (2,4,8,16,32), Part Markers, Choruses, whole song, and manually or play them all simultaneously. This is evidence BIAB can read from and select audio from a minimum of eleven different RealTracks at once.

These track sub-mixers have panning and volume controls for each additional RealTrack. There are special RealTracks to specifically interact with these sub-mixer RealTracks that along with WAV instructions direct the BIAB to make specific audio choices for intro's and outro's and process multiple actions across a single measure of the chord chart where one RT instrument is fading and another fades in, providing cross fading and correct audio for an ending for instrument and opening phrasing for the other instrument.

A user can designate all seven mixer tracks and sub-mixer tracks to specifically take advantage of the BIAB algorithm in order to comp a single instrument performance that's saved as an Artist Performance File. The Artist Performance File is imported and placed on a Legacy or Utility Track and the process can be repeated for another instrument. This process can be repeated over and over.

BIAB recognizes RT-1152 Silence the same as other RT's and BIAB will react differently and select different audio snippets than if a user chooses to use the (F5) mute feature and this method eliminates abrupt cut-off endings and intros. The difference is due to when using RT-1152 or any other RT, BIAB selects the audio based on the Chord Chart and Mixer programing which is a pre-render action whereas using (F5) mute is a post-render action.

Many users may never think of a time to need 77 RealTracks in a song and that's true. But, it's important to note these are RealTrack slots. This means as few as two RealTracks is all that's necessary to fill these slots in a pre-render arrangement format allowing a single song that consists of hundreds of variations and changes between the RealTracks. This makes it incredibly fast and easy to swap instruments while retaining the arrangement of the instruments and allows the BIAB algorithm to provide all its advanced features.

Note also that PGMusic staff finalizes all of the demos, demo with vocals, lessons and RealTrack/RealStyle videos as BIAB files. Not as RealBand Seq files, Pro-tools, Sonar, Studio One, Cakewalk or Reaper files. They use these software tools, but not from the inside out to finish them but from the outside in.

Then there's the additional features like MultiStyles that aren't recognized by the Plug-in, RealBand or any DAW.

While this is speculation on my part, so far, treating the speculation as true has given me the expected results 100% of the time.


BIAB 2026:RB 2026, Latest builds: Dell Optiplex 7040 Desktop; Windows-10-64 bit, Intel Core i7-6700 3.4GHz CPU and 16 GB Ram Memory.