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.

DM3730 H.264 in DVSDK 4.02

Other Parts Discussed in Thread: DM3730

Hello,

 

I had a DM368 running DVSDK 2.1 and I am able to decode the following stream:

 

rtsp://38.96.15.46/Stream1

 

But, when I go to 4.02 I then get a fatal bit error 0x0. I just went back to 2.1 at the time because I didn't have time to figure it out.

 

Now I am on DM3730 with 4.02 and see the same error again. I am wondering what changed from 2.1 to 4.02 that would cause this. Can someone at TI (or some other genious) take a look at this video stream and tell me why I am getting this error?

 

I am using Gstreamer with known good working pipeline on DVSDK2.1.

 Here is a trace:

 

http://pastebin.com/EPwtSZkT

 

Thanks

 

Tim

  • Anyone? Anyone at TI can help with this?

  • Tim,

          I can not access neither stream (rtsp://38.96.15.46/Stream1) nor the trace (http://pastebin.com/EPwtSZkT), Please re-upload them to investigate further.

         Could you also help with link from where you downloaded the DVSDK version 2.10 for DM3730.

    Thanks & Regards,

    Velan

  • Hi Velan,

    Thanks for the response. Where are you located? I can get to both the pastebin and the video. The video is coming from the US in California.

    I did not have DVSDK 2.1 on the DM3730, that was on the DM368. I was stating that I can decode the video on DM368 in DVSDK 2.1 on DM368 using Gstreamer-ti. I experience the same problem on DVSDK 4.02 in both DM368 and DM3730. I am troubleshooting right now on DM3730. Point is I am getting the following error from the above stream:

    1. @16,690,002us: [+0 T:0x44c47470 S:0x44c462b4] ti.sdo.ce.video2.VIDDEC2 - VIDDEC2_process> Exit (handle=0x1586dc8, retVal=0xffffffff)
    2. @16,690,032us: [+2 T:0x44c47470 S:0x44c46304] ti.sdo.dmai - [Vdec2] VIDDEC2_process() ret -1 inId 0 inUse 0 consumed 1500000
    3. @16,690,063us: [+2 T:0x44c47470 S:0x44c46304] ti.sdo.dmai - [Vdec2] VIDDEC2_process() non-fatal error 0x0

    Maybe you can try the pastebin again? If not I can copy the whole thing in here.

    Thanks

    Tim

  • Tim,

           In fact DVSDK 2.10.01.18 was particular for DM365, any it should work for DM368 also.

           While looking at the package The codec versions are as below

           DVSDK 2.10.01.18 uses H.264 dec codec version: 01.00.00.08

           DVSDK 4.02.00.06 uses H.264 dec codec version: 02.00.00.10

           In fact the codec version is advanced one, it is strange that this problem is happeinging in the latest codec. It is not worth comparing DM3730 at present as the codec implementation is different between DM36X and DM3730. At present it is one data point.

          Iam in Bangalore, Please attache the stream in this thread itself as other people will refer to this, or you can send mail (velan@ti.com) if there are any troubles.

    Thanks & Regards

    Velan

  • 2526.test_stream.mp4

     

    OK, let me know if you get this OK. I just record the stream from VLC to MP4 file. But normally, the video is just RTP H.264 720p MP 3.1

     

    Thanks for any help to figure this one out.

     

    Tim

  • Tim,

           I played the stream in VLC & it works fine. I would suspect some kind of stringent error check in later codec, which might got ignored in previous version.

           I am not so expert in codec, I have asked codec expert to look in to this.

           Could you please confirm if the decoding continues further for remaining frame or you observe hung or error thrown for all frames

    Thanks & Regards

    Velan

  • Hi Velan,

    Thanks for the update. I think there is something there as well because the older codecs would play it no problems. No, this happens. It doesn't completely stop, but it just keeps giving that error and never displays any images. So it is parsing the video but not decoding.

    Tim

  • Velan,

    Any word from the CODEC engineer?

    Thanks

    Tim