Hey! To answer your question about using this on Claude free.
Short answer: It works on the free plan, but with some inconvenience. On the paid plan (Pro) it’s much smoother.
On the free plan you can still upload the files manually at the start of each conversation. On the Pro plan you can create a Claude Project where the files are loaded once and always available — no re-uploading every time.
What is this package?
It’s a set of 5 instruction files that turn Claude into an expert on the Archetype Petrucci X plugin. Once loaded, you can ask things like “make me a preset like the intro of Pull Me Under” or “live setup: clean, rhythm, lead on 3 footswitches” — and the AI will generate a ready-to-use preset file or MIDI configuration.
How the AI mode actually works — important to understand
The AI doesn’t hear your tone. It searches the web for information about a given song or artist’s rig, then translates what it finds into plugin parameters using the mapping instructions included in the package. It tries to reconstruct the tone based on that research.
If it finds limited information online, it falls back on the tonal patterns built into the instructions — and I’ll be honest, there aren’t that many of them yet, simply because there wasn’t enough time to build more. But that’s something anyone can supplement over time.
You can also work the other way entirely — if you already know what you want, just tell the AI directly, either by typing or using voice input: “set the lead gain to this, rhythm EQ like this, add a delay with these values.” No web search needed, just direct parameter control.
Option A — Claude Free (manual, no Project)
At the start of each conversation:
Open a new chat on claude.ai
Upload all 5 files from the package (use the attachment/paperclip button)
After uploading, write what you need
Downside: you need to do this every new conversation.
Option B — Claude Pro + Project (recommended)
Log in to claude.ai → click “New Project” in the left panel
Name it e.g. Petrucci X AI
In the “Project Knowledge” section, upload all 5 files from the package
From now on, every conversation inside that project automatically has access to the instructions — no re-uploading needed
MIDI configuration — important note
The package supports two modes:
Classic mode — the AI generates an .xml preset file, you drag and drop it into the plugin. No MIDI needed, zero configuration.
MIDIPRO mode — the AI generates a MIDI Mapping file for scenes/stomps. This requires a MIDI controller.
If you have a Quad Cortex:
You’re almost ready. QC footswitches in MIDI mode send CC#1, CC#2, CC#3 etc. — exactly what the instructions expect. You just need to enable MIDI Out in QC settings and configure the knobs/footswitches according to the CC values in the generated file.
If you have a different MIDI device (MIDI footswitch, keyboard, pedalboard etc.):
Check your device’s manual to find which CC numbers each button/pedal sends, then tell the AI when requesting a setup — it will adjust the mapping to your hardware.
One more thing about MIDI: the plugin has over 300 mappable parameters. Asking the AI to map everything at once — especially in complex setups like 4 scenes plus stomps — can overload it and produce errors. Keep it focused: only request mappings for the parameters you actually need to change. Less is more here.
How to talk to the AI in the project?
In your own language — you can write in Arabic, English, or anything else. The AI understands requests like:
“Make me a preset for the intro of Another Day”
“Live setup: 3 scenes — clean, crunch, lead solo”
“MIDIPRO — PRO MIDI SETUP for Pull Me Under”
If anything is unclear, just ask inside the project — the AI will explain every step.
Hope this helps! If you have a different MIDI controller than QC, let us know which one and we can help with the configuration 
