Mac M1 Max not outputing parseq JSON properly
charliemagee opened this issue · comments
Having lots of trouble on my Mac. 3D does not work at all. That appears to be a Deforum Auto1111 problem.
But Parseq doesn't work in 2D either. I've tried the Copy Output and Copy URL methods and get exact same results: my JSON numbers don't match what Terminal (and Auto1111) are creating.
Example JSON:
{
"frame": 20,
"seed": 2971941896,
"zoom": 1.017139397622232,
"translation_x": 2.7838678312334286,
"translation_y": 2.1447515493049965,
"angle": 0.6387181711747354,
"deforum_prompt": "mdjrny-v4 style, full shot, wide angle shot photograph of a polar bear walking on a barren snowfield in the Arctic, (((white snow))), bright afternoon light reflecting off the Arctic ice, ((bright sunlight)), ((colorful)), ZEISS, studio quality, 8k, (((photorealistic))), ((detailed)), ((colorful)), intricate complexity, perfect composition, photo by Martin Gregus",
"subseed": 2971941896,
"subseed_strength": 0,
"seed_delta": 1,
"seed_pc": 99.99999737545346,
"zoom_delta": 0.998191477796093,
"zoom_pc": 95.33645028399819,
"translation_x_delta": -0.2260350397473907,
"translation_x_pc": 43.930224315301295,
"translation_y_delta": 0.08295829484691275,
"translation_y_pc": 49.015293456333445,
"angle_delta": -0.11810169546043392,
"angle_pc": 17.682294801862977
},
Compare translation_x and _y, for example.
Here's the screenshot of that frame in Terminal:
The file starts out perfect at frame 0 and then jumps to weird numbers at frame 1.
Solved it. Sorry if I missed this in the YouTube tutorials.
The "Use delta values for movement parameters" checkbox under the Parseq Manifest must be unchecked.