opus-stream-decoder | Instantly decode Ogg Opus audio streams in chunks | Binary Executable Format library

by AnthumChris JavaScript Version: 1.2.7 License: No License

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | opus-stream-decoder Summary

opus-stream-decoder is a JavaScript library typically used in Programming Style, Binary Executable Format applications. opus-stream-decoder has no vulnerabilities and it has low support. However opus-stream-decoder has 8 bugs. You can install using 'npm i opus-stream-decoder' or download it from GitHub, npm.

OpusStreamDecoder is an Emscripten JavaScript WebAssembly (Wasm) library for immediately decoding Ogg Opus audio streams (URLs or files) in chunks without waiting for the complete file to download, copy, or read. libopusfile is the underlying C library used for decoding. OpusStreamDecoder provides a lightweight JavaScript API for decoding Opus audio streams at near-native speeds.

Support

Quality

Security

License

Reuse

Support

opus-stream-decoder has a low active ecosystem.

It has 103 star(s) with 21 fork(s). There are 6 watchers for this library.

It had no major release in the last 12 months.

There are 6 open issues and 10 have been closed. On average issues are closed in 5 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of opus-stream-decoder is 1.2.7

Quality

opus-stream-decoder has 8 bugs (0 blocker, 0 critical, 8 major, 0 minor) and 0 code smells.

Security

opus-stream-decoder has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

opus-stream-decoder code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

opus-stream-decoder does not have a standard license declared.

Check the repository for any license declaration and review the terms closely.

Without a license, all rights are reserved, and you cannot use the library in your applications.

Reuse

opus-stream-decoder releases are not available. You will need to build from source code and install.

Deployable package is available in npm.

Installation instructions, examples and code snippets are available.

It has 156 lines of code, 0 functions and 7 files.

It has low code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi has reviewed opus-stream-decoder and discovered the below as its top functions. This is intended to give you an instant insight into opus-stream-decoder implemented functionality, and help decide if they suit your requirements.

Opstream decoder .
Opens an OpusAudio stream .
Update global cache
Get a function that is used to define a function call to its function .
call c function in C constructor
Convert a string value to a string
Wrap a function in a wrapper function that returns the result of the function call .
Converts a UTF8Array to a String .
Converts a UTF8 buffer to a UTF8 string .
Convert a string to UTF8Array .

Get all kandi verified functions for this library.

opus-stream-decoder Key Features

No Key Features are available at this moment for opus-stream-decoder.

opus-stream-decoder Examples and Code Snippets

No Code Snippets are available at this moment for opus-stream-decoder.

Community Discussions

Trending Discussions on opus-stream-decoder

Sound scheduling issue when playing OPUS from websocket

QUESTION

Sound scheduling issue when playing OPUS from websocket

Asked 2020-Nov-15 at 10:07

I'm trying to use the library https://github.com/AnthumChris/opus-stream-decoder/

I have a stream of OPUS encoded sound (2ch, 48kHz) from a high quality microphone (but I play a music in loop on it to test this). I know it works because I can hear it if I use:

websocat --binary ws://third-i.local/api/sound - | mpv -

(It's opening the websocket and streaming its output to mpv (mplayer)).

But when I play in the browser all I hear is very small parts of the sound every second or so. But the sound itself sounds good (I believe it is a very small part of the music).

Here is the JS code I wrote to listen in the browser:

...

ANSWER

Answered 2020-Nov-15 at 10:07

The problem of scheduling is due to the fact that you create the AudioContext at the same time that you create the WebSocket, thus adding the connection time to the AudioContext's scheduling.

In other words, when you create the AudioContext the scheduling is started immediately but since the AudioContext is created when the WebSocket is created (which only starts connecting), the scheduling is off by the amount of time it takes to the WebSocket to connect to the upstream and receive the first bytes.

This is your code fixed:

Source https://stackoverflow.com/questions/64663507

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install opus-stream-decoder

Emscripten is used to compile the C libraries to be compatible with WebAssembly. This repo was tested with 1.39.5.
Emscripten Installation Instructions
The Emscripten module builds in a few seconds, but most of the work will be spent configuring the dependencies libopus, libogg, and libopusfile. You may see the warnings (not errors) below, which don't prevent the build from succeeding. It is not known whether these warnings adversly affect runtime use.
Don't have the functions lrint() and lrintf ()
Replacing these functions with a standard C cast
implicit conversion from 'unsigned int' to 'float'

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: