RTMP side application allows restricting connections to clients from your domain only. So channels can be stolen for playback with other clients.
Plain php editions are for demonstrative purposes, easy integration and don't use a database. User/channel management depends on CMS integration. In example you can use editions like WordPress, Joomla, Oxwall, Elgg and control from there.
Video quality depends on allocated bandwidth per stream from settings (must be in the limits of the connection upload speed for broadcaster and download speed for watcher).
Higher video bandwidth setting will reduce required compression level and pixelation on movements but will require users to have higher connection or will cause massive frame loss, interruptions, big latency.
Latency depends on buffering settings (set 0.1 for flash minimum) and client-server connection latency that is independent of settings. Less buffering means less latency and is recommended for live chats. For 1 to many live streaming more buffering is recommended as fluency is more important.
Do a speed test of your home connection to your a location near your streaming server (rtmp) using
www.speedtest.net or another tool from
Then configure application streaming options (camBandwidth) to match your connection capabilities if you consider most users will have similar connections.
Also you can change camMaxBandwidth that will allow changing bandwidth allocation at runtime (by clicking webcam preview panel). With that you can apply different broadcasting settings at runtime while previewing playback on a different computer or browser tab.
Best low latency results, especially on high traffic sites, are obtained with latest versions that use p2p between the clients if rtmfp address is configured. Using P2P, latency is independent of server and only depends on client connections.
To enable P2P, get a RTMFP path (i.e. by registering for a free developer key from Adobe Cirrus ) and fill as rtmfp server.