Slice settings¶
Slice settings are a saved setup: the four picks you normally make by hand in the Slice dialog — printer preset, process preset, a filament preset per AMS slot, and the bed type. Save it once, and next time pick it from a dropdown instead of choosing all four again.
That's the whole feature. It's a shortcut for repeatable work, not a dispatcher: you still slice and queue exactly the way you always do.
Printing many copies? That's the auto-queue's job
Saved settings don't set a quantity or pick printers. To print a batch, use Auto-Queue Routing — set how many you want and which printer model, and BamDude spreads them across every matching printer, matching filament type and colour as it goes.
Earlier betas (0.4.7b2–0.4.7b5) shipped this as "Slicer Pipelines", which could also dispatch copies — two ways to do one job. That half was removed; the auto-queue does it and always did.
What gets saved¶
| Field | What it is |
|---|---|
| Name / description | Your label for the setup. |
| Printer preset | The printer profile to slice against (source + id — local, Orca Cloud, Bambu Cloud, or standard). |
| Process preset | The process/quality profile. |
| Filament presets | One preset per AMS slot, so a multi-material job maps each slot to the right filament. |
| Bed type | The build-plate type to slice for. |
Saving and using one¶
Save one straight from the Slice dialog with Save these settings — it captures the presets you've already picked there.
Use one from the same dialog: pick it under Apply saved settings and all four selections fill in at once. Then slice as usual and queue the result however you normally would — straight to a printer or into the auto-queue.
When a saved preset has been deleted¶
Presets change. If a saved set references one that no longer exists, BamDude does not apply that slot — it keeps whatever the dialog picked automatically and names the affected slots in a warning above the picker.
This matters: silently applying a dead reference would leave that dropdown blank while the dialog still looked ready to slice, and you'd send a job with a preset you never chose. Re-pick the flagged slot by hand and the warning clears.
Permissions¶
| Permission | Grants |
|---|---|
pipelines:read |
See saved settings and load them in the Slice dialog. |
pipelines:write |
Create, edit, and delete saved settings. |
Administrators and Operators get both; Viewers get read only.
| Endpoint | Method | Permission |
|---|---|---|
/slicer-pipelines/ |
GET / POST | read / write |
/slicer-pipelines/{id} |
GET / PUT / DELETE | read / write / write |
An API key with read scope can list saved settings; creating and editing them is an operator action.
Called pipelines in the API
The endpoints and permissions still say pipelines — the feature arrived from upstream Bambuddy under that name, and renaming the API would break anyone already calling it. Only the interface wording changed.
Manage, rename, and delete saved settings under Settings → Printing.
Related¶
- Auto-Queue Routing — print a set quantity across every printer of a model.
- Per-Printer Queues — where a sliced job lands.
- Slicer API — the containerised OrcaSlicer / Bambu Studio sidecar that does the actual slicing.
- Cloud Profiles / Orca Cloud — preset sources a saved set can reference.