[LAU] aeolus, compiled and repos

[tom haddington]

Hello, All--

i'm running Ubuntu Studio 16.04, for starters. The Aeolus that came with
the distro simply closes upon starting. It also crashes patchage when
doing so. i really got no error, not even a seg fault, except that the
terminal told me that Aeolus couldn't read ~/.aeolus-presets.

So, i went to the website and downloaded the latest version. After
compiling. Aeolus would start, but no stops are displayed. The terminal
tells me, "Can't open 'stops/Aeolus/definition' for reading."

This is very unfortunate. A few years ago, i gave a temperament lecture
and relied heavily on Aeolus. i'd like to know that i can give it again.
Any help would be appreciated.

Take care,
tom

[Francesco Ariis]

Hello Tom,

Post by tom haddington
This is very unfortunate. A few years ago, i gave a temperament lecture
and relied heavily on Aeolus. i'd like to know that i can give it again.
Any help would be appreciated.

Throwing guesses, let's see if they help:
- did you `apt-get install stops` too?
- maybe you run alsa? Did you try invoking aeolus with
`aeolus -A`?

[David Kastrup]

Post by tom haddington
Hello, All--
i'm running Ubuntu Studio 16.04, for starters. The Aeolus that came with
the distro simply closes upon starting. It also crashes patchage when
doing so. i really got no error, not even a seg fault, except that the
terminal told me that Aeolus couldn't read ~/.aeolus-presets.
So, i went to the website and downloaded the latest version. After
compiling. Aeolus would start, but no stops are displayed. The terminal
tells me, "Can't open 'stops/Aeolus/definition' for reading."

Which sounds like it does not find the stop definitions relative to
where it expects to find them.

Post by tom haddington
This is very unfortunate. A few years ago, i gave a temperament lecture
and relied heavily on Aeolus. i'd like to know that i can give it again.
Any help would be appreciated.

Try 18.04. The version in 16.04 does not reserve enough stack space for
its Midi(?) thread on 64bit architectures. By the way, mentioning the
architecture would have been useful.

[tom haddington]

Ah, a couple of responses while running an errand! Here goes:

Francesco:

i run aeolus through jack. i attempted to run it through alsa, but was
told that aeolus could not connect to alsa. This happened when setting the
sample rate to both 44100 and 48000.

It turns out that stops is installed, though it is the version that came
with the distro. it just never occurred to me that stops and aeolus would
be installed as separate programs. Could it be that the newer compiled
version is butting heads with this?

David:

The architecture is 64bit. My apologies for not mentioning that. My
projects are not quite in order enough for me to upgrade to 18.04, though
it was my plan to do so in the next few weeks.

That's what i was thinking: The path to definitions is not clearly
defined. i've never learned the format for setting those paths. i've half
a head to uninstall stops and recompile the newer version to see if that
solves anything. Given the morning's plans, though, i'm a few hours away
from that....

Thank you, Francesco and David, for your responses.
tom

[Francesco Ariis]

Post by tom haddington
That's what i was thinking: The path to definitions is not clearly
defined. i've never learned the format for setting those paths. i've half
a head to uninstall stops and recompile the newer version to see if that
solves anything. Given the morning's plans, though, i'm a few hours away
from that....

By invoking `aeolus -h` I see

-S <stops> Name of stops directory [stops]
-I <instr> Name of instrument directory [Aeolus]
-W <waves> Name of waves directory [waves]


You are definitely missing stops in the new version.
On my system, the stops directory is

/usr/share/aeolus/stops/

so try to run the new versions with `aeolus -S /path/to/your/stops`.
Let's see if this solves it!

[Fons Adriaensen]

Post by Francesco Ariis
You are definitely missing stops in the new version.
On my system, the stops directory is
/usr/share/aeolus/stops/
so try to run the new versions with `aeolus -S /path/to/your/stops`.

Distros which install the stops in /usr/share/aeolus are supposed
to also install the corrresponding /etc/aeolus.conf which allows
you to run aeolus without any options required.

[David Kastrup]

Post by tom haddington
The architecture is 64bit. My apologies for not mentioning that. My
projects are not quite in order enough for me to upgrade to 18.04, though
it was my plan to do so in the next few weeks.
That's what i was thinking: The path to definitions is not clearly
defined. i've never learned the format for setting those paths.

Aeolus' documentation is close to non-existent. For some stuff you just
need to read the source, like for figuring out which Midi events and
controllers are processed and how.

Post by tom haddington
i've half a head to uninstall stops and recompile the newer version to
see if that solves anything. Given the morning's plans, though, i'm a
few hours away from that....

The problem is one of stack space so a single-line change should be
sufficient. However, I don't think there are any drawbacks with newer
versions, so as long as you are recompiling anyway, you can just use the
newest.

[Len Ovens]

Post by tom haddington
Hello, All--
i'm running Ubuntu Studio 16.04, for starters.  The Aeolus that came with the
distro simply closes upon starting.  It also crashes patchage when doing so.  i
really got no error, not even a seg fault, except that the terminal told me that
Aeolus couldn't read ~/.aeolus-presets.
So, i went to the website and downloaded the latest version.  After compiling. 
Aeolus would start, but no stops are displayed.  The terminal tells me, "Can't
open 'stops/Aeolus/definition' for reading."
This is very unfortunate.  A few years ago, i gave a temperament lecture and
relied heavily on Aeolus.  i'd like to know that i can give it again.  Any help
would be appreciated.

I am now no longer running Ubuntustudio 16.04 and have 18.04. Aeolus just
runs with no problem. However, I can not say the same for patchage. When I
try to connect aeolus to my keyboard or an output patchage gives an error
and shows no connection. However, If I then look at connections using
qjackctl, those connections seem to have been made after all.

In truth I had given up on patchage because I had trouble with it crashing
at odd times. In fact that may have been in US 16.04. while there has been
activity in patchage git, the release the package is based on is some
years old (1.0.0 in 2014). It may be that some lib patchage relies on has
changed enough to cause the odd problem but not enough to stop building.


--
Len Ovens
www.ovenwerks.net

[tom haddington]

Well, well, well, Francesco, that fixed the problem immediately! i've
spent the last few minutes listening to a Bach fugue in a variety of
temperaments. Aeolus doesn't remember the path, but i can jigger with a
script. This can now be considered solved.

Thank you so much for your help!
tom