[mossroy]

OK I understand. Thanks for your answers.

It's too bad this can not be detected, so that to have one XBMC version optimized for both recent platforms (with hardware decoding) and a bit older platforms (with only software decoding but several cores).

[mossroy]

I was about to suggest a parameter that could be activated to enable multi-threaded decoding...
...but I read the discussion fritsch had in his pull request https://github.com/xbmc/xbmc/pull/2064 , in particular with davilla.

I agree with your conclusion : putting some parameters would be a workaround, not the real solution.

A long-term solution would be either to detect hardware decoding, or a white/black list as suggested.
Is there any place where this long-term solution is tracked? So that I could follow, or even participate?

[mossroy]

I recompiled version 12.1, for amd64, with the same modifications. It can be found here : http://mossroy.free.fr/xbmc/recompile_fr...d/xbmc.bin
It works great for me.

I was thinking of finding a better way to do it, and make it available to other people. I suppose it would be publishing it on a PPA? Would it be a good idea?

What would be your suggestion to easily create the .deb files and publish them on a PPA?
I have a amd64 Ubuntu 12.04.2 Virtualbox where I can easily compile XBMC with the above patch.
But I suppose it's not enough to create versions for i386, and for other versions of XBMC (Oneiric, Quantal, Raring). I hope I don't need to create a virtual machine for each config?

[fritsch]

Register a launchpad account.
As a hint - as you compile for linux: Do it with: --disable-vaapi --disable-crystalhd --disable-vdpau so that we don't get users here, where it harms hwaccel. If you wan't to keep them enable - make sure, that you LOG something somewere, so that it can be seen.

[mossroy]

Thanks for the hint.
I'll recompile without vaapi/vdpau/crystalhd. This should be safer if I put it on a PPA.

Regarding the PPA, it's already created. My question was more about generating the XBMC .deb files :
- Should I create them whith checkinstall, dpkg-buildpackage or any other manual way? I suppose I should better add my patch in the patch list of https://launchpad.net/~team-xbmc/+archiv...ian.tar.gz and somehow use this to create the .deb files? It looks like it uses Quilt. Should I "simply" refer to http://developer.ubuntu.com/packaging/ht...kages.html and http://askubuntu.com/questions/454/what-...custom-ppa?
- Should I put only the modified .deb in my PPA, with dependencies to the .deb files of https://launchpad.net/~team-xbmc/+archive/ppa ? I suppose I'd better generate all the .deb files, even if some of them are untouched
- How should I create the .deb files for other ubuntu versions/architectures?

Maybe I should ask these questions in the developer section of this forum?

[mossroy]

I asked the question in the developer section : http://forum.xbmc.org/showthread.php?tid=160986

[mossroy]

For the record, this issue has been fixed with XBMC version 13 (Gotham).
Multi-threaded decoding is activated and works well out-of-the-box on my low-spec machine