No worries. I have no doubt what you’re seeing is real, I just wish I knew why.
Another thing to know is MacOS has a “last one wins” approach to camera access. If there is a second app also trying to use the camera, then it could be changing the resolution. That will affect apps that already had the camera open, but because of the way MacOS works they don’t necessarily know about it. (it can quietly re-scale the image)
@JediJeremy
I’m testing with OBS, but what input format should I use for my 4 mp 85 degree LB camera?
As far as I can see there are no filters or effects applied.
hey sorry for the late reply, so the sv300-new is a ruida usb camera, our company and many others use, its mainly used with rdc6445g controller, head mounted and it reads either crosses our crop marks circle, I have moved over hundreds of our customers to lightburn but unfortunately some still need to use the camera, if there’s any way our company can help you all with this please let me know, I have some spare cameras here.
Issue with nesting. I tested it with some earrings. I had each earring grouped individually. When nesting to the rectangle it separated the inner parts of the earring. I had move as group and lock inner objects selected.
After 2 hours of testing (with standard/preselected input resolution), I can’t see any interfering filter or effect settings, nothing is activated. Filter/effects actually have to be actively selected in OBS before they are used.
I haven’t done the “blur test” with a person image, when the image is not blurred in OBS there is probably no need for it. ?
Switching between LB and OBS is surprisingly smooth, no problems with “getting” the camera from the respective, active program to the other.
Right now it looks a bit hopeless, I think. Do you have a plan B?
Can you reproduce the problem on your Macs, or is it just my 2 computers.
If I can be of any help in some way with testing or trying out ideas, I’m ready.
Those aren’t circles, they’re ellipses. I believe it only works with perfect circles.
They’re still not perfect circles. Hold down the shift key while dragging out the ellipse or select each one individually and ensure that the dimensions are the same in both width and height.
TY thank you - Ill try tomorrow, have to go..
Worked, when making them exactly perfect. 
Thank you
Did some poking around on the Galvo Z axis feature. 2 comments, in device settings no matter what you set the step distance at the bottom it only jumps 1 mm at the user interface buttons, so not a setting, only there for testing purposes I assume. Also don’t see anyway to reset the Z position counter back to zero.
Need some way to set distance like in Device settings and a Z position DRO would be nice.
Only bumps column 1mm at a time, unless I’m missing something, which is entirely possible. I know it’s a RC so just testing and reporting, not complaining. Appreciate all the work you all put into this stuff, Merry Christmas!
The mac version is still intel only. Any plans to release a version that runs natively on the computers released 5 years ago? Apple supported rosetta 1 for less than 5 years, so it seems kinda like you’re on borrowed time for rosetta 2.
This is awesome! I just tested this with my Commarker Omni X and managed to get it to work while in device settings with Motor 2 but when I ok and exit it keeps defaulting to Motor 1 and the up and down arrow buttons on the main interface don’t seem to work which I assume because Motor 1 keeps defaulting. Restarted the app after I saved and that didn’t seem to make it stick either.
Either way this is great to see us moving in this direction.
crash when importing camera settings
txt needs to be renamed to pdf
LB-Crach-RC1.txt (228.2 KB)
All the new features look really good, however, sadly another £100 for the pro licence upgrade for the nest feature as good and useful as it is, may be out side my budget.
You get a whole lot more for the $100, but not for the diode laser. I am starting to get Feature Envy myself.
Is there another spot to set the z axis homing direction and the steps per mm?
Totally fair to ask for a native Apple Silicon build — that’s a reasonable request in 2025.
Where I think your comment overreaches is the “borrowed time” conclusion. Yes, Rosetta 1 eventually went away, but that doesn’t automatically mean Rosetta 2 is about to disappear on the same timeline, or that Intel-only apps are nearing a hard cutoff right now. This is a future-proofing concern, not evidence of an imminent break.
Also worth separating two things:
In short: ask for native support, absolutely — but the “borrowed time” framing reads more alarmist than the situation warrants.
Great work to the dev team! I can confirm that this release and Falcon A1 Pro work well together!
I don’t think it should be that finiky..
