Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Ian Downard
    @ianwow
    Yes.
    Oliver Nordemann
    @olivernordemann

    Hello, i want to use the MIE API to execute a workflow with a video which is in S3 and I get a 500. How should the media object be specified?

    I use the following Code:
    headers = {"Content-Type": "application/json", "Authorization": IdToken}
    response = http.request('POST', workflow_api_endpoint+'workflow/execution', body=data.encode('utf-8'), headers=headers)
    json.loads(response.data.decode('utf-8'))

    {'Code': 'ChaliceViewError',
    'Message': "ChaliceViewError: Exception ''S3Bucket''"}

    {
    ...,
    "Input":
    {"Media":
    {"Video":
    {"S3Bucket": "mie-dataplane-1yk436e309xh",
    "S3Key":"Man_weiß_et_nich-TV_total_Nippel.mp4"}
    }
    }
    }

    1 reply
    Marc Rudkowski
    @marcrd
    Is there a way to make sure the operators when referencing their path via S3 doesn't actually move the video, but just copies it?
    1 reply
    leochan2009
    @leochan2009
    Hi, everyone, i was following the instruction on the website: https://github.com/awslabs/aws-media-insights-engine/blob/master/IMPLEMENTATION_GUIDE.md
    and tried to deploy my own stack. the stacks were created successfully, however, the access to the webapp url is denied. When i look into the S3 bucket of the webapplication, there is no index.html file inside. The access deny was logged in the S3 bucket when i try to access the webapplication
    9 replies
    leochan2009
    @leochan2009
    Hi Ian,
    Another questions i have is that if the media insight engine supports user interaction with video data. for example, tagging individual frame and save the tagging information in S3? the sagemaker ground truth service is able to do this kind of task. however, the UI is kind of primitive in sagemaker and i would like to design a labeling tool using media insights engine. Thanks in advance
    3 replies
    leochan2009
    @leochan2009

    In the https://github.com/awslabs/aws-media-insights-engine/blob/master/IMPLEMENTATION_GUIDE.md
    Obtain a Cognito Token
    First define the following environment variables. MIE_USERNAME and MIE_PASSWORD should have been emailed to the email address you specified when you deployed the stack. MIE_DEVELOPMENT_HOME should be the path to your aws-media-insights-engine/ development environment, such as /Users/myuser/development/aws-media-insights-engine/.

    The MIE_DEVELOPMENT_HOME should be set to "/Users/myuser/development/aws-media-insights-engine/source" instead

    jimmalone
    @jimmalone
    Hello, I deployed the MIE app to AWS successfully but unable to upload any audio files (wav, mp3). When dragging/dropping audio files in Upload page, I get an error "Unsupported file type: audio/wav". Per the github readme "The Media Insights sample application lets you upload videos, images, audio and text files for content analysis", i should be able to upload audio only file, no?
    2 replies
    Marc Rudkowski
    @marcrd
    Is there a way to skip the stage Execute Polly (defaultTextSynthesisStage)
    1 reply
    I tried this: "defaultTextSynthesisStage":{"Polly":{"Enabled":false}} with no avail
    Ian Downard
    @ianwow
    Media Insights Engine version 1.0.0 was released today. This release improves the developer experience with a simplified MIE code base, easier installations, and support for AWS_IAM.
    The reference front-end application for MIE was also release today, here.
    Ian Downard
    @ianwow

    We’ve developed a new application for transcribing and translating videos, using MIE. This new app enables users to control the tunable parameters in Transcribe and Translate. If you'd like to learn more about this application, register for the following webinar:

    Oct 29, 2020 10:00 AM - 11:30 AM PDT, "Session 1: “Artificial” AI: Improving Subtitles with Human in-the-Loop Review".

    Ian Downard
    @ianwow
    v1.0.2 of the AWS Content Analysis solution was released today. It includes support for mxf video formats and a handfull of important bug fixes.
    Landing page:
    https://aws.amazon.com/solutions/implementations/aws-content-analysis/
    Documentation:
    https://docs.aws.amazon.com/solutions/latest/aws-content-analysis/
    Source Code:
    https://github.com/awslabs/aws-content-analysise
    Changelog:
    https://github.com/awslabs/aws-content-analysis/blob/main/CHANGELOG.md
    Ian Downard
    @ianwow
    MIE 2.0.0 was released today. https://github.com/awslabs/aws-media-insights-engine/releases/tag/v2.0.0
    Notable new features:
    1. support for multiple deployments in one region
    2. debug tracing via AWS X-Ray
    3. standardized test scripts for unit, integration, and end to end tests. See, https://github.com/awslabs/aws-media-insights-engine/blob/master/test/README.md
    Brandon Dold
    @brandold

    MIE 2.0.1 was released today.

    https://github.com/awslabs/aws-media-insights-engine/releases/tag/v2.0.1

    This release introduces the ability to support human in the loop subtitle generation and editing workflows along with new mechanisms for performing automated builds, testing, and releases for faster release cycles. You can find additional details in the release notes.

    Ian Downard
    @ianwow

    MIE 2.0.2 was released today.

    https://github.com/awslabs/aws-media-insights-engine/releases/tag/v2.0.2

    This release includes bug fixes and developer usability improvements, such as:

    • simpler command line usage of the build script with named parameters,
    • MIE / API versions returned via a new API route and as a Cloudformation Output,
    • and tagging of all MIE resources.

    We also have a new Github pages site that contains API reference documentation:

    https://awslabs.github.io/aws-media-insights-engine/

    jimthebuilder
    @jimthebuilder
    Hi. It looks like the Implementation Guide link in the repo is broken.
    Ian Downard
    @ianwow
    @jimthebuilder Thanks! I fixed the broken link.
    jimthebuilder
    @jimthebuilder
    Thank you.
    Code Ninja
    @nikolai-git-house
    Hello @ianwow I am new to MIE. I am a frontend developer and want to implement MIE service to my React web app via Rest API. The thing is I am not familiar with AWS authentication so I can't find way how to set authentication for using /create api which upload video to MIE?
    3 replies
    Ian Downard
    @ianwow
    Luther Hill
    @lutherkhill
    Hi there. Checking to see if anyone is working on a video, photo, and audio asset management tooling using the framework.
    3 replies
    Ian Downard
    @ianwow
    The Media Insights (MI) demo app has been updated to work with MIE v2.0.3. Here is the release: https://github.com/awslabs/aws-media-insights/releases/tag/v2.0.3
    • Includes a new feature for controlling video playback speed
    • Also includes more robust support for deploying multiple MI instances per region
    Luther Hill
    @lutherkhill
    Does the app have the ability to get / display / search by exif meta data from the pictures or videos. I am working on adding an operator for it.
    1 reply
    Luther Hill
    @lutherkhill
    Is anyone working on something similar for pictures
    1 reply
    Ian Downard
    @ianwow
    Ian Downard
    @ianwow
    The Media Insights (MI) demo app was also updated today so it uses MIE v2.0.4: https://github.com/awslabs/aws-media-insights/releases/tag/2.0.4
    Chinmay337
    @Chinmay337
    Hello AWS Folks! We are working on a customization implementation on top of the Media Insights Repo (https://github.com/awslabs/aws-media-insights)
    We ran into an issue when trying to upload .MXF format video files. The upload is Successful when we 'Start Workflow' but the uploaded video file does not show up under 'Collections'. We tested the upload functionality for .MP4 and .MOV files and it worked fine and showed up under 'Collections'.
    We had some questions- is there a bucket policy or a Lambda policy that prevents .MXF files from proceeding in the flow? Any help would be highly appreciated, thank you!
    2 replies
    Chinmay337
    @Chinmay337
    Good Afternoon! We had some questions regarding the implementation and an issue we were facing. After troubleshooting through Developer tools when trying to upload files greater than 1 GB, we were seeing a CORS 'No-Access-Control-Origin-Allow' header error in the console. We checked the API Gateway function for 'workflowAPI' and figured that the API gateway resource did not have CORS permissions to invoke the parallel upload feature for larger files.
    After enabling CORS for the resources , we were seeing a 304 error but this potentially caused some issues that we were hoping we could get some assistance on! After enabling CORS, we were seeing Errors for files uploaded in the collection part of the solution. All of the uploaded files had Status of Error and after checking the Step Function logs it looks like the flow was failing at Thumbnail generation. I am assuming this was happening due to headers being overwritten when we tried to enable CORS for the API Gateway resources, and I was trying to find a way to revert the CORS changes or if there was a solution to this problem. Any help is greatly appreciated, thank you so much!
    2 replies
    Ian Downard
    @ianwow
    MIE 2.0.5 was released today. This is the first version of MIE to be released as an official AWS solution. Yay! https://github.com/awslabs/aws-media-insights-engine/releases/tag/v2.0.5
    alokmandloi
    @alokmandloi
    i was able to create the stack but on the README i do not see any specific instructions as to how to find the UI as shown in the screenshot in README
    https://github.com/awslabs/aws-media-insights
    1 reply
    alokmandloi
    @alokmandloi
    @ianwow tagging you since you have commented on the releases for this
    alokmandloi
    @alokmandloi
    3 replies
    Zoltan Arvai
    @zoltanarvai_twitter

    Hi all! MIE looks like an absolutely awesome piece of product / solution. We are considering it to be a central part in our application. We are currently evaluating it and an interesting question came up:

    • Can we implement custom operators outside of the MIE codebase with another language like node?

    I'm digging through the code base / the CFN templates and while it seems kinda doable feels very hacky. I'm wondering what is your position on that?

    5 replies
    Russell Claxton
    @russellc92

    Hi,
    Some of cloudformation templates from the MI (not MIE) repo contain git change/merge syntax with in them, for example:

    ...
    ...
    Mappings:
    <<<<<<< HEAD:cloudformation/aws-content-analysis-use-existing-mie-stack.yaml
    =======
      MediaInsightsEngine:
        Release:
          Version: "v2.0.3"
    >>>>>>> ef8e22eb9e28d8057d207ce692c76279ca15d5b2:cloudformation/aws-content-analysis-create-new-mie-stack.yaml
      ContentAnalysisApp:
        SourceCode:
    ...
    ...

    in this template:
    https://github.com/awslabs/aws-media-insights/blob/2.0.4/cloudformation/aws-content-analysis-use-existing-mie-stack.yaml,

    This exists in the releases as well (2.0.4). Is this intended ?

    7 replies
    Jack Liddiard
    @deadcore
    Hey chaps, first up fantastic product :+1:
    I have a quick question - is there a way to start an execution and pass through some arbitrary (in our case K/V) metadata at the start of the execution.
    An example use case of this would be passing through the human readable 'Name' of the media object, so that the Kineses consumer it is able to resolve that value.
    I hope that makes sense?
    5 replies
    Ian Downard
    @ianwow
    The Media Insights (MI) demo app was updated today, featuring misc bug fixes, doc improvements, and a return of dropzone.js for drag-and-drop multi-file uploads. https://github.com/awslabs/aws-media-insights/releases/tag/v2.0.5
    Hiren
    @happyhirendra_twitter
    Hi,
    I am trying to setup aws-media-insights and getting following error for CompleteVideoWorkflow and CompleteImageWorkflow steps:
    Exception during processing: 'An error occurred (AccessDeniedException) when calling the CreateStateMachine operation: User: arn:aws:sts::<accountid>:assumed-role/WorkflowCustomResourceRole/M3-MediaInsightsWorkflowApi-WorkflowCustomResource-JQ8PMRqATfB0 is not authorized to perform: iam:PassRole on resource: arn:aws:iam::<accountid>:role/CustomerManaged/M3-StepFunctionRole-QC7QPYKFEZLE
    Any idea, what could be the issue?
    35 replies
    Hiren
    @happyhirendra_twitter
    One question - in which version of aws-media-insights .. custom dictionary feature is available ? I have installed v 2.0.3 however not seeing option to define custom dictionary
    3 replies
    Ian Downard
    @ianwow
    MIE 3.0.0 was released today, which features the ability to trigger workflows from S3 events, so, for example, workflows can automatically process files when they are copied to an S3 bucket. https://github.com/awslabs/aws-media-insights-engine/releases/tag/v3.0.0
    Jack Liddiard
    @deadcore

    Hey chaps, another quick question for you.

    Have you ever run into an error where you exceed the max size of the Step Functions IAM Role's policy? I've deployed MIE 2.0.5 with 3 custom operators who's policies are pretty much identical looking something like this:

    {
        "Version": "2012-10-17",
        "Statement": [
            {
                "Effect": "Allow",
                "Action": "lambda:InvokeFunction",
                "Resource": [
                    "arn:aws:lambda:...:...:function:jackliddiardMediaInsightsEngine-..."
                ]
            }
        ]
    }

    When Cloud Formation comes to adding the custom operator it returns this error

    Exception An error occurred (LimitExceeded) when calling the PutRolePolicy operation: Maximum policy size of 10240 bytes exceeded for role jackliddiardMediaInsightsEngine-StepFunctionRole-PG...

    I did see a brief mention on the topic here: awslabs/aws-media-insights-engine#291
    I was wondering if you have ever worked around it in the past?

    Jack Liddiard
    @deadcore
    Screenshot 2021-06-28 at 11.23.34.png
    I did also come across another peculiar thing which is built in operators are being added to the inline policies even tho the code hint's they should not be:
    # TODO: Once IAM supports the ability to use tag-based policies for
    #  InvokeFunction, put that in the StepFunctionRole definition in
    #  media-insights-stack.yaml and remove the following code block. Inline
    #  policies have length limitations which will prevent users from adding
    #  more than about 35 new operators via the MIE workflow api. Tag based
    #  policies will not have any such limitation.
    
    # Skip the inline policy creation for operators packaged with MIE.
    # The inline policy is not needed for those operators because the
    # StepFunctionRole has already been defined with permission to invoke
    # those Lambdas (see media-insigts-stack.yaml).
    if not ("OperatorLibrary" in operation["StartLambdaArn"] or "start-wait-operation" in operation["StartLambdaArn"]):
        # If true then this is a new user-defined operator which needs to be added
        # to the StepFunctionRole.
        #
        # Create an IAM policy to allow InvokeFunction on the StartLambdaArn
    aburkleaux-amazon
    @aburkleaux-amazon
    @deadcore - this looks like a problem in the code you referenced above. In the case where the MIE stack is deployed from an application stack, the operator library lambdas names do not contain the string "OperatorLibrary" so that code block is being executed unintentionally. Are you deploying the MIE stack separately or as a nested stack from another stack?
    aburkleaux-amazon
    @aburkleaux-amazon
    I'll add an issue to track this problem. I think you can work around it by deploying your application and MIE stacks separately. There are instructions on how to do this with the content analysis application here: https://github.com/awslabs/aws-content-analysis/tree/Release/v3.0.0#option-1-install-demo-app-over-an-existing-mie-stack. Basically, you deploy the MIE back end, then deploy the application and pass in the stack name for the MIE back end the application should use.
    Jack Liddiard
    @deadcore
    @aburkleaux-amazon - Yep we're deploying it as part of a nested stack :)
    aburkleaux-amazon
    @aburkleaux-amazon
    Thanks for confirming. One more question, you mentioned that you are adding your operators via the custom resource. Did you add them to the OperatorLibrary stack?
    Jack Liddiard
    @deadcore
    We're adding them through custom resources in CDK and the provided custom resource Lambda in MIE. Something in the spirit of this:
    const resource = new cdk.CustomResource(this, `${operatorName}Operation`, {
      serviceToken,
      properties: {
        ResourceType: "Operation",
        Name: operatorName,
        Type: type,
        Configuration: configuration,
        StartLambdaArn: this.startLambda.handler.functionArn,
      },
    });
    
    const cfnResource = resource.node.defaultChild as cdk.CfnResource;
    cfnResource.overrideLogicalId(`${operatorName}Operation`);