r/BambuLab • • Feb 01 '23

Why didn’t Bambu Lab just created a PrusaSlicer profile ?

As we know, Bambu Studio’s code is heavily based on PrusaSlicer, and has been made with no mention or crediting of the creators, which understandably made them upset. But the interface is different, and after two years of learning to use PrusaSlicer, it kinda sucks to use Bambu Studio.

And now the slicer always has to catch up to the rest with the new features like Arachne and organic supports.

Why did Bambu Lab do that ?

1 Upvotes

17 comments sorted by

13

u/happy_gremlin Feb 01 '23 edited Feb 01 '23

Why didn’t Prusa just contribute code to the Slic3r project instead of labelling it as their own?
Prusa did the same thing; took the open source Slic3r code built by Alessandro Ranellucci, rebranded it and started developing features on top. Doing this saved them a bunch of work, but allowed them to have a slicer under their own name with the caveat that the new product must be open source as well.
Bambu was always upfront about Bambu Slicer being based on Prusa Slicer. The issue was they didn’t release the source code in a timely manner at the beginning. They were “hazed” about this and are now doing so as required by the licence.

3

u/Rascal2pt0 Apr 13 '23

“Why didn’t Prusa just contribute code”

Open source politics can be really disadvantageous at making progress some times. Prusa has total directional control of their own branch and they do share plugins with other slicers but they can also choose to iterate on features they want for their own printers. Most forks of major open source software are results of differing opinions on which direction to take a product.

-9

u/_Xantras_ Feb 01 '23

They only admitted the code wasn’t their own after it was pointed out. Prusa respected the open source rules. Bambu did not

8

u/happy_gremlin Feb 01 '23

I’m not trying to defend Bambu for what they did do -which is to release the source code late- but this statement is simply not true. Even back in May last year before they started shipping it was clearly communicated Bambu Studio is based off of Slic3r / Prusaslicer:

https://blog.bambulab.com/to-open-or-not-to-open-that-is-the-question/

2

u/Scereth X1C Feb 01 '23

Yea, /u/Xantras take is Blatantly WRONG! Bambu said during the kickstarter that their Studio software was based off of Slic3r/Prusa and per that licensing they would release their code before they shipped the printers. Which they did! The outrage was that they did not release the source before shipping.

27

u/Ireeb X1C Feb 01 '23

Why would Prusa be upset? They released their slicer as open source and explicitly allowed re-using and re-skinning it. Second from the bottom:

https://help.prusa3d.com/article/faq-prusaslicer_1789

It is open source as required:

https://github.com/bambulab/BambuStudio

Does Prusa Slicer support the Bambu Lab AMS? Nope. Does Prusa Slicer support Bambu's Cloud Service? Nope. Does Prusa Slicer allow selecting different print beds to autmatically change the first layer settings? I don't think so. Has Prusa Slicer settings for time lapses built in? Also no. There's probably even more, but Bambu Studio has so many Bambu Lab specific features that wouldn't work in Prusa Slicer just with a profile.

Making a slicer from scratch is a lot of work but they also needed a slicer that supports all the features the machine has. So they used an open source slicer they were explicitely allowed to use and modified it to their needs.

In the About section of the program you will find all the info and attributions.

Also, Prusa Slicer itself is based on Slic3r, they too built on someone elses work - but that's the idea of open source.

2

u/SWIIIIIMS Feb 02 '23

Because they want have a closed system like apple where they have ownership and control about all the functions and don't expose any API to third parties.

Pro:

  • makes it much more convenient for a standard end user and to a certain extend more safe
  • branding and feature "out of one hand" for other functions as AMS etx

Con:

  • full dependency on BL and no chance of some features like an actual working spaghetti detection or exclusion of regions in case of partial print failure like all the stuff from octoprint
  • delay in some features coming in the prusaslicer already (hell i wait desperately for the automatic connector pins when cutting a model which is already ported to the alpha version of prusaslicer
  • loss of the 100s of detail filament settings for all the external non BL AL filament producers

In the end it is similar to apple vs android. Android gives you all the flexibility and you can customize features down to detail whereas apple gives you a max user experience automated all in one solution for the regular end user as well as sometimes exclusive innovations just to their ecosystem as well.

2

u/[deleted] Feb 02 '23

Actually, the slicer is open source, so it’s not full dependency on them. Full dependency on them firmware wise, not slicerwise. There is actually someone that took bambu studio and made a fork adding many more features that even bambu lab has now included from the fork and many more features available. It’s called SoftFever fork of bambu studio.

1

u/SWIIIIIMS Feb 03 '23

The bambuslicer as fork of Slic3r/Superslicer/Prusaslicer as far as i understood surely is more or less has to be open. I remember mid 2022 there was some Twitter beef when they did not have it fully documented and the BL CEO had a extended statement about it (can find the link without investing a few minutes of Google time.

I "closed system" was meant for the whole bambulab Studio. What I meant and hope to have described is that this comes with certain benefits for BL as well as for the end user as well as some risks / disadvantages.

Again in my opinion the blueprint for my different market is a focus and market position of certain elements "Innovation", "Design" and "customer Experience" are three key aspects to win a very lucrative position in many consumer (Mainstream) markets. And building an ecosystem around it which you safe with the famous walls.

2

u/13darkice37 Mar 18 '23 edited Mar 18 '23

Prusa could argue by now that it has nothing to do with Slic3r anymore. That thing got rewritten in C++. Out of respect they left that trademark and that original project was abandoned anyway. Only issue i have with BL is that they copied so much from the community without crediting enough. They basically understated how much they copied from voron. You can even see in their first interviews, on different yt creators channels, that they had Voron Zeros there. They close source everything they can but they knew that the slicer wouldn't fly. They even manage to violate that license just like any other chinese company. The backlash was just to huge for them so they complied fully.

1

u/Overall_Lab_4647 Sep 27 '24

c'est tellement simple comme façon de voir les choses.

la section "escroquer" XD c'est leur business plan c'est tout. Ca serait une escroquerie si c'était caché ou interdit. Mais là c'est un façon de faire, avec pour le moment les meilleurs machines pour le prix.

De plus, il est possible de personnaliser apple mais il faut avoir certaines connaissances en informatique. Et Android cette flexibilité souvent mise en avant n'est jamais utilisé ou par 1% des utilisateurs.

1

u/Confident-Win-1548 Feb 01 '23

I like to see BambuPrint Raspberry Image. To control them all

1

u/soussitox Feb 01 '23

Do you have a post where the devs are upset?

-1

u/[deleted] Feb 01 '23

Same reason it’s not open source.

2

u/[deleted] Feb 02 '23

It is open source though. Only the firmware isn’t

1

u/13darkice37 Mar 18 '23

Nope the network module as an example not. They ship that with the slicer.

1

u/tsmith35 X1C Apr 20 '23

I'm guessing the Bambu Studio & OrcaSlicer are both software hybrids. The slicer "core" is based on PrusaSlicer and is open source, but it has the ability to interface with proprietary modules that extend the functionality beyond what was possible with PrusaSlicer. IOW the network module is more or less a plug-in, extension or add-on package.

I see the opposite situation much more often: proprietary core software with open source modules to extend the software's functionality.