Originally Posted by Charlie Fogle
Originally Posted by Rob Helms
Thanks for the information. This to me is a bad workflow. The system should be able to see that the audio is longer than the 32 bars and remind you or just analyze it. Just another example of a really cool feature that is not really completely thought out. When you import an audio file the whole file is visible in the Audio Edit window. If it intends to only do 32 bars then the 32 bars should be highlighted, or the rest of the bars greyed out. Anything so the customer knows what the issue actually is.
The important thing you are missing is how the audio file gets into BIAB makes a difference.

BIAB knows the difference between the length of the audio file and the Chord sheet and it does display the appropriate bars.

BIAB will either open a file or import a file. You open an audio file for a new BIAB project started based on that audio file. You import an audio file for the audio to add to your existing BIAB project.

BIAB displays the number of bars based on how the audio file gets into the BIAB project. If a project is opened with an audio file, the audio determines the number of bars. If audio is imported, the BIAB project has determined the number of bars.
Charlie,

I was just typing up something similar but your explanation is much better than what I had.

For what it's worth, my understanding of BIAB and RB is that anytime "import" is mentioned, it means "add to the currently opened project". For this reason, the existing project controls the outcome. On the other hand, whenever "open" is used, it means "create a new project based on what I'm loading in" thus whatever is opened controls the outcome.

--Noel

MY SONGS...
Audiophile BIAB 2025