Stable Diffusion Parseq

• What is this?
• What's new?
• Getting started
• Examples
• Features
  • Keyframed parameter values with scriptable interpolation
  • Interpolation expressions
    • Operators
    • Context variables
    • Constants
    • Units
    • Unit conversion functions
    • Oscillator functions
    • Transition functions
    • Noise functions
    • Maths functions
    • Javascript maths functions
    • Info text matching functions
    • Prompt manipulation functions
  • Working with time & beats (audio synchronisation)
    • Beats per minute and frames per second
    • Locking keyframes to beats or seconds
    • Interval keyframe creation
    • Keyframe labelling
    • Reference audio
    • Automatically generating keyframes from audio events
    • Sync'ing to pitch and amplitude using time series
    • Legacy Audio Analyser
  • Time series for arbtrary data sequences
  • Camera movement preview
  • Deforum integration features
    • Keyframable parameters
  • Prompt manipulation
  • Using multiple prompts
  • Subseed control for seed travelling
  • Delta values (aka absolute vs relative motion parameters)
• Working with large number of frames (performance tips)
• Development & running locally
  • Deployment
• Credits and support

What is this?

You can jump straight into Parseq here: https://sd-parseq.web.app/ .

To provide some context:

• Stable Diffusion is an AI image generation tool.
• Deforum is a notebook-based UI for Stable Diffusion that is geared towards creating videos.
• AUTOMATIC1111/stable-diffusion-webui is a Web UI for Stable Diffusion (but not for Deforum).
• The Deforum extension for Automatic1111 is an extention to the Automatic1111 Web UI that integrates the functionality of the Deforum notebook.

Parseq (this tool) is a parameter sequencer for the Deforum extension for Automatic1111. You can use it to generate animations with tight control and flexible interpolation over many Stable Diffusion parameters (such as seed, scale, prompt weights, noise, image strength...), as well as input processing parameter (such as zoom, pan, 3D rotation...).

For now, Parseq is almost entirely front-end and stores all state in browser local storage by default. All processing, including audio processing, is done in the browser. Signed-in users can optionally upload their work from the UI for easier sharing.

Using Parseq, you can:

Sequence, evolve and blend prompts with scriptable logic right in the prompt text	Control how parameters and prompt weights change over time, both visually and with an advanced expression language	Automatically detect audio events, and use them to influence your video.
Extract pitch and amplitude data from audio, and import any raw timeseries data, for use in your expressions	Preview 3D motion and final prompts before kicking off your diffusion	Simple integration with the A1111 Deforum extension - just copy one link!

What's new?

See the Parseq change log on the project wiki.

Getting started

Pre-reqs

• Start by ensuring you have a working installation of Automatic1111's Stable Diffusion UI
• Next, install the Deforum extension. – You should now see a Parseq section right at the bottom for the Init tab under the Deforum extension (click to expand it).

Ramping up

The best way to get your head around Parseq's capabilities and core concepts is to watch the following tutorials:

Part 1	Part 2	Part 3

Usage

In summary, there are 2 steps to perform:

Step 1: Create your parameter manifest

• Go to https://sd-parseq.web.app/ (or run the UI yourself from this repo with npm start)
• Edit the table at the top to specify your keyframes and parameter values at those keyframes. See below for more information about what you can do here.
• Copy the contents of the "Output" textbox at the bottom. If you are signed in (via the button at the top right), you can choose to upload the output instead, and then copy the resulting URL. All subsequent changes will be pushed to the same URL, so you won't need to copy & paste again.

Step 2: Generate the video

• Head to the SD web UI go to the Deforum tab and then the Init tab.
• Paste the JSON or URL you copied in step 1 into the Parseq section at the bottom of the page.
• Fiddle with any other Deforum / Stable Diffusion settings you want to tweak. Rember in particular to check the animation mode, the FPS and the total number of frames to make sure they match Parseq.
• Click generate.

Examples

Here are some examples showing what can do. Most of these were generated at 20fps then smoothed to 60fps with ffmpeg minterpolate or FILM. See the also the Parseq Example Library for a range of simple examples and all required settings to recreate them.

Features

Keyframed parameter values with scriptable interpolation

Parseq's main feature is advanced control over parameter values, using keyframing with interesting interpolation mechanisms.

