Details
-
Type:
extRequest
-
Status: Closed
-
Priority:
Major
-
Resolution: Done
-
Fix Version/s: 2021
-
Component/s: FIWARE-TECH-HELP
-
Labels:None
-
HD-Chapter:Data
-
HD-Enabler:Kurento
Description
Dear FIWARE coach,
we forward you a support request received from a CreatiFI applicant we are
not able to solve.
Please let us know if you need direct contact with the submitter.
Thanks.
The issue refers to a previous jira ticket HELC-1418
<https://jira.fiware.org/browse/HELC-1418>
*****************************
Dear,
we do not see MediaFlowInStateChange - Ivan Gracia said he could produce
the event in a demo app - can we have the source for that app?
thanks
Paul
*****************************
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-creatifi-coaching@lists.fiware.org) instead of the old one.
_______________________________________________
Fiware-creatifi-coaching mailing list
Fiware-creatifi-coaching@lists.fiware.org
https://lists.fiware.org/listinfo/fiware-creatifi-coaching
[Created via e-mail received from: Andrea Maestrini <amaestrini@create-net.org>]
Issue Links
- relates to
-
HELC-1463
FIWARE.Request.Coach.CreatiFI.MediaFlowInStateChange event not seen in Kurento
-
- Closed
-
Activity
The media flow in/out events refer to media coming in out an endpoint to/from the pipeline. That means the "in" event is only fired when another endpoint is feeding media into a certain endpoint: MediaFlowInStateChange is fired whenever any endpoint receives media from another endpoint. This means that endpoint that receives media from the browser won't be firing this event. If you connect a player to a WebRTC endpoint, and execute play, the WebRTC endpoint will fire the MediaFlowInStateChange event.
On the other hand, in case of WebRTC endpoint receiving media from a remote peer (i.e. a browser), the event MediaFlowOutStateChange will be fired. This is because the media received from the remote peer is pushed into the pipeline.
webrtc.addMediaFlowInStateChangeListener(event -> {
log.debug("Media of type {} is {} from the pipeline", event.getMediaType(), event.getState());
});
webrtc.addMediaFlowOutStateChangeListener(event -> {
log.debug("Media of type {} is {} into the pipeline", event.getMediaType(), event.getState());
});
This is probably not well enough explained in the documentation. We'll try to fix that in the future.
Dear,
I forwarded your feedback to the accelerator, so before closing the ticket we wait some applicant feedback
BR
Dear,
the applicant is able to see the event. You can close the ticket.
BR
Dear,
I suggest you to forward the issue to the Kurento expert
BR