> For the complete documentation index, see [llms.txt](https://dc-studio.gitbook.io/dc-studio-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dc-studio.gitbook.io/dc-studio-docs/track-preparation-guide/stems-preparation-guide.md). # Stems Preparation Guide ## 🎚️ Stems Preparation for Mixing & Mastering #### Professional project preparation allows us to focus on what matters most - achieving the best possible sound, dynamics and overall quality without unnecessary technical corrections. *** ## 👋 Introduction Thank you for choosing **Deep Concept Studio**. Below you'll find our complete guide to preparing your stems for professional mixing and mastering. Following these recommendations will speed up the production process and help us achieve the best possible final result. After placing your order, you'll receive a secure upload link for your project files. Every project is carefully reviewed before work begins. If we notice any technical issues, we'll contact you and help you resolve them. *** ## 🎚️ 1. Export Settings Export every stem as an individual audio file. #### Recommended Settings | Setting | Value | | ------------- | ------------------------ | | Format | WAV | | Bit Depth | 24-bit | | Sample Rate | 44.1 kHz or 48 kHz | | Export | Full Length | | Stereo / Mono | Match the original track | ### ⚠️ Important All stems should: * ✅ Start from exactly the same point * ✅ Have identical length * ✅ Remain perfectly synchronised This ensures your project imports correctly into our mixing session. *** ## 🔊 2. Headroom & Levels Before exporting, leave enough headroom. #### Recommended * ✅ Around **-6 dB** headroom on the master bus * ✅ No clipping * ✅ No master bus distortion ### 🚫 Do NOT use on the Master Bus * ❌ Limiters * ❌ Clippers * ❌ AI Mastering * ❌ Enhancers * ❌ Mastering Chains * ❌ Automatic Loudness Presets We always mix and master from clean, unprocessed audio. *** ## 🎤 3. Vocal Export For the best possible results, export each vocal separately. #### Recommended Structure * 🎙 Lead Vocal * 🎙 Doubles * 🎙 Ad-libs * 🎙 Harmonies * 🎙 Backing Vocals ### ✨ Creative Effects If certain effects are an essential part of your sound, feel free to keep them. Examples include: * Auto-Tune * Distortion * Creative Delay * Creative Reverb * Vocal FX 💡 If you're unsure, include both the processed and the dry version. *** ## 🗂 4. File Naming Keep your file names simple and organised. ### ✅ Good Examples * Lead Vox.wav * Adlib L.wav * Kick.wav * 808.wav * Snare Top.wav * Synth Pad.wav ### ❌ Avoid Names Like * audio\_final\_v2\_last\_REAL.wav * track\_001.wav * newproject.wav Well-organised file names speed up the workflow and reduce the risk of mistakes. *** ## 🎧 5. Reference Tracks If you have a specific sonic direction in mind, include a reference. Examples: * 🎵 Spotify Link * ▶️ YouTube Link * 🎚 Rough Mix * 🎼 Demo * 🎧 Reference Track * 📝 Description of the desired sound Reference material helps us better understand: * Vocal balance * Bass character * Stereo width * Energy * Overall vibe *** ## 📦 6. File Organisation Before uploading your project: * 📁 Place all stems in one folder. * ✅ Make sure nothing is missing. * 📦 Compress everything into a ZIP or RAR archive. *** ## ☁️ 7. Project Upload After placing your order, you'll receive: * 🔗 A private upload link * 📄 File upload instructions * 📬 Further information about the production process *** ## 🔍 8. Project Review Every project is checked before work begins. We verify: * ✅ Export settings * ✅ Stems synchronisation * ✅ Clipping * ✅ Missing files * ✅ File format * ✅ Audio quality If anything needs attention, we'll contact you before starting the project. *** ## ⚠️ Common Mistakes #### ❌ Stems exported from different starting points This causes timing issues after importing. #### ❌ Limiter on the Master Bus Makes professional mixing and mastering much more difficult. #### ❌ MP3 instead of WAV MP3 reduces audio quality and should be avoided. #### ❌ Clipping Distorted audio is often impossible to restore completely. #### ❌ Poor File Naming Unclear file names slow down the workflow and increase the risk of mistakes. *** ## ❓ FAQ #### Can I send my FL Studio, Ableton Live or Logic project? ✅ Yes, but always include the exported WAV files as well. *** #### Can I leave my effects enabled? ✅ Yes - if they're an essential part of your sound. *** #### Can I send only the stereo master? ✅ Yes, if you've ordered mastering only. *** #### What if I don't know how to export my project? ✅ No problem. Contact us and we'll guide you through the process step by step. *** ## ✅ Pre-Upload Checklist Before sending your project, make sure that: ☐ All stems are exported as WAV files. ☐ Every stem starts from the beginning of the project. ☐ Nothing is clipping. ☐ The limiter is disabled. ☐ All files are clearly named. ☐ The project is compressed into ZIP or RAR. ☐ You've included a reference track (if available). *** ## 📩 Contact If you have any questions about preparing your project or the mixing and mastering process, feel free to get in touch. We're always happy to help and make sure your project is ready for the best possible result. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://dc-studio.gitbook.io/dc-studio-docs/track-preparation-guide/stems-preparation-guide.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.