none
I'm using Azure Media Services Explorer to process a video with Hyperlapse, but the jobs all produce zero-byte outputs RRS feed

  • Question

  • All the operations are in the "Azure Media Services Explorer" GUI. Permission is granted to access any of the listed assets/Ids for the purpose of diagnosing the problem.

    An  example job:

    ==============================================================================

     START OF JOB REPORT
    ==============================================================================

    Job Name            : Hyperlapse processing of Kayaking.mp4
    Job ID              : nb:jid:UUID:6e45a55d-1500-8605-7f71-f1e8cc3be2d1
    Job State           : Finished
    Job Priority        : 10
    Job Template Id     : 
    Job Created (UTC)   : Wednesday, October 10, 2018 03:23:43
    Job StartTime (UTC) : Wednesday, October 10, 2018 03:24:49
    Job EndTime (UTC)   : Wednesday, October 10, 2018 03:42:54
    Job CPU runtime     : 00:00:17:51.75
    Job Duration        : 00:00:18:05.22
    Number of tasks     : 1
    Media Account       : jratt0media

    ==============================================================================
    Task Name           : Hyperlapse processing of Kayaking.mp4
    ==============================================================================

    Task ID             : nb:tid:UUID:6e45a55d-1500-8605-7f72-f1e8cc3be2d1
    Task Priority       : 10
    Task State          : Finished
    Task Options        : DoNotDeleteOutputAssetOnFailure, DoNotCancelOnJobFailure
    Media Processor     : nb:mpid:UUID:db657ff0-fc6e-407c-a03a-80fdca3b81cd
    Media Processor Name: Azure Media Hyperlapse
    Task StartTime (UTC): Wednesday, October 10, 2018 03:24:49
    Task EndTime (UTC)  : Wednesday, October 10, 2018 03:42:54
    Task CPU runtime    : 00:00:17:51.75
    Task Duration       : 00:00:18:05.22
    Task PerfMessage    : Mediatask af508eeb-79de-4bda-91ae-0d285bf30426: Download: 00:00:26.0257757
    Encode af508eeb
    Encode Subtask
    CPU Usage : 93.79 %
    Memory Usage : 4628.593 MB
    Disk reads / sec : 11.509
    Disk writes / sec : 3.070
    Disk transfers / sec : 14.582
    Network Utilization / sec : 0.00 %
    Process File Kayaking.mp4 , size is 2786 Mbytes, Hyperlapse processing time is 18
    Upload: 00:00:01.5722112


    Task Progress       : 100
    03:23:43 :-  
    03:24:44 :-  
    03:24:49 :-  
    03:42:54 :-  

    Task Body           : 
    =====================
    <?xml version="1.0" encoding="utf-16"?>
    <taskBody>
      <inputAsset>JobInputAsset(0)</inputAsset>
      <outputAsset assetCreationOptions="0" assetFormatOption="0" assetName="kayaking 2018-10-09 HYPER v02 1x 11340fr" storageAccountName="jratt0storage">JobOutputAsset(0)</outputAsset>
    </taskBody>

    Task Configuration  : 
    =====================
    (Not displayed here as task configuration is protected. This data is visible in Job Information / Tasks)

    Input Assets        :
    =====================

    ===============================================
    Asset Name          : Kayaking.mp4
    Asset Id            : nb:cid:UUID:1d6430ed-74fd-4741-8005-74ec64d19a33
    Last Modified (UTC) : 2018-09-11 02:43:41

       ------------(-P-R-I-M-A-R-Y-)------------------
       File Name           : Kayaking.mp4
       Size                : 2922372098 Bytes
       Last Modified (UTC) : 2018-09-11 03:49:02


    Output Assets       :
    =====================

    ===============================================
    Asset Name          : kayaking 2018-10-09 HYPER v02 1x 11340fr
    Asset Id            : nb:cid:UUID:b83d2a31-5558-415a-8fe9-dcb7c278cb02
    Last Modified (UTC) : 2018-10-10 03:23:43

       ------------(-P-R-I-M-A-R-Y-)------------------
       File Name           : Kayaking_1.00.mp4
       Size                : 0 Bytes
       Last Modified (UTC) : 2018-10-10 03:42:52



    ==============================================================================

    Input size processed by the job  : 2.7 GB
    Output size processed by the job : 0 B
    Total size processed by the job  : 2.7 GB

    ==============================================================================
     END OF JOB REPORT
    ==============================================================================

    Wednesday, October 10, 2018 4:04 AM

