First generation HDMI 1.4 spec UHD 4K, next-generation HDMI 2.0 spec UHD 4K and what integrators need to know.

An analysis of 4K Interim vs 4K Proper by Chris Pinder, Founder and MD of HDanywhere, June 2015.

blog2

4K is a complicated subject matter. 4K isn’t one format, it’s an umbrella term for many combinations of resolutions, frame rates and colours. Talking about 4K in too generalised a way is dangerous. When I discuss 4K with anyone, in as non-patronising a way as possible to simplify and aid understanding, I refer to ‘i’ and ‘p’, (like 1080i and 1080p) but my ‘i’ and ‘p’ doesn’t mean interlaced and progressive, I mean first generation 4K and next-generation 4K, or in other words  ’interim’ and ‘proper’. P could also quite easily stand for ‘premium’.

This is my take on the two-speed world of 4K UHD devices at the moment. It may be labelled and marketed as 4K, it may even support HDCP 2.2 – but is it 4Ki or 4Kp?

Proper 4K (4Kp) is next-generation HDMI 2.0 spec 4K, it’s what Ultra HD Blu-ray is and what premium 4K content will be. Ultra HD video refreshes at a smooth 60 frames per second in amazing 10-bit 4:2:0 colour (or if your display doesn’t support 10-bit) 8-bit 4:4:4 colour – basically hugely superior colours than what we have seen before over HDMI. 4Kp can also support HDR content and runs at very high 18Gbps data rates and, as a result, will require all new high-bandwidth HDMI 2.0a* spec electronics.  4Kp will also have HDCP 2.2 copy protection encrypting the content, which I’ll touch on later.

What is most important from integrator perspective is that single-cable HDBaseT DOES NOT carry 4Kp. It will only carry 4Ki because HDBaseT is max 10.2Gbps and 4Kp requires 18Gbps.

Most devices out there today labelled as ’4K’ do not support 4Kp, they only support 4Ki. And by most, I mean over 95%. But this is improving, more and more displays are coming out now that support HDMI 2.0 and have a 10-bit panel. Ultra HD Blu-ray is likely going to be the first 4Kp source device we see. So what is 4Ki?

Interim 4K (4Ki) runs at a 9G data rate (half that of 4Kp) and doesn’t necessarily require new HDMI 2.0 electronics. It will work on older HDMI 1.4 spec devices. It may or may not have HDCP 2.2 encryption. And colour-wise if it’s running at 60fps it can only be the lesser 8-bit 4:2:0 quarter colours. For 4:4:4 a lower 30fps refresh rate is used instead and smooth panning shots are sacrificed. 10-bit colour content just flatly isn’t supported full stop.

blog1

What is so important about colours?

4Kp/60 and 4Ki/60 if watched in black and white are EXACTLY the same. The same number of pixels wide and high, refreshing at 60 times per second, with the same pixel data for light and dark contrast. So no difference in sharpness, motion or contrast.

Where they differ is with a compromise on colour. The resolution of the colour layer that gets laid over the top of the black and white frame when combined to make the final image. With 8-bit 4:4:4 each pixel can choose a colour, whereas with 4:2:0 every 4 pixels have to share a single colour choice. Even though a cluster 4 pixels are sharing the same colour, the overlay of the black and white image creates different shades. The resulting 4:2:0 video content, although a lesser quality, is not as substantially different from 4:4:4 as you might think. In fact, when viewing the two from a couple of metres away, the human eye really struggles to differentiate them.

OK, now that you’re thinking is in tune with there being two primary types of 4K material and you understand the difference between the two.

You also NEED to be aware of a couple of associated meteors about to hit the AV side of the CI industry that relate to the facilitation of working 4K HDMI systems. (Remember HDMI is a system, NOT a cable) One is called ‘HDMI 2.0′ and the other is ‘HDCP 2.2′. The two meteors should really hit simultaneously, but not necessarily.

Meteor 1: HDMI 2.0 is the new twice-as-big digital pipeline to accommodate the higher data rates of proper 4K jumping from 9G to 18G bandwidth. Its not a new cable design, its new electronics at either end of the existing (short) HDMI cable we use. So that is new source devices (Ultra HD Blu-ray players for example) and new displays (10-bit SUHD Samsung panels for example). However for longish cable distances, say 3m and over, current passive cables may struggle with the higher data rates. We’ll begin to see some new breeds of HDMI cable types appear to solve this. Some will use integrated active/powered boosting chips and others are likely to be a copper/fibre hybrid cable. Existing long length HDMI cables, that may be buried in walls for example will be able to be utilised through the use of restorative dongles that can be placed at the start and end of the cable run. I expect to see this HDMI cable rescue/fixer market grow over the coming years sharply.

