Scaler2 Audio Detection - any way to improve accuracy?

Hi, I’m finding Scaler2 is struggling to identify much of the audio I feed it and seems hit and miss on whether it even attempts to identify a chord at all, even when a track is isolated. Sometimes it will fail numerous times, and then randomly on the next try it will hear the chord (all chords are playing well above the minimum detection level).

I know there are a few ways of detecting audio (here I’m using SideChaining in Logic), and I’m wondering if some ways are more accurate than others, or whether this is expected behaviour and it’s just not particularly reliable? It’s struggled with most of the files I’ve been trying.

Here is an EXAMPLE

Thanks.

EDIT: As you can hear/see I also tried separating the chords. I should note that I’ve tried changing the start and end of each chord to ensure there’s no clipping and that two chords don’t get mixed together, but it makes no difference.

Hi Eric (or James?)

It only depends on the “audio”

if it’s complex, let’s say a complete song with drums, bass, keyboards, vocals etc., and/or if it contains slow strumming or arpeggios, Scaler is unable to get single notes and the result is not good

I listened your chords, and they seem a sort-of strumming to me, i.e. I think they are a few single notes quite close in time to each other, so hard for the engine

But I’m not an expert, so maybe others will explain it better to you

1 Like

I thought I was up-to-date with Scaler2, but er, no. I’d downloaded it but not installed it (ha!). Can confirm that 2.9.0 breezes through this audio with zero issues! Apologies for being a muppet!

2 Likes

Thanks so much. I’ve just updated with another post and marked it as a solution. I, er, forgot to install the update whistles

I am happy that you got it

Anyway, don’t dare put in complex stuff like this one
:grinning:

1 Like