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

video error #1769

Open
XJY00 opened this issue Jul 10, 2024 · 9 comments
Open

video error #1769

XJY00 opened this issue Jul 10, 2024 · 9 comments
Labels
A-VoIP O-Uncommon Most users are unlikely to come across this or unexpected workflow S-Major Severely degrades major functionality or product features, with no satisfactory workaround T-Defect

Comments

@XJY00
Copy link

XJY00 commented Jul 10, 2024

Steps to reproduce

I configured the self-deployed jitis video service and applied config.json on the desktop client,
but after starting the call, I added rooms to different accounts on multiple devices to test.
Only the voice was normal, while the video and screen were not transmitted,
which was present in the element scene (beta version video room, Widget Windows, pop-up web pages).
I tried calling again on the self-deployed jitis web page and everything worked.
What happened? What should I do?

Outcome

What did you expect?

self-deployed jitis video service

What happened instead?

Only the voice was normal, while the video and screen were not transmitted,

Operating system

Windows11

Application version

Element 版本: 1.11.70 Crypto version: Rust SDK 0.7.1 (80a151e), Vodozemac 0.6.0

How did you install the app?

https://element.io/download

Homeserver

Synapse

Will you send logs?

Yes

@XJY00 XJY00 added the T-Defect label Jul 10, 2024
@dosubot dosubot bot added A-VoIP O-Uncommon Most users are unlikely to come across this or unexpected workflow S-Major Severely degrades major functionality or product features, with no satisfactory workaround labels Jul 10, 2024
@t3chguy t3chguy mentioned this issue Jul 10, 2024
@t3chguy
Copy link
Member

t3chguy commented Jul 10, 2024

For screensharing your issue is #683

@t3chguy
Copy link
Member

t3chguy commented Jul 10, 2024

Unfortunately the logs don't give any indication as to what is happening as they cannot get logs out of your jitsi iframe, you'd need to check the chromium console which you can open using Ctrl+I

@t3chguy t3chguy added the X-Needs-Info This issue is blocked awaiting information from the reporter label Jul 10, 2024
@XJY00
Copy link
Author

XJY00 commented Jul 10, 2024

I didn't understand what you meant, ctrl+ I should be used in where?
Nothing happened in the element desktop and widget window,
but I saved the element's web side browser log, and the pop-up window of the widget in the browser's log,
which I mentioned was the browser's F12 tool console log. And the browser model is vivaldi.
Is that right? The attachment is a log of two pages, and I hope I can express myself,
because my mother tongue is not English.

i.xjyofc.top-1720615049721.log
app.element.io-1720615076785.log

@t3chguy
Copy link
Member

t3chguy commented Jul 10, 2024

Sorry Control+Shift+I for the console, I haven't used Windows in a little while

@XJY00
Copy link
Author

XJY00 commented Jul 10, 2024

ok, chromium console log
vector-1720618235902.log

@t3chguy
Copy link
Member

t3chguy commented Jul 10, 2024

Can you clear the console, try sharing your video not screenshare as that is unsupported in Desktop as per #683 and share another console log as this one is quite long which makes it hard to see the problem

@XJY00
Copy link
Author

XJY00 commented Jul 10, 2024

  1. user1 join video room (Windows Element)
  2. user2 join video room (Android Nelement, has open camera)
  3. user1 open camera
  4. log end
    vector-1720618667671.log

I haven't looked at #683 carefully yet. If jitsi doesn't support it, is it possible to consider other open source projects instead? Such as https://github.com/screego/server/

@t3chguy t3chguy removed the X-Needs-Info This issue is blocked awaiting information from the reporter label Jul 10, 2024
@t3chguy
Copy link
Member

t3chguy commented Jul 12, 2024

If jitsi doesn't support it, is it possible to consider other open source projects instead? Such as screego/server

https://github.com/element-hq/element-call supports it fine, its already in Labs if you enable it via config.

@XJY00
Copy link
Author

XJY00 commented Jul 12, 2024

If jitsi doesn't support it, is it possible to consider other open source projects instead? Such as screego/server

https://github.com/element-hq/element-call supports it fine, its already in Labs if you enable it via config.

That said, there is already a better experimental feature element-call being developed that will also support our self-deployment in the future, so I've decided it's better to give up on jitsi and wait for an update on your project.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-VoIP O-Uncommon Most users are unlikely to come across this or unexpected workflow S-Major Severely degrades major functionality or product features, with no satisfactory workaround T-Defect
Projects
None yet
Development

No branches or pull requests

2 participants