Nota Bene :
Aeolus requires :
libclalsadrv1
libclthreads2
libclxclient3
these 3 rpms are in mdv 2010.2 too

CC: (none) => philippedidier

Created attachment 3119 [details]
an icon for the desktop file

Created attachment 3120 [details]
a spec file for aeolus

a cleaned spec file for aeolus
(some modifications added to the original mandriva spec file)

I don't see the need of creating separate bugs, for something that only aeolus require.

A packager/maintaier/apprentice/padawan/whatever should know that.

but well.

Sorry...

I thought it was the cleanest way to provide spec files and patches for those rpms required for building aeolus, in the order they need to be built, knowing that they also may depend on each other.
better than providing 8 attached files in one bug...

(I had been taught, too, not to mix several new rpm requests in only one bug report... but indeed, you're right these other request are only needed by aeolus)

If you think it's better, I can attach here the attached files of the other requests and then close as invalid those 3 other requests.

Regards

Created attachment 3168 [details]
cleaned spec file

Attachment 3120 is obsolete: 0 => 1

Created attachment 3169 [details]
diff between mdv 2011 imported spec file and cleaned spec file

Not sure I really agree with putting the .desktop in the spec, although I do it that way when there was never one in the package before.
The snag is that it's harder to validate when it's in the spec, and it clutters the spec, especially when it has lots of translations. I would be tempted to put it back in the sources in the future, however it is OK for now.

Aeolus is now in Cauldron. Please try to test it.

Thanks Philippe.

Status: NEW => RESOLVED
CC: (none) => zen25000
Resolution: (none) => FIXED

Is this normal?

Without jack running it just dies on start without any GUI warning, which is a bit disconcerting.

From CLI :

[baz@jackodesktop ~]$ aeolus
Warning: memory lock failed.
Cannot connect to server socket err = No such file or directory
Cannot connect to server socket
jack server is not running or cannot be started
Error: can't connect to JACK

With qjackctl launched and started it launches correctly to GUI, however looking at CLI output it has these messages:

[baz@jackodesktop ~]$ aeolus
Warning: memory lock failed.
Cannot lock down 82246176 byte memory area (Cannot allocate memory)
Cannot use real-time scheduling (RR/5)(1: Operation not permitted)
JackClient::AcquireSelfRealTime error
Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 9: reading configurations from ~/.fonts.conf is deprecated.
Warning: can't run midi thread in RT mode.
Warning: can't run model thread in RT mode.
Reading '/usr/share/aeolus/stops/Aeolus/definition'
Reading '/home/baz/.aeolus-presets'

Barry

(In reply to comment #9)
> Is this normal?
> 
> Without jack running it just dies on start without any GUI warning, which is a
> bit disconcerting.
> 

Yes it is normal ! Jackit is required to install aeolus.rpm...
We must know that a Midi program using JACK needs jackd  running to work (same for qsampler or rosegarden ) 
Aeolus is useless if it is not connected to a virtual piano keyboard (VKeybd for instance) or to an external MIDI piano keyboard or to a sequencer...
Those connections must be done using JACK.
There was a possibility to write a script launching QjakCtl before launching aeolus, but it would have created problems if qjackctl was already running.

Perhaps it needs a warning at launch... 
There's a good online manual on aeolus website .
> From CLI :
> 
> [baz@jackodesktop ~]$ aeolus
> Warning: memory lock failed.
> Cannot connect to server socket err = No such file or directory
> Cannot connect to server socket
> jack server is not running or cannot be started
> Error: can't connect to JACK
> 
> With qjackctl launched and started it launches correctly to GUI, however
> looking at CLI output it has these messages:
> 
> [baz@jackodesktop ~]$ aeolus
> Warning: memory lock failed.
> Cannot lock down 82246176 byte memory area (Cannot allocate memory)
> Cannot use real-time scheduling (RR/5)(1: Operation not permitted)
> JackClient::AcquireSelfRealTime error
> Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 9: reading
> configurations from ~/.fonts.conf is deprecated.
> Warning: can't run midi thread in RT mode.
> Warning: can't run model thread in RT mode.
> Reading '/usr/share/aeolus/stops/Aeolus/definition'
> Reading '/home/baz/.aeolus-presets'
> 
> Barry

All the warnings you get come from JACK and mean that jackd has to be configured with qjackctl... they are strictly not aeolus warnings...

But the Fontconfig warning is surprising... perhaps something to do with jackit itself (not qjackctl) (a bug inside cauldron ?)

I don't have have any warning on Mageia2 :
I disabled pulseaudio, to minimize latency, configured qjackctl playing with sample rate, number of ports, frames/period, periods/buffer, input latency etc... : with a non realtime kernel I can get 46 ms as latency, with a realtime kernel it can be lowered to 24 ms)
It's a little tricky to configure but when it's done it's stored in a config file... used at launch
I have been told that there are no more problems with PulseAudio now... but I don't want to break something that works well for me ;-)

I have not the fontconfig warning on Mageia2.

PS
I downloaded the rpms but they can't be used on Mageia2 (not using the same version of gc)
I downloaded the srpms and could build the rpms 
it's OK !
I can't test on cauldron... I don't want to install it. and it's not possible to test inside a virtualbox...

Thanks again for your import ...

My tests show indeed that everything may be proposed as updates for Mageia2 (all these programs were provided by Mandriva 2010.1)

Regards
Philippe

PS : just a typo in the spec file : line 12
URL: http://okkinizita.net/linuxaudio/aeolus/index.html
instead of 
URL: http://kokkinizita.net/linuxaudio/aeolus/index.html
the first k is missing

But this doesn't prevent to build  ;-)
and doesn't need an update !

I thought again to the warnings about realtime !!!

I completely forgot to say something that is quite an evidence for me because I do this automatically when I install a new version of Mandriva and now Mageia :


To use realtime and memory lock (even with a non specific Real Time kernel)
you have to do some "tuning" of your system :

1) add yourself in the audio group
in a console
the command :    groups     ,    allows to verify the group audio exists
in a console
the command : su -c "gpasswd -a my_user_name audio"  , adds you to the audio group
(you may do this with MCC too !)

2)give realtime access to audio group

Modify the file : /etc/security/limits.conf 
adding these lines if they don't exist

# Real Time support for audio group
@audio  -  rtprio   90
@audio  -  memlock  unlimited

and 
if this line exists :
@audio  -  nice -15
comment it :
#@audio  -  nice -15


3) unconnect from your session
4)reconnect

5)
Run the command :
 ulimit -l -r

it will give you these two lines :

max locked memory       (kbytes, -l) 3000000
real-time priority              (-r) 90

this shows :
You have realtime scheduling
you can lock memory


NB instead of unlimited memlock, you can choose a value depending of the memory you dispose (think to preserve nearly at least 500 000 KBytes)
That means if you you have 2 000 000 KBytes you may lock 1 500 000 KBytes by editing limit.conf this way :
# Real Time support for audio group
@audio  -  rtprio   90
@audio  -  memlock  1500000 

You won't have the warnings you encountered !!!

When it's done you have a system ready for computer assisted music ! and really fast and professional ability.

Regards
Philippe