• 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 » Venc1_create() fails with errorcode -1 (unspecified error)
Share
Multimedia Software Codecs
  • Forum
Options
  • Subscribe via RSS

Forums

Venc1_create() fails with errorcode -1 (unspecified error)

This question is answered
Andreas Nagel
Posted by Andreas Nagel
on Aug 02 2012 17:13 PM
Prodigy200 points

Hello,

I am trying to create a video encoder program by using the DMAI functions. I already created a working AAC decoder program, so I am familiar with the API quite a bit. The current code of the encoder fails during this call:

hEnc = Venc1_create(hEngine, "h264enc", &params, &dynParams);

Engine_open() works and hEngine is not NULL. The parameter structures have PAL D1 as maximum video resolution. param.size is set to sizeof(VIDENC1_Params). So I ran the program with CE_DEBUG=2. The output says, that XDM_SETPARAMS failed with status code -1, which boils down to the extremely helpful "unspecified error". Obviously, the failure occurs at the VIDENC_control() function, which is called by Venc1_create().

Does somone know, where the problem might be? Appended below is the debug information.

Best regards,
Andreas

-

**** Debug info ****

@0,226,749us: [+2 T:0x4001e340] ti.sdo.dmai - [Venc1] Creating encoder h264enc for max 720x576 bitrate 6000000 ratectrl 1
@0,226,841us: [+0 T:0x4001e340] ti.sdo.ce.video1.VIDENC1 - VIDENC1_create> Enter (engine=0x57508, name='h264enc', params=0xbeafdc4c)
@0,226,932us: [+0 T:0x4001e340] CV - VISA_create(0x57508, 'h264enc', 0xbeafdc4c, 0x520, 'ti.sdo.ce.video1.IVIDENC1')
@0,226,993us: [+0 T:0x4001e340] CV - VISA_create2(0x57508, 'h264enc', 0xbeafdc4c, 0x30, 0x520, 'ti.sdo.ce.video1.IVIDENC1')
@0,227,085us: [+0 T:0x4001e340] CE - Engine_createNode(0x57508, 'h264enc', 520, 0xbeafdc4c, 0x30, 0xbeafda70)
@0,227,146us: [+0 T:0x4001e340] CE - Engine> allocNode Enter(engine=0x57508, impId='h264enc')
@0,227,237us: [+0 T:0x4001e340] CE - Engine> allocNode(). Calling (Comm_create(gppfromnode_1041_1, 0x57af0, NULL)
@0,248,294us: [+4 T:0x4001e340] CE - Engine_createNode> created node(stdIn=0x2, stdOut=0x10001, msgq=0x57b10, algName='h264enc', rmsNode=0x87f11e08, algHandle=0x87f11ef8)
[DSP] @0,045,518tk: [+0 T:0x87f0d334] OM - Memory_alloc> Enter(size=0x18)
[DSP] @0,045,567tk: [+0 T:0x87f0d334] OM - Memory_alloc> return (0x87f11e08)
[DSP] @0,045,610tk: [+0 T:0x87f0d334] OM - Memory_alloc> Enter(size=0xa)
[DSP] @0,045,647tk: [+0 T:0x87f0d334] OM - Memory_alloc> return (0x87f11e20)
[DSP] @0,045,693tk: [+0 T:0x87f0d334] OM - Memory_alloc> Enter(size=0x20)
[DSP] @0,045,731tk: [+0 T:0x87f0d334] OM - Memory_alloc> return (0x87f11e30)
[DSP] @0,045,773tk: [+0 T:0x87f0d334] OM - Memory_alloc> Enter(size=0x24)
[DSP] @0,045,811tk: [+0 T:0x87f0d334] OM - Memory_alloc> return (0x87f11e50)
[DSP] @0,045,878tk: [+0 T:0x87f0d334] ti.sdo.ce.video1.VIDENC1 - VIDENC1_create> Enter (engine=0x0, name='h264enc', params=0x873048c0)
[DSP] @0,045,948tk: [+0 T:0x87f0d334] CV - VISA_create(0x0, 'h264enc', 0x873048c0, 0x520, 'ti.sdo.ce.video1.IVIDENC1')
[DSP] @0,046,010tk: [+0 T:0x87f0d334] CV - VISA_create2(0x0, 'h264enc', 0x873048c0, 0x30, 0x520, 'ti.sdo.ce.video1.IVIDENC1')
[DSP] @0,046,084tk: [+0 T:0x87f0d334] CE - Engine_open> Enter('local', 0x87f1100c, 0x873048c0)
[DSP] @0,046,136tk: [+0 T:0x87f0d334] OM - Memory_alloc> Enter(size=0x34)
[DSP] @0,046,174tk: [+0 T:0x87f0d334] OM - Memory_alloc> return (0x87f11ec0)
[DSP] @0,046,236tk: [+4 T:0x87f0d334] CE - Engine_open> engine->server = 0x0
[DSP] @0,046,276tk: [+0 T:0x87f0d334] CE - Engine_open> return(-2014241088)
[DSP] @0,046,335tk: [+0 T:0x87f0d334] OM - Memory_alloc> Enter(size=0x34)
[DSP] @0,046,372tk: [+0 T:0x87f0d334] OM - Memory_alloc> return (0x87f11ef8)
[DSP] @0,046,416tk: [+0 T:0x87f0d334] ti.sdo.ce.alg.Algorithm - Algorithm_create> Enter(fxns=0x87f8e8b8, idma3Fxns=0x87f8e8e4, iresFxns=0x0, params=0x873048c0, attrs=0x87f11128)
[DSP] @0,046,504tk: [+0 T:0x87f0d334] OM - Memory_alloc> Enter(size=0x10)
[DSP] @0,046,541tk: [+0 T:0x87f0d334] OM - Memory_alloc> return (0x87f11f30)
[DSP] @0,073,003tk: [+0 T:0x87f0d334] ti.sdo.ce.alg.Algorithm - Algorithm_create> return (0x87f11f30)
[DSP] @0,073,079tk: [+5 T:0x87f0d334] CV - VISA_create> local codec created (name='h264enc', handle=0x87f11f30)
[DSP] @0,073,137tk: [+0 T:0x87f0d334] ti.sdo.ce.video1.VIDENC1 - VIDENC1_create> return (0x87f11ef8)
[DSP] @0,073,229tk: [+4 T:0x87f0d334] OT - Thread_create > name: "h264enc#0", pri:  -1, stack size:  21288, stack seg: 0
@0,252,597us: [+0 T:0x4001e340] CE - Engine_fwriteTrace> returning count [2298]
@0,252,658us: [+2 T:0x4001e340] CE - Engine_createNode> Returning 0x57ae8
@0,252,720us: [+5 T:0x4001e340] CV - VISA_create> remote codec created (name='h264enc', localQueueID=0x10001, remoteQueueID=0x0002)
@0,252,781us: [+0 T:0x4001e340] ti.sdo.ce.video1.VIDENC1 - VIDENC1_create> return (0x57aa0)
@0,252,842us: [+2 T:0x4001e340] ti.sdo.dmai - [Venc1] Setting dynParams size 720x576 bitrate 6000000
@0,252,872us: [+0 T:0x4001e340] ti.sdo.ce.video1.VIDENC1 - VIDENC1_control> Enter (handle=0x57aa0, id=1, dynParams=0xbeafdc1c (size=0x30), status=0xbeafdb38 (size=0x9c)
@0x0003999e:[T:0x4001e340] ti.sdo.dmai - [Dmai] Dmai log level set to '2'. Note that calling CERuntime_init after this point may cause unexpected change to D
@0x0003999e:[T:0x4001e340] ti.sdo.dmai - [Dmai] Dmai log level set to '2'. Note that calling CERuntime_init after this point may cause unexpected change to D
MAI tracing behavior.
@0x000618f1:[T:0x4001e340] ti.sdo.dmai - [Venc1] Creating encoder h264enc for max 720x576 bitrate 6000000 ratectrl 1
@0x00066ec5:[T:0x4001e340] ti.sdo.dmai - [Venc1] Setting dynParams size 720x576 bitrate 6000000
@0x00067535:[T:0x4001e340] ti.sdo.dmai - [Venc1] XDM_SETPARAMS failed, status=-1

Report Abuse
  • Reply
You have posted to a forum that requires a moderator to approve posts before they are publicly available.
All Replies
  • Andreas Nagel
    Posted by Andreas Nagel
    on Aug 03 2012 07:09 AM
    Verified Answer
    Verified by Andreas Nagel
    Prodigy200 points

    Found the problem. When setting the framerate in dynParams, I didn't account for the factor 1000 and set 30 instead of 30000.

    Report Abuse
    • Reply
    You have posted to a forum that requires a moderator to approve posts before they are publicly available.
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