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
How to set a .wav or .mp3 sound event? #502
Comments
Apologies for the slow response. This is not currently possible, the only sound you can play is via the Tcl "bell" command. Playing user-defined sounds (from a .wav or .mp3, etc) would require an external library and additional code, and is something I've not gotten around to yet (see #31) |
If you're on a posix OS, you can use this in a global event's 'Replace' parameter:
Substitute whatever one-off command line audio player and audio file you desire. For a simple beep, this works:
|
THANK YOU SO MUCH
…On Tue, Aug 27, 2019 at 9:45 AM CyberLeo ***@***.***> wrote:
If you're on a posix OS, you can use this in a global event's 'Replace'
parameter:
[[/eval exec {*}["/usr/bin/play" "/path/to/sound.wav"] &; list][/get 0]]
Substitute whatever one-off command line audio player and audio file you
desire.
For a simple beep, this works:
[[/eval bell -displayof .][/get 0]]
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#502?email_source=notifications&email_token=AKJAA2ALPWTXG3FVVQABSXTQGUVXXA5CNFSM4FUCF5FKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5HZENY#issuecomment-525308471>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AKJAA2GS643GR6YYIM4XIALQGUVXXANCNFSM4FUCF5FA>
.
|
Is it possible to have the client play a sound file when an event happens?
I don't see anything obvious when I look at the events window. Am I missing something or is this not a feature? Please point me to where it's possible, if so.
With only visual cues, I still feel like I miss stuff happening in a busy room; I would like to attach sound cues to certain events and character names, etc. Thank you!
The text was updated successfully, but these errors were encountered: