• 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!

AudioSage — free audiophile app, looking for beta testers (Android)

I'm not sure what you are asking. If you are asking about the Assistant UI that has a history tab.
Yes.

please read my #16

multiple instances on different devices, same gMail login

Expected behaviour: History, continuity gets sync'd
 
So is lack of sync'ing History per login, as intended?
Chat history is intentionally session-based for privacy — it's not stored on our servers. Settings (philosophy preference, system components) are saved locally and we'll look at sync in a future update.
 
I joined and for kicks entered most of my audio gear and asked for an analysis. Your AI needs tuning. It screwed up the specs of about a third of the items (admittedly, many are vintage), so I went back in the notes with annotations. It still screwed up a couple. And, apparently, my weakest link is Michael Fidler's MM Pro Mk II - probably one of the finest phono stages in the world. But, it's kind of fun watching it clutch at straws. Also, it didn't like my Sony UBP X800 Mk2 that I use only as a CD & SACD transport (in my notes). It suggested a $5000 transport that does not play SACDs. Hey, it's AI; maybe it will learn.
 
It's Google's Gemini nothing more and yes a bluffing simpering flattering moron
 
Boy, is it! I tweaked my notes in an attempt to correct some of its misunderstandings an it got worse: it wants me to drive my monoliths IIIs with their non-existent internal crossover using the Apt model 1 power amp I have connected to my motion 15i speakers. Part of the problem is that I have what is essentially two complete systems but they are interconnected. It can't compute. But it is amusing.
 
I now have 7 testers and still need 5 more to make into the store. I am very grateful to my current testers and if 5 more people would be willing to help out that would mean the world to me.

 
I joined and for kicks entered most of my audio gear and asked for an analysis. Your AI needs tuning. It screwed up the specs of about a third of the items (admittedly, many are vintage), so I went back in the notes with annotations. It still screwed up a couple. And, apparently, my weakest link is Michael Fidler's MM Pro Mk II - probably one of the finest phono stages in the world. But, it's kind of fun watching it clutch at straws. Also, it didn't like my Sony UBP X800 Mk2 that I use only as a CD & SACD transport (in my notes). It suggested a $5000 transport that does not play SACDs. Hey, it's AI; maybe it will learn.
Boy, is it! I tweaked my notes in an attempt to correct some of its misunderstandings an it got worse: it wants me to drive my monoliths IIIs with their non-existent internal crossover using the Apt model 1 power amp I have connected to my motion 15i speakers. Part of the problem is that I have what is essentially two complete systems but they are interconnected. It can't compute. But it is amusing.
I have updated the AI instructions and this explains what was happening and how it will work going forward. I appreciate your great feedback and if you can stick with me, we might achieve something better. I will probably release an update later today or this evening.

Re: System Analysis — What's Happening and What's Coming

A few things to explain about what you experienced:

On incorrect specs, especially for vintage gear
The AI powering System Analysis (Google's Gemini) has a knowledge cutoff of early 2025, and its training data on vintage and niche components can be thin or flat-out wrong. It knows a Schiit Bifrost better than it knows a 1978 Marantz. The Notes field exists precisely so you can correct it — and your instinct to annotate was right. The next build tightens this significantly: the AI will be explicitly instructed to treat your notes as ground truth and not contradict them with its own assumptions.

On the "weakest link" misfire
If the AI doesn't recognise a component — a bespoke phono stage, a rare vintage piece — it has been defaulting to flagging it as a weakness simply because it doesn't know it. That's backwards. The next build adds a rule: unfamiliarity is not a weakness. The AI will only identify a weak link when it has genuine knowledge of the component, and will acknowledge when it can't make a confident call.

On the two-system topology confusion
This one is a structural limitation of the current format. A flat list of components doesn't tell the AI what's connected to what, so it guesses — sometimes badly, as you found. The next build instructs the AI to map out signal chains from your components and notes before writing anything, and to admit ambiguity rather than invent connections. In the meantime, explicit wiring notes on each component help a lot — something like "connected to [speaker name] only" gives it enough to work with.

What's already working in your notes
Your notes are being sent to the AI right now. The next build makes them authoritative. So the more explicitly you describe your setup in notes, the better the analysis will be even today — and significantly better with the next update.

Your setup — two interconnected systems with carefully curated vintage and specialist gear — is genuinely at the challenging end of what any AI analysis tool can handle. Appreciate you sticking with it.
 
Glad to oblige. It's kind of fun watching AI stumble all over itself. I'll amend the notes some more and see what happens.

Edited to add: After extensive annotation, it wants me to replace an SME series III arm (effective mass 5g) and an ADC XLM Mk3 cartridge installed with an SME series V arm (effective mass 11g). And it thinks that with a stable of mostly very high compliance, vintage MM and MI cartridges, I should switch to MC. Yeah, not happening. And still amusing.

At least, it seems to understand the interconnections of the combined systems now.

Also, I have now added almost everything I own. It took just over 3 minutes to figure it all out before it began giving me feedback
 
Last edited:
New build for today is available. Just update from Play store. I would love to hear back how the AI now handles edge cases. Any helpful info put in the notes will now be taken more seriously by the AI and should help.

Only 2 more testers needed.
https://groups.google.com/g/audiosage-beta
 
Last edited:
I wonder if any of the testers have discovered the Notifications feature. Just turn it on in the About screen. You will get periodic (not a flood) HiFi focused headlines pushed to you. Another way to stay current without doing proactive searches.

Also, I wonder if any of you have found the easter egg yet?
 
It's taken about 40 iterations with changes to the notes to "train" your AI to understand my complex combination of 2 interrelated systems containing a mix of vintage and current gear without getting ridiculous upgrade suggestions. In the notes:
1) identify the system
2) qualify the item
3) identify interactions
For example: Thorens TD-521, SME 3012-R, Nagaoka MP-700, Michael Fidler MM Pro Mk II, Topping A90D & EXT90
Thorens // TD-521 // system 1; vintage TT renovated 2026
SME // 3012-R // system 1; vintage 12" tonearm, 14g effective mass; mounted on TD-521
Nagaoka // MP-700 // system 1; flagship MI cartridge; medium compliance; mounted on 3012-R
Michael Fidler // MM Pro Mk II // system 1; bespoke phono preamp connected via XLR to A90D
Topping // A90D // system 1
Topping // EXT90 // system 1; additional switching capability for A90D

And if you use a multi-format disc player or transport for CD and SACD, if you don't list SACD 1st in the notes, it will tell you to replace it with a $5000 CD-only transport.
Sony // UBP X800 Mk2 // system 1; multiformat transport for SACD & CD; HDMI-2 out to DoP to D90 III discrete via I2S
 
If I'm interpreting this correctly, it appears to be a solicitation for a commercial app testing service.
 
AudioSage is gaining momentum. Remember this is the beginning. Many paths and ideas are being generated. You can shape its future by your input. According to Google I have to hang on to my testers for another week or so and then I can publish to the public Google app store. Tell your friends. If I get 100 downloads once it is live, I will pursue a iPhone version. Google charges a one time fee of $25 to developers. Apple, charges $100 every year to developers. It makes it more expensive for small developers. Thanks.
 
Back
Top Bottom