By using AWS re:Post, you agree to the Terms of Use
/Media Services/

Media Services

AWS offers the most purpose-built media services, software, and appliances of any cloud to make creating, transforming, and delivering digital content fast and easy. With pay-as-you-go Media Services and advanced video processing appliances, you can produce high-impact creative projects and outstanding viewing experiences.

Recent questions

see all
1/18

MediaConvert: Single frame video

My project uses MediaConvert to transcode user-generated content to lower resolution. I run into an issue that if user uploads a single frame video, MediaConvert will return "Frame rate is set to follow, but there is no frame rate information in the input stream info." Is there a way to solve the issue? Thanks, Alan ``` { "Description": "OTT, HLS (Cell), TS, AVC, AAC, 4x3 DAR, 640x480, QVBR", "Category": "OTT-HLS", "Name": "HLS_480", "Settings": { "VideoDescription": { "Width": 640, "ScalingBehavior": "DEFAULT", "Height": 480, "VideoPreprocessors": { "Deinterlacer": { "Algorithm": "INTERPOLATE", "Mode": "DEINTERLACE", "Control": "NORMAL" } }, "TimecodeInsertion": "DISABLED", "AntiAlias": "ENABLED", "Sharpness": 50, "CodecSettings": { "Codec": "H_264", "H264Settings": { "ParNumerator": 1, "Syntax": "DEFAULT", "HrdBufferInitialFillPercentage": 90, "Slices": 1, "GopBReference": "ENABLED", "HrdBufferSize": 1200000, "MaxBitrate": 600000, "ParDenominator": 1, "SpatialAdaptiveQuantization": "ENABLED", "TemporalAdaptiveQuantization": "ENABLED", "FlickerAdaptiveQuantization": "ENABLED", "EntropyEncoding": "CABAC", "RateControlMode": "QVBR", "QvbrSettings": { "QvbrQualityLevel": 7 }, "CodecProfile": "HIGH", "MinIInterval": 0, "AdaptiveQuantization": "HIGH", "CodecLevel": "LEVEL_3_1", "FieldEncoding": "PAFF", "SceneChangeDetect": "ENABLED", "QualityTuningLevel": "SINGLE_PASS", "UnregisteredSeiTimecode": "DISABLED", "GopSizeUnits": "AUTO", "ParControl": "SPECIFIED", "RepeatPps": "DISABLED" } }, "AfdSignaling": "NONE", "DropFrameTimecode": "ENABLED", "RespondToAfd": "NONE", "ColorMetadata": "INSERT" }, "AudioDescriptions": [ { "AudioTypeControl": "FOLLOW_INPUT", "AudioSourceName": "Audio Selector 1", "CodecSettings": { "Codec": "AAC", "AacSettings": { "AudioDescriptionBroadcasterMix": "NORMAL", "Bitrate": 64000, "RateControlMode": "CBR", "CodecProfile": "HEV1", "CodingMode": "CODING_MODE_2_0", "RawFormat": "NONE", "SampleRate": 48000, "Specification": "MPEG4" } }, "LanguageCodeControl": "FOLLOW_INPUT", "AudioType": 0 } ], "ContainerSettings": { "Container": "M3U8", "M3u8Settings": { "AudioFramesPerPes": 4, "PcrControl": "PCR_EVERY_PES_PACKET", "PmtPid": 480, "PrivateMetadataPid": 503, "ProgramNumber": 1, "PatInterval": 0, "PmtInterval": 0, "VideoPid": 481, "AudioPids": [ 482, 483, 484, 485, 486, 487, 488, 489, 490, 491, 492, 493, 494, 495, 496, 497, 498 ] } } } } ```
0
answers
0
votes
1
views
asked 13 days ago

V3 JS SDK Kinesis Client getting ERR_HTTP2_INVALID_SESSION error

Hi There, I am trying out Kinesis Client in [JS SDK V3](https://docs.aws.amazon.com/AWSJavaScriptSDK/v3/latest/clients/client-kinesis/globals.html). When I create a Kinesis Client in the global scope and reuse the same client for all further Kinesis ingestion, I am noticing that after a while I am getting the following error. ``` 1|new-sig | { Error [ERR_HTTP2_INVALID_SESSION]: The session has been destroyed 1|new-sig | at ClientHttp2Session.request (internal/http2/core.js:1559:13) 1|new-sig | at Promise (/home/ec2-user/signaling-v7.temasys.io/node_modules/@aws-sdk/node-http-handler/dist-cjs/node-http2-handler.js:57:33) 1|new-sig | at new Promise (<anonymous>) 1|new-sig | at NodeHttp2Handler.handle (/home/ec2-user/signaling-v7.temasys.io/node_modules/@aws-sdk/node-http-handler/dist-cjs/node-http2-handler.js:37:16) 1|new-sig | at stack.resolve (/home/ec2-user/signaling-v7.temasys.io/node_modules/@aws-sdk/client-kinesis/dist-cjs/commands/PutRecordCommand.js:27:58) 1|new-sig | at /home/ec2-user/signaling-v7.temasys.io/node_modules/@aws-sdk/middleware-serde/dist-cjs/deserializerMiddleware.js:5:32 1|new-sig | at /home/ec2-user/signaling-v7.temasys.io/node_modules/@aws-sdk/middleware-signing/dist-cjs/middleware.js:11:26 1|new-sig | at process._tickCallback (internal/process/next_tick.js:68:7) '$metadata': { attempts: 1, totalRetryDelay: 0 } } ``` I am not getting an idea as to why this is happening. However when I use a custom requestHandler and disable Keep-Alive the client stops throwing the error (like the below code) ``` const { NodeHttpHandler } = require("@aws-sdk/node-http-handler"); const { Agent } = require("http"); const kinesisClient = new KinesisClient({ region: kinesisDataStream.region, requestHandler: new NodeHttpHandler({ httpAgent: new Agent({keepAlive: false}) })}); ``` Could you help me in understanding what's going on ? Thanks a lot.
1
answers
0
votes
5
views
asked 13 days ago

Popular users

see all
1/18

Learn AWS faster by following popular topics

1/1