Other Parts Discussed in Thread: TVP7002
I close fdc in my MTB oms file,then the hvenc will not output anything to the encoded file.
Dose hvenc depends on the fdc?
This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Other Parts Discussed in Thread: TVP7002
I close fdc in my MTB oms file,then the hvenc will not output anything to the encoded file.
Dose hvenc depends on the fdc?
Feng,
Looking at the part of the pipeline where you are trying out your changes, (dei here is a dual out component)
vfcc->dei(->h264venc) (->vfdc),
the dei omx component needs all the three ports enabled (one input and two output) and buffers being available at those ports to function. If you close the vfdc component, then one of the output ports of dei starves of buffers and this will stall the entire pipeline. Hence you would see that h264 encoder has stalled as well.\
Archith
In the present pipeline as in the capture_encode demo as in EZSDK 5.2.1.59, yes. This because of DEI component's requirement of all input and output ports being populated with buffers for functionality (as explained in my previous post).
But it should be possible to construct a pipeline with
OMX-VFCC, OMX-TVP_CTRL (420SP, TVP7002 component-in)->OMX-H.264 VENC.
Here OMX-TVP_CTRL is for configuration purposes and VFCC and H.264 exchnage buffers with the ILclient. Same configuration for H.264 VENC, VFCC and TVP can be used as from the capture_encode demo. You will have to modify the demo code to route buffers from the VFCC to the H.264VENC.
Here there would be no dependency on vfdc, dei or any other OMX component.
Archith