This message was deleted.
# helpdesk
s
This message was deleted.
a
Are you running v1.4.1? This should be fixed
s
yes
root@mr01:/opt# docker inspect bc3 | grep image "org.opencontainers.image.created": "2022-09-15T181132.158Z", "org.opencontainers.image.description": "Export and record WebRTC sessions and tracks", "org.opencontainers.image.licenses": "Apache-2.0", "org.opencontainers.image.revision": "adae4d308d7a9179c7c6cdf755918b244180edfa", "org.opencontainers.image.source": "https://github.com/livekit/egress", "org.opencontainers.image.title": "egress", "org.opencontainers.image.url": "https://github.com/livekit/egress", "org.opencontainers.image.version": "v1.4.1" root@mr01:/opt#
Could it be related to GST_PLUGIN_SCANNER?
a
no, the error is
Copy code
gst_matroska_mux_video_pad_setcaps (): /GstPipeline:pipeline/GstBin:input: \nCaps changes are not supported by Matroska
s
egressrec01 | (egress:21): GStreamer-WARNING **: 223722.873: External plugin loader failed. This most likely means that the plugin loader helper binary was not found or could not be run. You might need to set the GST_PLUGIN_SCANNER environment variable if your setup is unusual. This should normally not be required though.
Do you have any suggestions for a solution?
a
the track changed from 360x640 to 540x960, which matroska mux does not allow
I’m currently building a tool to better reproduce and test this case, and we should have a better fix in 1.4.2
for now, downgrading to v1.2.0 will fix it but you will receive .ivf files instead of .webm files
s
So you're suggesting I use 1.2.0 ??
a
yes, if you need this to work immediately
otherwise, I will be releasing 1.4.2 sometime this week once I’m confident in the new fix
s
yes it should work for my client
Oh, that's very good news.
Yes, it continues to record with v120 without giving an error. thank you for your help. What are your suggestions for stable operation in long (1 hour) broadcasts?
a
it probably is taking a long time to finalize/upload the file
0 byte file is a sign that the process was killed before it was able to complete
make sure it’s being stopped with StopEgress and that the docker container isn’t being killed
Just pushed 1.4.2 - I was able to reproduce in 1.4.1 but not 1.4.2, but let me know if you see it again
👍 1
s
Thank you for your help. If I try v1.4.2 I will let you know. good work