• Join
  • Sign In with my.TI Login
Texas Instruments
  • Products
  • Applications
  • Tools & Software
  • Support & Community
  • Sample & Buy
  • About TI
Sample & Purchase Cart Sample & Purchase Cart
  • Search
  • Advanced
TI E2E™ Community
  • Support Forums
  • Blogs
  • Groups
  • Videos
  • 简体中文
  • More ...
TI Home » TI E2E Community » Support Forums » Embedded Software » Multimedia Software Codecs » Multimedia Software Codecs forum » All Tags » XDM
Share
Multimedia Software Codecs
  • Forum

Browse by Tags

Multimedia Software Codecs

Welcome to the Multimedia Software Codecs Section of the TI E2E Support Community. Ask questions, share knowledge, explore ideas, and help solve problems with fellow engineers. To post a question, click on the forum tab then "New Post".

Sign In to Post
Tags
You have subscribed to this tag. To view or manage your tag subscriptions, click here.   Close
You have unsubscribed from this tag. To view or manage your tag subscriptions, click here.   Close
You are currently viewing:
XDM
  • 6467
  • 720p
  • audio
  • C64x
  • C6747
  • C6748
  • CCSv5
  • Codec
  • Codec Engine
  • codec server
  • codecs
  • DaVinci
  • Davinci 6467
  • decode
  • DM365
  • DM368
  • DM6446
  • dvsdk
  • G.711 codec
  • h264
  • H264 Decoder
  • h264enc
  • RTSC
  • volib
  • xdais
