If you record to soloist from a bar that isn’t the first (say: bar 16) and after that, you want to record from start of the song... it records from bar 16. Notwithstanding the fact that you clicked: record from start of song.

If you want to record from a specific bar, there is a dialogue in Soloist allowing you to record from a bar, not the start of the song. When you click it, you eventually get sent to the general dialogue for recording to soloist. Two choices that end up being one single option.

Version 2021 solved some issues, like with notation, but as I start to use it, bugs keep popping up everywhere.

If your software has hundreds of features, it’s a recipe for several bugs and hiccups. Testing this kind of soft before a new release can’t be thorough... as this version shows.

Everyone uses different features, has a different workflow or preferred way of using biab. My preferred workflow, using jukebox, exporting video, using bar settings for arrangements and recording to melody or soloist, just isn‘t well served by the new version, to say the least.

Ya, I get it. You do tend to go into some dark deep waters with your workflow.

2019 new features....

Don’t go touching that. They could be encrypted messages from the past, coming to haunt you in the present.

This freaks me out.

I see you never touch the play button. Try it one day.

Dan are you sure you're using build 822? Mine shows 2021 New Features.

Absolutely I have been using 2021 for almost two months. When I click on the 2019 New Features, it opens up the 2021 New Features web page.

We fixed the 2019 new feature icon over in the beta forum. I had to RTFS and the 2021 icon appeared like magic! I guess I should be happy, but this kind of fix is used way too often to make up for obsolete code that is sitting in the programing.

I didn't mean to steal the OPs thread with this issue. Dzjang dare I suggest you try to RTFS to see what happens?

RTFS is my number 1 go to solution.

Sadly, it not only can’t magically repair bugs, but it has you run through layers and layers of settings to have your preferred midi, audio and display settings back.

Let’s say it needs a reset with every new update. I could live with that. And I put up with this “solution” for the sake of everything that’s great with Biab.

What happens is, imho: you change some midi settings, and all of a sudden your exported video has a two measure lag. Or something along those lines. You perform the sacred RTFS ritual, the video is ok, but your midi settings are not to your liking, so you tweak them. And, what do you think? The video has issues again.

Edit: I got tempted and did a full reset to factory...again. And video still lagged and other issues remained. Must....do....RTFS...

I do a return to factory settings (RTFS) after every update. It ensures the program always has a consistent starting point. I perform this step and restore my settings in less than a minute.

PG Music has made performing a return to factory settings a fairly painless task by including the "Open Preferences File" and "Save Preferences File" commands. The key points are to use the "Save Preferences File" command to create your preference file (1) once you have preferences set the way you want them (2) and the program is properly operating to your satisfaction.

Most people don't bother to make a preference file until the program is acting up. By then it's likely too late. There is a good chance the preference file you just saved has the corruption you're seeking to eliminate.

Return to Factory Settings, Open Preferences File and Save Preferences File are accessible under the "Options" tab in the menu bar.

Thx, Jim

If I get what you’re saying,
The trick is to restore your preferred settings by way of loading a preference file that used to work well in the past if RTFS doesn’t resolve your problem.

Good idea, certainly.

The trick is to save your preference file while Band-in-a-Box is properly working. That way you have some assurance the preference file is not corrupt.

Great minds think alike so I'm sure you and I are saying the same thing; we are just saying it different from each other.

Test driving build 823 doesn’t resolve this issue.

Record to soloist, starting from -say- bar 16. Ok, keep take.
Then you record to soloist, but specify from start of song. That doesn’t work. It starts on bar 16. Well, with a two bar lead in, starting on bar 14. As specified, so that’s not an issue.

But, it still ignores recording from the start of the song.