main app pipeline feedback from users

[wassfila]

provided by @MKDYasserH , I copied it from the slack channel

Here is a summary of the issues :

• No Sound was played back to us
• The User Interface was not intuitive and often did not respond. We were often not sure what the system is doing, or whether it crashed. This also impacted our ability to tracking bugs. Also, we were not sure how to use the GUI and what it was supposed to do in a given state. A documentation/demo would help.
• Sometimes the GUI would freeze. It would be good to know whether an expensive calculation is still running, such as the computation of wav files for pitches 46-88.
• We propose there should be a help button/question mark with which one could point on a GUI item, and a description should appear. The GUI works fine, but the Ux (User experience) insufficient.

User-Experience-And-Error-Reports_Beat_Tödtli.docx
error_reporting_logs_archit.zip
logs_beat_toedtli.zip

[Leofltt]

Ticking last one (We propose there should be a help button/question mark [..].) as 'Won't do'. The button are doing exactly what is written, there is the need to know what a button does in a specific context, but that will be addressed with manual / video demo. There is no amount of description overlay that would actually be useful and not just cumbersome and we definitely don't have the capacity to dev a whole new feature like that and test it in a way that makes sense in time for eval. Maybe we can think about it later on. -> See rg prod issue 28

[wassfila]

right, prio is for crashes and dysfunctions, or user frustrations on not being able to run the main app.

[Leofltt]

Third issue (Sometimes the GUI would freeze. It would be good to know whether an expensive calculation is still running, such as the computation of wav files for pitches 46-88.) addressed by the latest merge to dev branch #36

[Leofltt]

Manual is in #40