(2015-03-01, 04:58)rodalpho Wrote: Pulse worked fine for me, with a bog-standard stock ubuntu install.

I went to the trouble of disabling pulse and using ALSA on my old HTPC back in the 2000s with XBMC, but it's really no longer necessary, pulse and Kodi play fine together now.

(2015-03-01, 00:06)nickr Wrote: No need for pulse, just configure the default alsa device to be hdmi, or wherever you want audio to go.

Quote:that sounds like shitty processing/frame interpolation from your TV -- turn of all of that crap. Google the model/series of your TV, and I'm sure one of the home theater sites will have a list of recommended settings for your model.

Quote:As far as Kodi settings, you probably want to select the option to change the refresh rate to match the video framerate (under Video/Playback - set to 'on start/stop'). The 2nd and 3rd screenshots on the wiki are from the video options accessible via the menu when a video is playing.

Quote:Also, you didn't mention what OS/version you are running - that might have an impact as well.

(2015-03-01, 15:05)ant_thomas Wrote: I've struggled for a while to get cold booting working correctly with my setup:

Chromebox - Pulse Eight HDMI CEC adapter - Onkyo TX-SR309 - Panasonic TX-P50ST60B

Running standalone firmware with OpenElec 5.0.5.

If I cold boot with the TV and Receiver on I don't get anything on the TV except a blue screen from the Onkyo receiver.
CEC adapter is also set to turn on TV/Receiver when OE/Kodi starts (which works great when suspending)
If I connect the TV directly to the Chromebox I can get it to boot fine, switch HDMI cables to the receiver, reboot and everything boots fine and suspend works fine.

Would dumping the EDID and having OpenElec/Intel driver load from that rather than try and fail to get the receiver EDID on boot?

I did previously have some sort of boot script that would restart OE until the HDMI port was seen as active, is this what I need?

Or is my receiver just an issue when it comes to HDMI handshaking?

(2015-02-23, 23:15)Matt Devo Wrote:

(2015-02-23, 16:33)pcdude Wrote: I recently switched my chromeboxes from dual-boot Ubuntu to standalone OpenELEC running OE 5.02. I am seeing the GPU hang problem on one of the boxes where the video freezes and the audio keeps playing. I've seen it happen twice now in the past 3 days. This is the same problem that I had in Ubuntu prior to upgrading the kernel. I thought this was fixed in OE. If not, is there a workaround outside of turning off hardware acceleration?

to quote fritsch, "logs or it didn't happen"

(2015-03-01, 18:14)Rrrr Wrote: Did you check the part where it says something about power and CEC...http://kodi.wiki/view/Chromebox ?

(2015-03-01, 18:17)pcdude Wrote:

(2015-02-23, 23:15)Matt Devo Wrote: to quote fritsch, "logs or it didn't happen"

This has been happening about once a day of continuous playing. It seems like the GPU hang problem where the video will stop while the audio keeps playing. The box seems responsive otherwise, as I can hear the menu sounds when the remote buttons are pressed. I upgraded to OpenELEC 5.0.4 and it hung again this morning. Log file posted:
http://pastebin.com/7ageePRJ

(2015-03-01, 21:59)Matt Devo Wrote: that log is from the playback of an xvid file (software decoding), and doesn't show any sort of video/GPU hang. Additionally, would need a kernel log as well -- both from when it happens, not after a reboot

(2015-03-02, 00:37)pcdude Wrote: The log was taken from the kodi.old.log file, which should have been the log when the problem occurred, not after reboot. How do you make a kernel log on OpenELEC?

When I experienced the GPU hangs on Ubuntu, I completely fixed it by updating the kernel. It ran for weeks without a hang. The symptoms were very similar. The hang would occur playing the same type of files. At this point I'm thinking about loading KodiBuntu with an updated kernel and see how that goes. I assume that the PulseAudio problems I had on Ubuntu will not be a problem on Kodibuntu.