When the key or the tempo is the thing holding you up.

1A loop pack arrives and the key is nowhere in the filenames.

Play any loop in the pack and the key and tempo appear in the menu bar. Nothing is imported and no folder is scanned, so the pack can stay exactly where it is.

2A filename claims a key and the audio disagrees.

The read comes from the sound that is playing, not from the text on disk. When the two disagree, the filename is the thing that is wrong.

3A sample was pitched down after it was bought, so its label is now stale.

The read follows the pitch as it sounds right now. Whatever the file was called when it was bought stops mattering.

4A single one-shot needs a note, and somebody wants a tempo too.

The note comes back. A tempo does not, because one hit has nothing to count against. No honest reader gives a one-shot a tempo.

5A collaborator sends a stem with no session notes attached.

Play the stem and read it, instead of waiting on a reply from another time zone.

6An old bounce survived and the project file did not.

The bounce is the only surviving record of that session, and playing it recovers the key and the tempo without the project file.

7A voice memo was recorded on a phone at three in the morning.

A memo reads the same as a master, because the app listens to what the Mac is playing rather than to a file format.

8A vinyl rip is running slightly fast.

The read reports the pitch as it is playing, which is the pitch that will actually sit against the session, not the nominal key of the pressing.

9A construction kit lists one key for the folder, and some files do not match.

Each file is read as it plays, so the outliers get found one at a time instead of being trusted on the folder's word.

10A pack was tagged by whoever uploaded it and nobody ever checked.

Playing a file takes about as long as reading its tag, and the answer comes from the audio rather than from the uploader.

11Metadata sits inside the file, and the DAW has no field that shows it.

The reading appears in the menu bar with no inspector, no browser column and no import step.

12A file plays fine and refuses to import into the DAW browser.

Playing it in anything at all is enough, because the app reads the Mac's audio output and never touches the file itself.

13A drum loop has a tuned ring buried under the hits.

The ring goes amber and the panel names the contenders, because there is no stable tonal center to lock onto. Amber is a shortlist, not a verdict.

14A track is playing on a streaming service and cannot be downloaded.

Nothing needs to be exported. If it plays on the Mac it can be read.

15A video has an obvious hook and nothing useful in its description.

The description is irrelevant to the reading. Press play and watch the menu bar.

16A sample is being previewed in a store before a credit gets spent.

The preview is audio like any other, so the key is known before anything is bought or downloaded.

17A sound is being auditioned inside a plugin's own browser, where no file exists on disk yet.

The plugin's output goes through the Mac, so the preview reads without ever being rendered or saved.

18A hardware synth is coming back through an interface.

It reads once the part is monitored through the Mac. A synth wired straight to the speakers never reaches the Mac, so there is nothing there to read.

19A turntable is running through the interface into the open session.

The record reads while it plays, at whatever speed the platter is actually turning.

20A guitar is going through a pedal chain and into the room.

Monitored through the Mac, the chain reads like anything else, tuning drift and all.

21Somebody is holding up a phone across the room.

There is nothing to read. Audio that never reaches the Mac is outside what the app can hear, so the phone has to play through the Mac instead.

22A soundtrack is playing inside an app that has no export at all.

Export is not part of the path. The app reads playback, so a closed application is not a wall.

23Someone on a call plays a reference from their end.

Whatever the Mac plays back is readable, including audio arriving from somebody else's machine.

24A radio stream or a recorded set is running with no tracklist.

The reading updates as the audio changes, so a continuous stream gives a continuous answer.

25A reference lands in a client session and someone asks the key out loud.

The answer is already in the menu bar from playing it. Nothing has to be opened and nobody leaves the chair.

26An artist hums an idea at the mic before a project is even open.

The hum is audio, so it reads with no session, no track and no import.

27A topline writer asks for the key at the top of the second verse.

The read is settled from the first playback and it holds, because a locked reading stops listening by itself.

28A session player is plugging in and wants the key before the count.

Play eight bars of the demo and the key is on screen before the headphones are on.

