I did have a writeup on how it'd be great for debug and social media to have a save as video feature - then I found it. Doing so, however, discovered a few problems

1) The "focus" issue I was trying to demonstrate with a video does not happen with the video render since the rendered video shows 9 lines of chords (measures 1-36) while my screen shows 10 lines of chords (measures 1-38, measures 39-40 are past the end of the song).

Therefore, the saveas video is not a strict rendering of what is displayed on the screen. There may be something to this, however - since the screen focus seems to flip to the next page when the saveas video renderer flips (correctly) its page to display measures 37-38 (10th line) which in the rendered version is not displayed until the page flip happens. On my system screen (application version) I see the entire tune and therefore there should be no page flipping.

2) The audio of the avi is distorted. I'm using the default codec "CVSM: MS-CRAM". Have not used this feature before, so settings are as install default.

3) The dialog for the avi render menu/progress ("Make Video of the Chordsheet" is placed in the background. The "alt-tab" graphic in windows shows the dialog box - but when switching back to BIAB - the main application window is displayed. In order to "uncover" the dialog box, I have to press "alt-esc" until it comes up. The issue is that this dialog box is not modal and has a parent so it doesn't end up having its own taskbar icon. When it hides behind the main app window - it's "difficult" to uncover as I also do not see a button or other way to bring it back to the foreground.

Note that by starting the rendering process, the program changes focus back to the main application thereby placing the "Make Video Of the Cordsheet" window hide in the background. This loses the progress bar during the rendering. At the moment, I'm having issues recovering from this state ("finding" the dialog) without exiting out of bbw, restarting, and bringing up the feature (saveas ... save as video) after restart.

Sometimes it is not forced to the background for the video rendering portion. Perhaps while the window is in the background while the realtracks are regenerated, I clicked on the main window which prevented the focus from being restored. At any rate, there are pitfalls with the current implementation.

... for the original "focus" issue - I'm going to have to bring up a 3rd party screen recorder to demo the issue.

-- here's a link (focus issue): http://vimple.co/a1d12632e9414716879a2bb4334088a9

1/1/2024 - Win 10 BIAB 2019 64bit Build (644), RealBand 2019 (4)
Prior - Sig can't fit a running list - so just showing current version