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

Cannot play url ingress locally #299

Open
serhiynovos opened this issue Aug 16, 2024 · 4 comments
Open

Cannot play url ingress locally #299

serhiynovos opened this issue Aug 16, 2024 · 4 comments

Comments

@serhiynovos
Copy link

serhiynovos commented Aug 16, 2024

When I start ingress to play audio by local ip address it's not being played, I just wee EOS log

image

http://192.168.28.149/cms/public/uploads/audios/fa5d1cdc105793d43a64f71032ee6730d7.mp3

I tried to use remote host and http with the same file and it played well

@serhiynovos
Copy link
Author

After some research I found that this issue not only with local urls but also can happen with remote URLs for audio and video but less frequently.

1.4.0 version is working fine and starting from 1.4.1 version I'm facing this issue. On 1.4.1 release notes I see this PR #250 which I feel can be root of cause

@Yohe-Am
Copy link

Yohe-Am commented Nov 27, 2024

We're running into this as well. It seems not all files cause this issue. I'm not sure what exact property leads to the issue (it doesn't seem to be codecs) but I can share the ffprobe output if needed.

@serhiynovos
Copy link
Author

We're running into this as well. It seems not all files cause this issue. I'm not sure what exact property leads to the issue (it doesn't seem to be codecs) but I can share the ffprobe output if needed.

As I understand in 1.4.1 release they added asynchronous room joining which has some sync issue which means as let latency between ingress and http source than more frequently it happen. For me if http source and ingress are running in the same k8s cluster where latency is close to 0 it always happens. In other cases when try to use remote it's more stable but still is not working as solid as 1.4.0

@Yohe-Am
Copy link

Yohe-Am commented Nov 28, 2024

Yeah, your diagnosis is correct. The issue completely disappears when I revert the changes made in the PR.

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

No branches or pull requests

2 participants