Recording Pipeline wants to get ES data from Playbin3 pipeline.

[HoonHee Lee]

Dear All.
 
Our company uses the playbin3 pipeline as a general pipeline.
Also, it is used for playing broadcasting(e.g live TV).

In this case, audio, video and subtitle are fed separately and each ES data is fed by multi appsrc.
 
Now we have to support recording the live TV in such DVR(Digital Video Recording).
For this, our recording pipeline wants to get ES data from playbin3 pipeline. not mean raw data.
 
Thus, we are thinking to use tee and appsink elements.
In front of MQ, tee element would split the ES data and appsink will post sample data.
Then, Recording pipeline will get ES data and record as well.
This is our approach.


 
Please review my approach and share your opinions.
I am always welcome any of approaches with ideas.
 
Thanks.

[Nicolas Dufresne-4]

Le samedi 01 octobre 2016 à 17:01 -0700, HoonHee Lee a écrit :
> Thus, we are thinking to use tee and appsink elements.
> In front of MQ, tee element would split the ES data and appsink will
> post
> sample data.
> Then, Recording pipeline will get ES data and record as well.
> This is our approach. 
>
> <http://gstreamer-devel.966125.n4.nabble.com/file/n4679907/TV_Pipelin
> e.png>

This link is broken.
_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel

[HoonHee Lee]

Hello Nicolas
 
I uploaded again captured image.

http://gstreamer-devel.966125.n4.nabble.com/file/n4679939/DVR_Pipeline.png

 
And I also will add queue element between tee and appsink.
Please check my approach and share your opinions.
 
Thanks.

[Nicolas Dufresne-5]

The link still does not work here.

Le 4 oct. 2016 6:57 PM, "HoonHee Lee" <[hidden email]> a écrit :

Hello Nicolas

I uploaded again captured image.

Please check my approach and share your opinions.

Thanks.



--
View this message in context: http://gstreamer-devel.966125.n4.nabble.com/Recording-Pipeline-wants-to-get-ES-data-from-Playbin3-pipeline-tp4679907p4679939.html
Sent from the GStreamer-devel mailing list archive at Nabble.com.
_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel

_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel

[HoonHee Lee]

Hello Nicolas
I am using firefox in ubuntu and inserted and linked image is shown.
And it also works well at chrome browser.
 
 
So, Which browser do you use?
Anyway I upload the image file.
DVR_Pipeline.png
 
Thanks.

[Sebastian Dröge-3]

On Tue, 2016-10-04 at 20:14 -0700, HoonHee Lee wrote:

> Hello Nicolas
> I am using firefox in ubuntu and inserted and linked image is shown.
> And it also works well at chrome browser.
>   
>   
> So, Which browser do you use? 
> Anyway I upload the image file.
> DVR_Pipeline.png
> <http://gstreamer-devel.966125.n4.nabble.com/file/n4679944/DVR_Pipeli
> ne.png>  
>  
> Thanks.
> 

The problem is probably that you're nabble for writing mails. It often
creates incomplete or otherwise broken mails for anybody but other
nabble users.

--
Sebastian Dröge, Centricular Ltd · http://www.centricular.com
_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel

[HoonHee Lee]

Thanks for your help.
 
I've checked subscribe button and got a confirm mail from [e-mail].
Then I did something and got a message with 'subscription has been accepted' and 'You are already subscribed'.
 
Did I something wrong? Or Do I have to more?
 
Please let me know which items are missed.
 
Thanks.

[HoonHee Lee]

Dear All
This is our approach.
   
We are wanting to add new delivery plugin between parsebin and multiqueue's input so that it would post sample data to recording pipeline.
                                                                                      MultiQ     Output
                    Input(s)                                                       Slots      Streams
 /-------------------------------------------------------------------------------\   /-------\  /------------- \
+---------------------------------------------------------------------------------------------------------------+
|                                                                                                                 |
| +----------------------------------------------------------------------------+                                |
| |   GstParseBin(s)                                                     |                                |
| |                +----------------------+                                    |  +-----+                     |
| |                |                        |---[parser]---[deliverybin]-[|--| Mul |---[ decoder ]-[|
|]--[ typefind ]---|  demuxer(s)  |-----------------[deliverybin]-[|--| ti     |                    |
| |                |  (if needed)       |---[parser]---[deliverybin]-[|--| qu  |                     |
| |                |                        |---[parser]---[deliverybin]-[|--| eu  |---[ decoder ]-[|
| |                +-----------------------+                                   |  +-----+                 ^  |
| +-----------------------------------------------------------------------------+        ^                  |  |
|                                                                                ^         |                  |  |
+-------------------------------------------------------------------------------+--------+-----------------+--+
 
 
We are temporary named as 'deliverybin' and it is not fixed yet.
It will be having tee element so that split data to multiqueue's input and appsink.
Also we are adding a queue element between tee and appsink in order to separate thread.

+------------------------------------------------+
| GstDeliveryBin                           |
| +----------------+                             |
| |                 |-----------------------------[|
| |                 |                              |
| |   Tee         |                             |
| |                 |                              |
| |                 |---[queue]-[appsink]  |
| +----------------+                             |
|                                                  |
+-------------------------------------------------|
                                     |          |
                                     |          |
         Post sample data --/----------/
 
 
Please check and review our approach.
And come up with expected problems and let me know.
 
I am always welcome if you have any of questions and opinions.
 
Thanks.

[HoonHee Lee]

Dear All.
 
I implemented an element as named splitappsink.
And I confirmed that it is plugged at parsebin of decodebin3.
 
splitter-negotiation_in_decodebin3.png
 
Please check my approach and share your opinions.
 
Thanks.