Panasonic AW-UE100 Web Interface Control Supplement - Page 20

upper limit of JPEG2.

Page 20 highlights

The notes common for each CGI are as described below. When a video is acquired simultaneously by several PCs and receivers, the best effort judgment is performed at the camera side. Therefore, the expected frame rate display may not be achieved. When the WEB menu/Video over IP/JPEG/JPEG(1)~(3) transmission are OFF, the response may be in the form of a pitch black JPEG image. As for the resolution and frame rate, the content registered in the WEB menu/Video over IP/JPEG(1)~(3) is given priority. Therefore, even if the resolution is specified in the arguments, the response may be issued with an unexpected resolution and frame rate. Example) If JPEG(1) = 1280 x 720/30 fps, JPEG(2) = 640 x 360/5 fps, JPEG(3) = 320 x 180/15 fps, /cgi-bin/mjpeg?resolution=320&framerate=15 => As instructed, the response is in the form of content of the 320 x 180 JPEG(3). /cgi-bin/mjpeg?resolution=1280&framerate=15 => As instructed, the response is issued by subtracting the frame rate from the content of the 1280 x 720 JPEG(1) /cgi-bin/mjpeg?resolution=640&framerate=15 => The response is issued with a resolution of 640 x 360, but the frame rate is 5 fps, which is the upper limit of JPEG(2). /cgi-bin/mjpeg?resolution=320&framerate=1920 => Because no content is registered in JPEG(1) to (3), the response is issued with the resolution of JPEG(1) and a frame rate of 5 fps. /cgi-bin/mjpeg => Because there are no parameters, the response is issued with the resolution of JPEG(1) and a frame rate of 5 fps. Note that if you use /cgi-bin/aw_ptz?cmd=%23RZLx&res=1, the resolution of JPEG(1) changes. Integrated Camera Interface Specifications / Supplement for Web Control 19

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94

Integrated Camera Interface Specifications / Supplement for Web Control
19
The notes common for each CGI are as described below.
When a video is acquired simultaneously by several PCs and receivers, the best effort judgment is
performed at the camera side. Therefore, the expected frame rate display may not be achieved.
When the WEB menu/Video over IP/JPEG/JPEG(1)~(3) transmission are OFF, the response may be in
the form of a pitch black JPEG image.
As for the resolution and frame rate, the content registered in the WEB menu/Video over
IP/JPEG(1)~(3) is given priority.
Therefore, even if the resolution is specified in the arguments, the response may be issued with an
unexpected resolution and frame rate.
Example) If JPEG(1) = 1280 x 720/30 fps, JPEG(2) = 640 x 360/5 fps, JPEG(3) = 320 x 180/15 fps,
/cgi-bin/mjpeg?resolution=320&framerate=15
=> As instructed, the response is in the form of content of the 320 x 180 JPEG(3).
/cgi-bin/mjpeg?resolution=1280&framerate=15
=> As instructed, the response is issued by subtracting the frame rate from the content of the 1280
x 720 JPEG(1)
/cgi-bin/mjpeg?resolution=640&framerate=15
=> The response is issued with a resolution of 640 x 360, but the frame rate is 5 fps, which is the
upper limit of JPEG(2).
/cgi-bin/mjpeg?resolution=320&framerate=1920
=> Because no content is registered in JPEG(1) to (3), the response is issued with the resolution of
JPEG(1) and a frame rate of 5 fps.
/cgi-bin/mjpeg
=> Because there are no parameters, the response is issued with the resolution of JPEG(1) and a
frame rate of 5 fps.
Note that if you use /cgi-bin/aw_ptz?cmd=%23RZLx&res=1, the resolution of JPEG(1) changes.