... of course there are bugs, but I am wondering if the following specific "anomalies" are bugs.

1) When I highlight - or try to highlight a few chords for cut/paste - highlighting doesn't always seem to work. Case in point: I want to highlight one measure to cut/paste -- can't do it. Seems two measures are required. The workaround is to highlight two measures then scroll back to the first measure. Before I found that this worked, I had keyed in manually many measures (with multiple changes per measure).

It would be "better" if the highlight snap would allow for the resolution/granularity of chords per measure (which is 4 for charts in 4/4 time -- maybe different for other time signatures). Because there may be cases where I'd want to highlight chunks starting and ending at something other than beat 1 and beat 4 respectively. This would also allow for highlighting one measure without the extra step.

2) I looked up how to place "NC" (rests). There was a previous topic very long ago covering this. The way this has been implemented since makes some folks happy. Maybe I'm biased, but it seemed that use of "NC" as a chord symbol was favored as a suggestion to add. How one uses NC is up to them. A red chord symbol which denotes a rest looks wrong for my purposes. Just to check - I saw the printed lead sheet (print preview) doesn't handle these rests in what I would consider a correct way. There's no indication either with a rest symbol, "NC", etc. in the printed version of the leadsheet either.

I'm not too concerned about the lead sheet as I would generally use other software to generate that. However, in practice - I forego use of a lead sheet and read the transposed "what's on the screen" (chord sheet view). This is what is fueling the suggestion that the current implementation is perhaps a "bug" at least to my understanding of notation.

3) Audio Chord wizard is able to handle fractional tempos and is lined up better with source audio than BIAB. BIAB seems to round. Fractional tempos would be better for auditioning the algorithmic generated chords vs. the audio. Or maybe an added control for just a fractional push/pull. At any rate - the same resolution available in the wizard.

4) Where #3 has a limitation in BIAB in terms of lower resolution, this one is where the Audio Chord wizard has lower resolution than BIAB. The chord wizard has a maximum of two chords per measure. Presumably only beats 1-2 and 3-4 in 4/4 time. BIAB has a resolution of 4 chords per measure with further granularity of 8th or 16th note anticipation (negative) offset from each beat. The "whole farm" solution would be to support recognizing chord changes on the preceding 16th or 8th note and have the chord flow to BIAB as a "^^" or "^" if anticipated. However, beyond what it does now - it would be better to allow for up to BIAB's chords per measure (4) as an option to the Audio Chord Wizard. There are different ways to implement this including perhaps a way to tap a measure where you want to analyze all 4 beats which would be a hybrid approach - 2 chords per measure for most unless the user selects "high-res" mode on a given measure where there may be a beat-4 passing chord to throw at the wizard.

... also in the wish list category as the limitation is certainly by design.

5) I noticed soloist solos can, by random chance, repeat a phrase over and over and sometimes a few more overs again. This might be hip sometimes. But sometimes it picks the "hokey" phrase to repeat -- which isn't as hip. I'm wondering if there's a setting for limiting the regurgitation of material within the context of a soloist. Not a huge concern or bug - and I can always re-render (regenerate) until I find something that is only sparingly hokey.

6) Back to "bugs" - I noticed the leadsheet view doesn't always follow the music while playing. Sometimes the red highlight of which measure is playing is off or stuck. When there are soloist with notes I'm following to analyze what was chosen by the artist over different chords is generally how I've encountered this problem. Just loading the RealBand demos with soloist and looking at the lead sheet. Or maybe it's the "notation view" or maybe both. There are situations when the wrong section of music altogether is displayed.

Regression testing can be done by loading up demos with solos and looking at the notation and leadsheet views and ensuring the bouncing ball (red highlight) and music "focus" (portion of the score displayed in the visible screen area) is always correct. The laptop has limited screen size and resolution - so the testing should also include single pages that cannot fit in the window.

7) With limited resolution - the radio control for "Audio" is behind the Mixer/Plugins/Piano/Patches tab section. There are lots of spaces between the "Master", "Bass", "ElecPiano", "Drums", "Guitar", "Strings", "Melody", "Soloist", "Thru" -- and I guess "Audio" is next but is completely obscured. Squishing these closer together without spaces would help them fit. I'm not sure if it matters that the radio buttons would move around according to the instrument name length. They are not really spatially organized relative to anything else.

8) There were some less intuitive parts of the melody maker with workarounds - I may have handled these in an email. I had an entire set of "first impression" notes with questions and observations that was lost "in the fire" of a random blue-screen. I'll have to regenerate some of that later.

9) Part of the "lost in the fire" notes were some missing styles for some of the demos included with BIAB. Mostly realtracks for the jazz waltzes although there were two sets of different missing realtracks. I'll have to regenerate.

... incidentally: a "blue screen" comes after losing your work in a virtual fire and the fire is put out by dousing with water - which is, of course, blue.

Jason