{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreib2xsd3zskhc7qi2sldu7lww54vnm44ouyqpwsu3atkxma3j2fwo4",
    "uri": "at://did:plc:pgryn3ephfd2xgft23qokfzt/app.bsky.feed.post/3mlyas4p67qt2"
  },
  "path": "/t/wan2-2-i2v-clarifications-needed-regarding-settings-on-low-vram-system/175884#post_12",
  "publishedAt": "2026-05-16T15:40:15.000Z",
  "site": "https://discuss.huggingface.co",
  "textContent": "i been experimenting using the methodology you suggested, working by exclusion. i gotta say, the results are inconclusive. it seems to be EXTREMELY “picture dependent”. like every picture works best with its unique set of settings. if anybody stumbling onto this post is interested, the most solid results are cfg 1/ steps 4/ sa_solver,beta/start at step 0\n\nstart at step 1 gives more prompt obedience but it also takes quite a few artistic liberties in some areas (it seems like it defaults on what it encountered in its training rather than staying true to the source image). the thing i would really like to solve with start at step 1 is locking the camera movement. for some reason it keeps doing cinematic zooms etc even tho both pos and neg prompts explicitly state not to",
  "title": "Wan2.2 i2v (clarifications needed regarding settings on low vram system)"
}