OFFICIAL Q5 PRO FIRMWARE. FUTEKO. HMD-2.0.4 2017-07-07

[HereIsTom]

Will this update fix the audio pass-through problem with the Kodi 17 player due to the added IEC61937 Audio standard within Kodi? And how about the issue with the custom homescreen and a screensaver?

No it don't, but it can if you read this topic;
http://www.futeko.com/newforum/index.php?topic=2011.0

So you installed the shitty kodi version and the problem is solved? I really need kodi 17 because a lot off add-ons stopped working in Jarvis.

As you can see in that topic I installed the shitty build Kodi 17.4 and get audio passthrough.

[Eik]

It doesnt look worst without IE. It looks more realisitic without black and white crush. If you want unrealistic pictures, use the dynamic contrast and other stuff of your tv. It has the same effect.

I bet it's a bit more complex than simple dynamic contrast used in tv settings (which looks bad).
Beside that, I have dynamic contrast turned off in imprex, same with the other stuff, I'm talking about pure IE that doesn't cause black/white crush for me (at least nothing noticable), yet image looks better. Got other Q5 picture settings adjusted accordingly, so the image isn't oversaturated or with messed up bright/dark details.

It's still one of the main features of the box, it should work.

[hanspampel]

Believe me. There is no magic or voodoo from IE what your tv cant do. Its only playing with gamma, contrast and brightness. Nothing else.

And btw. the IE doesnt work on 4k und 4k HDR material. Sharpness and HDR saturation still not work on 2k material. Never worked since they released the pro devices . @futeko.com. Maybe you can report it to himedia.

[oxanna]

but yr competitor Egreat remain the best.
this new firmware don'read the new film 4k uhd full rip 1.1 with menu  as  movie "Inferno.2016.COMPLETE.UHD.BLURAY-TERMiNAL".
why???

[Mount81]

Hello!

So we still have a couple of bugs regarding subtitles, like this: http://www.futeko.com/newforum/index.php?topic=1967.msg16440;topicseen#msg16440.

My two questions: is automatic subtitle encodig recognition issue resolved (or at least eased) in 2.0.4? And is the issue with <i>italic character lines like this</i> still present in 2.0.4? Correction Edit: I mean that in the case of srt subtitles the italic lines doesn't appear as italic, rather just normal.
Could someone check, please?!

If these aren't fixed, than take these as a reminder, thank you!

[jeps]

Hello!

So we still have a couple of bugs regarding subtitles, like this: http://www.futeko.com/newforum/index.php?topic=1967.msg16440;topicseen#msg16440.

My two questions: is automatic subtitle encodig recognition issue resolved (or at least eased) in 2.0.4? And is the issue with <i>italic character lines like this</i> still present in 2.0.4?

Could someone check, please?!

If these aren't fixed, than take these as a reminder, thank you!

Hi

Automatic encoding of subtitles is not completely fixed.

The missing functionallity regarding tagging of subtitles still manage to surprise me.
I mean, how hard can it be?
They should at least remove "</i>" since they already remove "<i>".
I would of cause prefer the full functionallity.

[Eriol]

Hello!

So we still have a couple of bugs regarding subtitles, like this: http://www.futeko.com/newforum/index.php?topic=1967.msg16440;topicseen#msg16440.

My two questions: is automatic subtitle encodig recognition issue resolved (or at least eased) in 2.0.4? And is the issue with <i>italic character lines like this</i> still present in 2.0.4?

Could someone check, please?!

If these aren't fixed, than take these as a reminder, thank you!

Checked:
Autorecognition still not working
Line spacing still poorly implemented
Line tags like italic and bold not working but at least the tags (like <i>) are not displayed now
Too short time difference bug is fixed

New bug:
In the case of overlapping subtitles the second subtitle only blink up for a few millisecond doesn't matter how much is the actual duration of the subtitle.


Edit:
Checks were done with ANSI encoded external srt.

[jeps]

Checked:
Autorecognition still not working
Line spacing still poorly implemented
Line tags like italic and bold not working but at least the tags (like <i>) are not displayed now
Too short time difference bug is fixed

They are on my Q5 
Not the "tags on" part  <i> but only the "Tags off" part </i> is visible.

