Hi there,
The startup chime of the app should respect the mute settings of my system, and moreover go through headphones if they are the selected output (all the other PG application sounds do). In some environments having this sound blast through the speakers is /very/ undesirable but there is no way for me to stop it short of not starting the app at all.
I wouldn't mind being able to completely disable it, as well.
Version 2.5.582 on 10.14.2 (18C54).
Thanks,
-Laurens.
Startup chime shoul respect mute / headphone preference
Re: Startup chime shoul respect mute / headphone preference
OK, for anyone else who wants the startup chime to go away: I don't know for other platforms but on Mac you can easily silence it.
Follow these directions at your own risk; also, after updating PGS (let's keep hope!) you will have to do it again I expect.
Follow these directions at your own risk; also, after updating PGS (let's keep hope!) you will have to do it again I expect.
- Shut down PGS
- Find the Playground application (most likely in /Applications); Right click -> Show Package Contents
- Navigate to Contents / Resources / assets / audio / wav /
- Select snd_open_app.wav and press [cmd]-d (Duplicate) or use context menu
- Open snd_open_app.wav in Audacity or similar
- [cmd]-a ; delete to make an empty (silent) wav file of the correct length
- save file as a .wav to the same location and name (snd_open_app.wav)
- sw1tch73ch
- Posts: 539
- Joined: Tue Oct 18, 2016 1:23 pm
Re: Startup chime shoul respect mute / headphone preference
I like your solution, Laureness. Interestingly, my chime does go to the headphones. I didn't do anything that I know of to send it there.
== Just keep playing. Just keep playing. Just keep playing, playing, playing! ==
-- jbs --
-- jbs --
Re: Startup chime shoul respect mute / headphone preference
Ha, that's interesting. It's caused a few embarrassing moments here
Also tried and look for the cursor / "moving line" graphic to solve an issue in another thread, but alas, that's not so easily accessible.
Also tried and look for the cursor / "moving line" graphic to solve an issue in another thread, but alas, that's not so easily accessible.