When updating Overlay screen becomes Green

Runnin OSX (Latest)and lightburn 1.703.

When my client updates overlay, the bed goes green. If he runs a camera app in OSX to test camera no issues. Camera seems to also be workrign fine in Lighhtburn, unitl; you select update overlay.

All calibrations were completed.


That’s something I haven’t seen before - what camera make and model are you using with your setup? Are you running the camera through Nvidia Broadcast or OBX, by chance?

@Colin ELP 16MP 180Degree. It works perfectly with Windows.

I will ask him about nvidia or OBX

I see two versions of that camera, one has an autofocus that won’t work reliably with LightBurn’s camera support. See if you can get the specific listing as well so we know exactly what model it is.

Also, if the camera stream is being locked down by another application, that could be a source of the issue.

@Colin It is not the autofocus one. I have it on about 20 windows systems with lightburn . No issues. First Mac

Usb16mp01
Brian

@Colin He said he is not using neither to connect to the Mac. Not Nvida or OBX

Hi Brian,

Could you have the user go to ‘Help > Enable Debug Log’, switch away from device to ‘No Machine’ or any other device profile in the laser window, then back again to the correct device profile (to restart camera). Then, update overlay, turn off debug log from the ‘Help’ menu, and send us the file that it produces to us?

The Debug Log will automatically save to My Documents on Windows or Documents on Mac, with the file name LightBurnLog.txt

Please email support@lightburnsoftware.com with a link to this thread for context, and the log file attached.

Our primary camera dev has an ELP 48MP camera that is working on our side; this debug log will help us find out what is happening when the camera is started up via LightBurn.

I will have him do that. Thank you

@Colin I sent the email in today, with the log, reference to this thread and the pics I posted above
. Thank you Brian

@Colin Are there any updates from support on the ticket I entered for this issue? #171818)