Meteor 2: HDCP 2.2 is the new 128 bit encryption designed to secure 4K content from being pirated. It is the same level of security encryption as credit card issuers use for internet transactions. Unless every device in the signal path is HDCP 2.2-capable, theoretically the content will not be shown. Source, matrix, AVR, balun, display, projector must all support HDCP 2.2. One weak link means black screen. The thing about HDCP 2.2 support is that it’s essential to ensure the best chance of displaying 4K content from your favourite content providers (i.e Hollywood and sports). The HDCP 2.2 event horizon will largely be determined by the release of Ultra-HD 4K Blu-ray and 4K content being delivered via our set-top-boxes.

Conclusion

In summary, until more next-gen 4Kp source devices, like Ultra HD Blu-ray, set-top-boxes, and media players are released we live in a kind of interim 4K limbo land, a phoney, interim 4K world with no proper, premium 4K content to enjoy. In addition to this, more displays with HDMI 2.0, HDCP 2.2 and 10-bit panels need to be released so that users can take full advantage of the advancements in picture quality offered by 4Kp. Month-on-month this situation improves.

From an integrator perspective, quite rightly there is a lot of emphasis currently on HDCP 2.2 support within matrixes. But even when HDCP 2.2 compliant, single-cable HDBaseT is a bottleneck in many video distribution systems, which will result in premium 4K content video quality being downgraded when distributed. There is a quality compromise currently in order to deliver a distributed solution over a single network cable.

SIDELINE RED HERRING: What about 4K streaming like Netflix?

Well it’s not 4Kp and it’s not 4Ki… It’s dynamically compressed, streamed 4K content using AVC H.264 and HEVC H.265 codecs with varying quality from home to home according primarily to the speed and quality of their network. For the purposes of this article, I am talking about uncompressed 4K content.

More info here: http://www.dailytech.com/Netflix+to+Stream+House+of+Cards+in+4K+via+HEVC+H265+Compression/article33962.htm

 

Picture loss/dropout on one or more displays when using MHUB

​Your MHUB is similar to a central heating system in that there are many components that all need to come together to deliver a working system. An intermittent or full loss in picture on one or more displays can be down to a number of things.

  • HDMI cables going into MHUB and from the display receivers to the displays
  • Your network cabling infrastructure, the termination quality, the distance of the cable run and the number of times that cable runs through patch panels or wall plates.
  • The physical output port on the MHUB
  • The display receivers
  • The actual source devices (more common than you think!) and the AV they are outputting (4K, 1080p, surround sound, HDCP format etc)

Unfortunately, there is no fast way to determine this. To do this test correctly you will need to test for several days to ensure the results are accurate and your system is stable.

If dropout occurs on one display in your property…

The first thing to do is disconnect all sources and outputs from MHUB so you are left with 1 source (preferably the source you notice picture loss on) and 1 output (preferably the display you notice picture loss most frequently on).

Grab a piece of paper and log the following outcomes when you test the following:

  1. If picture loss is happening only in one location in your property then take a display receiver (and the HDMI cable going into the display) from a known working location and swap it in the area you’re noticing picture loss.
  2. If you still experience picture loss then run freshly terminated Cat 6 cable from the MHUB to the display receiver point-to-point (no breaks in cable) and check again.
  3. If you are still having a problem then connect your new Cat 6 cable to another output port on MHUB.
  4. If #3 doesn’t resolve the problem then disconnect your source from MHUB (and the HDMI cable) and plug it directly into your test display using the same HDMI cable.
  5. If the picture is stable then take the source and the HDMI cable back to MHUB and plug it into another HDMI input and test for picture loss on your display.
  6. Finally, drop the resolution on your HDMI source to something you know the display will accept easily (something like 1080p Stereo)

If dropout occurs on all displays in your property…

Start by disconnecting your source from MHUB (and the HDMI cable) and plug it directly into a test display using the same HDMI cable.

