How to Request Edits From a DJ Record Pool When a Track Is Missing
To request an edit from a DJ record pool, send a single clear message that names the exact track, the version you want (clean intro edit, short edit, acappella, transition edit, specific BPM or key), and when your gig is. Most pools take requests through a form, a Discord channel, or a support email, and the more precise you are, the faster it gets cut. Vague asks like "can you get this song" sit at the bottom of the queue. Specific asks like "clean short edit of X at 124, 8-bar intro" get made.
Every working DJ hits this wall. You build a set, you search the pool, and the one record that ties the whole thing together is either missing, only available in the dirty album version, or has a cold 4-second intro that gives you nothing to mix into. Before you panic or go hunting on sketchy download sites, understand how edit requests actually work on the back end and how to write one that jumps the line.
What a record pool can and cannot edit for you
Record pools are not a magic button. Editors work with the audio they can legally source, and they cut versions that serve a broad base of DJs, not one-off custom favors. Knowing the difference saves everyone time.
Realistic to request:
- A clean edit of a track that only exists as a dirty version in the pool
- A short edit or radio edit of a long club mix
- An intro edit with a mixable 8, 16, or 32 bar count-in
- An acappella or instrumental if the stems or a usable a cappella exist
- A transition edit (half-time outro, hype re-edit, redrum) of a song that is already trending
- A BPM-shifted version to bridge genres (a 100 BPM pop song bumped to 124 for a house set)
Unrealistic to request:
- Brand new leaks before the label services them
- A bespoke mashup of two specific songs cut just for your wedding
- Pristine stems of a track that was never released with stems
- Bootleg remixes the pool has no rights to host
If your ask lives in the first list, write it up properly. If it lives in the second, you are better off building it yourself or sourcing elsewhere.
How to request edits from a DJ record pool the right way
The editors reading your request are DJs too. They scan requests fast and prioritize the ones they can action without going back and forth. Give them everything in one message.
Include these details every single time
| Field | Example | Why it matters |
|---|---|---|
| Exact artist and title | Fred again.. feat. Baby Keem - leavemealone | Removes guesswork and misspellings that stall the search |
| Version you want | Clean short edit, 16-bar intro | Tells the editor exactly what to cut |
| Target BPM | 128 | Flags whether a tempo edit is part of the ask |
| Target key (if it matters) | 8A / A minor | Useful for transition or pitch edits |
| Reference link | YouTube or Spotify URL | Confirms the exact recording, not a live or sped-up version |
| Deadline | Needed by Friday for a club set | Lets staff triage genuinely urgent asks |
Write it like a text, not an essay
One tight paragraph beats a wall of backstory. Compare these two:
Weak: "Hey, I really need this one song that is so hot right now, everyone is playing it, can you add it please?"
Strong: "Requesting a clean short edit of [Artist - Title], around 126 BPM, 16-bar intro if possible. Reference: [link]. Playing it Saturday. Thanks."
The second one can be fulfilled in the time it takes to read it. The first one triggers three follow-up questions before anyone can even start.
Use the right channel
Pools route requests differently. Some run a dedicated request form, some use a Discord or Telegram community where staff and other DJs chime in, some want an email to support. Find the official channel before you blast a DM to a random account. Posting in the correct place means your request lands in the queue instead of a personal inbox that gets checked once a week. On GreenHitz, pulling clean, DJ-ready versions is the whole point of the library, so when something is missing the request path is built in rather than an afterthought.
Set realistic expectations on turnaround
A clean edit of an existing dirty track can be fast, sometimes same day. A fresh intro edit or a tempo-shift takes longer because someone has to actually cut and quality-check it. A full transition edit or redrum of a brand new record might wait until the song is clearly worth the labor.
Rule of thumb: if your gig is tonight, do not count on a request landing in time. Build in a buffer. Request edits for next week's set this week, and request your "nice to have" versions well before they become "need it now" versions. Treat the pool like a supply chain, not an emergency room.
What to do while you wait for the edit
Never let a pending request hold your set hostage. You have tools to bridge the gap yourself, and half the time you will not even need the official edit once you do.
Cut a quick edit yourself
If the only problem is a short or messy intro, you can fix it in minutes. Loop rolling the intro to extend a short record pool edit buys you the mix time you need without any file editing at all. For a cleaner fix, drop a loop at the first downbeat in Serato or Rekordbox and let it ride for an extra 8 or 16 bars, then save it as your own cue-mapped version.
Build the transition with technique instead
A missing "transition edit" is often just a mixing problem in disguise. Learn to use an echo out to end a track cleanly and you can exit almost any record without a custom outro. Same goes for busy intros: a high pass filter smooths transitions between two busy tracks so you do not need a stripped-down edit to make the blend work.
Source the acappella and build your own layer
If you requested an acappella to layer over an instrumental, you can often get most of the way there with what is already in the pool. Layering acappellas over instrumentals is a core skill, and nailing it means fewer custom requests in the first place.
Request etiquette that gets you taken seriously
The DJs who get their requests filled fast are the ones who make the editor's job easy and never burn goodwill.
- Do not duplicate. Search the pool thoroughly first, including alternate spellings and remixer names. Half of all "missing" tracks are already there under a different tag.
- One request per message. Dumping fifteen songs in one post guarantees most get ignored. Prioritize the two or three you genuinely need.
- Do not spam reminders. One polite follow-up after a reasonable window is fine. Daily "any update?" messages move you down, not up.
- Say thanks and report back. When an edit drops and crushes on the floor, tell them. Editors cut more of what they know is landing.
- Give honest feedback. If the intro edit came in at the wrong bar count, say so clearly and specifically so they can fix it fast.
Keep your library clean so you know what is actually missing
Half of all "this track is missing" requests are really "my library is a mess." If your tags are inconsistent, you will search for a song that is already downloaded and swear the pool never had it. Get your house in order first. Cleaning up ID3 tags on your record pool downloads keeps everything searchable, and setting up Rekordbox to import and organize downloads means new edits land where you expect them. Do this and you will request only what is genuinely absent, which keeps your credibility high with the people cutting the edits.
For more workflow guides on getting the most out of your pool, browse the full library of DJ guides, and if you need a deep catalog of clean, DJ-ready edits in the first place, that is exactly what GreenHitz is built for.
Frequently Asked Questions
How long does a record pool take to make a custom edit?
It depends on the ask. A clean version of an existing dirty track can arrive the same day, while a fresh intro edit, tempo change, or full transition edit usually takes a few days because someone has to cut and check it. Request anything time-sensitive at least a week before the gig to be safe.
Can I request a specific BPM or key for an edit?
Yes, and you should state it clearly. If you need a pop record bumped from 100 to 124 for a house set, say the exact target BPM. If key matters for harmonic mixing, list the Camelot or musical key. The more precise you are, the less back-and-forth before the edit gets made.
What if the record pool will not make the edit I requested?
Pools decline requests for tracks they cannot legally source, unreleased leaks, or one-off custom mashups. If yours gets turned down, build it yourself: loop the intro, use filters and echo outs for transitions, or source the acappella and layer it manually. Technique covers most gaps a custom edit would have filled.
Is it rude to request lots of tracks from a record pool?
Flooding staff with a long list in one message is counterproductive, not rude exactly, but it gets most items ignored. Send one or two priority requests at a time with full details. Space them out, follow up once if needed, and report back when an edit lands well.
Should I request an edit or just make my own?
If the problem is a short intro or a quick blend, make your own with loops and cue points, it is faster than waiting. Request an official edit when you need a clean version, proper stems, or a polished re-edit that would take real production work to match.
Where do I send a record pool edit request?
Use the pool's official channel: a request form, a Discord or Telegram community, or the support email. Avoid DMing random staff accounts, since those messages slip through the cracks. Posting in the correct place puts your request in the actual queue where editors review and action it.
