• Welcome to ASR. There are many reviews of audio hardware and expert members to help answer your questions. Click here to have your audio equipment measured for free!

What do we do about all the new audio software???

I've seen a coupla posts about software that I have no need for so mostly ignore it. A subforum for it might be a good way to go....

Not to mention, lately there has been a huge profusion of "me too" software. Just yesterday there was yet another music player that doesn't seem to do anything new or interesting. And then there are all the new DSP filter designers. Software is not like a restaurant, if you have a dozen burger joints in your suburb, the quality of each burger restaurant can remain decent and the market will weed out the bad ones and they will go out of business. But if you have a dozen music players, each one developed by one man and his AI, each one will have its own bugs and idiosyncrasies. Better if these dozen developers pooled their resources into one project.
 
It takes a lot of experience and .ore / diverse skillz to manage a bunch of developers in a collaboration than it does to just code

especially these days
 
It seems a day does not go by that someone doesn't come to us with a new piece of software they have written to solve this and that issue. I imagine with advent of AI, writing software has become far faster and easier.

Question is, what do we do with them all? Many say they are free but we worry that they are free now, and once we help them become successful, they won't be.

At the same time, such software may be useful to you all. And they could have genuine intentions.

So far, we have sort of treated them as Industry Members, giving them the tag and such. But there is pushback especially if the software is "free."

And at any rate, we have so many of these coming our way.

Let me know what you all think.
I can’t see any downsides at all. Developers who spend their long hours and skills at producing their software that they share freely for members benefits should be welcomed in my opinion. In answer to your question “What do we do with all of them”? My suggestion is absolutely nothing - let as many members as desired post and share free software.

Just my 2 cents..
 
I think a dedicated forum section is overdue. Preferably with mandatory tags for the various categories of software: commercial/educational/hobbyist, freeware/paid, open-source/closed-source, AI-assisted/classic coding, etc. That way readers get a clearer picture what they are dealing with.
 
Create a new DIY Soft subforum. I think this is quite sufficient from an organizational standpoint. Regarding potential revenues and their redistribution, that's up to Amir to decide.
 
What if someone who's an ASR contributor of some years wants to show off somehting and solicit comments?

For example, if I wanted to share my Kazoo neural analyzer/synthesizer but I had to wear a Vendor badge after that then I won't bother.

How about we put such software projects and vibe codes into a forum set up for that. If you're principle involvement at ASR is as representative of a commercial vendor, which includes new members hoping to advertise their hot new app and eventually profit, then you don't belong in that new forum and you should get the badge and put your offering in Audio Industry Forum.

So I'm not sure about badges. And I'm not sure open source is the distinction I'm concerned about.
I think we are only talking about vendor badges for people who are selling stuff.
 
Also there seems to be a class of "junk software " or "spam software" that exist because some dunning kruger candidate burst trough "open doors" or solving non existing problems ? because its to easy to code and you don't need any understanding of the audio science at all ? And can just produce these useless apps ?
 
Also there seems to be a class of "junk software " or "spam software" that exist because some dunning kruger candidate burst trough "open doors" or solving non existing problems ? because its to easy to code and you don't need any understanding of the audio science at all ? And can just produce these useless apps ?
This I'm seeing and not only in the audio field.

Part of me applauds the effort and often the cider learns something useful in the process. Something genuinely good may come of it.
 
On a side note, people need to be more cautious about downloading random software from just anyone.


JSmith
Yes - there is something to be said for free software that has existed for many years and is used everyday by huge numbers of people, compared with say a newcomer with zero provenance and 10 downloads. I'd be more likely to trust someone who'd been on ASR for a while though.

In any case, I'm happy to try all sorts of code that interests me - I have full-disks backups on multiple systems, so if I want to be sure, rather than uninstall (which does less than you think - I always look at the registry - and may have infected something you can't see), I just reload a previous full-boot image of the disk. In fact, this was how I got into using RAID/NAS - and spare disks and tape drives before that - before I even started ripping music to disk!

A new media player say, or some DSP code isn't quite enough to pique my interest these days - but I'd be reasonably safe trying it!

And Rescuezilla is very good free software for those who want to play safely.

[Edit - I'd go as far as saying if you have one PC that you rely on and not much external backup, I'd be wary of lots of free software, and even some that's paid for! Just because I'm paranoid does not mean they are not all out to get me!]
 
Last edited:
I think we are only talking about vendor badges for people who are selling stuff.
I'm talking about more than that.

An app that's ready, is for sale with established pricing, that will be supported is one thing. These are vendors. ASR already has protocols this.

Sharing a hobby project is another well known existing category here.

What's new is vibe coding has introduced an intermediate area that's impacting ASR. Someone stands up an app and is rather pleased with it and comes to us for comment (and perhaps praise) before having decided what to do with it next.

This new half-baked category is very easy. I figured that's what Amir is asking about. It is something I'm having to deal with in real life now and it's wasting my time. The barrier to entry with something that looks passable and does something novel is very low now. But in software, as in much engineering, the hard work is in finishing and support over time. It is for this that I proposed a forum specifically for presenting such apps. Faq, honor system, community involvement and moderation guide threads into it.
 