Grab a piece of paper and log the following outcomes when you test the following:

  1. If the picture is stable then take the source and the HDMI cable back to MHUB and plug it into another HDMI input and test for picture loss on your display.
  2. If you still experience loss in picture then drop the resolution on your HDMI source to something you know the displays will accept easily (something like 1080p Stereo)
  3. Remove all outputs from MHUB until you’re left with only one output connected, it could be any port but we recommend starting with A. Check for a stable picture and repeat for each output port individually.
  4. If all ports passed the test in #4 then start connecting additional outputs back to MHUB starting B (so you should have A + B now), if the picture is stable add output C and so on.

If you log any problems or positives with each test then let us know and we can assist you further.

Sending TV audio from MHUB to in-wall or ceiling speakers using MHUB PRO 2.0 and MHUB AUDIO

Extracting video audio from MHUB and sending it to speakers

Today’s TVs are very thin with the latest models able to be rolled away into a box! A thinner TV is lighter, easier to install and generally more pleasing to the eye as these new advancements can radically change how your traditional TV looks or is installed into your property.

These advancements have reduced the space inside the TV to an absolute minimum and often a causality of this is the internal TV speaker. Speakers are either located on the rear of the panel (leading to muffled audio) or underneath and in many cases can not provide the type of audio amplification to match the large screen sizes found in the marketplace today.

Soundbars have plugged the gap, but they aren’t the solution.

Soundbars have plugged this gap as customers try to achieve audio reproduction that matches their picture quality. Whilst a soundbar is a simple solution to the problem it fair to say that it doesn’t present itself as the most elegant in that it’s additional (visible) hardware that you need to add to your AV setup. The soundbar is also tied to the function of the TV; so it’s not very easy to listen to music on the same device, for example.

De-embed the audio and manage it separately.

Using MHUB it’s possible to extract the audio that would be sent to your TV – or even the audio generated from your TV apps like Disney+ or Netflix and send that to speakers in your room. Additionally, when the TV is off you can listen to music on the same speakers. If your speakers are embedded in your walls or are in the ceiling then you won’t even notice them, but you’ll hear the difference.

Watch the setup video instead.

MHUB PRO 2.0 + MHUB AUDIO: how does it work

To achieve this you will need to use MHUB PRO 2.0 and MHUB AUDIO operating together as one system which we call V&A (video & audio).

Download the MHUB (V&A) guide.

The MHUB PRO 2.0 can de-embed the audio from any video stream or TV app (using ARC) and downmix it into 2 channel stereo. This audio is then fed into the inputs on MHUB AUDIO which manages amplification of that audio. If you have inputs that require amplification then you can stack another MHUB AUDIO (up to three times using uControl) or as many as you want if you’re using a control system.

We are here to help. Let us know if you have any questions…

.

Contacting us is super easy and we respond fast. Let us know if you have any questions about setting up a V&A system.

Handling Dolby Audio (Atmos) and DTS-HD audio with MHUB

Using a matrix and providing Dolby Atmos or DTS-HD audio.

atmos-mhub

If you are planning a cinema or media room supplied by MHUB that requires a multichannel audio signal like Dolby Atmos or DTS-HD then you will need additional hardware to achieve this result.

Why do I need additional hardware and what does it do?

In order to enjoy Dolby or DTS audio in a cinema or media room you will need to instruct your source device (AppleTV / Bluray / Set top box etc) to output its audio in Dolby Atmos or DTS-HD only.

If all the zones in your property can accept a multichannel Dolby or DTS signal then you will have no problem but the chances are that the rest of the rooms in the property will just have a standard TV with a left and right speaker only – think of a kitchen TV display or a TV in a kids room.

You therefore need a device that sits in-line (between) your HDMI video source and the MHUB that does the following important things:

  1. Sends an untouched signal from your HDMI source to your AVR (as if they were connected directly to one another) to provide it with Atmos or DTS-HD audio and…
  2. Split the signal and ‘downmix’ it so all those channels of audio are mixed into a left and right only for all other displays that the MHUB serves.

What is it called?

The device that you need is called the Dolby™ & DTS® AV Signal Manager.

What devices does it work with?

It will work with MHUBs and XTND hardware which feature HDMI mirrored outputs.

Extracting ARC from your TV to a nearby AVR or (Sonos) Amp

