- issue 385304:- Enabled VP8 denoising by default. To turn it off use the googNoiseReduction constraint.
- issue 346616:- Fixed issue with GetUserMedia, where 2 calls to GetUserMedia with different resolutions were resulting in same resolution.
hey Vikas,thanks!
- issue 385304:- Enabled VP8 denoising by default. To turn it off use the googNoiseReduction constraint.
Can you make that public please? Also note that denoising can sometimes generate artifacts, see https://code.google.com/p/webrtc/issues/detail?id=3807
- Issue 373690:- Fixed issue, now PeerConnection should be garbage collected after calling close().
It seems those are now removed from webrtc-internals which I find highly unfortunate. This makes it alot harder to snoop on other peoples usage of the peerconnection api!
- issue 346616:- Fixed issue with GetUserMedia, where 2 calls to GetUserMedia with different resolutions were resulting in same resolution.
<3https://code.google.com/p/webrtc/issues/detail?id=3249 seems to be missing from the list. Even more confusing, I still see lots of those kind of connections run into a timeout, but need to verify that with a proper test setup.
On Thursday, September 18, 2014 11:43:55 AM UTC-7, Philipp Hancke wrote:hey Vikas,thanks!
- issue 385304:- Enabled VP8 denoising by default. To turn it off use the googNoiseReduction constraint.
Can you make that public please? Also note that denoising can sometimes generate artifacts, see https://code.google.com/p/webrtc/issues/detail?id=3807Sure i will look into it.. That's right and issue 3807 is on track for M38.
- Issue 373690:- Fixed issue, now PeerConnection should be garbage collected after calling close().
It seems those are now removed from webrtc-internals which I find highly unfortunate. This makes it alot harder to snoop on other peoples usage of the peerconnection api!Now PeerConnection object is destroyed after Close(), it's also removed from webrtc-internals, since it removes any PC on destruction.
https://code.google.com/p/webrtc/issues/detail?id=3249 seems to be missing from the list. Even more confusing, I still see lots of those kind of connections run into a timeout, but need to verify that with a proper test setup.Thanks for bringing this up, checked with Mallinath that should have made to M37, feel free to respond on to that issue or file a new one if you still see the problem.
- Issue 373690:- Fixed issue, now PeerConnection should be garbage collected after calling close().
It seems those are now removed from webrtc-internals which I find highly unfortunate. This makes it alot harder to snoop on other peoples usage of the peerconnection api!Now PeerConnection object is destroyed after Close(), it's also removed from webrtc-internals, since it removes any PC on destruction.I think that's pretty annoying. Do you have anything to hide in hangouts? :-p
--
---
You received this message because you are subscribed to the Google Groups "discuss-webrtc" group.
To unsubscribe from this group and stop receiving emails from it, send an email to discuss-webrt...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.