Paid vs free and closed vs open is easy to separate at a couple of sub-forums.

What's not easy to see and understand though is the difference between a simple tool or quirk (a VU meter vis for example) and a piece of software who can mess things big time (messing with levels, or wrong filter stacking, etc)

About the later, how many people you know here at ASR that are formally educated about it? Let alone creating apps too?
Filters (DSP if you like) is just about the most messy area, whatever has the potential to go wrong, it will, big time.

And since DSP (EQ in particular) involves levels and gain, I would really want to know the credentials of the author and the safeguards (for filter-stacking for example) .

(I do like beta-testing, but for less used stuff)
 
I think there's a narrow window now for new software built with AI, as I discovered recently Claude Code can do what most of this software can do on it's own and soon we'll be just pointing the AI at the need we have directly and cutting the middle man (Software) out of the equation completely.
 
This still boils down to a system where those we want to control do not want to be controlled. They have multiple ways of avoiding this kind of badging, and at the end of the day, they are the problem we are trying to solve. They are the ones putting an unpleasant flavour on these badges, even without having one attached to their name.

Like the guy who not long ago accidentally used the phrase "our customers", before later refusing to elaborate. He obviously did not intend to reveal that he was a dealer selling the product that he defended. He wanted to be seen as just another enthusiast using "trust me, I'm an expert" - rhetoric...

So I would state that the issue is not the ones dealing with software. It is the ones who in some way or another has an interest that is not revealed. Are they building a network of users for future opportunities? Are forum members writing about software they got for free while others have to pay for it? Do they have a new free software, but slightly hidden from view is that they have associated software that cost money? Are they working for a company that sells software to the audio consumers?

There are so many possibilities here. I am not worried about the badge itself.

But I am a bit worried by the ones not having a badge. What do I really know about them?
 
Last edited:
I’m a total amateur who has learned a lot of audio science from ASR. I’m handy with a soldering iron or repairing speakers, but coding is mostly beyond me, because when I went to school it was still the era of the slide rule. I’d therefore qualify as ‘at risk’ from dubious software promotion and claims.
However my experience on ASR is that it is quickly apparent how genuine, useful or reliable a piece of software is. I’m not sure badging or regulation would improve upon the ability of ASR contributors to call out or comment on unsubstantiated claims or dodgy procedures.
Having one forum or subforum for DIY software would be great just to make it easier to find stuff. It doesn’t seem logical to have hardware DIY but not software.
I’d also love to see some reviews- although I’ve no idea what issues would need to be thought through to make it possible to distinguish the software from the hardware running it.
In my dreams would be a test of how difficult it was to inadvertently use the software to wreck some hardware.
 
Paid vs free and closed vs open is easy to separate at a couple of sub-forums.

What's not easy to see and understand though is the difference between a simple tool or quirk (a VU meter vis for example) and a piece of software who can mess things big time (messing with levels, or wrong filter stacking, etc)

About the later, how many people you know here at ASR that are formally educated about it? Let alone creating apps too?
Filters (DSP if you like) is just about the most messy area, whatever has the potential to go wrong, it will, big time.

And since DSP (EQ in particular) involves levels and gain, I would really want to know the credentials of the author and the safeguards (for filter-stacking for example) .

(I do like beta-testing, but for less used stuff)
You are spot on with the background of the individual building it mattering big time, and I'd say it matters far more than them being able to code. If the person driving the agent to build the software can't verify what the agent is writing (both the code and the science), then the person building it needs to have serious rigor in their process, and even then it's very difficult. You cannot simply replace a math/science degree with an agent. It's not impossible, but it's far from simple, and the person doing it still needs to be an engineer who is deep into software testing and cares deeply about accuracy.

My own skepticism went thru the roof when I started building my own piece of audio software (out of my depth) using agents. Agents will build plausible code, and will even write you plausible tests that show the code works. However, the number details they get wrong in audio science in code is pretty astonishing, and also deflating if you were hoping for the easy path to close your knowledge gaps. I would never trust agent coded audio software that relies on science and math unless the developer brings receipts or I don't care about it's accuracy.

That said, it is possible, but you need to be a very rigorous software developer to design a process around rooting out agent inference, building from specs and source material, with verifiability and incredibly rigorous testing built in from day one. I just don't think most people would be willing to put in this much work. You REALLY need to care. It's not exaggeration to say it's an order of magnitude higher in time, cost, and effort than the effort to just YOLO it and hope the agent gets it right (which it very likely will not).
 
I can't say much useful about the badge thing, because I think separating 'professional audio software' from the vibe-coding, home-brew stuff we are creating by the dozens, may be hard to keep track of.

But, as a non-software engineer who is vide-coding stuff in my audio/video system, while also incorporating other people's projects, I would love a dedicated forum subsection. This could also be helpful to learn some basics and best practices from people who have the expertise, along with a better organization of the software being produced here anyway (some are hidden on page 53 of a 90 page thread, for example).
 
Back
Top Bottom