Many displays sold from 2015 come with apps to watch TV directly from the Internet (Netflix, Disney+, YouTube etc). If you want to extract that audio to nearby speakers you have two options: 1) extract the audio using a technology within the HDMI cable called Audio Return Channel (ARC) back to an amplifier that also has ARC or 2) extract the audio from the TV using its stereo or optical connection and run additional cabling back to the amplifier.

If the TV is wall mounted, is at a distance, or you are unable to run any additional cable to the amplification equipment then your only choice is to rely on ARC – if supported by your display – to achieve this result.

Both MHUB and XTND support ARC (check model spec) BUT there are some important points you should understand before purchasing your system. This article describes ARC extraction and control via CEC for XTND models.

xtnd-audio

Do they support eARC?

No. eARC is not supported currently. ARC support includes 2 channel audio (stereo) and multichannel audio upto 5.1 (if supported by your display).

Our extenders do not mimic a long HDMI cable…

Your MHUB or XTND device does not act like a long HDMI cable and should not be thought of as one. Our devices can handle HDMI features like HDCP, EDID, CEC and ARC but it doesn’t ‘pass it through’ like a standard copper HDMI cable does point-to-point.

With ARC on our XTND models for example, it doesn’t pass through to the HDMI cable on the source side. Instead our extenders extract the audio to an optical or analogue output which can then be fed in to an AVR or Amp.

This is done because the XTND is not an ARC extender. It is primarily a HDMI video extender that supports the ARC featureset.

…meaning you can’t use ARC + CEC together.

So for scenarios where you want to use Sonos Amp you might have a problem because you can not use the TVs remote control to control the Sonos Amp but you have an alternative options because you can use IR passback to control the Sonos Amp instead.

MHUB, XTND and soundbars

Soundbars

As TVs have become thinner, the space required for housing speakers within them have diminished, often leaving TV audio weak, lacking in depth and richness. Soundbars are an effective solution to that problem and HDANYWHERE works with them absolutely fine.

Picking the right soundbar.

There are generally three types of soundbar available.

  1. Stereo soundbars
  2. Multichannel 5.1 soundbars
  3. Multichannel (Spacial) soundbars that support Dolby Atmos and DTS-HD

1. Stereo soundbars

If you have #1 (stereo soundbars) then you’re good to go. This will work all over your property as the speaker arrangement and capability is just a better version of what your TV already supports.

2. Multichannel soundbars

If you intend on fitting #2 then you will need to consider what capability your other rooms/zones can handle around your property. If your soundbar supports 5.1, then we suggest reading the guidance here.

What the guidance above says (briefly).

If you want your soundbar to output 5.1 then you will need to make sure your source is also set to output 5.1. When you do this all displays connected to MHUB will receive a 5.1 audio signal and if that display can’t decode 5.1 audio and downmix it into stereo then you will have an audio problem.

3. Multichannel (Immersive) soundbars

If you intend on installing a soundbar with this capability and require the source to be distributed then you will need additional hardware to manage the signal. We would recommend that you read Using MHUB and providing Dolby Audio (Atmos) and DTS (DTS-HD) audio.

Confused? Help is available, drop us an email for a fast response.

Using MHUB with an AVR

Using an AVR and MHUB for multichannel audio in 1 room/zone.

Adding a cinema or media room to MHUB is a relatively easy task for the MHUB to do but if you are planning to have a room with equipment inside it that is of a higher specification to the rest of the property then you need to do a little pre-planning beforehand.

multichannel-1

For best results the source(s) that will be watched in that room should be fixed to serve just that room.

The chances are that this room will have the best display capability and the best audio capability. Because all HDMI sources (bluray, AppleTV, Amazon Fire etc) can only output one format of video and one format of audio at any given time you should ideally serve this room with sources dedicated to it. This way the source can be set to output the correct video resolution and audio format without having to readjust when the stereo 1080p TV accidentally tries to request a picture from the source.

If you have MHUB PRO then we recommend using the HDMI cable direct to your AVR and then the digital coax after.

… Then tell MHUB to only request what that room can handle

Other displays in your property (like that 1080p display in the kitchen) are able to contact your source device to downgrade it’s audio and video capability. You can block this from happening by selecting an appropriate EDID profile for your source from within MHUB-OS.

You don’t need to do this if you fix the output from the source device to your room but we recommend it to make sure your system doesn’t suffer from strange behaviour.

