Sound at end of galvo job, again

This morning I was running a bunch of coasters to give away as prizes at our park volunteer training, and once again I was a bit annoyed by the end-of-job sound on the two galvos I was running simultaneously. I know from the previous time this came up that the sound is a single sound baked into the executable with no way to change it, and I know there’s already a feature suggestion generally about it:

The thing is, it really does make my experience using LightBurn slightly but noticeably worse having only one sound versus what it would be in a world where I had some number more than one, and I’m sure I’m not the only such user. The population of people running multiple galvos simultaneously, on the other hand, is always going to be considerably less than even the general galvo-using population of LightBurn users.

I was just wondering, in theory with no commitment, how difficult would it be to, perhaps, just bake in… let’s say… three end-of-job sounds and add a UI element (in the machine settings?) to select between them? If it’s not something likely to be a huge time sink, could there be any way to get the idea onto a dev’s “Well, I don’t want to start something deep this late on a Friday…” list? (I don’t know that all devs have such a list, but I know I definitely do.) I mean, if it’d help, I’d gladly send along a genuine Louisiana king cake to show my appreciation. :sweat_smile: :grin:

I know it’s really low on the priority list, and I don’t expect we have nearly enough affected users who are also on the forums to amplify the request and vote up the feature suggestion in fider. I certainly do not want anyone to think I’m trying to jump the line and take away dev time from far more meritorious, more impactful, and more widely useful work. Just if it’s something that would be pretty trivial to implement (just providing a few baked-in sounds instead of the one), I wouldn’t want it not to exist just because nobody had ever really thought about it (or thought about it that way).

Anecdote: One of my projects is a bespoke Helpdesk system for our couple dozen techs, ~5000 staff, and 40k students’ families. Occasionally, I’ll hear one of our techs complaining about something trivial, like having to do an extra step before saving or some such, and within minutes, I’ve fixed the issue with a trivial patch. It annoys the tar out of me when I think about how much cumulative annoyance has resulted from such a trivial issue existing, sometimes for years, when it could have been ameliorated with trivial effort at any point if it just came to my attention.

I don’t know whether the potential for baking in just a very small plural number of sounds would be in the “uh, utterly trivial” or “well, actually more difficult than it would seem” bins, but if it’s in the former, the cumulative benefit would eventually compound to make it worthwhile, and if I could gently and graciously do the psst-look-over-there eyebrows to help it along, it would make my life more pleasant in a very small but significant way.

Also I’m not really completely joking about the king cake. If it’d make a dev smile to have edible appreciation, bribing with food does seem like a valid Louisiana tradition. :rofl:

2 Likes

Nathan,

I am sure others including myself would like to have an End_of_Cycle tone from the PC, like when the blue laser status bar disappears, like at 100% completion.

Make it a Feature Suggestion (https://lightburn.fider.io/) and people will vote on it. Enough votes and it moves to the top of the stack of programmer assignments.

Mikey

The fact there is a feature suggestion (linked above in my post, see the inline box labeled “lightburn.fider.io”) that gets no traction is rather most of the point of my missive, or at least that was among my intentions.

Also, no worries and I’m not offended or anything, but for the record, I’m so not a “Nathan”. Call me Nathaniel, call me Nate, call be Nick if you really want to, but please don’t call me “Nathan”. It’s just so rounded and lacking flavor in my (admittedly rather odd) head. :grin:

Major apology here! I have no idea why I did not finish typing it. I always try the use the name in the bio so I don’t offend anyone. Should not edit before first cup of coffee!

I believe I originally resisted because I was afraid it would promote not staying close to the laser while it is running. I still think that part is a major safety hazard. But I added my vote.

I agree about not staying near the laser being a major safety hazard, certainly. I would make the case that in my workflow (which does not involve moving away from the laser enclosures), having the same end-of-job sound may actually increase the hazard.

I was running coasters on two galvos: slate coasters on the MOPA fiber with a job time of about 9 minutes and cork coasters on the CO2 galvo with a job time of about 20 seconds. The MOPA is in the left enclosure with a left-hinged outswing door, and the CO2 is in an enclosure immediately adjacent and to the right, with a right-hinged outswing door.

Multiple times a minute, the tones play and I open a door, swap a coaster, and stomp the respective pedal to start the next coaster. Usually it’s the enclosure at my right hand, but once in a while, the same tones actually signal for the enclosure at my left hand.

Both enclosures are equipped with door interlocks that immediately stop the laser when the door opens while a job is in progress, and I obviously look before opening so I don’t interrupt a running job, but interlocks could fail and I could make a mistake during a few hours of constant work. Having distinct tones for the two would allow for bog-standard conditioned response to develop, reducing (but of course never eliminating) the potential of opening the wrong enclosure while a job is running.

I would therefore make the case that distinct end-of-job sounds would be a process optimization enhancing safety by adding one more layer in the Swiss cheese model of accident prevention.

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.