# T1 Summary and User Testing

## Summary
* Overall, a successful first term. It took a while to have everyone get started with Unity, Maya, Unity-Git. But with nearly all the modeling done, we are hopeful that we can build on the current product next term.
* Some of the interactions with the virtual environment were unintuitive and difficult to understand (i.e. touching objects). To fix this, we thought it might be useful to:
* Add an introductory tutorial scene to help with this
* Have consistent UI throughout the program. For example, we could implement "pinching" for all of UI instead of "touching"
* Character models could be changed
* More friendly looking
* More diversity

#### Observations
* Found that nearly everyone struggled with interacting with the VR environment without a tutorial
* It seemed that throughout the usage of the application, people were confused what the progression of steps was. It could be useful to include helpful-hints that direct the user towards the next steps.

#### Analysis
* Is there any analysis you can do of the testing - what percentage of users claimed X or Y. If you had numerical answers was there any statistical significance to the answers?*
* Almost all users (>85%) have commented that the UI and the music itself could be improved.

#### Notes To Future Us
* Improve the integration of music into the project. The current version plays music too quietly.
* Have multiple sources playing from the same position (Multiple String #1 playing from the same spot)
* Include tutorial for UI interaction and/or make it more intuitive
* Figure out a better solution to sharing the Unity project/repo.
* Right off the bat, have a working implementation of the real-time score following functionality. If it doesn't seem to work, pivot to a product with a slightly altered functionality.
* Finish up modeling, especially instrument modeling as well as instrument playing animation
* Some minor FPS issues at random spurts. Should make sure that animations don't slow down the frames, especially in the future when we plan on enlargening the audience
## TeamWork
* The team was great at communicating via Slack about meetings, issues, etc
* We kept our ZenHub updated constantly
* Good idea to split the team up into a Unity team and a Score Following team. It might be cool to swap teams for next term.

#### What has been working well?
* Excellent communication between team members
* ZenHub was very useful for identifying and narrowing down tasks.
* Whenever merge conflicts arose, our team met up in person. This was helpful for ensuring that we were all on the same page before merging/pulling again.
* Kept a consistent meeting schedule. We would also tend to have meetings if there were any significant bugs or merge conflicts

#### What has not?
* It was difficult coordinating our GitHub for the Unity project. Constantly ran into merge conflicts and other issues that were difficult to solve.
* With the score following, we had some issues sticking with one particular method/strategy. Of course, this might be just a side effect of a more research-based component, but it seemed like we wasted a lot of time experimenting with different score following methods every other week or so. Thankfully, it seems like we've found the paper/method that we would like to use. We will continue doing research/experimentation over spring break.

#### Steps
* One solution is to use GitHub for Unity. Another is to use the Unity integrated project sharing that is built into the Unity application itself.
* We should work out a plan to finish up an implementation of the score-following algorithm building off what has been done within the first few weeks of the term.
* We need to think of other functionalities in the mean time that could help pivot the project in the event that we cannot implement score-following in a timely manner.
* Developing small functions that enhance the experience (lights and colors that react to real-time audio input, etc.) could be good initial sprints.