An automated reference implementation leveraging AWS Step Functions and AWS Media Services to deploy a scalable fault tolerant Video on demand workflow
When I create a MediaConvert Job to generate Apple HLS outputs from and input test.mp4 for 360p, 540p and 720p resolutions with their named modifiers set as _360, _540and _720 respectively, the files are all stored in this format:
test_360.m3u8, test_540.m3u8, test_720.m3u8 and test.m3u8 (for the sake of simplicity). Isn't there a way to separate the files into folders based off their resolutions? Like <s3 bucket URL>/test/360p/0001.m3u8 for each resolution as storing everything in a single folder is quite messy.
When I create a MediaConvert Job to generate Apple HLS outputs from and input
test.mp4
for360p
,540p
and720p
resolutions with their named modifiers set as_360
,_540
and_720
respectively, the files are all stored in this format:test_360.m3u8
,test_540.m3u8
,test_720.m3u8
andtest.m3u8
(for the sake of simplicity). Isn't there a way to separate the files into folders based off their resolutions? Like<s3 bucket URL>/test/360p/0001.m3u8
for each resolution as storing everything in a single folder is quite messy.