Latest post Tue, Jul 22 2014 11:26 PM by Vadym. 7 replies.
Page 1 of 1 (8 items)
Sort Posts: Previous Next
  • Tue, Jul 15 2014 2:49 PM

    • datkins
    • Not Ranked
    • Joined on Tue, Jul 15 2014
    • Posts 14
    • Points 140

    Writing Medoa to Interplay/Isis through AMT

    Hi,

     

    Trying to write media to Isis throught the AMT sdk, I can write to local files successfully usign AMT and the .mxfs and .aaf can be sued in media composer. 

     

    If w try and write to the Isis we get a error code 4 "cannot create video track", the logs do suggest its faling to copy files from my local drive, not sure why this is being done, a snippet of the logs follows.

    Any pointers to resolve this welcome.

    2014-07-15T14:25:45,116UTC [DEBUG] [AMT] [] {P:12608 - T:7224 } [sources\Core\GH_interface.cpp:155] Entering AvAmtGH::AvAmtGH.

    2014-07-15T14:25:45,116UTC [DEBUG] [AMT] [] {P:12608 - T:7224 } [sources\Core\GH_interface.cpp:155] Entering AvAmtGH::AvAmtGH.

    2014-07-15T14:25:45,117UTC [INFO] [AMT] [] {P:12608 - T:7224 } [sources\CORE\AMT_class.cpp:1635] Initializing Amt folder with temporary folder: C:\Users\datkins\AppData\Local\Temp\test2014-07-15-15-13-01test2014-07-15-15-13-01__4094169452

    2014-07-15T14:25:45,131UTC [DEBUG] [AMT] [] {P:12608 - T:7224 } [sources\CORE\AMT_class.cpp:441] AMT configured for pass through video.

    2014-07-15T14:25:45,132UTC [DEBUG] [AMT] [] {P:12608 - T:7224 } [sources\CORE\AMT_class.cpp:454] AMT configured for pass through audio.

    2014-07-15T14:25:45,132UTC [DEBUG] [AMT] [] {P:12608 - T:7224 } [sources\CORE\AMT_class.cpp:480] Initializing AMT codec interface.

    2014-07-15T14:25:45,132UTC [DEBUG] [AMT] [] {P:12608 - T:7224 } [sources\CORE\AMT_class.cpp:1711] Initializing AMT writer interface.

    2014-07-15T14:25:45,132UTC [DEBUG] [AMT] [] {P:12608 - T:7224 } [sources\Core\GH_interface.cpp:2078] Parsing input XML document.

    2014-07-15T14:25:45,132UTC [DEBUG] [AMT] [] {P:12608 - T:7224 } [sources\Core\GH_interface.cpp:2110] timecode: 09:59:30:00

    2014-07-15T14:25:45,132UTC [DEBUG] [AMT] [] {P:12608 - T:7224 } [sources\Core\GH_interface.cpp:2111] tapeTimecode: 

    2014-07-15T14:25:45,132UTC [DEBUG] [AMT] [] {P:12608 - T:7224 } [sources\Core\GH_interface.cpp:2112] filmTimecode: 

    2014-07-15T14:25:45,132UTC [DEBUG] [AMT] [] {P:12608 - T:7224 } [sources\Core\GH_interface.cpp:2113] soundTimecode: 

    2014-07-15T14:25:45,132UTC [DEBUG] [AMT] [] {P:12608 - T:7224 } [sources\Core\GH_interface.cpp:2314] Timecode generic settings: rate: 25 df:0

    2014-07-15T14:25:45,132UTC [DEBUG] [AMT] [] {P:12608 - T:7224 } [sources\Core\GH_interface.cpp:2029] Creating timecode original_start_tc with startTimeCode: 899250

    2014-07-15T14:25:45,132UTC [DEBUG] [AMT] [] {P:12608 - T:7224 } [sources\Core\GH_interface.cpp:2029] Creating timecode start_t_tc with startTimeCode: 0

    2014-07-15T14:25:45,132UTC [DEBUG] [AMT] [] {P:12608 - T:7224 } [sources\Core\GH_interface.cpp:2336] Creating start_tc equal to original_start_tc.

    2014-07-15T14:25:45,133UTC [DEBUG] [AMT] [] {P:12608 - T:7224 } [sources\Core\GH_interface.cpp:2029] Creating timecode sound_start_tc with startTimeCode: 0

    2014-07-15T14:25:45,133UTC [DEBUG] [AMT] [] {P:12608 - T:7224 } [sources\Core\GH_interface.cpp:2988] Creating AG::Filelist with timecode: 9:59:30:0

    2014-07-15T14:25:45,133UTC [DEBUG] [AMT] [] {P:12608 - T:7224 } [sources\Core\GH_interface.cpp:3166] Read back AG::Timecode from AG::FileList with : 9:59:30:0

    2014-07-15T14:25:45,134UTC [DEBUG] [AMT] [] {P:12608 - T:7224 } [sources\CORE\AMT.cpp:834] CreateAmtInterplayClip returning: AMT_SUCCESS.

    2014-07-15T14:25:48,000UTC [DEBUG] [AMT] [] {P:12608 - T:7224 } [sources\CORE\AMT.cpp:1282] Calling GetMobIDs.

    2014-07-15T14:25:48,000UTC [DEBUG] [AMT] [] {P:12608 - T:7224 } [sources\Core\GH_interface.cpp:1710] Entering AvAmtGH::GetMobIDs with  and .

    2014-07-15T14:25:48,000UTC [DEBUG] [AMT] [] {P:12608 - T:7224 } [sources\CORE\AMT.cpp:1297] GetMobIDs returning: AMT_SUCCESS.

    2014-07-15T14:27:40,183UTC [DEBUG] [AMT] [] {P:12608 - T:7224 } [sources\CORE\AMT.cpp:1042] Calling CreateAmtTrack with: 0 | 0.

    2014-07-15T14:27:40,184UTC [ERROR] [AMT] [] {P:12608 - T:7224 } [sources\CORE\AMT_class.cpp:2545] Internal error occurred: 8

    2014-07-15T14:27:40,184UTC [DEBUG] [AMT] [] {P:12608 - T:7224 } [sources\Core\GH_interface.cpp:212] Entering AvAmtGH::~AvAmtGH.

    2014-07-15T14:27:40,184UTC [DEBUG] [AMT] [] {P:12608 - T:7224 } [sources\CORE\AMT_class.cpp:1754] Copying AAF and XML files to final destination folder.

    2014-07-15T14:27:40,224UTC [WARN] [AMT] [] {P:12608 - T:7224 } [sources\CORE\AMT_class.cpp:1776] Error copying AAF 'C:\Users\datkins\AppData\Local\Temp\test2014-07-15-15-13-01test2014-07-15-15-13-01__4094169452\test2014-07-15-15-13-01test2014-07-15-15-13-01_.aaf' to final location '\\avidisis\DM_Library\Avid MediaFiles\MXF\SUITCASE\test2014-07-15-15-13-01test2014-07-15-15-13-01_\test2014-07-15-15-13-01test2014-07-15-15-13-01_.aaf': AMT_CODEC_FAILURE.

    2014-07-15T14:27:40,234UTC [ERROR] [AMT] [] {P:12608 - T:7224 } [sources\CORE\AMT.cpp:1060] CreateAmtTrack returning error: AMT_COULD_NOT_CREATE_TRACK. Closed Amt File.

    2014-07-15T14:27:40,234UTC [DEBUG] [AMT] [] {P:12608 - T:7224 } [sources\CORE\AMT.cpp:1063] CreateAmtTrack returning: AMT_COULD_NOT_CREATE_TRACK.

    David
  • Tue, Jul 15 2014 4:19 PM In reply to

    • Vadym
    • Top 500 Contributor
    • Joined on Thu, Apr 17 2014
    • Posts 262
    • Points 3,110
    • ! Avid Employee
      Avid Developer Moderator

    Re: Writing Medoa to Interplay/Isis through AMT

    Hi David,

    From the log it looks like you're writing aaf to the PAM indexed location which should never happen.

    To ingest file into PAM you'd need to create AMT clip locally and point essense output to an ISIS temp folder. Once finished you'd move essense to the target folder and check-in AAF through WebServices or import it manually.

    You can use AMT to check-in AAF into PAM or even do a Frame Chase ingest if required.

    Please refer to AMT function reference for additional PAM related functionality.

    Thanks,

    Vadym

  • Tue, Jul 15 2014 5:47 PM In reply to

    • datkins
    • Not Ranked
    • Joined on Tue, Jul 15 2014
    • Posts 14
    • Points 140

    Re: Writing Medoa to Interplay/Isis through AMT

    Hi,

     

    So create Interplay clip does not allow writign of media to Isis? I find 3 methods referenced

     

    1) CreateAmtFile, allows creation of media anywhere we can write to

    2) CreateAmtFileOnSharedStorage, writes to shared storage, I assuem thsi whats we need to use to cretae media that can used while we are creating

    3) CreateAmtInterplayClip which writes to files agai, documentatiuon says CreateAmtInterplayClip creates a new Interplay media clip for write. Essence files may be stored on shared storage.

    I'm confused as to what we shoudl be doing, is it option 1,2 or 3, and if not 3, whats does it do? How do we allow users to see whats been written while we are still ingesting?

     

    DAvid

  • Tue, Jul 15 2014 6:09 PM In reply to

    • datkins
    • Not Ranked
    • Joined on Tue, Jul 15 2014
    • Posts 14
    • Points 140

    Re: Writing Medoa to Interplay/Isis through AMT

    Sorry, another quick query which I think is an erro in the AMT docs, for int ImportIntoInterplay() it states

     

    interplay_uri specifies the asset that is to be retrieved in the form of an Interplay Folder by Path, e.g. interplay://WGA/Projects/Test Project/Test Project Bin

     

    I assume this means exports not retrieves.

     

    David

     

     

     

  • Tue, Jul 15 2014 7:45 PM In reply to

    • datkins
    • Not Ranked
    • Joined on Tue, Jul 15 2014
    • Posts 14
    • Points 140

    Re: Writing Medoa to Interplay/Isis through AMT

    Hi,

     

    Now wrting media to a local file and then doing ImportIntoInterplay, now getting 

     

    2014-07-15T19:35:01,211UTC [DEBUG] [AMT] [] {P:15792 - T:12136 } [sources\CORE\AMT.cpp:487] ImportIntoInterplay returning: AMT_COULD_NOT_CHECK_IN_AAF.

     

    this is error code 59, 

     

    the media files are are in Isis folder so the data tranbsfer is working.

    my formatting is as follows, have replaced usernames and passwords, 

     

    Status = ::ImportIntoInterplay( &Session, sourceClip, "interplay://Username:password@ip-address:80",

          "interplay://AvidWG/Catalogs/FromIngest", "username", "password",

          "\\\\avidisis\\DM_Library\\Avid MediaFiles\\MXF\\NODE11.1\\" );

     

    Status on returns which takes some time and we can see the media copying over is 59.

     

    Ideas? have I formatted one fo the URL/URI's 

     

    David

     

  • Mon, Jul 21 2014 9:31 PM In reply to

    • Vadym
    • Top 500 Contributor
    • Joined on Thu, Apr 17 2014
    • Posts 262
    • Points 3,110
    • ! Avid Employee
      Avid Developer Moderator

    Re: Writing Medoa to Interplay/Isis through AMT

    Hi David,

    There are various ways to get AMT clip imported into Interplay. If this is your goal then you may decide which fits your needs most. If you have a completed AMT clip then ImportIntoInterplay may be the best option. If you transcode another media then you may use CreateAmtInterplayClip to transfer it to Interplay on the fly.

    In any case you'd need a valid and configured Interplay WebServices instance running with known credentials to check-in metadata.

    AMT clip contains both metadata (aaf) and essense (mxf) files where essense may be put directly into Interplay indexed folder, but metadata should be stored either on local drive or in a separate non-indexed folder on ISIS.

    Please refer to the whitepaper for AMT overview available at http://www.avid.com/us/partners/AvidMediaToolkitProgram and let me know if this explains your questions.

    Thanks,

    Vadym

  • Tue, Jul 22 2014 6:22 AM In reply to

    • datkins
    • Not Ranked
    • Joined on Tue, Jul 15 2014
    • Posts 14
    • Points 140

    Re: Writing Medoa to Interplay/Isis through AMT

    Hi,

     

    CreateAmtInterplayClip was what we expected to use, but an earlier resposne on this thread suiggested we should not, the issue we had with Interplay Web Services has been addressed, (it had not been installed....) 

     

    I'n not clear from your message and the docuementation how we write metadata to a local file, which parameter in the call determines where metedata is written?

     

    int CreateAmtInterplayClip(  amtSession_t* amtSession,

                                            const char* local_amt_specification,   Is this needed of stored on Isis

                                            const char* media_properties,

                                            const char* external_media_properties,  Not sure why ReadAmtTrackSample is reference in the AMT documentation here

                                            const char* masterMobID,

                                            const char* sourceMobID,

                                            const char* interplay_web_services_endpoint,

                                           const char* interplay_uri,

                                           const char* interplay_user_name,

                                           const char* interplay_password,

                                           const char* interplay_shared_storage_folder,   Is this the machines folder on ISIS

                                           const char* update_aaf_after_x_frames_written   Is this a byte value or or ASCIIZ? );

     

    Your updates on this looked forward to keenly!

     

    David

  • Tue, Jul 22 2014 11:26 PM In reply to

    • Vadym
    • Top 500 Contributor
    • Joined on Thu, Apr 17 2014
    • Posts 262
    • Points 3,110
    • ! Avid Employee
      Avid Developer Moderator

    Re: Writing Medoa to Interplay/Isis through AMT

    Hi David,

    There should be AMT_Function_Reference_Guide.pdf in the AMT SDK package provided.

    For the CreateAmtInterplayClip

    local_amt_specification defines the folder/archive with metadata files to be written to, should be local

    interplay_shared_storage_folder defines the UNC path of the workspace location to which the media files should be written. Should not exceed 220 characters.

    external_media_properties contains char array pointer to define format for the ReadAmtTrackSample function

    update_aaf_after_x_frames_written is a pointer to char array representing integer number

     

    Thanks,

    Vadym

Page 1 of 1 (8 items)

© Copyright 2011 Avid Technology, Inc.  Terms of Use |  Privacy Policy |  Site Map |  Find a Reseller