Audio troubleshooting guide?
#1
Most of the problems I have with my XBMC installations are related to audio. Some audio tracks just don't play. Furthermore, they may play on one system, but not on another. I'm sure that I'm not the only one with such issues. Can you point me to some threads describing a systematic approach to audio troubleshooting?
Reply
#2
Put xbmc into debug mode.
Play the non working files.
Post Debug Log
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#3
What OS?

If Windows see http://forum.xbmc.org/showthread.php?tid=146911

Some basic stuff also at Audio_troubleshooting (wiki)
Reply
#4
I know that I can post a debug file, want to try to troubleshoot myself first. I use Linux based systems- XBMCBuntu and RaspBMC
Reply
#5
Then skip the last step and read the log byself:-)
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#6
I'm trying, but it doesn't make much sense so far. I see an audio passthrough failure, but not even sure if it is the indication of the problem.
This is the log: http://xbmclogs.com/show.php?id=283088
Reply
#7
You cut the important part. Change scaler to bilinear for Festung further.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#8
I didn't think I missed anything useful. Here is the capture between the press of the "play" button and the beginning of the previous paste.
http://xbmclogs.com/show.php?id=283144
The scaler was in bilinear. Changing it had no effect.

This is another capture from the same box, which is even more interesting- this file has 2 audio tracks, each time I switch between them audio may or may not appear.
http://xbmclogs.com/show.php?id=283103
Each audio track change is after this line in the file: OnKey: rightbracket (0x29) pressed, action is AudioNextLanguage
Reply
#9
Please don't cut the log files
Reply
#10
I posted everything starting from selection of the file to play. This is a combined log http://xbmclogs.com/show.php?id=284875
Reply
#11
Again don't cut logs. We need HW enumeration, GPU drivers, Version, etc. which is all in there last chance now.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#12
Sorry about it. I previously posted relevant code snippets and you helped me with the troubleshooting. I thought that posting the whole huge log file for the developers to dig in was considered rude. I will redo the whole thing.
Reply

Logout Mark Read Team Forum Stats Members Help
Audio troubleshooting guide?0