ATMOS

Taking longer than usual — check your network connection.

AtmosAtmos
LibraryBlogPricing
Sign inDownload
Journal

How to Add Your First Audio Track

Learn how Atmos turns audio files into reusable profiles, what happens when you upload a track, and how playback settings work once your first song is loaded.

TutorialAudioLibraryDocumentation

How to Add Your First Audio Track

Adding an audio track is usually the first real setup step inside Atmos. It is also the moment when the app starts to make more sense, because uploading a track does more than simply place a file in a list. It creates an audio profile, connects that profile to Atmos's playback system, and makes the track available as part of your reusable desktop environment.

This guide explains how the audio upload flow works, what Atmos does after a track is added, and which playback controls matter once your first song is loaded.

What counts as an audio track in Atmos

Atmos supports standard audio files directly through its upload flow. It also allows some video files to behave like audio sources, depending on how you configure them.

In practice, Atmos treats these as audio-capable content:

  • regular audio files such as MP3, M4A, WAV, AIFF, FLAC, OGG, Opus, ALAC, AAC, and WMA
  • video files when their audio component is enabled

This is important because Atmos does not only think in terms of file extensions. It thinks in terms of whether a profile contributes audio, background visuals, or both.

The fastest way to add your first track

To add your first track:

  1. Open the Atmos window from the menu bar.
  2. Go to the Upload area.
  3. Choose an audio file from your Mac.
  4. Confirm the track name in the final step.
  5. Press Add.

Once you do that, Atmos creates a new audio profile and adds it to your library automatically.

If it is the first audio-capable item you just added, Atmos will also load it into the player immediately so you can begin listening right away.

What Atmos does when you upload a file

The upload flow is more structured than a simple file picker.

When you choose a file, Atmos first identifies what kind of media it is:

  • image
  • audio
  • video

If the file is audio, Atmos treats it as an audio-only profile.

If the file is video, Atmos gives it a mode that determines whether the file should contribute audio, background visuals, or both. That means some uploaded videos behave like tracks in the player, even though they are not traditional music files.

After that, Atmos builds a profile record for the item. That profile includes:

  • the display name
  • the local file path
  • the media type
  • artwork if you add artwork
  • whether the item should contribute audio
  • whether the item should contribute background visuals

This profile-based design is what makes Atmos feel persistent. You are not loading one-off files every time. You are building a reusable library.

How Atmos chooses the initial track name

If the first file you add is not an image, Atmos uses the file name as the starting track name automatically. You can keep that name or replace it during the final step of the upload flow.

This makes the first upload faster, but it also gives you a chance to normalize names if your files have messy filenames or inconsistent formatting.

If you upload multiple files together, Atmos will still ask you for the final name during the details step before saving.

What happens after you press Add

When you finish the upload, Atmos saves the new profile into your library and then checks whether it should make that profile active immediately.

For audio content, Atmos looks for the first added item that contributes audio. If it finds one, it loads that profile into the shared player state.

That means the newly added track becomes more than a saved entry. It becomes the current playable source inside Atmos.

Once the track is loaded:

  • the player shows the track name
  • Atmos knows that a track is available
  • playback can start immediately
  • progress and duration begin updating once the media is ready

The difference between loading a track and playing it

In Atmos, loading a track and playing a track are related but not identical.

When a profile is loaded, Atmos prepares an AVPlayerItem, connects it to the shared player, updates the current track state, and marks the app as having a track available.

When playback begins, Atmos applies the current playback rate and starts the player if audio is enabled and the app is not globally disabled.

This distinction matters because there are cases where a track is loaded but not actively playing, such as:

  • when playback was paused
  • when audio has been disabled
  • when the app is in a disabled license state
  • when a saved state restores a track but not active playback

How audio files and video files behave differently

A pure audio file contributes only audio.

A video file is more flexible. In the upload flow, a video can be configured as:

  • audio only
  • background only
  • both audio and background

