2013-11-17, 18:33
Nvm fixed
(2013-11-17, 07:24)lmyllari Wrote:(2013-11-17, 05:46)Clack Wrote: Ran it, rebooted, no luck.What's the output of those commands?
Then ran:
# sh /storage/.config/autostart.sh
# dmesg | tail -15
no luck.
btw, I really appreciate all your collective help with this. Wife won't be happy with me if I can't make it go..... :/
(2013-11-17, 20:12)Clack Wrote: I get:I think you have the script in DOS format instead of unix. Did you use the network share and a Windows text editor to create it?
OpenELEC (official) Version: 3.2.3
OpenELEC:~ # sh /storage/.config/autostart.sh
: not foundonfig/autostart.sh: line 2:
not found.ATAL: Module nuvoton-cir
/storage/.config/autostart.sh: line 4: can't create /sys/bus/acpi/devices/NTN053: nonexistent directoryurces
not found.ATAL: Module nuvoton-cir
: not foundonfig/autostart.sh: line 6:
(2013-11-18, 00:30)Clack Wrote:Quote:http://forum.xbmc.org/showthread.php?tid=176718
I think you have the script in DOS format instead of unix. Did you use the network share and a Windows text editor to create it?
You could try running vi/nano/whatever you're comfortable with on the NUC and cut'n'pasting into it.
Yes, I opened the network share on a windows machine and edited the script in notepad.
I'll give it a shot. Thanks for sticking with me
(2013-11-16, 07:41)lmyllari Wrote: Two options:Thank you lmyllari. I tried the test package you linked and setting #2 was the only one that gave me acceptable results. Much better! Excellent work!!
1) Full range output:, disable VA-API decodingCode:xrandr --output HDMI1 --set "Broadcast RGB" "Full"
2) Limited range output (with nightly):, disable VA-API decoding, set 16-235 range in system -> video and set limited range RGB from your TV/monitor. This gives the best quality (no banding in greyscale ramp, blacks and whites don't clip).Code:xrandr --output HDMI1 --set "Broadcast RGB" "Full"
(2013-11-18, 07:37)gamble Wrote: lmyllari, did u see my posting where i tried ur configurations, any word about it?Hi gamble,
Problem is for ME i see NO difference when disabling VA-API and set it to software decoding,
i now have 3.2.3 running with autostart set to Full-RGB and i get as opposed the crushed blacks,
but switching VA-API on/off makes no change for me...i even tried rebooting after disabling it...still no change...
And where in the XBMC Display Settings can i choose 16...235, i can not see that option...should be in the same menu as VA-API i guess...?
(2013-11-18, 08:12)lmyllari Wrote:(2013-11-18, 07:37)gamble Wrote: lmyllari, did u see my posting where i tried ur configurations, any word about it?Hi gamble,
Problem is for ME i see NO difference when disabling VA-API and set it to software decoding,
i now have 3.2.3 running with autostart set to Full-RGB and i get as opposed the crushed blacks,
but switching VA-API on/off makes no change for me...i even tried rebooting after disabling it...still no change...
And where in the XBMC Display Settings can i choose 16...235, i can not see that option...should be in the same menu as VA-API i guess...?
I saw your post but couldn't yet figure out what was going on. Can you clarify how changing the RGB range with xrandr works for you? Are you getting grey blacks with "Limited 16:235" and crushed blacks with "Full"?
The color problem doesn't seem to be with VA-API decoding itself, any path which uses bt.601 will show the same issue. Maybe take a look at xbmc log and see what the player says?
The 16..235 option is only in Gotham, but 16..235 didn't work reliably for me using VA-API. The way VA-API works I'm not optimistic that it can be implemented nicely.