It will be nice to have this option. For our case in plugNmeet we always require participant's metadata for various purpose. If user doesn't have metadata then we can't verify lot of other logic in frontend.

Currently, when we setup an ingress stream as WHIP source with not transcoding to avoid wasting server resources. But in that case the ingress interface does not allow us to tag the tracks in the ingress as screenshare or screenshare audio.

As application manage differently main video from screenshare, there are some use cases where it is needed to tag some ingress streams as screenshare.

Right now WHIP returns a 405 for HTTP Patch requests with Trickle ICE Candidates, as per https://www.ietf.org/archive/id/draft-ietf-wish-whip-01.html#name-ice-and-nat-support.

It would be amazing if we could remove the TODO in the code for implementing Trickle ICE and ICE Restarts. I would love guidance on how to implement it, but I don't know where to start.

i'm getting below error while start streaming

ERROR	ingress	service/handler.go:120	ingress failed	{"nodeID": "CENSORD", "ingressID": "CENSORD", "ingressID": "CENSORD", "error": "could not establish signal connection"}

ingressrtmp/server.go:285 Failed to write video	{"nodeID": "CENSORD", "streamKey": "CENSORD", "error": "preroll buffer reset"}
ey": "aRiBEsYufex2", "error": "preroll buffer reset"}
github.com/livekit/ingress/pkg/rtmp.(*RTMPHandler).OnVideo
	/workspace/pkg/rtmp/server.go:285
github.com/livekit/go-rtmp.(*serverDataPublishHandler).onMessage
	/root/go/pkg/mod/github.com/livekit/[email protected]/server_data_publish_handler.go:35
github.com/livekit/go-rtmp.(*streamHandler).Handle

config.yaml ingress :

log_level: debug
api_key: access_token
api_secret: CENSORD
ws_url: wss://CENSORD

redis:
address: CENSORD
db: 0
username: default
password: CENSORD
use_tls: true

I'm trying to use WHIP instead of RTMP (RTMP works fine) but after accepting the connection the connection drops.

Config

logging:
  level: debug
redis:
    address: localhost:6379
api_key: *******
api_secret: *******
ws_url: wss://MY.URL
rtmp_port: 1935
whip_port: 8080
http_relay_port: 9090

rtc_config:
  tcp_port: 7882 # 7881 - already in use
  udp_port: 7885
  use_external_ip: false

Reported in slack

With livekit-server 1.4.2 and Ingress 0.9.0, when I tying to send some test rtmp data to ingress, I get following error in logs:

ERROR	ingress	service/handler.go:120	ingress failed	{"nodeID": "NE_Caea23Ygkz3s", "ingressID": "IN_AgLrhaGk9jhP", "ingressID": "IN_AgLrhaGk9jhP", "error": "unauthorized: no permissions to access the room"}

This happens if ws_url has a trailing slash like wss://livekit.example.com/. Removing the trailing slash appears to fix the auth error above.

Sometime, we should pull http+flv streams from other origin sites. We now only can push rtmp to ingress.

I found cmd.Err have exec: "ingress": executable file not found in %PATH% ?

this is my ingress log

