H3 Audio Reference:
The H3 Audio Reference node prepares standalone audio clips for use as MiniMax H3 references. It lets you gather a variable number of clips in one place and encode them into a dedicated audio-reference value for a compatible downstream workflow. This is useful when you want to organize several reference sounds without adding a separate node for every clip. The provided source shows that the node passes the clips to an audio-encoding function; it does not establish how a downstream model interprets them or whether adding more clips improves a result.
H3 Audio Reference Input Parameters:
audio_vae
A required VAE input used when the node encodes the reference audio. Connect the audio VAE intended for your H3 workflow before running the node; without this connection, the required input is missing. The interface specifies no selectable options, numeric minimum or maximum, or default value for this parameter.
audios
An optional, expandable group of AUDIO inputs for the standalone clips you want to encode. Its sockets follow the audio_ prefix and can expand from a minimum of 0 to a maximum of 16, so you can supply up to 16 clips without changing nodes. The execution method passes this group to the encoder and uses None when the parameter is omitted. The source does not specify how an empty group is handled by the encoder, so connect at least one clip when you need an audio reference containing audio.
H3 Audio Reference Output Parameters:
audio_reference
The node’s single output, with type TURING_UTILS_H3_AUDIO_REFERENCE, contains the value returned by the audio-encoding function. Connect it to a downstream input that accepts this reference type. It represents the node’s prepared audio reference, not a playable audio output; the supplied source does not describe its internal format or guarantee a particular result when no clips are connected.
H3 Audio Reference Usage Tips:
- Connect the required
audio_vaefirst, then add theaudiossockets you need and attach your reference clips. - For a single reference clip, use one audio socket. Add more sockets only when you have additional clips to include; the interface supports at most 16.
- Check that the receiving node accepts
TURING_UTILS_H3_AUDIO_REFERENCE. A general audio input is not the same declared type. - If an empty
audiosgroup produces an unexpected result, attach a clip and rerun. Empty-group behavior is not specified in the provided source.
H3 Audio Reference Common Errors and Solutions:
Missing required input: audio_vae
- Explanation: The node requires a
VAEconnection ataudio_vae. This heading describes a possible validation issue; the provided source does not specify the exact error text. - Solution: Connect the appropriate audio VAE to
audio_vaeand run the workflow again.
Incompatible connection type for an audio socket
- Explanation: Each expandable socket expects
AUDIOdata. A connection carrying another type may be rejected by the workflow interface; the exact message is not shown in the source. - Solution: Connect an audio-producing node to the socket, and check the socket types if the connection is refused.
Incompatible connection type for audio_reference
- Explanation: The output has the dedicated
TURING_UTILS_H3_AUDIO_REFERENCEtype. A downstream input expecting another type may not accept it; the source does not provide exact validation wording. - Solution: Connect
audio_referenceonly to a compatible reference input.
Audio socket limit reached
- Explanation: The expandable
audiosgroup has a declared maximum of 16 sockets. You cannot add a seventeenth socket to this node under the shown schema. - Solution: Use no more than 16 clips with one H3 Audio Reference node.
Error while encoding audio references
- Explanation: Execution calls
encode_audios(audio_vae, audios), but that function’s implementation is not included. The provided source therefore does not establish its specific failure messages or requirements for clip format, duration, or an empty audio group. - Solution: Confirm that
audio_vaeis connected and that each attached socket receives valid audio. If the error remains, inspect the full workflow error for the failing clip or consult the encoder’s documentation; do not assume a particular format requirement from this node class alone.