I would like that source available throughout my property? What happens if I fix the source and set EDID above?

If the source is fixed to output 5.1 then MHUB will deliver 5.1 audio to all HDBaseT outputs connected to MHUB. If your TV or display can decode and downmix multichannel audio into stereo (many now do) then you will hear the content correctly in stereo. If the TV is unable to decode the 5.1 audio then you are likely to have audio problems or hear nothing at all.

Listening to content on all displays.

Are there any ways around this problem?

Yes. Many modern TVs can accept a 5.1 audio signal so that they can work with 5.1 compatible soundbars over HDMI ARC or Optical connections. Depending on the TV specification, it can work in two ways:

  1. MHUB outputs 5.1 audio to the TV and it passes the audio directly to a compatible soundbar (additional soundbars required).
  2. MHUB outputs 5.1 audio to the TV and the TV downmixes the audio back into stereo.

multichannel-2

This will mean that you get 5.1 audio in rooms where you need it and stereo everywhere else. It is important that you check the specification of your displays carefully before considering this option. Older TVs are not likely to handle multichannel audio at all ruling out this option entirely.

 

Using control drivers which require authorisation before use.

update-mos

HDANYWHERE are now working with Intrinsic Dev for control driver integration.

If you see the label “DRIVER REQUIRES LICENSE ACTIVATION FROM VENDOR” then this means you need to create an account and generate a license key before the driver will work. As always, the driver remains FREE OF CHARGE. The process takes under 5 minutes to complete and offers HDA Pros the following benefits:

1. Track and find your drivers for every install you commission.
2. Be kept updated if the driver gets patched or improvements are added.
3. Check to see if the driver is operating correctly.
4. The ability to improve your HDA Pro listing

 

1. Visit https://www.intrinsicdev.com/ and login or create an account.

1

 

2. Ensure that you are logged in.

2

3. Find the HDA driver you want to download https://www.intrinsicdev.com/brands/hdanywhere

3

 

4. Click on “Get License Key”

 

5. You will need to provide the MAC address of your controller and some site details. Scroll to the bottom of the page and a button will appear to proceed/download. If you have not completed this step correctly then the button to download will not appear.

5

 

6. Download the driver and make a note of the activation code.

6

HDANYWHERE product information on power usage and BTU outputs

The table below details the PSU DC rating, the system power draw in watts and BTU(British thermal unit) heat output of each device.

Product Code Release PSU Rating (DC) Power Draw (watts) BTU

XTND

XTND2K30 2017 5V 1A 2.5 9
XTND4K40ARC 2018 24V 1A 20 68
XTND4K100TPC 2018 24V 1A 12 41

MHUB

MHUBAUDIO64 2018 24V 13.4A 520 1774
MHUBMAX44 2018 24V 2.71A 19.2 66
MHUB431U 2018 24V 2.71A 36 123
MHUB862U 2018 24V 2.71A 28 198
MHUBPRO4440 2018 24V 2.71A 40 136
MHUBPRO8870 2018 24V 6.3A 98 334
MHUB4K44PRO 2016 24V 2.71A 42.72 146
MHUB4K88PRO 2016 24V 6.3A 100 341
MHUBPRO24440 2019 24V 5A 68 232
MHUBPRO288100 2019 24V 6.3A 130 444

SPLITTERS AND SCALERS

SPLITTERMAX12 2019 5V 1A 2 7
SPLITTERMAX14 2019 5V 1A 2 7
SIGNALMANAGER 2018 5V 1A 1.65 6

MHUB-OS 8 and uControl 2 update troubleshooting and FAQ

Below is a list of three issues which have been reported to HDANYWHERE (HDA) after updating older systems to MHUB-OS 8 (MOS 8). If you have encountered any of these problems then you will find a solution below. If your issue is not shown below then contact the HDA support team via email on – support@hdanywhere.com.

Jump to issues and solutions:

  1. My MHUB is stuck in a loop and is always prompting me to update again – I can not access any other MHUB-OS page.
  2. I am having problems connecting with HDA Cloud because there is an error with my serial number.
  3. I have connected to my MHUB and all my settings are gone.
  4. I can’t get uControl to connect to MHUB.
  5. I have an 8×8 system and I can not control my TVs anymore.

1.
I’ve clicked the update from within MHUB-OS and now appear to be stuck on an update page and cannot access any other MHUB-OS page.

