After playing around with the Appro DM368 IPNC and our own DM368 based hardware I have the impression that the network performance of the DM368 does not match the encoder performance. Using JPEG, it is easy to generate bitrates > 25MBit/s, but when sending these via RTP, the CPU load goes up and frames get lost. Also when using the H.264 encoder with 16MBit/s and streaming to multiple clients not all frames can be transmitted.
Am I doing anything wrong? What is the maximum throughput one can expect from the combination DM368 Encoder + RTP streaming?
Also are there any features in the DM368 EMAC that are currently unsupported by the Linux driver and that could boost performance?
Regards,
Andreas.