# EOS message is not received

**URL:** https://discourse.gstreamer.org/t/eos-message-is-not-received/698
**Category:** General Discussion
**Tags:** android
**Created:** [December 16, 2023, 3:34am UTC](https://discourse.gstreamer.org/t/eos-message-is-not-received/698 "2023-12-16T03:34:09Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![abu\_abdulla](https://discourse.gstreamer.org/letter_avatar_proxy/v4/letter/a/3da27b/32.png) [@abu\_abdulla](https://discourse.gstreamer.org/u/abu_abdulla)
#### Post date: [December 16, 2023, 3:34am UTC](https://discourse.gstreamer.org/t/eos-message-is-not-received/698/1 "2023-12-16T03:34:09Z")

</div>

Hi,

I have used android tutorial-3 to build a pipeline that display and record at the same time.

> pipeline\_video = “udpsrc buffer-size=50000 port=5478 ! application/x-rtp,payload=96 ! rtpjitterbuffer latency=300 ! rtph264depay ! tee name=t t. ! queue ! h264parse ! mp4mux ! filesink name=fdisk async=false location=/storage/emulated/0/Download/test.mp4 t. ! queue ! decodebin ! videoconvert ! autovideosink sync=false”

the issue is that the generated file is not playable due to missing EOS. I have searched to find a solution for this but really couldn’t reach anywhere.  
1- send EOS in the gst\_native\_finalize (before and after quitting the main loop):

```auto
gst_element_send_event(data->pipeline_video, gst_event_new_eos());
GstMessage *msg;
msg = gst_bus_timed_pop_filtered(gst_element_get_bus(data->pipeline_video),
                                     2 * GST_SECOND, 
                                     (GstMessageType) (GST_MESSAGE_ERROR | GST_MESSAGE_EOS));

```

2- tried to send eos directly to mp4mux/fliesink, it gives me errors.  
3- tried this one also

```auto
/* tell pipeline to forward EOS message from filesink immediately and not
     * hold it back until it also got an EOS message from the video sink */
    g_object_set(data->pipeline_video, "message-forward", TRUE, NULL);

```

for some reason EOS is not reaching the pipeline, i tried to catch the messages everywhere in element, eos … nothing received

the file is in:

> **[player1.c](https://drive.google.com/file/d/12OT1jFMPTJbwTCx-u3i0fRScgu11vIfg/view?usp=sharing)**
>
> Google Drive file.

i would appreciate any hint

---

<div class="post-metadata">

### Author: ![ndufresne](https://discourse.gstreamer.org/user_avatar/discourse.gstreamer.org/ndufresne/32/10_2.png) [@ndufresne](https://discourse.gstreamer.org/u/ndufresne)
#### Post date: [January 17, 2024, 12:40am UTC](https://discourse.gstreamer.org/t/eos-message-is-not-received/698/2 "2024-01-17T00:40:53Z")

</div>

You might be hitting this [bug](https://gitlab.freedesktop.org/gstreamer/gstreamer/-/merge_requests/5451)? Please try the patch and let us know. This code needs a unit test to be merged.

---

<div class="post-metadata">

### Author: ![abu\_abdulla](https://discourse.gstreamer.org/letter_avatar_proxy/v4/letter/a/3da27b/32.png) [@abu\_abdulla](https://discourse.gstreamer.org/u/abu_abdulla)
#### Post date: [January 20, 2024, 8:06am UTC](https://discourse.gstreamer.org/t/eos-message-is-not-received/698/3 "2024-01-20T08:06:43Z")

</div>

thanks for the hint but I’m developing on android so i do not know how to prepare the gstreamer universal binaries with this patch.

---

<div class="post-metadata">

### Author: ![vivideradicator](https://discourse.gstreamer.org/letter_avatar_proxy/v4/letter/v/ec9cab/32.png) [@vivideradicator](https://discourse.gstreamer.org/u/vivideradicator)
#### Post date: [May 31, 2024, 7:37pm UTC](https://discourse.gstreamer.org/t/eos-message-is-not-received/698/4 "2024-05-31T19:37:12Z")

</div>

Build using Cerbero, it will create the Android binaries for you from my understanding.

---

<div class="post-metadata">

### Author: ![abu\_abdulla](https://discourse.gstreamer.org/letter_avatar_proxy/v4/letter/a/3da27b/32.png) [@abu\_abdulla](https://discourse.gstreamer.org/u/abu_abdulla)
#### Post date: [March 3, 2025, 4:21am UTC](https://discourse.gstreamer.org/t/eos-message-is-not-received/698/5 "2025-03-03T04:21:02Z")

</div>

still facing this issue even with the latest 1.25.90 version
