From: Yue <yu...@ru...> - 2016-11-14 04:06:46
|
Hello everyone, I recall I once wrote one paper about the issues as part of my team's portfolio (2015 - 2016 team Charlotte, Gaoxin & Yue). However, I could not carry it on because of my current workload. If I'm not mistaken: In Python script, all avatars ( and images) are saved and parsed into an array (in a sequential order). Replication of the case: Audiences and actors enter the same stage while more media (images etc) are being uploaded/assigned to the stage. This also explains why people re-entering the stage resolves the issue. An instant remedy is to force the stage reload on the creator's panel (a button forces stage reload for all). Or only make stage accessible once all media are uploaded onto the stage. Hope this helps. If anyone has the updated information, please let the rest of us know. Cheers Yue On 11/14/2016 07:25 AM, helen varley jamieson wrote: > > hi devs, > > we have just tried to do a stress-test for streaming on our new > server, however we ran into multiple issues which meant that instead > of really stress-testing, we ended up trying to trouble-shoot & > replicate what i'm calling the "complete chaos" bug. > > it's actually a combination of multiple known issues, but because it > happened at the same time for all 3 of us (me, mem & annie), it seems > like it was something getting confused at the server rather than an > individual network or browser problem. so i created a new issue for it > on github: https://github.com/upstage-org/upstage/issues/296 > > it is related to many issues that some of you have worked on, > including the avatar swap (where more than one person is holding the > same avatar &/or wrong names appear in the chat &/or one avatar > showing up in one browser and a different one in another browser), not > seeing avatars when you enter a stage, & webcams in different positions. > > this time we solved it by all leaving the stage and then re-entering. > we put our webcams back on stage & spent some time trying to trigger > the complete chaos again, however we could not. so i know - without > being able to replicate it, it's difficult for anyone to try & solve it. > > i'm sending this to the dev list since maybe some of the ex-students > who have worked on some of these bugs can remember something, & have > time to have a look. we have a performance in a week & a half (on 24th > november) & i am starting the workshop for the performance on > thursday, so i know it's unlikely anything can be "fixed" before then, > but if anyone out there has any ideas about it, please say!! > > h : / > -- > helen varley jamieson > he...@cr... <mailto:he...@cr...> > http://www.creative-catalyst.com > http://www.upstage.org.nz > > *We have a situation, Coventry! <http://www.wehaveasituation.net/?p=1402>* > 24 November 2016 > > > > ------------------------------------------------------------------------------ > Developer Access Program for Intel Xeon Phi Processors > Access to Intel Xeon Phi processor-based developer platforms. > With one year of Intel Parallel Studio XE. > Training and support from Colfax. > Order your platform today. http://sdm.link/xeonphi > > > _______________________________________________ > Upstage-list mailing list > Ups...@li... > https://lists.sourceforge.net/lists/listinfo/upstage-list |