gnif Wrote:If your problem is indeed a core AE issue, then post your problem, full debug logs, and if applicable, a stack trace. Keep this thread clean of extra crap, I need to see the REAL bug reports and not the configuration bug reports.
[/b]
Hi Gnif,
Glad to see your back around again - I see you deleted a couple of my posts as well... they were most definitely the evil support related posts, so fair call... However I think they are needed for certain users who are attempting to trial/test AE (which would help in the development phase etc), but because of the difference in mainstream to AE can't figure out how to make AE work in the first place to test so give it a miss.
The more users testing your work out the better for you guys as long as they are posting actual bugs and not just "how do I get my NVidia card working" etc.
As Phil65 posted, the forum rules state:
Code:
Developers forums for XBMC related development, by programmers and coders only!
No end-user support, [b]no bug reports[/b], and no feature/function requests in this forum!
To tell you the truth I didn't read that until now, but it leaves me feeling a little confused as to whether or not we should even be posting bugs in this forum or just leave this forum entirely alone for the developers...
If it's the latter then I think it would be useful that a support thread is created, where these support issues and bugs can be posted,
by one of the developers or moderators of this forum, and this dev thread is left alone entirely for the developers.
That way this one would be clear of all this other mess and then you could skim through the support thread instead for actual bugs, that should be clearer to spot, because lets face it bugs are things that can't be resolved with support. Like the bug that no matter what I can't get HD sound through AE with pulse enabled (PCM only displays on the receiver), and I can't get ANY sound at all with pulse disabled and without my patch.
This regression was clearly introduced with the commit I specified in my previous post after a few hours of hacking around with different branches.
I understand now the error I posted is not related to the device string - I am new to XBMC so assumed that was the indicator for the incorrect device name but now I know it's this one
Code:
INFO: CAESinkALSA::Initialize - Attempting to open device plug:hdmi
ERROR: CAESinkALSA::Initialize - snd_pcm_open_lconf(-2) - plug:hdmi
I have all passthrough options enabled, I build AE with --disable-pulse, and only have Alsa & Pulseaudio drivers in my system.
The device string I am using is hdmi:NVidia - and not trying to teach you how to suck eggs but HDMI NVidia users will most likely have a combination of the following as a custom device name:
hdmi:Card=name/number,Dev=number
hdmi:name/number,DEV=number
hdmi:name/number,number
hw:Card=name/number,Dev=number
hw:name/number,DEV=number
hw:name/number,number
plughw:Card=name/number,Dev=number
plughw:name/number,DEV=number
plughw:name/number,number
I can tell you that for me AE built WITH --disable-pulse AND my little patch, the above hdmi combinations all work, but the hw: and plughw: fail.
AE built WITH --disable-pulse and WITHOUT my patch ALL of the above fail because no matter what custom name is put in it ONLY attempts to initialise plug:hdmi which doesn't exist.
The only audio config change from a default install I've made is to add a modprobe mask that's it.
Also Not to be picky, but why is it Eden can enumerate the device names but AE can't... is that a known bug or is it just my machine?