This error can occur when MHUB fails to complete the update process completely. This can be caused by a power outage, multiple sessions of MHUB-OS being open at the same time (browser tabs, app) or network issues as the update is applied to MHUB. This has been patched in version 8.02 of MHUB-OS. However, if you find yourself with a problem like this, you will need to contact HDANYWHERE technical support services by emailing support@hdanywhere.com with the subject line: “Update error code:728″ and we will treat this with the highest priority.

2.
I’ve updated to MHUB-OS 8 and when linking to HDA cloud it says there is an error with my serial number.

This error can occur when the MHUB cannot connect with HDA cloud. This can be caused by network issues or power outage. This has been patched in MHUB-OS version 8.02. However, should you find yourself in this situation you can recover the serial number following these steps

  1. Step 1 – Load a web browser on a pc or mac(such as Chrome), and enter the following in to the URL bar [MHUB IP ADDRESS]/diagnostics.php. Then click on “GET SERIAL NUMBER”
  2. Step 2 – Confirm that you want to change the serial number
  3. Step 3 – You will get a notifcation saying that the serial number has been updated, and should notice the serial number is showing in the system information section near the top of the page.

If after using the serial number recovery method above, it still does not appear, you will need to contact HDANYWHERE technical support services by emailing support@hdanywhere.com with the subject line: “Update error code:628″

3.
uControl has updated, when I reconnected to my MHUB all my settings were gone.

This can occur when reconnecting to your MHUB after uControl has updated to version 2 or greater and selecting the incorrect option. When uControl loads you are shown 2 options:

  • “SETUP A NEW MHUB SYSTEM” – This is used when you are connecting to a brand new or unconfigured MHUB system. If you select this option and have a previously configured system, all user data will be removed requiring the MHUB to be fully reconfigured like a new system.
  • “CONNECT TO AN EXISTING MHUB SYSTEM” – This is used when you are connecting to a previously configured MHUB system. Existing data will remain untouched, and uControl will sync the data stored. If you were connected with a previous version of uControl this option should be used.

4.
After the update, uControl can not connect to MHUB

HDANYWHERE released an update to uControl and all MHUB systems on Wednesday 10th October 2018. To ensure that your MHUB works correctly both your MHUB and uControl must be on the correct software version.

MHUB / MHUB-OS = version 8 or above
uControl (iOS / Android) = version 2 or above

If you find that one version of uControl can connect to MHUB and the other can not then it is very likely that you did not complete the update to MHUB-OS. As soon as you have run this process then uControl should work on all devices with no issue. For this solution HDANYWHERE are assuming that your system is already in a pre-configured state and that you are wanting to CONNECT TO AN EXISTING SYSTEM.

Steps to resolve this issue:

  1. Ensure that you have the latest version of uControl installed on your iOS or Android device. Download uControl for iOS or download uControl for Android
  2. Once you have the app installed, please load it up and follow the instructions here:

5.
I have a 8×8 or 8×6+2 system and after the update, I lost the ability to control my TVs

If you are able to control your source devices with uControl but can not control your displays then a quick update to your MHUB will resolve this problem. Instructions detailing how to update your MHUB can be found here. Ensure that you use uControl to update your MHUB and do not try to update your system via MHUB-OS.

MHUB-OS 8: a quick guide to zones

Zones define a physical space in a property where outputs from MHUB terminate.

A Zone can include a maximum of 1 video output and a maximum of 4 audio outputs. For example, you can create a zone called “Kitchen” and assign 1 video and 1 audio output to it to provide you with viewable TV and sound. A Zone must contain at least 1 output from an MHUB for it to be addressable for control. Note: outputs can not be shared or split to more than 1 Zone.


MHUB zones

MHUB-OS 8 first boot process

The first boot process for MHUB-OS has remained largely unchanged with the exception of zones.

The slideshow below walks you through the steps within MHUB’s first boot process and how to setup zones to refect the different rooms or areas within you property.

If you wish to configure a stacked system please watch this video – Creating a MHUB stacked system.

You should be able to complete the process in under 10 minutes.

MHUB-OS first boot steps are as follows:

  1. EULA and Privacy policy
  2. Name your MHUB
  3. Name your source devices
  4. Create zones
  5. Assign outputs to zones
  6. Confirm zones
  7. Connect MHUB to HDA Cloud
  8. Complete setup

