[88keyz]

I am not too much interested in workarounds as the Firetv 4K worked flawlessly without any issues at all. They should fix their stuff. So now I have speedy menus but that's it, speedy menus with wrong colors.

Guess what outcry would happen if we would fuck up the colors that much here in kodi ...

Agreed.  Recently picked up a 2019 Cube to try and I have been very disappointed.  The device is quick, like really quick, but the BT.2020 colour space issues when attached to an AVR are unacceptable.  The device never switches to Rec. 709 when set to Adaptive Dynamic Range.  8-bit, Up to 10-Bit, Up to 12-bit, Auto Colour Space, RGB, YCbCr - all of them behave the same - SDR is output using the BT.2020 colour space.  When connected directly to the TV the issue isn't nearly as bad but its still there.  When connected to an AVR the colours are all sorts of wrong.  The Fire TV Stick 4K is a night and day difference with colour space switching that works and behaves properly.

Kodi (using latest fritschfiretv build) also doesn't seem to function correctly.  Skipped ahead or back causes most files to freeze up while the playback timer continues and audio seems to take a second or two to sync up and sometimes doesn't work at all requiring a stop/start of the file.  Haven't spent too much time trying to troubleshoot it because with the colour issues its not really worth the effort.

Raised a service ticket with Amazon Customer Service and after an hour or so of going back and forth they decided to escalate the colour space issue to the engineering team.  Said it would be a week or two before they heard back but they would update me via email once a response was received.  Hopefully they can reproduce the colour space issues, should be pretty easy, and fix them so that this becomes a serviceable Kodi device.  As is I wouldn't recommend it over the Fire TV Stick 4K.

[fritsch]

Thanks very much! Let's hope ... it's realy unbelievable ... I keep it currently to test it a bit more. After the CEC double presses, which I workarounded by setting the Control to TV instead of AVR ... let's hope.

[noggin]

I am not too much interested in workarounds as the Firetv 4K worked flawlessly without any issues at all. They should fix their stuff. So now I have speedy menus but that's it, speedy menus with wrong colors.

Guess what outcry would happen if we would fuck up the colors that much here in kodi ...

Agreed.  Recently picked up a 2019 Cube to try and I have been very disappointed.  The device is quick, like really quick, but the BT.2020 colour space issues when attached to an AVR are unacceptable.  The device never switches to Rec. 709 when set to Adaptive Dynamic Range.  8-bit, Up to 10-Bit, Up to 12-bit, Auto Colour Space, RGB, YCbCr - all of them behave the same - SDR is output using the BT.2020 colour space.  When connected directly to the TV the issue isn't nearly as bad but its still there.  When connected to an AVR the colours are all sorts of wrong.  The Fire TV Stick 4K is a night and day difference with colour space switching that works and behaves properly.

Kodi (using latest fritschfiretv build) also doesn't seem to function correctly.  Skipped ahead or back causes most files to freeze up while the playback timer continues and audio seems to take a second or two to sync up and sometimes doesn't work at all requiring a stop/start of the file.  Haven't spent too much time trying to troubleshoot it because with the colour issues its not really worth the effort.

Raised a service ticket with Amazon Customer Service and after an hour or so of going back and forth they decided to escalate the colour space issue to the engineering team.  Said it would be a week or two before they heard back but they would update me via email once a response was received.  Hopefully they can reproduce the colour space issues, should be pretty easy, and fix them so that this becomes a serviceable Kodi device.  As is I wouldn't recommend it over the Fire TV Stick 4K.

This isn't the issue we used to see with nVidia Shield TVs is it - prior to them offering a Rec 709 / Rec 2020 switch - when they used to output all Rec 709 or all Rec 2020?  

They used to correctly map Rec 709 into Rec 2020 colour space in SDR and output with a BT.1886 SDR EOTF flagged - which caused a lot of TVs to display somewhat differently to the same material output Rec 709 without an EOTF flagged, which the TVs then displayed with a Power Law Gamma (2.2-2.4) rather than a BT.1886 SDR EOTF (which is only power law for some of the range)

Or is this Rec 709 video output as Rec 709 - but flagged as Rec 2020 without any mapping? (i.e. the colours are so off as to be ridiculous with luminous greens and retina burning reds and oranges etc.)

