Group 10: “Team X”
Osman Khwaja (okhwaja)
Junjun Chen (junjunc)
Igor Zabukovec (iz)
(av)
Group Members:
We all observed dance rehearsals together, and afterwards met and discussed what features we’d want our project to have. Alejandro did some more in depth interviews of dancers, Junjun and Osman took care of the storyboarding part, Igor sketched out a user interface.
Problem and Solution Overview
We are addressing the problem of a dancer having to go back and forth to whatever device they are using to play music while practicing or choreographing, which results in inefficiency. Our system will recognized user-defined gestures to start or stop the music, to loop a section of the music, and to speed it up or down, so that they can control these parameters remotely, while retaining complete control over their movement.
Users Observed in Contextual Inquiry
Our target user group is dancers who practice or choreograph using previously recorded music. Obviously, if dancers do not use recorded music, then they do not need to control it. Furthermore, we did not feel the need to limit our system to specific styles of dance, because it can apply to all dance where recorded music is used. We conducted contextual inquiry on three different dancers. Dancers 1 and 2 are seniors in the Comparative Literature department and both are pursuing Certificates in Dance. They both do contemporary styles of dance and Dancer 2 also works as a choreographer. Dancer 1 is interested in the relationship between dance, theatre and music. Dancer 3 is a graduate student in political economy who danced professionally for several years before going to college, primarily hip hop and some contemporary, and continues to dance for her own enjoyment. All three seem very interested in improvised dance and contemporary choreography, and as described they have different levels of commitment to dance.
Interview Descriptions
We observed Dancer 2 in rehearsals in New South Dance Studios for a thesis production, Dancer 3 practicing and improvising to music by herself, and Dancer 1 practicing for a dance sequence in a play. We watched these rehearsals taking place, asked the dancers how they felt that their movements connected to the music that they were using, watched how often they felt the need to change how the music was playing, and watched how they undertook that task. We interviewed them about their general practice routine, with a variety of questions that aimed to have them propose ways in which they thought it could be improved. We then described our design idea to them and asked them more specifically what they thought of it and how they thought it might fit into their practice and choreographing routines.
A lot of what we observed and were told by the dancers was fairly unexpected. Although it was clear that starting/stopping music was necessary, overall it seemed that they used those moments to rest or think more carefully about their moves, or to discuss what they were doing with someone else if they were not dancing alone. Furthermore, when asking them they said they felt that this was only somewhat annoying, and that it was a natural and important part of their practice routine. It seemed obvious to us that, although the system might improve efficiency, this wasn’t something crucial for dancers and therefore would not necessarily interesting them enough in order to have them adopt a new system.
When we explicitly discussed the system with them, all three of the dancers agreed that it would be a useful and interesting system to use. However, they seemed to be interested in using it in different ways. Dancer 1 thought that it would be most interesting as an actual performance tool, something with which a dancer would interact with in a live setting, rather than a practice setting. Dancer 2 thought it would a good tool for practicing but did not think it would be interesting for choreographing, as she prefers to choreograph without music, and then see how the music will fit with the dance (this is the same that we observed when watching her rehearsal: it was clear that the music was added afterward, and it didn’t seem like our system would be particularly applicable in that case). Like Dancer 1, she thought it would be most interesting when applied to a live setting, which would allow for dancers to interact with a computer playing recorded sound in a similar way that they could interact with live musicians. Dancer 3 suggested that it would be good both as a both a practice and choreographing tool, and thought that it could even be extended to be used to edit music on the fly when trying to develop both the dance and musical aspects of a performance.
In conclusion, these observations led us to see our project’s development in the following way: we will start from a practical perspective, where a dancer can use the system to practice, and the system will accomplish the very specific tasks that we will describe later. However, we hope that this will be the basis of what can then become an interactive system which can be introduced into improvised dance performances, allowing dancers to interact with the music on the fly, something that they seemed to think would be even more valuable than the improvement of the practice routine that we have in mind as a starting point.
Task Analysis Questions
- Who is going to use system?
Dancers and people who are trying to teach dancers who are trying to practice or choreograph their dance to a recorded song. - What tasks do they now perform?
Currently, dancers use some sort of jukebox/stereo/computer to play their recording. They start the song from the beginning or some relevant point and then get into position. The music plays at its normal pace and they dance. When they mess up, they have to head over to the computer and start it again. This process repeats - What tasks are desired?
Dancers want to be able to play a relevant part of music that they’re trying to learn and practice until they mess up. If they do, they want an easy way to go back and restart the music from that point. Additionally, if the music or moves are too fast to learn at the normal pace, they could use some way to slow down the music. - How are the tasks learned?
The process of creating a methodology of learning how to dance basically comes down to one’s personal experience trying to learn dances. There isn’t a formalized approach that all dancers adhere to. - Where are the tasks performed?
Normally performed in a dance studio - What’s the relationship between user & data?
There isn’t necessarily user data created by the process of learning to dance. Optionally, one can create a video of the dance and watch it, but that’s not always necessary because dance studios usually have mirrors - What other tools does the user have?
Normally the user has a stereo, iPod, computer, or something that can play music and allows them to start and restart it - How do users communicate with each other?
There isn’t a relevant user to user interaction that needs to be addressed - How often are the tasks performed?
Normally, Dancers practice dances with a show upcoming. Often, they also just do it for fun. Dancers practice as often as necessary to learn the dance. - What are the time constraints on the tasks?
Dancers normally have a limited amount of time to learn a dance (before a show or something) so they want to have the most efficient practice. - What happens when things go wrong? (Pretty sure this question is not relevant)
It is rarely the case that there is some sort of problem with the music playing that causes the dance practice to come to a halt. I guess if something happens, then they have to reboot, find a new way to play music, or just reschedule the dance practice. I don’t think this question is very relevant to our specific inquiry
Description of three tasks
- (Easy) The user would be able to stop and start the music. Currently, the user would have to either: have someone else control the music, walk over to a computer or other sound system and push start/stop (with a delay to get into back into position), or control the music with a remote (which they would have to carry with them, hindering their movements). With our system, there would be gesture and voice commands for pause and play. Ideally, the system would also know to pause the music when the user stops dancing, and start when the user starts. This would make this task incredibly easy with the proposed system, as user would not have to think about the task at all.
- (Medium) The user would be able to repeat sections of the music. When practicing anything, repetition is key, and dancers often have to repeat sections of a dance to learn it. Currently, to go back to a section, the user would need to press buttons to skip to the proper section, or if the music isn’t divided into sections, they may have to fast forward or backward to seek to the proper place in the song. It is difficult to stop the music, seek to the right place, and then start it. With our proposed system, the dancer would be able to set “breakpoints” in the music with gestures while running through it, and then go back to that point later. This would make the process much easier.
- (Hard) The speed of the music would change to follow the dancer. Currently, there is no way to do this on the spot. Either the speed has to be changed beforehand, with some software, or the dancer has to follow the music (perhaps stopping and rewinding a section many times until they can follow that tempo). With our system, the speed of the music would changed based on the dancer. This would give dancers who are just learning the choreography an easier, and perhaps less frustrating, way of practicing with music, and it would give a dancer who knows the choreography more freedom of expression. It would be very easy to do on our system, as it could happen automatically (the user would indicate beforehand whether they want this to happen).
Interface Design
TEXT DESCRIPTION
Our system would provide a way for dancers to interact with music without having to think about it. The system would provide defined gesture and voice commands for the user to use to stop, start, and repeat a section of music, but additionally, system would also try to automatically follow the dancer’s intentions without additional gestures (the music will stop when the dancer stops moving, etc). The system would also allow the user to set the pace of the music, by following the dancer’s steps. All the user would have to do is tell the system to enter this “follow” mode, and the rest would be automatic. This allows the user to basically focus on their practice without having to think about the technology. There are existing systems for interacting with music, including keys on a computer, remotes, and even voice commands, but what makes our idea different it would be more “intelligent” and responsive, making the routine more fluid and efficent. Some others systems similar to ours are those which use the connect to interact with music. One example is a system that translates a user’s moves into music (http://www.mendeley.com/catalog/creating-musical-expression-using-kinect/). Our system would be different in that it focuses on practicing: the user group and aim is different.
STORYBOARDS
TASK 1:
TASK 2:
TASK 3:
SKETCHES