SceneCity - privacy-focussed live streaming and chat for the demoscene
category: general [glöplog]
I'd call it analytical. Again, I need proper bug reports to be able to fix bugs. And if those who have problems aren't communicating I can not improve things. Sorry if that sounds aggressive to you, it's not meant this way.
i second with stream troubles, tried several different servers/protocols/devices/browsers/ISPs (both mobile and wired), in the end only 1080p 10mbps + HLS gave me somewhat stable playback (with occasional buffering). 720p was totally unwatchable :(
On the 720p one I had to rework stuff multiple times. Originally on Friday the stream source was pushed via RTMP, but that caused a massive time drift on the edge servers (OBS was claiming to send 60fps but for whatever reasons sent 62.5 fps, wtf). So on Friday I switched to SRT streaming which rocks, but then the NVEnc transcoder for the 720p stream was unable to parse the MPEG TS frames so there hasnt been a 720p stream at all. In the end I switched to software transcoding for that, which according to feedback I got worked fine. Lots of lessons learned, but obviously I will have to wait until the next live event to make use of those.
That being said: If anyone here is able to reproduce issues with the demo loop stream that is running all the time, let me know.
That being said: If anyone here is able to reproduce issues with the demo loop stream that is running all the time, let me know.
Quote:
If anyone here is able to reproduce issues with the demo loop stream that is running all the time, let me know.
Right now, demo loop:
- WebRTC works, both 5/10 mpbs, with minor glitches (which could be easily on my side, as you said webrtc is sensitive tech).
- the interface is not always responsible though, sometimes have to reload the page to make the buttons work again
- HLS / Dash sometimes work but more often not: Often the circle just seems to circle forever, and the pause and play icons flash in rythm; or in case of Dash sometimes even just a black screen and again sometimes an error message.
- Sometimes, still after a very long time of buffering (?) it starts to work, but not always (or maybe I'm not patient enough, but we are talking about several minutes here)
- in general it seems to be really very fragile
I have rather shitty internet, with peak bandwith 17mbps, but I could watch the 10mbps stream during Revision without serious issues. Speedtest net says 24ms ping, 17mbps down, 2.35mbps up. Browser is Firefox. Switching to Chrome does not help either.
Back during Revision I was mainly using the HLS stream because WebRTC does not work on my older "streaming computer" (probably because the software is not up to date there).
Hope this helps.
It does. Sounds like an ISP peering issue.
If you could post me traceroutes to the servers where this is happening for you, that would help further. As posted earlier, the "give a selection of the five servers NEAREST to the users' IP" isn't optimal. It's very well possible that the routing between your ISP and the ones used by the servers has changed since Revision.
You can find the relays selected for you on the bottom right corner (gear icon). If it says "Nbg-8" the hostname is nbg1-edge8.scenecity.tv, "Hel-2" becomes hel1-edge2.scenecity.tv and so on.
I guess it would be preferable to post those traceroutes to #SceneCity on SceneCity instead of doing it in this thread.
If you could post me traceroutes to the servers where this is happening for you, that would help further. As posted earlier, the "give a selection of the five servers NEAREST to the users' IP" isn't optimal. It's very well possible that the routing between your ISP and the ones used by the servers has changed since Revision.
You can find the relays selected for you on the bottom right corner (gear icon). If it says "Nbg-8" the hostname is nbg1-edge8.scenecity.tv, "Hel-2" becomes hel1-edge2.scenecity.tv and so on.
I guess it would be preferable to post those traceroutes to #SceneCity on SceneCity instead of doing it in this thread.
Blala,
If it's of any help - next time you're watching a party livestream, maybe think about using MS Edge. Yep, it's now built on the Chromium engine - so the same engine as Chrome - but it's not as bloated as a browser (yet!) and seems to be a bit more stable with the streams as a result. Just a thought. Edge is available on multiple platforms and has been for some time, so you're not just stuck with Windows.
Once I'd managed to stop one or two games from downloading DLC in the background, the Outline 2022 stream largely worked pretty well via my Xbox One, also using the Edge browser. We did have some difficulties with the Chromecast but it has transpired that the ISP I use were doing some works in the area over the weekend, which explains this.
The web browser on PS4 was quite unstable when accessing SceneCity, but this is known to b0rk on this kind of thing. It was relatively stable when watching the CCC-hosted Revision stream though.
Many thanks once again to Scamp for providing the welcome Outline 2022 stream though; in general - given that this is still cutting edge, the provision was as good as could be expected.
If it's of any help - next time you're watching a party livestream, maybe think about using MS Edge. Yep, it's now built on the Chromium engine - so the same engine as Chrome - but it's not as bloated as a browser (yet!) and seems to be a bit more stable with the streams as a result. Just a thought. Edge is available on multiple platforms and has been for some time, so you're not just stuck with Windows.
Once I'd managed to stop one or two games from downloading DLC in the background, the Outline 2022 stream largely worked pretty well via my Xbox One, also using the Edge browser. We did have some difficulties with the Chromecast but it has transpired that the ISP I use were doing some works in the area over the weekend, which explains this.
The web browser on PS4 was quite unstable when accessing SceneCity, but this is known to b0rk on this kind of thing. It was relatively stable when watching the CCC-hosted Revision stream though.
Many thanks once again to Scamp for providing the welcome Outline 2022 stream though; in general - given that this is still cutting edge, the provision was as good as could be expected.
Nice stream !
on the bottom left of SceneCity there are two buttons
[Demoloop] [Outline 2022]
I can't press the Outline button as it's greyed out. Can I rewatch the Outline stream somehow?
on the bottom left of SceneCity there are two buttons
[Demoloop] [Outline 2022]
I can't press the Outline button as it's greyed out. Can I rewatch the Outline stream somehow?
Sadly the website seems to be not reachable to view the Evoke'2022 livestream.
Any alternative video streaming adress?
Any alternative video streaming adress?
Seems the stream switched from SceneCity over to twitch...
https://www.twitch.tv/evoke
https://www.twitch.tv/evoke
Yeah, I am most sorry for this. I had rolled out new code last weekend, and this weekend I am at a techno/art festival deep in a forest in poland and was unable to monitor things. And then yesterday the main relay server physically died and I had to try fix this remotely non-sober.
I really need more sys admins for the scenecity servers.
anyway, services should be fine now, and I'll ask another scener to also monitor things.
Once again: sorry.
I really need more sys admins for the scenecity servers.
anyway, services should be fine now, and I'll ask another scener to also monitor things.
Once again: sorry.
No problem scamp. Things like that can happen. Thanks for your fast remotely fix. Enjoy your techno/art festival in a forest in poland. Sounds great!
We are having a severe problem on the main server - fixing it will probably take all Sunday. During that, SceneCity sadly will be down.
Server problems are fixed.
So, during the last couple of months the team behind SceneCity has worked on building a second generation of our streaming system, which by using h.265 all the way from the demoparty itself is about enabling a quality of scene streaming not seen before.
As part of that mission, we have also built a hardware transcoder pipeline. Last night we've now finally installed it into the data center. Next we'll finish the software chain and start testing. Once that is completed, within the next weeks, SceneCity.TV 2.0 will go live.
Here is a video showing us powering up the finalized hardware for the first time:
https://youtu.be/1YmTKNaN07M
(While the video may make you believe otherwise, the new system is extremely energy-effeciant, reducing power usage compared to the existing standard-server based system by 80%.)
As part of that mission, we have also built a hardware transcoder pipeline. Last night we've now finally installed it into the data center. Next we'll finish the software chain and start testing. Once that is completed, within the next weeks, SceneCity.TV 2.0 will go live.
Here is a video showing us powering up the finalized hardware for the first time:
https://youtu.be/1YmTKNaN07M
(While the video may make you believe otherwise, the new system is extremely energy-effeciant, reducing power usage compared to the existing standard-server based system by 80%.)
There will be maintenance work this weekend. In the past, we were using multiple domains for the various services - scenecity.tv, scenecity.chat etc.
Due to us having multiple top level domains, the cookies needed for the SceneID authentication by the browser are seen as "third party cookie". Due to Chrome now getting a really strict on this (those cookies may be filtered even if correct HTTP headers are set) it's time for us to change our domain layout.
So from now on the actual domain used will be *.scenecity.net (tv.scenecity.net, chat.scenecity.net and so on). The top level domains will keep running but internally will redirect to the right scenecity.net subdomain.
Long story short: You don't need to change anything, but there will be a couple of minutes where you will be unable to login to the system.
Due to us having multiple top level domains, the cookies needed for the SceneID authentication by the browser are seen as "third party cookie". Due to Chrome now getting a really strict on this (those cookies may be filtered even if correct HTTP headers are set) it's time for us to change our domain layout.
So from now on the actual domain used will be *.scenecity.net (tv.scenecity.net, chat.scenecity.net and so on). The top level domains will keep running but internally will redirect to the right scenecity.net subdomain.
Long story short: You don't need to change anything, but there will be a couple of minutes where you will be unable to login to the system.
Thanks for keeping up the good work <3
tv.scenecity.net seems to be down for me; it just gives “404 Not Found”. I'd try from a different site, but wget doesn't trust the SSL certificate (some cross-signing cert not being served in the chain?).
Yeah, there had been TONS of problems introduced by my changes. Everything should be back to normal again when it comes to logging in.
scenecity.tv however right now is not yet showing the Demo stream channel again, that will be fixed tomorrow.
Sorry for the troubles.
scenecity.tv however right now is not yet showing the Demo stream channel again, that will be fixed tomorrow.
Sorry for the troubles.
In other words: If anyone is STILL having trouble logging in via Web, Desktop App, Mobile Apps or IRC, please let me know!
The certificate is still broken, at least. SSLLabs agrees. (I haven't tried logging in, since I don't have an account.)
You do have an account - it's sceneid. And as you are writing here on pouet, you are using a sceneid account. :)
Thanks for letting me know. I'm quite confused now - I can connect to https://tv.scenecity.net without any problem, however SSLLabs indeed is unable to connect to it. I'll investigate further...
Thanks for letting me know. I'm quite confused now - I can connect to https://tv.scenecity.net without any problem, however SSLLabs indeed is unable to connect to it. I'll investigate further...
Problem is fixed. Thanks!
Certificate chain works now, but I get a redirect to https://tv.scenecity.net/index.html and then that request just hangs.
Login via SceneID stopped working yesterday, "ERR_CONNECTION_TIMED_OUT".
Quote:
works againLogin via SceneID stopped working yesterday, "ERR_CONNECTION_TIMED_OUT".