-
Notifications
You must be signed in to change notification settings - Fork 33
input sample rate should not be used as the decoder rate #20
Comments
I'm not sure if in node there is a way to determine the device sample rate and implement the logic as specified in the xiph wiki:
|
That's indeed an issue, |
Pushed #21 to npm, so this should be fixed. |
(Oh, and thanks for reporting it!) |
Hi, On Nov 7, 2016 1:29 PM, "Mikko Rantanen" notifications@github.com wrote:
|
Oh dammit. The publish hadn't gone through for some reason or another and I didn't actually confirm the message. Published now again - and this time I actually read what npm publish said in the end. :) |
Hehe, On Nov 7, 2016 8:21 PM, "Mikko Rantanen" notifications@github.com wrote:
|
Hi, Thanks,
|
Oh crap. So sorry for that! Doing a git rebase really shouldn't have been that hard. For some reason I completely forgot that, being all satisfied with just fetching the merge. Okay it finally should be there. At least this.emit( 'format', {
channels: this.channels,
sampleRate: this.rate,
...
this.encoder = new OpusEncoder( this.rate, this.channels ); .. and it even seemed to pull that off npm instead of using some pre-existing |
And it works great now!!! Thank you! Rotem
|
Glad to hear. Sorry for the delays again! |
https://github.com/Rantanen/node-opus/blob/master/lib/Decoder.js#L57
The sample rate defined in the header here is strictly informational and should not be used to determine the decoder sample rate (nor encoder). See https://wiki.xiph.org/OggOpus#ID_Header
The text was updated successfully, but these errors were encountered: