| 1 |
OUTDATED |
| 2 |
-------- |
| 3 |
|
| 4 |
|
| 5 |
case 1) |
| 6 |
|
| 7 |
(--------------------------------------------------) |
| 8 |
! bin ! |
| 9 |
! (--------) (--------) (--------) ! |
| 10 |
! ! fakesrc! !identity! !fakesink! ! |
| 11 |
! ! 1 src ----- sink 1 src ---- sink 1 ! ! |
| 12 |
! (--------) (--------) (--------) ! |
| 13 |
! ! |
| 14 |
! (--------) (--------) (--------) ! |
| 15 |
! !fakesrc ! !identity! !fakesink! ! |
| 16 |
! ! 2 src ----- sink 2 src ---- sink 2 ! ! |
| 17 |
! (--------) (--------) (--------) ! |
| 18 |
(--------------------------------------------------) |
| 19 |
|
| 20 |
just two scheduled chains in a single bin. |
| 21 |
|
| 22 |
.scheduling. |
| 23 |
|
| 24 |
we have two chains here fs1-i1-fsk1 and fs2-i2-fsk2 |
| 25 |
fakesrc1 will output 1 buffer, fakesrc2 3 buffers |
| 26 |
|
| 27 |
.eos. |
| 28 |
|
| 29 |
fs1 will return a NULL buffer on EOS. the scheduler |
| 30 |
detects the NULL buffer and puts chain1 in EOS so that it |
| 31 |
doesn't get scheduled again. The scheduler fires the EOS |
| 32 |
signal for all the elements in the chain and puts the fs1 |
| 33 |
element in the READY state. |
| 34 |
|
| 35 |
the same procedure happens for chain2. At that point, the bin |
| 36 |
has no chains to schedule and so it fires EOS. |
| 37 |
|
| 38 |
|
| 39 |
case 2) |
| 40 |
|
| 41 |
(---------------------------------------------------) |
| 42 |
! bin ! |
| 43 |
! (--------) (--------) (---------) ! |
| 44 |
! ! disksrc! ! mpg123 ! !audiosink! ! |
| 45 |
! ! 1 src ----- sink 1 src ---- sink 1 ! ! |
| 46 |
! (--------) (--------) (---------) ! |
| 47 |
! ! |
| 48 |
! (--------) (--------) (---------) ! |
| 49 |
! !disksrc ! ! mpg123 ! !audiosink! ! |
| 50 |
! ! 2 src ----- sink 2 src ---- sink 2 ! ! |
| 51 |
! (--------) (--------) (---------) ! |
| 52 |
(---------------------------------------------------) |
| 53 |
|
| 54 |
same as case 1, an mp3 mixer where the mixing is performed |
| 55 |
in hardware (in the audiosink). |
| 56 |
we want to show how the EOS state can be undone. |
| 57 |
|
| 58 |
.scheduling. |
| 59 |
|
| 60 |
we have two chains here ds1-mpg1-ask1 and ds2-mpg2-ask2 |
| 61 |
the song in chain1 is about to end, chain2 has just begun |
| 62 |
playing a song. |
| 63 |
|
| 64 |
.eos. |
| 65 |
|
| 66 |
fs1 will return a NULL buffer on EOS. the scheduler |
| 67 |
detects the NULL buffer and puts chain1 in EOS so that it |
| 68 |
doesn't get scheduled again. The scheduler fires the EOS |
| 69 |
signal for all the elements in the chain and puts the fs1 |
| 70 |
element in the READY state. |
| 71 |
|
| 72 |
the app sets the new location for the disksrc. The element is |
| 73 |
put in the PLAYING state, the chain is marked !EOS so that |
| 74 |
it will be scheduled again. |
| 75 |
|
| 76 |
|