audiojs/audio-play

Play audio buffer in browser/node

audio-play's Issues

Make rate, detune and volume work for node

`speaker` package was not found. Using `audio-sink` instead.

Apparently installation fails due to "invalid syntax" somewhere in Python code.
The need to have Python installed is not documented, nor is which version of Python is expected.

nw.js and audio-play

I have been trying to play an mp3 under nw.js (26.2) in Windows, and haven't had any success. I rebuilt (node-gyp) the speaker module, giving it the correct nw.js version, but still no luck. My code is simple:

const playBeep = require('audio-play'); // npm module to play beep for configuration
const loadBeep = require('audio-loader');
.
.
loadBeep('./solemn.mp3').then(playBeep); // play the beep

But I would like to play multichannel wav files as well.
Has it been tested under nw.js, and is there something I should be modifying/adding?

Select output device.

Can I select where my sound will be played?

Find good npm name

The problem is that audio-play is taken by former play-audio, whereas play-audio is free-like.

I am going to write to @npm and @deathcap to resolve this, if possible, to make swapping.

Make rate etc writable

To change playback during the playback :inception_mem:

let playback = play(stuff)

playback.rate *= 1.1

Playing files over 100 kb large slows the rate arbitrarily

I'm using this package from an Electron application. As the title says, any files that are less than 100 kb in size play fine, but any over that get the playback rate cut in half as far as I can hear. This happens regardless of format.

Is there any reason for this happening, and is there a fix? Not exactly the optimal situation to have.

(node:36124) UnhandledPromiseRejectionWarning: Error: Argument should be an audio buffer

i am paasing array buffer and below error is happening please guide

(node:36124) UnhandledPromiseRejectionWarning: Error: Argument should be an audio buffer
    at Play (/Users/koenig/Documents/electron/TSP/node_modules/audio-play/index.js:12:36)
    at IpcMainImpl.<anonymous> (/Users/koenig/Documents/electron/TSP/main.js:29:18)
(node:36124) UnhandledPromiseRejectionWarning: Error: Argument should be an audio buffer
    at Play (/Users/koenig/Documents/electron/TSP/node_modules/audio-play/index.js:12:36)
    at IpcMainImpl.<anonymous> (/Users/koenig/Documents/electron/TSP/main.js:29:18)
(node:36124) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 2)
(node:36124) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 2)
^Ckoenigs-MacBook-Air-2:TSP koenig$ npm start

An in-range update of is-audio-buffer is breaking the build 🚨

Version 1.0.9 of is-audio-buffer just got published.

Branch	Build failing 🚨
Dependency	is-audio-buffer
Current Version	1.0.8
Type	dependency

This version is covered by your current version range and after updating it in your project the build failed.

is-audio-buffer is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

---

Commits

The new version differs by 2 commits.

• f6b4e6a 1.0.9
• 87f1f1a Remove needless dep

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

Can't play audio buffer returned from @google-cloud/text-to-speech

Google Cloud Text to Speech returns a response.audioContent which logs to console as:

<Buffer ff f3 44 c4 00 12 6a d5 44 01 41 10 01 c6 37 00 20 8c 6c 80 04 05 fe 84 6a 9c ef f3 9f 39 f2 10 9f e4 24 8d bf fc e7 79 cf 21 09 c9 53 9e 42 49 53 ba ... 4846 more bytes>

Running this:

let playback = play(response.audioContent);
playback.play();

Errors out with:

Error: Argument should be an audio buffer

Am I doing something wrong?

An in-range update of audio-lena is breaking the build 🚨

Version 1.1.3 of audio-lena just got published.

Branch	Build failing 🚨
Dependency	audio-lena
Current Version	1.1.2
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As audio-lena is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

---

Commits

The new version differs by 7 commits.

• f709b66 1.1.3
• 176a0c7 Remove greenkeeper
• eb21a39 Explain example better
• d502bb9 Add spec table
• efdebef Merge pull request #4 from audiojs/greenkeeper/initial
• 66b1414 docs(readme): add Greenkeeper badge
• 7041c5a chore(package): update dependencies

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

Please package pre-compiled version

I use create-react-app and one of my dependencies is audio-play. Sadly I can't build my create-react-app due to this error:

▶ yarn build
yarn run v1.6.0
$ react-scripts build
Creating an optimized production build...
Failed to compile.

Failed to minify the code from this file:

 	./node_modules/audio-play/browser.js:16

As per their instructions to resolve this it says

"Open an issue on the dependency's issue tracker and ask that the package be published pre-compiled."

So can we please have a pre-compiled version within the package?

Cann't play mp3: A decoder for .mp3 was not found.

It happened on Mac Big Sur and Windows 10.

List of files

how can i play list of .wav files sequentially

audio pitched down and mixed weirdly

When using NPM local mp3 audio gets pitched down and is mixed weirdly.

warning: Didn't have any audio data in callback (buffer underflow) on MacOS High Sierra

After playing a buffer, I get the following error.

play('testfile.mp3');

[../deps/mpg123/src/output/coreaudio.c:81] warning: Didn't have any audio data in callback (buffer underflow)

This error repeats in a loop.

CLI

For CLI would be nice to play any source audio-loader can play, as well as soundcloud etc.

play https://soundcloud.com/xxx

Just leave it here to cancel later.

mp3 playback speed is slowed down and it starts in the middle of the track

I'm on Mac OS (10.13.6) using nodejs (10.13). When I'm trying to play an mp3 file the playback speed is slowed down and it starts in the middle of the track.

I've tried multiple mp3 files from different sources - mostly all with the same outcome.
This is an example which is not working for me when I download it and try to play it locally.

The only file I actually could get to play as expected was a random test I downloaded here.

Unfortunately I don't know how to determine which audio library is being used to decode the mp3 files to provide further information.

gyp ERR!

When I try to install this library with

npm i audio-play

Then

node-gyp rebuild
gyp ERR! stack Error: Can't find Python executable "python", you can set the PYTHON env variable.

skip forward/backward

Would skipping forward/backward on the buffer fit inside the use of this module? For example player.forward(duration?)/.backward(duration?) Also taking into account when buffer is playing/paused.

If this is possible, it would be even cooler to potentially adapt the interface to streams. So for example it lazy loads over the network (buffers data as it plays), and if you skip forward it can compensate with loading that data, and with skipping backwards it could just refer back to what the stream has received.

Track currentTime better

In particular, browser time is tracked only when paused. Guess we can define sort of getter on playback object.