The keyframe grid is the central UI concept in Parseq. Each row in the grid represents a keyframe. Each parameter has a pair of columns: the first takes an explicit value for that field, and the second takes an interpolation formula, which defines how the value will "travel" to the next keyframe's value. If no interpolation formula is specified on a given keyframe, the formula from the previous keyframe continues to be used. The default interpolation algorithm is linear interpolation.

Below the grid, a graph allows you to see the result of the interpolation (and edit keyframe values by dragging nodes):

The interpolation formula can be an arbitrarily complex mathematical expression, and can use a range of built-in functions and values, including oscillators and helpers to synchronise them to timestamps or beats:

Interpolation expressions

Interpolation expressions define how the value for a given field should be computed at each frame. Expressions can return numbers or strings. String literals must be enclosed in double quotes ("").

Here are the operators, values, constants and functions you can use in Parseq expressions.

Function live documentation

💡 You can visualise and play with all interpolation logic using Parseq's live documentation. 💡

Operators

operator	description	example
<expr1> + <expr2>	Add two expressions. Also acts as string concatenation if either expression is a string (with the same type conversion semantics as Javascript string concatenation).	Make the seed increase by 0.25 on every frame (Parseq uses fractional seeds to infuence the subseed strength):
<expr1> - <expr2>	Subtract two expressions.
<expr1> * <expr2>	Multiply two expressions.
<expr1> / <expr2>	Divide two expressions.
<expr1> % <expr2>	Modulus	Reset the seed every 4 beats:
<expr1> != <expr2>	1 if expressions are not equal, 0 otherwise.
<expr1> == <expr2>	1 if expressions are equal, 0 otherwise.
<expr1> < <expr2>	1 if less than , 0 otherwise.
<expr1> <= <expr2>	1 if less than or equals , 0 otherwise.
<expr1> >= <expr2>	1 if greater than , 0 otherwise.
<expr1> < <expr2>	1 if greater than or equals , 0 otherwise.
<expr1> and <expr2>	1 if and are non-zero, 0 otherwise.
<expr1> or <expr2>	1 if or are non-zero, 0 otherwise.
if <cond> <consequent> else <alt>	if cond evaluates to any value other than 0, return consequent, else return alt. cond, consequent and alt are all arbitrary expressions.	Use a square wave which alternates between 1 and -1 with a period of 10 frames to alternatively render the step and cubic spline interpolations:
<expr1> : <expr2>	Syntactic sugar for easily creating strings of the format (<term>:<weight>). For example, putting the following in your prompt ${"cat":prompt_weight_1} will render to ${(cat:0.5)} where 0.5 is the value of prompt_weight_1 for that frame. expr1 must return a string and expr2 a number.

Context variables

Your expression runs in a context that provides access to a number of useful variables:

value	description	examples
L	(default) The value at this frame assuming linear interpolation betwen the previous and next keyframed value
S	The value at this frame assuming step interpolation. This is equivalent to active_keyframe_value, i.e. the value last seen in the value column.
C	The value at this frame assuming cubic spline over all keyframed values.
P	As above, but using polynomial interp. Very similar to Cubic spline.
f	The current frame number. Not very useful alone, but can be used to reference the overall video position in your interpolation algoritm. For example, add it to your seed value to increment the seed on every frame.
k	The number of frames elapsed since the active keyframe started for this field
b	The current position in beats. Depends on BPM and FPS.
s	The current position in seconds. Depends on FPS.
active_keyframe	The frame number of the currently active keyframe for this field
next_keyframe	The frame number of the next keyframe for this field
active_keyframe_value	The value set at the currently active keyframe for this field. Equivalent to S (step interpolation).
next_keyframe_value	The value set at the next keyframe for this field
prev_computed_value	The value calculated at the previous frame for this field, or 0 for the first frame.
last_frame	The value set in the "Final frame" input field. Similar to the "max_f" variable in deforum.

Constants

Units

Units can be appended to numerical constants to convert from frame to beats/seconds using the document's FPS and BPM. This is particularly useful when specifying the period of an oscillator (or anything else representing a time period).

Unit conversion functions

Use these functions to convert between frames, beats and seconds:

Oscillator functions

All functions can be called either with unnamed args (e.g. sin(10,2)) or named args (e.g. sin(period=10, amplitude=2)). Most arguments have long and short names (e.g. sin(p=10, a=2)).

