(2013-11-23, 06:08)merlinn31 Wrote: So apparently Windows doesn't do well with NFS, but I should have known that. I switched to SMB and a hardwire link and it's definitely more tolerable and actually plays all my files, but still takes a good 10-20 seconds to begin playing them. Sometimes 30 seconds. This is on an unsaturated 1Gbps link. The Boxee plays the same movie wirelessly (N) in less than 5 seconds. It's weird too because sometimes I'll play a movie and it will insta-play on XBMC. Sometimes I'll play the same movie later and it will take the standard 10-30 seconds to start. VLC plays the same movie immediately. Once it starts playing it plays fine.

Is this a NUC issue, an XBMC issue, or a user issue?

(2013-11-23, 17:48)solamnic Wrote:

(2013-11-23, 17:33)mushoss Wrote: I just purchased an i3 NUC Haswell from Newegg (through ebay) for $256.49. Newegg had it for $284.89. Ebay had sent me a 10% off coupon for purchases through their mobile app. It was good through today so I pulled the trigger. Now I need to nail down which RAM to purchase, thinking of going with Crucial 8 gb. Will this work http://www.ebay.com/itm/251336690182 Also need to get a wi-fi / blue tooth any recommendations on that.

4GB 204-Pin SoDIMM DDR3 PC3-12800 • CL=11 • Unbuffered • NON-ECC • DDR3-1600 • 1.35V • 512Mx64 • 2Rx8

ram is ok

(2013-11-23, 18:13)joelbaby Wrote:

(2013-11-23, 17:33)mushoss Wrote: which RAM to purchase, thinking of going with Crucial 8 gb.

8Gb is overkill. You could just get a 4Gb stick and save $40. As someone already pointed out, make sure it is 1.35V . Sometimes it says DDR3L (L means low voltage).

(2013-11-23, 19:39)mushoss Wrote: I am confused someone please help. I am being told 4gb of ram is enough, get 1.35v etc. But when I search it comes up with single sticks at 4 gb, or 2 sticks at 2 gb. Could someone please give me a link to the crucial 4gb RAM that i can use, preferably on ebay.

(2013-11-23, 19:39)mushoss Wrote:

(2013-11-23, 17:48)solamnic Wrote:

(2013-11-23, 17:33)mushoss Wrote: I just purchased an i3 NUC Haswell from Newegg (through ebay) for $256.49. Newegg had it for $284.89. Ebay had sent me a 10% off coupon for purchases through their mobile app. It was good through today so I pulled the trigger. Now I need to nail down which RAM to purchase, thinking of going with Crucial 8 gb. Will this work http://www.ebay.com/itm/251336690182 Also need to get a wi-fi / blue tooth any recommendations on that.

4GB 204-Pin SoDIMM DDR3 PC3-12800 • CL=11 • Unbuffered • NON-ECC • DDR3-1600 • 1.35V • 512Mx64 • 2Rx8

ram is ok

(2013-11-23, 18:13)joelbaby Wrote:

(2013-11-23, 17:33)mushoss Wrote: which RAM to purchase, thinking of going with Crucial 8 gb.

8Gb is overkill. You could just get a 4Gb stick and save $40. As someone already pointed out, make sure it is 1.35V . Sometimes it says DDR3L (L means low voltage).

I am confused someone please help. I am being told 4gb of ram is enough, get 1.35v etc. But when I search it comes up with single sticks at 4 gb, or 2 sticks at 2 gb. Could someone please give me a link to the crucial 4gb RAM that i can use, preferably on ebay.

(2013-11-23, 19:35)arokh Wrote: gamble did you check if HD audio is working for you if you set 23.98 refresh in GUI? Works every time here, I think there's some bug triggered if you're on 60Hz and XBMC changes refresh before playing the movie.

(2013-11-23, 19:35)arokh Wrote: gamble did you check if HD audio is working for you if you set 23.98 refresh in GUI? Works every time here, I think there's some bug triggered if you're on 60Hz and XBMC changes refresh before playing the movie.

(2013-11-23, 19:36)furii Wrote:

(2013-11-23, 06:08)merlinn31 Wrote: So apparently Windows doesn't do well with NFS, but I should have known that. I switched to SMB and a hardwire link and it's definitely more tolerable and actually plays all my files, but still takes a good 10-20 seconds to begin playing them. Sometimes 30 seconds. This is on an unsaturated 1Gbps link. The Boxee plays the same movie wirelessly (N) in less than 5 seconds. It's weird too because sometimes I'll play a movie and it will insta-play on XBMC. Sometimes I'll play the same movie later and it will take the standard 10-30 seconds to start. VLC plays the same movie immediately. Once it starts playing it plays fine.

Is this a NUC issue, an XBMC issue, or a user issue?

sounds like whatever you're trying to play is on a spun down server. does it take as long to start if you stop the movie and restart it?

(2013-11-23, 21:31)lmyllari Wrote:

(2013-11-23, 19:35)arokh Wrote: gamble did you check if HD audio is working for you if you set 23.98 refresh in GUI? Works every time here, I think there's some bug triggered if you're on 60Hz and XBMC changes refresh before playing the movie.

I think you're onto something.

I set my GUI to 60Hz and disabled mode switching to avoid any switches, and HD audio seems stable.


edit: still something weird - 5.1ch PCM gets sent as 7.1 to the receiver. If I set xbmc to 5.1 output, I get crackling output.

(2013-11-23, 18:19)lmyllari Wrote: Another build? In addition to the one in my post above?

(2013-11-23, 21:31)lmyllari Wrote: edit2: 23.976 works too. I can actually start the playback, go to settings and switch refresh rates and the audio keeps playing fine after the mode is switched. Maybe it is a timing issue opening audio while switching modes.

(2013-11-23, 23:23)arokh Wrote: Wasn't there someone here who didn't have this issue? What kind of AVR do you have and which output are you using? HDMI/DP

(2013-11-23, 18:04)lmyllari Wrote: I did some patching based on the recent developments. You can see my work at https://github.com/laurimyllari/OpenELEC.tv/commits/va-intel-on-master

I took the VA-API colorspace fixes from staging. This should fix both SD and HD colorspace issues. I've only tried HD, but that seems good. I'll need to find some SD test material.

I made a small patch to kernel based on Ville's advice to fix the black levels in limited range output. I also implemented a pass-through mode for use with sw decoding and 16:235 range in xbmc.

These should fix the grey blacks and inaccurate colors. There are three ways to configure:

1) GPU scaled limited range output: This is the default setting when connected to a TV. There is no need for any settings - remove xrandr from Autostart.sh to use this.

2) Full range output: This is the default when connected to a computer monitor. This can also be forced with the xrandr setting in Autostart.sh.

Image should look identical between #1 and #2. If the screen supports switching RGB input ranges, both should be signaled automatically - otherwise #2 is used. Leave everything at default and things should work right automatically.

There is another way for better quality:

3) Direct limited range output: This allow for BtB, WtW and avoids banding. Software decoding needs to be used (VA-API output is first clipped and scaled to full range). Configure xbmc for 16-235 output and no hardware decoding. Use xrandr to set "Broadcast RGB" to "Video 16:235 pass-through" (this allows full range output, but tells the screen content is limited range)


There is a build based on recent OE master (with Gotham) at https://www.dropbox.com/s/s4cqdn8vh324cpf/OpenELEC-Generic.x86_64-devel-20131123070845-r16417.tar

If you still see black level problems with this build, please post numbers and details ( you can follow instructions at http://forum.xbmc.org/showthread.php?tid=176718&pid=1555766#pid1555766 )

(2013-11-24, 03:52)Ravetrancer Wrote:

(2013-11-23, 18:04)lmyllari Wrote: I did some patching based on the recent developments. You can see my work at https://github.com/laurimyllari/OpenELEC.tv/commits/va-intel-on-master

I took the VA-API colorspace fixes from staging. This should fix both SD and HD colorspace issues. I've only tried HD, but that seems good. I'll need to find some SD test material.

I made a small patch to kernel based on Ville's advice to fix the black levels in limited range output. I also implemented a pass-through mode for use with sw decoding and 16:235 range in xbmc.

These should fix the grey blacks and inaccurate colors. There are three ways to configure:

1) GPU scaled limited range output: This is the default setting when connected to a TV. There is no need for any settings - remove xrandr from Autostart.sh to use this.

2) Full range output: This is the default when connected to a computer monitor. This can also be forced with the xrandr setting in Autostart.sh.

Image should look identical between #1 and #2. If the screen supports switching RGB input ranges, both should be signaled automatically - otherwise #2 is used. Leave everything at default and things should work right automatically.

There is another way for better quality:

3) Direct limited range output: This allow for BtB, WtW and avoids banding. Software decoding needs to be used (VA-API output is first clipped and scaled to full range). Configure xbmc for 16-235 output and no hardware decoding. Use xrandr to set "Broadcast RGB" to "Video 16:235 pass-through" (this allows full range output, but tells the screen content is limited range)


There is a build based on recent OE master (with Gotham) at https://www.dropbox.com/s/s4cqdn8vh324cpf/OpenELEC-Generic.x86_64-devel-20131123070845-r16417.tar

If you still see black level problems with this build, please post numbers and details ( you can follow instructions at http://forum.xbmc.org/showthread.php?tid=176718&pid=1555766#pid1555766 )

the dropbox link doesnt work

(2013-11-23, 19:57)aesalazar Wrote:

(2013-11-23, 19:39)mushoss Wrote: I am confused someone please help. I am being told 4gb of ram is enough, get 1.35v etc. But when I search it comes up with single sticks at 4 gb, or 2 sticks at 2 gb. Could someone please give me a link to the crucial 4gb RAM that i can use, preferably on ebay.

I put 2 of these in mine:

http://www.rakuten.com/prod/crucial-4gb-ddr3-sdram-memory-module-4-gb-ddr3-sdram-1600-mhz-ddr3/223775933.html