29Four people are working on four machines and the beat came from a fifth.

Each machine reads the beat from its own playback, so nobody waits on the person who made it.

30A vocalist wants to know whether the track sits in their range.

The reading gives the key it is in. What to do about it stays the singer's call.

31A mix is playing back for a client and stopping it would break the spell.

It lives in the menu bar. No window takes focus and playback is never interrupted.

32Someone asks a question in the middle of a take.

The reading runs while the take runs, so answering it costs the take nothing.

33A band is about to be counted in and the tempo is still a guess.

Play the demo once and the tempo is a number instead of an argument.

34An A&R plays a comparison record and asks what it would take to match.

Key and tempo for the comparison come off one playback, which is the part of that question that has an answer.

35A writer walks in with a reference and no idea what is in it.

One playback settles both numbers, and the ring shows whether the reading is a lock or still deciding.

36Pro Tools is open and the session is still at the default tempo.

Send sets the session tempo and the Key Signature ruler directly in Pro Tools, once Accessibility has been granted and the set confirmed.

37Logic Pro is open and the project needs both numbers before tracking starts.

Send sets the project tempo and the key signature directly in Logic, on the same one-time Accessibility grant that Pro Tools needs.

38Ableton Live 12 is open and the key needs to land somewhere.

Live applies the tempo and the song scale, with the companion selected once. Live has no project key field to write into, so the scale is what there is.

39FL Studio is open and the same question comes up.

FL Studio applies the tempo. It has no global project key at all, so no key is sent, and no page here will pretend otherwise.

40The DAW in use is not one of those.

A standard MIDI file is saved instead, and no program is brought forward. Anything that reads MIDI can take it from there.

41A tempo gets retyped and one digit lands wrong.

The handoff removes the typing, which is where that class of mistake comes from.

42The DAW is not installed on this machine, so there is nothing to send to.

The key and the BPM are put on the clipboard as well, on every send. The action is never a no-op, even when there is no program there to receive it.

43A project has been running for an hour at the wrong tempo.

The correct tempo goes in from the app rather than being reconstructed by hand.

44A number could be right, or exactly double, or exactly half.

The reading is taken from the audio as it plays rather than from a tap, which is where the half and double confusion normally comes from.

45A loop does not land on a round number.

The reading is reported as it is. A loop that sits between two round numbers is not rounded into one of them.

46A drummer speeds up through the chorus.

The tempo reading moves while the drummer moves, so the drift is visible instead of averaged.

47Tapping it in gives a slightly different answer every time.

Nothing is being tapped. The number comes from the sound, so it does not change with how tired the hand is.

48The groove is heavily swung and the count keeps slipping off.

The reading is taken from the playing audio, and a swung groove is read the same as a straight one.

49The intro has no drums in it yet.

The tempo settles once there is enough rhythmic content to count. Until then the ring keeps moving rather than showing a number that is not earned.

50A track changes tempo partway through.

The reading follows the change rather than holding the first number. One track with two tempos reads as two tempos.

51The tempo is very slow, and it could equally be half of a faster one.

The reading names what the audio supports. Where the audio genuinely supports two readings, the ring says so instead of picking one.

52The audio is pure drums.

The reading stays amber. There is no stable tonal center in a drum part, so nothing there earns a lock.

53The audio is speech or a podcast.

The reading stays amber, for the same reason. Speech has pitch and it has no key.

54The audio is a riser, a sweep or plain noise.

It stays amber. Noise without a tonal center does not resolve into a key.

55A song modulates halfway through.

The reading changes when the song does. A single answer for the whole track would be wrong for half of it.

56Two parts are layered in different keys.

The panel names contenders rather than choosing between them, which is the accurate description of what is actually playing.

57The part is sub bass and almost nothing else.

A reading on a very low part with few harmonics is not a lock, and the ring shows that rather than hiding it.

58A master is loud, dense and fighting itself.

Density is not certainty. A crowded master can read amber where a sparser mix of the same song locks.

