MediaWiki API result

{
    "batchcomplete": "",
    "continue": {
        "gapcontinue": "Revotech",
        "continue": "gapcontinue||"
    },
    "warnings": {
        "main": {
            "*": "Subscribe to the mediawiki-api-announce mailing list at <https://lists.wikimedia.org/postorius/lists/mediawiki-api-announce.lists.wikimedia.org/> for notice of API deprecations and breaking changes."
        },
        "revisions": {
            "*": "Because \"rvslots\" was not specified, a legacy format has been used for the output. This format is deprecated, and in the future the new format will always be used."
        }
    },
    "query": {
        "pages": {
            "1484": {
                "pageid": 1484,
                "ns": 0,
                "title": "Reference Image Blend Percentage aka Vapor Trails",
                "revisions": [
                    {
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": "[[General_Notes#Zone_Configurations_and_Fine_Tunings|Back]]\n\nThere is one important adjustment that is available for Fine Tuning the Zone sensitivity and selectivity, and it will not be found in the Config pages for a zone.\n\nIn the Console screen, click on the ID number for any camera.  This is the far left column.\n\nSelect the Misc Tab, and one of the options will be:  \"Reference Image Blend %ge\".  This parameter determines how much of any previous alarm pixels will be averaged into your current reference image.  If you have Outlining enabled, and you are seeing the outlines of your alarmed areas or blobs in your images, then you have probably seen the vapor trails, or ghosts that follow any moving object across the screen.  This ghosting can significantly increase the area of the alarm pixels, or blobs when the object moves quickly across the camera, as an automobile would.\n\nAs an object moves, it will change some pixels on the leading edge, and on the trailing edge, some pixels are changing back to the background, and these get interpreted as changed pixels as well.  So there will always be a \"ghost\" that follows a moving image.  The Ref Image Blend parameter exaggerates this effect, and can make your alarmed areas and/or blobs uncontrollably large.\n\nOne downside is that this parameter is set on a per camera basis, and not on individual zones.\n\nThe official docs say:\n\n----\n\nReference Image Blend %ge \u2013 Each analysed image in ZoneMinder is a composite of previous images and is formed by applying the current image as a certain percentage of the previous reference image. \n\nThus, if we entered the value of 10 here, each image\u2019s part in the reference image will diminish by a factor of 0.9 each time round. \n\nSo a typical reference image will be 10% the previous image, 9% the one before that and then 8.1%, 7.2%, 6.5% and so on of the rest of the way. \n\nAn image will effectively vanish around 25 images later than when it was added. \n\nThis blend value is what is specified here and if higher will make slower progressing events less detectable as the reference image would change more quickly. Similarly events will be deemed to be over much sooner as the reference image adapts to the new images more quickly. \n\nIn signal processing terms the higher this value the steeper the event attack and decay of the signal. It depends on your particular requirements what the appropriate value would be for you but start with 10 here and adjust it (usually down) later if necessary.\n\n----\n\nHowever, I have found that values greater than 10 work quite well.  Indeed, I have used a value of 50, which shouldn't work, but is giving me acceptable results."
                    }
                ]
            },
            "8247": {
                "pageid": 8247,
                "ns": 0,
                "title": "Reolink",
                "revisions": [
                    {
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": "===Reolink Cameras That Can Work With ZoneMinder===\n\nPoE camera: RLC-410, 520, 522, 423, 511, 510A, 520A, 810A, 820A, 1220A, 1210A, Trackmix POE, 1212A;\n\nWiFi camera: E1 Pro; E1 Zoom; 410W, 510W;\n\nLearn more about these cameras in Reolink official site: https://reolink.com/\n\nPlease note:\n\n# The list doesn't include the discontinued products. If you want to learn about these discontinued device, please ask Reolink employee in reddit: https://www.reddit.com/r/reolinkcam/ . Thanks!\n# The models that have \"A\" in the name are the cameras having on-board Person/Vehicle Detection, that is, RLC-510A, 520A, 810A, 820A, 1220A, 1210A. You may not use this local smart detection with Zoneminder, but you can use the advanced AI powered detection feature supported by the ZM.\n# When there are new products, this list will be updated.\n# Some products which are not supported are listed [http://web.archive.org/web/20240208083337/https://support.reolink.com/hc/en-us/articles/360007010933-Introduction-to-the-Third-Party-Software-Reolink-Products-Support/ here]: \"Reolink battery-powered cameras, Reolink E1, B400, D400, B500, D500, B800, D800, B1200, D1200 and Reolink Lumus\"\n\n===Reolink Cameras (Recommended)===\nThe latest step-by-step guide here\n\nhttps://www.reddit.com/r/reolinkcam/comments/jnurzm/adding_reolink_cameras_to_zoneminder_nvr/\n\n\n===RLC-410===\nThere is a lengthy forum thread here: \nhttps://forums.zoneminder.com/viewtopic.php?f=10&t=25874\n\n===RLC-423===\n\n<pre>\nSoooo, after lots of reading and just as much trial and error, I came up with this config that seems to work best:\n\nSource Type: ffmpeg\nSource Path: rtmp://10.0.0.165:1935/bcs/channel0_main.bcs?channel=0&stream=0&user=admin&password=password\nMethod: UDP\nOptions: reorder_queue_size=5000,allowed_media_types=video,buffer_size=10000000\nCapture Resolution: 640x480\nControllable: yes\nControl Address: admin:password@10.0.0.165:8000\nAuto Stop Timeout: 0.25\n\nThe high quality stream is \"channel0_main\", the low quality on \"channnel0_sub\". Strangely, the high quality channnel only works when I put the low quality resolution. So instead of 2560x1920 I need to put 640x480. That was a hard thing to find.\n\nOn the camera the following settings seem to provide the best results in ZM:\n\nClear Stream:\nResolution: 2560x1920\nFrame Rate: 30\nMaximum Bitrate: 6144\nH2.64 Profile: Base\n\nFluent Stream:\nResolution: 640x480\nFrame Rate: 7\nMaximum Bitrate: 160\nH2.64 Profile: Base\n</pre>\nRef: https://forums.zoneminder.com/viewtopic.php?f=14&t=30078\n\n===RLC-520===\n\n[[File:REOLINK-PoE-IP-Camera-Outdoor-5MP-rlc-520.jpg|200px]]\n\nLearn more about this camera: https://reolink.com/product/rlc-520/\n\nFirst: In a browser connect to the cam, config.gear, IN: Network Settings, Advanced, Port Settings, enable RTMP and Save. IN: System, User Managment, Change Password and Save.\n\n<pre>\nSource Type: ffmpeg\nSource Path: rtmp://10.0.0.165:1935/bcs/channel0_main.bcs?channel=0&stream=0&user=admin&password=password\nMethod: UDP\n</pre>\n\nThe default username/password on this model is \"admin\" and an empty password, but I had to set a password before the source path above would work.\n\nIf you want audio with the video recordings place this in the \"Options\" field of the \"Source\" tab:\n<pre>\nallowed_media_types=video,audio\n</pre>\n\nAnd use this option in the \"Video Writer\" field of the \"Storage\" tab:\n<pre>\nH264 Camera Passthrough\n</pre>\n\n===4K Cameras, Firmware, and RTSP===\n\nThe cameras below are 4K (8MP) cameras. As of this writing, the latest firmware for both the RLC-810A and RLC-820A is v3.1.0.956, released April 2022. I had mixed results with the 4K RTSP stream with these cameras. If you find the 4K RTSP stream unstable with lots missed packets, image degradation, and artifacts, you have two options:\n* Contact Reolink support. They are very prompt and helpful. They provided me with beta firmware, v3.1.0.1983, which solved the RTSP issues. With this firmware, you should use TCP rather than UDP. Maybe by the time you are reading this, these improvements have already made their way into an official firmware update that you can download from Reolink's support site.\n* Switch the main stream to 5MP and use RTMP instead of RTSP. This has been perfectly stable in my experience, but of course then you miss out on 4K (RTMP doesn't do 4K, at least on these cameras).\n\nThere are other Reolink cameras with 4K and even higher resolution. The above may or may not apply to them also. If someone has experience with them, they can add it...\n\n===RLC-810A===\n\nCamera detailed on: https://reolink.com/product/rlc-810a/   This is a 4K camera\n\nMost of the information for the RLC-820A (below) is relevant for the 810A also. Make sure you have the latest firmware (from April 2022 as of this writing, version v3.1.0.956_22041503), as it has updates to the RTSP server that significantly improve usability. I still got some artifacts on the 4K stream with TCP method, but so far UDP has been clean, so I recommend that. (See notes about beta firmware in the section above.)\n\nFor use with ZoneMinder, I recommend RTSP for both the substream and main stream, as RTMP does not work for the 4K main stream. The substream is only 640x360, but this is sufficient for motion detection. Use one monitor for motion detection on the substream in Modect mode, and another monitor in Nodect mode linked to the first one for saving 4K recordings of events. Make sure you have large enough pre- and post-event image buffers. I use 15 pre- and post-event frames on the substream (set at 7FPS) and 30 on the main stream (set at 15 FPS). The 4K stream is h265-encoded, so to avoid unnecessarily high CPU usage, turn off decoding on the main stream monitor and set the video writer as \"Camera Passthrough.\" Unfortunately, you will probably not be able to view the 4k videos on the web interface due to the encoding, but you can view them in an offline player that supports that codec.\n\nHere are the RTSP urls:\n\nrtsp://admin:password@IP:554//h264Preview_01_sub (substream)\n\nrtsp://admin:password@IP:554//h265Preview_01_main (main stream)\n\nNote that RTSP is not enabled by default in the camera; you have to log into the web interface and enable it there. (The same probably applies to all other Reolink cameras.)\n\nI did not need to set reorder_queue_size as mentioned for the RLC-820A below.\n\n===RLC-820A===\n\nCamera detailed on: https://reolink.com/product/rlc-820a/   This is a 4k camera\n\nCamera firmware version 3.0.0.494 works.  Camera firmware version 3.1.0.764 also works BUT you must go into the cameras Network Settings, Advanced, Ports and\nenable rtsp or rtmp.  The main difference between firmware appears to be the addition of more hardware motion sensing analysis in the camera and that after a factory reset the camera boots with rtsp and rtmp disabled until you turn whichever one you are using back on.\n\nReports with some Reolink cameras say they get smearing using RTSP and recommend RTMP.  I did not find this to be the case with this model of camera and\napparently only the low res substream works with RTMP, the 4K stream only works with RTSP\n\nHere are the links for RTSP  (substitute your own information)\n\nrtsp://admin:12345678@192.168.96.23:554//h264Preview_01_sub\n\nrtsp://admin:12345678@192.168.96.23:554//h265Preview_01_main\n\nWith the 4K stream set reorder_queue_size=1000\n\nor higher in Monitor->Source->Options\n\nOlder versions of ZM may require hard coding the CODEC to MJEPG.  zm 1.36.14 worked with the Auto setting, however.\n\n===Trackmix POE===\n[[File:Trackmixpoe.jpg|200px]]\n\nCamera detailed on: https://reolink.com/product/reolink-trackmix-poe/ This is a PTZ 4K camera with POE\n\nCamera came with firmware v3.0.0.1817_23022700 seems to be working well so far.\n\nrtsp://admin:password@hostname:554/Preview_01_main\n\nI'm seeing some smearing occasionally that causes an event.  Tried the reorder_queue_size option that the 820A has listed above, that doesn't seem to affect the problem. Waiting to hear back from ReoLink support.\n\nControl seems to work if you select the RLC-423, but I'm not confident it's complete and accurate.  I wouldn't know how to start figuring out how to change any of that to get it working better.  Also waiting on any advice ReoLink support might have on that.\n\nZM 1.36.33 on Rocky Linux 8.8\n\n[[User:Biloxigeek|Biloxigeek]] ([[User talk:Biloxigeek|talk]]) 08:17, 27 August 2023 (EDT)\n\n===RLC-1212A===\n[[File:Rlc1212a.jpg|200px]]\n\nSome basic information is given below. RLC-1212A is a bullet style camera with 12MP resolution, power over ethernet, f=4mm lens, infared and color night vision, two-way audio. Note that if you are using Camera Passthough on Monitor setup with h.265 encoded streams there could be issues with playback. Many browsers such as Firefox do not yet support h.265 encoded video.\n\n*Detailed manufacturer information: https://reolink.com/product/rlc-1212a/\n*Firmware: v3.1.0.2174_23050815\n*Server: RTSP (need to enable in web interface)\n*Main Stream: rtsp://username:password@ipaddress/h264Preview_01_main\n*Sub Stream: rtsp://username:password@ipaddress/h264Preview_01_sub\n\nResolutions Available\n*Main: 4512x2512 (h.265), 3840x2160 (h.265), 2560x1440 (h.264), 2304x1296 (h.264)\n*Sub: 896x512 (h.264)\n\nTested with ZoneMinder 1.36.33 on Ubuntu Server 22.04"
                    }
                ]
            }
        }
    }
}