Recherche avancée

Sur d’autres sites (5286)

• Making Sure The PNG Gets There

  14 juin 2013, par Multimedia Mike — General

  Rewind to 1999. I was developing an HTTP-based remote management interface for an embedded device. The device sat on an ethernet LAN and you could point a web browser at it. The pitch was to transmit an image of the device’s touch screen and the user could click on the picture to interact with the device. So we needed an image format. If you were computing at the time, you know that the web was insufferably limited back then. Our choice basically came down to GIF and JPEG. Being the office’s annoying free software zealot, I was championing a little known up and coming format named PNG.

  So the challenge was to create our own PNG encoder (incorporating a library like libpng wasn’t an option for this platform). I seem to remember being annoyed at having to implement an integrity check (CRC) for the PNG encoder. It’s part of the PNG spec, after all. It just seemed so redundant. At the time, I reasoned that there were 5 layers of integrity validation in play.

  I don’t know why, but I was reflecting on this episode recently and decided to revisit it. Here are all the encapsulation layers of a PNG file when flung over an ethernet network :

  
  
  

  So there are up to 5 encapsulations for the data in this situation. At the innermost level is the image data which is compressed with the zlib DEFLATE method. At first, I thought that this also had a CRC or checksum. However, in researching this post, I couldn’t find any evidence of such an integrity check. Further, I don’t think we bothered to compress the PNG data in this project long ago. It was a small image, monochrome, and transferring via LAN, so the encoder could get away with signaling uncompressed data.

  The graphical data gets wrapped up in a PNG chunk and all PNG chunks have a CRC. To transmit via the network, it goes into a TCP frame, which also has a checksum. That goes into an IP packet. I previously believed that this represented another integrity check. While an IP frame does have a checksum, the checksum only covers the IP header and not the payload. So that doesn’t really count towards this goal.

  Finally, the data gets encapsulated into an ethernet frame which has — you guessed it — a CRC.

  I see that other link layer protocols like PPP and wireless ethernet (802.11) also feature frame CRCs. So I guess what I’m saying is that, if you transfer a PNG file over the network, you can be confident that the data will be free of any errors.

• Including library header file

  4 juin 2015, par Erik Villegas

  I’ve installed OpenSSL, and put the header files in /usr/include.

  So when I compile this very simple program, it works just fine with gcc and clang :

  #include <openssl></openssl>ssl.h>
  
  void main() {}

  Now I’m trying to compile FFmpeg with OpenSSL. I’ve include the appropriate flags, but ./configure gets hung up here :

  /Users/..../ffmpeg-2.2.1/libavformat/network.c:40:10: fatal error: 'openssl/ssl.h' file not found
  
  #include <openssl></openssl>ssl.h>
  
           ^
  
  1 error generated.
  
  make: *** [libavformat/network.o] Error 1

  Any idea why it wouldn’t recognize the location of openssl ? I’m stumped.

• Efficient low latency stream forwarding in intel atom

  31 juillet 2017, par Sönke Felsing

  I have a certain problem in forwarding a stream from a web camera to my local network.

  My Network camera provides a RTP video stream 720p24 to NIC1 of my Gateway PC (Intel Atom, 1.8GHz , Ubuntu 16.04). Now I would like to forward this stream to all PCs (Intel i5, i7,...) which are connected to NIC2 of the Gateway PC.

  I tested already some stuff with ffmpeg and VLC. VLC does not even run the Video on the Atom due to Hardware limitatons and ffmpeg is just capable of 1-2fps at 480p, but ffserver works fine. MPlayer at least Shows the Video in all its beauty but does not support Streaming unfortunately.

  Does anybody know a well performing way to get access to the stream of the camera through the Gateway PC without directly connecting the two Networks ? Due to the fact that we would like to make some remote operations there may not be introduced any further latency for buffering, transcoding, ...

  If the Solutions uses multicast I would be happy.

  I really look forward to your responses !