Kodibuntu audio works fine out of the box. For desktop Audio you just install pulse audio, you then get audio in netflix steam ect.. But then lose hd audio or something like that. I don't use it so don't care.
No need for pulse, just configure the default alsa device to be hdmi, or wherever you want audio to go.
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.
i have an ipad air with kodi on it and on the same network as my chromebox i am able to load up and start watching a show way faster and NO buffering and using the same process on my chromebox, it is buffering and has issues with buffering? i will say that this does not happen every single time but my chromebox is wired direct to router and my ipad air is wireless and i have had them running side by side and the ipad will not buffer on the same tv show with the same episode and my chromebox will. i thought that the chromebox was supposed to be pretty quick? is there a setting or tweak that i can install/adjust to help speed it up? the kind of buffering is similar to my rasberry pi and its a fraction of what the chromebox is (it should be able to buffering faster than a rasberry pi shouldn't it?). I am a noob with the chromebox and perhaps i am missing something very simple. i am running single OS (ubuntu 14.10). thanks for any help in advance
(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.
As long as you don't want HD audio I guess.
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-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.
Steam doesn't seem to play very nice with Alsa. Plus installing pulse is a two command fix all. If you don't need hd audio.
@
matt Devo
You hit the nail right on the head!
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.
None of the options of my TV were enabled. I had it calibrated by a professional.
Only when playing a movie, the 24p SMOOTH FILM option shows it was set to MIN. This was the only option that was set.
I have now set it to MID and have even better results: no more the light flicker I always had when panning.
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.
This completely solved my problem of a little jerkiness when panning. You are a hero!
It even worked for my Raspberry Pi, actually taking away one of the main reasons I forked out 150 euro for the Chromebox (the other reasons are still valid). Butter smooth!
Quote:Also, you didn't mention what OS/version you are running - that might have an impact as well.
I am running the latest OpenElec 5.0.5 on Linux 3.17.8, freshly installed yesterday.
Thank you so much!
(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?
Did you check the part where it says something about power and CEC...http://kodi.wiki/view/Chromebox ?
(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"
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, 18:14)Rrrr Wrote: [ -> ]Did you check the part where it says something about power and CEC...http://kodi.wiki/view/Chromebox ?
Thanks!
I can't believe I hadn't seen that before. Powered USB hub for the CEC adapter and now it boots when the TV/AVR are turned on.
Now to get it to work when they're turned off.
Finally figured it out along with using a powered USB hub for the CEC adapter.
In autostart.sh I have added
Code:
echo -n "HDMI-A-1:edid.bin" > /sys/module/drm_kms_helper/parameters/edid_firmware
(
sleep 10
/bin/sh /storage/.config/hdmi-fix.sh
)&
/storage/.config/hdmi-fix.sh being:
Code:
#!/bin/sh
enabled="`cat /sys/class/drm/card0-HDMI-A-1/enabled`"
if [ "$enabled" = "disabled" ];
then
xrandr -display :0 --output HDMI1 --auto
sleep 1
systemctl restart xbmc
else
:
fi
There's probably a better way to do this (and I'd love to know!) but it seems to work for me from a cold boot with TV/AVR off.
(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
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-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
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.
(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.
well, the log you provided didn't show the issue you described. Obviously, if this were a widespread issue like the GPU hang bug (which this is not -- the fixes from the updated kernel have been backported into OE), there would be more users posting about it. kernel log: dmesg | pastebinit
I don't know why you'd assume that Kodibuntu wouldn't have the same audio issues as "regular" Ubuntu; you're very much likely to.