59An ambient pad never moves off its root.

A drone gives the note it is on. Whether the piece is major or minor is not in the audio to be found.

60Only half a second has played so far.

The ring is still moving, which means the app is listening and has not yet reached an answer. Red only ever moves while it listens.

61Somebody wants a number for how accurate the reading was.

Test it in about ten seconds. Play a drum loop and you should get no key back, then play something you can name and watch it lock.

62The session is happening on a plane.

Detection runs on the device, so no connection is needed to get a reading.

63The studio has no working wifi.

Nothing about the reading depends on the network.

64The material is unreleased and the client will not let it leave the room.

It does not leave the room. Audio is not uploaded, not recorded and not stored.

65A machine is kept off the network on purpose.

A licensed copy keeps working offline between license checks. A licensed copy keeps working offline between license checks, for up to 21 days at a time.

66A facility blocks outbound traffic as policy.

Readings do not require an outbound request, so a blocked network does not block the work.

67Service on the bus drops for an hour.

The reading is unaffected, because it was never travelling anywhere in the first place.

68An agreement forbids sending the audio to a third party.

No audio is sent anywhere. The reading is computed on the Mac that is playing it.

69Somebody in the room asks where the audio actually goes.

Nowhere. That is the whole answer, and it is the same answer with the network cable pulled out.

70Remix stems arrive under an embargo.

The stems are read on the machine they are already on, and no copy of them is made to get the reading.

71A beat is being auditioned before any money changes hands.

The key and the tempo are known from the preview, before the purchase and without the file.

72A brief names a reference record and expects the pitch to match.

One playback of the reference gives the two numbers the brief is actually asking about.

73A sample is going to be sent for clearance.

The reading identifies what is in the sample as it plays. Whether it can be cleared is a question for a lawyer, not for a reader.

74The work is ghost production and cannot be posted anywhere.

Nothing is posted anywhere. There is no account, no library and no upload in the reading path.

75A label needs everyone working from the same numbers.

Everyone playing the same audio gets the same reading on their own machine, with the same ring showing how settled it is.

76A whole folder needs sorting by key.

Play the folder through and each track reads as it goes, one at a time, at the speed of listening to them.

77An old catalog needs checking, track by track.

Each track reads as it plays, which works, and it takes as long as listening to them does.

78A solo is being transcribed by ear.

The key gives the transcription a starting point. The notes still have to be worked out.

79A cover has to be learned before rehearsal.

Key and tempo come off the record in one pass, so rehearsal starts with both already settled.

80A kick is fighting the bass and nobody is sure of the root.

Play the bass part alone and read it, then tune the kick against the note that comes back.

81Toms need tuning to the song.

The song's key reads off playback, and the toms get tuned to a note rather than to a memory.

82A filter is self-oscillating and the pitch needs naming.

A self-oscillating filter is a tone, and a tone reads as a note.

83Two records are being checked before they get mashed together.

Play each one and compare the two readings. The page does not say whether they will work.

84A cue has to match a temp track.

The temp reads while it plays, including when it is playing inside a video editor.

85A guitar is tuned down a half step.

The reading reports the pitch that is sounding, which on a detuned instrument is not the pitch on the chart.

86A vocal sample is going under a new chord progression.

The sample's own key reads first, so the progression is written against a known note instead of a guess.

87A project cannot be opened because the DAW that made it is not installed.

A bounce of it can still be played, and a played bounce still reads.

88The studio machine is an Intel Mac.

Session Key runs on Apple Silicon. Any Mac with an Apple chip in the room is the one to run it on.

89The Mac is on an older version of macOS.

macOS 14.4 or later. The on-device capture it uses arrived in that release, so a system update is the whole setup step.

90The collaborator works on Windows.

It is a Mac app. Read the key on your Mac and send them the number, which is what their project needs typed into it either way.

91The work moves between a laptop at home and a machine at the studio.

One license covers up to three Macs, so the second and third machine do not need a second purchase.