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

Add recipe to deploy qubes-video-companion for screensharing/videoconferencing #49

Closed
tlaurion opened this issue Apr 23, 2024 · 8 comments
Labels
new formula Enhancement request creation of a formula T: enhancement New feature or request

Comments

@tlaurion
Copy link

Commitment

I confirm that I have read the following resources:

Current problem (if any)

Sharing screens/webcam for people doing videoconferencing or live screensharing is complicated under Qubes.
https://github.com/QubesOS/qubes-video-companion resolved that.

But its not installed by default. qusal offers the possibility to do it easily and do the right thing creating the proper qubes to do ti efficiently.

Proposed solution

Another out of the box inexperience.

The value to a user, and who that user might be

User: ability to use camera easily
Documentarists: now they can use qubes-screenshot merged into dom0 deployment. But creating screencast videos is still convulated.
Developers: Easily share workflow leading to an error in github issues, screeencasting directly a single window content for recording, with/without sound.

@tlaurion tlaurion added the T: enhancement New feature or request label Apr 23, 2024
@tlaurion
Copy link
Author

tlaurion commented Apr 23, 2024

Not sure how to propose the proper way to do this though. It's a two part thing, dom0+template installation.

Seems like the workflow I see here is to add this in the default templates (xfce) so the companion is available into standard qubesos deployment vs in minimal templates cloned and specialized? Throughts?

@tlaurion
Copy link
Author

@ben-grande
Copy link
Owner

But its not installed by default. qusal offers the possibility to do it easily and do the right thing creating the proper qubes to do ti efficiently.

It won't be present in the default installation (explained at the bottom of this post).

Proposed solution

Another out of the box inexperience.

Possible.

The value to a user, and who that user might be

User: ability to use camera easily
Documentarists: now they can use qubes-screenshot merged into dom0 deployment. But creating screencast videos is still convulated.
Developers: Easily share workflow leading to an error in github issues, screeencasting directly a single window content for recording, with/without sound.

Thanks for writing this with details, it is important.

Not sure how to propose the proper way to do this though. It's a two part thing, dom0+template installation.

The Dom0 part is easy. The Template part for use with devices will be targetting sys-usb formula, the template tpl-sys-usb (optional installation of video-companion) at least in the documentation side, this way, you can target any other template with it:

qubesctl --skip-dom0 --targets=QUBE state.apply video-companion.install

Seems like the workflow I see here is to add this in the default templates (xfce) so the companion is available into standard qubesos deployment vs in minimal templates cloned and specialized? Throughts?

It will not be added to the default template by me for two reasons:

  • It's a WIP, that probably why it is not installed in the full template by default (Qubes OS decision);
  • Qusal doesn't install anything on the default templates, to always clone from a clean slate/template.

@ben-grande ben-grande added the new formula Enhancement request creation of a formula label Apr 24, 2024
@tlaurion
Copy link
Author

tlaurion commented Apr 24, 2024

Just make sure that you understand that qubes-video-companion needs to run in the "stream receiver" qube (where the screenshare is needed, where the videoconference will happen) and the qubes selected by the app is where the stream originates from.

QubesOS/qubes-issues#7991 (comment)

@ben-grande
Copy link
Owner

I am not sure it makes sense to create qubes for this package. What do you think?

Qusal already has things that can be used for sharing and receiving, such as browser and signal. The state that install the qubes-video-companion will target those qubes (at user's will, not by default).

@tlaurion
Copy link
Author

tlaurion commented May 26, 2024

As discussed it might make sense to think of integrating obs since the most ideal stream aggregatior here to advance what was presented by @deeplow https://m.youtube.com/watch?v=_UxndcxIngw&t=20052s, without the whole video editing with dgpu pass-through used for video editing.

Just being able to stream screen capture and my videocam with voice would be good enough to do short, unedited videos in my use case.

@ben-grande
Copy link
Owner

How did you install in Debian? Flatpak, Debian repo or Ubuntu PPA?

  • Flatpak I won't consider this time, I am avoiding it as the update method is not integrated in Qubes;
  • Debian repo should be the best, but I am afraid from time to time it can get old on Debian freezes before new major releases; and
  • Ubuntu PPA is not vetted by Ubuntu, but it is an official build by the OBSProject maintained by one of it's members, so it is not a random PPA or less trusted than OBS itself, PPA link. Didn't test if the PPA works on Debian, maybe it is not build with Debian in mind, just Ubuntu.

Debian releases are 1 year behind upstream, which for some software, it can make a great difference. I don't have much experience with OBS to justify the PPA, unless security patches are made much earlier to the Ubuntu PPA than to the Debian repos.

@ben-grande
Copy link
Owner

OBS is a client, every client has a formula, signal, browser, media etc. Please open an new issue about OBS if you want it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
new formula Enhancement request creation of a formula T: enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants