Uploaded image for project: 'Help-Desk'
  1. Help-Desk
  2. HELP-5435

FIWARE.Request.Tech.Data.Stream-oriented.Re: Update on Kurento implementation

    Details

    • Type: extRequest
    • Status: Closed
    • Priority: Major
    • Resolution: Done
    • Fix Version/s: 2021
    • Component/s: FIWARE-TECH-HELP
    • Labels:
      None

      Description

      Hi there,

      yesterday I asked for help to Luis López Fernández about kurento
      development, and, being me part of a FIWARE acceleration program (company
      sofasession), he suggested me to contact FIWARE helpdesk directly.
      It's about developing and installing a new kurento module (not filter).
      All the details are in the forwarded email.

      Hope to hear from you soon,
      Thanks,

      Alberto Pierini

      On Mon, Nov 30, 2015 at 7:09 PM, Luis López Fernández <luis.lopez@urjc.es>
      wrote:

      > Hi Alberto,
      >
      > See comments in-line
      >
      >
      > El 30/11/2015, a las 17:00, Alberto Pierini <albertopierini@gmail.com>
      > escribió:
      >
      > Hi Luis,
      >
      > I'm Alberto, one of the developer at sofasession.
      > As you know we are in the process of integrating kurento functionalities
      > in our technology stack. We already managed to plug kurento in our
      > signalling server, and establish peer connections between the clients and
      > kurento.
      >
      > Unfortunately now I'm struggling to implement a brand new kurento module.
      > This new GStreamer module should mix local tracks and "expose" the src
      > pad. I already implemented the gstream logic but unfortunately the process
      > to port it into kurento is far from trivial. There's no documentation about
      > it, and the small sample to create a new module is about creating a filter,
      > according to the forum it is kind of outdated, and it doesn't compile
      > anyway.
      >
      >
      > Kurento extensibility mechanism are designed for filters. Kurento
      > documentation dealing with Filter extensions is up to date and we don't
      > have any (serious) reports of having it out of sync or failing in
      > compilation. Creating a Kurento extension out of the filter model is, as
      > you are noticing, quite complex and requires to manage a lot of different
      > variables and conditions. In general that's not a trivial task.
      >
      > I was wondering if you could help anyhow in this process.
      >
      >
      > I understand that you are coming from a FIWARE acceleration. In that case,
      > you need to use the FIWARE helpdesk for receiving support. Open a ticket
      > with your request and we'll figure out how to address it.
      >
      > Right now the only documentation that I have access to, is the one located
      > at https://www.kurento.org/docs/current/index.html. Is there a more
      > technical, more developer-oriented one available perhaps?
      >
      >
      > This is the most advanced documentation we have and it should be enough
      > for doing filter extensions. For going deeper into KMS internals I'm afraid
      > the code is the only available additional resource.
      >
      >
      > I also recently asked for help in the forum (
      > https://groups.google.com/forum/#!topic/kurento/N6St7t1EvKs
      > https://groups.google.com/forum/#!topic/kurento/8E2NtDodPlI).
      >
      >
      > I saw it, but as you have noticed, doing such type of extension is
      > complex. For being able to really help you I would need to invest many
      > hours of my developers and FIWARE is not providing such much resources now
      > (Kurento budget in FIWARE has been cut in 60K€ in the last couple of
      > months). Lets open the issue in the FIWARE help desk (so that the time we
      > invest on it officially counts from FIWARE perspective) and lets work
      > together to see if we can provide you some hints on how to progress.
      >
      > Best regards.
      >
      >
      >
      > Thanks,
      > –
      > Alberto Pierini
      >
      > On Tue, Nov 24, 2015 at 10:28 AM, Carmen Mac Williams <
      > Carmen@grassroots-arts.eu> wrote:
      >
      >> Hi Helmut,
      >>
      >> Danke für die Info.
      >>
      >> My contact person for Kurento is
      >>
      >> Luis López Fernández luis.lopez@urjc.es
      >>
      >> Subdirector de Investigación y Relaciones con la Empresa
      >> Escuela Técnica Superior de Ingenieros de Telecomunicación
      >> Universidad Rey Juan Carlos
      >> http://www.etsit.urjc.es
      >> e-mail: luis.lopez@urjc.es
      >> Tf1: +34 914 888 747
      >> Tf2: + 34 914 888 713
      >>
      >> Ich habe mit meinem Partner Dirk Krause (Technischer Leiter von
      >> Pixelpark) selbst den Kurento Enabler ausprobiert und installiert im
      >> Februar 2014. Ich sende Dir unseren Email Exchange.
      >>
      >> Vielleicht richte Dich direct an ihn.
      >>
      >> Seine Mitarbeiter sind Ivan Boni und Miguel.
      >>
      >>
      >>
      >> Weiter hat Johnny von Iminds mir erzählt, dass Du eine telefonische
      >> Beratung von Iminds Living Lab bekommen hast.
      >>
      >>
      >>
      >> Sie haben mir gesagt, dass Du Ihnen in diesem Gespräch gesagt hast, dass
      >> “your ideas and Your cofounders may not be aligned. “
      >>
      >> Gibt es vielleicht ein Problem in Deinem Team?
      >>
      >>
      >>
      >> Viele Grüsse
      >>
      >>
      >>
      >> Carmen
      >>
      >>
      >>
      >> Von: Helmut Herglotz h.herglotz@sofasession.com
      >> Gesendet: Montag, 23. November 2015 14:22
      >> An: 'Carmen Mac Williamss' <Carmen@grassroots-arts.eu>
      >> Cc: s.bider@sofasession.com; Alberto Pierini <albertopierini@gmail.com>
      >> Betreff: Update on Kurento implementation
      >>
      >>
      >>
      >> Hi Carmen,
      >>
      >>
      >>
      >> Just a short update from our side:
      >>
      >>
      >>
      >> We have been working on implementing Kurento into our system
      >> architecture. Alberto or Stefano contacted you regarding a technical issue,
      >> which we were able to resolve on our own. Alberto contacted Franck Le-Gall
      >> a couple of days ago with a technical question, which he was not able to
      >> answer (Franck referred Alberto to a newsletter subscription… this is a
      >> good way to get updated about news, but will not help in solving concrete
      >> questions in case they pop up).
      >>
      >>
      >>
      >> We met Ivan Garcia from Kurento in Vienna earlier this year, we’ll also
      >> get in touch with him.
      >>
      >>
      >>
      >> Thanks a lot and talk soon!
      >>
      >>
      >>
      >> Helmut
      >>
      >
      >
      >

      Since January 1st, old domains won't be supported and messages sent to any domain different to @lists.fiware.org will be lost.
      Please, send your messages using the new domain (Fiware-tech-help@lists.fiware.org) instead of the old one.
      _______________________________________________
      Fiware-tech-help mailing list
      Fiware-tech-help@lists.fiware.org
      https://lists.fiware.org/listinfo/fiware-tech-help
      [Created via e-mail received from: Alberto Pierini <albertopierini@gmail.com>]

        Activity

        Hide
        fw.ext.user FW External User added a comment -

        Hi,

        thanks a lot for your reply.
        My module seems to work properly.

        Please check my comments inline.

        On Tue, Dec 15, 2015 at 6:13 PM, Help-Desk <jira-help-desk@fi-ware.org>

        I call gst_element_sync_state_with_parent just with appsink and appsrc,
        exactly as playerendpoint does.
        There are two bins, the internal pipeline, and self, also exactly as
        playerendpoint.
        I manage the state of the internal pipeline, and it switchs correctly
        between play, stop and pause.

        Could you please be a bit more specific? With "a player" what do you mean?
        At the beginning I did some experiments with composite, but back then it
        didn't seem a good idea to use it. Also, I'm not sure it is goin to support
        all features we will need: states, eos, seek, volumes for each input.

        Cheers,

        Alberto

        Show
        fw.ext.user FW External User added a comment - Hi, thanks a lot for your reply. My module seems to work properly. Please check my comments inline. On Tue, Dec 15, 2015 at 6:13 PM, Help-Desk <jira-help-desk@fi-ware.org> I call gst_element_sync_state_with_parent just with appsink and appsrc, exactly as playerendpoint does. There are two bins, the internal pipeline, and self, also exactly as playerendpoint. I manage the state of the internal pipeline, and it switchs correctly between play, stop and pause. Could you please be a bit more specific? With "a player" what do you mean? At the beginning I did some experiments with composite, but back then it didn't seem a good idea to use it. Also, I'm not sure it is goin to support all features we will need: states, eos, seek, volumes for each input. Cheers, – Alberto
        Hide
        fw.ext.user FW External User added a comment -

        On Tue, Dec 15, 2015 at 7:20 PM, Help-Desk <jira-help-desk@fi-ware.org>

        Ok, yes, I noticed that!
        When I was pausing and then resuming, the stream was starting from the
        beginning with odd behaviors. The reason was that I had a mistake in my
        code,
        this: gst_bin_add(GST_BIN(self->priv->pipeline), appsrc);
        instead of: gst_bin_add(GST_BIN(self), appsrc);

        Show
        fw.ext.user FW External User added a comment - On Tue, Dec 15, 2015 at 7:20 PM, Help-Desk <jira-help-desk@fi-ware.org> Ok, yes, I noticed that! When I was pausing and then resuming, the stream was starting from the beginning with odd behaviors. The reason was that I had a mistake in my code, this: gst_bin_add(GST_BIN(self->priv->pipeline), appsrc); instead of: gst_bin_add(GST_BIN(self), appsrc);
        Hide
        llopez NaevaTeC Development Team added a comment -

        Manuel Escriche Please, do not close the issue yet. We are trying to solve a quite comple problems and I feel there are still some topics to be discussed. I'll close the issue a soon as we feel that the development is fully functional.

        Show
        llopez NaevaTeC Development Team added a comment - Manuel Escriche Please, do not close the issue yet. We are trying to solve a quite comple problems and I feel there are still some topics to be discussed. I'll close the issue a soon as we feel that the development is fully functional.
        Hide
        llopez NaevaTeC Development Team added a comment -

        We didn't have further news in relation to this issue. Hence, we understand it has been solved. We close it.

        Show
        llopez NaevaTeC Development Team added a comment - We didn't have further news in relation to this issue. Hence, we understand it has been solved. We close it.
        Hide
        fw.ext.user FW External User added a comment -

        I think this issue can now be closed.

        On Wed, Dec 16, 2015 at 9:31 AM, Alberto Pierini <albertopierini@gmail.com>

        Show
        fw.ext.user FW External User added a comment - I think this issue can now be closed. On Wed, Dec 16, 2015 at 9:31 AM, Alberto Pierini <albertopierini@gmail.com>

          People

          • Assignee:
            llopez NaevaTeC Development Team
            Reporter:
            fw.ext.user FW External User
          • Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: