Your platform
Tell us whether you're on Windows, macOS, or Linux, plus the app version, build channel, and whether the install is from Steam or a direct download if available.
Ask the community first — most setup questions get answered fast. Email us directly when you need license or account help from support staff.
Tell us whether you're on Windows, macOS, or Linux, plus the app version, build channel, and whether the install is from Steam or a direct download if available.
Include your audio interface, selected input/output device, mixer levels, operating system permissions, input gain, and anything unusual about your routing.
For drums or keys, include the MIDI device name, whether it appears in Audio settings, Kit Setup lane mapping, Keyboard Setup range, and any Reset GM or range-clear step you tried.
For tone or pitch issues, include the selected model/tone, input level, noise gate settings, whether Calibrate Gate was run, and whether built-in tones behave differently from a custom tone.
If the issue is song-specific, include the song name, source repo, official repo download state, package type, Guitar Pro format, duplicate/update state, and relevant inspection or error details.
For Browse or sync issues, include the repo URL, whether it is the official repo or an external repo, the repo status shown in Content settings, and the last retry error if visible.
For authoring issues, include whether you started from Guitar Pro, ZIP, folder, or project.json, plus the part or tool you were using.
If media is involved, include the backing track format, cover art source, background video file, optional video size if shown, and whether preview, inspection, or package export showed a warning.
If Shredit offered a recovery draft, tell us whether you resumed, discarded, or replaced it, and include any recovery or unresolved media warning you saw.
For Edition help, include the status from Settings > Edition. For direct license-key installs, include the buyer email and visible masked key suffix; for Steam installs, include the Steam status text.
Describe what you expected, what actually happened, and the steps that got you there. If custom Shredit packages, external repos, local imports, or custom tones are involved, note that those require ShredQuest Full unless the content is verified official repo content.
Open Diagnostics and include the visible system status, backend status, gameplay audio status, console text, and any exact toast or modal error text.
Steam builds manage Full through the ShredQuest Full Upgrade on Steam. Launch through Steam if Settings > Edition says Steam access could not be checked.
Direct license-key builds activate through Settings > Edition. Steam builds do not need a separate ShredQuest license key for Full.
Each direct ShredQuest Full license covers 3 active devices (support can raise this for legitimate cases). Email support with the buyer email and masked key suffix so we can review stale activations.
For direct license-key installs, install the current app, then enter your key in Settings > Edition. If the old install still counts, support can reset a stale activation.
We can resend a direct license only to the license email on file — that's what keeps a key from going to the wrong person. Email changes are handled manually and audited by support.
Direct Full and Steam Full unlock the same features when active, but one store channel doesn't automatically grant ownership in the other.
Support can reset only local direct-license identity and activation state. Your songs, tones, repo settings, progress, and normal settings stay intact.