This message was deleted.
# helpdesk
s
This message was deleted.
c
It does look high and may be worth looking into, but hard tell for sure/reproduce without more details on the test parameters
s
Here are some more details: Regarding Egress installation its running on Debian 11 and libgstreamer dependencies have been installed via apt-get (is this ok? should I be using specific versions?). Regarding the test I have a small bash script but the main parts are: • start a room with a pub and a sub:
Copy code
livekit-cli load-test --api-key $LKKEY --api-secret $LKSECRET --url $LKURL --room $ROOM_NAME --publishers 1 --subscribers 1
• get the participant and get the video track
Copy code
livekit-cli list-participants --api-key $LKKEY --api-secret $LKSECRET --url $LKURL --room $ROOM_NAME
livekit-cli get-participant --identity $PARTICIPANT_ID --api-key $LKKEY --api-secret $LKSECRET --url $LKURL --room $ROOM_NAME
• start recording the track
Copy code
livekit-cli start-track-egress --api-key $LKKEY --api-secret $LKSECRET --url $LKURL --request $REQFILE
• REQFILE has the following format:
Copy code
{
  "room_name": "$ROOM_NAME",
  "track_id": "$TRACK",
  "file": {
    "filepath": "$ROOM_NAME.mp4",
    "s3": {
      "access_key": "KEY",
      "secret": "SECRET",
      "region": "us-east-1",
      "bucket": "BUCKET"
    }
  }
}
• After this I sleep for a while, right now I’m doing 300s • After that I stop the track egress
Copy code
livekit-cli stop-egress --api-key $LKKEY --api-secret $LKSECRET --url $LKURL -id $EGRESS_ID
c
Thanks for the report. It looks like contrary to what the documentation states, H264 track egress are getting transcoded. We will fix the logic.
As a side note since you mention installing he dependencies on the host system: are you running egress directly on the host or in docker? Running directly on the host can be convenient for testing but would not be advised with production traffic.
s
Thx for your input @chilly-animal-65189, do you happen to have an issue link that I can track for the transcode problem?
I'm indeed running the binary directly on the host ... I'm kind of old school VoIP guy and I'm a little scared to run media through docker/kubernetes. I will take that into consideration for sure. But can you tell me what kind of issues can I run into when running directly on the host? Just so I can keep an eye out during my tests.
c
Security, mostly. the egress service writes media to a path provided in the StartEgress request
regarding a ticket, we do not have one on GH. Best would be to create one if you want a notification when it's fixed
s
Will do. 🙏 Thx for your help