GP-33's log and the diagnostic report
What it is
GP-33 keeps a small log of what it's doing, on your Mac, so that when something goes wrong there's a record to read instead of a guess. It's on all the time. Nothing needs switching on, and nothing about it phones home. The only way any of it leaves your Mac is when you choose to export a diagnostic report and send it to us.
What the log records
Plain lines, each with a time. Read one and you know what the app was doing at that moment.
- Launches and quits. When the app started, and which build.
- Your library. Files imported and where they were filed, tags read, and the moments a tag couldn't be read and the app fell back to "Unknown". These lines carry artist, album, and file names, because that's what the app was working on.
- Playback. Play, pause, the end of a song, a stall, and a heartbeat while a song plays, each naming the track and the state of the audio engine at that instant, including how much signal is leaving the engine on its way to your speakers. This is how "the meters move but there's no sound" becomes a line we can read.
- Your sound output. Which output device your Mac is using (speakers, an interface, headphones), every time it changes, whether your Mac has it muted, whether anything is playing through it, and where GP-33's own sound is going at that moment. We read only our own audio process, never what any other app on your Mac is doing.
- Controls. Shuffle, EQ, volume, crossfade, Sound Check, the meter style, the visualizer, and each press of Test sound. State, so a report opens with a snapshot of how the app was set.
- The family bridge. When GP-33 tells Groovemark where to find it, so a saved album lands in your library.
- Errors. Anything the app's page trips over, with enough of a trace to fix it.
- Requests. The app's own server answering its own window, including the audio files it streamed.
The log is capped. When it fills, the oldest half is dropped and it keeps going.
What it never records
Your audio. Your artwork. Anything typed anywhere else on your Mac. What other apps are playing or doing. Nothing is sent anywhere on its own.
The diagnostic report
Settings, then Export diagnostic report. GP-33 zips the log together with one short page of facts about the setup: the app's version and mode, the macOS version, where your library lives, and the current output device. You pick where to save it, and you decide whether to send it. It contains the file and folder names above, including your library's path, so treat it like any file that names what's on your Mac.
Test sound
Next to Export diagnostic report sits Test sound. Press it and GP-33 plays two short beeps, a higher one and then a lower one. The first goes through the player's own audio engine. The second goes through a fresh engine opened just for the beep and closed again. Nothing about the song you're playing changes.
Which beeps you hear tells us where sound is getting lost. If the second beep plays and the first doesn't, the player's engine is what needs a reset. If neither plays, the trouble is past the app, in the Mac or the device. So when you send a report about silence, tell us what you heard.
When to send one
When something looks wrong that a relaunch fixes: silence with the meters moving, a song that won't start, an import that didn't land. Export the report while it's still wrong, press Test sound and note what you heard, then relaunch. The log after a relaunch is a log of a healthy app.
Still need help? hit us up.