-------- Forwarded Message --------
From: Ralf Mardorf <ralf.mardorf(a)rocketmail.com>
To: linux-audio-user(a)lists.linuxaudio.org
Subject: Re: [LAU] RTC/HPET timer permissions
Date: Tue, 27 Nov 2012 14:00:48 +0100
On Tue, 2012-11-27 at 13:32 +0100, Clemens Ladisch wrote:
> In theory, always. But it might be possible that it forgets to tell
> udev about itself ...
udev btw. is effected by all the temporary arrangements, since it's part
of the systemd packages or distros use outdated version to keep it
independent of systemd packages.
Message: 20 Date: Tue, 27 Nov 2012 10:49:26 +0300 From: Louigi Verona <louigi.verona(a)gmail.com> To: Dan MacDonald <allcoms(a)gmail.com> Cc: Linux Audio Users <linux-audio-user(a)lists.linuxaudio.org> Subject: Re: [LAU] [OT] OT question, please respond by private mail only Message-ID: <CADqqn4-2NmBcORnG2EvoOrDLBC9O+YvLUx33-Xt3LND+k9+zcQ(a)mail.gmail.com> Content-Type: text/plain; charset="iso-8859-1" No, Dan, I am sure he is hunting UFOs. Positive. On Tue, Nov 27, 2012 at 11:31 AM, Dan MacDonald <allcoms(a)gmail.com> wrote: > That's about the most mysterious posting I've ever seen here. Any chance > of a clue what you're up to for us non-pilots? > > Hopefully you're not just trying to wing a discount flight! :) > Maybe he's escaping to Brazil! It's the only answer that makes any sense.
My MUA is broken :(.
-------- Forwarded Message --------
From: Ralf Mardorf <ralf.mardorf(a)rocketmail.com>
To: linux-audio-user(a)lists.linuxaudio.org
Subject: Re: [LAU] RTC/HPET timer permissions
Date: Tue, 27 Nov 2012 13:53:34 +0100
On Tue, 2012-11-27 at 12:54 +0100, Jeremy Jongepier wrote:
> What do you mean by hardware MIDI? External synths? So when only using
> soft synths using snd-hrtimer doesn't make any difference at all?
Yes, that's my experience. Perhaps it's tickless vs not tickless
regarding to IRQ handling of the hardware MIDI or simply the very high
resolution. A coder might give us some insight.
For MIDI internal Linux I guess there are no layers, excepted of bridges
between ALSA and JACK that might cause issues. perhaps I'm mistaken, but
I never noticed an issue for a stable DAW.
> > Usually system timer (default) is the best way to go,
> > hr timer is better, but can cause issues,
>
> What kind of issues?
MIDI jitter.
> linuxmusicians.com Wiki
Take care to keep backwards compatibility, some people e.g. still use 64
Studio.
Other stuff at the moment is in a transition state. You never know what
services to start and stop by /etc/init.d/foo and what by the command
"service".
Better wait with editing until we all are forced to use GNOME3 or Unity
with hard dependencies to upstart or systemd, sorry I couldn't resist,
since current Xfce at the moment is a PITA and the upstream situation
makes me taking a look at FreeBSD now, of cause not for audio and MIDI,
but I will test this too.
Regards,
Ralf
Are there any (aircraft) pilots on the list ?
--
FA
A world of exhaustive, reliable metadata would be an utopia.
It's also a pipe-dream, founded on self-delusion, nerd hubris
and hysterically inflated market opportunities. (Cory Doctorow)
Long ago, I've read many people recommending setting relaxed permissions
on /dev/rtc for using programs like Muse, and I remember back in the
early 2000's even seeing MPlayer requiring this and complaining on the
console when it couldn't get it.
Pretty much all distros now set default permissions of 0600 root:root on
/dev/rtc now, and MPlayer works now anyway. Is it still necessary or
recommended these days for proper operation of audio apps to have a
user-accessible /dev/rtc? Is there a security risk? Do regular users
need write access, or would a mode like 0640 root:realtime be
sufficient?
Also, I notice there is a /dev/hpet node too. Same questions apply
there, since I would imagine HPET gives the best time of all.
--
+ Brent A. Busby + "We've all heard that a million monkeys
+ Sr. UNIX Systems Admin + banging on a million typewriters will
+ University of Chicago + eventually reproduce the entire works of
+ James Franck Institute + Shakespeare. Now, thanks to the Internet,
+ Materials Research Ctr + we know this is not true." -Robert Wilensky
-------- Forwarded Message --------
From: Ralf Mardorf <ralf.mardorf(a)rocketmail.com>
To: linux-audio-user(a)lists.linuxaudio.org
Subject: Re: [LAU] [OT] OT question, please respond by private mail only
Date: Tue, 27 Nov 2012 12:47:56 +0100
On Tue, 2012-11-27 at 10:24 +0000, Fons Adriaensen wrote:
> On Tue, Nov 27, 2012 at 07:31:41AM +0000, Dan MacDonald wrote:
>
> > That's about the most mysterious posting I've ever seen here. Any chance of
> > a clue what you're up to for us non-pilots?
>
> Nothing mysterious. I've some questions to which I don't find a
> satisfying answer on the web, and which any real pilot can probably
> answer without even having to think. It's all about how exactly an
> aircraft reacts when you use its flight controls.
>
> (And googling for 'pilots mailing list' turns up a zillion offers
> to buy lists of email addresses to spam pilots).
>
> Ciao,
Too funny since it's a hobby of rich audio engineers in Germany, near to
my home, Klaus Dieter Keusgen VDT and Dirk Brauner VDT come to mind, so
I guess it's very likely we've some pilots on this list too.
:D
Hi all,
I'm writing this for a friend of mine.
This particular friend is a recording hardware developer that build several
preamps, EQ's, etc.
He is well known in the high end analog gear community and build tools for
the some pretty big names in the industry (e.g. Bob Katz).
So this friend and I were discussing a new hardware analog device with
digital control that he designed and I must say that his idea is pretty
good.
I asked him if it will be possible to control the device from a plugin and
got a negative answer, but he said he would be glad to offer information to
a developer interested in this kind of project.
I told him about Linux, Ardour and LV2 and he was very interested.
I proposed to him to contact the Linux Audio community and see if there is
anyone that would be interested to participate.
Basically the idea is to make an interface for his device in LV2 format.
I don't know how much (if any) money will be involved, so you will have to
discuss these matters with him directly.
Please understand that I cannot give his or the company's name at this time.
Anyone interested please contact me directly so I can give you more details.
Best regards,
Moshe Werner
Hi all,
I have some live concert recordings (some destined for LMA[1]) which
could use some processing in certain sections (usually to cut out crowd
noise and AC hum).
The recordings are hours long, but I only want to selectively process
some portions (often sections inbetween music).
So far, I've been writing scripts+makefiles to drive SoX. I use
the SoX "trim" effect to split out sections, process the sections
indivdually, and rejoin them (often with fade); but I'm wondering if
there's something similar for command-line users which already exists.
I've been considering writing a make-like tool, but would like know if
something existing fills the role. I haven't been able to find
information on using csound for mastering a few sections of audio, but
maybe that could work...
I don't like pointing devices, so it must be 100% keyboard-driven and
easily repeatable/version-controlled. I manage my current
scripts+makefiles via git.
[1] - Live Music Archive (on archive.org)
Thanks for reading!
-------- Forwarded Message --------
From: Ralf Mardorf <ralf.mardorf(a)rocketmail.com>
To: linux-audio-user(a)lists.linuxaudio.org
Subject: Re: [LAU] [OT] LV2 control for hardware device
Date: Mon, 26 Nov 2012 13:18:33 +0100
You should send this to
http://lists.linuxaudio.org/listinfo/linux-audio-dev
For sure many developers are subscribed to LAU too.
IMO it's not OT.
Good luck!
Ralf
-------- Forwarded Message --------
From: Ralf Mardorf <ralf.mardorf(a)rocketmail.com>
To: linux-audio-user(a)lists.linuxaudio.org
Subject: Re: [LAU] looking for command-line/scriptable mastering
software
Date: Sun, 25 Nov 2012 21:40:52 +0100
On Sun, 2012-11-25 at 12:05 -0800, J. Liles wrote:
> On Thu, Nov 22, 2012 at 7:26 PM, Grekim <grekimj(a)acousticrefuge.com>
> wrote:
>
> [snip]
>
> It's too bad the closed source issue has rubbed you guys the
> wrong way. The way I see it, I've invested well over 1000
> hours and a year of work on something which I ask nothing for
> in return except maybe a little respect now and then :)
>
>
> You're not likely to get any respect from this community unless/until
> you release your source code under a free/libre license. Who have
> spent decades and 10's of thousands of hours working on projects that
> we give away freely and openly, your software is irrelevant and your
> request for respect is borderline insulting. If you're truly proud of
> what you've created, then show it to the world. You're not getting the
> feedback you want because no one wants to run your mysterious binary
> blob, and I don't blame them. You're never going to strike it rich
> with this software, so the only legitimate reason you could possibly
> have for not sharing the source code is that you're ashamed of what a
> mess it is.
It's stupid not to share knowledge. Secret recipes are from another
time. If people don't want to share their knowledge, e.g. good or bad
code, it's ok, valuation is stupid too.
Close source code for a open source community is absurd, OTOH the open
source community tends to be dogmatic and to evaluate others often by
exaggerated opinions of them self and prejudices.
AFAIK the community does like LinuxDSP and AFAIK they give away binary
blobs only, I might be mistaken.
It has a lot to do with aversion and devotion. Two people can say the
same, or by a misunderstanding somebody does think person A said
something, but person B said it. The rating isn't neutral, but
sentimental.
Respect has to do with group behaviour only, not with knowledge or
something like that. It's simple dogmatism, nothing more. Such noise is
typical for some Linux lists.