Track Analysis

Every track you import gets analyzed so Ora knows how it behaves: how fast it is, what key it's in, where the energy sits. The work happens on your machine, in the background, and you can quit at any point without losing it.

What Ora measures

• BPM and beatgrid. The tempo, plus the precise position of every beat.
• Musical key. The tonic and whether it's major or minor, shown in both standard notation and Camelot.
• Waveform. A multi-resolution waveform that drives the deck displays.
• Energy. A 1 to 10 score for the whole track, plus a curve that shows how the energy moves bar by bar.

How it works

Analysis runs through a native engine built into Ora. There is no separate process to manage and nothing leaves your computer: no track is ever uploaded, and analysis works with no internet connection at all.

The work spreads across your CPU cores, sized automatically to the machine, so there's no setting to tune. On a busy import you may notice your Mac feels a little slower while it runs. That's expected: measuring beats and keys is real computation.

The queue

Analysis starts on its own as soon as tracks land in the library. Each row in the library shows its own progress, a spinner that resolves into BPM, key, and the rest as the numbers come in.

The queue knows to get out of your way:

• It pauses the instant either deck starts playing, and picks back up when playback stops.
• It pauses during library imports, then resumes once the import finishes.

You can quit mid-analysis without a second thought. Anything that was in progress is reset and queued again next time you open Ora, so no work is lost and nothing gets left in a half-finished state.

Where the results live

Everything Ora measures is stored in its own internal database. Your audio files are never touched: Ora does not write BPM, key, or anything else back into the files' tags. The source stays exactly as you imported it.