-
-
Notifications
You must be signed in to change notification settings - Fork 448
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Audio Cues for printer paused and finished in browser #520
Comments
Indeed, this can be added to Fluidd or any other Klipper interface, but I do wonder if using the native support in Klipper isn't a preferred method (as that will work even if no graphical interface is connected!) In the case of Fluidd, for this to work it would mean that you have a computer with the browser pointing to Fluidd and that the audio is not mute... 🤔 |
The buzzer won't work for some users (me included), my printer isn't in the same room as me so I can't hear it. I do think having a browser notification sound would be useful, for me Fluidd is constantly open while printing anyway. |
That's a fair point... given that, I wonder if we shouldn't just look into browser notifications instead and let the host Browser/OS handle it for us! If we go this way, we might just use the vue-native-notification to help out! |
I'm agree with @pedrolamas we must use the native notification. |
Related: #129 |
I started toying with this by adding
to statustab.vue. Works well, but needs more tweaks to know if the job just completed vs a page refresh. Unfortunately, as a vanilla JS guy, all this typescript + hardcore linting is killing my soul 😄 |
Closing in favor of #129 |
Is your feature request related to a problem? Please describe
when printer goes in pause because of fillament runout or a M600 and printer is not near the user watching on browser
it can go by unnoticed and ruin some prints
Describe the solution you'd like
upload sound files or pick between built in sounds to play when printer is done or paused
Describe alternatives you've considered
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: