Streaming Issue with 2.0b21

We are trying to stream on our Wowza server using 2.0b21 and we get sound, but no video. We have tried to downgrade to earlier Betas, but are being plagued with audio lag issues. The earlier Betas do allow us to stream with no issues.

With 2.0b21 console shows the following as soon as we start the stream (I replaced our server info with x’s):

3/1/16 10:23:41.123 AM mimoLive[688]: [Crashlytics] Version 3.6.0 (99)
3/1/16 10:23:49.483 AM mimoLive[688]: -[TVLightsController netService:didNotPublish:] {
NSNetServicesErrorCode = 48;
NSNetServicesErrorDomain = 1;
}
3/1/16 10:23:49.483 AM mimoLive[688]: -[TVLightsController netServiceWillPublish:]
3/1/16 10:23:51.013 AM mimoLive[688]: ERROR while mapping 0 channels.
3/1/16 10:23:55.943 AM mimoLive[688]: -[CIContext invalidate] not implemented
3/1/16 10:25:33.395 AM mimoLive[688]: -[RTMPStream socket:didConnectToHost:port:] connected 10.xxx.x.xx
3/1/16 10:25:33.399 AM mimoLive[688]: URL=rtmp://xxxxxxx:xxxxxxxx@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
3/1/16 10:25:33.399 AM mimoLive[688]: -[RTMPStream socketDidDisconnect:withError:] (null)
3/1/16 10:25:33.400 AM mimoLive[688]: -[RTMPStream socket:didConnectToHost:port:] connected 10.xxx.x.xx
3/1/16 10:25:33.403 AM mimoLive[688]: __29-[TVDocument startStreaming:]_block_invoke:3507 1 (null)
3/1/16 10:25:33.405 AM mimoLive[688]: -[RTMPStream socketDidDisconnect:withError:] (null)
3/1/16 10:25:33.406 AM mimoLive[688]: -[RTMPStream socket:didConnectToHost:port:] connected 10.xxx.x.xx
3/1/16 10:25:33.569 AM mimoLive[688]: Dropping Frame due to h264 load
3/1/16 10:25:33.586 AM mimoLive[688]: Dropping Frame due to h264 load

… (Deleted these entries to save space)

3/1/16 10:25:40.393 AM mimoLive[688]: Dropping Frame due to h264 load
3/1/16 10:25:40.408 AM mimoLive[688]: Dropping Frame due to h264 load
3/1/16 10:25:40.429 AM mimoLive[688]: Dropping Frame due to h264 load
3/1/16 10:25:40.442 AM mimoLive[688]: Dropping Frame due to h264 load
3/1/16 10:25:40.459 AM mimoLive[688]: Dropping Frame due to h264 load
3/1/16 10:25:40.475 AM mimoLive[688]: Dropping Frame due to h264 load
3/1/16 10:25:40.493 AM mimoLive[688]: Dropping Frame due to h264 load
3/1/16 10:25:40.508 AM mimoLive[688]: Dropping Frame due to h264 load
3/1/16 10:25:40.526 AM mimoLive[688]: Dropping Frame due to h264 load
3/1/16 10:25:40.542 AM mimoLive[688]: Dropping Frame due to h264 load
3/1/16 10:26:21.970 AM mimoLive[688]: This NSLayoutConstraint is being configured with a constant that exceeds internal limits. A smaller value will be substituted, but this problem should be fixed. Break on void _NSLayoutConstraintNumberExceedsLimit() to debug. This will be logged only once. This may break in the future.
3/1/16 10:26:22.170 AM mimoLive[688]: -[CIContext invalidate] not implemented

This is the entry in the Console when we start to experience the Audio lag (This exact entry is using 2.0b16, but it is the exact same entry when using any of the other versions):

3/1/16 4:10:42.471 PM mimoLive[1396]: VarispeedRenderProc - Fetching audio data from ring buffer returned error: 1 the second time.

We changed some things in the streaming to make it more robust from b16 to b21. However this warning message “Dropping Frame due to h264 load” tells us, that the H264 encoder is not working as expected. This issue should be independent from your streaming destination. Can you please check if you can stream to any other service like YouTube? Do you get the same warning message here?

Just tested 2.0b21 and we’re getting the same “Dropping Frame due to h264 load” warning trying to stream to youtube.

Streaming was working great on all versions until 2.0b21.

@“Achim (Boinx)”: Streaming is working again with 2.0b22. However, the quality of the image seems degraded a bit. Also while the stream is running if you click on “Stream Settings” mimoLive crashes.