![]() expat: solved CVE-2022-40674, which affected the firmware.dhcp: solved CVE-2022-2928, CVE-2022-2929, none of which affected the firmware.Updated base libraries and components, the main changes are as follows. 802.1x and Wi-Fi enterprise authentication methods using client certificates with a private key (e.g., EAP-TLS) did not work due to a missing component needed to parse the certificates.In some particular conditions (unreliable network connections and feeds with large amounts of data) the jSignage feed cache could fill up resulting in an unhandled exception that would prevent retrying retrieving the feed.Streams with an incomplete description in their SDP could make the player reboot. ![]() Fixed an issue where streaming sources which used MPEG-2 Transport Stream (TS) could freeze momentarily every few seconds, this occurred when the MPEG-2 TS only included PCR values every few seconds (violating MPEG-2 TS requirements) and the stream had variable bitrate this is now avoided by using a more robust stream clock estimator.Synchronization of audio and video could be off by a noticeable amount, in particular for streaming sources which use long-delay codecs.The player would reboot when the content referenced the player's own hostname, for instance to trigger an RPC command.Any fatal machine check exception (MCE) messages that cause an immediate reboot are now logged and decoded in the following boot to improve diagnostics.Recovery Console is updated to version 2.13.0 which includes the same core libraries and component updates as firmware 4.7.6-1.0.1.Īpplies to HMP400, HMP400W, and third-party players.The SNMP functionality is now available on all device models and no longer requires a DSOS license.The player configuration file is now included in the report when the report is uploaded to a server, via Pull Mode.The DSOS license data is now included in the response of the get_info command of the RPC API and in the Status API.Perhaps, to better understand, could you run the same query but crossing the equator.Applies to HMP400, HMP400W, HMP350, HMP300, DiVA, and third-party players.įirmware version number: 4.7.6-1.0.1-b73dbc11 Improvements Searching in Google I found this maillist exchange regarding AT_Area and polys touching the equator: How could I generate a grid of valid geometries that covers the whole globe?Īs for your first problem, what would you want to happen with a point that falls exactly on the boundary between two grid cells? Throws couldn't project point (-180 90 0): latitude or longitude exceeded limits (-14) If I avoid the geography type, and use a geometry there is no global projection that outputs the correct size of all grids. Throws an error ptarray_area_spheroid: cannot handle ptarray that crosses equator e.g when I compute the square meters of a grid (for the density) SELECT ST_Area(ST_GeographyFromText('POLYGON((-15 0,-15 5,-10 5,-10 0,-15 0))')) Second, it seems the algorithm generates invalid geometries. The question is thus if there is a constant for the absolute minimum step value that I could use to guarantee that one point exactly lays next to another with no space inbetween. I could subtract a very small value from corners, but this risks loosing objects when they come to lay exactly on the original line. 180 in a fixed step size creating the multiline polygons.įirst, adjacent cells share a separating line, making objects on it counting towards two or more cells. To create the grid, I have created multiline polygons, both using a script of my own, and the function suggested here: How to create a regular polygon grid in PostGIS?. The grid is used to measure a density value by counting the number of certain spatial objects in each grid cell. I want to create a grid spawning the whole globe.
0 Comments
Leave a Reply. |