Team Status Report for 3/23/24

  • The most significant risks that could jeopardize our project are the lights and knowing when to remove a song from the queue after it has been played. As described a little bit in Matt’s status update, the lights were working for a little until they were not. We think it has something to do with our cord connection between the computer and the lights. We may need an extra device to connect the two. This risk is being managed by us devoting a lot of attention to the lights this week and communicating with a team that has used the lights in the past. No contingency plan yet since we think we can figure it out and have not struggled for long. As for the timing of removing a song, our backend code does not know how long the song is at the time of queuing, we would have to query the Spotify api. But that is tricky since the Spotify api takes time and we want to be as accurate as possible. We are managing this risk by starting to think about the options available to us. We could get the song length back from the Spotify api and only play it for a certain time (less than the total song length) decided by the backend then tell the api to play the next song and increment the queue. That will make sure the timing is all in one place. We will be thinking of better solutions this week.
  • No changes
  • Photos/videos are in individual status reports

Leave a Reply

Your email address will not be published. Required fields are marked *