(Rec 709 can be mapped perfectly well into Rec 2020 colour gamut - after all your TV has to do that to Rec 709 content to display it on a Rec 2020 display - however Rec 2020 has a properly specified SDR EOTF, whereas Rec 709 - and Rec 601 before it - didn't really.  This is very different to the reverse case - where you have to tone map wider gamut Rec 2020 content into the reduced gamut of Rec 709)

[fritsch]

I am not too much interested in workarounds as the Firetv 4K worked flawlessly without any issues at all. They should fix their stuff. So now I have speedy menus but that's it, speedy menus with wrong colors.

Guess what outcry would happen if we would fuck up the colors that much here in kodi ...

Agreed.  Recently picked up a 2019 Cube to try and I have been very disappointed.  The device is quick, like really quick, but the BT.2020 colour space issues when attached to an AVR are unacceptable.  The device never switches to Rec. 709 when set to Adaptive Dynamic Range.  8-bit, Up to 10-Bit, Up to 12-bit, Auto Colour Space, RGB, YCbCr - all of them behave the same - SDR is output using the BT.2020 colour space.  When connected directly to the TV the issue isn't nearly as bad but its still there.  When connected to an AVR the colours are all sorts of wrong.  The Fire TV Stick 4K is a night and day difference with colour space switching that works and behaves properly.

Kodi (using latest fritschfiretv build) also doesn't seem to function correctly.  Skipped ahead or back causes most files to freeze up while the playback timer continues and audio seems to take a second or two to sync up and sometimes doesn't work at all requiring a stop/start of the file.  Haven't spent too much time trying to troubleshoot it because with the colour issues its not really worth the effort.

Raised a service ticket with Amazon Customer Service and after an hour or so of going back and forth they decided to escalate the colour space issue to the engineering team.  Said it would be a week or two before they heard back but they would update me via email once a response was received.  Hopefully they can reproduce the colour space issues, should be pretty easy, and fix them so that this becomes a serviceable Kodi device.  As is I wouldn't recommend it over the Fire TV Stick 4K.

This isn't the issue we used to see with nVidia Shield TVs is it - prior to them offering a Rec 709 / Rec 2020 switch - when they used to output all Rec 709 or all Rec 2020?  

They used to correctly map Rec 709 into Rec 2020 colour space in SDR and output with a BT.1886 SDR EOTF flagged - which caused a lot of TVs to display somewhat differently to the same material output Rec 709 without an EOTF flagged, which the TVs then displayed with a Power Law Gamma (2.2-2.4) rather than a BT.1886 SDR EOTF (which is only power law for some of the range)

Or is this Rec 709 video output as Rec 709 - but flagged as Rec 2020 without any mapping? (i.e. the colours are so off as to be ridiculous with luminous greens and retina burning reds and oranges etc.)

(Rec 709 can be mapped perfectly well into Rec 2020 colour gamut - after all your TV has to do that to Rec 709 content to display it on a Rec 2020 display - however Rec 2020 has a properly specified SDR EOTF, whereas Rec 709 - and Rec 601 before it - didn't really.  This is very different to the reverse case - where you have to tone map wider gamut Rec 2020 content into the reduced gamut of Rec 709)

It's the ridiculous one :-).

[noggin]

Agreed.  Recently picked up a 2019 Cube to try and I have been very disappointed.  The device is quick, like really quick, but the BT.2020 colour space issues when attached to an AVR are unacceptable.  The device never switches to Rec. 709 when set to Adaptive Dynamic Range.  8-bit, Up to 10-Bit, Up to 12-bit, Auto Colour Space, RGB, YCbCr - all of them behave the same - SDR is output using the BT.2020 colour space.  When connected directly to the TV the issue isn't nearly as bad but its still there.  When connected to an AVR the colours are all sorts of wrong.  The Fire TV Stick 4K is a night and day difference with colour space switching that works and behaves properly.

Kodi (using latest fritschfiretv build) also doesn't seem to function correctly.  Skipped ahead or back causes most files to freeze up while the playback timer continues and audio seems to take a second or two to sync up and sometimes doesn't work at all requiring a stop/start of the file.  Haven't spent too much time trying to troubleshoot it because with the colour issues its not really worth the effort.

Raised a service ticket with Amazon Customer Service and after an hour or so of going back and forth they decided to escalate the colour space issue to the engineering team.  Said it would be a week or two before they heard back but they would update me via email once a response was received.  Hopefully they can reproduce the colour space issues, should be pretty easy, and fix them so that this becomes a serviceable Kodi device.  As is I wouldn't recommend it over the Fire TV Stick 4K.

This isn't the issue we used to see with nVidia Shield TVs is it - prior to them offering a Rec 709 / Rec 2020 switch - when they used to output all Rec 709 or all Rec 2020?  

They used to correctly map Rec 709 into Rec 2020 colour space in SDR and output with a BT.1886 SDR EOTF flagged - which caused a lot of TVs to display somewhat differently to the same material output Rec 709 without an EOTF flagged, which the TVs then displayed with a Power Law Gamma (2.2-2.4) rather than a BT.1886 SDR EOTF (which is only power law for some of the range)

Or is this Rec 709 video output as Rec 709 - but flagged as Rec 2020 without any mapping? (i.e. the colours are so off as to be ridiculous with luminous greens and retina burning reds and oranges etc.)

(Rec 709 can be mapped perfectly well into Rec 2020 colour gamut - after all your TV has to do that to Rec 709 content to display it on a Rec 2020 display - however Rec 2020 has a properly specified SDR EOTF, whereas Rec 709 - and Rec 601 before it - didn't really.  This is very different to the reverse case - where you have to tone map wider gamut Rec 2020 content into the reduced gamut of Rec 709)

It's the ridiculous one :-).

Wow... OK... That's a pretty major mistake to slip through testing...

[meccs]

What realistic speeds can I expect if I buy one of the USB 3.0 to Ethernet adapters with the AX88179 chipset (like the official one from Amazon)?

[noggin]

What realistic speeds can I expect if I buy one of the USB 3.0 to Ethernet adapters with the AX88179 chipset (like the official one from Amazon)?

I'm not sure that's an 'official' adaptor for Fire TV devices - it's just an Amazon branded one for laptops. That won't mean it doesn't work - but I wouldn't think of it as 'official'.  I think ~300Mbs is the ballpark that USB 2.0 connected USB 3.0/Gigabit adaptors deliver usually on these kind of devices (which is more than enough for streaming of UHD BD content that is losslessly ripped from the original discs)

[Vimes]

Using our Fire TV Cube I simply side loaded the vanilla Android Leia Kodi and took it from there. Noting this thread on the first page is states " latest fritschfiretv Kodi builds" and then the link. But I see no such builds listed...? Is there a separate build more applicable for the Cube...?

Thanks

[fritsch]

It's rotated away from the mirror - I don't plan to rebuild it, now that Leia is done and v19 beta was released -> focussing forward on v19.

[Vimes]

ah thanks for that. So if and when and Cube / Fire TV focussed builds get released they will be made with Matrix.

Installed Beta 1 of Matrix and it seems that I might no longer need the audio offset for lip sync.

[fritsch]

Everything fritschfiretv had is now in kodi's master and available via the v19 beta.

[Vimes]

We are pleased with how much better it seems worth lip sync, audio pass through, no clicks or noises or failing to play audio.
So far it has been great.
Thanks, and....

Thanks to the team for a good job 👍

[fbi1970]

Everything fritschfiretv had is now in kodi's master and available via the v19 beta.

Should we download the test build marked with AFTV4K in name (/test-builds/android/arm/kodi-20201122-9268af39-matrix-wsnipex-aftv4k-armeabi-v7a.apk) or the standard beta1 (/releases/android/arm/kodi-19.0-Matrix_beta1Android-armeabi-v7a.apk)?

Thanks

[Vimes]

Running fine it seems on the Cube, that is Beta 1 Kodi 19. Has the refresh rate switching been disabled due to this I read in the Firestick thread...

If you change refreshrate, the hdmi edid information is shortly lost and when display comes back it's resynced. Certain devices (AVRs, streaming sticks) have issues with that. As they don't properly return connected after the edid information is back. That's the background why it directly influences audio.

Therefore: Disable refreshrate switching and try again.

Rather than being able to select it, it simply no longer works.

Thanks

@fbi1970 I am running the official Beta 1 Matrix fine on my Cube and also a 4k Firestick

[arbee0729]

Is this built (releases/android/arm/kodi-19.0-Matrix_beta2-armeabi-v7a.apk) works also fine on new Cube since I can not find the fritschfiretv builts?