•   
  • 1
  • 2
  • 3
  • 4(current)
  • 5
  • 6
  • 9
  •   
Raspberry Pi 4
#46
So weird, i've been waiting for a raspberry pi with 4k support for a year. So i went ahead and bought an s912 box. Just a mere DAY LATER this drops lmao
Reply
#47
(2019-06-25, 10:23)Klojum Wrote:
(2019-06-25, 09:21)solamnic Wrote: LOLOLOLOLOLOLOLOLOLOLOL

What else do you expect with only a limited number of developers, and the rest of the people picking their noses on the sidelines.

The delay is because RPi devs will implement it with V4L2/GBM. HDR support is still not in a stable kernel release to date. As such, things are in a state of flux, but the expectation would be that other vendors would follow this approach (intel, AML, Rockchip) to implement HDR in Kodi on Linux.

It is the correct approach and should solidify a unified standard for HDR so other hardware will have a foundation in the future as well.
Reply
#48
I'm sure there are technical and programming reasons for the HDR roadmap as it is, but the low number of developers should not be forgotten IMO.
It's not like Kodi can open a new can of developers, and expand the team.
Got a Kodi problem? Provide us with a full Debug log (wiki) || Usefull pages: First time user (wiki) || Troubleshooting (wiki) || Free content (wiki) || Forum rules (wiki) || VPN policy (wiki)
Reply
#49
(2019-06-25, 09:21)solamnic Wrote: "4K and HDR support expected on late 2020 - beginning of 2021...."

LOLOLOLOLOLOLOLOLOLOLOL

That is saying it won't appear in a stable release until Kodi v19 is done, which will likely land sometime next year going by the fact it's usually about a year between releases. If you are willing to run the nightly development builds then you will be able to get it a lot sooner than that, although exactly when is still highly uncertain.
Reply
#50
(2019-06-25, 10:23)Klojum Wrote:
(2019-06-25, 09:21)solamnic Wrote: LOLOLOLOLOLOLOLOLOLOLOL

What else do you expect with only a limited number of developers, and the rest of the people picking their noses on the sidelines. 
I am sorry but when something is advertised that supports 4K and HDR, i expect at least that there is software to support it.

Out there there are so many chineze Android Boxes that their specs look amazing but..... but.....
Reply
#51
atm
I rely on AppleTV 4K with MrMC for 4K and HDR playback...
Reply
#52
(2019-06-25, 18:54)solamnic Wrote: I am sorry but when something is advertised that supports 4K and HDR, i expect at least that there is software to support it.

It's not advertised as such. Your quote was from OSMC, which has no connection to the Pi Foundation

The Raspberry Pi is hardware device for developers. The hardware supports 4K and HDR, it's up to you to develop software (or find 3rd party developed software, like OSMC)
Reply
#53
I totally agree to this...

We have hardware that is capable of 4K HDR, and - again - there is no software to support it...

(i am only referring to the capabilities of R4 as a 4K HDR media player - not commenting its other uses)
Reply
#54
(2019-06-26, 20:39)solamnic Wrote: We have hardware that is capable of 4K HDR, and - again - there is no software to support it...

I still think you sound like you're nagging towards Kodi. Again. Smile
Got a Kodi problem? Provide us with a full Debug log (wiki) || Usefull pages: First time user (wiki) || Troubleshooting (wiki) || Free content (wiki) || Forum rules (wiki) || VPN policy (wiki)
Reply
#55
(2019-06-26, 21:12)Klojum Wrote:
(2019-06-26, 20:39)solamnic Wrote: We have hardware that is capable of 4K HDR, and - again - there is no software to support it...

I still think you sound like you're nagging towards Kodi. Again. Smile  
Nah... NEVER Smile
Drivers is the magic word Wink
Reply
#56
Just to update. If you are running LibreElec and want to try 4K/50-60 (aka 2160p50-60) video output you need to edit your config.txt to include 'hdmi_enable_4k=1', without this line you will be limited to 2160p30 and below in 4K.

Also, my Pi 4B is currently outputting RGB 8-bit in 2160p60 modes, which requires a higher bandwidth HDMI 2.0 input.  If your TV only supports 4:2:0 2160p50-60 inputs (as is particularly common with UHD SDR TVs sold in the early days) you won't be able to get 2160p50-60.  In a thread over at the Pi Forums there is a suggestion that 4:4:4/RGB and 4:2:2 are supported but 4:2:0 isn't currently (as it requires more processing for vertical subsampling).  