Answers

  • As a fellow sea-kayaker, I'm familiar with that use case scenario!  I would actually not recommend the Hyperlapse processor for this scenario.  

    Personally, i prefer the quality of a nice 3-Axis gimbal, with a mount. Like the Evo or other cheap ones on Amazon.com.  

    To that effect, the Hero-7 does a much better job in camera now with the Hypersmooth tech that leverages more of the camera's on board sensing capabilities that we don't have access to in the Hyperlapse layer. 

    Hyperlapse Pro desktop actually does a better job, as it leverages the GPUs on your machines to provide a better calculation of the path.  To date, that team has not updated the algorithm any further, and we are not getting further updates from them either. 

    We will soon deprecate the "preview" Hyperlapse processor due to the factors that I mention above. 

    • Marked as answer by jratt0 Wednesday, October 10, 2018 10:39 PM
    Wednesday, October 10, 2018 8:03 PM

All replies

  • Thanks, I'll have someone reply to the thread with an investigation. 


    Can you explain which use case you are interested in with Hyperlapse?  Are you looking for just "time compression" or are you also looking for image stabilization? 

    Wednesday, October 10, 2018 4:01 PM
  • In this case, I'm primarily interested in stabilization and spatial smoothing of the track. The video was shot from a kayak using the GoPro Hero5 "timelapse video" feature, with a 2-Hz frame-rate.

    I had great luck running the video through the Hyperlapse Pro desktop software, but that doesn't appear to be frequently updated. I was hoping that the newer Azure code would be a long-term replacement.

    I did also try to use the "Azure Media Stabilizer". It consistently produces a failing job error code. For example:

    ID  nb:jid:UUID:6e45a55d-1500-8605-a253-f1e8cc3af27f
    NAME  Azure Media Stabilizer processing of Kayaking.mp4
    TIME SUBMITTED  Tue, Oct 9, 2018, 20:17 PDT
    TIME STARTED  Tue, Oct 9, 2018, 20:24 PDT
    TIME COMPLETED  Tue, Oct 9, 2018, 21:21 PDT
    PRIORITY 10
    Job Tasks
    STATE
    ID
    PROGRESS
    Error
    nb:tid:UUID:6e45a55d-1500-8605-a254-f1e8cc3af27f
    60%
    Task Errors
    ERROR CODE
    ERROR MESSAGE
    ErrorProcessingTask
    An error has occurred. Stage: ApplyIntelligenceCommand. Code: 0x80940001.
    Output Assets
    NAME
    ID
    kayaking 2018-10-09 AMS v01
    nb:cid:UUID:0df40060-003d-4cc6-a8da-0b35974f3f92

    Wednesday, October 10, 2018 5:09 PM
  • As a fellow sea-kayaker, I'm familiar with that use case scenario!  I would actually not recommend the Hyperlapse processor for this scenario.  

    Personally, i prefer the quality of a nice 3-Axis gimbal, with a mount. Like the Evo or other cheap ones on Amazon.com.  

    To that effect, the Hero-7 does a much better job in camera now with the Hypersmooth tech that leverages more of the camera's on board sensing capabilities that we don't have access to in the Hyperlapse layer. 

    Hyperlapse Pro desktop actually does a better job, as it leverages the GPUs on your machines to provide a better calculation of the path.  To date, that team has not updated the algorithm any further, and we are not getting further updates from them either. 

    We will soon deprecate the "preview" Hyperlapse processor due to the factors that I mention above. 

    • Marked as answer by jratt0 Wednesday, October 10, 2018 10:39 PM
    Wednesday, October 10, 2018 8:03 PM
  • Ok, thanks for letting me know!
    Wednesday, October 10, 2018 10:39 PM