This week we worked on possible designs for the user interface, while at the same time continuing to flesh out the concept. We came up with a lot of good ideas, and it's prooving difficult to chose which ones to go with. The UI design will depend a lot on certain design decisions; for example, wether we aim for more of a compositional tool or focus on real-time performance aspects. Because we have still not settled on just one idea, figuring out what the UI will look like is tough, so I decided to try a more technical approach. I created a quick list of task objects and task actions which fit to the general ideas that we seem to be leaning towards.
Task Objects:
1. Instrument
- Unit(s)
- ??
- Notes
- Units/Instruments
- ??
- Type/Weakness
- Spead?
- ??
Task Actions:
1. Compose
Objects:
- Instrument(s)
- Pattern(s)
Actions:
- Create patterns by selecting instruments and notes for them to play
Objects:
- Pattern(s)
- Monster(s)
- Select patterns to perform to appease/weaken monsters
- Create good sounding music
One of the things me and Dylan also looked into was a possible metric or algorithm for scoring "good" music. We came up with some possible ideas for scoring how well the user is able to follow certain criteria, but it is still difficult to score creativity which might break the rules but still sound good. This is something we will certainly have to keep in mind throughout this project.
No comments:
Post a Comment