On 27 Nov 2009, at 06:28, Tim Moore wrote:
> In my git repositories on gitorious, http://gitorious.org/fg, I've been
> keeping
> "master" branches that are supposed to be stable; the intent is for them to
> be a kind of rolling release candidate that could be turned into a release
> in short ord
Tim Moore wrote:
> In my git repositories on gitorious, http://gitorious.org/fg, I've been
> keeping
> "master" branches that are supposed to be stable; the intent is for them to
> be a kind of rolling release candidate that could be turned into a release
> in short order. I've just pushed a bunch
I'm having major problems getting FG CVS to work with Ubuntu 9.10 and
Pulseaudio.
I have the standard alsa, pulseaudio from Ubuntu.
I have installed the latest openal-soft, just to be sure.
For the following contents of ~/.alsoftrc here are the results I get...
drivers=pulse
- very unreliabl
James Sleeman wrote:
> So, does anybody have the current CVS working well with pulse+alsa or
> pulse on it's own?
I've never been a fan of pulse audio and will never use it in the
future. Let's face it, it's like sending OpenGL streams through a
software renderer before handing it over to the
James Sleeman wrote:
> So, does anybody have the current CVS working well with pulse+alsa or
> pulse on it's own?
I don't use sound with FlightGear, but with other setups my best
experience is with leaving the system-wide "drivers" setting as is -
which typically means to leave the declaration e
On 28/11/09 01:41, Martin Spott wrote:
> experience is with leaving the system-wide "drivers" setting as is -
> which typically means to leave the declaration emtpy - and not setting
> anything different in the private config
In this case it selects the alsa->pulse setup with it's stuttering.
James Sleeman wrote:
> On 28/11/09 01:41, Martin Spott wrote:
>
>> experience is with leaving the system-wide "drivers" setting as is -
>> which typically means to leave the declaration emtpy - and not setting
>> anything different in the private config
>>
> In this case it selects the alsa
On 28/11/09 01:21, Erik Hofman wrote:
> I've never been a fan of pulse audio and will never use it in the
> future. Let's face it, it's like sending OpenGL streams through a
> software renderer before handing it over to the OpenGL hardware.
>
Be that as it may,
a) it's the standard audio set
On 28/11/09 01:59, Nathanael Rebsch wrote:
enable users to load modules, see /etc/default/pulse
Doesn't appear to make a difference.
--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
tri
I have edited /etc/default/pulse and made sure users are allowed to load
additional modules,
i also installed all modules i could find, and simple left .alsoftrc
state drivers=oss
i no longer need to kill pulse for it to work
(thou there was a need to restart services (which is tricky if pulse i
Erik Hofman wrote:
> James Sleeman wrote:
>
>
>> So, does anybody have the current CVS working well with pulse+alsa or
>> pulse on it's own?
>>
>
> I've never been a fan of pulse audio and will never use it in the
> future. Let's face it, it's like sending OpenGL streams through a
> soft
James Sleeman wrote:
> On 28/11/09 01:59, Nathanael Rebsch wrote:
>>
>> enable users to load modules, see /etc/default/pulse
>>
> Doesn't appear to make a difference.
sorry, i meant /etc/default/pulseaudio, but i assume you found the file
i meant ^^
i also installed a bunch of pulseaudio module
Nathanael Rebsch wrote:
> point though being, that a large amount of people are 'forced' to use it!
> and therefore it aint a bad idea to know how to work with or around it!
True.
Erik
--
Let Crystal Reports handle the
On Sat, Nov 28, 2009 at 12:19 AM, Erik Hofman wrote:
> Nathanael Rebsch wrote:
>
>> point though being, that a large amount of people are 'forced' to use it!
>> and therefore it aint a bad idea to know how to work with or around it!
>
> True.
>
> Erik
>
Some people have had some better success wi
Hi Erik,
Erik Hofman wrote:
> I've never been a fan of pulse audio and will never use it in the
> future. Let's face it, it's like sending OpenGL streams through a
> software renderer before handing it over to the OpenGL hardware.
Yes, let's face it: I've seen quite a lot of different approach
Jari Häkkinen wrote:
Tatsuhiro Nishioka wrote:
Ah, so there is no real need for alut.h at all. Hm, so the alut.h issue
should rather go in to simgear. I now tested with a zero length alut.h
and no libalut. Compiling works but the linker fails with alut-complaints
Undefined symbols:
"_alutInit
On Fri, Nov 27, 2009 at 1:38 PM, Nathanael Rebsch wrote:
> Erik Hofman wrote:
>> James Sleeman wrote:
>>
>>
>>> So, does anybody have the current CVS working well with pulse+alsa or
>>> pulse on it's own?
>>>
>>
> point though being, that a large amount of people are 'forced' to use it!
> and ther
Hi,
I have just commited some changes to the xml autopilot. Along with a tiny
bugfix comes a new feature which now allows more than one
definition in the aircraft's -set.xml.
You may now do something like this:
Aircraft/Hansajet/Systems/Hansajet-flightdirector.xml
Hi Torsten,
One thing I noticed recently (but this could have been in the code for a
while) is that if a is a hard coded instead of a
then if the autopilot definition is reloaded (something you might
do often when tuning the autopilot) the value nodes can get mismapped to
other nodes. I took a
Csaba Halász wrote:
> James wants to *use* pulse while most users would be happy to just
> have FG work *around* pulse.
I disagree. Instead, I suspect that most (Linux) users would be happy
to see FlightGear playing seamlessly through PulseAudio. And I'll
explain, why I think this is the case.
I
Hi All,
I'd like to propose a couple of straightforward menu changes:
- Move Instant Replay from the View menu to the File menu. Conceptually, it
doesn't fit in with the other contents of the View menu, and given that we're
replaying existing data, it feels to me that it fits better within the
That sounds good to me , but I see my additions were removed ,
and no reply to the suggestion of splitting view and rendering , so I'll
stay out of it :)
Other than to suggest maybe the hud config could be added under view
instead of a separate dialog, with a checkbox to toggle 3d mode.
Just a thou
Hi,
> Hi,
>
> I have just commited some changes to the xml autopilot.
> Along with a tiny
> bugfix
Tiny? ;-)
Thanks for the fix!
Regards
Heiko
__
Do You Yahoo!?
Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz gege
On 11/27/2009 10:08 AM, Erik Hofman wrote:
> Tim Moore wrote:
>> In my git repositories on gitorious, http://gitorious.org/fg, I've been
>> keeping
>> "master" branches that are supposed to be stable; the intent is for them to
>> be a kind of rolling release candidate that could be turned into a r
Csaba Halász wrote:
> These are two questions as I see it.
> James wants to *use* pulse while most users would be happy to just
> have FG work *around* pulse.
> For this latter case, I believe an alsoftrc with alsa driver and
> dmix/dsnoop devices should be fine.
>
I could work around pulse, by
On Sat, Nov 28, 2009 at 12:56 AM, James Sleeman wrote:
> Csaba Halász wrote:
>> These are two questions as I see it.
>> James wants to *use* pulse while most users would be happy to just
>> have FG work *around* pulse.
>> For this latter case, I believe an alsoftrc with alsa driver and
>> dmix/dsn
On 28/11/09 13:18, Csaba Halász wrote:
> But have you actually tried keeping pulse running and directing openal
> to alsa dmix?
>
No, it sounds really complicated to setup (I always found any monkeying
with alsa to be a nightmare personally). And it kinda seems like it'd
be a lot of trouble f
On Sat, Nov 28, 2009 at 1:40 AM, James Sleeman wrote:
> On 28/11/09 13:18, Csaba Halász wrote:
>> But have you actually tried keeping pulse running and directing openal
>> to alsa dmix?
>>
> No, it sounds really complicated to setup (I always found any monkeying
> with alsa to be a nightmare perso
On 28/11/09 13:18, Csaba Halász wrote:
>
> FG ---> OpenAl ---> ALSA (dmix) > hardware
> app1 > pulse ^
> app2 --- ALSA (pulse) ---^
>
Also, that's double mixing for pulse applications isn't it? Seems a
fairly bad idea for latency and cpu on everything that goe
On Sat, Nov 28, 2009 at 1:48 AM, James Sleeman wrote:
> On 28/11/09 13:18, Csaba Halász wrote:
>>
>> FG ---> OpenAl ---> ALSA (dmix) > hardware
>> app1 > pulse ^
>> app2 --- ALSA (pulse) ---^
>>
>
> Also, that's double mixing for pulse applications isn't it? Seems
On 28/11/09 13:55, Csaba Halász wrote:
> I wonder if you can try any other OpenAl application and see if it has
> the same problem.
>
Gladly if you suggest one, I'm not familar with any.
--
Let Crystal Reports handle t
For what it's worth, here's a backtrace of when it's hung trying to
connect to pulse...
#0 pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:261
#1 0x7125e42b in pa_threaded_mainloop_wait () from
/usr/lib/libpulse.so.0
#2 0x75af12
On Sat, Nov 28, 2009 at 1:48 AM, James Sleeman wrote:
>
> Also, that's double mixing for pulse applications isn't it? Seems a
> fairly bad idea for latency and cpu on everything that goes through
> pulse, which is, pretty well everything else except flightgear :-/
And skype and possibly flash.
I
On Sat, 2009-11-28 at 02:23 +0100, Csaba Halász wrote:
> On Sat, Nov 28, 2009 at 1:48 AM, James Sleeman wrote:
> >
> > Also, that's double mixing for pulse applications isn't it? Seems a
> > fairly bad idea for latency and cpu on everything that goes through
> > pulse, which is, pretty well every
Hi Jari,
First, I made patches for configure.ac in both SimGear and FlightGear (except
svn lib part) so please give it a try.
# This assumes you have alut.h (that comes with Creative's OpenAL.framework) in
/Developer/SDKs/MacOSX10.6/System/Library/OpenAL.framework/Headers
On Nov 27, 2009, at 10
Hi Tim,
As I said to you in IRC, I have a weird transparency problem with the shaders
enabled.
Here's the snapshot (helicopter view) with shaders.
http://macflightgear.sourceforge.net/wp-content/uploads/snapshots/3dclouds-effect-enabled.png
I used both FG/SG @ cvs-head as of yesterday and FG/SG
36 matches
Mail list logo
