Chase Composer Errs/Crashes

Chase Data issues and crashes

JerkyTreats

Continued chasing down crashes and bad data.

I will have to reflect on building this complex data object out of whole cloth. It may have been more efficient to build the data piecemeal, adding iterative layers on top of each other.

Not sure how feasible that is though.

Either way, the data seems mostly correct now, just smoothing out the details to have it actually working.

And by working, I mean straight garbage:

• PedalPoint is the only strategy at this point
• All instruments are choosing PedalPoint with appropriateness of 0.0
• The Scale I’m generating defaults to C if no value is given. Meaning I get scales like A, C, C, C, C ...
• The GenerateBars loop appears to be taking longer than the bars themselves. Meaning I am generating data for bar 4 when we’re already on bar 5.
• The code is messy, whole comment blocks of code sitting around, hacks-n-workarounds
• One thing about the “be OK about messy code during feature dev” is you need to record the issues you’re being OK with during feature dev.

But, once the Pedal Point strategy is technically working, it should be fairly straightforward to fix the things above.

Then we can revisit the more endemic issues of the current data structure, where we will consider flattening and/or decoupling some of these data objects.

But alas, step one will be make the noise go.