In the examples below, note how the oscillators' amplitude is set to the linearly interpolated value of the field (L), from its initial value of 1 on frame 0, to value 0 on frame 120. This is why the amplitude of the oscillator decreases over time.

function	description	example
sin()	Sine wave oscillator. See below for arguments (only period is required).
sq()	Square wave oscillator
tri()	Triangle wave oscillator.
saw()	Sawtooth wave oscillator.
pulse()	Pulse wave oscillator.

Oscillator arguments:

• Period p required: The period of the oscillation. By default the unit is frames, but you can specify seconds or beats by appending the appropriate suffix (e.g. sin(p=4b) or sin(p=5s)).
• Amplitude a (default: 1): The amplitude of the oscillation. sin(p=4b, a=2) is equivalent to sin(p=4b)*2.
• Phase shift ps (default: 0): The x-axis offset of the oscillation, i.e. how much to subtract from the frame number to get the frame's oscillation x position. A useful value is -active_keyframe, which will make the period start from the keyframe position. See below for an illustration.
• Centre c (default: 0): The y-axis offset of the oscillation. sin(p=4b, c=2) is equivalent to sin(p=4b)+2
• Limit li (default: 0): If >0, limits the number of periods repeated
• Pulse width pw (default: 5): pulse() function only The pulse width.

Examples:

	Defining a sine wave with linearly increasing amplitude using sin(p=2b, a=L), meaning the amplitude is the linear interpolation of the keyframe values.
	Limiting to 1 period at each keyframe with li=1. Notice how the phase is maintained relative to the full sinewave, so the period does not start with the keyframe.
	By setting the phase shift to the negative offset of the active keyframe with ps=-active_keyframe, we can ensure the period starts at the keyframe point.

Transition functions

function	description	example
`bez()`	Bezier curve between previous and next keyframe. All arguments are optional: `x1`, `y1`, `x2`, `y2`: control point co-ordinates. Set these explicitly if you don't like any of the pre-defined curves you can set with `c` as described below. https://cubic-bezier.com/ to establish the values . Defaults to `bez(0.5,0,0.5,1)` if none specified. `from` or `start`: Starting y position. Ignore the previous keyframe value and start from this value instead. `to` or `end`: Ending y position. Ignore the next keyframe value and curve towards this value instead. `in`: duration. Ignore the duration between the previous and next keyframe, and draw the curve over this number of frames instead. `os`: offset. Ignore how far along the curve the current value is, and use this value instead, where 0 is the start of the curve and 1 is the end of the curve. Curve type `c`: a string defining the shape of the curve, e.g. `bez(c="easeOut")`. Supports all values on https://easings.net/ except elastic an bounce, plus some convenience aliases. See [the code for the full list](https://github.com/rewbs/sd-parseq/blob/master/src/parseq-lang/parseq-lang-ast.ts#LL948C18-L948C18). Better documentation with pretty pictures TODO. :)
`slide()`	Linear slide over a fixed time period. Requires at least one of `to` or `from` parameters (frame value will be used if missing), and `in` parameter defines how long the slide should last. Optional value `os` behaves like offset for `bez()`. See image for 3 examples.

Noise functions

function	description	example
rand()	Returns a random number between min and max (default 0 and 1), using seed s (default current time using high precison timer), holding that value for 'h' frames (default 1). See the image for 3 examples. prompt_weight_1 changes value between 0 and 1 on every frame and will get a new set of values on every render. prompt_weight_2 gets a new random value between 1 and 2 every 40 frames, and will also get a new set of values on every render. prompt_weight_3 gets a new random value between 2 and 3 every beat, and will use the same series of values on every render.
smrand()	Smooth random function (simplex noise). Arguments are smoothing factor sm (higher values mean smoother noise, default 10), min (default 0), max (default 1) and seed s (default current time using high precison timer). Because simplex is inherently a >2D noise generation algorithm, there is also a y parameter (default 0) you can increase by small increments (e.g. 0.05) to slightly alter the overall noise pattern.
perlin()	Similar to smrand() but using perlin algorithm instead of simplex.
vibe()	Plots points at random intervals and draws bezier curves between them. Takes min and max to define the value range (defaults 0, 1), pmin and pmax to define the range of frame-count intervals between points (defaults: 1, 20) or alternatively p which overrides pmin and pmax to the same value, rand seed s (default current time using high precison timer), and c or x1,y1,x2,y2 to define the shape of the bezier curve (see bez() above).

