Hi
We are facing with DM365 MPEG2 Encoding troubles such as unexpected Block Noise and unexpected Green Overlapping at each macro block basis.Please look at the sample small bitmap file for your understanding.(GreenErrorSample.bmp)
Are there any countermeasures?
・MPEG-2 Encoder: 01.00.00.08・DVSDK: 2.10.01.18・Input: NTSC/PAL・VBRthe parameters will be posted later.
If you see the attached mpeg file (test45_MPEG2_NTSC_M2N5_p_0.mpg) which was generated by DM365 Codec, you can find out all of the I Frames are overlapped Green and different from all of P frames.It is a little bit hard to see with the naked eye but if you analyze with some mpeg analysis you could definitely could find.
Anybody help us.
Regards,Takeshi
Takeshi-san,
Please elaborate on the issue that you are seeing. I tried using elecard botstream analyzer and could not understand. Please explain more.
Also do an experiment on your side. Write the YUV to a file before encoding. Analyse the YUV for green overlap. If there is green overlap in the capture then encoder is fine and we will ask capture driver team to look into it.
Regards,
Neelakanth
Please elaborate on the issue that you are seeing. I tried using elecard bitstream analyzer and could not figure it out. Please explain more.
Neelakanth-san,
Thank you for quick response. I thought it is very easy to reproduce, but I will let you know how and our parameters later on.However, if you look at the following zoom-uped file, you can understand what is happening on our side.
1) 8x8 macro block noise2) Unexpected Green color at 8x8 basis.
Do you see this kind of phenomena before? Or can you say something that what could cause the problem?
I'll post the sequence and parameters.
When the customer input only Black & White (CrCb=128), still Green coloar is unexpectedly added.Can you advise what is happening to this Encoder?
The parameters is as below.
== VIDENC1_Params ========= encodingPreset : 2 rateControlPreset : 1 maxHeight : 480 maxWidth : 720 maxFrameRate : 30000 maxBitRate : 4096000 dataEndianness : 1 maxInterFrameInterval: 1 inputChromaFormat : 9 inputContentType : 1 reconChromaFormat : 9 == IMP2VENC_Params ======== aspectRatio : 2 pixelRange : 1 timerResolution : 30 ME_Type : 1 QscaleType : 0 IntraDCPrec : 0 hdvicpHandle : (nil) == VIDENC1_DynamicParams == inputHeight : 480 inputWidth : 720 refFrameRate : 30000 targetFrameRate : 30000 targetBitRate : 4096000 intraFrameInterval : 5 generateHeader : 0 captureWidth : 1440 forceFrame : -1 interFrameInterval : 0 mbDataFlag : 0
Takeshi
Check input to encoder? To me looks like it may be some issue with capture.
No. Even if we input no color data (like as U=0x80h, V=0x80h), DM365 generated encoded data with color information.
The actual unexpected green color is just added as "three value", such as if we put R=95, G=95, B=95 then DM365 Encoder generated like as R=95, G-98, B=95.The above still picture was emphasised for easy to understand. Therefore it is dificult to see the differences especially in moving pictures.
Do you recognize this phenomenon?
This post getting discussed over email though TI FAE. Closing this thread.