HDANYWHERE(HDA) recommends that every MHUB install goes through its first boot process to ensure that the MHUB is setup correctly.

How long does the process take to complete

If you have an update to install then then first boot usually take about 10 minutes. If there is no update you can normally finish the entire process and have an operational MHUB system well within 5-7 minutes.

Yes. You do not need to access MHUB-OS if you don’t want to. But this is only recommended if you intend to control you MHUB via a control system. You will also miss the opportunity to increase your warranty period and open your MHUB to additional features or services.

I don’t want to use MHUB-OS or go through the first boot process, will MHUB work like a normal?

Yes. You do not need to access MHUB-OS if you don’t want to. But this is only recommended if you intend to control you MHUB via a control system. You will also miss the opportunity to increase your warranty period and open your MHUB to additional features or services.

I made a mistake in the first boot process, can I go back or make a change?

Yes. You can go all the way back to the update step and correct any incorrect information you entered. Alternatively, you can also access MHUB-OS (after you have completed first boot) and change anything then.

Updating MHUB-OS to a new version

If you have received a notification in uControl or by email that an update is available for your MHUB-OS then follow these steps to update your system. All updates are now handled by uControl. Please ensure you have installed the latest version.

If you have not connected to your MHUB before, please follow this guide first – Connecting to a MHUB

If you have received a notification in uControl or by email that an update is available for your MHUB then chose the correct option below:

Updating an existing system

The majority of MHUB customers will be on MHUB-OS 7 and their systems will contain user data which needs updating to the latest version. If this is you then follow these steps.

  1. Click ‘Connect to an exisiting MHUB system’, uControl will scan your network for any MHUB systems
  2. Select your MHUB device
  3. Connect to your MHUB
  4. uControl will show popup message that MHUB-OS requires updating, click ‘update’ and follow on screen prompts

 

Updating an New system

This is likely to happen if you have recently bought MHUB and it was shipped to you on older software. You will run through the following steps:

  1. Click ‘CONNECT TO MHUB SYSTEM’, uControl will scan your network for any MHUB systems
  2. Select your MHUB device
  3. uControl will check the current version of MHUB-OS, if an update is required, you will be prompted to update it.
  4. Connect to your MHUB
  5. Perform first boot process.

Updating to MHUB-OS 8.00 from an earlier version

If your version of uControl updates to version 2.0 or above automatically, any previous connection to your MHUB will be reset. This is normal and part of the update process. Follow the process as described in ‘Updating a New System’ and uControl will update your system as part of the connection process.


update-mos

Follow the instructions within the app to connect back to your system. During this process uControl will check MHUB(s) to see if they also require updating.

Watch a video of it here:


Having trouble updating your MHUB, check here -Update Troubleshooting

MHUB-OS Firmware 1.30 update – Complete

The first part of this update roll-out has now been completed. Any new MHUB’s connected to the internet will automatically upgrade when the unit is powered on, this may extend the boot time by 30 seconds

 MHUB Firmware 1.30

HDA Cloud is moving to a new & more sophisticated server.
This will automatically start at 8:00am (BST) Monday 30th July.

HDA Cloud is our secure online portal that allows you to remotely access any network-connected MHUB system around the world. It allows you to remotely manage, configure, and troubleshoot installations to help keep your systems running smoothly.
Perhaps most importantly, HDA Cloud is our central data storage server and we take our responsibility to keep all data super safe and secure very seriously. As such, we have provisioned the very latest server technology and security for a faster and more secure connection. Additionally, the platform will enjoy new features and upgrades which will be revealed soon!

The update will come in two stages; first, we will update MHUB systems around the world and after that is complete we will move HDA Cloud to its new home. You will not need to do anything. MHUB systems will update in the following order:

MHUB systems

MHUB MAX (4×4) – Monday 30th July 2018 – Complete
MHUB PRO (4×4) 40 – Wednesday 1st August 2018 – Complete
MHUB (8×6+2) – Wednesday 1st August 2018 - Complete
MHUB (4×3+1) – Thursday 2nd August 2018 - Complete
MHUB PRO (4×4) 70 – Friday 3rd August 2018 – Complete
MHUB PRO (8×8) 70 - Friday 3rd August – Complete

HDA Cloud Migration - Monday 6th August

