Skip to content

Wan 3.0 Reference-to-Video fails: reference_images sent as string instead of array #198

Open

Description

@perrycolegg

Node Banana version

2.3.0

Platform

Windows (x64)

OS version

Windows 11 Pro N 25H2

Steps to reproduce

Description

Video generation fails when using WaveSpeed's Alibaba Wan 3.0 Reference-to-Video model with reference images connected to the Generate Video node.

The API rejects the request because the reference_images parameter is submitted as a string instead of an array of strings.

Steps to reproduce

  1. Create a workflow containing two Image Input nodes with separate reference images.
  2. Connect both Image Input nodes to the Reference Images input of a Generate Video node.
  3. Connect a text prompt (either directly or through an LLM Generate node) to the Prompt input of the video node.
  4. Select the WaveSpeed provider and the model alibaba/wan-3.0-prime/reference-to-video.
  5. Run the video generation.

Actual result

Video generation fails with the following error:

Video generation failed

alibaba/wan-3.0-prime/reference-to-video:
Invalid request body: field "reference_images"
must be an array, got string
"https://d2h7xmz5gqybh9.cloudfront.net/..."

The error indicates that Node Banana is submitting the image reference as a string rather than an array.

Expected result

Node Banana should automatically collect all connected reference images and submit them as an array of image URLs, matching the provider's API schema.

For example:

{
  "reference_images": [
    "https://example.com/reference1.jpg",
    "https://example.com/reference2.jpg"
  ]
}

Even a single connected reference image should be submitted as an array containing one URL.

Additional information

  • Provider: WaveSpeed
  • Affected model: Alibaba Wan 3.0 Prime Reference-to-Video
  • Two reference images were connected to the Reference Images input.
  • The Generate Video node does not expose a setting for changing the input data type.
  • Bundling or unbundling the image connections does not appear to affect how the API request is constructed.

Possible cause

The Generate Video node or its provider adapter may be serializing the reference_images parameter as a single string rather than an array.

This may also affect other models requiring arrays of reference images, videos, or audio files.

Suggested fix

Validate the model's input schema and serialize all images connected to reference_images as an array of strings, preserving the reference order.

The same behavior should work for both single-image and multiple-image workflows.

Screenshot 2026-11-14 202645

Diagnostics


Checks

  • I am on the latest release (the app offers updates under Help → Check for Updates…)
  • I have removed keys, personal paths and private media from what I attached

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions