First @Codeberg #acxi issue (silly mistake, and good issue). acxi is a specialized CLI audio processing tool that, unlike #inxi (which is made as general utility for the wider #FreeSoftware ecosystem), is intended to meet specific audio file processing needs. It makes no effort to be 'easy' or 'user friendly', although it is immensely powerful. But not for newbies. Unlike inxi, which is fully operational out of the box, acxi does nothing until configured or run with the right CLI switches.,

And that closes the very first @Codeberg #acxi issue. And creates the first proper #codeberg acxi release, 3.6.02.

acxi is designed to be very stable, unlike #inxi which evolves constantly, and only gets updates for fixes, like this one, or to introduce new features wanted by me or a small handful of acxi users I know. eg --tagllst, which the #slackware packager requested. A feature I now use all the time. This has happened with several powerful features. Benefit of a few good eyes.

In terms of the #acxi code itself, because #inxi is far larger and more complex, and requires far more code discipline to maintain, and gets refactors all the time to achieve that goal, acxi tends to follow along like inxi's little brother, and benefits from all the improvements I introduce internally in inxi code. Particularly #Perl syntax and structures. In this sense, inxi really benefits acxi since acxi's code basically gets a 'free' upgrade using my latest stress tested inxi techniques