I have the following pipeline that use in c++ that I switch between each
branch on the tees. I will eos on one branch and start recording on the
Block teePads,Eos through queues,unlink queues from tee, null each
element,unblock the tee,release pads
request pads on tees,link pads to queues, play each element
for some reason when I go to start the branch after it was null last time I
stopped it, the last flow return was flushing. why would that be? It doesn't
happen every time I go to start a new one it just happens to occur the one
time. The branch doesn't start correctly so I have to stop it. If i try to
stop it it can't block the tee that is flushing. What would be the reason?
Well I guess this didn't work at all. The rest of the pads beyond the tee are
fine. for some reason at the tee pad src_2 or src_1 are flushing even though
I released the pads from the tee. It just happens randomly.
if you remove the probe then release the pad from the tee could the flushing
affect right when I remove the probe? So If stop the flushing on each
element before removing the probe could that be the answer to my problem?