[META] Windows/MacOS support mega thread #57
Comments
ehfd
added
enhancement
|
// Removal of patches to the GStreamer build process in #51 means that the binary build available from the project for Windows will work without additional alterations. Does this mean I can currently run a compile of the project while removing the patches to make a windows build? Answer from maintainer: Yes, but the capture interface and input interface are not written. |
|
We have a channel specifically for Windows development. |
|
Hi folks, what's the status of Windows development ? |
|
@ehfd would you be able to point me to a branch with the windows port ? I looked at the forks but couldn't find anything windows specific. |
|
@ehfd still interested in seeing code for the windows port. Any updates on when that might be available ? |
|
hmmmmmm - I would very much like to see any selkies code ported to windows. |
|
Hello @ehfd and all. Really sorry for the Windows port has not been
released. I was facing on a plenty of gstreamer connection bug on my local
repo and after many fail attempts I decide refactore and revise all code,
most of them on gstreamer webrtc core.
Em qui., 27 de abr. de 2023 às 23:13, Seungmin Kim ***@***.***>
escreveu:
… @callTx <https://github.com/callTx>
—
Reply to this email directly, view it on GitHub
<#57 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AIYW2VRTYTSJ624N4CJXVNLXDMRWFANCNFSM6AAAAAAQWL57OU>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
Don't worry guys I'll not give up this project.
Em sex., 28 de abr. de 2023 às 08:43, callTX ***@***.***>
escreveu:
… Hello @seungmin Kim and all. Really sorry for the Windows port has not
been released. I was facing on a plenty of gstreamer connection bug on my
local repo and after many fail attempts I decide refactore and revise all
code, most of them on gstreamer webrtc core.
Em qui., 27 de abr. de 2023 às 23:13, Seungmin Kim <
***@***.***> escreveu:
> @callTx <https://github.com/callTx>
>
> —
> Reply to this email directly, view it on GitHub
> <#57 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AIYW2VRTYTSJ624N4CJXVNLXDMRWFANCNFSM6AAAAAAQWL57OU>
> .
> You are receiving this because you were mentioned.Message ID:
> ***@***.***>
>
|
|
@callTx thanks, looking forward to this. Even though not complete, why don't you share the code on a branch? I'm very keen to take a look. Also, I may be able to help with port. |
|
@callTx |
|
The code has become too Linux-centric. Whoever wants to do this must clean up the code to distinguish elements between Windows and Linux. |
ehfd
changed the title
Windows support is in progress with the contribution from the community with @callTx mainly working on the project (edit: seems like it has stalled).
For Windows, the pipeline should add
d3d11screencapturesrc(screen capture),d3d11colorconvert(color convert), andwasapiorwasapi2(audio capture).In addition, it would be worth adding the
mfh264encandmfvp9encencoder pipelines for Windows native encoding capabilities as well asnvd3d11h264enc,nvd3d11h265enc, andnvd3d11av1encfor NVIDIA, which also may be used for Windows.Assess the implementation for
pynputfor Windows input. Apparently, there are no specific dependencies.Removal of patches to the GStreamer build process in #51 means that the binary build available from the project for Windows will work without additional alterations.
For MacOS,
pyobjc-framework-applicationservicesandpyobjc-framework-quartzare the frequently used interfaces for input.avfvideosrc capture-screen=true(video capture),glcolorconvert(color convert, not sure), andosxaudiosrc(audio capture) are probably the way to go for media capture.Relevant to #34.
The text was updated successfully, but these errors were encountered: