Skip to content

Add extra model paths for WAN models discovery #165

Description

@Shellishack

Is your feature request related to a problem? Please describe.
I am using WAN2.2 s2v's official workflows, and I ran in to "Value not in list" issues like

[{'type': 'value_not_in_list', 'message': 'Value not in list', 'details': "clip_name: 'umt5_xxl_fp8_e4m3fn_scaled.safetensors' not in []", 'extra_info': {'input_name': 'clip_name', 'input_config': [[], {}], 'received_value': 'umt5_xxl_fp8_e4m3fn_scaled.safetensors'}}]

According to WAN2.2 (s2v) usage manual, the following models need to be present in this structure:

  • diffusion_models
    • wan2.2_s2v_14B_fp8_scaled.safetensors
    • wan2.2_s2v_14B_bf16.safetensors
  • audio_encoders
    • wav2vec2_large_english_fp16.safetensors
  • vae
    • wan_2.1_vae.safetensors
  • text_encoders
    • umt5_xxl_fp8_e4m3fn_scaled.safetensors

Upon checking #48, I notice these paths are not present in src/extra_model_paths.yaml:

  diffusion_models: models/diffusion_models/
  audio_encoders: models/audio_encoders/
  text_encoders: models/text_encoders/

Describe the solution you'd like

Add the following to src/extra_model_paths.yaml:

  diffusion_models: models/diffusion_models/
  audio_encoders: models/audio_encoders/
  text_encoders: models/text_encoders/

Describe alternatives you've considered

Additional context

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

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions