Custom MPC Expansion Application

Build your private MPC drum system.

This creative brief gives me the sonic, programming and compatibility details needed to build a complete MPC Expansion around your workflow. Be specific about the drum identity, pad behaviour and creative result you want.

Personally reviewed Native MPC delivery Invoice sent after review Limited monthly availability
MPC Expansion brief progress Choose your expansion
Step 1 of 6 · 0% complete
View your live MPC brief
PackageNot selected
MPCNot selected
WorkflowNot selected
WorldsNot selected
Kit structureNot selected
Step 01

Choose your expansion and setup.

Select the plan, confirm your MPC model and explain how you work. Compatibility is reviewed before the invoice is sent.

Package *

Choose a package to continue.

What will you use this expansion for? *

Choose the main purpose of the expansion.

Choose the main device or software environment where the expansion must work.

Choose an option before continuing.

Compatibility for legacy or specialist models must be reviewed before payment. A manual format may be required instead of standard XPN delivery.

Enter the exact model.

Hardware operating system *

Choose the hardware operating system or mark it as not applicable.

Desktop MPC application *

Choose the MPC desktop application you use.

Main workflow *

Choose your main MPC workflow.

Included delivery Every standard project includes the XPN installer, a standalone expansion folder, an organised source WAV library, browser identity and an installation guide. Exact compatibility is confirmed before payment.
Step 02

Define the drum identity.

Choose only the directions that genuinely belong together. A focused brief creates a stronger and more recognisable expansion.

Production worlds *0 of 3 selected

Select between one and three production worlds.

Main drum source *

Choose the main drum source.

Era *0 of 2 selected

Select one or two eras.

Describe the era you want.

Overall drum character *0 of 4 selected

Select between one and four drum characteristics.

Overall energy *

Choose the overall energy.

Describe impact, room, movement, machines, records and the physical feeling you imagine. Concrete details are more useful than a long list of names.

Add enough detail so the direction is clear.

Step 03

Build the kit architecture.

Define how the kits should relate to each other, which drum elements matter most and how the programs should feel when you browse and play them.

Kit family structure *

Choose a kit family structure.

Consistency versus variety *

Choose a consistency and variety direction.

Priority drum elements *0 of 6 selected

Choose the elements that deserve the most attention. Detailed questions appear only for the categories you select.

Select between one and six priority elements.

Pad layout philosophy *

Choose a pad layout philosophy.

Can selected sounds appear in more than one kit when tuned, layered or processed differently? *

Choose a sound reuse preference.

How kit count worksKit count refers to finished, mapped and playable programs. It does not mean that every sound can only appear in one program. Strong sounds may be tuned, layered or processed across related kits when that creates a more coherent expansion.
Tuning behaviour *

Choose a tuning approach.

Step 04

Program the MPC behaviour.

Define how the programs should respond, how much character should be built in and how the included MIDI content should behave.

Pad response *

Choose a pad response direction.

Program processing *

Choose a program processing direction.

Programming priorities *0 of 3 selected

Choose the programming behaviours that matter most. The final settings are adapted to each kit rather than forced identically across the expansion.

Select between one and three programming priorities.

Filter and FX direction *0 of 3 selected

Select between one and three FX directions.

Optional additions0 of 4 selected

Optional. Selected additions are reviewed and quoted separately before the invoice is sent.

Choose no more than four additions.

Optional. Add any technical behaviour that is important to your workflow.

Step 05

Show me the expansion you hear.

References explain impact, groove, texture and processing. Every sound and program will be created from scratch. Protected audio will not be copied or extracted.

Reference tracks *

Add three public links. Include a timestamp, choose the main focus and explain exactly what matters in each reference.

Reference 01Required

Add a valid public reference link.

Add the relevant timestamp.

Explain what matters in this reference.

Reference 02Required

Add a valid public reference link.

Add the relevant timestamp.

Explain what matters in this reference.

Reference 03Required

Add a valid public reference link.

Add the relevant timestamp.

Explain what matters in this reference.

Google Drive and Dropbox links are accepted. Make sure private files are set so anyone with the link can listen.

Optional, but very useful when you already have an established sound.

How should the references guide the result? *

Choose how the references should guide the expansion.

Optional. Use this to point toward a quality, workflow or broad character you already like.

Would you like your own legally cleared sounds included? *

Choose whether you want to provide your own sounds.

Optional at this stage. You may send the files after the brief is approved.

Choose how the files should be used.

Confirm that you have the rights to every supplied file.

Add enough detail so the direction is clear.

Add enough detail so the direction is clear.

Add enough detail so the direction is clear.

Contact details

Enter your name.

Enter a valid email address.

Step 06

Review your MPC Expansion brief.

Check the complete setup, creative direction and programming choices before submitting. You can return to any previous section without losing your answers.

Your information is sent through Shopify’s native contact form and delivered to the sender email configured for the store.

Progress is saved on this device