Troubleshooting
Most VoiceTracker issues come down to three things: the TuneTracker Go! connection, the microphone, or the Dropbox folder. Here's how to diagnose and fix the common ones.
Red Connection Dot
The dot in the bottom-right corner is red, meaning VoiceTracker can't reach your station.
- Is the helper running at the station? Glance at the menu bar on your station Mac and look for the "G" symbol. If it isn't there, see Keeping the Helper Running on the TuneTracker Go! page.
- Did you just log in? The connection takes a second or two to establish. Wait a moment and the dot should turn green on its own.
- Has the station Mac gone to sleep? Sleep severs the helper's connection until the Mac wakes back up. Wake it and the connection re-establishes automatically.
- Did the station's internet drop? The helper auto-reconnects as soon as connectivity returns — no action needed at your end once it's back.
No Dates in the Log Panel
The right panel says "Connecting to helper…" or "No logs found," or stays empty after connecting. Look at the message in the status bar at the bottom of the screen first — it names the specific problem (see Reading the Error Messages).
- Is Station Name filled in? Open Settings and enter your station's name. With the field blank, VoiceTracker won't load logs and the panel stays on "Connecting to helper…".
- Has ClockWork generated logs? Logs appear here only after ClockWork, at the station, generates program logs with VoiceTracker registered and its folder set. Logs generated before that are not copied over; ask the station to regenerate them.
- Are you on the right station? Log out (click the TuneTracker Go! logo, top right) and back in, making sure the Station Code is the one for the station you expect.
Reading the Error Messages
When VoiceTracker can't load or save something, the status bar at the bottom of the screen now says exactly why. The part after the last colon is the cause reported by the station.
| Message contains | What it means / what to do |
| Could not read Logs folder: not found (…) | The station has no VoiceTracker/Logs folder at the path shown. Either no log has been generated since VoiceTracker was set up, or ClockWork's VoiceTracker folder setting points somewhere other than you expect. At the station, check ClockWork > Settings > VoiceTracker and regenerate a log. |
| VoiceTracker folder not set | No VoiceTracker folder has been chosen in ClockWork. At the station: ClockWork > Settings > VoiceTracker > Browse…. |
| macOS is blocking TTGO from reading this location | The folder exists but macOS won't let TuneTracker Go! read it. At the station Mac: System Settings > Privacy & Security > Full Disk Access, add TuneTracker Go! and switch it on, then quit and reopen TuneTracker Go!. |
| VoiceTracker folder issue: using last-known VoiceTracker folder… | TuneTracker Go! couldn't read ClockWork's current setting, so it is using the last folder it knew. The rest of the message says what it couldn't read. Open ClockWork on the station Mac and confirm the VoiceTracker tab shows Configured. |
| TuneTracker Go is not running | VoiceTracker can't reach the helper at the station. See Red Connection Dot. |
| Could not load bundle… / Could not save… | Same causes as above, for a single bundle or recording. The reason follows the colon. |
Microphone Not Working
VU meters show no signal or the mic dropdown is empty.
- Grant mic permission. Your browser may have blocked microphone access. Check the browser's address bar for a mic icon or go to browser Settings → Privacy → Microphone and allow the VoiceTracker site.
- Scan Inputs. Open Settings and click Scan Inputs. This requests fresh mic access and repopulates the dropdown.
- Check your system's Sound settings. On Mac, open System Settings → Sound → Input. On Windows, open Settings → System → Sound → Input. Confirm your mic is selected and the input level is up.
- Use Chrome or Brave. These browsers have the best Web Audio support and work reliably with TuneTracker Go!. Safari is not currently supported.
Recording Levels Are Too Low
- Increase Input Gain in Settings. Move the slider right while watching the VU meters.
- Enable Broadcast Processing in Settings. The compressor brings quiet passages up and the limiter prevents peaks.
- Check your mic position. USB mics work best 6–12 inches from your mouth. Too far away and the signal is weak.
VT Slot Says "Could Not Load Bundle"
- Has ClockWork generated bundles? Bundles are created by your station's ClockWork software at the moment it generates a program log. If a log was generated before VoiceTracker was set up, ask the station to regenerate it.
- Did ClockWork report a problem? After generating a log, ClockWork's status bar says how many bundles were built. If it reports that some failed (for example, because a song file couldn't be found), those slots won't have a bundle.
- Check the bundle folder. Each VT slot should have a folder named like
VTA_032526_19 (slot letter, date as MMDDYY, hour) inside the VoiceTracker Bundles folder, containing songA.mp3, songB.mp3, and bundle.json.
- Read the reason. The status bar message ends with the specific cause — see Reading the Error Messages.
Voicetrack Won't Save
- Is the connection still alive? Check the dot. If it's gone red, see Red Connection Dot above.
- Can the station Mac write to the VoiceTracks folder? Your recording is saved on the station Mac, not on your own computer. The status bar message says why a save failed.
- Check the status bar. Error messages appear in the status bar at the bottom of the screen when a save fails.
Audio Sounds Choppy or Glitchy
- Close other audio apps. Other applications using your audio interface can cause conflicts.
- Reduce browser tabs. Each open tab uses memory. Close tabs you don't need.
- Use Chrome or Brave. They have the best audio performance for web applications.
💡
When in doubt, the nuclear option: refresh the browser tab, then re-open Settings and click Scan Inputs to re-detect your mic. This resets every browser-side connection. If that still doesn't help, send a Support Wizard bundle from the station Mac (see the Support Wizard) — that's the fastest way for us to diagnose anything that survived a reset.