On Sun, Jun 27, 2010 at 20:00:18 (CEST), Matthias Klumpp wrote:

> On Sun, 27 Jun 2010 10:39:18 +0200, Reinhard Tartler <siret...@tauware.de>
> wrote:
>> I've just testbuild and installed the package in a test VM. Granted, it
>> has no real sound hardware, but for basic testing, this has to be
>> enough.
>> Observations:
>>  - it seems the user has to choose if he wants the jack or the
>>    pulseaudio backend at installation time. I find this odd, can't we
>>    pick a sensible default?
> The packages projectm-pulseaudio and projectm-jack are just applications to
> visualize Jack or PulseAudio streams using projectM.
> They are no backends and can be installed parallel. This is mentioned in
> the package description, but I could descriobe it more clearly if
> necessary.

as said on irc, yes, I didn't get it. I guess the description should be
clarified then.

>>  - there are two projectm icons, one provided by the jack variant and
>>    one for the pulseaudio. Same argument as above.
> Hmm... The icon is located in the projectm-data package, both .desktop
> files just refer to it. There are no two projectM icons.

if both packages are installed, two menu entries are displayed. Perhaps
they should read: "Visualize Pulseaudio Stream" and "Visualize Jackd
Stream" instead of "projectm (pulseaudio)"?

>>  - starting the pulseaudio backend segfaults on startup:
>> siret...@debian:~$ projectM-pulseaudio 
>> dir:/usr/share/projectM/config.inp 
>> reading ~/.projectM/config.inp 
>> QGLContext::makeCurrent(): Cannot make invalid context current.
>> Connection failure: Connection refused
>> QGLContext::makeCurrent(): Cannot make invalid context current.
>> Speicherzugriffsfehler (Speicherabzug geschrieben)
> This is a really stupid issue. A lot of people found it in projectM, but I
> can't fix it and noone else, including the Fedora team, as able to find the
> source of this crash. I sent a mail to upstream to quote on that error.

yes, let's see if they can comment on that.

Reinhard Tartler, KeyID 945348A4

pkg-multimedia-maintainers mailing list

Reply via email to