Maths functions

function	description	example
min()	Return the minimum of 2 argument
max()	Return the maximum of 2 argument
abs()	Return the asolute value of the argument
round()	Return the rounded value of the argument. Second argument specifies precision (default: 0).
floor()	Return the value of the argument rounded down. Second argument specifies precision (default: 0).
ceil()	Return the value of the argument rounded up. Second argument specifies precision (default: 0).

Javascript maths functions

A range of methods from the Javascript Math object are exposed as follows, with a _ prefix.

Note that unlike the sin() oscillator above, these functions are not oscillators: they are simple functions.

Info text matching functions

All keyframes have an optional "info" field which can hold an arbitrary string. You can query these from your expressions. For example, you can use functions to check whether the text of the current keyframe matches a regex, or to count how many past keyframes contained a given substring, or look forwards to when the next keyframe with a given string will occur.

function	description	example
info_match()	Takes a regular expression as an argument. Returns 1 if the info label of the current active kefframe matches the regex, 0 otherwise.
info_match_count()	Takes a regular expression as an argument. Returns the number of keyframes that have info labels that matched the regex so far.
info_match_last()	Takes a regular expression as an argument. Returns the frame number of the previous keyframe that matched the regex, the current frame number if it is a matching keyframe, or -1 if none.
info_match_next()	Takes a regular expression as an argument. Returns the frame number of the next keyframe that matches the regex, or -1 if none.

Prompt manipulation functions

Prompts can include any Parseq expression. For example, the following is a valid prompt using a conditional, the prompt weight operator : and string concatenation +:

A painting of 
${
 if (f<10)
   "a cat":prompt_weight_1
 else
   "a dog":prompt_weight_2 + " with floppy ears"
}
, highly detailed

On frames less than 10, it will produce a rendered prompt like A painting of (a cat:0.45), highly detailed, and on frames 10 and above, it will yield A painting of (a dog:0.45) with floppy ears, highly detailed.

Note that if you want to ensure something does not appear in your generated image, giving it a negative weight in the positive prompt is generally not sufficient: you need to put the term in the negative prompt. Therefore, if you want something to appear then disappear, it becomes necessary to "move" it between the positive and negative prompts. This can be done with conditionals, but the following functions make it easier.

See also the : operator above.

Working with time & beats (audio synchronisation)

Parseq has a range of features to help you create animations with precisely-timed parameter fluctuations, for example for music synchronisation.

Beats per minute and frames per second

Parseq allows you to specify Frames per second (FPS) and beats per minute (BPM) which are used to map frame numbers to time and beat offsets. For example, if you set FPS to 10 and BPM to 120, a tooltip when you hover over frame 40 (in the grid or the graph) will show that this frame will occur 4 seconds or 8 beats into the video.

Furthermore, your interpolation formulae can reference beats and seconds by using the b and s suffixes on numbers. For example, here we define a sine oscillator of a period of 1 beat (in green), and a pulse oscillator with a period of 5s and a pulse width of 0.5s (in grey):

Locking keyframes to beats or seconds

By default, keyframe positions are defined in terms of their frame number, which will remain fixed even if the FPS or BPM changes. For example, if you start at 10fps and create a keyframe on the 4th beat of a 120BPM track, the keyframe will be at frame 20. But if you decide the change to 20fps and update your track to be 140BPM, your animation will be out-of-sync because the 4th beat should now be on frame 34!

To solve this, you can lock your keyframes to their beat (or second) position. After doing this, they will remain in-sync even when you change FPS or BPM.

Interval keyframe creation

You can quickly create keyframes aligned with regular events by using the "at intervals" tab of the Add keyframe dialog. For example, here we are creating a keyframe at every beat position for the first 8 beats. The keyframe positions will be determined by using the document's BPM and FPS. Note that only 6 keyframes will be created, because keyframes already exist for beats 0 and 4:

Keyframe labelling

A common practice is to label keyframes to indicate the audio event they represent (e.g. "bassdrum", "snare", etc...). You can then reference all such keyframes in interpolation formulae with functions like info_match_last(), info_match_next() and info_match_count(), as well as in the bulk edit dialog.

Reference audio

To help you align your keyframes and formula with audio, you can load an audio file to view its waveform alongside the your parameter graph. Zooming and panning the graph will apply to the audio (click and drag to pan, hold alt/option and mouse wheel to zoom). Scrolling the audio will pan the graph. A viewport control is available between the graph and audio. Prompt, beat and cursor markers are displayed on both visualisations.

Automatically generating keyframes from audio events

Manually creating and labelling keyframes for audio events can be tedious. Parseq improves this with an audio event detection feature that uses AubioJS:

After loading a reference audio file, head to the event detection tab under the waveform and hit detect events. Markers will appear on the waveform indicating detected event positions.

You can tweak the event detection by controlling the following:

• Filtering: above the waveform and to the right is a biquad filter that allows you to apply a low/band/high-pass filter to your audio. This will enable you, for example, to isolate bassdrums from snares.
• Method: a range of event detection algorithms to choose from. Experiment with these, as they can produce vastly different results. See the aubioonset CLI docs for more details.
• Threshold: defines how picky to be when identifying onset events. Lower threshold values result in more events, high values result in fewer events.
• Silence: from aubio docs: "volume in dB under which the onset will not be detected. A value of -20.0 would eliminate most onsets but the loudest ones. A value of -90.0 would select all onsets."

Once you're satisfied with the detected events, you can create keyframes by switching to the keyframe generation tab. You can pick a custom label that will be assigned to all newly generated keyframes. If a keyframe already exists at an event position, the label will be combined with the existing label.

See event detection and keyframe generation in action in this tutorial.

Sync'ing to pitch and amplitude using time series

Time series are a powerful feature of Parseq that allows you to import any series of numbers and reference them from Parseq formulas. A primary use case for this is to sync parameter changes to audio pitch or amplitude.

Click 'Add time series' and select an audio file to work with. You can then choose whether to extract pitch or amplitude. When extracting pitch, you can choose from a range of methods (see the aubiopitch CLI docs for details).

A biquad filter that allows you to apply a low/band/high-pass filter to your audio is available if you wish to pre-process it before performing the pitch/amplitude extraction.

After extracting the data, you can post-process it to take the absolute value, exclude datapoints outside a given range, clamp datapoints outside a given range, and normalise to a target range.

Using absolute value is particularly valuable for amplitude, where the unprocessed amplitude will oscillate between positive and negative.

The final timeseries will be decimated to a maximum of 2000 points. The green dots represent where frames land on those points.

Once the time series are created, you can chose an alias for them, and then reference them in your formula.

There are two ways to reference timeseries:

Method	Description	Example
timeseries_name	Returns the timeseries value at the current frame. Equivalent to timeseries_name(f)	Time series replicated as is:
timeseries_name(n)	Returns the timeseries value at frame n	Time series' first 10 frames repeated:

See pitch detection in action in this tutorial.

Legacy Audio Analyser

This feature is deprecated. See its archived documentation on the Parseq wiki.

Time series for arbtrary data sequences

In addition to audio pitch and amplitude data, you can also load any CSV as a timeseries. This means you can import essentially any series of numbers for use in Parseq.

The format of the CSV file must be timestamp,value on each row. You can choose whether the timestamp represents milliseconds or frames before you import the file.

For example, here we have imported data given to us by ChatGPT 4 the after asking the following:

Please generate CSV output in the format x,y , where x is a number increasing by 1 from 0 to 100, and the y value draws a simple city skyline. Output only the CSV data, do not provide any explanation.

Camera movement preview

Parseq has an experimental feature that enables you to visualise your camera movements in real time. It is inspired by AnimationPreview by @pharmapsychotic .

It currently has a few caveats:

• It is a rough reference only: the image warping algorithm is not identical to Deforum's.
• It currently only works for 3D animation params (x, y, z translation and 3d rotation).
• It does not factor in FPS or perspective params (fov, near, far).

Nonetheless, it is quite useful to get a general sense of what your movement params are going to do:

Deforum integration features

Parseq can be used with all Deforum animation modes (2D, 3D, prompt interpolation, video etc...). You don't need to do anything special in Parseq to switch between modes: simply tweak the parameters you're interested in.

Keyframable parameters

Here are the parameters that Parseq can control. You can select which ones are controlled by your document in the 'Managed Fields' section. Any 'Managed Fields' for which you also set values in the A1111 UI for Deforum will be overridden by Parseq. On the other hand, fields you don't select in 'Managed fields' can be controlled from the Deforum UI as normal. So you can 'mix & match' Parseq-controlled values with Deforum-controlled values.

