OpenKatana · Music file:
OpenKatanaAudioFile lets you choose or upload music for an OpenKatana workflow, making it easy to bring a soundtrack into your video or audio-based creative work. It loads an existing recording through ComfyUI’s audio-loading functionality and prepares the sound for compatible nodes to use, without generating music or applying audio effects. You can also leave the selection empty when you want the surrounding workflow to use the video’s own sound instead; the node itself does not extract that sound or perform the fallback. Its purpose is to provide a straightforward starting point for supplying optional music, rather than analyzing beats, adjusting volume, or mixing tracks.
OpenKatana · Music file Input Parameters:
music
Required interface field of type COMBO[STRING] that lets you select an audio file from the available choices, with audio upload support enabled. Selecting a file causes the node to resolve its location through ComfyUI and load its audio samples and sample rate. An empty selection is explicitly supported by the execution code and causes the node to return no audio data, allowing a compatible downstream workflow to handle the absence of external music. The available options are supplied dynamically by input_choices('audio'); the provided source does not specify a fixed file list, supported extension list, or explicit default selection. Minimum and maximum values do not apply because this is a file selector rather than a numerical setting. Although the field is marked required in the interface, its value can be empty when the selector permits that choice.
OpenKatana · Music file Output Parameters:
audio
An output of type AUDIO containing the loaded recording in ComfyUI’s audio structure. For a selected file, its value contains waveform, the numerical sound samples with an added batch dimension, and sample_rate, the number of samples per second reported by the audio loader. Together, these allow compatible downstream nodes to interpret and process the recording at its loaded playback rate. The output is audio data, not a file path, a finished soundtrack mix, or a beat-analysis report. When the music selection is empty, the output value is None instead of an audio structure; this means no external audio has been supplied, not that a silent recording or the video’s soundtrack has been generated.
OpenKatana · Music file Usage Tips:
- Select or upload your intended soundtrack through
music, then connectaudioto a downstream input that accepts ComfyUI AUDIO data. - Leave
musicempty only when the receiving workflow supports optional audio. This is appropriate for an OpenKatana workflow designed to use the video’s original sound when no music is supplied. - Prepare the recording before loading it if you need a particular excerpt. This node has no start-time or duration controls and does not provide trimming settings.
- Use separate processing nodes for volume changes, fades, mixing, or beat analysis. OpenKatanaAudioFile only loads the selected recording; it does not perform those operations.
- Check the selected recording with a compatible audio preview or playback node before running a longer workflow. This helps you catch an incorrect file, unexpected content, or an unsuitable recording early.
- If you move a workflow to another computer or ComfyUI installation, make sure its audio file is available there and select it again if necessary. The node resolves a local ComfyUI file selection rather than embedding the recording in the workflow.
OpenKatana · Music file Common Errors and Solutions:
Selected music is rejected during validation
- Explanation: The node passes
musictocheck_choicebefore execution. The implementation of that helper is not included, so its exact rejection rules and error messages cannot be confirmed from the provided source. - Solution: Choose an audio file currently offered by the selector, or upload the recording again and select the new entry. If an empty choice is rejected by your installed interface, check that your OpenKatana version supports the intended optional-music workflow.
File not found or inaccessible audio file
- Explanation: The selected file must resolve to a readable location through ComfyUI. A missing, moved, deleted, or inaccessible file can prevent loading. The exact message comes from the file-resolution or loading components rather than this node’s own code.
- Solution: Confirm that the recording still exists in the location managed by ComfyUI, upload it again if needed, and reselect it. If ComfyUI runs on another machine or in a container, make sure the file is accessible to that installation.
Audio decoding failed or unsupported recording
- Explanation: ComfyUI’s audio loader may fail if the recording is damaged, contains no usable audio, or uses an encoding unavailable in your installation. The provided node does not define a decoder-specific error message or guarantee support for particular file formats.
- Solution: Test the recording in an audio player. If necessary, export a fresh copy in a format supported by your ComfyUI installation, then upload and select that copy. Renaming the file extension alone does not convert the audio.
ImportError or ModuleNotFoundError involving comfy_extras.nodes_audio
- Explanation: The node imports its loading function from
comfy_extras.nodes_audiowhen a nonempty selection is processed. An incomplete or incompatible ComfyUI installation can prevent that import from succeeding; the exact message depends on which component is missing. - Solution: Verify that ComfyUI’s built-in audio functionality works, review the console for the missing component, and update or repair ComfyUI and its required dependencies using your installation’s supported procedure.
A downstream node reports missing audio or a NoneType-related error
- Explanation: An empty
musicselection deliberately returnsNone. This is valid behavior for OpenKatanaAudioFile, but a downstream node that requires actual audio data may reject it. Leaving the selection empty does not make this node extract the video’s sound. - Solution: Select a recording when the next node requires audio, or use a downstream workflow that explicitly supports optional music and handles the video-sound fallback. If you need the video’s audio as an AUDIO value, use an appropriate extraction or loading node.