This may mean that the only mode supported for HDR at 2160p50-60 will be 4:2:2 12-bit (which can carry 10-bits padded - there isn't an HDMI 2.0 4:2:2 10-bit mode in the spec)  For 2160p30 and below 4:4:4/RGB are valid specs for 8-16 bit output, with 4:2:2 also supported for 12-bit (same as 2160p50-60) (4:2:0 isn't a valid output spec for 2160p30 and below)

(2160p50-60 4:2:0 8-bit was often the only HDMI 2.0 mode supported on early SDR UHD TVs as it didn't require the higher HDMI 2.0 bandwidth hardware and could use HDMI 1.4b bandwidth chipsets. This is how some manufacturers were able to offer an 'HDMI 2.0 upgrade' via a firmware update...)

The LibreElec image has a lot of rough edges at the moment, as would be expected for an Alpha, and this is only 3 days after launch.  So far in my tests 1080i h.264 isn't deinterlacing well, the GUI tearing is pretty noticeable, I'm not seeing HDMI 5.1/7.1 PCM audio output for FLAC multichannel stuff (Dolby Digital is bitstreaming OK) but HEVC hardware playback is good.  I also noticed that both LibreElec and Raspbian required HDMI to be used for reliable single display working. Using HDMI 1 on its own didn't seem reliable.
Reply
#57
(2019-06-27, 10:24)noggin Wrote: Just to update. If you are running LibreElec and want to try 4K/50-60 (aka 2160p50-60) video output you need to edit your config.txt to include 'hdmi_enable_4k=1', without this line you will be limited to 2160p30 and below in 4K.

Also, my Pi 4B is currently outputting RGB 8-bit in 2160p60 modes, which requires a higher bandwidth HDMI 2.0 input.  If your TV only supports 4:2:0 2160p50-60 inputs (as is particularly common with UHD SDR TVs sold in the early days) you won't be able to get 2160p50-60.  In a thread over at the Pi Forums there is a suggestion that 4:4:4/RGB and 4:2:2 are supported but 4:2:0 isn't currently (as it requires more processing for vertical subsampling).  

This may mean that the only mode supported for HDR at 2160p50-60 will be 4:2:2 12-bit (which can carry 10-bits padded - there isn't an HDMI 2.0 4:2:2 10-bit mode in the spec)  For 2160p30 and below 4:4:4/RGB are valid specs for 8-16 bit output, with 4:2:2 also supported for 12-bit (same as 2160p50-60) (4:2:0 isn't a valid output spec for 2160p30 and below)

(2160p50-60 4:2:0 8-bit was often the only HDMI 2.0 mode supported on early SDR UHD TVs as it didn't require the higher HDMI 2.0 bandwidth hardware and could use HDMI 1.4b bandwidth chipsets. This is how some manufacturers were able to offer an 'HDMI 2.0 upgrade' via a firmware update...)

The LibreElec image has a lot of rough edges at the moment, as would be expected for an Alpha, and this is only 3 days after launch.  So far in my tests 1080i h.264 isn't deinterlacing well, the GUI tearing is pretty noticeable, I'm not seeing HDMI 5.1/7.1 PCM audio output for FLAC multichannel stuff (Dolby Digital is bitstreaming OK) but HEVC hardware playback is good.  I also noticed that both LibreElec and Raspbian required HDMI to be used for reliable single display working. Using HDMI 1 on its own didn't seem reliable.

What about movie browsing speed in Libre?
using skins like nox
Reply
#58
It would be too nice if someone with a Raspberry 4 could check if it's playing 1080p within the Netflix addon.
Many thanks in advance...
Reply
#59
(2019-06-27, 16:04)C.O.D. Wrote: It would be too nice if someone with a Raspberry 4 could check if it's playing 1080p within the Netflix addon.
Many thanks in advance...

from @Sam.Nazarko on OSMC forum:

1080p Netflix is still out of reach in testing.
Reply
#60
(2019-06-27, 16:04)C.O.D. Wrote: It would be too nice if someone with a Raspberry 4 could check if it's playing 1080p within the Netflix addon.
It's all very early days. Initial testing was done with LibreELEC, sw decoding had a 2/3rd impact.
But there is a long list of to-do's, we're only 3 days after the launch.
Got a Kodi problem? Provide us with a full Debug log (wiki) || Usefull pages: First time user (wiki) || Troubleshooting (wiki) || Free content (wiki) || Forum rules (wiki) || VPN policy (wiki)
Reply
  •   
  • 1
  • 2
  • 3
  • 4(current)
  • 5
  • 6
  • 9
  •   
 
Thread Rating:
  • 3 Vote(s) - 3.67 Average



Logout Mark Read Team Forum Stats Members Help
Raspberry Pi 43.673