Quote:

Tony Pabon (Intel) wrote:

Hi,
I believe I've reproduced the same issue and I'm investigating.

-Tony

Hi,Tony
I had recalled a piece of important information that I didn’t think of before.

Due to my own need, I had cancelled
if(nMin > (mfxU32)props.cBuffers) { hr = E_FAIL; }
in CEncoderInputPin::NotifyAllocator() method.(My post with this issue: http://software.intel.com/en-us/forums/topic/339247)

This works fine with my webcam. But the video source was replaced by a hd video capture card this time(as you can see in capturegraph.png).

Today, I rebuilt the filter by bringing the buffer number judgment statement back to the NotifyAllocator() method. Now graphedit automatically inserts a AVI Compressor everytime I tried to connect Infinite_Pin_Tee_Filter to h264_enc_filter . I think this implied that Infinite_Pin_Tee_Filter and h264_enc_filter failed to make an agreement(mMin>cBuffers) on the allocator. This is why on yesterday I could directly connect Infinite_Pin_Tee_Filter to h264_enc_filter but the encoder returned an error in runtime.

How can I modify the Infinite_Pin_Tee_Filter to collaborate with h264_enc_filter directly and perfectly?(Fortunately, Mircosoft provides the sample code for the infinite_pin_tee in Windows SDK. ).I don't want the existance of AVI Decompressor because it takes a great CPU load.

Many thanks.

-Patrick

Quote:

Tony Pabon (Intel) wrote:

Hi Patrick,

This would explain some of the behavior I was seeing too. I see others have seen this issue as well (http://software.intel.com/en-us/forums/topic/311877). I suspect the Infinite_Pin_Tee_Filter could be modified to require more cBuffers from the source filter, but I am not familiar with that code.

-Tony

Hi,Tony
I had just roughly gone through the infinite_pin_tee source code and discovered that it has overloaded the DecideAllocator() method and it assigned the allocator to the one from the upstream.
I will upgrade this post if I make any progress.
Thank you.

-Patrick

Quote:

Tony Pabon (Intel) wrote:

Hi Patrick,

This would explain some of the behavior I was seeing too. I see others have seen this issue as well (http://software.intel.com/en-us/forums/topic/311877). I suspect the Infinite_Pin_Tee_Filter could be modified to require more cBuffers from the source filter, but I am not familiar with that code.

-Tony

Hi,
I have modified the inifinite pin tee filter to require more buffers in the following code:

STDMETHODIMP
CTeeInputPin::NotifyAllocator(IMemAllocator *pAllocator, BOOL bReadOnly)
{
CheckPointer(pAllocator,E_FAIL);
CAutoLock lock_it(m_pLock);

// Free the old allocator if any
if (m_pTee->m_pAllocator)
m_pTee->m_pAllocator->Release();

// Store away the new allocator
pAllocator->AddRef();
m_pTee->m_pAllocator = pAllocator;

//Require 10 buffers
ALLOCATOR_PROPERTIES props;
pAllocator->GetProperties(&props);
props.cBuffers = 10;
ALLOCATOR_PROPERTIES actual;
pAllocator->SetProperties(&props,&actual);

// Notify the base class about the allocator
return CBaseInputPin::NotifyAllocator(pAllocator,bReadOnly);

} // NotifyAllocator

The MFX_ERR_NOT_INITIALIZED error still occurs after the graph starts. (EncodeFrameAsync returns MFX_ERROR_NONE for several times before it returns MFX_ERR_NOT_INITIALIZED).
It seems that the samples have not been released in the CBaseEncoder::DeliverNextFrame() method. The running code has not stepped into the sample release statements before the error is thrown.
if (!jt->pmfxSurface->Data.Locked)
{
MSDK_SAFE_DELETE(jt->pmfxSurface);
jt->pSample->Release();//has not been executed before MFX_ERR_NOT_INITIALIZED error
pEncoder->m_InputList.erase(jt);

break;
}

I’ve uploaded the inftee project files for you to investigate my problem.
What else should I do to the inftee filter?
Thanks.

-Patrick

Sorry,Eric,I've been busying preparing for exams recently.
I will be free next week.;) Please wait. Thanks!!

-Patrick

Hi Eric,
Sorry for keep you waiting so long.
My MSDK version is 3.0.774.38156. Driver version is 8.15.10.2696. And my CPU is i5-3570K.
Actually the MFX_ERR_NOT_INITIALIZED problem only occur when the capture source is "Analog Xbar+PCIe HD Caputre Device"(with 720p,50 frames/second).Using webcams like MS HD-5000,MS Lifecam Cinema,Logitech C525(I've all tried,under 720P,30frames/second) does not have such kind of problem.

-Patrick

Hi Eric,
I found out that I had made a mistake in setting cbAlign and cbBuffer. Now the graph works most of the time.
I will carefully re-check my modification part to the infinite_tee_pin.
I will report here if I get any progress.
Thank you!!

-Patrick