(2014-12-21, 15:45)Sunflux Wrote:

(2014-12-21, 15:38)fritsch Wrote:

(2014-12-21, 15:34)Sunflux Wrote: Hmm, interesting. Taking a screenshot of a 1920x800 file being played, it's actually occupying 1920x808? Thus why the doubled lines every 100 pixels in Nearest Neighbor? Properties in debug log show:

07:37:26 T:140159228024576 INFO: ffmpeg[7F795CFF9700]: Stream #0:0(eng): Video: h264 (High), yuv420p, 1920x800, SAR 1:1 DAR 12:5, 23.98 fps, 23.98 tbr, 1k tbn, 47.95 tbc (default)

07:37:32 T:140158590506752 NOTICE: fps: 23.976024, pwidth: 1920, pheight: 800, dwidth: 1920, dheight: 800
07:37:32 T:140158590506752 DEBUG: OutputPicture - change configuration. 1920x800. framerate: 23.98. format: VAAPI_NV12
07:37:32 T:140158590506752 NOTICE: Display resolution ADJUST : HDMI1: 1920x1080 @ 23.98Hz (22) (weight: 0.000)

And yet a screen capture clearly shows the viewable window as 808 pixels high:

http://i59.tinypic.com/20i6hl5.png

That seems way too much to account for the PAR error.

07:37:10 T:140160032450432 INFO: ID:0x48 Name:1920x1080 Refresh:60.000000 Width:1920 Height:1080
07:37:10 T:140160032450432 INFO: Pixel Ratio: 1.000512

1920 / 1.000512 = 1919,017463059

Yeah, teach your TV to behave better. For the 808 that's not an issue. It is centered and the rest of the surface is black, but the 1919 introduces a ratio change, rescaling and so on. You need the patch I posted above.

...And I just figured out what's causing the 808 pixel issue. Disabling the 1% allowable aspect ratio error fixes the vertical scaling. So it's a MANDATORY 1% error - enforced if it can be, no matter what..

So to fix a 1 pixel horizontal scaling issue, I'm expected to accept an 8 pixel vertical scaling issue? If the file's 1050 pixels high, that'll be an 11 pixel error! Gee. I do wish your "rounding error" fix would be made mainstream, because the alternate fix is worse than the problem!

Any way to simply override the screen's PAR without a complicated EDID replacement?

Quote:DisplaySize width height
This optional entry gives the width and height, in millimetres,
of the picture area of the monitor. If given this is used to
calculate the horizontal and vertical pitch (DPI) of the screen.

(2014-12-21, 15:51)fritsch Wrote: Hehe :-) Most likely, haha. You could try to experiment with "DisplaySize" in xorg.conf

Quote:DisplaySize width height
This optional entry gives the width and height, in millimetres,
of the picture area of the monitor. If given this is used to
calculate the horizontal and vertical pitch (DPI) of the screen.

In OE create /storage/.config/xorg.conf with something like that:

Edit also make sure your output is HDMI1 if not, change it to HDMI0 or HDMI2. xrandr -q will tell.

(2014-12-20, 22:08)nickr Wrote: Read the openelec web page particularly the warnings about backing up etc

Download the latest openelec tar file.

Transfer to your chromebox and put it in the directory /storage/.update

Reboot

(2014-12-21, 11:58)nolight Wrote: Hi, I recently installed dual boot Chrome OS/OpenELEC on Asus Chromebox with OpenELEC as default OS.

On my Sharp LCD TV LC-32M400M-BK (native resolution 1366x768) it is able to display the OpenELEC on boot up. Connection is direct HDMI.

On my Panasonic plasma TV TH42PV70H (native resolution 1024x768) it is showing up as if no signal. Tried both direct HDMI connection and HDMI connection through chromebox -> AVR -> TV.

Pls help on how I can fix the no display on Panasonic TV. Thanks.

(2014-12-21, 14:45)toadleyb Wrote: I just purchased the Asus Celeron Chromebox as a gift for someone for Christmas. I have Ubuntu and ChromeOS setup as dual boot.

I have a Logitech keyboard and mouse that I am having major issues with. I have no problem with the keyboard as far as selecting Ctrl D or Ctrl L but once I am booted into ChromeOS or Ubuntu the mouse and keyboard become completely unresponsive. The keyboard will work sometimes in Ubuntu but the mouse is unusable. This same mouse and keyboard work fine on my Home Theater Computer in the same room in both Windows and Ubuntu.

Is it worth me buying another Mouse and Keyboard and trying it or could it be an issue with the Chromebox. I do not own a wired mouse or keyboard to try (Can you even buy them anymore?).

