RE: MPEG4 encoder not giving output

Hi Yuvraj, When you say not giving proper output, does that mean that the output is corrupted? Guess there are no failures observed. Can you send the absolute values for all the params that you use instead of variables? Also, can you try explicitly setting the captureWidth value same as that

RE: MPEG4 encoder not giving output

From: Yuvraj Pasi [mailto:yuvraj.p...@nextbitcpu.com] Sent: Wednesday, July 21, 2010 4:46 PM To: JayaKumar, PremKumar Cc: davinci-linux-open-source@linux.davincidsp.com Subject: Re: MPEG4 encoder not giving output Hi Prem, As I said we are using our custom based board not dvevm. we do

RE: DM365 H.264 Encoder size change problem

Jeremy, This scenario works with the DVTB application present in the DVSDK 3.10 installation. We could sequentially encode two YUV 420SP streams of size 1920x1088 and 1280x720 using two codec instances. However we have kept the maxWidth to 1920 and maxHeight to 1088 for both instances. Can

RE: JPEG Baseline Profile Encoder on C64x+ 2.00.002 Can't work on 6446 Linux

Hi Frank, Since you've created a JPEG encoder instance using base params, can you also give a try by using only the base IIMGENC1_DynamicParams instead of extended IDMJPGE_TIGEM_DynamicParams in your code? (I see that you need only base dynamic params to be set in your code.) Also, you can try

RE: TI JPEGENC 2.00.00.2 unable to call IMGENC1_create

Frank, To eliminate param setting issue, I would suggest trying the following parameters while creating the JPEG encoder instance? IMGENC1_Params.maxHeight = 480 IMGENC1_Params.maxWidth = 720 IMGENC1_Params.maxScans = 0 IMGENC1_Params.dataEndianness = 1 IMGENC1_Params.forceChromaFormat = 2

RE: Trouble building demos for dvsdk 2.10.00.

Is the EDMA3_LLD_INSTALL_DIR variable in the Rules.make set to the right path where the edma3_lld_xx package is installed? If not, please try building the demos after setting it. Regards, Prem -Original Message- From: davinci-linux-open-source-boun...@linux.davincidsp.com

RE: Using buildinstructions fatal error #5: could not open source file ti/xdais/dm/ividdec.h

From the error message you can see that the xdais path is tried to be picked from the cetools. Try setting USE_CETOOLS_IF_EXISTS = 0 in the xdcpaths.mak so that the path which you want to be set as xdais path in the XDCPATH will take effect. Regards, Prem

RE: Example code servers: Error: xdc.loadPackage: can't find package 'dsplink.dsp'

From the xdcpaths.mak file it looks like your DVSDK installation is having all the required components. So, cetools reference may not be required. And further not sure if your CE installation has the cetools in it. So, try setting USE_CETOOLS_IF_EXISTS := 0 instead of 1 in the xdcpaths.mak

RE: ARM application build issue

Can you check if XDCPLATFORM is rightly defined in your app's makefile? Regards, Prem Texas Instruments India -Original Message- From: davinci-linux-open-source-boun...@linux.davincidsp.com [mailto:davinci-linux-open-source-boun...@linux.davincidsp.com] On Behalf Of Jaya krishnan Sent:

RE: can't open engine

CE_DEBUG will not work in CE 1.02. You might have to use CE_TRACE for getting trace info on GPP side. http://tiexpressdsp.com/index.php?title=TraceUtil Regards, Prem Texas Instruments India -Original Message- From: davinci-linux-open-source-boun...@linux.davincidsp.com

RE: decode video problem

Hi, It depends on the way the video decoder algorithm is implemented. In such cases, usually, decoders will return with Extended Error(s) indicating either the input data is corrupted or there is insufficient input data for the process call to go through successfully. Application will be

RE: RE: decode video problem

the cause. Regards, Prem Texas Instruments India From: 姚寒冰 [mailto:ya...@tom.com] Sent: Friday, May 15, 2009 3:24 PM To: JayaKumar, PremKumar; davinci-linux-open-source@linux.davincidsp.com Subject: Re: RE: decode video problem Thank you to answer. But sometimes

RE: Re: I can't boot linux2.6.18 uImage in dm355

I faced similar issue when switching between kernel builds for different platforms. In such cases, a proper/full clean before build helped in getting the right uImage built. Probably, you can try that too. make distclean make ARCH=arm CROSS_COMPILE=arm_v5t_le- davinci_dm355_defconfig make

RE: DM355 mpeg4 encoding performance

Hi Andre, SPRS488e.pdf defines the performance measurement procedure. Please follow it for reproducing the numbers. According to it, the first I and P frame process call's numbers needs to be excluded while averaging. Also, the measurement should not be done for the first instance that is run

RE: difficulty in VDEC2 interface in dm6467

Unable to locate alg error might be due to a mismatch between the names defined in multiple places. Check out consistency of the alg names used: 1. Algorithm module name (+package path) matches with the algorithm module path mentioned in useModules( ) in the server's cfg file. 2.

RE: what I am missing here with DVEVM kit? How to solve this issue.

Dengyz, This issue would be most likely due to an incorrect mem setting in the bootargs. Guess mem=64M should work for a cmem insertion at 0x8500 Regards, Prem Texas Instruments India. -Original Message- From: davinci-linux-open-source-boun...@linux.davincidsp.com