modelscope / modelscope/DiffSynth-Studio

Question regarding the noise scheduler and training objectives

Open
#1,014 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
13.1k
Forks
1.3k
Avg merge
13h 12m
Merged PRs (30d)
45

Description

Thank you for open source the code for Wan video! The quality is truly amazing. I really have fun using the model to generate all kinds of videos. And they are all high quality!

I have one question regarding training the model. Specifically the noise schedule part. I read the technical report and the paper states that Wan is trained with the rectified flow objectives:

$x_t = t x_1 + (1-t) x_0$

Thus the ground truth velocity $v_t = x_1 - x_0$ and the model's objective is trying to predict such velocity given the context, timestep, and $x_t$.

But when I tried to train the TI2V-5B model, I found that the FlowMatchScheduler has different implementation. For instance, the add_noise and training_target here: https://github.com/modelscope/DiffSynth-Studio/blob/main/diffsynth/schedulers/flow_match.py#L94-L105

So I am wondering is this the same scheduler that was used to train the model released in the repo of Wan 2.2?

Thank you so much!

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with diffsynth/schedulers/flow_match.py, especially add_noise and training_target around lines 94-105, then inspect the Wan2.2 repository and its training or scheduler entry points. Compare those implementations with the rectified-flow objective described in the issue's technical-report excerpt. Done means documenting whether the released model uses this scheduler and explaining any apparent difference.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
machine-learning
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.