Stable diffusion generation parameters:

• seed
• scale (CFG)
• noise: additional noise to add during generation, can help
• strength: how much the last generated image should influence the current generation

2D animation parameters:

• angle (ignored in 3D animation mode, use rotation 3D z axis)
• zoom (ignored in 3D animation mode, use rotation translation z)
• translation x axis
• translation y axis

Pseudo-3D animation parameters (ignored in 3D animation mode):

• perspective theta angle
• perspective phi angle
• perspective gamma angle
• perspective field of view

3D animation parameters (all ignored in 2D animation mode):

• translation z axis
• rotation 3d x axis
• rotation_3d y axis
• rotation_3d z axis
• field of view
• near point
• far point

Anti-blur parameters:

• antiblur_kernel
• antiblur_sigma
• antiblur_amount
• antiblur_threshold

Hybrid video parameters:

• hybrid_comp_alpha
• hybrid_comp_mask_blend_alpha
• hybrid_comp_mask_contrast
• hybrid_comp_mask_auto_contrast_cutoff_low
• hybrid_comp_mask_auto_contrast_cutoff_high

Other parameters:

• contrast: factor by which to adjust the previous last generated image's contrast before feeding to the current generation. 1 is no change, <1 lowers contrast, >1 increases contract.

Prompt manipulation

Parseq provides a further 8 keyframable parameters (prompt_weight_1 to prompt_weight_8) that you can reference in your prompts, and can therefore be used as prompts weights. You can use any prompt format that will be recognised by a1111, keeping in mind that anything enclosed in ${...} will be evaluated as a Parseq expression.

For example, here's a positive prompt that uses Composable Diffusion to interpolate between faces:

Jennifer Aniston, centered, high detail studio photo portrait :${prompt_weight_1} AND
Brad Pitt, centered, high detail studio photo portrait :${prompt_weight_2} AND
Ben Affleck, centered, high detail studio photo portrait :${prompt_weight_3} AND
Gwyneth Paltrow, centered, high detail studio photo portrait :${prompt_weight_4} AND
Zac Efron, centered, high detail :${prompt_weight_5} AND
Clint Eastwood, centered, high detail studio photo portrait :${prompt_weight_6} AND
Jennifer Lawrence, centered, high detail studio photo portrait :${prompt_weight_7} AND
Jude Law, centered, high detail studio photo portrait :${prompt_weight_8}

And here's an example using term weighting:

(Jennifer Aniston:${prompt_weight_1}), (Brad Pitt:${prompt_weight_2}), (Ben Affleck:${prompt_weight_3}), (Gwyneth Paltrow:${prompt_weight_4}), (Zac Efron:${prompt_weight_5}), (Clint Eastwood:${prompt_weight_6}), (Jennifer Lawrence:${prompt_weight_7}), (Jude Law:${prompt_weight_8}), centered, high detail studio photo portrait 

A corresponding parameter flow could look like this:

Note that any Parseq expression can be used, so for example the following will alternate between cat and dog on each beat:

Detailed photo of a ${if (floor(b%2)==0) "cat" else "dog"} 

Some important notes:

• Remember that unless you set strength to 0, prior frames influence the current frame in addition to the prompt, so previous items won't disappear immediately even if they are removed from the prompt on a given frame.
• To counter-act this, you may wish to put terms you don't wish to see at a given frame in your negative prompt too, with inverted weights.

So the prior example might look like this:

Using multiple prompts

You can add additional prompts and assign each one to a frame range:

If the ranges overlap, Parseq will combine the overlapping prompts with composable diffusion. You can decide whether the composable diffusion weights should be fixed, slide linearly in and out, or be defined by a custom Parseq expression.

Note that if overlapping prompts already use composable diffusion (... AND ...), this may lead to unexpected results, because only the last section of the original prompt will be weighted against the overlapping prompt. Parseq will warn you if this is happening.

Subseed control for seed travelling

For a great description of seed travelling, see Yownas' script. In summary, you can interpolate between the latent noise generated by 2 seeds by setting the first as the (main) seed, the second as the subseed, and fluctuating the subseed strength. A subseed strength of 0 will just use the main seed, and 1 will just use the subseed as the seed. Any value in between will interpolate between the two noise patterns using spherical linear interpolation (SLERP).

