Glenn Ko Glidias

IFV2V VACE File-based Task Batch Manager workflow-specific setup info

For an introduction and the list of main configuration/file setup parameters to get you started, refer to the earlier section at: https://gist.github.com/Glidias/b15b51598ae643bab9dbc7aa12fe62ed

These doc only covers anything workflow specific beyond file/json-based stuff.

Workflow group: Save Blended WEBP Inpaints

This is normally used only when inpainting localised regions across multiple (or single-image) frames. Can disable this if not needed.

IFV2V VACE File-based Task Batch Management Workflow parameters

The purpose of this ComfyUI workflow (Image/Frame(s)/Video To Video process) is to manage batch generations of multiple file items found in a folder with varied mixed image/video file formats (including PSD file format for layers to define frames) through a unified VACE workflow . ((note: this can be swapped out to other types of workflows), but VACE was used because it's most versatile to fit all use cases under the V2V/I2V/FLF2V umbrella)

BY adopting file-system/config conventions, it allows you to mix and match all of VACE capabilities (single/multiple I2V/FLF2V/V2V inpainting, outpainting, restyling/repainting, extension, looping) without overcomplicating the workflow nodes since most of the intention is implied within the accompanying file assets and their respective json configurations. The complexity of the workflow nodes however only comes in the process of managing multiple varied image/video/txt sources and handling the batch seri

	{
	"last_node_id": 42,
	"last_link_id": 56,
	"nodes": [
	{
	"id": 25,
	"type": "easy showAnything",
	"pos": [
	1054.7166748046875,
	-30.893224716186523

	{
	"last_node_id": 42,
	"last_link_id": 56,
	"nodes": [
	{
	"id": 25,
	"type": "easy showAnything",
	"pos": [
	1054.7166748046875,
	-30.893224716186523

	/**
	* @param callback Important: A Memomized callback reference (eg. via `useCallback()`) or a Permanent function
	* to process/return a given lazy initialized state!
	* State will re-update on next frame via useEffect if callback method supplied is different from previous case,
	* but on subsequent renders only.
	* @returns The state payload consisting of [state, setState]
	*/
	export function useStateByCallback<T>(callback: () => T) {
	const payload = useState(callback);
	const [, setVal] = payload;

	/**
	* useEffect() that skips the first render execution before being mounted
	* @param callback Important: A Memomized callback reference (eg. via `useCallback()`) or any other function
	* to process/return a given lazy initialized state! eg. `usePostEffect(useCallback(.., [...]))`
	* Callback will call again on next frame via useEffect() if callback method supplied is different from previous case,
	* but on subsequent renders only.
	*/
	export function usePostEffect(callback: Function) {
	const ref = useRef(false);
	useEffect(() => {

	_callComponentMethod: function (name, dt) {
	var wasLooping = this._beginLooping();
	var nextN;
	var lastN = null;
	for (var n = this.compNodeList; n!=null; n=nextN) {
	nextN = n.next;
	var c = n.c;
	if (c._destroyed \|\| !c.entity.enabled \|\| !c.enabled) {
	if (lastN) {
	lastN.next = nextN;

	SONG OF SWORDS: Character Creation UI Field formulas (for Beta 2.0)

	/*
	PSEUDO CODE LEGEND SUMMARY:
	* instance field quantifier/process description
	"the" - single/sole/final, etc.
	"each" - for each, resolves to different results per instance
	"all" - for all instances, resolves similarly across all instances
	=> Direct instance implication/continuation (ie. holds internal field)
	\|=> per instance respective field value implication (1 to 1 relationships)