`2023-11-24T18:34:58.019+0800 INFO ingress redis/redis.go:127 connecting to redis {
"nodeID": "NE_BJf5hZKdUSCN", "simple": true, "addr": "localhost:6379"}
time="2023-11-24T18:47:18+08:00" level=info msg="Change state: From = , To = NotConnected(Server)" logger=ingress nodeID=NE_BJf5hZKdUSCN state="NotConnected(Server)" stream_id=0
time="2023-11-24T18:47:18+08:00" level=info msg=Connect logger=ingress nodeID=NE_BJf5hZKdUSCN state="NotConnected(Server)" stream_id=0
time="2023-11-24T18:47:18+08:00" level=info msg="Set win ack size: Size = 2147483647" logger=ingress nodeID=NE_BJf5hZKdUSCN state="NotConnected(Server)" stream_id=0
time="2023-11-24T18:47:18+08:00" level=info msg="Set peer bandwidth: Size = 786432, Limit = 0" logger=ingress nodeID=NE_BJf5hZKdUSCN state="NotConnected(Server)" stream_id=0
time="2023-11-24T18:47:18+08:00" level=info msg="Stream Begin: ID = 0" logger=ingress nodeID=NE_BJf5hZKdUSCN state="NotConnected(Server)" stream_id=0
time="2023-11-24T18:47:18+08:00" level=info msg="Connect: ResponseBody = &message.NetConnectionConnectResult{Properties:message.NetConnectionConnectResultProperties{FMSVer:"GO-RTMP/0,0,0,0", Capabil
ities:31, Mode:1}, Information:message.NetConnectionConnectResultInformation{Level:"status", Code:"NetConnection.Connect.Success", Description:"Connection succeeded.", Data:amf0.ECMAArray{"type
":"go-rtmp", "version":"master"}}}" logger=ingress nodeID=NE_BJf5hZKdUSCN state="NotConnected(Server)" stream_id=0
time="2023-11-24T18:47:18+08:00" level=info msg=Connected logger=ingress nodeID=NE_BJf5hZKdUSCN state="NotConnected(Server)" stream_id=0
time="2023-11-24T18:47:18+08:00" level=info msg="Change state: From = NotConnected(Server), To = Connected(Server)" logger=ingress nodeID=NE_BJf5hZKdUSCN state="Connected(Server)" stream_id=0
time="2023-11-24T18:47:18+08:00" level=info msg="Release stream...: StreamName = GnrxqezSrVnf" logger=ingress nodeID=NE_BJf5hZKdUSCN state="Connected(Server)" stream_id=0
time="2023-11-24T18:47:18+08:00" level=info msg="FCPublish stream...: StreamName = GnrxqezSrVnf" logger=ingress nodeID=NE_BJf5hZKdUSCN state="Connected(Server)" stream_id=0
time="2023-11-24T18:47:18+08:00" level=info msg="Stream creating...: &message.NetConnectionCreateStream{}" logger=ingress nodeID=NE_BJf5hZKdUSCN state="Connected(Server)" stream_id=0
time="2023-11-24T18:47:18+08:00" level=info msg="Change state: From = , To = Inactive(Server)" logger=ingress nodeID=NE_BJf5hZKdUSCN state="Inactive(Server)" stream_id=1
time="2023-11-24T18:47:18+08:00" level=info msg="Stream created...: NewStreamID = 1" logger=ingress nodeID=NE_BJf5hZKdUSCN state="Connected(Server)" stream_id=0
time="2023-11-24T18:47:18+08:00" level=info msg="Publisher is comming: &message.NetStreamPublish{CommandObject:interface {}(nil), PublishingName:"GnrxqezSrVnf", PublishingType:"live"}" logger=ingr
ess nodeID=NE_BJf5hZKdUSCN state="Inactive(Server)" stream_id=1
2023-11-24T18:47:18.216+0800 INFO ingress service/service.go:382 received ingress info {
"nodeID": "NE_BJf5hZKdUSCN", "ingressID": "IN_TJHKcQP8Ygh2", "streamKey": "GnrxqezSrVnf", "resourceID": "RT_nowW8MRPzN7E", "ingressInfo": "ingress_id:"IN_TJHKcQP8Ygh2" name:"test-ingress" stream_k
ey:"{Gnr...Vnf}" url:"rtmp://localhost:1935/live" audio:{} video:{} room_name:"7bzo-wkka" participant_identity:"kkkk" participant_name:"kkkk" reusable:true state:{status:ENDPOINT_BUFFERING s
tarted_at:1700822838208197100 resource_id:"RT_nowW8MRPzN7E"}"}
2023-11-24T18:47:18.242+0800 INFO ingress service/session_manager.go:47 ingress started {
"nodeID": "NE_BJf5hZKdUSCN", "ingressID": "IN_TJHKcQP8Ygh2", "resourceID": "RT_nowW8MRPzN7E"}
2023-11-24T18:47:23.989+0800 INFO ingress rtmp/server.go:206 Received a new published stream {
"nodeID": "NE_BJf5hZKdUSCN", "streamKey": "GnrxqezSrVnf", "resourceID": "RT_nowW8MRPzN7E"}
2023-11-24T18:47:23.989+0800 ERROR ingress service/process_manager.go:164 could not launch handler {
"nodeID": "NE_BJf5hZKdUSCN", "error": "exec: "ingress": executable file not found in %PATH%"}
github.com/livekit/ingress/pkg/service.(*ProcessManager).awaitCleanup
D:/直播流媒体/backend/ingress/pkg/service/process_manager.go:164
2023-11-24T18:47:23.990+0800 WARN ingress service/service.go:401 ingress failed {
"nodeID": "NE_BJf5hZKdUSCN", "error": "exec: "ingress": executable file not found in %PATH%"}
time="2023-11-24T18:47:23+08:00" level=info msg="Publisher accepted" logger=ingress nodeID=NE_BJf5hZKdUSCN state="Inactive(Server)" stream_id=1
time="2023-11-24T18:47:23+08:00" level=info msg="Change state: From = Inactive(Server), To = Publish(Server)" logger=ingress nodeID=NE_BJf5hZKdUSCN state="Publish(Server)" stream_id=1
2023-11-24T18:47:23.991+0800 INFO ingress rtmp/server.go:307 key frame found {
"nodeID": "NE_BJf5hZKdUSCN", "streamKey": "GnrxqezSrVnf", "resourceID": "RT_nowW8MRPzN7E"}
2023-11-24T18:47:23.992+0800 INFO ingress service/service.go:326 shutting down {
"nodeID": "NE_BJf5hZKdUSCN"}
2023-11-24T18:47:23.992+0800 INFO ingress service/session_manager.go:61 ingress ended {
"nodeID": "NE_BJf5hZKdUSCN", "ingressID": "IN_TJHKcQP8Ygh2", "resourceID": "RT_nowW8MRPzN7E"}
panic: runtime error: invalid memory address or nil pointer dereference
[signal 0xc0000005 code=0x0 addr=0x0 pc=0x1573fae]

goroutine 65 [running]:
github.com/prometheus/client_golang/prometheus.(*Registry).Unregister.func1()
C:/Users/Administrator/go/pkg/mod/github.com/prometheus/[email protected]/prometheus/registry.go:372 +0x2e
created by github.com/prometheus/client_golang/prometheus.(*Registry).Unregister in goroutine 1
C:/Users/Administrator/go/pkg/mod/github.com/prometheus/[email protected]/prometheus/registry.go:371 +0x198

Debugger finished with the exit code 0
`

