Mac version: fwrite takes too long

[renzhilan]

Hi, I installed the virtual camera service in the Mac version, and then tried to write a 2m pixel fwrite (buffer, buffer_size, 1, proc) each time, but it took about 200 milliseconds, causing the picture to get stuck. What's the reason,

[hipersayanX]

The delay is because the plugin needs to convert the source frame to the destination frame, the higher the resolution of the frame, the slowest it will get.

[renzhilan]

The same pixel size of 2M does not freeze on the window version, but it freezes on the mac version.

[hipersayanX]

I freezes completely, or it just lags?

[renzhilan]

The streaming time has slowed down. It takes about 100ms to write a frame
fwrite(frameRGBBuffer, bufferSize, 1, outputStream);

[isomov]

Hi! Is there any way to send frames to virtual camera without pipe?

[qing-wang]

One of the bottlenecks is the std::vector used in VideoFrame. The allocation of vector objects costs a lot of time. I have made a modification which improves this.

[qing-wang]

The streaming time has slowed down. It takes about 100ms to write a frame fwrite(frameRGBBuffer, bufferSize, 1, outputStream);

Based on my profiling, write seems fast enough, the bottleneck is the frequent memory allocation.

[hipersayanX]

@qing-wang I know, I must find some time to port the video converter from Webcamoid to the virtual cameras.

[jbain]

I'm seeing AKVCamManager consuming 85% cpu and can't get past 21fps

I assume this might be related to this issue? Or should I open a new issue? I'm using 9.11 on a intel mac