(2016-03-29, 18:10)movie78 Wrote: All Done,The Intel NUC DN2820 going to be my ALL IN ONE KODI device, I am beginning to pull the plug of some on some of my devices.
Raspberry Pi2 ==Done
WeTek Core == Done
ZiDoo X5/6 Pro == Done
VidOn Box == Done

Still in service.
Minix NEO U1 == For BLURAY MENU Fonction with VidOn Kodi
ChromeBox == Still hanging in there until I complete the full migration to the Intel NUC

(2016-03-29, 22:44)dukester Wrote: anyone currently using a skin that supports atmos and dts:x flags that works with the latest 3D MVC windows test build?

(2016-03-30, 10:42)noggin Wrote: Isn't the big difference between the N2820 (Bay Trail Celeron) and the 2955U (Haswell Celeron) that the Bay Trails support 3D MVC whereas the Haswell Celerons don't?

AIUI 3D MVC decode functionality was limited to Core i3 and above Haswells, with Celerons and Pentium Core-based devices (Haswell etc.) not supporting it? I'm happy to be proved wrong - but ISTR that 3D decode was one of the platform differentiators to drive people to Core-i3 etc.

I totally agree that there is zero point switching from a Haswell Celeron to a Bay Trail Celeron unless you want to use the new 3D MVC decode that has appeared in Windows Kodi recently. However given that this is a 3D thread that may well be the reason?

(2016-03-30, 12:35)ArieS Wrote:

(2016-03-29, 22:44)dukester Wrote: anyone currently using a skin that supports atmos and dts:x flags that works with the latest 3D MVC windows test build?

I'm still trying to get my new NUC to work :\
But on my other HTPC, I use Aeon Madnox and it has support for Atmos/X flags. The best skin IMO

(2016-03-30, 14:00)Stereodude Wrote:

(2016-03-30, 10:42)noggin Wrote: Isn't the big difference between the N2820 (Bay Trail Celeron) and the 2955U (Haswell Celeron) that the Bay Trails support 3D MVC whereas the Haswell Celerons don't?

AIUI 3D MVC decode functionality was limited to Core i3 and above Haswells, with Celerons and Pentium Core-based devices (Haswell etc.) not supporting it? I'm happy to be proved wrong - but ISTR that 3D decode was one of the platform differentiators to drive people to Core-i3 etc.

I totally agree that there is zero point switching from a Haswell Celeron to a Bay Trail Celeron unless you want to use the new 3D MVC decode that has appeared in Windows Kodi recently. However given that this is a 3D thread that may well be the reason?

You are probably right. I'm pretty sure the Haswell Celeron hardware actually supports it. Intel just has disabled it in the Windows drivers, though I suppose they could have used efuses or laser cut traces to disable it at the chip level.

(2016-03-30, 21:59)wizziwig Wrote:

(2016-03-30, 14:00)Stereodude Wrote:

(2016-03-30, 10:42)noggin Wrote: Isn't the big difference between the N2820 (Bay Trail Celeron) and the 2955U (Haswell Celeron) that the Bay Trails support 3D MVC whereas the Haswell Celerons don't?

AIUI 3D MVC decode functionality was limited to Core i3 and above Haswells, with Celerons and Pentium Core-based devices (Haswell etc.) not supporting it? I'm happy to be proved wrong - but ISTR that 3D decode was one of the platform differentiators to drive people to Core-i3 etc.

I totally agree that there is zero point switching from a Haswell Celeron to a Bay Trail Celeron unless you want to use the new 3D MVC decode that has appeared in Windows Kodi recently. However given that this is a 3D thread that may well be the reason?

You are probably right. I'm pretty sure the Haswell Celeron hardware actually supports it. Intel just has disabled it in the Windows drivers, though I suppose they could have used efuses or laser cut traces to disable it at the chip level.

Intel didn't disable it in hardware. It's just a driver limitation in Windows. I tested setting frame-packed 3D 1080@24p output in Linux and it worked fine on the 2955U Chromebox. Based on their online database, they re-enabled it in Windows starting with the Broadwell Celerons like this one.

It's similar to the whole HD Audio passthrough issue where some chips work fine in Linux but not in Windows. No idea why Intel plays these games.

(2016-03-30, 22:03)noggin Wrote:

(2016-03-30, 21:59)wizziwig Wrote:

(2016-03-30, 14:00)Stereodude Wrote: You are probably right. I'm pretty sure the Haswell Celeron hardware actually supports it. Intel just has disabled it in the Windows drivers, though I suppose they could have used efuses or laser cut traces to disable it at the chip level.

Intel didn't disable it in hardware. It's just a driver limitation in Windows. I tested setting frame-packed 3D 1080@24p output in Linux and it worked fine on the 2955U Chromebox. Based on their online database, they re-enabled it in Windows starting with the Broadwell Celerons like this one.

It's similar to the whole HD Audio passthrough issue where some chips work fine in Linux but not in Windows. No idea why Intel plays these games.

Was it Frame Packed output or MVC decode that you checked? (Or is MVC decode done in software in Intel drivers rather than hardware?)

(2016-03-30, 23:12)noggin Wrote: I thought it was 3D MVC decode that wasn't supported not Frame Packed output. Had assumed that was possible on all the Intels.

(2016-03-30, 23:22)hdmkv Wrote: Thought Fritsch said Linux MVC decoder was like $5K. Forgetting which thread I read that in. Under Linux would be ideal w/OpenELEC.