effects

Practice Rack Effects Reference

Direct answer

Practice Rack contains 16 fixed, reorderable module types: noise gate, compressor, pitch shifter, boost, overdrive, neural amp, pedal capture, exciter, EQ, cabinet IR, chorus, phaser, tremolo, delay, reverb, and looper. Each appears once and can be enabled, bypassed, or moved. The tuner and WAV recorder are separate utilities, not rack slots.

The current catalog includes the tuner, effects chain, looper, recorder, preset system, cabinet IR, and advanced effects in Community. Professional adds synchronized playback and lifts the current three-user-preset Community limit.

Signal-order rule

Audio flows through the displayed rack order. Moving a module changes what later modules receive. There is no universally correct chain, but start with:

Gate → Compressor → Pitch/Boost/Drive → Amp → Cabinet → EQ
→ Modulation → Delay → Reverb → Looper

Match output level before comparing changes. A louder preset usually seems better even when its tone, dynamics, or noise are worse.

Goal	Move or adjust
Cleaner tracking	Gate and compressor early
Drive amp harder	Boost/overdrive before amp
Post-amp tone shaping	EQ after amp/cabinet
Dry loop with changing ambience	Looper before delay/reverb
Printed ambient loop	Looper after delay/reverb

Noise Gate

The gate uses threshold, release, hold, and range. Set threshold just above the actual idle noise, then check soft notes and long decays. Excessive threshold or range can cut attacks and sustain.

Compressor

Controls include threshold, ratio, attack, release, knee, makeup, sidechain high-pass, and mix. Begin with moderate ratio and little makeup. Compare at equal loudness and listen for flattened pick attack, pumping, or extra noise.

Pitch Shifter

Set semitone shift from -12 to +12, fine detune, and wet mix. Full wet creates a shifted line; partial mix adds an interval. Polyphonic chords and large shifts can sound less natural, so test the actual material.

Boost

Boost provides gain and output level. It is not guaranteed to be perceptually transparent because the next nonlinear stage can distort differently when driven harder. Watch both the module output and final meter.

Overdrive

Gain controls saturation, tone changes brightness, and level feeds the next module. Place it before the amp for a pedal-like drive or move it deliberately for a different result. Reduce level before switching to high gain.

Neural Amp

The amp stage offers named built-in models plus gain, tone, and level. Treat those as Practice Rack amp models; do not repeat the old claim that they are verified captures of specific physical amp heads. Pair the amp with cabinet IR unless a deliberately direct sound is required.

Pedal Capture

Pedal Capture exposes capture slots A, B, and C with gain, tone, and level. The public workflow does not document importing an arbitrary physical pedal profile, so describe these as product capture slots rather than claiming a user’s real pedal has been cloned.

Exciter

Amount, tone, and mix add upper harmonic emphasis. Use a low mix and bypass frequently. Excess can make pick noise and hiss more obvious.

Eight-band EQ

The bands are centered at 80, 160, 320, 640, 1.25k, 2.5k, 5k, and 10k Hz. Cut a specific problem before boosting broadly. Large adjacent boosts can consume headroom.

Cabinet IR

Cabinet IR provides stock cabinet choices, mix, and level, and the app has a compatible WAV IR load workflow. Place it after the amp in the common chain. When loading a file, verify the source, sample-rate handling, impulse response, latency, rights, and resulting level.

Chorus

Chorus provides sync enable, beat division, free rate, depth, and mix. Tempo sync derives movement from global BPM; free rate uses hertz. Keep mix low when timing accuracy matters.

Phaser

Controls include sync, beat division, rate, depth, feedback, stages, and mix. Higher feedback and more stages create stronger notches. Avoid judging it only on sustained chords.

Tremolo

Tremolo changes level with sync or free rate and depth. High depth can make monitoring appear to drop out. Check bypass before diagnosing the audio device.

Delay

