Laurent Denoue

Yes and so I would need to change the accepted video codec in https://github.com/pion/webrtc/blob/master/examples/rtp-forwarder/main.go to specify H264 instead of the current VP8. Thanks!

Follow up: if I limit my frame sizes I send to max 540 pixels (in either width or height), then it runs fine. Have others seen issues? Do you know...

More info: specifying "VP8" (or "VP9") as the preferred encoder solves the issue. Not sure why H264 fails on MacOS. ``` private static let factory: RTCPeerConnectionFactory = { RTCInitializeSSL() //...

@anthonynevo I'm on macOS Monterey 12.4 (21F79) and iOS 15.4.1 (on iOS H264 works).

I updated my package to use the latest 103.0.0 but it still does not work unless I explicitly specify VP8 in `videoEncoderFactory.preferredCodec = RTCVideoCodecInfo(name: "VP8")`

@card-b Does this work even when the incoming WEBRTC video size changes during the session? It's not uncommon that during a session, the video changes from e.g. 640x480 to 160x120....

Love this idea. I developed a native Mac/Windows app called Screegle https://www.appblit.com/screegle that allows a user to select one or more windows during a screen sharing session, and overlay them...

@eladalon1983 yes `zOrder` is useful (currently, the demo first paints all selected window at their last seen position, and then paints over them the recently found windows, so z-order works,...

I get the same error: 937/937 [==============================] - 458s 488ms/step - loss: 0.0376 - acc: 0.9922 - val_loss: 0.0496 - val_acc: 0.9975 Epoch 00001: val_acc improved from -inf to 0.99750,...

I "fixed" the problem by removing the validation computations in fit_generator, as such: ``` #history = model.fit_generator(train, steps_per_epoch=len(trainitems) // train_batch_size, #validation_data=val, #validation_steps=len(valitems) // val_batch_size, epochs=epochs, #callbacks=[checkpoint], ) #plot_history(history, './results/', 'unet')...