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, 6 months
Fedora Audio Spin meet-up at LAC?
by Jeff Sandys
Brendan, Christopher or others interested in a Fedora Audio Spin,
Will you be attending the Linux Audio Conference at Stanford, April 12-15?
If so, we should meet up and discuss a roadmap for the project.
Add your name to the list on this page if interested:
https://fedoraproject.org/wiki/Linux_Audio_Conference_2012
Thanks,
Jeff Sandys
On Fri, Mar 23, 2012 at 11:59 AM, Brendan Jones
<brendan.jones.it(a)gmail.com>wrote:
>
> Hi all,
>
> I was approached to do an interview regarding the Audio spin and the GSoC
> project - hopefully this kind of PR will get syndicated and we can attract
> a bit more interest (or maybe I should stick to coding ;)
>
> I tried to convey that its really early days, subject to change etc.
>
> You can read it here:
>
> http://www.muktware.com/news/**3445/fedora-audio-spin-**
> creating-music-fedora-**exclusive-interview<http://www.muktware.com/news/3445/fedora-audio-spin-creating-music-fedora...>
>
> regards,
>
> Brendan
>
>
>
> ______________________________**_________________
> music mailing list
> music(a)lists.fedoraproject.org
> https://admin.fedoraproject.**org/mailman/listinfo/music<https://admin.fedoraproject.org/mailman/listinfo/music>
12 years, 1 month
Google Summer of Code [was: Thoughts on spin tools]
by Brendan Jones
On 03/20/2012 12:49 AM, Karsten 'quaid' Wade wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> I do think we should carry this back to the fedora-music-list - ideally
> it gets more attention because we need to spread the word, fast. If you
> agree, you can reply back to the list.
>
> On 03/18/2012 01:04 AM, Fernando Lopez-Lezcano wrote:
>> On 03/17/2012 01:56 PM, Brendan Jones wrote:
>
>>> as you've probably noticed I followed up on Karsten's suggestion
>>> to register the Audio Spin as a GSoC project. Fedora has been
>>> accepted so we've got roughly a week and a half or so to refine
>>> our idea(s) and promote it to students.
>
> We should definitely look in to doing more than one project idea, if
> needed.
>
>>> As Karsten suggested this could be a good opportunity for
>>> students at Stanford looking to expand their interest in audio
>>> (and perhaps an opportunity for you to recruit likewise
>>> interested people in helping out with the PlanetCCRMA project?)
>>>
>>> What's the best way (beside the PlanetCCRMA mailing list) to
>>> promote the spin in this sphere? Any tips are really welcome - I
>>> must admit its been a good 15 years since I was a student (apart
>>> from language school this last month - tough going on top of my
>>> normal work week , sheesh).
>
> Get people on f-music-list and other CCRMA lists to blog about it.
> Maybe write up a canonical blog post others can refer to - gives the
> entirety of the spin concept and how students can help make it happen.
>
>>> At first I was thinking that the GSoC idea would be a good way to
>>> recruit packagers/technical expertise but the more I think about
>>> it, we should probably expand the idea to those interested
>>> learning more about open source communication in general. What I
>>> mean is we could create a role here for someone to ensure the
>>> dialogue in the Fedora audio community keeps rolling, tags bugs
>>> for the spin, and follows up on milestone progress toward the
>>> final goal.
>
> Just speaking statistically, most students don't stick around the
> project after the summer is over. So a student could do some of the
> seed work that would support someone doing that role ongoing,
> including just working with that person directly (you Brendan? what
> could you do if one or two students were working to get you ready to
> maintain a new Fedora/CCRMA relationship?)
>
> I agree with the idea of focusing on open source communication, and we
> need to realize that 25% to 50% of the project time might be taken up
> with communication - just because the student projects cover the
> entire summer doesn't mean we should expect 40 coding hours per week.
> A week is going to look more like: research, ask, wonder, ask more,
> research more, code a few hundred lines, send to the mailing list,
> chat, debate, decide, code some more, research, ask, then finish part
> of a section. Learning to interact with the project - Fedora, CCRMA as
> an upstream, and other upstream projects - is a huge part of the
> learning for the students.
>
> So consider all that when working out what can be done.
>
> When talking to the hundreds of other projects that get together at
> the annual mentor summit in Mountain View, you hear a lot of values
> that go beyond "code received." These are programming student and code
> is important, but it's only part of the scenario. We've had very
> packaging-focused summer coding projects before, including work done
> for the KDE Spin.
>
>>> If you are interested you could also list yourself as a mentor if
>>> you can spare the time.
>>
>> I can always help...
>
> Co-mentoring can work very well, just make sure that you have one of
> you checking the schedule, checking with the student(s) regularly, and
> so forth - managing the drum beat.
>
>>> What do you think, I've copied Karsten on this as well.
>>
>> Well, the Planet CCRMA and Fedora Music lists are obvious places to
>> look for interested users. I could also advertise in our
>> local-users and staff CCRMA mailing lists. Your GSoC url would be a
>> good starting point for the goal of the project. Do you know how
>> GSoC projects are supposed to work? (sorry, I don't)
>
> Encourage people to spread the word - it's a great deal for a student,
> especially one where the US$5K (iirc) goes a bit farther.
>
> - - Karsten
(Thanks Karsten I have forwarded to the list)
Fedora has been accepted as a Google Summer of Code Project. We have
added the Fedora Audio Spin as an idea [1]. At this stage the idea only
outlines a packaging role(s), but I have been discussing with Karsten
and Fernando that it might be a good idea that we expand on the role to
cover all aspects of the project, not just packaging and technical
issues (see above).
I think this could be a really good opportunity to provide the Audio
Spin with a formal process and some much need momentum.
Here's what I think we need to start discussing:
* how can we expand upon the role. We are not limited to one idea here.
We could create a new one to cover other aspects of the project. Tasks
that will need coordinating down the track are:
- documentation / wiki's / musician's guide / community wrangling
- testing the kick starts
- pushing the spin through the acceptance process
* how can we promote the idea to students. What mailing lists, webblogs,
forums etc can we use to attract students to the task (I have been
approached by one site for an interview already - this kind of thing if
we can get it out quick enough)
* potential mentors. Not just technical here, if we create further roles
we will need to co-mentor those as well
* anything else? this is just a start
I will have some time a little later in the week to go over this in more
detail, just wanted to start the ball rolling. We have a week until we
start receiving student submissions.
Brendan
[1]
http://fedoraproject.org/wiki/Summer_coding_ideas_for_2012#Fedora_Audio_C...
12 years, 2 months
New audio spin tracker bug
by Brendan Jones
Hi all,
for convenience I've created a tracker bug to tie all of the Fedora
Audio Spin related bugs together [1]. These will mainly be review
requests, but also any other change request / bugs that impact us in the
coming months.
Add this as a blocker to _any_ new audio packages so we can review them
for inclusion later. I've already added mine and a couple of others.
Also add to anything that you think is relevant to the spin or in moving
Fedora Audio forward in general. Bugs that are likely to be fixed in the
short term by packagers are probably not relevant here, but we do want
to track any updates which have wider implications.
The alias is FedoraAudio and you can add it in the 'Blocks' field.
[1] https://bugzilla.redhat.com/show_bug.cgi?id=805236
regards,
Brendan
12 years, 2 months
PlanetCCRMA vs. Agnula vs. Fedora Music etc.
by Kyrian
Folks,
Apropos of this fedora music spin, it would probably be good if someone
could clarify how it all fits together, what's (in terms of package
sources, websites, etc) deprecated, what's currently relevant, etc. I'm
still on the PlanetCCRMA list(s), but I seem to recall Agnula somehow
morphing into that, and now I'm just horribly confused about what's what.
Even just a reply to this message would allow for it to show up in
Google and hence help people who search on the subject.
K.
12 years, 2 months
Thoughts on spin tools
by Brendan Jones
Hi all,
I been thinking about what we need to do differentiate the audio spin
from a just a collection of audio packages in addition to the spins we
already have.
We really need some kind of UI or set of tools which tries to tie
everything together, allowing for the coexistence of jack/pulseaudio (or
not), multiple sound device configurations and context switching between
audio and normal desktop use. I've mapping out such an application and
in my travels have come across laditools [1] and kxstudio's cadence [2].
Good to see that there have been some recent efforts in this area.
Perhaps we can leverage of these.
I'd be really keen to hear other peoples experiences using these tools.
I'll start building them locally here when I have the time but
personally haven't put them through their paces as yet.
We also need to collate all the tips and tricks we've all picked up
along the way. Those that can be made generic we can ship in a
fedora-audio-tools package. I'll set up a wiki page (in the next week or
two) just to record these and we can collate them together later. Here
I'm thinking alsa device settings, pulse scripts, qjackctl start/stop
scripts: anything that people have had to create themselves to get their
systems in a position to be productive for what they want to do.
Footnote: some people have made some very valid points to me regarding
the audio spin w.r.t pulseaudio. I think if this project is going to be
widely accepted we will need to cater for it. Having said that, I can
see no reason why we can't ship a minimal audio spin as well,
pulseaudio-less sitting on top of a very light DE. The aforementioned
tools should ship with this as well.
regards,
Brendan
[1] http://repo.or.cz/w/laditools.git
[2] http://kxstudio.sourceforge.net/KXStudio:Applications:Cadence
12 years, 2 months
Re: [Fedora-music-list] Good hardware specs for a "Fedora Music" box?
by Kyrian
>
> Hi:
>
> What do you plan to do with your audio workstation? As you can
> imagine, editing one file with Audacity is very different from running
> a SuperCollider server for many users while simultaneously recording
> its output with Ardour *and* broadcasting it on the Internet.
>
A very good point indeed.
I would like to be able to record stuff from guitar, midi-keyboard,
microphone, DJ setup (via line input I suppose), and then edit the
results with the appropriate applications. Not all at once, but maybe
1-3 inputs at a time. The ability to play in real-time through the
computer's output would be very important I think as I reckon it's much
harder to work any other way.
That's all I can think of right now. I currently have an SB Live with
the LiveDrive thing, which has all the inputs I need, but I am thinking
in terms of general system horsepower (RAM/CPU/disk etc). Finding a
supported sound card it's really a problem, I'll just go with M-Audio
for that. But I would like to know if I need to get one to do what I want.
K.
--
Kev Green, aka Kyrian. E: kyrian@ore.org WWW: http://kyrian.ore.org/
Linux/Security Contractor/LAMP Coder/ISP, via http://www.orenet.co.uk/
DJ via http://www.hellnoise.co.uk/
Human Rights left unattended may be Removed, or Destroyed, or Damaged
by the Security Services.
12 years, 2 months
Good hardware specs for a "Fedora Music" box?
by Kyrian
Folks,
I know what hardware spec I'd put in a server, and what spec I'd put in
a standard workstation, but can anyone give me some idea of what a
decent spec is for a Fedora Music / PlanetCCRMA / etc workstation is
please? Do I really need a quad-(or more-)core system? what about RAM?
etc? Assume I've done all the sane things like install Jack, kick
Pulseaudio to the curb where it belongs, disable unnecessary services,
etc. My current box is an "AMD Sempron(tm) Processor 3000+" based
system, but it seems to struggle with even the most basic tasks, and I
struggle to see why. I want to be in a situation where I can be 75%+
sure that the hardware is fast enough and not causing me issues.
I don't hold with this (apparent) Microsoft philosophy of that the newer
version of windows is faster, but that's because your new PC that comes
pre-installed will be faster by virtue of Moore's Law, so I usually
refrain from upgrading hardware too quickly, but this whole Fedora Music
thing is a different ball-game for me, where I really genuinely might
need the extra resources for a useful purpose.
K.
--
Kev Green, aka Kyrian. E: kyrian@ore.org WWW: http://kyrian.ore.org/
Linux/Security Contractor/LAMP Coder/ISP, via http://www.orenet.co.uk/
DJ via http://www.hellnoise.co.uk/
Human Rights left unattended may be Removed, or Destroyed, or Damaged
by the Security Services.
12 years, 2 months