Login at Kodi Home

**patseguin** · (This post was last modified: 2014-07-14, 21:19 by patseguin.)

I've had the nVidia 640 in my htpc for some time now. In recent builds of OpenElec, I've been experiencing audio drop outs of a second or two on HD audio content. I do have the latest drivers installed. Would maybe upgrading to a 750 card solver my problem or maybe even an AMD card? Nobody on the OE forums or here have been able to offer an explanation and nobody has responded with the same problem. So, I wondered if maybe it was a faulty video card and if a newer architecture or even a switch to AMD would solve things. Any opinions?

Edit: marking it solved not because I knew what the issue was, but OE 4.0.7 seems to have fixed it and a mod sent me a link to a dev build and told me 4.0.7 would be fine. He was right!

FernetMenta · 2014-07-07, 18:15

AFAIK there has been some packaging issues with OE recently, i.e. upgrade of ALSA driver etc. I doubt that anything with your gfx is wrong or you would need anything with more power.

**patseguin** · 2014-07-07, 20:01

That's good to know. I wish the guys over at OE would have clued me into that instead of ognoringmy post.

**fritsch** · 2014-07-07, 20:09

try: http://snapshots.openelec.tv/test/OpenEL...64c4bc.tar better?

If not, return with a Debug Log please

**patseguin** · 2014-07-07, 20:59

(2014-07-07, 20:09)fritsch Wrote: try: http://snapshots.openelec.tv/test/OpenEL...64c4bc.tar better?

If not, return with a Debug Log please

I will try this when I get home. Is it a nightly?

**patseguin** · 2014-07-08, 13:43

Well, I installed that build last night and so far so good. It usually starts that way though so I'll report back later today or tomorrow. Was that just a nightly build that you posted for me?

**fritsch** · 2014-07-08, 14:09

Nope - that was a build which had the 4.0.6 ALSA bugs resolved.

**patseguin** · 2014-07-08, 15:47

Ah, what does ALSA stand for?

**fritsch** · 2014-07-08, 15:50

What does google stand for?

**patseguin** · (This post was last modified: 2014-07-08, 16:39 by patseguin.)

(2014-07-08, 15:50)fritsch Wrote: What does google stand for?

LMAO. Point taken.

Looks like it's a bus company. ;-)

http://en.wikipedia.org/wiki/ALSA_(bus_company)

Just kidding obviously, I saw in the next search thread that it means Advanced Linux Sound Architecture. Should I keep updating with nightlies and then 4.0.7 or just leave it alone? The only bug I've seen so far is when I selected TV shows, the screen went black and I saw a cursor and then XBMC relaunched and TV Shows opened fine after that. I watched a couple hours of TrueHD and no sound problems. I'm not sure if it was isolated to DTS-HD so I'll find some stuff in that and watch it. The good part is I've installed the OE and Windows variants so many times, I'm an expert and I can fully configure OE in less than 20 minutes including SQL and the skins/addons I want. Windows is a different story. XBMC is easy but I have to spend a super long time installing updates until it gets to 8.1 and current. That's why OE is so attractive to me.

**patseguin** · 2014-07-09, 20:55

(2014-07-08, 14:09)fritsch Wrote: Nope - that was a build which had the 4.0.6 ALSA bugs resolved.

I see that OE just released 4.0.7. Do you know if that incorporates this ALSA fix? They had this to say and I have no idea what it means or what to do:

alsa-utils: dont install default ALSA restore rule, to avoid overwriting our own mixer settings with default values. rename our udev rule to start after other default sound config rules. this should fix #3350, this should fix #3346

**fritsch** · 2014-07-09, 20:56

4.0.7 should work ALSA wise - but other packages were bumped without reason - not sure about further regressions. Install and find out.

**patseguin** · 2014-07-10, 15:54

OK I just don't understand their instructions regarding alsa-utils. There is no choice what to install when you install OE. Are they referring to some config or xml file that I have to edit? I ask here because nobody answers on their forums. Thanks!

**fritsch** · 2014-07-10, 15:54

Just use 4.0.7 and everything should be fine. This was broken in 4.0.6

**patseguin** · 2014-07-10, 15:55

Gotcha, thanks a ton.