3 ms·

Is this open source Mighty?

graderjs 5y ago
Hahaha. NO mate, but good marketing copy (thanks for the idea;)). I believe Mighty works mighty different. They have a focus on crystal clear ultra fast video streaming of the viewport (I'm not sure of their setup, but I've seen suhail tweet about GPUs and one tweet of an image of a "MPEG compression textbook"). I've considered experimenting with ffmpeg as well, but I'm satisfied with my current solution's usability and responsiveness, and low lag over a range of bandwidths, which I prioritize over high framerate, and for what I originally wanted it for a high frame rate didn't matter. People have often commented that the frame rate is too low, or they would like me to make them a "co-browsing / remote browser video streaming" system to stream videos or watch them together. I just think doing streaming really well at high volume is both incredibly expensive and very difficult. I do this alone and I'm coming to the end of my (very gratefully received) GCP "cloud for startups" free credits, so "I have no plans to announce at this time" about doing ffmpeg or not :)
- tentacleuno 5y ago
  Just going to point out the obvious and say a co-watch remote browser definitely wouldn't work with Netflix. I love the confusion on people's faces when they try to do it over Zoom ("Why is the video black?"). Yay Widevine?
  - graderjs 5y ago
    This is cool! Thanks for bringing that to my attention. I didn't know that and had never tried netflix until your comment just now. First I tried with Firefox, then with Chrome UAs, and tried importing a libwidevine.so. Nothing works, and Netflix says the error is a missing CDM component. I suppose that's better that it doesn't work. I don't think Netflix / Spotify would be cool with that. It's a little disappointing to not me able to test out Netflix on this, but less risky :P ;) xx
  - getcrunk 5y ago
    That's caused by hardware acceleration ... I have not tried it. But I'd say make sure you are on a desktop using desktop zoom app and then a web browser for Netflix and turn hardware acceleration off. I can't imagine how widevine could stop that. Zoom would have to be working with Netflix to make it happen
    - capableweb 5y ago
      > That's caused by hardware acceleration .. Eh, no, this is because of DRM. The DRM that browsers now offer (wtf) allows browser applications to black out themselves if they detect things like screen recording. Not sure exactly how the implementation works (as DRM is generally a black box, on purpose), but it definitely is on purpose and not really related to hardware acceleration. The API Zoom is using for screen sharing is probably the same API you'd use to record the screen, so when Netflix detects that, they chose to black out the content.

Hahaha. NO mate, but good marketing copy (thanks for the idea;)). I believe Mighty works mighty different. They have a focus on crystal clear ultra fast video streaming of the viewport (I'm not sure of their setup, but I've seen suhail tweet about GPUs and one tweet of an image of a "MPEG compression textbook"). I've considered experimenting with ffmpeg as well, but I'm satisfied with my current solution's usability and responsiveness, and low lag over a range of bandwidths, which I prioritize over high framerate, and for what I originally wanted it for a high frame rate didn't matter. People have often commented that the frame rate is too low, or they would like me to make them a "co-browsing / remote browser video streaming" system to stream videos or watch them together. I just think doing streaming really well at high volume is both incredibly expensive and very difficult. I do this alone and I'm coming to the end of my (very gratefully received) GCP "cloud for startups" free credits, so "I have no plans to announce at this time" about doing ffmpeg or not :)

tentacleuno 5y ago
Just going to point out the obvious and say a co-watch remote browser definitely wouldn't work with Netflix. I love the confusion on people's faces when they try to do it over Zoom ("Why is the video black?"). Yay Widevine?
- graderjs 5y ago
  This is cool! Thanks for bringing that to my attention. I didn't know that and had never tried netflix until your comment just now. First I tried with Firefox, then with Chrome UAs, and tried importing a libwidevine.so. Nothing works, and Netflix says the error is a missing CDM component. I suppose that's better that it doesn't work. I don't think Netflix / Spotify would be cool with that. It's a little disappointing to not me able to test out Netflix on this, but less risky :P ;) xx
- getcrunk 5y ago
  That's caused by hardware acceleration ... I have not tried it. But I'd say make sure you are on a desktop using desktop zoom app and then a web browser for Netflix and turn hardware acceleration off. I can't imagine how widevine could stop that. Zoom would have to be working with Netflix to make it happen
  - capableweb 5y ago
    > That's caused by hardware acceleration .. Eh, no, this is because of DRM. The DRM that browsers now offer (wtf) allows browser applications to black out themselves if they detect things like screen recording. Not sure exactly how the implementation works (as DRM is generally a black box, on purpose), but it definitely is on purpose and not really related to hardware acceleration. The API Zoom is using for screen sharing is probably the same API you'd use to record the screen, so when Netflix detects that, they chose to black out the content.