UDPSyphon makes you input IP address and network port manually, while TCPSyphon gives you them automatically by Bonjour. Alternatively UDPSyphon supports local broadcast and multicast as well as conventional unicast (one-to-one communication). Using broadcast and multicast, you are required to select "Method" pull-down list and to prepare IP address for them.
Merit that UDP allows to send data without specific receiver lead less stability and less reliability due to packet loss etc. during communication. Mainly bigger transfer data or less network quality causes packet loss in sending, routers, and receiving, so to avoid these mischiefs, you can confirm the size on display of transfer data and make it as small as possible before you send them. Please prepare adequate configuration and sufficient network environment referring to numbers of packet loss on both server and client.
Logically, this allows transferring data over a quite large number of machines, however in practice we confirmed operation check on a few machines and we could not scrutinize the breaking point of numbers. We welcome feedback from spontaneous testers.
|Multiple simultaneous transfer:||inefficient||efficient|
|Recommend TCPSyphon when you need to secure high frame rate under the condition of a few receiver.||Recommend UDPSyphon when you do not need to stick to deliver quality under the condition of many receivers (more than 10). With UDPSyphon the better quality of images brings the bigger transfer size, and dramatic lower frame rate on the client. Please make transfer size as small as image quality permits by selecting TURBOJPEG compression as low quality of image.|
defaults write sg.techlife.UDPSyphonClient NSAppSleepDisabled -bool YES
defaults write sg.techlife.UDPSyphonServer NSAppSleepDisabled -bool YES
It would be encouragement for our future development and production if you contact us with requests and examples of your using way/ style etc. by the below desk.