tsightler

Closing as it's not the actual problem. Will eventually address in a future update.

Here is a [test video](https://drive.google.com/file/d/1Fi-EYnFt_JrapB6rrMjbp297XA_lidDd/view?usp=share_link). With 0.20.2 the behavior did improve. Before that this video would almost always start off with a black screen for about 10-12 seconds, but with...

I don't know the answer to your question, but my project uses werift via a dependency on another project and, since the switch to werift, I've struggled to determine if...

Yep, I'm pretty familiar with Scrypted, have also run it myself. I think we might just have different definitions of "runs great", I would consider it as "runs sufficiently", probably...

Fair enough, I didn't say that was for sure the issue, it was just the only obvious differences in the traces compared to the previous RTP code I was using,...

Receiving. Basically, my use is via ring-client-api, receiving streams from Ring and piping them out via RTSP. Overall, werift works fairly well with this use case, but CPU use is...

I've been recently playing with using werift directly exactly for that reason (rxjs) but, so far, I haven't found that to be a huge part of the overall performance issue....

I had hacked around a little with this wrtc build: https://www.npmjs.com/package/@cubicleai/wrtc But I don't really want to do all the work to move because I've also found it quite buggy...

> Taking a look at the js profiler, the werift nack loop is unnecessarily running 200 times per second, even when there is no packet loss. The top `anonymous` hit:...

The current version in develop branch on Github is 0.17.6, see https://github.com/shinyoshiaki/werift-webrtc/blob/develop/packages/webrtc/package.json It's also published via NPM, you can see all NPM published versions here: https://www.npmjs.com/package/werift?activeTab=versions The ring-client-api code is...