https://livekit.io logo
Join Slack
Powered by
This message was deleted.
# cloud
s
This message was deleted.
d
Hey @fancy-tailor-45239, please thread your messages please 🙏 We are aware of your report and will follow up there. Please note that our react-native SDK is still in beta. We are working on getting a 1.0 release of it out.
one question for you. from the screenshots it appears that the lighting conditions between the two are very different. are they taken at different times/with different light?
and are you saying the received video is lower resolution? but the local video looks fine?
f
@David Thanks for your quick response. • So the issue is only for react-native SDK? or it is also in iOS SDK? • Regarding the screenshots it's 6 minutes apart at night I tried my best to keep the condition same as web conditions. that's why I put the planet under same table lamp. so technically 99% same conditions • On our app both resolution effected for local and remote. most of the time it worst than these
d
I don't know what the issue is.. or if there is an issue at all. Really just trying to understand it
ok, so your question/issue is that both local and remote video (when acquired) appear lower resolution. if local is also an issue, we'd have to look at reproducing it ourselves.. are you able to reproduce with the example app?
f
I don't know what the issue is.. or if there is an issue at all. Really just trying to understand it
the issue basically: meet.livekit.io quality is perfect for us but when we tried to implement the library on our app is totally different
if local is also an issue, we'd have to look at reproducing it ourselves.. are you able to reproduce with the example app?
I'll try to test the example app and get back to you...
d
yup, that's good to know, but the key difference I needed to know was if it the remote video appear lower quality, or if that applied to the local video too. you've confirmed it was local
it's very difficult for us to know what's happening within your application, since there's no way for us to run the same on our devices nor be able to see what the rest of the application is doing. For example, if the application is running other forms of processing, that would impact consumption of resources and it could cause video to be lower resolution
f
Yeah Simply the quality ratio: ------ WEB ------ Local: 95% | Remote: 90% ------ OUR APP ------ Local: 65% | Remote: 40% Which is the local is always better than remote but with some ratio
đź‘Ť 1
d
but yeah, let me know what you see with the example app.
đź‘Ť 1
f
For example, if the application is running other forms of processing, that would impact consumption of resources and it could cause video to be lower resolution
Yes it could be. so in that case I have to test on the example app check the result and I'll get back to you with my feedback here
đź‘Ť 1
e
hey @fancy-tailor-45239, can you check the resolution of the camera used on the publisher side? there should be a log that has “publishing track”, that contains 
_mediaStreamTrack
with its 
settings
that should show the width/height given
also, found a bug with the 
screen
pixelDensity for react-native; for now, omit this. it’s probably unrelated since the publish video quality is already low, but it will cause the receiver to get lower quality video
f
@eager-raincoat-52616 sure give me a minutes i’ll check the resolution for local and remote with removing pixelDensity
console.log(publication.dimensions);
console.log(publication.videoTrack?.mediaStreamTrack.getSettings());
output: 
{"height": 720, "width": 1280}
{"frameRate": 3, "height": 720, "width": 1280}
by removing 
pixelDensity
I can tell its improve the quality but still not same as meet.livkit.io
specially when the camera is moving
e
hmm, not able to reproduce it exactly, but it seems like there’s a warmup period for the camera where it starts low and gradually goes to high res. does this happen for you as well?
f
Yes this is happening in web also. But for app after warming up after slightly moving it goes to low res
e
So it goes from low res -> high res -> low res?
f
Yes, but still high res in web not same as high res in iOS app
e
does this happen with react-native-webrtc 106? I wonder if there’s something affecting this in the m111 update
f
I didn’t tried 106 but I tried latest native iOS SDk example. Publisher publish 1.5Mbps bitrate and (1920x1080) Viewer receives around 300Kbps with significant lower resolution around (320x180) And this issue doesn’t happen in meet.livekit.io using Safari.
I tried using 100ms.live the quality is better, However they have higher latency around 300ms. Now I believe the issue caused by react-native-webrtc becuase they are using modified webrtc depenedancy.
d
the bitrate you mention seems really low for 1080p. Meet is using the defaults, which is 720p at ~2mbps. to be clear, your issue is that the remote video seems lower quality, but you no longer have issues with the local video?
e
@fancy-tailor-45239 hey, any updates here?
f
Sorry guys I was at holiday. I’ll do my test and get back to you ASAP
đź‘Ť 1
Open in Slack
PreviousNext
Powered by