SEGA Junkie
Given we've now decided that we're doing a remote marathon, we need to look at exactly how we can make it happen with as few glitches as possible. We're going to have a set of challenges that we haven't yet faced with in-person marathons, such as:
Streaming method - I think this one is mostly resolved, it sounds like we're going to have one Ustream account that the runners will sub into and out of as required per the schedule. It does sound like we're not going to be able to implement all the changes to the stream that we wanted to make for the next marathon due to time constraints, however - and the fact that every individual streamer would have to have those changes applied at their end.
Races - Given the way we're planning to do the stream, is this even technically feasible? How much do we trust co-hosting to give us good results after the fiasco that was races at the last marathon?
Donation tracking - Given two obvious facts: a) we don't have a centralised machine specifically for this purpose, and b) no one person is going to be awake for the entire marathon, the database of donors is going to have to be able to be passed around between multiple different people. People with actual experience with SMK's donation tracker will need to provide input here as to how easy passing around information using that would be. Also, the Chipin page will need to be shared around amongst multiple people, but that's much easier to co-ordinate.
Commentary - This is going to be a big issue. With the amount of people who want to commentate, there's going to be significant amounts of talking over people unless we are really careful with how we structure commentary. I'm not honestly sure how we go about solving this, we can have a hard limit on the amount of people in the Skype call at any one time but that seems counter-productive to actually producing a good marathon atmosphere. So there needs to be some guidelines for how the commentators commentate, with respect to each other.
Setup time - We've got a couple of weeks to work this out, but switching between players all the time is going to cause significant downtime periods. This obviously can't completely be eradicated, but it can be minimised by issuing a strong directive that players have their setup ready a good ten minutes before their game starts.
I'm sure I had more to say but I can't remember it all now. If you have any solutions to these issues, or further issues to present, speak up! As romscout said, best to get everything on the table as soon as possible!
Streaming method - I think this one is mostly resolved, it sounds like we're going to have one Ustream account that the runners will sub into and out of as required per the schedule. It does sound like we're not going to be able to implement all the changes to the stream that we wanted to make for the next marathon due to time constraints, however - and the fact that every individual streamer would have to have those changes applied at their end.
Races - Given the way we're planning to do the stream, is this even technically feasible? How much do we trust co-hosting to give us good results after the fiasco that was races at the last marathon?
Donation tracking - Given two obvious facts: a) we don't have a centralised machine specifically for this purpose, and b) no one person is going to be awake for the entire marathon, the database of donors is going to have to be able to be passed around between multiple different people. People with actual experience with SMK's donation tracker will need to provide input here as to how easy passing around information using that would be. Also, the Chipin page will need to be shared around amongst multiple people, but that's much easier to co-ordinate.
Commentary - This is going to be a big issue. With the amount of people who want to commentate, there's going to be significant amounts of talking over people unless we are really careful with how we structure commentary. I'm not honestly sure how we go about solving this, we can have a hard limit on the amount of people in the Skype call at any one time but that seems counter-productive to actually producing a good marathon atmosphere. So there needs to be some guidelines for how the commentators commentate, with respect to each other.
Setup time - We've got a couple of weeks to work this out, but switching between players all the time is going to cause significant downtime periods. This obviously can't completely be eradicated, but it can be minimised by issuing a strong directive that players have their setup ready a good ten minutes before their game starts.
I'm sure I had more to say but I can't remember it all now. If you have any solutions to these issues, or further issues to present, speak up! As romscout said, best to get everything on the table as soon as possible!
Thread title: