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

Documentation missing "Jumps" #126

Closed
fealXX opened this issue Apr 10, 2018 · 4 comments
Closed

Documentation missing "Jumps" #126

fealXX opened this issue Apr 10, 2018 · 4 comments

Comments

@fealXX
Copy link

fealXX commented Apr 10, 2018

Hi there,
I can't find a definition in the documentation (explaning the universeview) for the "Jumps" column.

image

Can anyone give me a hint where to find it or what it means?

Thanks,
Felix

@marcusbirkin
Copy link
Collaborator

Hi Felix,

Jump is a lost packet.
E.G. we get packet 1, then 3, but not 2

SeqErr is a packet arrived out of sequence.
E.G. We get packet 1, then 3, then 2

From your screen shot it appears you are getting network packet loss.

@marcusbirkin
Copy link
Collaborator

Should implement tooltips

@mrrodgers23
Copy link

sACN is a UDP transmission, correct? How does sACNView detect packet losses without a handshake between hosts?

Hi Felix,

Jump is a lost packet.
E.G. we get packet 1, then 3, but not 2

SeqErr is a packet arrived out of sequence.
E.G. We get packet 1, then 3, then 2

From your screen shot it appears you are getting network packet loss.

@docsteer
Copy link
Owner

There's now a full description of jumps and sequence errors in the 2.1 documentation at https://github.com/docsteer/sacnview/blob/2.1-dev/docs/documentation.md - this will appear on the main site when we make 2.1 a full release.

To answer @mrrodgers23 question, each sACN packet contains a sequence number that increments with every packet from a source - that allows us to track lost or out of order delivery

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants