Slope ↗

A one-sided slew processor that slows rising changes while allowing falling changes to pass more directly.

What it does #

Slope ↗ reshapes only upward movement. When the input rises above the current output, the output approaches it according to Time; when the input falls, the module follows that decrease without applying the same upward slew.

Controls and ports #

Control	Label	Official description
time	Time	Slew time for rising signal changes

Practical uses #

• Add attack or portamento only to rising control changes while preserving fast downward resets.
• Turn gates or steps into rising ramps with sharp falls.
• Place it after random or sequenced modulation to soften upward jumps without blurring downward accents.

Things to know #

• This is not an envelope follower: it processes the signal value itself rather than first extracting amplitude.
• Only the rising direction receives the configured slew behavior.
• Successive rising targets can change the destination before the previous ramp has finished.
• The exact response may be rate-limited or exponential; the installed description alone does not establish that distinction.

Technical details #

No Nitro implementation has been confirmed for this visible module. The behavior is described conservatively from module metadata and editorial research.

The behavioral contract is a one-sided smoother: if input > state, move state toward input according to Time; otherwise pass or rapidly follow the falling input. The atlas contains a generic symmetric linear slew helper using state = clamp(input, state-step, state+step), but there is no evidence that Slope ↗ is this helper with one branch bypassed. Exact curve, time normalization, initialization, stereo policy, and zero-time behavior require measurement.

Open questions #

• Distinguish linear rate limiting from exponential smoothing with several step sizes and Time values.
• Measure falling pass-through, changing targets mid-ramp, negative values, zero crossing, initialization, and stereo behavior.
• Determine whether Time specifies full-scale travel, a time constant, or a settling threshold.

Version and sources #

Checked against Bitwig Studio 6.0.6. This page combines Bitwig's module metadata, the existing Grid course and guides, and Nitro analysis where the mapping is strong enough to support a technical statement.

Related material #

• Grid Modules course reference

Return to Bitwig Grid Modules or the Grid Modules course lesson.