Video streaming uses much higher CPU for streaming in v10.0.0-beta1
# Bug Report

### Describe the Bug
Hi @dgreif,

I wasn't sure if I should just comment in the other thread, but I thought it would be worth opening a new thread instead.  I've had pretty good success with the v10 beta of ring-client-api, but one thing that I have noticed is that the node process uses significantly higher CPU than the older streaming method.

For example, with 9.24.0, I can support about 7 actiive streams on an RPi4b with only some minor artifacts, 6 streams works pretty flawlessly.  CPU usage on the Node process approaches 100% but it handles it OK.

However, with v10.0.0, I can support about half as many streams on the same system.  3 streams seems to work OK, but if I start a 4th stream, CPU usage goes to 100% and artifacts begin to appear in the streams due to lack of CPU.  I'm curious if you have any ideas on why this might be.  The ffmpeg process are configured to just copy the stream to an RTSP server, no transcoding or anything, so the use for those per-stream is still quite low, it seems to be higher CPU usage in the RTP packet handling within the Node process itself.

I may be able to work around this by forking the streams off to separate node processes as it seems that the other cores have some CPU headroom, and perhaps I should do this anyway, but as it was demonstratably different with just chaning the API version back and forth I thought it might be worth mentioning as it was a surprise to me with the new streaming method that otherwise works exceptionally well.  It looks like the new code completely replaces the RTP packet handling code, so perhaps something in there isn't as efficient as the old code?

Ideally I'd love to figure out how to just consume the RTP streams directly, bypassing node for that part, and I feel like this should be possible, but I haven't had time to dig into it that much.  Happy to provide any more detail if it helps.

### To Reproduce
Just call camera.streamVideo() for multiple streams and monitor CPU usage with 9.24.0 vs 10.0.0-beta1

### Expected behavior
Similar CPU usage to prior API versions

### Environment
 - OS: Alpine container on HASS OS and Ubuntu 20.04
 - Node.js: 16.13.2
