Hi guys,
Season's greetings.
Here are a few of the cover songs I produced and recorded for my
Christmas album.
I'm playing and singing everything here for better or worse.
I recorded and mixed everything in Nama over about two months of
sporatic evenings..
There are moments which I'm proud of, and things I know could have
been better. But, rather than letting it languish, I wanted to get it
out. I can always remix and redo. :-)
I wish I could have corrected the vocal intonation in several places.
I wish I hadn't mixed the bass so hot, and wish I had punped up the
percussion a bit. I also need to learn to master.
There are other nocks, but those are the biggest.
Feel free to pass along your gentle constructive criticism. :-)
Here are the links.
Drummer Boy
https://dl.dropboxusercontent.com/u/30068518/Drummerboy.mp3
Do They Know It's Christmas
https://dl.dropboxusercontent.com/u/30068518/DoTheyKnow.mp3
Do You Hear What I Hear
https://dl.dropboxusercontent.com/u/30068518/DoYouHear.mp3
Mary Did You Know
https://dl.dropboxusercontent.com/u/30068518/MaryDidYouKnow.mp3
What If God Rest
https://dl.dropboxusercontent.com/u/30068518/WhatIfGodRest.mp3
These songs obviously belong to their owners, and I only lay claim to
my arrangements.
Rusty
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hey, just a heads up on this controller I found, I know some guys here
might be interested:
http://www.illucia.com/
it surely looks way more interesting to me than the various Monome-like
controllers
cheers,
renato
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
iQEcBAEBAgAGBQJSl3LvAAoJEBz6xFdttjrfjfIH/jTGP8uFqkYEibHhP7whd4Ep
jRdXpKciEydXpxefIbqYUtfohqLY2X8pYXyfnDPV3S/OyJlvTzZWQJZUQ7xhp+JT
lHdzKVqNyI0+PKtUtyo7WUmOEekRQ0k6vKYx23cDPTuyvVbqzxatMDAMKSBoSlSp
M7ttb7C4hgmSusPFAxrGsk/x5mCvG521f0s/a4fCGsuElxg3dwye0KcysBZMj90r
KzkLqwUDCESELEFQV5MEODn4zKntjsIFVuJbDuP1WAMUEKfTnYLk/ZfkRpMSobim
QxuFnVeh75uNuiccUHCwuFuBF4yNH6lkIv4v5drSQ7MrkHunKJpSAY71YjnTaOU=
=p9af
-----END PGP SIGNATURE-----
Hail citizens!
M'colleague and I are proud to announce the first releases from Julius
Quintus, LAU's least-productive prog supergroup (for which I am entirely
to blame -- the productivity thing, that is, I'm only partially to blame
for the music).
These were recorded at JQ's first recording session (and second ever
meeting) in August 2010, in the UK.
Rough mixes were done three years ago, but they've languished ever
since, basically waiting for me to get my arse into gear. An injury
earlier in the year that rendered me unable to play, together with other
personal circumstances, made it a good opportunity to revisit these two
pieces and finally do them justice.
I'd like to take this opportunity to dedicate these two pieces to
m'colleague, Julien, as a thank you for all the friendship and music
we've shared, and as an apology for being so damn slow with everything.
Those that can, make music: those that can't, make excuses. We have a
good partnership: m'colleague makes the music and I have a batch of
freshly made excuses specially prepared...
https://soundcloud.com/quirq-uk/julius-quintus-as-a-cloudhttps://soundcloud.com/quirq-uk/julius-quintus-time-to-go
Details and other links further below. We hope you enjoy and, as always,
comments are welcomed.
No capes, Persian rugs, curries, knives or ice rinks were harmed during
the making of this music.
Ave,
Julius Quintus
---
AS A CLOUD PASSES THE SUN, SO MY LIFE TURNS GREY
This main bulk of this short piece was written in the studio in August 2010.
The flute was added later in August, following the main session. The
take was only supposed to be a placeholder until a better one could be
recorded, but so far that hasn't happened. So the flute playing is even
crappier than is usual.
The guitar overdubs were the last to be done, being added in September
2010 following an inspirational break in Orkney.
J: Black Grand piano, Virtual String Machine, M-Tron Pro (three violins,
eight choir), drums
Q: guitars (SA503TVL, Les Paul), fretless bass, flute, percussion
Music: J&Q
Engineering, mixing & mastering: Q
SoundCloud:
https://soundcloud.com/quirq-uk/julius-quintus-as-a-cloud
FLAC download:
http://juliencoder.de/nama/Julius_Quintus-As_A_Cloud_Passes_The_Sun_So_My_L…
---
TIME TO GO [6:01]
This was a studio marmalade -- you can't really jam a full prog piece
with two people -- recorded in August 2010.
Piano and guitar were laid down together with the string machine overdub
quickly following (sadly not the real deal, since the studio wasn't
equipped with real string machines until later). The next day, the drums
were improvised/overdubbed, followed by the bass (improvising on a
fretless was not the best of ideas and protestations were made!).
The improvised lead guitar part was overdubbed on the last full day in
the studio, as it was beginning to dawn that it would soon be time to go
and something needed to be laid down. It's the first take.
The other details were added during pre-production, which commenced this
summer.
J: Black Grand piano, Virtual String Machine, drums
Q: guitars (SA503TVL), fretless bass, ChamberTron (female voice, male
voice), M-Tron Pro (boys' choir, female choir, male choir), Little
Phatty SII, Dark Energy, percussion
Music: J&Q
Engineering, mixing & mastering: Q
SoundCloud:
https://soundcloud.com/quirq-uk/julius-quintus-time-to-go
FLAC download:
http://juliencoder.de/nama/Julius_Quintus-Time_To_Go.flac
---
Our special thanks go to, but are not limited to, all those behind:
Ardour, Linuxsampler, Hydrogen, linuxDSP, Calf, Invada, zita, IR, SWH,
Guitarix, ZamAudio, GForce Software, Sampletekk, NI, plus Ian Shepherd.
Hi there,
I'm want to give live-coding a try and am looking for a nice
environment. I came across LuaAV again, didn't find it in any repos and
now I remembered why: the guys who develop it use a rather weird build
system, basically a few scripts specifically written for some version
of ubuntu. However, I guess it's not impossible to build it on other
distros.
Has anyone tried? Is it worth it?
Regards,
Philipp
Hard. Fast. Highly political. Most of the heavy lifting was done in
Ardour. Most of the drum programming was in Hydrogen, with additoinal
programming was done in Ardour MIDI'd to Hydrogen via JACK. Other details
can be found in the SoundCloud description.
https://soundcloud.com/dj-dual-core/the-reactionaries-believe-in
Neil
--
DJ Dual Core's Blog
http://oldmixtapes.blogspot.com/
Order without government; Peace without violence.
Dear all,
QMidiArp 0.5.3 fixes a number of bugs and should from now on replace 0.5.2. It also has some minor functional improvements, all is listed below.
With thanks to all reporters, contributors and translators.
And....enjoy!
Frank
------------------------------------
QMidiArp is an advanced MIDI arpeggiator, programmable step sequencer and LFO for Linux with ALSA and JACK MIDI backends.
------------------------------------
Downloads are available at
http://qmidiarp.sourceforge.net/
direct link:
http://sourceforge.net/projects/qmidiarp/files/qmidiarp/0.5.3/qmidiarp-0.5.…
------------------------------------
qmidiarp-0.5.3 (2013-11-26)
New Features
 o Random functions for sequencer and LFO steps and arp repeat mode
   (feature request #5 Keith Milner)
Improvements
 o NSM support now handles import/export/clear to facilitate
   getting started (Roy Vegard Ovesen)
 o Tempo is now MIDI-controllable (MIDI-learn)
 o Sequencer transpose slider is now MIDI controllable (MIDI-learn)
   (feature request #7)
 o Sequencer pattern maximum length extended to 32 bars
   (feature request #6)
Fixed Bugs
 o LFO offset jumped back to fixed value when MIDI controlled
   (bug #6 distrozapper)
 o Arp trigger behavior was not practical with chords pressed on keyboard
   (bug #7 Burkhard Ritter)
 o JACK Transport no longer worked when no JT Master tempo was present
   (bug #5 Barney Holmes)
 o Deleting an arp pattern in text window while running caused crash
 o Note lengths were not consistent between alsa and jack backends
 o Note lengths did not account for current tempo
 o Sequencer did not honor "D" button when MIDI controlled
 o Seq note length is now a 16th at half slider scale
2013/11/14 Carlos sanchiavedraz <csanchezgs(a)gmail.com>:
> 2013/11/14 Robin Gareus <robin(a)gareus.org>:
>> On 11/14/2013 01:20 PM, Carlos sanchiavedraz wrote:
>>> Hello dear all LAUers.
>>>
>>> Time ago I did some research about open source/free software licences:
>>> types, pros and cons, etc. I'm reviewing it and, given that I follow
>>> and love many of the great projects and applications coded by members
>>> of this list, I would love to here you're opinions (pros, cons) and
>>> experience in practice and why you chose X licence for your project(s)
>>> (business model or enterprise view in mind, 'cause you like it...).
>>
>> Software concerning infrastructure and inter-operation should *provide
>> freedom to the developer*. Less restrictive licensing (eg. MIT, BSD,
>> public-domain) is important to promote standards (in particular network
>> or communication protocols.)
>>
>> Application software aimed at end-users should *protect the freedom of
>> the user*. Here GPL is appropriate. It ensures that any user will be
>> free to run it (which must include the freedom to modify it e.g. to make
>> it work on future systems,...) amongst other freedoms. From a developer
>> point of view the GPL also provides continuity and allows software to
>> evolve.
>>
>>
>> Personally I either choose the MIT or the GPLv2+ license for all of my
>> projects. The former for libs, the latter for apps (with the usual
>> exceptions, mainly due to re-using code and inheriting licenses). The
>> reason for those two is that they're the only two licenses that I have
>> read, understand and agree with.
>> I have no intention to spend any time reading all of the others licenses
>> cover-to-cover, and I believe that any developer who is using a given
>> license should at least have a basic understanding of [the implications
>> of] the license which mandates reading it completely.
>> I keep an open eye on [new] licenses but have not had any reason to
>> investigate any of them any further.
>>
>>> I see that the most commons are GPL2 (some don't like yet the v3) and
>>> GPL3. And nowadays with so many services in the cloud also AGPL, and
>>> MIT or Apache as well with HTML and Javascript libs and artifacts.
>>>
>>> Thanks as always for sharing your work and knowledge.
>>
>>
>> 2c,
>> robin
>
> Well and clearly explained.
>
> Thanks so much, Robin.
>
> --
> Carlos sanchiavedraz
> * Musix GNU+Linux
> http://www.musix.es
I've made a quick search in Sourceforge to see the number of projects
with each licence and related to Audio:
* GPL2/GPL2+: they are a vast majority, maybe just because It's older
than v3. Here you can see some of the projects that we love at Musix
and myself: Ardour (in its own repo), Qsynth, Qjackctl, (all the rncbc
stuff), Rakarrack Hydrogen, LMMS
* GPL3: Here we have Guitarix (also has GPL2 and BSD), Virtual MIDI
Piano Keyboard
* AGPL: not much
You can check also the chapter "Adoption"[1] Wikipedia as part of the
article on GPL. There you can read:
"
In 2011, four years after the release of the GPLv3, according to Black
Duck Software data, 6.5% of all open-source license projects are GPLv3
while 42.5% are GPLv2.[45] Google open-source programs office manager
Chris DiBona reported that the number of open-source projects licensed
software that had moved to GPLv3 from GPLv2 was 50% in 2009,
"
I thought at the beginning that choosing GPLv3 was the way to go
nowadays: It's newer, and takes into account problems like
"Tivoization", patents and stuff.
And also AGPL is one for me to consider because many of my projects
could benefit from its protection against being "cloud-servified"
against your will, let's say.
But then I see that big projects (reference for me in the FLOSS world)
like Ardour, Jackd, Qjackctl, Qsynth, Rakarrack are GPL2+ and others
just GPL2, so I wonder if they just keep going on with what was chosen
in first place (backwards compatibility I guess) or they just don't
like GPLv3 yet even with those mentioned potential benefits.
I'd be very appreciate to know in particular the experience of these
projects I mentioned and that of people who actually make a living
developing floss software and have a business model that supports
and/or benefits from it.
Thanks so much anyways you all.
[1] https://en.wikipedia.org/wiki/GPLv2#Adoption
--
Carlos sanchiavedraz
* Musix GNU+Linux
http://www.musix.es