Search results

  1. N

    Re-stream RTP desktop capture to browser for 20-30 users

    Thanks - that has helped to control the bandwidth
  2. N

    Re-stream RTP desktop capture to browser for 20-30 users

    I'm very grateful for your continued support on this. Adding the keyframes option as you suggested had the immediate benefit of much faster start for playback. However, it has increased the bandwidth required by a factor of 10! I can see the outgoing stream for ffmpeg which settles around...
  3. N

    Re-stream RTP desktop capture to browser for 20-30 users

    Seems I was too quick to say that worked - it sort of works. But after 10s the live stream in the player freezes. sometimes making a big change like moving a window on the client unfreezes it. But mostly not, it just is stuck. The sending stream is fine. So still not reliable enough to be...
  4. N

    Re-stream RTP desktop capture to browser for 20-30 users

    Ah finally! This was the key: disable_streaming_proxy=true Now I have something working - thanks for the support. One last question - in my intended use, the client running ffmpeg will initiate the stream. Where should I start looking to understand how to set the web player to automatically...
  5. N

    Re-stream RTP desktop capture to browser for 20-30 users

    Thanks for the detailed analysis. I've tried the first set of config changes - which as far as I can see require changing two properties files - flashphoner.properties and server.properties (is that right?). Then restarted the server. This has not helped, still spinning wheel. I didn't...
  6. N

    Re-stream RTP desktop capture to browser for 20-30 users

    I've tried reducing the client streaming massively - now 562x350 (too small to be useful) and also stepped up te EC2 server instance size to t2.large - now the server.log in Web Call Server no longer reports bandwidth issue, but the Javascript console reports bandwidth issue and still the wheel...
  7. N

    Re-stream RTP desktop capture to browser for 20-30 users

    Had a chance to try this now - still no luck with the above change to the player - still spinning wheel in the player with 'PLAYING' shown beside the Start button. In the server log I see 'not enough bandwidth' being reported: OBJECT: { "nodeId" ...
  8. N

    Flashphoner and WCS problems

    Turns out for the EC2 instances I was doing two things wrong: The user for logging in to the linux console for the WCS AMI on EC2 is 'ec-user' - I had that wrong The URL for accessing the admin MUST have the trailing slash <ip>:8888/ Still not sure why https://flashphoner.com/ can't be...
  9. N

    Flashphoner and WCS problems

    On Friday and today I was unable to get new instances of Web Call Server running on EC2 - using the marketplace AMI I'd used before, I tried creating new EC2 instances of Web Call Server. Everytime, I was unable to connect to the server once it had started on port 8888. I was also unable to...
  10. N

    Re-stream RTP desktop capture to browser for 20-30 users

    Thanks! So now I have my own trial server working on EC2 and I'm able to stream a sample mp4 from my PC to the admin demo panel. A big step forward. However when I try to replace the source movie with capture from desktop, the stream player connects but just spins. The ffmpeg line I use is...
  11. N

    Re-stream RTP desktop capture to browser for 20-30 users

    Thank you for the reply. My question was more specific - I already have the desktop capture working, it can not use the browser - it is a command line invocation of ffmpeg that generates an RTP stream of h264 encoded packets which I send to a fixed port on the server. The server would need to...
  12. N

    Re-stream RTP desktop capture to browser for 20-30 users

    Hi I have a need to capture and broadcast desktop with low latency to 20-30 users. The end users need to be able to just use HTML5 video tag to view the desktop. Currently I've managed to get a low latency, high quality desktop capture to server using FFMPEG to generate and send h264 encoded...
Top