You can do this by selecting your Wowza live application, and selecting the Properties tab (possible only if you have enabled Advanced Settings on your Manager UI account). If you do need to stream to mobile devices and latency is important, you can opt to tweak the HTTP streaming packetization in your Wowza server so that your target chunk durations are shorter. But if you know that your target audience will only be using desktop, you control these machines (such as in an internal corporate network) where you can install the required plugins, and latency is a paramount requirement, then RTMP might be a better choice for you, as RTMP is a streaming protocol and is inherently less latent. Mobile devices don't support RTMP unless you use an app (like the VLC mobile app). The playback formats that you choose is really dependent on your target audience and players. Note that you need to include the application instance (default is _definst_). If your application name is vodedge, and you are streaming sample.mp4 from your amazons3 source, your example playback URL would then be: You will then need to create a VOD Edge type of application which can access these MediaCache sources. Each of these sources are identified with a prefix (for example, amazons3). MediaCache sources can be a Cloud storage provider (currently AWS S3, Google Cloud or Microsoft Azure), a file server, or a web server. ![]() To use MediaCache, you need to first create the MediaCache store (where the cached content is stored) and the MediaCache sources (where your Wowza server will obtain the remote content). On initial player request, it grabs the specified number of blocks from the remote location and caches the segments locally, which it then serves to all subsequent player requests. This is a more optimal way of streaming content that is not located locally. Since it sounds like you are trying to stream VOD files from a web server or S3 bucket, it's best to use the Wowza Streaming Engine MediaCache functionality.
0 Comments
Leave a Reply. |