Dynamic preview method per task

[huchenlei]

Feature Idea

Each queued task can spcify its own preview method instead of relying on a static preview method set via server launch args.

This should enables selecting preview method by adjusting frontend settings without restart the server.

Existing Solutions

https://github.com/ltdrdata/ComfyUI-Manager has a UI selection to pick preview method. However, it requires restart to take effect.

Other

No response

[ltdrdata]

The preview method selection in ComfyUI-Manager is applied immediately without restarting the server.
However, it does not affect the inference currently in progress and will only apply to the next inference.

[huchenlei]

The preview method selection in ComfyUI-Manager is applied immediately without restarting the server. However, it does not affect the inference currently in progress and will only apply to the next inference.

I think this feature should be in core. Maybe you can help upstream the manager impl to core?

[ltdrdata]

Currently, the settings are saved in the config.ini of ComfyUI-Manager, but it seems better to move them to comfy.settings.json.

However, one thing to consider in this case is that comfy.settings.json has so far been structured to configure only the front-end information.

Since this change will involve modifying the backend settings, it would be good to allow for a callback to handle this.

[huchenlei]

Currently, the settings are saved in the config.ini of ComfyUI-Manager, but it seems better to move them to comfy.settings.json.

However, one thing to consider in this case is that comfy.settings.json has so far been structured to configure only the front-end information.

Since this change will involve modifying the backend settings, it would be good to allow for a callback to handle this.

I don't think the setting JSON file needs to be read by the backend python server, as the frontend can pass the setting value as a request param to achieve per-request dynamic adjustment.

[ltdrdata]

Currently, the settings are saved in the config.ini of ComfyUI-Manager, but it seems better to move them to comfy.settings.json.
However, one thing to consider in this case is that comfy.settings.json has so far been structured to configure only the front-end information.
Since this change will involve modifying the backend settings, it would be good to allow for a callback to handle this.

I don't think the setting JSON file needs to be read by the backend python server, as the frontend can pass the setting value as a request param to achieve per-request dynamic adjustment.

Then, is it sufficient to simply expose an endpoint that allows the preview method to be dynamically configured?

[ltdrdata]

Once it is reflected in the front, I will remove the feature from ComfyUI-Manager.