Bugs/Mark

Notes in italics

In order of priority (subject to change):

Most time consuming since it has to be done repeatedly on every single track:

• Fix "save MSI default"!!!!

• After you read the metadata in, either when you import the track, or get it from sunfly.csv, or edit by hand, when you first open in Producer, it rereads all the metatdata from the fly file again, obliterating all your changes, and baking them into the track. So you have to then close Producer, go back to the track in the playlist, re-edit or re-paste from the CSV, run Producer again, and then rebake. It gets REALLY old after awhile! It would be nice if you could push metadata, have it saved, and have Producer actually aware that it has been, so it stops re-reading it from the fly file!

• As discussed before, being able to set a maximum percentage to reduce the size of the final blogs on each page to accommodate the post and pre gaps, first shrinking the final blob until it reached 100 - max percentage, and then shrinking the next one, etc., until the post and pre gaps fit, would finalize this procedure. Currently, Producer just shrinks the last blob on the "pre" page to nothing, and only then goes on to shrink the next to last blob, with the result being that the final word just flies by. this has a very disconcerting psychological effect that hampers finding your place on the next page. Second most time consuming, because every track must be checked, it is hard to d by visual inspection, and since when a track needs one edit, it often needs MANY, and involves lots of zooming in and zooming out, and blob dragging, which is not particularly efficient in the current interface:

• Sometimes words that are supposed to be separated are not. They are placed right next to each other. E.g., "Willyou" instead of "Will you", even though they are separate words oin the actualy .fly file. Because of this, although it is not particularly common, I still have to go through every track, page by page, checking to see if this has occurred. This can be time-consuming and a bit frustrating. When one is found, there are usually repeats, and editing them all can take significant amounts of time. Of almost equal priority, since it has to be checked in every file, and if not corrected, forces a redo (unlike the previous one, which can sneak by the quality control staff!):

• In a related issue, if it were possible, it would be nice if, if the final blob on a given line was punctuation, that it actually be placed directly adjacent to the previous word, rather than separated by white space. E.g., "you …." would be "you…." This is important stylistically, not only because of aesthetics, but because of consistency, as some times, for instance an ellipsis will appear as part of the blob, and other times as a separate one, in the same phrase in the same sentence in the same song.

(The flip side of this is when words that should be continuous are syllable-separated (e.g. punc tu a tion). I assume there is nothing short of an AI Turing Machine that can fix this.) :)

• In the YSTHs tracks, Words with hyphens get incorrectly sized. The hyphen is too long but more interestingly, the bounding box is made too big vertically. This is probably a font issue (Univers 67 condensed bold) but when I replace the hyphen in the blob with the keyboard hyphen, I get the correctly sized character. I thought the preference we added, "producer: interpret hyphens as syllable markers" was supposed to ignore syllable markers, and thus allow the standard keyboard hyphen-minus char to survive the encoding process? If not, it really should!

• Also in the YSTHs tracks, I still can not create a YSTHs-specific break screen (like "Instrumental/n 10 seconds) that does not crash kJams like a stone.

• Switching venues multiple times, as I have to do in my copy singers script, often crashed kJams. It is also SLOWWWWW, but I suspect fixing that will require a re-architecting. Thought this was fixed, but it is not.

• Heads up: There is still an issue of random crashes, I think server-related, but not sure. more data coming if I can catch it with Activity monitor and get code samples.