starred/ace-step-ui
1
0
Fork 0
mirror of https://github.com/fspecii/ace-step-ui.git synced 2026-04-25 14:15:49 +03:00
Code Issues 45 Projects Releases Packages Wiki Activity

[GH-ISSUE #38] Allow ACE-Step API to be started from within the UI with selectable model configurations (e.g., -turbo, -base, -sft). #34

New issue
Open
opened 2026-02-26 21:30:56 +03:00 by kerem · 2 comments
kerem commented 2026-02-26 21:30:56 +03:00
Owner
Copy link

Originally created by @Basthet on GitHub (Feb 7, 2026).
Original GitHub issue: https://github.com/fspecii/ace-step-ui/issues/38

Problem/Motivation:

  1. Currently, users must manually start the ace-step-api separately.
  2. Also the model (e.g., acestep-v15-turbo, acestep-v15-base) to load have to be set via ACESTEP_CONFIG_PATH environment variable. Either via:
  • the .env file in the ace-step-1.5 folder or
  • directly via the command line export ACESTEP_CONFIG_PATH=acestep-v15-base && uv run acestep-api (or 'set' instead of 'export' on Windows) before starting the ACE-Step API.

This process is cumbersome and requires technical knowledge of environment variables and command-line operations.
It also prevents seamless switching between different model configurations directly from the user interface.

Proposed Solution:
I request an enhancement to the ACE-Step UI that provides an intuitive way to select the desired ACESTEP_CONFIG_PATH when initiating the API server. This could be implemented as:

  • A dropdown menu or radio buttons within the UI, allowing users to choose from available model configurations (e.g., "acestep-v15-turbo", "acestep-v15-base", "acestep-v15-sft").
  • Upon selection and API startup, the UI should internally set the ACESTEP_CONFIG_PATH environment variable for the API process, ensuring the correct model is loaded.

Benefits:

  • Improved User Experience: Simplifies the process of starting the API with different model configurations, making it accessible to a wider range of users.
  • Efficiency: Eliminates the need for manual command-line intervention.
  • Flexibility: Allows quick and easy switching between models for testing or different use cases.

Technical Context (for developers):
The underlying mechanism involves setting the ACESTEP_CONFIG_PATH environment variable, and start the api. For example, on Linux, this is typically done via export
ACESTEP_CONFIG_PATH=acestep-v15-turbo && uv run acestep-api. On Windows, it's (most likely) set ACESTEP_CONFIG_PATH=acestep-v15-turbo && uv run acestep-api. The UI would need to abstract this command-line interaction and manage the environment variable for the API process it launches.
In addition, it should be indicated by the red/green status light on the top-left traffic light (next to the Simple/Custom slider) if the api is running. A click on this item should open the option to select the model and start it (+ a short notice: click here to change model).

Originally created by @Basthet on GitHub (Feb 7, 2026). Original GitHub issue: https://github.com/fspecii/ace-step-ui/issues/38 Problem/Motivation: 1. Currently, users must manually start the ace-step-api separately. 2. Also the model (e.g., acestep-v15-turbo, acestep-v15-base) to load have to be set via ACESTEP_CONFIG_PATH environment variable. Either via: - the .env file in the ace-step-1.5 folder or - directly via the command line export ACESTEP_CONFIG_PATH=acestep-v15-base && uv run acestep-api (or 'set' instead of 'export' on Windows) before starting the ACE-Step API. This process is cumbersome and requires technical knowledge of environment variables and command-line operations. It also prevents seamless switching between different model configurations directly from the user interface. Proposed Solution: I request an enhancement to the ACE-Step UI that provides an intuitive way to select the desired ACESTEP_CONFIG_PATH when initiating the API server. This could be implemented as: * A dropdown menu or radio buttons within the UI, allowing users to choose from available model configurations (e.g., "acestep-v15-turbo", "acestep-v15-base", "acestep-v15-sft"). * Upon selection and API startup, the UI should internally set the ACESTEP_CONFIG_PATH environment variable for the API process, ensuring the correct model is loaded. Benefits: * Improved User Experience: Simplifies the process of starting the API with different model configurations, making it accessible to a wider range of users. * Efficiency: Eliminates the need for manual command-line intervention. * Flexibility: Allows quick and easy switching between models for testing or different use cases. Technical Context (for developers): The underlying mechanism involves setting the ACESTEP_CONFIG_PATH environment variable, and start the api. For example, on Linux, this is typically done via export ACESTEP_CONFIG_PATH=acestep-v15-turbo && uv run acestep-api. On Windows, it's (most likely) set ACESTEP_CONFIG_PATH=acestep-v15-turbo && uv run acestep-api. The UI would need to abstract this command-line interaction and manage the environment variable for the API process it launches. In addition, it should be indicated by the red/green status light on the top-left traffic light (next to the Simple/Custom slider) if the api is running. A click on this item should open the option to select the model and start it (+ a short notice: click here to change model).
kerem commented 2026-02-26 21:30:56 +03:00
Author
Owner
Copy link

@cynical2010 commented on GitHub (Feb 8, 2026):

https://github.com/fspecii/ace-step-ui/issues/41

Same so i went back to Gradio

<!-- gh-comment-id:3867361791 --> @cynical2010 commented on GitHub (Feb 8, 2026): https://github.com/fspecii/ace-step-ui/issues/41 Same so i went back to Gradio
kerem commented 2026-02-26 21:30:56 +03:00
Author
Owner
Copy link

@kajan988 commented on GitHub (Feb 11, 2026):

Same so i went back to Gradio +1

<!-- gh-comment-id:3882147719 --> @kajan988 commented on GitHub (Feb 11, 2026): Same so i went back to Gradio +1
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
gradio-experimental
No results found.
Labels
Clear labels   
pull-request

Mirrored from GitHub Pull Request

No labels
pull-request
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/ace-step-ui#34
No description provided.