Any troubleshooting tips?

(2014-12-21, 15:50)Jpopgt Wrote: Hello again,

I have followed the tutorial again on the first page and finished the setup and i still can't dual boot ChromeOS and OpenElec, when my machine boots up it is still on the 1 second boot option to boot into Chrome.

I must be missing something somewhere and can't figure out where i'm going wrong.

The only thing that i done different was remove the screw before i powered on the chromebox.....could this possibly be something to to with it?

Appreciate some help again.

cheers.

(2014-12-21, 20:04)paintmecyanide Wrote: Posting here because this script is among the top Google results for Chromebox Ubuntu.

The current version does not enable i386 by default. As a result, a number of packages will not install, particularly pipelight - needed to get Amazon Prime Video, among other things, working. This triggers errors that don't make it apparent that the problem is related to the architecture. This can be fixed, post install, by running the commands shown below.

sudo dpkg --add-architecture i386
sudo apt-get update

You might also want to consider not hard coding the Ubuntu version to "latest," and making Kodi installation optional. I am likely not the only person using this script as a starter for a general purpose Ubuntu box. I manually switched to lts, and deleted out Kodi while troubleshooting this problem, but they obviously ended up being unrelated.

(2014-12-21, 20:51)Matt Devo Wrote: If you're using it as dedicated Ubuntu box, just install from a Ubuntu ISO on a USB stick (after installing the coreboot firmware).
If you want to dual boot but don't want Kodi or the latest release, then use Jay Lee's ChrUbuntu script.
I've added i386 to the build script - thanks for the heads up

(2014-12-21, 21:01)paintmecyanide Wrote: Much appreciated. I wasn't sure what fixes were built in, nor was I sure of how to make sure I partitioned correctly and didn't make my system, or at the very least ChromeOS unbootable. The Kodi option and latest vs lts option were just things I stumbled upon while trying to fix my i386 issue. I had installed default Ubuntu using the script when I bought the Chromebox, and decided to test out pipelight. I then decided to start from scratch with xubuntu for performance reasons, and right off the bat, pipelight wasn't installable.

The reason I didn't use the Chrubuntu script is because when I initially bought the ChromeBox I ran into a large number of errors, and the script hasn't been updated in a long time.

(2014-12-21, 17:26)fritsch Wrote: OE RC3 will have that solved. So wait until that is released.

(2014-12-22, 07:50)waterskier1018 Wrote: Looking for some help on initial setup issues.
New stuff for me: Synology DS213j, WD Red 3TB's, Asus Chromebox M004U. All hardwired.

Goal to store and stream photos and videos to TV via Chromebox. Music and DVR via OTA comes later.

Completed: Device Prep, OpenELEC, Kodi install.

Issue 1: When trying to add files / folders to Kodi, all it sees on the DS213j are the "photos", "videos", and "music" folders, not the ones I created. How can I get it so see these? I selected UPnP Devices in the browse for new share menu. Is this right? Or am I not able to make my own folders? THe Samsung DLNA smart TV didn't see my folders either. Can I have spaces in my folder names?

Issue 2: Using UPnP method above (to get to a few test files in the "photo" folder), it won't play (or even see) my movie files. Filetypes are mts and mov. It was able to see the picture filenames, but didn't pull them up. jpegs.

Quote:Issue 3: Logitech K400r wireless keyboard didn't seem to allow me to press ctrl L to boot to openelec. I had a hardwired USB one that did. Can you recommend a low cost keyboard that may work?

Quote:Issue 4: Upon boot up, I don't get the developer screen on the TV (via HDMI). Just the default screen for no picture. Not sure if this is significant, as long as I remember to hit crtl-L quickly...

Thanks in advance, hope I can get this going, as the interface looks nice for sure.

(2014-12-21, 20:04)paintmecyanide Wrote: Posting here because this script is among the top Google results for Chromebox Ubuntu.

The current version does not enable i386 by default. As a result, a number of packages will not install, particularly pipelight - needed to get Amazon Prime Video, among other things, working. This triggers errors that don't make it apparent that the problem is related to the architecture. This can be fixed, post install, by running the commands shown below.

sudo dpkg --add-architecture i386
sudo apt-get update

You might also want to consider not hard coding the Ubuntu version to "latest," and making Kodi installation optional. I am likely not the only person using this script as a starter for a general purpose Ubuntu box. I manually switched to lts, and deleted out Kodi while troubleshooting this problem, but they obviously ended up being unrelated.