This means a single uploaded video can behave like:

  • a track with no visual use
  • a visual background with muted audio
  • a combined sound-and-visual profile

If your goal is simply to add your first song, a regular audio file is the easiest path. If you want one media file to power both the sound and the visual atmosphere, video becomes much more interesting.

We will cover video profile behavior in its own tutorial, but it is useful to know that the audio system already supports that crossover.

How playback starts once a track is loaded

Atmos starts playback through a shared audio player object that controls:

  • whether a track exists
  • whether it is currently playing
  • the current playback rate
  • the volume
  • loop behavior
  • Smart Loop behavior
  • saved playback position

As soon as the media item is ready, Atmos measures its duration and begins updating playback progress over time.

That progress is not only for the user interface. Atmos also uses it for state persistence, position restoration, and Smart Loop behavior when enabled.

The playback settings that matter first

Once your first audio track is loaded, there are four playback settings worth understanding early.

Volume

Atmos stores volume as part of the player state. If you change it, the app updates the active player and saves the setting so it can be restored later.

Playback rate

Atmos supports playback speed changes and remembers the chosen rate. If the track is already playing, the new rate is applied immediately.

Loop track

Standard loop mode restarts the track from the beginning when it reaches the end.

Smart Loop

Smart Loop adds a more advanced looping system that analyzes the audio and looks for musically similar jump points instead of always returning to zero.

You do not need Smart Loop to use Atmos, but it becomes one of the app's most distinctive features once you are comfortable with normal playback.

What happens when you add more than one audio item

Atmos can accept more than one upload in a session, and it includes an arrange-audio step when multiple audio-capable items are present.

This matters because Atmos is designed around profiles, not a fragile one-track-at-a-time workflow. You can add several items, reorder them during setup, and then save them into the library as separate reusable entries.

Even so, for first-time users, I recommend starting with a single file. It keeps the flow simple and makes it easier to understand what the player is doing.

How audio profiles appear later in the library

After saving, your track becomes visible in the Library area under the Audio section.

From there, you can:

  • load it again later
  • switch between audio profiles
  • rename it
  • attach or replace artwork
  • delete it if it is not built-in

This is one of the most important concepts in Atmos. Uploading a track is not a temporary action. It creates a library item that remains part of your setup until you remove it.

Why your uploaded track may not behave exactly like a normal music app

Atmos is not trying to be a full music library application in the traditional sense. Its playback model is tied to the rest of the environment.

That means audio behavior is connected to:

  • the current desktop atmosphere
  • background enable or disable state
  • app disable state
  • saved player state
  • Smart Loop analysis
  • profile restoration after relaunch

This is why Atmos feels different from a normal desktop audio player. It treats a track as part of a larger setup instead of as an isolated song in a playlist.

Good first-track choices

If you are trying Atmos for the first time, the best audio files to start with are:

  • ambient instrumentals
  • piano pieces
  • steady lo-fi or drone tracks
  • slow background music designed for looping

These work especially well because Atmos is built around repeated listening, seamless transitions, and long-lived desktop sessions.

A practical first-track workflow

If you want a smooth first experience, use this checklist:

  1. Add one audio file.
  2. Keep the default name if it already looks clean.
  3. Press Add and let Atmos load the profile.
  4. Start playback.
  5. Adjust volume and playback rate only if needed.
  6. Leave Smart Loop off at first if you want to understand the standard behavior before enabling advanced looping.

That gives you the clearest introduction to how the player behaves.

Final thoughts

Adding your first audio track is the step that turns Atmos from an interesting interface into a functional desktop environment. Once you have a real track loaded, the app's structure becomes easier to understand: the player becomes active, the library starts to matter, and the rest of the customization features begin to feel connected.

In the next tutorial, we will expand that setup by adding visual content and walking through how image and video backgrounds work inside Atmos.

Atmos Journal

More posts, product updates, and deep dives from the team.

Browse the journal