Related Posts
  • Forum Post: Re: IUNIVERSAL_Status

    Chris Ring Chris Ring
    A bit of background may be needed, and the docs can definitely be cleaned up. In general, the *_Status structs (in all XDM interfaces, including IUNIVERSAL) are algorithm 'output' from a control() call. The mention of 'read only' in the doc is from the caller/app POV - the intent is...
    on Mar 12, 2010
  • Forum Post: Testing h264Dec rev.2.00

    Ja Maitan Ja Maitan
    We are in the process of testing the h264dec rev.2.00. To run the test we need to build a test app that can display a video clip downloaded into dm6437 eval board. I am using CCS 3.3. As a test template, I used testAppDecoder.pjt which comes with h264dec distro (on my computer it is in "D:\dvsdk_2_00...
    on May 10, 2010
  • Forum Post: algFree doesn't be invoked

    jialin fan jialin fan
    hi, these days I was implementing a new codec on dm6446, and then I used xdm to encapsulate this codec, later I added it into the decodeCombo.x64P, meanwhile I use decode demo to test the new decodeCombo.x64P. when I was using the xdm to encapsulate the codec, I realized these functions: #pragma CODE_SECTION...
    on May 31, 2010
  • Forum Post: Re: Specific H264 codec parameters (how to set?)

    Chris Ring Chris Ring
    There is an article with some details on extending XDM structs (and fields). Typically, you'll #include the codec-provided ih264venc.h file to get the codec-specific definitions, then you can use those definitions when initializing the XDM fields. Chris
    on Aug 9, 2010
  • Forum Post: How to build the *.l64 to pass QualiTI checking?

    JuliannH JuliannH
    Hi there, I'm trying to make a speech codec XDM-compliant to pass the QualiTI checking. When I use CCSv3.3 to build the input of QualiTI (say, **.l64), CCS has problems to locate some certain header files like: #include <ti/xdais/dm/isphdec1.h> #include <xdm.h> .... I probably can...
    on Sep 14, 2010
  • Forum Post: Re: Need Clarification on XDM :: Data Structures

    Chris Ring Chris Ring
    So long as you assign params.size = sizeof(IVIDDEC1_Params), it doesn't matter whether the struct you allocate in your app is "really" sizeof(IVIDDEC3_Params) big or sizeof(IMP2DEC_Params) big. The codec won't know. As a recommendation though, if your test app _really_ only want...
    on Oct 25, 2010
  • Forum Post: Need Clarification on XDM :: Data Structures

    CRN PRASANNA CRN PRASANNA
    Hi, I am working in Video Codec testing & as of now i am doing a test procedure which is now being doubted by my colleagues. Normally we used to run codec with Base class params mode or with Extended class variables (if codec supports) My Way of test Procedure for Basic Param from my understanding...
    on Oct 25, 2010
  • Forum Post: Re: DM365 MPEG4 encode noise at inputWidth>=160

    Chris Ring Chris Ring
    By design, the codec is supposed to indicate whether the encoded output buffer was filled by the codec using the CPU - my understanding is that the codec indicates this via the IVIDENC1_OutArgs.encodedBuf.accessMask field. If that field has the XDM_ACCESSMODE_WRITE bit set, the codec wrote into that...
    on Mar 2, 2011
  • Forum Post: Re: VoLIB/Codec Server Integration

    Dennis E Dennis E
    Thanks for the reply, Our purpose for looking at this library is to process the audio to detect the presence or absence of speech. 8kHz is probably fine. I know the VAU component supports XDAIS. Does it make more sense to try to export this component directly by our codec server or to write a "wrapper...
    on Jun 21, 2011
  • Forum Post: VoLIB/Codec Server Integration

    Dennis E Dennis E
    We have a need to integrate algorithms from the VoLIB into our existing codec server (for the OMAP3530/C64+). Our server currently contains a number of audio & video encoders and decoders, as well as a custom video processing algorithm we wrote in-house that uses DSPLIB 2.1, IMGLIB 2.01, and VLIB...
    on Jun 20, 2011
  • Forum Post: First calling UNIVERSAL_control() fails

    Peter Ladanyi Peter Ladanyi
    Hello, I would like to develop a codec using IUNIVERSAL interface (DM6446) and I have a problem. I made an empty project using ti.xdais.wizards.genalg wizard. The codec and the codec server built successfully (I think but I am not sure: I am new in Codec Engine/XDAIS/xDM development...
    on Aug 18, 2011
  • Forum Post: create video decoder error on dm6467t

    liang yun liang yun
    Hi, In my program, The Vdec2_create() and Venc1_create() would be called twice respectively,When i called Vdec2_create() at the second time , sometimes it didn't return.it stop at VIDDEC_control(,XDM_SETPARAMS,...), why? with evm:dm6467t dvsdk:3.10_00_19 codec engine:2.25.05.16 ...
    on Oct 24, 2011
  • Forum Post: Re: how to implement extra function (for example, process and control) for writting warppers around g729 codec.

    Chris Ring Chris Ring
    If you're using Codec Engine you use the APIs appropriate for the XDM class. For example, if your codec implements ISPHENC1, you'll use Codec Engine's SPHENC1 APIs . If you're not using Codec Engine but rather just invoking the codec directly, you'll have to call the fxns through...
    on Dec 2, 2011
  • Forum Post: DM365 H.264 encoder 2.10.00.06 codec-specific error flags

    Frank Talbot Frank Talbot
    Hi, We're testing an in house encoder application that uses TI's H.264 Platinum encoder (v. 2.10.00.06) on a DM365 eval board. The example application that comes bundled with the encoder works, so I know the right pieces are in place in Linux. When we try to run our encoder application...
    on Apr 6, 2012
  • Forum Post: RE: Unable to build project using c64x+ G.711 encoder library under CCSv5

    Joseph Zolyak Joseph Zolyak
    According to the following TI wiki page: http://processors.wiki.ti.com/index.php?title=RTSC_Codec_And_Server_Package_Wizards there should be some sort of RTSC Codec Package Wizard that was used to create the packages found in c64xplus_g711_2_00_000_production. Likewise there should be some sort of...
    on Jul 20, 2012
  • Forum Post: RE: Unable to build project using c64x+ G.711 encoder library under CCSv5

    Joseph Zolyak Joseph Zolyak
    Hello Janet, You still haven't answered my question. I have already been two both wiki pages, and neither page provides enough information on how to "consume" a package. Likewise, on the Codec Engine wiki it says: "If you intend your algorithm to be consumed by Codec Engine,...
    on Jul 20, 2012
  • Forum Post: RE: Unable to build project using c64x+ G.711 encoder library under CCSv5

    Joseph Zolyak Joseph Zolyak
    Hello, I followed a footnote from your posted wiki page which led me to: http://rtsc.eclipse.org/docs-tip/RTSC_Packaging_Primer/Lesson_0 This filled in one of the missing pieces to this puzzle. According to this primer, the producer of an RTSC package is responsible for providing 3 files: package...
    on Jul 24, 2012
  • Forum Post: RE: Unable to build project using c64x+ G.711 encoder library under CCSv5

    Joseph Zolyak Joseph Zolyak
    Hello, Why do we want to create a vanilla Empty Project with a dummy main.c and not an Empty RTSC project? I created another new Empty Project as you suggested and called it "g711aenc2". I followed your instructions and created an "alg.h" header file and placed it in the same...
    on Jul 24, 2012
  • Forum Post: RE: Unable to build project using c64x+ G.711 encoder library under CCSv5

    Joseph Zolyak Joseph Zolyak
    Hello, Yes, I have g711aenc_tii_elf.I64P in the same directory in the project as g711Encodermain.c, and yes I have changed the output format to eabi (ELF). Upon closer examination of the warning messages, the alg_create.c file is not seeing a header file for "_ALG_allocMemory(memTab, n)"...
    on Jul 25, 2012
  • Forum Post: RE: Unable to build project using c64x+ G.711 encoder library under CCSv5

    Joseph Zolyak Joseph Zolyak
    Hello, I haven't seen the first five compilation errors that you listed in your posting. I believe that they were caused by difference in our tool chain paths, which in turn affect our respective include paths, i.e. "${CG_TOOL_ROOT}/include" "C:/ti/xdctools_3_22_03_41/packages"...
    on Jul 25, 2012
  • Forum Post: RE: Unable to build project using c64x+ G.711 encoder library under CCSv5

    Joseph Zolyak Joseph Zolyak
    Hello, If I don't use the "_alg.h" obtained from somewhere else, then we to create one to resolve the problem with the missing _ALG_allocMemory() and _ALG_freeMemory() functions . The following are the error and warning messages that I am still seeing: Description Resource Path...
    on Jul 25, 2012
  • Forum Post: RE: Unable to build project using c64x+ G.711 encoder library under CCSv5

    Joseph Zolyak Joseph Zolyak
    Hello, After adding the file search path to the project to locate g711aenc_tii_elf.l64P, it resolved the missing symbol G711AENC_TII_IG711AENC. There are no further errors preventing g711aenc3.out from being produced, but there still are 23 warning message that I reported earlier. I would like to...
    on Jul 26, 2012
TI E2E™ Community
  • Support Forums
  • Blogs
  • Videos
  • Groups
  • Site Support & Feedback
  • Settings
TI E2E™ Community Groups
  • TI University Program
  • Make the Switch
  • Microcontroller Projects
  • Motor Drive & Control
Other Communities
  • Deyisupport
  • Designsomething.org
  • beagleboard.org
  • TI on Element 14
  • TI on TechXchangeSM
Other Technical & Support Resources
  • WEBENCH® Design Center
  • Product Information Centers
  • Technical Documents
  • TI Design Network
  • TI Technical Articles
  • TI Training

All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with respect to these materials. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.

Content on this site may contain or be subject to specific guidelines or limitations on use. All postings and use of the content on this site are subject to the Terms of Use of the site; third parties using this content agree to abide by any limitations or guidelines and to comply with the Terms of Use of this site. TI, its suppliers and providers of content reserve the right to make corrections, deletions, modifications, enhancements, improvements and other changes to the content and materials, its products, programs and services at any time or to move or discontinue any content, products, programs, or services without notice.

Follow Us Texas Instruments on Facebook Texas Instruments on Twitter Texas Instruments on LinkedIn Texas Instruments on Google+
TI Worldwide | Contact Us | my.TI Login | Site Map | Corporate Citizenship | mobile m.ti.com (Mobile Version)

TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs and
embedded processors, along with software, tools and the industry’s largest sales/support staff.

© Copyright 1995-2013 Texas Instruments Incorporated. All rights reserved.
Trademarks | Privacy Policy | Terms of Use