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

Transmission jitter after reconnection #1566

Open
Morgan0328 opened this issue Sep 22, 2020 · 4 comments
Open

Transmission jitter after reconnection #1566

Morgan0328 opened this issue Sep 22, 2020 · 4 comments
Labels
[apps] Area: Test applications related improvements Type: Bug Indicates an unexpected problem or unintended behavior
Milestone

Comments

@Morgan0328
Copy link

Hi when i pull and rebuild the srt-live-transmit.exe at 2020-09-07 version , my process doesn't work

Caller:
srt-live-transmit.exe udp://228.8.8.8:8888?adapter=169.254.24.188 srt://192.168.0.165:5101?adapter=192.168.0.171

Listener:
srt-live-transmit.exe srt://:5201?adapter=192.168.0.165 file://con | tsp --max-input-packets 7 -I file -P regulate --packet-burst 7 -O ip 227.7.7.7:9999 -l 192.168.0.165

the Caller side show the msg :

16:36:17.284000/T9036*E:SRT.ea: IPE: remove_usock: @425358004 not found as either socket or group. Removing only from epoll system.
13160 bytes lost, 32072236 bytes sent, 32085396 bytes received

what is that mean ? It work if i remove the adapter from Caller like
"srt-live-transmit.exe udp://228.8.8.8:8888?adapter=169.254.24.188 srt://192.168.0.165:5101"

The bitrate is stable if i run caller first and then start to receive the srt source at another computer ,
but if run Listener first the waveform of bitrate like sawtooth wave.
is it necessary to run caller first?

Thank you.

@Morgan0328 Morgan0328 added the Type: Question Questions or things that require clarification label Sep 22, 2020
@maxsharabayko maxsharabayko added this to the v1.5.0 - Sprint 24 milestone Sep 22, 2020
@maxsharabayko maxsharabayko added [apps] Area: Test applications related improvements Type: Bug Indicates an unexpected problem or unintended behavior and removed Type: Question Questions or things that require clarification labels Sep 22, 2020
@maxsharabayko
Copy link
Collaborator

Hi @Morgan0328
Just to confirm, could you please also try to surround the URI with quotation marks like this

srt-live-transmit.exe "srt://:5201?adapter=192.168.0.165" file://con

@Morgan0328
Copy link
Author

Hi @Morgan0328
Just to confirm, could you please also try to surround the URI with quotation marks like this

srt-live-transmit.exe "srt://:5201?adapter=192.168.0.165" file://con

i rebuild it and try again , but ..... the problem still exists

Caller :

caster

Listener :

Listener
:

@Morgan0328
Copy link
Author

The second waveform is When i Restart the Caller Side .

RestartCaller

@maxsharabayko
Copy link
Collaborator

As I understand, there are two issues you are reporting:

  1. The IPE message (addressed in [apps] Fixed stransmit processing a socket twice #1569). Does not seem related to the adapter URI option.
  2. Some waveform you are seeing when you restart a caller? Could you please provide more information on this topic?

Note 1. In the following example, you are using UDP as a source. You don't need the target address as you won't send any data there.

srt-live-transmit.exe udp://228.8.8.8:8888?adapter=169.254.24.188

can be

srt-live-transmit.exe udp://:8888?adapter=169.254.24.188

Note 2. TSDuck has added support for SRT recently. This part can be reduced to just tsp. Refer to the TSDuck's docs.

srt-live-transmit.exe srt://:5201?adapter=192.168.0.165 file://con
| tsp --max-input-packets 7 -I file -P regulate --packet-burst 7 -O ip 227.7.7.7:9999 -l 192.168.0.165

@maxsharabayko maxsharabayko changed the title Srt adapter Transmission jitter after reconnection Oct 12, 2020
@mbakholdina mbakholdina modified the milestones: v1.5.0 - Sprint 24, v1.5.0 Oct 14, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[apps] Area: Test applications related improvements Type: Bug Indicates an unexpected problem or unintended behavior
Projects
None yet
Development

No branches or pull requests

3 participants