Dear Linux Audio Conference friends!
We need your support for this year's conference [1].
Currently we are still looking for volunteers to help us with the
following:
* Session Chairs - https://dudle.inf.tu-dresden.de/LAC18_Session/
* Stage Hands - https://dudle.inf.tu-dresden.de/LAC18_Stage/
* Camera/ Videomixer operators -
https://dudle.inf.tu-dresden.de/LAC18_Video/
If you would like to support us, please provide your mail address and
availability
to the corresponding dudle instance.
A short introduction/workshop for the different kinds of tasks will be
held on Thursday,
20180607 16:00 (CEST) (two hours before the Welcome Speech).
Your e-mail address will only be used by us to communicate with you
through a dedicated
mailing list, that will be disposed of after the conference.
The organizing team would like to thank you in advance, if you can spent
some time
to help us with running the conference.
See you in Berlin!
[1] https://lac.linuxaudio.org/2018
--
Linux Audio Conference team
Does anyone have the solfege ear-training package up and running (and actually producing sound)? I've noticed a few issues that I'd like to confirm before filing a bug report. Missing optional dependencies are the easy ones <https://nosuckdotorg.files.wordpress.com/2018/05/solfege-csound-mma-lilypon…>:
· csound https://www.archlinux.org/packages/community/x86_64/csound/
· mma https://aur.archlinux.org/packages/mma/
· lilypond https://www.archlinux.org/packages/community/x86_64/lilypond/
Then, there's the bigger issue of pyalsa <https://nosuckdotorg.files.wordpress.com/2018/05/solfege-pyalsa.png>, which is required for ALSA playback (and apparently completely different from the AUR's python2-pyalsaaudio and python-pyalsaaudio packages). The solfege package includes a Python script, however, for downloading and setting up pyalsa. Perhaps this script should be mentioned by pacman, when solfege is installed?
> ■ python2 /usr/share/solfege/solfege/download_pyalsa.py
> Traceback (most recent call last):
> File "/usr/share/solfege/solfege/download_pyalsa.py", line 25, in <module>
> import solfege
> ImportError: No module named solfege
... That is, once the script stops failing miserably. I will be reporting this issue upstream, if nobody tells me I'm missing something obvious.
Thanks!
Dear all,
we're happy to announce (and you might have noticed already),
that the schedule for Linux Audio Conference 2018 is live!
https://lac.linuxaudio.org/2018/pages/schedule
Please note, that it will still be subject to slight changes!
We have prepared a registration form for attendees:
https://www.ak.tu-berlin.de/index.php?id=195758
Please sign up at your earliest convenience to let us know,
if you're part of the conference.
Also, we'd like to draw special attention to this year's keynote,
which will be held by Gianfranco Ceccolini of MOD Devices:
https://lac.linuxaudio.org/2018/pages/event/102/
Looking forward to seeing you in Berlin,
--
Linux Audio Conference team
Hi AUR packagers,
which environment / tools are you using to build your AUR packages to
ensure you don't miss any dependencies?
I'm a bit confused on whether devtools can be used to build AUR packages
in a chroot environment or if it is only for packages in the official
repositories. Can somebody shed some light on this or link to a guide on
how to do this?
I tried this docker-based solution:
https://github.com/Aisbergg/docker-arch-aur-makepkg
It works for some packages, but I'm having trouble compiling e.g. the
juce AUR package. I get some strange missing symbols in the linking
stage, even though the needed library package seems to installed (icu).
Does anybody have any experience with this solution? Or can anybody
recommend an easy to use docker-based recipe for building AUR packages?
Cheers, Chris
