Low Latency vs. Real Time Kernel
by Brian Monroe
I've been spending a lot of time on the #opensourcemusicians channel
talking to Ubuntu Studio users about their kernel and latency times they're
getting. Seems like most of them are using g a stock kernel with the
preemptive option enabled and they are getting great latency results
(2ms)while utilizing the @audio group on their user. I ended up compiling
my own low latency kernel and I haven't had any issues with it yet. If this
is what we are missing for the spin I'd be happy to maintain packaging for
the kernel. I know ccrma has been behind a few kernel releases.
I saw the instructions for adding the real time patch for a tick less
kernel and from what I can tell it wouldn't be hard to get that rolling as
well.
I'm not entirely sure what ccrma does differently with their kernels
compared to other Linux users, and I'm still a bit of a noob so I could be
off base with this, but I would reason that we should be able to just
utilize the same settings to archive similar performance enhancements.
I thought I read that ccrma uses a unique scheduler, but if we could get a
2ms latency time without it, the point may be moot.
9 years, 4 months
Another GSoC 2013 Idea
by Christopher Antila
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi everybody!
Maybe we could propose multiple ideas for GSoC this year. (Speaking of
which, we'd better get started with posting our Ideas!)
https://fedoraproject.org/wiki/Summer_coding_ideas_for_2013
Here's an Idea that I'm willing to mentor, even though I previously
said I wouldn't: we sponsor an electronic musician to prepare a series
of musical works, using only software available in Fedora (including
PlanetCCRMA), and to document their process.
This would be a huge benefit for us, for a number of reasons. First,
we'd have more tangible demonstrations of the viability of creativity
with FOSS software. Second, we could require different software (e.g.,
PureData, SuperCollider, Csound) for a broad demonstration. Third,
we'd have more extensive documentation on "how to use computers to be
musically creative," that would hopefully inspire both "unmusical"
people and people who are "bad with computers." Fourth, we'd
demonstrate that "coding" doesn't mean "use JavaScript to write a
mobile app then profit lawlz" as "the media" seems to think, and to
demonstrate that Fedora isn't only the upstream to Red Hat Enterprise
Linux. Finally, and most importantly, we could use this as the basis
to create a musical community around Fedora.
When I first got here in 2010, what we needed most was a greater
number of dedicated and active volunteers. That's still true now, but
we're much better off than we used to be. In 2013, we have our own
spin, we have our own documentation, and I suggest that the only thing
we're still missing is the vibrant musical community. Whereas I used
to believe that providing "the right tools" would create an active
community, now I realize it's much more complicated.
Active communities reproduce themselves. More specifically, the power
relations of active communities tend to reproduce the communities in
which they were formed. What we need to do is create the relations for
the community we want, even though it doesn't already exist. It's a
complicated way to say "cool music attracts people that will make cool
music."
Consider that, on this music mailing list, we should be discussing
music and related issues, but we only discuss related issues (and
D-flat). I really don't know what musical things people here do, and
you have no idea what I do. I believe this is where we need to focus
our efforts now. If we can use GSoC to basically commission a
composer, and if a few more of us commit to producing at least one
musical thing this summer, and if we do a good job of circulating our
music through the right channels, I think we can kick-start the
community we (or at least I) have been hoping for!
Any thoughts?
Christopher
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
iQIcBAEBAgAGBQJRKmwbAAoJEGpo1cWDqVnYj6UP/iPA3qLYJ0N0Msy9kp6pkgh6
Yd7pgSEwtqh051OQetlvmVCD4bZNahQMTehs+TyCOp+nAimY+LscPG92VA7ETwOJ
inhdEUcPAy+PJk9oNSrOMPG1qrv6AWyz6AmpeRLJqDss61TRQLMhwNlsyEexkYiJ
9T9fAnsXd6NgzgHvVPSJ578XmfEAqFDsYcrN9zbwW+Py4oYIXKO0tNFdRdiyxn3z
7UEpkHUpNVS/4G83zyRun3/oAN29w5zeJ2COdDNMQhUWQ7gGYJWPzHUn92jKCx2y
iivVoLJJav/6oSfq7RlsZUKVdL7BOIXc7EP1XIu5xWDYMvEpEzvI+pM9tpMvi0S8
EQs0CPvbv9QsgZ89wor+CFpZ3OFRVAxUD7D21SYlADSkw0S5jkG9ep1yAoK0uLxs
aqXcpv8W+AFmRugQh7glHstOVwrj/7P4F0p8wikAs3CsrQnruofScYHeDOu6qqmm
hQ7mJKF3QaYUyap6Ra3WW4ZXe5hmX3laWUHfUcMrTj/g2BSYjquC5c3+tlZSyXar
k/WhZUxVO1qA8WB8HG56CahTohjLuMa991m9vSCclp+FCDATdq/mIucZDMATTkRD
nx8U6Squ5b451uRIxtT/nI5ZbwzfyS2E0c+kAda5JmDYgE7RqN6u1QqrvWDPgLjo
QvI7bTZn261QGPoOt3Vh
=I+NX
-----END PGP SIGNATURE-----
11 years
New packages
by Brendan Jones
Hey all,
just a heads up on some new updates recently passed review and hitting
f17/f18 update testing in the next week:
guitarix-0.25.2 - in case you missed the new 5 amp LV2 plugins of 0.25.1
there's three new effects plugins with this minor release as well
(booster, autowah and tubescreamer). Upstream welcomes feedback so don't
hesitate
lv2-fomp-plugins - port from LADSPA - 13 plugins: 1 auto-wah, 1 EQ, 3
chorus, 5 filters, and 3 oscillators.
radium-compressor: an intuitive QT compressor with an awesome UI --
child of the radium project, built with faust.
Brendan
11 years, 1 month
DreamStudio Audio Indicator
by Christopher Antila
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi:
Just wondering if people knew about this:
http://www.dickmacinnis.com/dreamstudio/wiki/index.php?title=Audio_Indicator
Seems like we should try to use (or extend) this or Cadence, rather
than developing yet another solution... unless there's some reason I
don't know.
Christopher
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
iQIcBAEBAgAGBQJRIbATAAoJEGpo1cWDqVnYe4cP/jwId7eJ2bbZFfa2G9tJpR2a
XzRIgv1BHOYeSFdKCP1Mpix6eI7DkXvWOrX5j34/ez2junB3HH+hR9SXBTYRoOZe
Vg3Zufz6YPkzAEGuG5uZ+anXv6mJbmqhb5aOzyDzqXDnoLjw+z9cjbGJMfw/nGDE
LlLm32iagQcTpg8a9NljcB9NBI28YbtlhmAnQ/l1FtOQbyxCS9agMuBbzCrziU0d
GsVPLUSt9QGLljszaoJC3o+qmSbH24idn60225eXzKBPOk0ma4mZxv6bLX9otwSB
fJhza/yb3MwrhXvI0RTHgPXNd1JnegEhw2p1LDCtYYvEe9HnqeCtpTm+oduMFcmJ
i7NzPxcduO7rSCrIn2ra/jxePPiv7/Pg80DqCNMgEbv6R6XLRLAaZhh26jWjgqpZ
BFgT13W9gQlnWHZ/7nYHsgaZKU61+jAby+G1gw7i93p+Fa076V+5cA+4JtzvRLF7
l++pIPw9bmVDMgaWaD+AJPhSz8VYrNGImTTiOGD1KrYCIyREJ6QyqPvH4ScMN6dx
r3rwwxNMqC74RIZ96buGcaYzy5+NjAQa4P40SjbGKLfDnXsjvqZIv/TOyMMnqoCG
v9r2RByafTkuTG18A1GrmvNB6gS7TTeopXfEzPX0+VDmw32yY3PB5xS5SbEeocut
Lc8xGBzqIRKQBWkAHAw+
=m51U
-----END PGP SIGNATURE-----
11 years, 1 month
Re: [Fedora-music-list] GSOC announced
by Christopher Antila
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 14 February 2013 11:28:31 Brendan Jones wrote:
> On 02/14/2013 01:37 AM, Christopher Antila wrote:
> > I'm obviously supportive of any attempt to improve documentation of free
> > software, but we have to keep in mind that this is Google Summer of Code,
> > and they only want "code"-centred projects. When I wrote the Musicians'
> > Guide, it was part of Fedora Summer Coding, in a year when Google wasn't
> > involved.
> Well it could very well be a coding project. Think of "packaging" the
> musicians guide with project files and sample templates.
I really don't see this going well, unless...
> It could even be interactive (ie. clicking on a link would launch said
> software with packaged project file etc).
... unless somebody comes up with a truly excellent idea like this one.
> I'm thinking this is probably a project which other distro's could use
> as well. I've been talking to the UbuntuStudio maintainer and he is keen
> to link to our stuff as well,
Okay, this is starting to look promising!
> so perhaps we can float a project that requires building and installing the
> docs + project files + samples in locations defined by what you pass to the
> makefile. That's where the coding component would come in - packaging is
> considered coding.
It is?! Well even so, this "packing" thing is a pretty boring project. But why
do you keep talking about packaging, anyway?
> Here's what Len Ovens, one of the UbuntuStudio maintainers had to say
> about the Musicians Guide:
>
> "It is far more detailed than any of our documentation. A great job. It
> certainly makes me realize how far I have to go in documenting things."
Wow--I'm flattered!
> Seems like a shame to duplicate effort. I certainly have used the Arch
> Wiki many times to obtain the perfect audio setup.
I've used the Arch wiki on many an occasion too (though strangely never for
audio documentation).
> Be great to have documentation which is dynamic, interactive and that caters
> for different distro peculiarities.
Yes, and this is again the beginnings of your great idea.
> I pretty much know nothing about documentation. How does it work for
> Fedora, can you explain the workflow?
For the Musicians' Guide, it generally goes like this:
1.) Have an idea and decide how to write it.
2.) Write a text-only draft of the idea.
3.) Put DocBook XML tags in where appropriate.
4.) Copy-and-paste into the appropriate section.
5.) Send the document for translation.
6.) Use Publican to generate the various output formats.
Fedora documentation is usually published in four formats: HTML, HTML (single
page), PDF, EPUB. Publican supports other formats. One result of this is that
the same DocBook source code is used to generate all the formats, so we are
advised against things that are only effective in one format. An example of
such a thing is that we write out the whole URL rather than "click here,"
because somebody printing a PDF obviously can't click on paper--they would
need to type the whole URL.
For documents that interest Red Hat, there's a more complicated process
involving paid writers, editors, and translators.
> > Also, I just noticed that---although I published it and it is technically
> > available---the Fedora 18 Musicians' Guide isn't properly listed in the
> > menu on Fedora's Documentation website. I'll see what I can do to fix
> > that!
> I did notice that. Thanks.
It's fixed.
- ----
And finally, here's the idea Brendan inspired.
I think any packaging attempt is going to end badly because of our limited
resources, and the reality that well-maintained packages require periodic,
dedicated maintenance. Not to mention our "cross-distro" aspirations. But
there's a better way.
We could develop a web application that dynamically adjusts for distribution
choice and integrates multimedia content. We could host it on Red Hat
OpenShift. We could have the student develop an extension/module/something for
Publican that would generate this web app automatically from pre-existing
DocBook XML files. Obviously, this wouldn't be able to launch applications on a
desktop computer (yet).
But there are several important advantages:
- - developing for Publican is a significant coding project,
- - all DocBook-format documentation could be built into a web app,
- - it's cross-distribution,
- - it doesn't involve packaging (although Publican does already output RPM
packages of documentation).
Christopher
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
iQIcBAEBAgAGBQJRHaPCAAoJEGpo1cWDqVnYsB8P/1jc0nXNmlyCUJkc+yDuyozZ
ic8ja+VmtTQCm48dOCU+TjBElbJ9OfGm0tzdYvEtJlokWgqgxZ1397fWP0RJ4EEu
pgkld+wvznxT2x3FYFJihCcdEcU6+Vs6wKjTpOgAW2cNGUg46CSjCai2k2TGoSoJ
3mJI9b0W1XYZevM3NpiKBuHGZUu2RDtr+M1IQ+WuhHfj3Mxd74zpxFCLy76vRq34
5LZrBYq1bY2mb5rU5VbJhfyvtm0CqreaHhp9/6gqtodyjI6SHtZcQaulw4i2VzDp
gUgdyCoxOCbr9XeaSrithWDoOP/YXiQSpwafYdVRbApsyNHl580FVeLL+CvLWEdD
8YgWbqSu3sWTln+CLg4GSo+iz8hsl048+6jYwFksHW5LZEZXmXLEvrZbkrSTEjcm
Sma4QdyQIrf1zLxk7jd02L+2uDscrW2OU7/dTvrXjwVXlt7o51r9BBMmPo4Wwm6O
FYEm7vkCzqilYVaO0TTDEO7N8bVrM+uAOY2312tz3IWNngNJYKEVC70oG7TJ11su
RV3uB7MsM3MoYXwhXpfbk+RdxlDc/rSSpJz3N6gWuQivxtW6Yvijjazl1CNIZlxm
YDM2NBAsf6ISvN9u0s2CQop1jFMRRkzItuOM3ds0weHiIKpOzCnQIdJI4Hx52q7g
2cYwDtO2tZKi/OJmbJC6
=GhvG
-----END PGP SIGNATURE-----
11 years, 1 month
Re: [Fedora-music-list] GSOC announced
by Christopher Antila
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 14 February 2013 00:01:20 M. Edward Borasky wrote:
> I'd start with the perennial "Why Linux Audio Sucks" threads that can
> be found all over the web, and isolate projects that can be closed on
> deadline during GSOC, then prioritze. ;-)
>
> For what it's worth, I like the documentation project ideas - there's
> too much "code" out there already.
I'm obviously supportive of any attempt to improve documentation of free
software, but we have to keep in mind that this is Google Summer of Code, and
they only want "code"-centred projects. When I wrote the Musicians' Guide, it
was part of Fedora Summer Coding, in a year when Google wasn't involved.
Also, I just noticed that---although I published it and it is technically
available---the Fedora 18 Musicians' Guide isn't properly listed in the menu
on Fedora's Documentation website. I'll see what I can do to fix that!
Christopher
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
iQIcBAEBAgAGBQJRHDHjAAoJEGpo1cWDqVnYDCUQAKLcYv0iYxYTMVCw9KYsuQyv
7mOgkP3NKfHOj1AjEq8+QDJM4ArklqMEZ/hrSHYAJ8ZvadaL4k4M44lJhHPb8jGl
vBKHHt4epAn89tqQmOjcKCEO2NpGwkIfMV/ZNa9QMWVMUYH23Z1KiIZI8NpJrtdo
+eaLcRfbFTQ/BEQt5UabCuKbMc4bwl4klQJ/6jqwQawUfWHEgYvL3Rsk9xRjMMVo
lX8LXOZQzmEisINxckVBU5UjUY093reBmsZ9fud2zFxw1CmPM3yrnARuxkonMczE
peKvC5fY65NZ/1doF8961DxHz+NG/15JXlCbbvwRvMANgEPJXDATVPZzEaAIqOU0
8+gGHe4Qrbuao7t3T8gAirPJJg1MS0xvSGqL/SEBLOeU6iLmBRe4dlEbQDhcUR2A
9GKN7ZWmVdNMmm/AV04rU5AvKjgEozHmMXKD0il8eqQ3IbyMa0XiYOgyxVzI5fnn
NBCtwzueXWAPg1UAei5Ou9qjbx5pu7K4EoO5byonvHecg0JILXfNoKD1pcPurzoP
VKlvCta8BfSpCcM+KHZ9Dt4doWJUMkJN0tqqL0sSHwUwe3URX4aFLQoXdfVc+BLG
CHCBJptnx+M5qDlFC4WDzYuvbiGw9cfRNltfVPGXilQzwus47D8m5uvVlOPtsrKy
9ttKfmy8mVNb8UgF7rTE
=hGt0
-----END PGP SIGNATURE-----
11 years, 1 month
GSOC announced
by Brendan Jones
Hey all,
GSOC has been announced for this year. If you have any ideas for the
audio SIG, add them to the ideas page [1].
We lumped Jorn with a lot of ill-defined stuff to complete last year,
and yet we still ended up with a nightly audio distro, which is a first.
One project that comes to mind is finishing off Jorn's fedora-jam app,
but we can only do this if we define exactly what it is supposed to do.
Another I was thinking about was a documentation project albeit outside
of Fedora. More of a Linux Audio user manual, based on what Chris has
done, but packaged as a distro-agnostic project in its' own right (i.e.
with examples, samples, project files etc). Something that can be
packaged for use across all distributions? (the coding component would
be to determine where everything lives - ie. the Makefile, make && make
install etc). Just an idea
I'm sure there are many other ideas to be had. I don't think I want to
necessarily be a mentor this year, but there's more than enough of this
list that will qualify. I would probably throw my hat in for the
ultimate quintessential audio console which finally bridges jack and
pulseaudio in an intuitive manner. jam-control Mach #2. Will definitely
be available to co-mentor
regards,
Brendan
[1] https://fedoraproject.org/wiki/Summer_coding_ideas_for_2013
11 years, 1 month
Re: [Fedora-music-list] All for Db
by Brendan Jones
On 02/10/2013 11:47 PM, twohot wrote:
> no. i ran it as root
> On Feb 10, 2013 12:51 PM, "Brendan Jones" <brendan.jones.it(a)gmail.com
Unless you have a really good reason to you should not run jack as root.
You will run into problems (but it is possible)
Try again as the normal user. Also add the audio group to your logged in
user.
11 years, 1 month
All for Db
by twohot
So I rushed to my Fedora box trying to hum a tune into Audacity in Db
(D-flat) major ... only, I dont trust my sense of pitch. So I decided
to try a virtual keyboard to spot the Db frequency/pitch and was rather
disappointed that Ubuntu was getting all the packaged versions. Bah!
Alright, I compiled one (VMPK) and got jack-keyboard from the repo. The
only problem now is that I have no idea how to start jackd. #jack forum
at freenode isn't helping much. I couldnt even get a sound from ALSA in
VMPK. HELP!
So much for Db and I think we need an active IRC channel
Regards
Onyeibo
11 years, 1 month
Re: [Fedora-music-list] Icon Pack
by Christopher Antila
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Brian:
I'm wondering what these icons are for? If they are indeed intended to be
functional (i.e., they will represent applications/programs, actions, places,
resources, etc.) rather than decorative (i.e., they will be on the splash
screen, desktop background, and marketing materials), I have a few
suggestions.
1.) The drum set icon sticks out because it's much more detailed than the
others. Generally, funcitonal icons should be as simple as posible.
2.) I don't know what source files you're using to generate the PNG images you
sent, but ideally icons should be scalable SVG files.
3.) If you prefer PNG files, you could make different sizes of images, like most
of the icons in the Oxygen set. If you do, when you make smaller icons, you'll
probably want to change the metallic background to a gradient, and as you go
even smaller, into a flat colour.
I'm also not a graphic designer. My comments are things I remember from
reading blog posts and developing icons for my own programs. In my case at
least, it seemed that the more accurately I could depict something, the *less*
obvious it was for other people!
Christopher
On 1 February 2013 06:00:04 Brian Monroe wrote:
> I'll go ahead and work on this tomorrow. I wanted to get a few more icons in
> before I started working on theming, but does anyone have any more
> suggestions/requests for icons before I start? Here's my updated icon
> pack... [Inline image 1] [Inline image 2] [Inline image 3] [Inline image 4]
> [Inline image 5] [Inline image 6] [Inline image 7] [Inline image 8]
>
>
> Looks great! I am away this weekend so don't have time to try them out just
> yet, but here's a link to what Ian has done. If you follow his instructions
> you should be able to test it out with KDM.
>
> I will post something up on my site when I get back if you are unable
> to.
> http://lists.fedoraproject.org/pipermail/music/2012-September/001346.html
>
> thanks again.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
iQIcBAEBAgAGBQJRC/bTAAoJEGpo1cWDqVnYzJ4QAIte0KTL/9lQ70rrLCT+hAPc
7naf/+M+8kKuUfXCedhe/ZYotQ/PB+Chdq+j/AeVaDcHVW1rYuv++H3Kbqf/qMBu
IAr2jLya1WyZGM/K+T/Ys/u+/L8EpcNbpzIUCCJHBta3DGymHZbpaNxiqoGIl/W4
LoQRwDhCQ53PS4fbkofSJlfkvo/gjFTS3SjueGXm+Vro88COkmQWbcmdqULfG5/H
CcbfgTkJRO7hQX0JQpU6i50BWQ1kHDN+B+Rbs4NI+ciFcxByg4XXDrPafvwixQ9A
0A0rAuhVFROhZLzep5AWubr5Ba68hIb4S8XhiVdWWIW4ZXEPP9lIBwk9999QhMCY
aIvgu6siCzzxh0tP7m4vP07VmtXx0UVbAdrbNqwy8jNJCY121+BqSQBZRRKNF6Dc
Wv+N4l23o4s8nTvGQB4OXjsp0PFo/KwQhNh6uEZjVVyUk2+uha73xjb/TqPNP59y
G0MRYLQspo7uBshbEwGOdfxgWhWCjjPDRCB2CDTyHRR7HHKjTIX8mtikXlKRJE16
mZbN3KM83OGKf7k1tlL0OrfE8fnqwQSvOFQ7tGZOjDNwyOsR9Vno506yxYYSfJOk
N/Kxl1ncVXP5eMHksoSPLvz0Fspu7UYqBrMk2Ug1Ph7Cd5EOgxPw0km/keF/dM2C
2Ca8VGL0SL8kPncO8zYk
=hZkU
-----END PGP SIGNATURE-----
11 years, 1 month