Support
Frequently asked questions
The short answers to the questions that arrive most often — licensing, delivery, and everything in between.
Support library
Answers with practical next steps
Beyond quick answers, use these field notes to prepare better briefs, releases, sessions, licences and support requests.
What should I prepare before asking for a mix?
Provide consolidated audio, tempo, key information, references, notes and a clear statement of what you want improved.
Practice: Send a versioned folder with one reference mix and one written brief.
More field notesHow should I choose a beat licence?
Choose from the rights you actually need: distribution, performance, video, term and exclusivity all matter.
Practice: Compare the licence terms against your release plan before paying.
More field notesWhat makes a master ready for distribution?
A master should be checked for clipping, unwanted noise, translation and delivery format rather than judged only by loudness.
Practice: Listen on multiple systems and verify the final files before upload.
More field notesCan I revise a service after delivery?
Revision policies work best when the original brief is specific enough to distinguish a requested change from a new production direction.
Practice: Describe the change in musical or technical terms and reference the delivered version.
More field notesWhat should artists bring to an Academy session?
Bring a real project, a clear question and the willingness to make decisions during the lesson.
Practice: Use your own material so the lesson produces an immediately useful result.
More field notesHow do I prepare for a live event?
Confirm arrival time, set length, inputs, playback requirements, monitor needs and any special cues.
Practice: Send the production sheet early and keep a backup playback plan.
More field notesHow should I credit a producer?
Credit should follow the licence or collaboration agreement and remain consistent across platforms where required.
Practice: Keep a master credits document and copy from it for every upload.
More field notesWhat is a useful release checklist?
A release checklist should cover assets, metadata, rights, distributor delivery, platform profiles, content, links and post-release measurement.
Practice: Set deadlines backward from release day and assign every task to a person.
More field notesWhat should I do when a mix sounds different everywhere?
Translation problems often come from monitoring, low-end balance, dynamics or arrangement rather than one bad plugin setting.
Practice: Compare references at matched loudness across headphones, speakers and a practical playback system.
More field notesHow do I keep a music career organized?
A lightweight operating system for contacts, releases, assets, finances and goals reduces the amount of creative energy lost to administration.
Practice: Review the system weekly and keep one source of truth for every release.
More field notes