Parseq does not currently expose the subseed and subseed strength parameters explicitly. Instead, it takes fractional seed values and uses them to control the subseed and subseed strength values. For example, if on a given frame your seed value is 10.5, Parseq will send 10 as the seed, 11 as the subseed, and 0.5 as the subseed strength.

The downside is you can only interpolate between adjacent seeds. The benefit is seed travelling is very intuitive. If you'd like to have full control over the subseed and subseed strength, feel free to raise a feature request!

Note that the results of seed travelling are best seen with no input image (Interpolation animation mode) or with a very low strength. Else, the low input variations will likely result in artifacts / deep-frying.

Otherwise it's best to change the seed by at least 1 on each frame (you can also experiment with seed oscillation, for less variation).

Delta values (aka absolute vs relative motion parameters)

Parseq aims to let you set absolute values for all parameters. So if you want to progressively rotate 180 degrees over 4 frames, you specify the following values for each frame: 45, 90, 135, 180.

However, because Stable Diffusion animations are made by feeding the last generated frame into the current generation step, some animation parameters become relative if there is enough loopback strength. So if you want to rotate 180 degrees over 4 frames, the animation engine expects the values 45, 45, 45, 45.

This is not the case for all parameters: for example, the seed value and field-of-view settings have no dependency on prior frames, so the animation engine expects absolute values.

To reconcile this, Parseq supplies delta values to Deforum for certain parameters. This is enabled by default, but you can toggle if off in the A111 Deforum extension UI if you want to see the difference.

For most parameters the delta value for a given field is simply the difference between the current and previous frame's value for that field. However, a few parameters such as 2D zoom (which is actually a scale factor) are multiplicative, so the delta is the ratio between the previous and current value.

Working with large number of frames (performance tips)

Parseq can become slow when working with a large number of frames. If you see performance degradations, try the following:

• In the Managed Fields section, select only the fields you want to control with Parseq.
• Close the sections you're not using. For example, if you're not using Sparklines or the test Output view, close them using the ^ next to the section title.
• Hide the fields you're not actively working with by unselecting them in the "show/hide fields" selection box (or toggle them by clicking their sparklines).
• Disable autorender (and remember to manually hit the render button every few changes).
• Note that the graph becomes uneditable when displaying more than 1000 frames, and does not show keyframes. To restore editing, zoom in to a section less than 1000 frames.

Development & running locally

Parseq is currently a front-end React app. It is part way through a conversion from Javascript to Typescript. There is currently very little back-end: by default, persistence is entirely in browser indexdb storage via Dexie.js. Signed-in users can optionally upload data to a Firebase-backed datastore.

You'll need node and npm on your system before you get started.

If you want to dive in:

• Run npm install to pull dependencies.
• Run npm start to run the Parseq UI locally in dev mode on port 3000. You can now access the UI on localhost:3000. Code changes should be hot-reloaded.

Deployment

Hosting & deployment is done using Firebase. Merges to master are automatically deployed to the staging channel. PRs are automatically deployed to the dev channel. There is currently no automated post-deployment verification or promotion to prod.

Assuming you have the right permissions, you can view active deployements with:

firebase hosting:channel:list

And promote from staging to prod with:

firebase hosting:clone sd-parseq:staging sd-parseq:live

Credits

This script includes ideas and code sourced from many other scripts. Thanks in particular to the following sources of support and inspiration:

• Everyone supporting Parseq on Patreon, including: Adam Sinclair, MJ, AndyXT, King Kush, Ben Del Vacchio, Zirteq, Kewk, BinaryLady at TheTechMargin, ascendant, Sasha Agafonoff, Brandon Glasgow, Koshi Mazaki, lexvesseur, Andreas Lewitzki, veryVANYA, Nenad Kuzmanovic, Stash
• Everyone who has bought me a coffee!
• Everyone who has contributed to the A1111 web UI
• Everyone who has contributed to Deforum
• Everyone trying out Parseq and giving feedback on Discord
• Everyone behind Aubio, AubioJS, Wavesurfer, react-timeline-editor, ag-grid (community edition), p5, chart.js and recharts.
• The following scripts and their authors from whom I picked up some good ideas when I was starting out:
  • Filarus for their vid2vid script.
  • Animator-Anon for their animation script.
  • Yownas for their seed travelling script
  • feffy380 for the prompt-morph script
  • eborboihuc for the clear implementation of 3d rotations using cv2.warpPerspective()