Evaluate LightBurn Early Access beside the stable installation and open separate copies of your projects. Preserve the approved source file, settings record and expected output before trying new features. A recoverable test starts with a known way back to the job that already works.
LightBurn's 2.2 RC1 Early Access announcement explicitly allows installation alongside the official release. That provides a practical evaluation route, but it does not guarantee that files saved by the new version will reopen identically in an older one. These features have not been tested here on TYVOK hardware.
Protect the production inputs first
Choose one representative project with a known accepted result. Save its approved file in a clearly named location, then create a separate evaluation copy. Include any linked data or images needed to reproduce the job. A copied project is less useful if the original CSV or source image later changes underneath it.
Record the stable application version, selected device profile, job origin and material setup. Keep a photograph or retained sample that shows what acceptance means. This is especially helpful when a new layout tool changes positions without obviously changing the artwork.
A reversible X1S Pro evaluation
- Confirm the stable application still opens the approved project correctly.
- Install the optional Early Access build according to LightBurn's instructions and identify the two applications clearly.
- Open only the evaluation copy in the new build. Verify the application version before editing.
- Test one feature with known geometry and save under a new name.
- Compare the resulting preview with the recorded baseline before considering supervised material testing.
- If the result is unsuitable, reopen the untouched approved file in the stable application. Do not use the RC-saved file as your only rollback copy.
Keep both applications from simultaneously controlling the same laser. The purpose of retaining two installations is a recoverable choice of environment, not competing connections to the machine.
Define what would justify a change
The TYVOK X1S Pro is presented for large-format workshop use with LightBurn support. That does not qualify every Early Access feature for your controller, accessories or existing jobs. Maintain the approved stable production workflow until a specific change has been evaluated against your own requirements.
First separate update entitlement from Pro edition requirements. Then compare the actual job behavior, including travel order after a software change. The useful result is evidence about a particular job, not a blanket statement that the new version is better.
If the feature being explored is software integration, remember that API status does not replace supervision. Keep initial evaluation read-only and retain direct observation for every machine run.
Is a copy saved by RC1 sufficient for returning to stable?
Do not rely on it. New features or file representations may not behave the same in an older release. Keep the original stable project untouched and make changes only in a separately named evaluation file.
Must I test every new feature before continuing normal orders?
No. Keep normal orders on the proven workflow. Evaluate only the feature that solves a real need, using copied inputs and a defined acceptance check. Optional Early Access testing should remain separate from customer deadlines.
