# Updates > Part of [LISQM](https://zhenxianli.github.io/LISQM/) (List of Implementations of Sound Quality Metrics), a list of open-source implementations of psychoacoustic metrics. Data as of 2026-10-28. Web page: https://zhenxianli.github.io/LISQM/updates.html ## 27 October 2026: Version 0.5.10: rota-order added Added rota-order (ROTA), a newly released Python library for order analysis of noise and vibration from rotating machinery. It computes the ECMA-418-1:2024 tone-to-noise ratio and prominence ratio of machine orders along a run-up, and since its version 0.6.0 it wraps MoSQITo, sottek-hearing-model and SQAT to bin loudness, sharpness, roughness and tonality along rpm; the project map shows these links. ## 19 October 2026: Version 0.5.9: SQAT's interface follows pySQAT's layout The FAQ, the SQAT and pySQAT pages and the Languages page now say that the graphical interface SQAT added in v2.0 follows the layout of pySQAT's interface, as the header of its code says. ## 19 October 2026: Version 0.5.8: SQAT's graphical interface The SQAT page and the Languages page describe the graphical interface that SQAT added in v2.0, and the FAQ names the SQAT version that pySQAT ports (v1.3). ## 17 October 2026: Version 0.5.7: SQAT v2.0 and ecma418-torch - SQAT v2.0 is out. Its 4th-edition ECMA-418-2 functions and the Widmann annoyance model are now in a release, the release is under the GPL, and the SQAT page says what changed from v1.3. - Added ecma418-torch, a newly released Python package with differentiable ECMA-418-2:2025 roughness and fluctuation strength in PyTorch. It was found by the scheduled search for new projects. ## 14 October 2026: Version 0.5.6: the maps agree The whole project map now shows every line of every metric page's map: a project with its author's own code for one metric and ported code for another has both lines, and a comparison for one metric is drawn beside a code line for another. Only a same-contributor line is left out beside a line of the author's own code. ## 10 October 2026: Version 0.5.5: the map before the implementations On each metric page the project map now comes right after the editions, before the table of implementations. On the Projects page the legend of the map is back above the picture. ## 10 October 2026: Version 0.5.4: metric maps keep to their metric A line on the map of a metric page now joins only projects listed for that metric; the whole project map still shows every recorded relation. ## 10 October 2026: Version 0.5.3: the Projects page The Projects page opens with how its lists are ordered, then the project map with its legend under it. ## 10 October 2026: Version 0.5.2: tidier maps and links - On the map of each metric page, projects that no line joins are laid out in rows instead of a column. - A link to a standard or a paper opens the Standards page at its whole row, which is marked. ## 9 October 2026: Version 0.5: search A search field in the tab bar finds metrics, standards and papers, projects and function names; on phones it opens from the Search button. On the Projects page, a filter shows only the projects that match, for example a language, a licence or a metric. - The project map gives every line its own end, so that lines no longer meet at one point, and joins every pair of projects that share a contributor. Code from another project is "ported or adapted"; projects that no line joins are drawn as boxes without lines, also on the map of each metric page. - Each standard or paper on the Home timeline links to its entry on the Standards page. - All text has one reading width; only tables, the timeline and the maps are wider. - Validation tags name HEAD acoustics ArtemiS SUITE wherever a project compared its results with it, now also for SQAT's ECMA-418-2 loudness, roughness and tonality. - Metric pages and the Languages page flag licences that limit use; the FAQ says what a listing does not certify. - Corrections from a review of the site. ## 8 October 2026: Version 0.4: the project map A new page, the [project map](https://zhenxianli.github.io/LISQM/projects/map.html), shows how the listed projects are connected: code ported or adapted from another project, the author's own code, use at run time, results checked against another project, and shared contributors. ## 8 October 2026: Licence: CC BY 4.0 for the data and the text The data and the text of LISQM are now released under CC BY 4.0: they may be reused, also commercially, with credit. The code that builds the website stays under MIT. Versions up to 0.3.0 remain available under MIT. ## 7 October 2026: Version 0.3: ported code, citations and new projects Method pages show which implementations were ported from which; a comparison with an implementation's own source is marked as such. A new section, *Before you compare numbers*, lists the settings that make correct implementations give different results. - Every project page says how to cite the project, and all references are available as BibTeX. - New projects: ITA-Toolbox, Mosqito.NET, two legacy MATLAB tools, and PsyTools in a new group, *Status unknown*. - SQAT and MoSQITo (widely used) and sottek-hearing-model (a very good implementation) come first, in bold. - Each project page explains its kind: library/toolbox, research code, application, plug-in or reference program. - The monthly refresh also reports broken links. ## 7 October 2026: Version 0.2: how each implementation was validated A new section, *How it was validated*, says what each project checked, against what, and with what result. Validation tags name the reference, for example "compared with MoSQITo". - On the home page, "+ more" opens the remaining projects in place. - Edition labels link to the standard or paper. ## 7 October 2026: Two newly released projects Added PsychoacousticMetrics.jl, a Julia library, and Kirin Hypha, a measurement plug-in for audio workstations written in Rust. Both were found by the first scheduled search for new projects. ## 6 October 2026: Version 0.1: the first public version LISQM starts with 32 projects in eight languages and 22 methods, from Zwicker loudness to aural detectability. Every implementation is tied to the standard edition or model paper it follows, with links to its sources. Repository and package data are refreshed monthly.