[sheva7]

Hi guys,

I am planning to build a HTPC that will be able to play full HD with HD Audio 7.1 smoothly. I'd like it to be future-proof also, e.g. 4K support etc.

For this, I am thinking to get the new Haswell-based i5 NUC (D54250WYK).
From what I understand, the requirements above can be fulfilled by this small but powerful box. Please correct me if this is not right.

The setup that I have in mind:

The NUC is connected to my Samsung Blu-Ray Home Theatre System via HDMI (and the Home Theatre System is connected to my TV via HDMI).
The NUC will be connected to my router via Gigabit Ethernet cable, which will connect to my PC, where my media files are stored.

I am planning to use XBMC for the media centre software. However, I am not sure if I should install Windows in the NUC or just run off OpenELEC from a USB stick.

If I am to install Windows, I believe I need to buy mSATA SSD drive, which at the moment quite pricey..
On the other hand, I read that if running OpenELEC from a USB stick, it can be slow in loading the artworks graphics, etc. Is that right?

This is where I need your advice and suggestions because I am really new to HTPC world.

Thank you heaps in advance.

Cheers

EDIT zag: Please read the wiki here for more info on the NUC hardware

http://wiki.xbmc.org/index.php?title=Intel_NUC

Power usage
StandBy: 1,2W
Power Off: 0,6W
Default Theme: about 6W-7W with short spikes up to 33W on Win 8.1 and OpenElec spikes up to 22W.
Aeon Nox: about 6W-7W with short spikes up to 33W on Win 8.1 and OpenElec.
Playback: about 8W to 9W on Win 8.1 and around 8W on OpenElec.

Boot problems
If you cant get into the bios then maybe your monitor is not displaying the boot option screen. It needs to support a full resolution. They key is F2 to enter the bios.

Booting from a USB3 stick has problems. Use a USB2 stick for now.

Latest Bios
https://downloadcenter.intel.com/Detail_...dType=BIOS

Changing settings in the bios sometimes crashes with the keyboard. Its better to use the mouse.

HD Audio problems
If "Adjust display refresh rate to match video" is enabled in the System -> Video Settings, HD-Sound doesn´t work any more.

Windows 8 Notes
none yet...

Windows 7 Notes
none yet...

Mint + Ubuntu

Mint Install guide

Mint and Ubuntu both have issues with UEFI. The files simply aren't in the right directory after install for some reason. Fixing this was easy for me, I found a GRUB rescue distro that I put on a USB stick. After install I run this and it does a reinstall of GRUB which puts the files in the right place - problem solved. I'll try to lookup the name of this distro when I'm home, google is how I found it but I'm not finding it again as easily right now.

If this is too hard then I'd suggest Openelec. The UEFI boot is no issue, the video is fine, sound just works without having to update to an ALSA bleeding edge, and issues are being worked out quickly. The cost is certainly right and it boots quickly! The way the shares are setup makes updating and configuring it really easy too.

OpenSUSE

I have the IR device working on opensuse 13.1. I discovered reading an intel forum (https://communities.intel.com/message/216302) that the BIOS has the device disabled after it is enabled. The solution posted was to do the following at boot time on Linux. I put these commands in the /etc/rc.d/boot.local file and IR started working.

modprobe -r nuvoton-cir
echo "auto" > /sys/bus/acpi/devices/NTN0530:00/physical_node/resources
modprobe nuvoton-cir

Openelec Notes

Download: Frodo Stable - http://openelec.tv/get-openelec/download...tel-builds
Download: Gotham Nightly - http://sources.openelec.tv/tmp/image/

Colour problems:

The banding comes from expanding luma from 16-235 to 0-255. This is done for typical PC monitors, which expect a full range signal. New Intel linux drivers by default give TVs a limited range signal, taking the expanded 0-255 and scaling it to 16-235. This does not eliminate the banding that was created by the original expansion, and original information below 16 and above 235 was already lost in that same step. (Why do they do it? It's the right thing according to the standards, and some TVs don't like full range -> crushed blacks.)

If the player software (xbmc in this case) decodes to 16-235 (meaning "don't change luminance, keep black at 16 and white at 235"), the video card outputs full range 0-255 (meaning "don't scale the levels, just output what you're given"), and display is set to limited range input (meaning "16 is black, 235 white"), we eliminate the banding in greyscale ramp (because the range is not scaled at any point) and keep blacker-than-black (luma values under 16) and white-than-white (luma values above 235).

If your plasma defaults to limited range RGB (and doesn't listen to the infoframes in the HDMI stream) or you can set limited range manually, you don't need anything special. Just set your player software to 16-235 (which you can now do with Gotham and software decoding) and make sure the video card doesn't change the signal (the xrandr broadcast range "Full" setting mentioned a lot in this thread). In my case, the monitor obeys the infoframes (and there are other devices connected to the same input preventing a manual setting), so I need a patch to switch it to limited range without altering the video signal.

Remote:

SSH to openelec box and type:

cd /storage/.config
touch autostart.sh
chmod 0777 autostart.sh
nano autostart.sh


# IR fix
modprobe -r nuvoton-cir
echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources
modprobe nuvoton-cir

Suspend/shutdown Problems in Linux

Turn off "Wake on Lan" in the bios to prevent any shutdown problems