Bug 573 (Befriend28) - Problem I keep getting buffer overflow when I try to get sound from mythTV
Summary: Problem I keep getting buffer overflow when I try to get sound from mythTV
Status: RESOLVED INVALID
Alias: Befriend28
Product: Fedora
Classification: Unclassified
Component: mythtv (show other bugs)
Version: 10
Hardware: i386 GNU/Linux
: P3 normal
Assignee: Jarod Wilson
URL:
Depends on:
Blocks:
 
Reported: 2009-04-25 14:34 CEST by Dennis Appelon Nielsen
Modified: 2011-05-24 16:33 CEST (History)
0 users

See Also:
namespace:


Attachments
Frontend logfiles (30.86 KB, application/octet-stream)
2009-04-25 14:34 CEST, Dennis Appelon Nielsen
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Dennis Appelon Nielsen 2009-04-25 14:34:02 CEST
Created attachment 169 [details]
Frontend logfiles

I use a SBLive 1024 card and the ALSA driver stack. MythTV configured like this

Sound Device ALSA:default

Pass though: none

Aggressive sound buffering unchecked

Extended sound buffering on

and still I get:
NVP::AddAudioData():p1: Audio buffer overflow, audio data lost!
NVP::AddAudioData():p1: Audio buffer overflow, audio data lost!
NVP::AddAudioData():p1: Audio buffer overflow, audio data lost!
NVP::AddAudioData():p1: Audio buffer overflow, audio data lost!
NVP::AddAudioData():p1: Audio buffer overflow, audio data lost!
NVP::AddAudioData():p1: Audio buffer overflow, audio data lost!
NVP::AddAudioData():p1: Audio buffer overflow, audio data lost!
NVP::AddAudioData():p1: Audio buffer overflow, audio data lost!

I have been googling my fingers off the last mounted and the closed I have been to a solution is to patch my MythTV, could this ALSA problem be fixed in the next release of MythTV or MythDora?

I have tried a lot of settings, and I have attached my mythfrontend logfile
Comment 1 Jarod Wilson 2011-05-24 16:33:56 CEST
This is more of a thing that should be tackled on the mythtv-users mailing list, and its for a now 5 versions old fedora (sorry for not noticing the bz 'til now...), so I'm going to close this.