kms-windows port interest group #14
Comments
|
Oh, that sounds terrible. I can assist, but I can not work on this. I just have other priorities. |
|
@luismcosta, @chris64digital, @petergerten, @nintha, @Stefan-Z-Camilleri, @devblissit, @ArJavBi, I just want to make you aware of this issue here. |
|
Hi @sledz , this is a good initiative. Unfortunately I do not have that much bandwidth right now, so not sure how much time I can dedicate to this. That said, I am willing to help as I can. |
|
I think best way to proceed with this is to contact Kurento team with me so we can merge this into their project. |
|
Ciao @kirushyk, you write "...to contact Kurento team with me so we can merge..." |
|
No,
I just meant that's good idea in my opinion: to merge to main project.
… On Nov 6, 2017, at 16:32, pschuessler ***@***.***> wrote:
Ciao @kirushyk <https://github.com/kirushyk>, you write "...to contact Kurento team with me so we can merge..."
Does it mean you would/could support us contacting kurento team for further proceeding?
Greetings, Peter (from DResearch team)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#14 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ADSah7uvfIhawaKhyUkq9UEaq9iUkyIbks5szxhrgaJpZM4QF_mY>.
|
|
Okay, misunderstanding. Do you know any commercial parties/companies who are interested in pushing forward this issue? |
|
Looks like one who created this issue is interested :-) I am not sure I know somebody else. Maybe company named ESTOS. |
|
Thats true ;o) |
|
I would be happy with the current state - if a built would work. Did anyone get that far? (also see #13) |
|
@kirushyk: could you give a rough estimation of development effort expected for finishing the project (days/weeks)? |
|
What do you mean?
We can declare it finished right now.
… On Nov 7, 2017, at 10:32, pschuessler ***@***.***> wrote:
Reply to this email directly, view it on GitHub <#14 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ADSahzf-86LXfWTvfmrkGcy2N7TvqC1dks5s0BWogaJpZM4QF_mY>.
|
|
@kirushyk: okay, understood. Finsihed (except bug #13) but without additional feature we need for our purposes... Could you imagine to join a type of "extention project" in role as assistant (with limited effort on your side due to your current situation) for support to ensure the developers work on the right track? |
|
@kirushyk @sledz @Stefan-Z-Camilleri @pschuessler @petergerten Well, thanks to your snippets and notes I was able to compile KMS v. 6.7.1 for windows using MinGW-w64 via MSYS2 under Windows 7. After few weeks of work all seems to build just fine. Now, I've set environment variable GST_DEBUG=4, to see some log data and started the kurento-hello-world sample. From the log file all seems to be ok, but no image on remote side, even if client console states "Loopback established". Also, when the client is connected, some errors are displayed on the server console:
Log file attached Any help would be appreciated! Oh, if you want to have a look at my build you can download it from here: |
|
Please ignore the previous post. I just found my issue: I was missing libgstnice15.dll. |
|
Hi Slimbyte, |
|
Who is now manages development of Kurento Media Server? I think we should contact them and dedicate some time to merge Windows-related stuff into the their repository. |
|
@kendziorra the gdrive repo was updated with working binaries; so, you can use same download link to download my latest build: |
|
Hello @slimbyte, this is really great news. 👍 As @kirushyk wrote, the next step would be to integrate the things related to the Windows build into the upstream Kurento repositories so as not to have just a one-shot release. Could you imagine doing this job? If so, how much effort do you expect? And when could this be completed? In order to motivate you a little bit, we could well imagine offering a decent bonus (e.g. via Bountysource or another preferred way) for this task. |
|
Hi @sledz, I will be happy to do that job. Thanks for understanding. |
|
@sledz I represent the third party slimbyte is talking about. Feel free to send me an email: kms@skylab-mobilesystems.com |
|
Hello @slimbyte and @kms4win, we're not quite sure what "own my work" means in this case, probably it's a script or a build procedure. Irrespective of this, we believe it makes sense for everyone involved if this build procedure is made available in general and actively maintained by the community in the future. This is the only way to ensure that future features or bug fixes will find their way into the KMS Windows port. As I wrote above, we are willing to co-finance this task. (@kms4win, regardless of this I'll contact you by email) |
|
I think we should focus on making good contact with present Kurento team. |
|
@sledz yes, I replied the same day - looks like you did not get my mail. Will send again. |
|
hey everyone it will expire soon , if it can help please tell me before this saturday to renewal |
Unfortunately this project has fallen asleep since @kirushyk has finished the work here more or less.
On the other side there are some people interested in this port. Our company is one of them.
It would be very good to update the port to the latest Kurento version which has fixed a lot of bugs, a lot of features are still missing (e.g. H.264, see #4), the build process is a little horror, and so on.
At the moment our company does not have the manpower to work on these tasks ourselfs. So we are looking for other ones who are willing to form some kind of an interest group to finance some external ressources doing the work.
Interested parties please reply here or contact kms-windows@dresearch-fe.de!
The text was updated successfully, but these errors were encountered: