9 Aug
2009
9 Aug
'09
10:24 a.m.
On 08/09/2009 10:12 PM, Kjetil S. Matheussen wrote:
On Sun, 9 Aug 2009, Patrick Shirkey wrote:
Oh, I get you now.
So are you advocating that the official recommendation of LAD is not to
use a 64 bit system?
Cheers.
Patrick Shirkey
Boost Hardware Ltd
On 08/09/2009 08:12 PM, Kjetil S. Matheussen wrote:
No, as I said, the solution is very simple: Don't install a 64 bit OS.
That's what's causing your problems, apparently.
Patrick Shirkey:
To clarify, I have found that is difficult to get 32 bit apps to
connect to a 64 bit build of pulseaudio but these apps don't cause
stability issues with pulse. The problem is they just don't connect.
I can still run them directly over the alsa layer but that locks the
device in a standard Fedora 11 setup. I believe this would affect
alot of "normal" users so I would like to find a workable solution
that can be recommended to all packagers as a LAD standard. On 08/08/2009 09:57 PM, Jens M Andreasen wrote:
> On Sat, 2009-08-08 at 16:44 +1000, Patrick Shirkey wrote:
>
>
>
>> Here's what I have found after extensive testing with the latest dev
>> version of pulseaudio-v0.9.16-4 and jack-0.116.1 on a 2 core amd,
>> 4GB
>> notebook running Fedora 11.
>>
>> 1. 32 bit apps will not play on a 64 bit pulseaudio easily or at
>> all.
>> 2. Skype, Realplayer/Helix and Flash are a pain to get working with
>> pulseaudio if they work at all.
>>
>>
> These two items are related, right? Does it go away with a
> 32bit/extended kernel?
>
>
>
I haven't tested with a 32 bit system. I'm not sure if I will get the
time for that. I don't think in this case it has much to do with the
kernel. I think it is because pulse is compiled for 64 bit and the
apps
are looking for 32 bit libs.
Well, there's your problem. It's great that you try out new
software though, but of course then you'll get more stability
issues as well.