Playback of audio only content from Azure Media Services65 votes
This feature is a future planned item.
Audio Only scenarios are currently supported by live streaming pipeline, but not fully supported by Azure Media Player on DASH and on some platform with Smooth Streaming. You can use iOS native player to play audio only HLS output untill AMP gets the support.
Having to plan ahead and manually reserve Encoding Units prior to submitting jobs, then manually stopping them upon job completion loses one important aspect of cloud computing: auto-scalability.
It would be much more useful to set an upper limit on number of reserved concurrent encoding units and let WAMS manage according to size of job queue.
This would make WAMS Encoding elastic and on par with other cloud encoding services.59 votes
Auto-scaling of reserved units is on the roadmap for Windows Azure Media Services.
See https://en.wikipedia.org/wiki/High_Efficiency_Video_Coding. Our internal tests with HEVC/H.265 encoding is that it can decrease 4K file size by 4X. Please consider adding support for this encoder as an option for video output.37 votes
The live streaming channels should be able to keep online for a longer time window to support 24/7 live streams. The actual service works as long as you don't use the transcoding functionality but has some issues.
For this type of streams a channel has to persist at all time and player URL has to be the same... even when a the ingest RTMP has some issues. A really nice feature would be a static slate/image that is showed in the live stream when there is no RTMP signal for some time.21 votes
When we use Live, some useful properties like Video length, bitrate for CMS don't have from other system. It's usually video file like mp4 itself have data in property.
it's useful if there is any Property via API for live streamings to put CMS.
- Video length
- Video Size10 votes
In live streamin we have a bug with flash media live encoding to use encoding with channels in order to try keep the frame rate. I think that the focus must be in solve this issues and make better compatilbility whit other programs too this happens with obs and fmpeg too.4 votes
Individual asset names do not show up in the portal when asset was created using v3 API.
However querying the client works.1 vote
This is a limitation in the Azure Portal for customers that are using v3 API. The portal is currently just using v2 API’s so there are a number of gaps and backward compatibility issues with regard to use of v3 APIs. We recommend just using the v3 capabilities via API for now. Work is underway to support v3 API’s in the portal. If UI tool is needed prior to this availability, the Azure Media Services Explorer tool (https://github.com/Azure/Azure-Media-Services-Explorer) can be used as it has full support for v3 API’s.
- Don't see your idea?