builds without issues on Arch Linux. Running it works too, but I didn't
test it. Jack audio IOs and Jack MIDI out are shown by QjackCtl. Are you
aware that Rakarrack provides a relatively good working monophonic MIDI
JFTR I got those messages:
Samplerate 44100 Buffersize 256
QObject::connect: No such slot GSEngine::setInputGain(int)
QObject::connect: (sender name: 'InputVol')
QObject::connect: No such slot GSEngine::setOutputGain(int)
QObject::connect: (sender name: 'OutputVol')
Take a second keyboard from the dollar store (mine is USB) add a driver
and it can cantrol the DAW.
I get 5 channel strips and enough keys left to emulate al the rest of the
mackie controller keys with one or two left over.
I was thinking of using the little controller inside and trying to hook up
some encoders between two keys, but even with cheap encoders it becomes
worth getting a better controller pretty quick. I am looking at the odroid
I think. It would use either rtpmidi or ipmidi or both. However, this code
is still useful. It is not hard to think of ways to use an extra set of
I would like to express my thanks to all the organizers and the support
teams in Mainz. It was again a great conference, with exchange of
informations, opinions and music, and it was nice to have the chance to
have a beer or two with many great people from the community.
Thanks to Albert and his family for their great job in making LAC 2015
as threatened in the closing sessions of this year's LAC, here are some
of my observations about the conference and suggestions for improving
some things. I attended the conference for the fist time, so please let
me say, that I enjoyed the conference *very much*. I liked many things
about it. The list below is only about the things that I didn't, but
please don't take away from this that I think that the organizers did a
bad job, they did very well IMHO. But there's always room for
improvement. So here goes. Items in each section are listed in
descending order of importance / seriousness.
- For a conference about audio, the speakers' audio was surprisingly
poorly organized and consequently technical issues lead to
*sometimes* poor intelligibility of the speakers or poor quality of
audio demonstrations (especially in P2 and P5).
- Poor leveling leading to:
- too quiet speech levels,
- huge level differences between microphone(s) and other audio.
- Non-functioning or accidentally switched-off microphones.
- Too short cables.
- Loud pops when things were plugged in or unplugged.
- Sometimes it seemed that the video stream was more important than the
present audience. Indicators:
- Camera in front of the screen, obstructing part of the presentation
- Camera filming the setup on the table next to the speaker desk but
for the audience in the lecture hall it was hard to see what was on
- The video splitter *may have* interfered with resp. prevented video
output to projector from working.
- Camera set up in the middle of the audience room, and thus making
seats in front of it unavailable for participants (Camera team
asked participants not to obstruct the camera view even during the
breaks between talks).
IMHO the needs of the people who make the effort to come to attend the
conference personally should always be the most important.
- The intended purpose and acceptable usage of the "Hack'n'Roll" room
and how to organize its shared usage or request using it for a
certain time slot was *not at all* clear.
- There was no opportunity to *spontaneously* do a small presentation
of a project or idea to a bigger audience (see Lightning Talks below).
- The "Aufenthaltsbereich" (lounge area) in the hall outside P2-P5 did
not have enough tables and seats and it could have been a bit more
- The wifi access was slightly mis-configured, one had to change the
encryption type used from "Tunneled TLS" to "PEAP" and this was not
clearly documented, so one had to find this out by trail-and-error.
- Have a mailing list for conference organization that's also there for
discussion about the future of the conference, so that ideas are not
lost in the noise of the general LAU mailing list
- Have a session chair for each session, including for workshops, that:
- May fill the role of technical assistant (see below) as well.
- Maintains order:
- Sees that doors are closed at the beginning.
- Reminds everybody to turn their cellphones silent and keep
disturbance by leaving or fiddling with equipment to a minimum.
- Announces the title of the talk, the name of the speaker, the
duration and time for questions.
- Makes sure the speaker stays on time.
- Moderates the question session and reminds the speaker to repeat the
Session chairs can be filled by participants. Assuming three days and
three tracks and one session chair per half-day, twelve persons max.
are needed to volunteer as a session chair.
- Require speakers to test their video and audio setup (including the
speaker microphone) *before* the beginning time of the talk, and plan
change-over times accordingly or have dedicated testing slots in
between session slots (e.g. during lunch breaks).
This means that somebody is needed to actively seek out speakers and
check that they have tested their setup. Speakers can also be
reminded to do so at the registration desk and be told where to find
- Provide a pool of common adapters and cables for video and audio
connections with sufficient cable lengths. Even if speakers are told
to bring appropriate adapters in advance, some of them *will* forget
to do so.
- Have a technical assistant in *each* lecture hall that:
- Helps the speakers to check their setup.
- Sets up audio and video connections.
- Levels audio channels.
- Mutes/unmutes mixer channels as needed.
- Fixes problems.
- Prevents other participants form tampering with the equipment.
- Tape over on/off switches on microphones.
- Have a more informal Lightning Talk Session of approx. 1 hour with
*5-minute* lightning talks, possibly on several days. Speakers can
apply for lightning talks slots *only* during the morning of the day
of the LT-Session on a first-come-first-served basis (only one slot
per speaker, if necessary).
The LT-Session needs a moderator and possibly a technical assistant,
which ensure that talk times are strictly kept and change-over time
Slides are not mandatory for lightning talks and if they are used,
the number of slides should be kept to the minimum necessary. There
should be a central space on the web site to upload LT slides without
- Have a paper time table on the door of the "Hack'n'Roll" room where
people can register for using it at a certain time for a given
purpose (restrict number of slots that can be used by one
Identify an opportunity (e.g. at the beginning of the first talk in
the morning/afternoon), where people/projects can announce when they
have something happening in the "Hack'n'Roll" space.
- Provide a glass and a bottle of water for each speaker.
- Have more power sockets in the lecture halls.
- Buy more (real) milk for the coffee and do not use plastic cups
(waste, too hot to hold). Put up a sign with the suggested donation
amount. If necessary, find a sponsor for the coffee.
Thank you for your attention and for a great LAC 2015,
Gene Hesket wrote:
>> Some of you may be interested in a fresh slice of "The Saints Go Marching
>> in" from the "Pixel Land Jazz Ensemble" as arranged by Dr Richard
> I thought this one was worth listening too, and on balance it was.
> Nicely creative but a bit slower paced than the Saints would normally
> be. Rather than the rousing march it usually is, it gives the
> impression of just slowly ambling down the street. Solo work from
> around the 4 minute mark on was nicely highlighted. Thank you.
Thanks Gene, I agree that the main section has a tighter feel to it and
the "Pixel Land Jazz Ensemble" comes together well at that point but I
hope you'll have another listen to the lead in again. It's Actually more
Impressive than the main section from several aspects ;-)
> You can hear this track and others on the LCRM jazz stream:
Boost Hardware Ltd
I compiled 4.0, seems to work fine, however jack audio breaks up, and my
quadcore is only running on one core (only one cpu listed in
/proc/cpuinfo). I suspect the two to be related.
Any thoughts? Others running on 4.0? Special things to think about?
NB: Couldn't find the config for multicore support in the kernel, hints?
every year the post-lac nostalgic syndrome gets its toll...
all the photos taken by this lousy photo-shooter of yours during the
lac2015@jgu-mainz are now online:
the even lousier videos taken from some of the linux sound night live
acts are also delivered unedited and online:
rncbc aka. Rui Nuno Capela