We have experienced decoding artifacts like pixelation and even green screens on browsers receiving video tracks from an ingress that is using WHIP.
We verified that the video that is fed to ingress using whip was correctly encoded and in fact we could record it and see that the video at whip ingress was correct. However at the same time, the video received in all browsers subscribed to the track show decoding artifacts. We have been able to reproduce the problem using H264 and VP8. and if many browser subscribe to the tracks, all of the show the same problem at the same time

We have analysed the ingress and we think we have found possible causes for this problem: basically on ingress frames may be dropped to several causes, that may happen when media comes from WHIP. The problem seems to be that dropping samples in the middle of an encoded video stream casuses gaps in the stream that will make the video player impossible to correctly decode the stream until a new keyframe appears on the stream. The main problem is that after a sample is dropped subsequent samples are still pushed downstream even to the RemoteTrack that without sequence numbers has no way for livekit server or the browser to detect that there is a gap on the stream. Thus, when this issue happens, the decoder on the browser cannot detect the gap and just tries to decode frames causing decoding artifacts.

This happens in two places:

• The jitter buffer used at the reception of WHIP packets may drop late ones. It is true that in this case, jitter buffer dropping samples will also cause a PLI request that theoretically should generate a key frame at some point in the near future, but until that happens, subsequent frames that has lost their previous frame reference will be pushed downstream, making the decoder to cause decoding artifact that may last from just a flash to a few seconds depending on when the keyframe appears
• Also the output synchronizer may drop samples

  ingress/pkg/whip/sdk_media_sink.go

  Line 271 in 2204d43

  drop, err := t.sink.outputSync.WaitForMediaTime(ts)

  and in this case apart from pushing downstream subsequent frames, the point is that no PLI request is generated, so the publisher has no way to know that a keyframe is needed and the decoding artifact may last for many seconds, even minutes, in fact until for any other reason a keyframe is generated.

We have created a fix for this that basically whenever a sample is dropped, it just drops all subsequent frames until a keyframe appears. Also for the sdk_media_sink.go the fix includes that if a sample is dropped a PLI is requested upstream.

We have verified that with this fix the decoding artifacts completely dissapear, so we are pretty sure that the issue is as we described. However, I am afraid that the fix also impacts the output synchronizer causing freezings longer than what theoretically should appear. We haven't gone further on that analysis, but it seems that as when a sample is dropped a sequence of samples is dropped, this may be impacting the output synchronizer that handle sample durations thus having more difficult to correctly synchronize when not short gaps appear on the stream.

ERROR: WriteN, RTMP send error 104 with librtmp,

windows run main,go found error!!!

Hi I have a configuration question it seems my configuration dosnt work, I have an RTMP nginx server setup and im pushing streams from external devices to the server then pushing them to ingress server with address 1936 but it dosnt seem to be working,

This is my

rtmp {
        server {
                listen 1935;
                chunk_size 4096;
                # Todo only allow external publishing from specific IPs
                allow publish all;

                application stream {
                        live on;
                        record off;
                        # Push to internal ingress RTMP server
                        push rtmp://127.0.0.1:1936/live/$name;
                        allow play 127.0.0.1;
                }
        }
}

And this is my base url in livekit server config

ingress:
  rtmp_base_url: "rtmp://example.com:1935/stream"

And my ingress config

cpu_cost:
  rtmp_cpu_cost: 2.0
log_level: debug
rtmp_port: 1936
http_relay_port: 9090

From external devices I push to rtmp://example.com:1935/stream using ingress streamkey

I'm using ingress to send audio file to devices using URL ingress. Noticed that it cuts first seconds of audio file. It's very noticeable when audio file with text is used

failed to send update {"nodeID": "NE_G6wbh9hpPx9P", "ingressID": "IN_ELgkd7J8ZAoj", "resourceID": "RT_4pu5e65b4oFE", "ingressID": "IN_ELgkd7J8ZAoj", "resourceID": "RT_4pu5e65b4oFE", "error": "trying to ovewrite an ingress with an older version"}
github.com/livekit/ingress/pkg/params.(*Params).SendStateUpdate
/workspace/pkg/params/params.go:355
github.com/livekit/ingress/pkg/media.(*Pipeline).Run.func1
/workspace/pkg/media/pipeline.go:173
github.com/livekit/ingress/pkg/media.(*Pipeline).Run
/workspace/pkg/media/pipeline.go:210
github.com/livekit/ingress/pkg/service.(*Handler).HandleIngress.func2
/workspace/pkg/service/handler.go:94

this will always print info log. Debug log is missing.

LK Server v. 1.4.2, LK Ingress v0.9.0

Streaming works just fine, I see that Ingress participant joins with the respective webhook called, but ingress_started / ingress_ended is not triggered.

Starting the service it exists with exit code 0 and throws "Failed reading cpu stats file".
Im using WSL2 and Docker Engine v4.16.1. I tried running it as a seperate docker container and adding it as a service to livekit, but seems to return the same message.

These are the logs:
{"level":"info","ts":1674200810.1469305,"logger":"ingress","caller":"redis/redis.go:53","msg":"connecting to redis","nodeID":"NE_hdd82Cduay5A","sentinel":false,"addr":"host.docker.internal:6379"} failed reading cpu stats file {"level":"debug","ts":1674200810.1541233,"logger":"ingress","caller":"service/service.go:119","msg":"starting service","nodeID":"NE_hdd82Cduay5A"} {"level":"info","ts":1674200810.1541848,"logger":"ingress","caller":"stats/monitor.go:126","msg":"available CPU cores: 12.000000 max cost: 2.000000","nodeID":"NE_hdd82Cduay5A"}

This is my configuration file:
log_level: debug api_key: <retracted> api_secret: <retracted> ws_url: ws://<retracted>:7880 redis: address: host.docker.internal:6379 username: "" password: "" db: 0 cpu_cost: rtmp_cpu_cost: 2.0 ingress: rtmp_base_url: rtmp://<retracted>

Hello

I have an issue when using Ingress for audio streaming to a room with ffmpeg. I have two backends

• Go backend for room creation, Egress instantiation and rtmp URL generation for Ingress I'm using node.js for backend
• Node.js backend for playlist management and audio streaming to given rtmp URL.

Frontend is written in Flutter/Dart and uses livekit flutter SDK of the latest version (1.3.4). Flutter version: 3.7.12

When I spawn ffmpeg process to strem music to previously generated rtmp URL with this code (Node.js)

const ffmpeg = childProcess.spawn(
    `ffmpeg`, [`-re`, `-ss`, `${toHHMMSS(req.body.seekSeconds)}`, `-stream_loop`, `-1`, `-i`, `${concat}`, `-c:v`, `libx264`, `-c:a`, `aac`, `-f`, `flv`, `${req.body.rtmpUrl}`],
    {
        cwd: process.cwd() + '/songs'
    }
);

it looks like some parts of a song are dropping and it becomes choppy (watch the attached video). This behaviour happens only on Android devices: it works fine in example Web app and iOS build of my Flutter application.
Snipper comment: toHHMMSS transforms transforms seconds to MM:SS format and concat is a list of mp3 files for playback.

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• Update livekit deps (github.com/livekit/mediatransportutil, github.com/livekit/psrpc)
• Update go deps (github.com/Eyevinn/mp4ff, github.com/pion/interceptor, github.com/pion/rtp, github.com/pion/webrtc/v3, github.com/urfave/cli/v2, google.golang.org/protobuf)
• Update go deps (major) (github.com/go-gst/go-glib, github.com/go-gst/go-gst, github.com/pion/rtp)
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

dear author:
when i use ingress service , there are some issue as below:
param: ingressRequest := &livekit.CreateIngressRequest{
InputType: livekit.IngressInput_URL_INPUT,
Name: "ingress_" + name,
RoomName: room,
ParticipantIdentity: from,
ParticipantName: from,
Url: url,
}

result: {"error": "twirp error invalid_argument: invalid ingress type
could u please tell me what should i do to resolve them?