[Eriol]

Line tags like italic and bold not working but at least the tags (like <i>) are not displayed now

They are on my Q5 
Not the "tags on" part  <i> but only the "Tags off" part </i> is visible.

What is the encoding of the srt and what is the encoding setting on the himedia player?

[jeps]

.SRT encoding is ANSI
Normally I keep subtitles to "Auto" in the settings.

[Eriol]

.SRT encoding is ANSI
Normally I keep subtitles to "Auto" in the settings.

Could you try to change "Auto" for the correct encoding manually to see if the tags are still there?

[Icarium20]

Can anyone make any sense out of the following...
Total bollocks.

Thousands of people have followed the instructions without a problem.

Do you ever wonder if, perhaps, the 'bollocks' might be coming from yourself?!

I also believe the instructions could be made a lot clearer. Perhaps thousands of people have encourtered the PROBLEM and worked it through (the word 'copy to ' comes to mind ) and have not reported it, as other problems became more important once  whatever FW is finally installed.

You seem to beleive everyone on this forum is a tech genius. Believe me many are not,and have found the forum having bought the device and discovered it doesn't just work with a plug and play for KODI especially, but also for many other features to a greater degree than should be.

So fix, patch, workaround, extract and copy to,  etc are having to  become common vocabulary for these individuals which never was the case.

IMO some "Q10/5 PRO instructions for dummies" wouldn't go amiss and may be helpful. Perhaps a full time sticky thread so all  new members/ veiwers  know  where to go initially and probably find their solution there.

This post is here due to original thread post, not because of the subject topic,,

[futeko.com]

I also believe the instructions could be made a lot clearer. Perhaps thousands of people have encourtered the PROBLEM and worked it through (the word 'copy to ' comes to mind ) and have not reported it, as other problems became more important once  whatever FW is finally installed.

You seem to beleive everyone on this forum is a tech genius. Believe me many are not,and have found the forum having bought the device and discovered it doesn't just work with a plug and play for KODI especially, but also for many other features to a greater degree than should be.

So fix, patch, workaround, extract and copy to,  etc are having to  become common vocabulary for these individuals which never was the case.

IMO some "Q10/5 PRO instructions for dummies" wouldn't go amiss and may be helpful. Perhaps a full time sticky thread so all  new members/ veiwers  know  where to go initially and probably find their solution there.

This post is here due to original thread post, not because of the subject topic,,

We do our best to make something that is intrinsically difficult as easy as possible.

In an ideal world the updates from HiMedia would be much easier to handle. I think we've done well to avoid any mass bricking events bearing in mind the material we've had to work with.

The installation process and update path for 2.0.4 is complicated. If we over-simplified, it would encourage cavalier attempts at updating and potential product damage.

'copy to' isn't relevant for this update process. If we said 'extract update.zip to a local download location and then copy it to a USB flash drive' is that really simpler than 'Extract update.zip to the root of a FAT32 formatted USB pen drive'?

[Standard]

I've recently updated from 1.0.8 to 2.0.4, it's *the* patch I've been waiting for.

My videos that used to play with a black border, now fixed.
My 5.1 AAC videos that used to have no sound, now fixed.

Only 1 small issue, the player now seems to forget my resolution settings on restart. I set it at 2160p50, but when I restart the player it reverts to 1080i50.

Any ideas?

Also 1 quick question, back when I had 1.0.8 Kodi, the back button let me go up the directory structure. Now with 2.0.4 Krypton, the back button exits me to the top menu. I had a look at input configuration but couldn't figure it out.

[hanspampel]

Only 1 small issue, the player now seems to forget my resolution settings on restart. I set it at 2160p50, but when I restart the player it reverts to 1080i50.

This is a known issue since we had 2.0.0 or so. Still not fixxed.

Also 1 quick question, back when I had 1.0.8 Kodi, the back button let me go up the directory structure. Now with 2.0.4 Krypton, the back button exits me to the top menu. I had a look at input configuration but couldn't figure it out.

You have to disable joystick support in kodi. Goto Addons-->User-Addons-->Peripheral Library(or something else, dont know teh excactly word)-->Joystick Support and deactivate it.