-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Warn user when multiple IP routes are being used for the WebRTC streaming #591
Warn user when multiple IP routes are being used for the WebRTC streaming #591
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I feel I had a bit of difficulty reading/memorizing the text.
src/stores/video.ts
Outdated
text: `Cockpit detected more than one IP being used to route the video streaming. | ||
This situation often leads to video stuterring, specially if one of the IPs is from a non-wired connection. | ||
To prevent issues and have an optimum streaming experience, please open the configuration of one of your | ||
video widgets and choose the IP that should be used for the video streamings.`, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
text: `Cockpit detected more than one IP being used to route the video streaming. | |
This situation often leads to video stuterring, specially if one of the IPs is from a non-wired connection. | |
To prevent issues and have an optimum streaming experience, please open the configuration of one of your | |
video widgets and choose the IP that should be used for the video streamings.`, | |
text: `Cockpit detected more than one IP being used to route the video streaming. | |
This situation often leads to video stuterring, specially if one of the IPs is from a non-wired connection. | |
To prevent issues and have an optimum streaming experience, please follow the steps below: | |
1. open the configuration of one of your | |
video widgets, and | |
2. choose the IP that should be used for the video streaming.`, |
I don't know how to format it, but the text should not be centered and should have new lines.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
By the way, shouldn't this configuration be global in cockpit over on the stream widget ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I liked the suggestions. Will change.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the notice @joaoantoniocardoso. I did that in a rush and ended up not styling the message.
This popup is going to appear for most/all users, so it should indeed look good.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice, that's much better. Can you switch the bullets to just the numbers? Or vice-versa? And there's a space missing between the words "your" and "video" ("yourvideo")
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Followed this guide for list formatting.
…explicitly set This allows one to track when it is was already populated, and react to that.
792b373
to
f496c54
Compare
src/stores/video.ts
Outdated
<li>1. open the configuration of one of your video widgets</li> | ||
<li>2. choose the IP that should be used for the video streaming</li> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
<li>1. open the configuration of one of your video widgets</li> | |
<li>2. choose the IP that should be used for the video streaming</li> | |
<li>1. Open the configuration of one of your video widgets.</li> | |
<li>2. Choose the IP that should be used for the video streaming.</li> |
(following this)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nicer indeed.
… candidates were not yet defined
f496c54
to
39a81d5
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why not having the IP configuration done on cockpit over stream widget ?
Actually when I was first coding this patch we didn't have the video store yet, so it wouldn't be doable, but now that we have, I think it's indeed a better solution, specially because the variable is shared between all video widgets. Will change! |
It's a trade-off... I'm not opposed to, also because the signaling address is also global, already limiting the person to receive video from different sources when they live in different networks/vehicles. |
The most common use case is to have a single vehicle with multiple cameras,
the black/white list is.... a list, allowing it to a single list to work
with multiple widgets with different vehicles in different networks.
Having the user to configure every video stream widget for a single vehicle
does not make sense to me, having a global configuration allows all the use
cases and also simplifies it.
Em seg., 27 de nov. de 2023 às 14:26, João Antônio Cardoso <
***@***.***> escreveu:
… Why not having the IP configuration done on cockpit over stream widget ?
It's a trade-off... I'm not opposed to, also because the signaling address
is also global, already limiting the person to receive video from different
sources when they live in different networks/vehicles.
—
Reply to this email directly, view it on GitHub
<#591 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAJIYCOPYBINWCJTY6K6NJDYGTENBAVCNFSM6AAAAAA7ZSTUFCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMRYGI4TONRSGI>
.
You are receiving this because you commented.Message ID:
***@***.***>
--
Patrick José Pereira
Electronics Engineer
|
The configuration is already global, not widget-wise. |
This can be addressed in another PR if you prefer. |
Agree. Will merge this one them. |
Fix #583