Native CAD files on the BEAM.

cadmpeg reads the formats a shop actually has — SolidWorks .sldprt, CATIA .CATPart, Inventor .ipt/.iam, Creo, NX, Fusion .f3d, FreeCAD .FCStd, Rhino .3dm, IGES, STEP, Creo View, OpenUSD — into one format-neutral CAD IR, and writes that IR back out. This is a binding of it, so the same job is a function call rather than a translator process.

{:ok, document} = Cadmpeg.open("bracket.sldprt")
{:ok, _report} = Cadmpeg.Document.write(document, "step", "bracket.step")

A document is a value, and the geometry is a resource

open/1 reads a file once and answers a Cadmpeg.Document holding the parsed document. Every other call takes that handle, so the file is parsed once however many questions follow, and — because a B-rep never changes — one handle serves every process on the node. It cannot be sent to another node: the document is local.

What the formats are, and what they are not

formats/0 answers what this build reads and writes. cadmpeg's codecs are compiled in by feature, so a build without the SolidWorks codec cannot read a .sldprt and says so instead of guessing — the list is a fact about the binary in the VM, not a promise.

Support is a ladder, one level per format: a file that reads is not a promise that every feature was transferred. That is what the decode report is for, and it is why open/1 answers the report beside the handle: "it opened" and "it opened faithfully" are different answers.

Limits, said out loud

• The document is read-only here. cadmpeg's IR can be edited, and this binding does not expose editing yet: Cadmpeg.Document.to_json/1 is the way to a document a caller can change, and from_json/1 the way back.
• A decode is a best effort within cadmpeg's own ladder. A refusal arrives as Cadmpeg.Error with the code "refused" and the loss that caused it; it is not retried at a laxer policy, because that would change the answer silently.
• Assemblies are documents too: the parts, their occurrences and their placements are in the IR. Walking them is not exposed yet.