• State
  • Locked Locked
  • Replies 6 replies
  • Subscribers 99 subscribers
  • Views 522 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

What is TI's official opinion for DM365-300MHz maximum resolution?

Seung Youl Lee10425
Prodigy 240 points


As far as I know, the maximum resolution of DM365-300Mhz is 1920x1080.

But, from DVSDK encoder codec(MPEG4,H.264) user guide, the maximum resolution is 1280x720.

Is it encoder codec library's limitation?

What is TI's official opinion for DM365-300MHz maximum resolution?

My development environments are the followings.

1. TI DSP : DM365-300Mhz

2. DVSDK version : dvsdk_2_10_01_18

Thank in advance.

  • 0
    TI__Mastermind 37340 points

    Resolution depends on the stage, from a video pipeline perspective (leaving encode/decode out for a minute), the best place to look for this information is the VPFE User Guide (http://focus.ti.com/general/docs/litabsmultiplefilelist.tsp?literatureNumber=sprufg8a ).  From this document, it appears that it supports 32K pixel x 32K pixel image sizes from a video input perspective, with subsequent video hardware blocks being constrained to lower line lenghts should you have these blocks enabled.  From the complete video pipeline perspective, 1920X1080 should not be an issue, in fact the video pipeline can support higher resolutions.

    Now let us consider the encode/decode libraries; you are correct that our current MPEG-4 and H.264 libraries suggest a max size of 1280x720 (720p); however, we do have newer libraries which should be coming out over the next month or so that will be able to support 1920x1080.  These should just be in the form of firmware (software library) updates.

    Hope this helps clear up the confusion.

  • 0 in reply to Juan Gonzales
    Expert 1055 points

    What frame rate will be supported by those newer libraries at 1920x1080? Which profiles/levels for H.264?

  • 0 in reply to Alexander Khvilivitzky
    TI__Mastermind 37340 points

    Unfortunately, we are going thru the testing phase and I do not have any numbers I can share at this point.

  • 0 in reply to Juan Gonzales
    Prodigy 240 points

    Thank you for your response.

    WeI have two DVSDKs. One DVSDK_2_10_01_18 is provided Appro Camera SDK and the other is DVSDK_2_10_01_18 is distributed by TI's DM365 official site.

    Appro DVSDK supports 1920x1080 for MPEG4 and H.264(framesize limitation). But, TI's DVSDK does not support 1920x1080. It's very confusing.

    Our company will license DM365 DVSDK. Does this DVSDK support 1920x1080 for both MPEG4 and H.264? 1920x1080 support is very critical for our IP network

    camera. 1280x720p IP PTZ network camera have been already produced by our competiting company.

    So, we want to know TI's official opinion for DM365-300MHz maximum resolution.

    Re-question.

    What is TI's official opinion for DM365-300MHz maximum resolution?

     

  • 0 in reply to Seung Youl Lee10425
    TI__Mastermind 19985 points

    Hi SY Lee,

    I believe the Appro IP Camera SDK mentions that the DVSDK used in the package is for Appro Camera. The sole reason of including DVSDK in Appro camera is to have camera specific enhancements in DVSDK. So we took the DVSDK 2.10.01.18 from TI official release and enhaced it for some fixes and features specific to Appro camera. This is why the version number is not changed.

     

    TI has not released any new DVSDK after 2.10.01.18. Please do not compare the DVSDK from Appro camera SDK against TI's official release.

    DVSDK in Appro camera is to be used in conjunction with Appro camera SDK. The license agreement also mentions it and we do not ensure the functioning of all demos in DVSDK released with Appro SDK.

     

    As far as official new release of DVSDK from TI is concened, i think you might have already got answers in other posts in this thread.

     

    Regards,

    Anshuman