starred/bambuddy-maziggy-1

Fork 0

mirror of https://github.com/maziggy/bambuddy.git synced 2026-05-09 08:25:54 +02:00

[GH-ISSUE #310] [Feature]: Import Profiles from OrcaSlicer Export #194

New issue

Closed

opened 2026-05-07 00:07:28 +02:00 by BreizhHardware · 6 comments

BreizhHardware commented

2026-05-07 00:07:28 +02:00

Owner

Originally created by @TheUltimateC0der on GitHub (Feb 9, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/310

Originally assigned to: @maziggy on GitHub.

Problem or Use Case

I don’t use Bambu Studio and don’t plan to in the future. Instead, I exclusively use the open-source alternative OrcaSlicer, and I keep it completely local – I do not have the Bambu Lab Cloud plugin installed.

Because of this, my printer, filament, and process profiles are not synced to the Bambu Lab Cloud. As a result, I’m currently unable to use bambuddy’s slicer presets feature, since it depends on profiles that exist in or are synced through the Bambu ecosystem.

In other words: users who rely solely on OrcaSlicer (without Bambu Cloud integration) have their profiles available locally, but cannot use them with bambuddy.

Proposed Solution

Add an option to import profiles directly from an OrcaSlicer export into bambuddy, without requiring Bambu Studio or Bambu Lab Cloud.

Ideally, bambuddy would:

Allow users to select one or more OrcaSlicer profile export files.
Parse the relevant data (printer, filament, and process settings) from those exports.
Expose these imported profiles as regular slicer presets inside bambuddy, so they can be selected and used just like cloud-synced profiles.

This would allow users who use OrcaSlicer standalone to benefit from bambuddy’s slicer presets feature, while keeping their workflow fully local and independent of Bambu Studio / Bambu Cloud.

Alternatives Considered

No response

Feature Category

Cloud Profiles

Priority

Critical for my use case

Mockups or Examples

No response

Contribution

I would be willing to help implement this feature

Checklist

I have searched existing issues to ensure this feature hasn't already been requested

Originally created by @TheUltimateC0der on GitHub (Feb 9, 2026). Original GitHub issue: https://github.com/maziggy/bambuddy/issues/310 Originally assigned to: @maziggy on GitHub. ### Problem or Use Case I don’t use Bambu Studio and don’t plan to in the future. Instead, I exclusively use the open-source alternative **OrcaSlicer**, and I keep it completely local – I do **not** have the Bambu Lab Cloud plugin installed. Because of this, my printer, filament, and process profiles are **not** synced to the Bambu Lab Cloud. As a result, I’m currently unable to use bambuddy’s **slicer presets** feature, since it depends on profiles that exist in or are synced through the Bambu ecosystem. In other words: users who rely solely on OrcaSlicer (without Bambu Cloud integration) have their profiles available locally, but cannot use them with bambuddy. ### Proposed Solution Add an option to **import profiles directly from an OrcaSlicer export** into bambuddy, without requiring Bambu Studio or Bambu Lab Cloud. Ideally, bambuddy would: - Allow users to select one or more OrcaSlicer profile export files. - Parse the relevant data (printer, filament, and process settings) from those exports. - Expose these imported profiles as regular slicer presets inside bambuddy, so they can be selected and used just like cloud-synced profiles. This would allow users who use **OrcaSlicer standalone** to benefit from bambuddy’s slicer presets feature, while keeping their workflow fully local and independent of Bambu Studio / Bambu Cloud. ### Alternatives Considered _No response_ ### Feature Category Cloud Profiles ### Priority Critical for my use case ### Mockups or Examples _No response_ ### Contribution - [ ] I would be willing to help implement this feature ### Checklist - [x] I have searched existing issues to ensure this feature hasn't already been requested

BreizhHardware

2026-05-07 00:07:28 +02:00

closed this issue
added the
enhancement
label

BreizhHardware commented

2026-05-07 00:07:28 +02:00

Author

Owner

@TheUltimateC0der commented on GitHub (Feb 9, 2026):

Maybe this could work with https://github.com/OrcaSlicer/OrcaSlicer/issues/9893 ?

@TheUltimateC0der commented on GitHub (Feb 9, 2026): Maybe this could work with https://github.com/OrcaSlicer/OrcaSlicer/issues/9893 ?

BreizhHardware commented

2026-05-07 00:07:28 +02:00

Author

Owner

@maziggy commented on GitHub (Feb 9, 2026):

This is a valid use case — users who run OrcaSlicer without Bambu Cloud shouldn't be locked out of preset management.

Interesting link to OrcaSlicer/OrcaSlicer#9893 — if OrcaSlicer adds Git-based profile sync, that could be a clean integration path. Bambuddy could pull presets from a Git repo the same way it currently pulls from Bambu Cloud. That said, it's still a feature request on their side, so we can't depend on it.

In the meantime, a more immediate approach: allow creating local presets directly in Bambuddy without requiring any cloud or external sync. You'd define filament presets with the relevant parameters (type, temperature, pressure advance, etc.) right in the UI, stored locally in Bambuddy's database. These would work exactly like cloud-synced presets for AMS slot configuration.

This would serve:

OrcaSlicer-only users like yourself
Anyone who wants quick local presets without cloud dependency
Users in regions with unreliable cloud connectivity

And if OrcaSlicer's Git sync does land in the future, we could add that as an additional import source.

Would that approach work for your use case?

@maziggy commented on GitHub (Feb 9, 2026): This is a valid use case — users who run OrcaSlicer without Bambu Cloud shouldn't be locked out of preset management. Interesting link to OrcaSlicer/OrcaSlicer#9893 — if OrcaSlicer adds Git-based profile sync, that could be a clean integration path. Bambuddy could pull presets from a Git repo the same way it currently pulls from Bambu Cloud. That said, it's still a feature request on their side, so we can't depend on it. In the meantime, a more immediate approach: allow creating local presets directly in Bambuddy without requiring any cloud or external sync. You'd define filament presets with the relevant parameters (type, temperature, pressure advance, etc.) right in the UI, stored locally in Bambuddy's database. These would work exactly like cloud-synced presets for AMS slot configuration. This would serve: - OrcaSlicer-only users like yourself - Anyone who wants quick local presets without cloud dependency - Users in regions with unreliable cloud connectivity And if OrcaSlicer's Git sync does land in the future, we could add that as an additional import source. Would that approach work for your use case?

BreizhHardware commented

2026-05-07 00:07:28 +02:00

Author

Owner

@TheUltimateC0der commented on GitHub (Feb 9, 2026):

Thanks a lot for the detailed answer and for considering this use case!

Yes, the approach of local presets directly in Bambuddy would already work for me. Being able to keep everything local fits very well with my workflow.

So from my perspective:

Short term:
Local, Bambuddy-managed filament presets would fully unblock my use case and already be a great improvement.
Long term / nice-to-have:
If OrcaSlicer’s Git-based profile sync (OrcaSlicer/OrcaSlicer#9893) ever lands, a Git integration or a direct Orca export import would still be very valuable to avoid maintaining the same data twice. Even a simple “Import from Orca export” be perfectly fine for me.

I’m happy to help test any implementation if that would be useful.

@TheUltimateC0der commented on GitHub (Feb 9, 2026): Thanks a lot for the detailed answer and for considering this use case! Yes, the approach of **local presets directly in Bambuddy** would already work for me. Being able to keep everything local fits very well with my workflow. So from my perspective: 1. **Short term:** Local, Bambuddy-managed filament presets would fully unblock my use case and already be a great improvement. 2. **Long term / nice-to-have:** If OrcaSlicer’s Git-based profile sync (OrcaSlicer/OrcaSlicer#9893) ever lands, a Git integration or a direct Orca export import would still be very valuable to avoid maintaining the same data twice. Even a simple “Import from Orca export” be perfectly fine for me. I’m happy to help test any implementation if that would be useful.

BreizhHardware commented

2026-05-07 00:07:29 +02:00

Author

Owner

@maziggy commented on GitHub (Feb 9, 2026):

Here we go.....first version is available in branch 0.1.9b. Please check and let me know.

Docs -> https://wiki.bambuddy.cool/features/local-profiles/

Can you please test, that the local profiles are working with the AMS slot assignments on printer card and in print/schedule modal?

@maziggy commented on GitHub (Feb 9, 2026): Here we go.....first version is available in branch 0.1.9b. Please check and let me know. Docs -> https://wiki.bambuddy.cool/features/local-profiles/ Can you please test, that the local profiles are working with the AMS slot assignments on printer card and in print/schedule modal?

BreizhHardware commented

2026-05-07 00:07:29 +02:00

Author

Owner

@TheUltimateC0der commented on GitHub (Feb 9, 2026):

Tested. Works!

@TheUltimateC0der commented on GitHub (Feb 9, 2026): Tested. Works!

BreizhHardware commented

2026-05-07 00:07:29 +02:00

Author

Owner

@maziggy commented on GitHub (Feb 10, 2026):

If you find Bambuddy useful, please consider giving it a ⭐ on GitHub — it helps others discover the project!

@maziggy commented on GitHub (Feb 10, 2026): ----- If you find Bambuddy useful, please consider giving it a ⭐ on [GitHub](https://github.com/bambuman/bambuddy) — it helps others discover the project!

BreizhHardware referenced this issue

2026-05-07 00:15:11 +02:00

[PR #194] [CLOSED] Feature/192 #960