• 1
  • 13
  • 14
  • 15(current)
  • 16
  • 17
  • 29
OSMC announced new Vero4k, opinions?
What's posted there is quite recent. Use of ppmgr seems to be completely removed in v18. In theory, it can be re-added, but this may be subject to change.
Reply
(2018-03-12, 01:45)TheShoe Wrote: is 3D still coming? recent posts at osmc seem to indicate because the work would be undone by kodi18 that it is now dead. that is a shame if so.
Why not release for Kodi 17 while working on a new solution for 18? It was more than teased as coming.
Reply
(2018-03-12, 02:48)hdmkv Wrote:
(2018-03-12, 01:45)TheShoe Wrote: is 3D still coming? recent posts at osmc seem to indicate because the work would be undone by kodi18 that it is now dead. that is a shame if so.
Why not release for Kodi 17 while working on a new solution for 18? It was more than teased as coming. 
 Agreed, this is the reason I went with the Vero 4K.
Box 1: ODroid N2+ 4GB
Box 2: Intel NUC D34010WYK (Windows afedchin's Krypton MVC Build)
Box 3: Vero 4K
RIP schimi2k | I miss you buddy :(
Reply
(2018-03-12, 11:07)ArieS Wrote:
(2018-03-12, 02:48)hdmkv Wrote:
(2018-03-12, 01:45)TheShoe Wrote: is 3D still coming? recent posts at osmc seem to indicate because the work would be undone by kodi18 that it is now dead. that is a shame if so.
Why not release for Kodi 17 while working on a new solution for 18? It was more than teased as coming. 
 Agreed, this is the reason I went with the Vero 4K.

putting it on ebay if this is the case.

sam - please be upfront and honest here. it is a fine device. but i invested because you personally said it was coming. i have no need for it otherwise
Reply
(2018-03-10, 17:58)Sam.Nazarko Wrote: As always: thanks for the review and feedback. We'll keep supporting and improving this device with regular updates for a long time yet.

Sam
Nicely thought out additions and extra usability features you have implemented there Sam on the Vero 4K. So good I had to borrow some of them for the LE C2 Wink

In reality all you need for most 4K HDR users, ones without restricted 4:2:2 only projectors is a Kodi GUI user setting of 444,10bit or 444,12bit
I'm already using a Kodi GUI user selectable 422,10bit on the LE U9 with the newer AML Linux Kernel.

HERE is the patch I'm originally using for Kodi Krypton GUI colorspace settings.
Note I cannot get the various 444,10bit options to string parse properly in Krypton. I end up with a greyed out Krypton user settings option.
You may have more luck and skills to spot an obvious error.

Reply
(2018-03-14, 02:42)wrxtasy Wrote: Nicely thought out additions and extra usability features you have implemented there Sam on the Vero 4K. So good I had to borrow some of them for the LE C2 Wink

In reality all you need for most 4K HDR users, ones without restricted 4:2:2 only projectors is a Kodi GUI user setting of 444,10bit or 444,12bit
I'm already using a Kodi GUI user selectable 422,10bit on the LE U9 with the newer AML Linux Kernel. 

Hi wrxtasy. Can you please point me to the LE U9 build mentioned above. THX
Reply
https://forum.libreelec.tv/thread/5848-8...#post84350

Works really well. Excellent work by @wrxtasy.
Reply
(2018-03-14, 02:42)wrxtasy Wrote:
(2018-03-10, 17:58)Sam.Nazarko Wrote: As always: thanks for the review and feedback. We'll keep supporting and improving this device with regular updates for a long time yet.

Sam
Nicely thought out additions and extra usability features you have implemented there Sam on the Vero 4K. So good I had to borrow some of them for the LE C2 Wink

In reality all you need for most 4K HDR users, ones without restricted 4:2:2 only projectors is a Kodi GUI user setting of 444,10bit or 444,12bit
I'm already using a Kodi GUI user selectable 422,10bit on the LE U9 with the newer AML Linux Kernel.    
 Glad to hear these improvements are beneficial for other users.

We'll fix the green screen issue imminently. but the newer AML drop will lead to disappointments for some users I suspect. While I haven't followed LE community builds in detail, I wouldn't be surprised if they revert back based on our internal evaluation. It's completely unsuitable for HDR, which is probably enough alone to warrant not using it. 

Sam
Reply
@Sam.Nazarko : Do you know whether the below statement from narmstrong is correct. If it is, it may explain the banding/flicker issues that some users have reported.
 
Quote:Found the relevant quote from @narmstrong at Baylibre:
S912 has a 10bit pipeline, s905x has only a 8bit to 10bit converter right before the hdmi controller
https://forum.libreelec.tv/thread/9759-c...#post84351
Reply
I think Neil refers to P_VPU_HDMI_FMT_CTRL, which is used to control rounding and dithering. As you can see from [1] the values are different for GXL and GXM.
Both S912 and S905x will obviously engage 10-8bit dithering when CD is < 10-bit.

12-10 bit dithering is used on S912, but not on S905x. It's unknown if this works properly yet.

We fixed flickering but now we get banding. I have added [2] so we can now poke the regs during playback and see how we can improve this.
With [3], we should also now be able to decouple the colour space and HDR output (which has been a mistake from AMLogic for some time).

We have to poke at some of this because the docs either aren't there; or contradict some of our experiences.

[1] https://github.com/osmc/vero3-linux/blob...hw.c#L1975
[2] https://github.com/osmc/vero3-linux/comm...f273aec6b6 
[3] https://github.com/osmc/vero3-linux/comm...2524149d29
Reply
Hey guys sorry for that basic question, but I don't find a simple answer to that:
Does OSMC run a Kodi fork or the "normal" Kodi? So will I be able to use all addons and skins I can use in Kodi, too? (aside from performance limitations given by the hardware)
Reply
afaik and use... is the "normal" kodi 
Code:
20:44:57.481 T:4075270736  NOTICE: Starting Kodi (17.6). Platform: Linux ARM (Thumb) 32-bit
20:44:57.481 T:4075270736  NOTICE: Using Release Kodi x32 build (version for Vero)
20:44:57.481 T:4075270736  NOTICE: Kodi compiled Mar 12 2018 by GCC 6.3.0 for Linux ARM (Thumb) 32-bit version 4.9.30 (264478)
20:44:57.481 T:4075270736  NOTICE: Running on Open Source Media Center 2018.03-2, kernel: Linux ARM 32-bit version 3.14.29-69-osmc
20:44:57.481 T:4075270736  NOTICE: FFmpeg version/source: ffmpeg-3.1-kodi
20:44:57.481 T:4075270736  NOTICE: Host CPU: AArch64 Processor rev 4 (aarch64), 4 cores available
20:44:57.481 T:4075270736  NOTICE: ARM Features: Neon disabled
20:44:57.481 T:4075270736  NOTICE: special://xbmc/ is mapped to: /usr/share/kodi
20:44:57.481 T:4075270736  NOTICE: special://xbmcbin/ is mapped to: /usr/lib/kodi
20:44:57.482 T:4075270736  NOTICE: special://xbmcbinaddons/ is mapped to: /usr/lib/kodi/addons
20:44:57.482 T:4075270736  NOTICE: special://masterprofile/ is mapped to: /home/osmc/.kodi/userdata
20:44:57.482 T:4075270736  NOTICE: special://envhome/ is mapped to: /home/osmc
20:44:57.482 T:4075270736  NOTICE: special://home/ is mapped to: /home/osmc/.kodi
20:44:57.482 T:4075270736  NOTICE: special://temp/ is mapped to: /home/osmc/.kodi/temp
20:44:57.482 T:4075270736  NOTICE: special://logpath/ is mapped to: /home/osmc/.kodi/temp
20:44:57.482 T:4075270736  NOTICE: The executable running is: /usr/lib/kodi/kodi.bin
20:44:57.482 T:4075270736  NOTICE: Local hostname: osmc
20:44:57.482 T:4075270736  NOTICE: Log File is located: /home/osmc/.kodi/temp//kodi.log

BHH
HDConvertToX, AutoMKV, AutoMen author
Reply
Same add-ons / skins etc. The only slightly more limiting factor is screensavers / visualisations as we have a GLES windowing system.
Reply
Is 3D effort dead?
Reply
(2018-03-22, 00:52)hdmkv Wrote: Is 3D effort dead?
 Not that I recall?
Reply
  • 1
  • 13
  • 14
  • 15(current)
  • 16
  • 17
  • 29

Logout Mark Read Team Forum Stats Members Help
OSMC announced new Vero4k, opinions?4