Delay provides sync, beat division, time, feedback, and mix. In sync mode, global tempo controls the derived delay time. High feedback can build rapidly; start low and keep a stop/bypass path ready.

Reverb

Reverb provides size, dampening, mix, width, and freeze. Freeze can sustain indefinitely until released or bypassed. Lower mix helps reveal timing and muting mistakes during practice.

Looper

The looper records the signal at its rack position, then plays and destructively overdubs one buffer. It supports record, stop/play, overdub, and clear. It does not currently support undo, redo, separate layers, loop-file save, or bar quantization. See the looper workflow.

Tuner and recorder

The tuner reports pitch as a separate utility; it is not a movable “first effect.” The recorder captures final output to a selected WAV path and is not a final rack slot. Use the recorder when a loop or complete practice take must persist.

Tempo and sync boundary

Manual BPM and tap tempo are available. Chorus, phaser, tremolo, and delay can use beat divisions. Professional synchronized playback updates global BPM and position from the paired playback workflow. That capability does not change the underlying effect list.

Effects QA

Input is clean before effects.
Output starts at a safe level.
One module changes at a time.
Comparisons are level matched.
Gate preserves soft attacks and decay.
Compressor does not hide timing dynamics.
Amp and cabinet choices are described accurately.
Tempo-sync modules use the intended BPM and division.
Looper capture point is intentional.
Recorder files are reopened after saving.
Custom files have appropriate rights.

FAQ

Can I add a second instance of an effect?

No. The current rack keeps one slot for each of the 16 module types, though you can reorder and bypass them.

Is the recorder part of the chain?

No. It is a top-level final-output workflow. The looper is the utility module inside the rack.

Which effect should always be first?

None universally. Start from the recommended order, then move modules only for a stated sonic or capture reason and compare safely.

Direct answer and acceptance boundary

For “Practice Rack Effects Reference”, the short answer is: Reference the 16 fixed Practice Rack modules, their current controls, signal-order effects, safe gain staging, tempo sync, cabinet IR, looper, tuner, and recorder boundaries. Treat that statement as a result to verify, not as a promise that every input, device, project, or environment behaves identically. A complete result records the starting state, the exact action, the visible output, and the condition that proves the task is finished in Practice Rack.

Evidence-first operating procedure

Work from a small, repeatable case before changing a full project. Record the application version, operating system, input or device identity, relevant settings, and the expected result. Perform one deliberate action, preserve the first unexpected transition, and compare it with a known-good run whenever one is available. Changing several controls at once may hide which condition fixed or created the problem.

Checkpoint 1: Practice Rack Effects Reference

Treat “Practice Rack Effects Reference” as a separate acceptance gate for “Practice Rack Effects Reference”. Record its initial state before acting, then capture the first visible change and the final state. If the result differs from the page’s stated outcome, return to the last confirmed checkpoint instead of continuing with assumptions.

Checkpoint 2: Reference the 16 fixed Practice Rack modules, their current controls, signal-order effects

Verify “Reference the 16 fixed Practice Rack modules, their current controls, signal-order effects, safe gain staging, tempo sync, cabinet IR, looper, tuner, ” with the smallest representative input. Keep unrelated settings unchanged, repeat the same action once, and note whether the result is stable after reopening or reconnecting. A screenshot alone is weaker than a record that includes the input, setting, action, output, and time.

Checkpoint 3: Direct answer

For “Direct answer”, distinguish a product decision from an operating-system, hardware, source-file, permission, or workflow boundary. Confirm which layer supplied the evidence before assigning a cause. This prevents a nearby symptom from being reported as a proven root cause.

Checkpoint 4: Signal-order rule

Use “Signal-order rule” to define a pass/fail statement that another operator can repeat. Include what should be present, what must be absent, and what recovery action is safe if the check fails. Keep the original project or capture unchanged until the repaired copy has passed the same check.

Checkpoint 5: Noise Gate

