-
Notifications
You must be signed in to change notification settings - Fork 172
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
adding configurable target bitrate #11
Conversation
Thanks for the great contribution! Can I suggest a few changes before I merge it?
|
Sure thing. Good catches. |
* moved bitRate inside recordOpus * added documentation to README.md * fixed casing for bitRateLocation
That should do the trick. |
Thanks, after those changes the example.html page stops working. Do you think we really need it in the example? Edit, the example is working. My bad |
If you want me to drop it from the example I'm happy to do so. Just lemme know. |
Adding configurable target bitrate
I've got one more commit where I remove the configurable bitrate from the example.html page – feel free to pull in lepinsk/Recorderjs@8527797 if you want it. |
Nah, lets keep it. On 28 April 2015 at 20:14, Julian Lepinski notifications@github.com wrote:
|
Sounds good – for the record, I was a bit confused by the dual use of |
Yes, good point, I agree the dual bool/config is not clear. For future versions, I might drop the wav support. Most people who are interested in this project seem to be interested for the opus encoding. |
I've tried to stick close to the coding style used throughout the project.
Rather than fall back on a default target bitrate in
recorder.js
, ifnew Recorder
is initialized without a bitrate key in the configuration object, the bitrate simply isn't set (which means the encoder goes with its default). I figured this was the best course of action, given that the encoder has different default bitrates depending on the selected encoder application.