(2014-09-07, 00:14)c0mm0n Wrote: [ -> ]Burn, I mean put an iso on the key. You have another method ?
Went crazy with all the iso => usb thing, built a PXE server, so convenient.
I'm not following, why would you need to do this more than once? One USB key for initial OpenELEC install, and a 2nd for ChromiumOS to update the firmware via script as needed. OE updates are done either automatically or by simply copying the .tar file into the update folder over SMB
Once you have openelec installed you never have to write another USB stick.
(2014-09-07, 00:29)Matt Devo Wrote: [ -> ] (2014-09-07, 00:14)c0mm0n Wrote: [ -> ]Burn, I mean put an iso on the key. You have another method ?
Went crazy with all the iso => usb thing, built a PXE server, so convenient.
I'm not following, why would you need to do this more than once? One USB key for initial OpenELEC install, and a 2nd for ChromiumOS to update the firmware via script as needed. OE updates are done either automatically or by simply copying the .tar file into the update folder over SMB
I'm going for the ubuntu vaapi ppa, I need a stick to install ubuntu (or PXE)
(2014-09-07, 00:39)nickr Wrote: [ -> ]Once you have openelec installed you never have to write another USB stick.
Once you start testing and playing with such devices, you often need usb sticks for nightlys, custom builds, etc...
Pxe would certainly be useful for that. I can't find much that is helpful when Googling.
Why do you set "UseVC-1 VAAPI" to on? Writen in the wiki. Whats going on with the chromebox when i set this to off?
(2014-09-07, 06:35)magy77 Wrote: [ -> ]Why do you set "UseVC-1 VAAPI" to on? Writen in the wiki. Whats going on when i set this to off?
because I want hardware acceleration enabled for VC-1 encoded videos. Setting it to off forces software decoding for VC-1 content.
But then it sets interlaced to default right? Cant use deinterlaced anymore?!
(2014-09-07, 06:40)magy77 Wrote: [ -> ]But then it sets interlaced to default right? Cant use deinterlaced anymore?!
I'm not sure what the two have to do with each other. Enabling HW VC-1 decoding doesn't disable deinterlacing, not that you're likely to come across VC-1 encoded interlaced content.
(2014-09-07, 06:45)magy77 Wrote: [ -> ]http://forum.xbmc.org/showthread.php?tid=165707
Have a look at point 3. Do i understand this wrong?
those settings are valid only for that test version of XBMC which has hardware deinterlacing implemented (13.x does not). Enabling VC-1 won't cause you any issues, but it's not necessary either if you don't have any VC-1 content.
Nice to know. Thx for education.
(2014-09-07, 06:42)Matt Devo Wrote: [ -> ] (2014-09-07, 06:40)magy77 Wrote: [ -> ]But then it sets interlaced to default right? Cant use deinterlaced anymore?!
I'm not sure what the two have to do with each other. Enabling HW VC-1 decoding doesn't disable deinterlacing, not that you're likely to come across VC-1 encoded interlaced content.
Actually BBC release a lot of interlaced VC1 material on Bluray, so it is not completely uncommon.
(2014-09-07, 06:53)nickr Wrote: [ -> ]Actually BBC release a lot of interlaced VC1 material on Bluray, so it is not completely uncommon.
did not know that
My recommendation to enable stands (for now)
I disabled vc-1 by default cause the Intel driver just segfaulted with interlaced vc1. Nowadays intel gracefully returns and you end up with black screen while decoding. For progressive only content it should work correctly.
Can I update coreboot and bios from a regular Linux terminal or do I have to boot into chromium?