When “Noise Gate” is ambiguous, compare one known-good case with one failing case under matching conditions. Mark the first meaningful difference rather than listing every later symptom. That first boundary usually produces a clearer support request and a safer next experiment.

Checkpoint 6: Compressor

Close “Compressor” only after the saved, exported, or reopened result still matches the observed state. Temporary UI feedback is useful, but durable evidence is stronger. Record any limitation that remains so the next reader does not interpret an incomplete path as a successful one.

Checkpoint 7: Pitch Shifter

Treat “Pitch Shifter” as a separate acceptance gate for “Practice Rack Effects Reference”. Record its initial state before acting, then capture the first visible change and the final state. If the result differs from the page’s stated outcome, return to the last confirmed checkpoint instead of continuing with assumptions.

Checkpoint 8: Boost

Verify “Boost” with the smallest representative input. Keep unrelated settings unchanged, repeat the same action once, and note whether the result is stable after reopening or reconnecting. A screenshot alone is weaker than a record that includes the input, setting, action, output, and time.

Checkpoint 9: Overdrive

For “Overdrive”, distinguish a product decision from an operating-system, hardware, source-file, permission, or workflow boundary. Confirm which layer supplied the evidence before assigning a cause. This prevents a nearby symptom from being reported as a proven root cause.

Checkpoint 10: Neural Amp

Use “Neural Amp” to define a pass/fail statement that another operator can repeat. Include what should be present, what must be absent, and what recovery action is safe if the check fails. Keep the original project or capture unchanged until the repaired copy has passed the same check.

Acceptance matrix

Checkpoint	Evidence to retain	Pass condition
Practice Rack Effects Reference	Initial state, one action, and resulting state	A second operator can reproduce the stated outcome
Reference the 16 fixed Practice Rack modules, their current controls, signal-order effects, safe gain staging, tempo syn	Initial state, one action, and resulting state	A second operator can reproduce the stated outcome
Direct answer	Initial state, one action, and resulting state	A second operator can reproduce the stated outcome
Signal-order rule	Initial state, one action, and resulting state	A second operator can reproduce the stated outcome
Noise Gate	Initial state, one action, and resulting state	A second operator can reproduce the stated outcome
Compressor	Initial state, one action, and resulting state	A second operator can reproduce the stated outcome

Failure isolation, recovery, and handoff

If a check fails, stop at the first failed boundary. Preserve the source, project, session, or capture; duplicate it before destructive editing; and change one variable per experiment. Repeating a broad workflow after several simultaneous changes may produce a different result without explaining why.

Separate absence of evidence from evidence of absence. A blank view may mean the wrong input, scope, filter, permission, device, time range, or project state rather than “nothing happened.” Verify the acquisition or import path before interpreting a decoder, editor, report, or export.

Before handoff, reopen the durable artifact and inspect its beginning, the decision point, and its end. Record version, platform, relevant configuration, expected behavior, observed behavior, and the smallest reproduction. Remove or redact sensitive material and confirm the recipient is authorized to receive it.

Questions and answers

What is the fastest reliable way to start?

Use the smallest representative case, write down the expected result, and change one variable. Confirm the basic path before adding filters, effects, edits, automation, or a larger source. This creates a baseline that can be compared after every later decision.

What evidence should be saved?

Keep the input identity, application version, platform, relevant settings, exact action, first unexpected transition, and final output. If the workflow creates a project, session, report, or export, close and reopen it before treating it as durable evidence.

When should the procedure be repeated?

Repeat it after an application, operating-system, driver, firmware, model, source, or workflow change that can alter the result. Preserve the earlier accepted case so the comparison uses the same acceptance boundary rather than memory.

When is the task ready for handoff?

It is ready when another authorized person can identify the input, repeat the action, see the same result, understand any remaining limitation, and open the saved artifact without relying on undocumented local state.

Related guides

Continue with the same-language pages below. They cover adjacent stages without changing the canonical owner of this topic: