#Possible Audio Analysis Bugs

1 messages · Page 1 of 1 (latest)

balmy isle
#

Hey all, been loving Music Assistant for about year now and especially in the last few months, between the new plugins and the android app/AA integration, I'm finding myself almost completely removed from cloud services, and MA has been my go-to for 2-3 hours of music a day at home, work, and on the go!

I am in the process of running my ~9000 track library through the Sonic Analysis and AcoustID, but I think I am running into two issues during this process that are slowing me down.

The first is with the Sonic Analysis. It works flawlessly on tracks that I am playing, but I also have a NAS share with DJ sets and other flac/opus files that are >200mb and >1 hour playtime. I'm not sure if these files are taking too long to compute, or erroring out. (Running HA/MA on HAOS on a 5th gen intel NUC, CPU and RAM loads are under 50% while analyzing music).

As a workaround, I could either temporarily disable my music provider with the large files, or I also ran an automation that would cycle songs every 45 seconds on a muted speaker to trigger the analysis while playing, but whenever I forget to disable the large file provider, sonic analysis will eventually grind to a halt while it gets stuck on these files.

My logs don't show any errors, but with a 4 hour run budget, I would expect these files to eventually complete. (see attached logs)

The other issue I am having is related to AcoustID. 100% of the tracks that get analyzed cause a "AcoustID returned HTTP 400 - discarding result" error in my logs. My audio analysis page shows 0 tracks fingerprinted, so maybe the requests are malformed? I did create an acoustID account and enter my API key into MA.

Specs: HAOS baremetal, i5-5300u, 16gb ddr3, HA2026.1, MA BETA 2.9.0rc2

📎 message.txt
tepid oak
#

@eager current @surreal drum FYI
especially the acoustID issue seems like a serious one to look into before release ?

eager current
#

@balmy isle did you "Get user API key for sumitting new fingerprints" or did you "Register a new Application" because you needed to do the later and the prior is the obvious one and what I did when I first tried it. Once you register a new application it gives you an API key on the "Your applications" Page.

image.png
#

as for sonic analysis, it will take about as long as the track the way we have it set up. The RC's and above will set the automatic timeout of a track to 1.5x the track length, and the background process will let a running analysis go until it hits the timeout (it wont' stop it when the analysis job runs out of time budget). So, given a single a 4 hour file it should finish in 4-5 hours. We do limit speed to avoid crushing your CPU. In your case, with a dual core CPU I wouldn't' change the setting for how many to analyze at once higher than 1, you don't really have that much headroom.

Seperately, we should probably allow for specific libraries to be opted out of analysis. That folder full of 4 hour DJ sets isn't goign to get much good from being analyzed and I wouldn't want it analyzed personally.

tepid oak
#

@eager current why didnt we register one api key for MA itself instead of letting everyone register

surreal drum
#

Because they said in their docks that everyone should register their own API key and they didn't respond to my many emails to clarify that.

tepid oak
balmy isle
#

@eager current thanks for the tips! you were 100% on the nose with the AcoustID issue. The 10 char key from https://acoustid.org/api-key is what I set up with originally.

Once I registered an application key at https://acoustid.org/my-applications I started getting valid lookups!

I also agree with the sentiment of opting certain music sources out of sonic analysis and fingerprinting. In my case, the only reason for analyzing these large files is so they don't clog my analysis queue 🤣

#

I appreciate the insight into the sonic analysis as well!

surreal drum
tepid oak