Skip to content
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

not working in windows 10 x64 #39

Closed
ferdiozer opened this issue Nov 5, 2019 · 9 comments
Closed

not working in windows 10 x64 #39

ferdiozer opened this issue Nov 5, 2019 · 9 comments

Comments

@ferdiozer
Copy link

const player = require('play-sound')();

player.play('alert.mp3', (err) => { if (err) console.log(Could not play sound: ${err}); });
Error: Couldn't find a suitable audio player
Error: INFO: Could not find files for the given pattern(s).

Thank you

@kot-shrodingera
Copy link

You need to install compatable console player (mplayer for example) and make it available in the shell (add mplayer folder to %PATH%)

@ferdiozer
Copy link
Author

image

image

I can not.
i guess i couldnt

@kot-shrodingera
Copy link

If you go to your project directory in cmd and type mplayer alert.mp3 is it playing?

@ferdiozer
Copy link
Author

image

Yeah, it's ringing. It does not work anymore. It worked when I turned on the computer again. Thank you

@ferdiozer
Copy link
Author

image
Is that the right thing?
system variables?
or user variables?

@kirax999
Copy link

kirax999 commented Apr 9, 2020

I found a solution if other people have the same error

download mplayer in https://mplayerhq.hu/design7/dload.html scroll for middle page and download "windows Binaries" after download please uncompress

and copy mplayer.exe in main directory project

play-sound not use path in windows just search in main directory project

@unional
Copy link
Contributor

unional commented Jan 7, 2022

The issue for Error: INFO: Could not find files for the given pattern(s). is caused by find-exec.
1.0.2 fixed it, but right now play-sound pinned to 1.0.1

@shime
Copy link
Owner

shime commented Jan 8, 2022

I've just published a new version that should fix this issue. Thanks for reminding me, @unional.

@shime shime closed this as completed Jan 8, 2022
@unional
Copy link
Contributor

unional commented Jan 8, 2022

Thank you! :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants