While hosting a Go Live stream, moho shows no picture of what is being sent. discordSharing reaches exactly one component
(src/renderer/src/components/CallView.tsx:36) and all it changes is the
button's icon and a line of text reading "You are sharing a screen".
The capture itself is running and has a perfectly good MediaStream - the
encoder is reading frames off it, and shareScreen already hands it back as ScreenShare.stream (src/renderer/src/lib/discordscreen.ts:149). Nothing
draws it.
What that costs is confidence. Somebody sharing has no way to tell whether they
picked the right window, whether it froze, or whether anything is going out at
all - they have to ask. It is also the only check available on a machine where
capture silently produces nothing, which has happened here before and presented
as Discord error 2012 rather than as an empty picture.
A small tile in the call view fed from that same stream, the way a camera
preview works, is the whole of it. No new capture and no second encoder - the
frames are already in the window.
While hosting a Go Live stream, moho shows no picture of what is being sent.
`discordSharing` reaches exactly one component
(`src/renderer/src/components/CallView.tsx:36`) and all it changes is the
button's icon and a line of text reading "You are sharing a screen".
The capture itself is running and has a perfectly good `MediaStream` - the
encoder is reading frames off it, and `shareScreen` already hands it back as
`ScreenShare.stream` (`src/renderer/src/lib/discordscreen.ts:149`). Nothing
draws it.
What that costs is confidence. Somebody sharing has no way to tell whether they
picked the right window, whether it froze, or whether anything is going out at
all - they have to ask. It is also the only check available on a machine where
capture silently produces nothing, which has happened here before and presented
as Discord error 2012 rather than as an empty picture.
A small tile in the call view fed from that same stream, the way a camera
preview works, is the whole of it. No new capture and no second encoder - the
frames are already in the window.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
While hosting a Go Live stream, moho shows no picture of what is being sent.
discordSharingreaches exactly one component(
src/renderer/src/components/CallView.tsx:36) and all it changes is thebutton's icon and a line of text reading "You are sharing a screen".
The capture itself is running and has a perfectly good
MediaStream- theencoder is reading frames off it, and
shareScreenalready hands it back asScreenShare.stream(src/renderer/src/lib/discordscreen.ts:149). Nothingdraws it.
What that costs is confidence. Somebody sharing has no way to tell whether they
picked the right window, whether it froze, or whether anything is going out at
all - they have to ask. It is also the only check available on a machine where
capture silently produces nothing, which has happened here before and presented
as Discord error 2012 rather than as an empty picture.
A small tile in the call view fed from that same stream, the way a camera
preview works, is the whole of it. No new capture and no second encoder - the
frames are already in the window.
Finished
https://git.salastil.com/Salastil/moho/commit/f700713
https://git.salastil.com/Salastil/nobilis/commit/a5eb3b4
https://git.salastil.com/Salastil/moho/commit/27f15df