This message was deleted.

Hey @strong-kite-90563, first off, for transparency, I deleted your message asking for a status update on this thread. The core team provides free support to the community and often times (i.e. weekdays), we’re quite busy working to make LiveKit better for everyone. Many of us try to catch up on community messages in the early mornings, evenings and weekends. If your questions go unanswered for some time, rest assured, we want to help you, but we just need a bit more time to get around to it. It’s possible that we miss things, and if you think we may have (i.e. it’s been over a week without a response), a gentle bump in the original thread works just as well. Thanks so much for your patience and understanding. 🙏🏽

Oh I thought the message may have been lost since I saw reply on others but not mine, so I just thought I added something make sure it wasn't lost. Sorry, not really sure how slack notification works since im new to slack. Ok thanks, I will keep this in mind 👍

for (5), the short answer is yes, @strong-kite-90563. With LiveKit Cloud, we meter all upstream and downstream data (i.e. bytes) transmissions. So any audio/video tracks that are published and/or subscribed, and all data messages that are sent/received. This includes transmissions associated with Ingress and Egress. Every month, we calculate the max of your upstream and downstream usage. If the resulting max usage is over the free monthly threshold (currently set to 50GB/month), you are charged for the difference at the per-GB rate (for current rates, see pricing).

1. you can check for

adaptiveStream

on the remote video tracks’

isAdaptiveStream

getter. for

dynacast

there’s currently nothing exposed to verify the status of a room. for

simulcast

I think you had the correct approach in the previous thread already with

isSimulcast

2. have you tried

remoteTrack.dimensions

? 3. yeah, generally the resolution of the acquired camera track will be used as the highest quality layer (and the only one in case simulcast is turned off). you can have a look at the publish options to customize the simulcast layers, specifically

videoSimulcastLayers

and

screenShareSimulcastLayers

1. I will play around with it again thanks. 2. Both

RemoteTrack

and

RemoteVideoTrack

does not have property

dimensions

😕 (I am using

"livekit-client": "^1.6.2"

)

(4) yes, all server function/api’s count towards the allocated API rate limit. These are currently set at 1K requests per minute, which can be raised based on individual requests (5) This is dashboard issue, and not a backend bug. When the browser is refreshed, this leads to the participant reconnecting, and publishing the tracks again(Same identity, but different sessions). That is why you see bump in published track counts when you refresh the browser every time. We are working on handling this better where a participant on rejoin/republishing so that it does not lead to double counting. This should be rolled out soon 🙂

2. sorry, should have clarified,

dimensions

exists on

TrackPublication

and

RemoteTrackPublication

Thanks @polite-kilobyte-67570 @bright-dream-51521