Ask what the engineer actually needs.
Before exporting, confirm the delivery format, sample rate, bit depth, preferred track organization, and whether the engineer wants individual tracks or grouped stems. Different projects call for different handoffs. Do not rely on a generic checklist when the person doing the work has supplied specific instructions.
Also confirm the service itself: who is mixing, whether mastering is included, the number of revisions, turnaround, and the final files you will receive. This site has not set a mixing package or price, and it does not claim Helluva personally performs every mix.
Distinguish individual tracks from grouped stems.
Describe what you are sending rather than relying only on the word “stems.” An individual lead vocal, its doubles, and separate ad-libs give a different level of control from one combined vocal file. Similarly, a grouped drum export is different from separate kick, snare, and percussion tracks. Confirm the level of separation the engineer requests.
Do not promise to deliver separated files you do not have. An instrumental purchased as a stereo file does not automatically come with its underlying production tracks. Check the beat’s actual license and file entitlements before arranging the mix.
Make the files easy to place.
Ask how files should be aligned and exported so that they return to the correct positions in the receiving session. Use your production software’s documentation for the actual export settings. Keep a copy of the original session, and test the exported files rather than assuming the export worked.
Give files names that identify their musical role and version. For example, a lead vocal, a left double, and a hook harmony should be distinguishable without opening every file. Avoid leaving several different takes named only “final.”
Include a rough mix and explain it.
A rough mix helps communicate the direction, even when it is not the finished sound. Tell the engineer which parts of that rough mix matter to you and which are temporary. A production effect that defines the idea should not be confused with a placeholder added only to make a demo listenable.
Confirm whether the engineer wants processed tracks, unprocessed tracks, or both. Do not remove a creative effect or commit a technical process without considering the agreed workflow. Label any alternatives so they cannot be mistaken for simultaneous parts.
Keep feedback specific.
Use timestamps and a description of what you hear: “the hook lead feels behind the instrumental at 0:42” is clearer than “make it better.” Explain the feeling you want without prescribing a technical fix you have not tested. Separate essential changes from optional experiments.
Keep notes for one version together. When a new mix arrives, identify it clearly before giving feedback. This prevents a conversation about one export from being applied to another.
Choose the correct upload workflow.
The private mixing request workflow accepts up to 12 audio files, with a 64 MiB limit per file. Submit the project request first and follow its private access instructions. A successful upload does not confirm that paid work has started. For larger projects, confirm another transfer method rather than merging parts to fit the limit.
Protect the originals.
The separate My Studio mix-preparation tool stores files locally in the browser, unlike the private request workflow above. Its limits are 50 MB per file and 250 MB per project. Saving a file there does not upload it, send it to an engineer, or create a production backup.
Keep the original project and exports outside the browser. Download any unique rough takes or notes before clearing site data. Arrange the actual transfer method with the engineer once the project scope is confirmed.
For the service overview, return to mixing and mastering preparation. For rights questions involving an instrumental, review the proposed licensing overview and the agreement that applies to that music.