Skip to content
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

Conversation

rafaellehmkuhl
Copy link
Member

image

Fix #583

Copy link
Member

@joaoantoniocardoso joaoantoniocardoso left a 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.

Comment on lines 19 to 22
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.`,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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.

Copy link
Member

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 ?

Copy link
Member Author

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.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

image

Copy link
Member Author

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.

Copy link
Member

@joaoantoniocardoso joaoantoniocardoso Nov 27, 2023

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")

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

image

Followed this guide for list formatting.

…explicitly set

This allows one to track when it is was already populated, and react to that.
Comment on lines 66 to 67
<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>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
<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)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

image

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nicer indeed.

Copy link
Member

@patrickelectric patrickelectric left a 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 ?

@rafaellehmkuhl
Copy link
Member Author

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!

@joaoantoniocardoso
Copy link
Member

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.

@patrickelectric
Copy link
Member

patrickelectric commented Nov 27, 2023 via email

@rafaellehmkuhl
Copy link
Member Author

rafaellehmkuhl commented Nov 27, 2023

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.

The configuration is already global, not widget-wise.
It's just a matter of moving the component to a configuration page. I'm doing that right now.

@patrickelectric
Copy link
Member

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.

The configuration is already global, not widget-wise. It's just a matter of moving the component to a configuration page. I'm doing that right now.

This can be addressed in another PR if you prefer.

@rafaellehmkuhl
Copy link
Member Author

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.

The configuration is already global, not widget-wise. It's just a matter of moving the component to a configuration page. I'm doing that right now.

This can be addressed in another PR if you prefer.

Agree. Will merge this one them.

@rafaellehmkuhl rafaellehmkuhl merged commit f1ae9b4 into bluerobotics:master Nov 27, 2023
7 checks passed
@rafaellehmkuhl rafaellehmkuhl deleted the warn-user-about-multiple-stream-ips branch November 27, 2023 17:49
@ES-Alexander ES-Alexander added the docs-needed Change needs to be documented label Nov 29, 2023
ES-Alexander added a commit to ES-Alexander/ardusub-zola that referenced this pull request Dec 12, 2023
ES-Alexander added a commit to ES-Alexander/ardusub-zola that referenced this pull request Dec 12, 2023
ES-Alexander added a commit to ES-Alexander/ardusub-zola that referenced this pull request Dec 12, 2023
ES-Alexander added a commit to ES-Alexander/ardusub-zola that referenced this pull request Dec 13, 2023
ES-Alexander added a commit to bluerobotics/ardusub-zola that referenced this pull request Dec 13, 2023
ES-Alexander added a commit to bluerobotics/ardusub-zola that referenced this pull request Dec 13, 2023
ES-Alexander added a commit to bluerobotics/ardusub-zola that referenced this pull request Dec 13, 2023
@ES-Alexander ES-Alexander added docs-complete Change documentation has been completed and removed docs-needed Change needs to be documented labels Dec 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs-complete Change documentation has been completed
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Inform the user that more than one IP is being used for video stream routing, encouraging to choose one
4 participants