Home Articles Forums Gallery Marketplace Videos

WoodCentral Forums

Knowledge You Can Build On — Est. 1998

Price drop on over 1300 Rockler items

AI is being used to build open-source, clean-room alternatives to Adobe's software suite

Posts

AI is being used to build open-source, clean-room alternatives to Adobe's software suite

#1

Peter Martin

https://youtu.be/O4leOGek6ww?si=stA1xPcNre89gP0y
This video explores how AI is being used to build open-source, clean-room alternatives to Adobe's software suite, driven by user frustration with Adobe's predatory subscription model and cancellation fees.

  • Founder Brandon Thomas launched a collection of open-source tools—including PhotoCraft, VectorCraft, and FilmCraft—written in Rust. These are built using AI to perform black-box reverse engineering based on public specifications, ensuring no original Adobe code is copied.

  • The host successfully tested FilmCraft for a video edit, noting it is remarkably stable for alpha-level software, despite some minor UI bugs.

  • Beyond creative software, the video highlights the use of AI-assisted tools like REA (Reverse Engineer Anything) to speed up the process of recompiling classic console games for modern PC hardware, citing examples like Wind Waker and Halo Wars.

  • The host acknowledges valid artist objections regarding AI models trained on copyrighted data and the potential for legal risks, particularly from companies like Nintendo regarding game recompilations.

Re: AI is being used to build open-source, clean-room alternatives to Adobe's software suite

#2

What is a "clean room alternative?"  In my world, "clean room" actually means something.  I suspect in this case it doesn't.

Re: AI is being used to build open-source, clean-room alternatives to Adobe's software suite

#3

admin

@John in NM, 

A clean-room alternative is a piece of software built to do the same job as an existing product without copying its code, so the new work is legally and provably independent of the original.

The method comes from a classic legal safeguard. Copyright protects the specific code someone wrote, not the idea of what the software does or how it behaves from the outside. So a team can lawfully replicate behavior as long as they never copy the implementation. The tricky part is proving they didn’t copy it, and that’s where the “clean room” comes in. The traditional approach splits the work between two groups:

  1. The spec team studies the original product (using it, testing it, reading public documentation, sometimes examining its inputs and outputs) and writes a detailed functional specification describing what it does, but includes no code and no copied expressive details.

  2. The implementation team has never seen the original code. They build new software from the spec alone.


Because the people writing the code never had access to the original, the company can later show that nothing was copied, even by accident. The most famous example is Compaq’s reverse-engineering of the IBM PC BIOS in the early 1980s, which let them sell IBM-compatible computers without infringing. Phoenix Technologies later did the same thing commercially, and Sega v. Accolade and Sony v. Connectix are court cases that helped establish that this kind of reverse engineering for compatibility can be lawful.

In the AI version described, the interesting question is how the separation works. A human clean room relies on the implementers being ignorant of the original code. An AI model, though, may have been trained on huge amounts of code, possibly including the very software being replicated or similar projects, so it’s harder to claim it has never “seen” the original. Projects doing this typically try to get around that by having the AI work from documented file formats, public specs, and observed behavior rather than from leaked or proprietary source. Whether that holds up legally is still an open and debated question, since courts haven’t really tested it.

Also worth noting that “clean-room” doesn’t mean the result is automatically free of risk: patents are a separate issue (clean-room methods only address copyright and trade secrets), and trademarks and file format licensing can also come into play.

Re: AI is being used to build open-source, clean-room alternatives to Adobe's software suite

#4

Pretty ironic.  In order to describe code that is independently developed and supposedly not pilfered, they have co-opted a word that means something completely different as originally defined.

× Share

Share on

✉ Email this page