– Complete
During this migration, HDA cloud will be unavailable. Starting at 10.00am UTC for 4 hours.

In most case’s this is a background update and should not require any user interaction. However, some systems may need a manual hard reboot (full mains power down for 10 seconds, then reconnect) to apply the update. MHUB video operation will function, but if you notice MHUB control (uControl/MHUB-OS/control system) is not responding, perform the above reboot.

 

To confirm that the unit has been updated either check in MHUB-OS on the MHUB setup page or check on HDA Cloud

EDID management on MHUB systems

All MHUB systems offer advanced EDID management from within MHUB-OS and from the units front panel(PRO systems only). EDID management is an important facet of installing a whole-home AV system, and improper configuration will result in a system that doesn’t operate at its full capabilities. More and more source devices are limiting there selectable output resolutions based on the EDID they read from the display, as such you may find without proper EDID management that your devices won’t offer you the display resolutions and audio formats you want.

EDID (Extended Display Information Data) data exchange is a standardized means for a display to communicate its capabilities to a source device. The premise of this communications is for the display to relay its operational characteristics, such as its native resolution, to the attached source, and then allow the source to generate the necessary video characteristics to match the needs of the display. This maximizes the functional compatibility between devices without requiring a user to configure them manually, thus reducing the potential for incorrect settings and adjustments that could compromise the quality of the displayed images and overall reliability of the system.

EDID information looks something like this:

(20) Video Input Definition: Analog
0.700, 0.000 (0.700 V p-p)
Separate Syncs, Composite Syncs, Syncs on Green

(21) Maximum Horizontal Image Size: 62 cm
(22) Maximum Vertical Image Size : 34 cm
(23) Display Gamma : 2.20
(24) Power Management and Supported Feature(s):
Active Off/Very Low Power, RGB Color, Non-sRGB, Preferred Timing Mode

(25-34) Color Characteristics
Red Chromaticity : Rx = 0.626 Ry = 0.337
Green Chromaticity : Gx = 0.306 Gy = 0.626
Blue Chromaticity : Bx = 0.156 By = 0.057
Default White Point: Wx = 0.313 Wy = 0.329

(35) Established Timings I

720 x 400 @ 70Hz (IBM, VGA)
640 x 480 @ 60Hz (IBM, VGA)
640 x 480 @ 67Hz (Apple, Mac II)
640 x 480 @ 72Hz (VESA)
640 x 480 @ 75Hz (VESA)
800 x 600 @ 60Hz (VESA)

(36) Established Timings II

800 x 600 @ 75Hz (VESA)
1024 x 768 @ 60Hz (VESA)
1024 x 768 @ 75Hz (VESA)
1280 x 1024 @ 75Hz (VESA)

(37) Manufacturer’s Timings (Not Used)

(38-53) Standard Timings

1920×1080 @ 60 Hz (16:9 Aspect Ratio)
1280×1024 @ 60 Hz (5:4 Aspect Ratio)
1280×960 @ 60 Hz (4:3 Aspect Ratio)
1440×900 @ 75 Hz (16:10 Aspect Ratio)
1440×900 @ 60 Hz (16:10 Aspect Ratio)
1680×1050 @ 60 Hz (16:10 Aspect Ratio)
1280×720 @ 60 Hz (16:9 Aspect Ratio)

However, this becomes much more complicated in situations with multiple displays such as a splitter or a video matrix, this is because the device in question must now decide on a single EDID to present to a source device from the available displays. Normally this will be the lowest common denominator, which is ok for initial setup as it will guarantee you have video/audio in all locations. This may not be the desired result long term.

This is where EDID management becomes important. EDID management is the process by which you manually select the EDID you wish to be presented to each individual source device, this ensures you get the desired Video/Audio output from each connected source device and utilise your system to the maximum of its capabilities.

This menu can be accessed via the AV Settings menu in MHUB-OS

Edid 1

This menu contains 2 main types of EDID, Pre-Defined EDIDS such as

4K2K60, Stereo Audio 2.0, HDR

This would present a source device with a ‘display’ capable of 4K video with HDR enabled and 2.0 channel audio.

Alternatively, MHUB-OS has the ability to copy an EDID from a connected display. Depending on the MHUB system you have EDID data can be copied from either the HDMI mirror or from the HDBT output(supported on PRO 2, MHUB41140).