Wowza - Tips

Updated on December 10th, 2022

manifest.f4m no EXTM3U delimiter

Following the configuration of Wowza with HTTPS, ClipLink/Select may show an error similar to: manifest.f4m no EXTM3U delimiter

To resolve this, it is necessary to configure the web app web.config with the below:

    <add key="VideoServerAddress" value="https://5a5d7ebd5091c.streamlock.net:453" /> (Has to be a streamlock URL)
 <!-- <add key="VideoServerAddress" value="https://85.46.127.110:453" /> -->
    <!-- WOWZAServer address for Spectre View Web Proxies ! -->
    <add key="ProxyPathPrepend" value="sv6/_definst_" />
    <!-- E.g. required for WOWZA paths to HLS video -->
    <add key="ProxyRootFolder" value="" />
    <!-- Curator asset proxy paths are relative to this, assuming the URL to the video has the same file location from this root. -->
    <!-- <add key="ProxyPathAppend" value="/playlist.m3u8" /> -->
 <add key="ProxyPathAppend" value="/playlist.m3u8" /> (Does not need to be manifest.f4m)

Using USB licences on a VM

If you've installed Wowza on a VM and are also using a USB licence dongle, typically the Hypervisor won't be able to pass this through to the VM. The reason for this is that the USB presents itself as a HID rather than mass storage. To get around this, a 3rd party tool called Incentives Pro can be used to redirect the USB device to the VM. More information on this can be found here - http://www.incentivespro.com/hyper-v-usb.html 

A more flexible method would to be use a device such as AnywhereUSB which allows a USB device to be present over the network. The reason this is the preferred method is because if the VM was to change host, the USB device would also have to be physically moved to the new host. For situations like a clustered failover, this would be a requirement.

More information on this can be found here - https://www.digi.com/products/usb-and-serial-connectivity/usb-over-ip-hubs/anywhereusb 

 

Was this article helpful?