About the "Multimedia Hub Stopped" Error

You can sometimes receive a message on the unit itself that says Multimedia Hub Stopped:

Some common causes of this are actually related to the input to the LiveU Solo unit, which may not be clear given the error's statement.  

The sequence of events is:

1. The unit is not successfully sending a stream to the LRT cloud (see reasons below)
2. The cloud, which is expecting the stream, waits for a timeout period then stops the resource that was waiting for the stream
3. The cloud then indicates to the unit that the resource in the cloud has stopped due to never seeing a stream, and the unit reports "Multimedia Hub Stopped" 

So while the error is triggered from the cloud, it is really caused by the unit never successfully sending a stream.

The reasons a unit may not send a stream can include:

1. Bad video and audio input, such as no audio on the SDI or HDMI, or unusable video such as HDCP protected HDMI, or 4K video
2. While the unit can talk to the cloud, packets are never delivered to the cloud, which can be caused by specific firewall configurations on firewall protected connections such as corporate networks
3. More rarely, a hardware failed LiveU Solo unit 

A good first step in debugging this error is to look at your video and audio source input and ensure its what the LiveU Solo needs: audio included, HD video up to 1080p60, etc.