Greetings:
I recently submitted another article for my monthly column at Linux
Journal on-line, it should show up within the next few days. I wanted to
let LA* folks know that I've placed the article's two short example
files here:
http://linux-sound.org/lj-seq24-examples.html
They aren't finished pieces, nor were they meant to be (though I'm
liking them enough to maybe work on them some more). I made them as
examples of what can be done with seq24 and a batch of Linux softsynths
(and one VST plugin). I had an enormous amount of fun doing these
pieces, and I want to extend great thanks to Rob Buse for seq24 and Nick
Dowell for amSynth.
The state of things in our little world is getting to the point where
it gets harder to write about the stuff because I'd really just rather
be making music with it. Vast thanks to all Linux audio developers for
making dreams come true. You guys rock, every one of you.
Now if I can just get seq24 working with JACK... ;)
Best regards,
Dave Phillips
Hi.
When I was at LAC2005 I made a lot of pictures. I
sorted the pictures that are interesing for the people
who participated LAC2005, I corrected them (rotate,
etc.) and I uploaded them at:
http://zynaddsubfx.sourceforge.net/doc/PicturesPaulNascaLAC2005.zip
The pictures are in a single zip archive (55MB) and
there are 215 pictures;-)
MD5SUM(PicturesPaulNascaLAC2005.zip)=8c6877789e5c303d979d0dd85f73dc79
SHA1SUM(PicturesPaulNascaLAC2005.zip)=b4f18efd4eb51dee711e6b7d1c1fb183048a2479
Please note that this link is NOT permanent and very
likely the pictures will be available at linuxdj.com.
Hope you'll like it.
Paul Nasca, the author of ZynAddSubFX.
__________________________________
Discover Yahoo!
Get on-the-go sports scores, stock quotes, news and more. Check it out!
http://discover.yahoo.com/mobile.html
vanDongen/Gilcher wrote:
> If there are little brown spots on the top of some condensers on the mobo,
> then they are fried and you have to get a new one.(unless you fancy soldering
> multi-layer boards) Apperently some factories saved a few tenths of pennies
> by using substandard parts.
Steve Harris wrote:
> ... but If the motherboard is oldish (couple of years or so) then its
> worth eyeballing the motherboard for bulging capacitors, I lost my studio
> PC to this and we lost a load at work.
>
> The tops should be slightly concave and clean, if theres any sign of brown
> gunge (technical term) or bulging then the motherboard is a gonner.
>
> There was a bad batch of capacitors for a while from a major manufacturer,
> but I suspect all the bad boards have blown allready by now.
There was a bad batch of capacitors doing the rounds a few years back. I've
seen a large number of MSI K7T Turbo boards die this way as well as two HP
boards from the same era - around the time of the Athlon-900. It wouldn't
surprise me if Dave's mainboard is suffering from these bad capacitors since
the symptoms are very close to those I've seen in the 20 or so failures I've
witnessed: the machine gets less and less stable until finally either it
doesn't boot (mostly) or the offending capacitor(s) explode (as has happened
twice in my experience).
I've been told from a reputable source that it wasn't actually the mobo
factories which did the dirty as such. An electrolyte formula was
apparently stolen from a factory, copied at another and then stolen *again*
and passed to a third. It was the resulting capacitors from the third
factory which, falsely branded as a reputable brand, found their way into
all these mainboards which have been dying over the past 3 or so years.
I started seeing mainboards failing in machines which run 24/7 about 3 years
ago. Since then, mainboards with intermittant use have been showing up with
the same fault. The last one I saw suffering this problem surfaced only a
few months ago, so there are still some out there. From my observations it
appears related to power-on hours which, given the failure mode of the
capacitors, isn't all that surprising.
Of course this is all cold comfort for those unfortunate enough to be stuck
with a faulty board.
Regards
jonathan
On Tue, 7 Jun 2005 10:18 , Paul Winkler <pw_lists(a)slinkp.com> sent:
>On Mon, Jun 06, 2005 at 04:12:27PM -0500, Jan Depner wrote:
>> I just have to respond to this. I have been writing code for 27
>> years and every time I get a neophyte programmer in they want to cut
>> corners to save programming time. Here's the bottom line - if it saves
>> you a day in coding but costs the user 3/4 of a second in application
>> time would you consider that a good tradeoff? Not if you have over 100
>> users and they're having to deal with that 3/4 of a second 20 or so
>> times a day, every day for a year. Remember, it's only hard for you to
>> program it correctly once - it's a PITA for the user many times a day.
>
>I sort of agree, with the very large caveat that "once" is unlikely.
>The time to write the code is often dwarfed by the time to maintain
>the code. So your optimizations had damn well better be as readable
>as you can make them, and well-commented.
>
Too true. That's why I comment like a madman ;-)
Jan
>From: Olivier Guilyardi <ml(a)xung.org>
>
>http://www.samalyse.com/labs/edrum
Because I don't want build anything, I would record
drumming on whatever I find from our kitchen.
The software should detect the pitch and volume
of the hits.
If only one microphone is used, choosing differently
pitched objects for the controller makes it easier to
separate the objects.
Juhana
--
http://music.columbia.edu/mailman/listinfo/linux-graphics-dev
for developers of open source graphics software
Greetings:
I've been having some problems with my desktop machine during and
after booting into Planet CCRMA RH9. At first I started getting some
kernel panics booting into the system, then I started having trouble
during operation of the system. X would suddenly freeze shortly after I
started it, usually after the first mouse move.
Okay, so I don't panic because I have another drive in the same box
running FC3, so I figure I'll just boot into that system instead and
transfer files before everything heads south. At first everything seemed
fine on that drive, but soon after I started using it FC3 started
showing the same symptoms with sudden reboots and total freezes of the
machine.
I've been able to transfer a lot of stuff to my laptop via the local
network, but mounting the RH9 drive is very dangerous, things can freeze
at any moment. Alas, there's still stuff on that drive that I'd like to
retrieve.
So there's something wrong with the box. Can anyone point me in the
right direction to begin troubleshooting this machine ? Could it be RAM
? The graphics card ? Or what ?? And how can I test things on the
hardware side, i.e., what utilities are indicated ?
Any and all suggestions vastly appreciated.
Best,
dp
Hi. I'm a lurker from the Open-Source Speech Recognition Initiative.
We are starting to collect voice samples and need an audio program that
can segment speech by word, or attempt to, by recognizinig all the
silences and placing markers at each location.
Any ideas?
Thanks for any and all input.
Susan R Cragin, Clerk
OSSRI
Open Source Speech Recognition Initiative
http://www.ossri.orghttp://harvee.org/mailman/listinfo/ossri
A Massachusetts Not-For-Profit Organization
On Wed, Apr 27, 2005 at 08:13:21AM +1000, Luke Yelavich wrote:
> Some distros, like Slackware do not use pam. How could this patch still
> be used?
I've written a small setuid utility which gives access to the new resource
limits on an otherwise unpatched system (so long as a kernel with the new
resource limits is running, of course). It should work regardless of
whether PAM is installed, but my main motivation in writing it was to allow
me to access the new functionality under Slackware 10.x (with a 2.6 kernel).
Grab the tarball from
http://www.physics.adelaide.edu.au/~jwoithe/set_rtlimits-1.0.0.tgz
Sorry, no homepage yet. Read the enclosed README and manpage for full
details. In short, a simple text file /etc/set_rtlimits.conf is used to
configure which users (or groups) can run which programs with elevated
realtime/nice priorities. The maximum priorities requestable is limited on
a user+program basis, so a single user or group can have different
maximum priorities for different programs if this is desired.
Once set up, using it is as simple as inserting set_rtlimits in front of
the program you wish to run (and its parameters). For example:
set_rtlimits -r=100 /usr/local/bin/muse -a
will run muse with the dummyaudio driver with a maximum realtime priority
resource limit of 100. Note the full path to the program to execute is
required so ordinary users can't just substitute their own binaries of
the same name as "allowed" programs.
It might not be the most secure program written (although I've tried to
avoid gaping holes), but it gets the job done for me.
Regards
jonathan
With the recent adoption of the realtime rlimits patch into the mainline
kernel, people have needed a way of utilising this for their music software.
There is apparently a PAM module out there which can be used if one's system
uses PAM, but for people on Slackware (which doesn't use PAM) - and perhaps
other distributions as well - this is not an available option.
set_rtlimits is a small program I hacked up over the weekend to allow
controlled non-priviledged access to realtime scheduling through the new
RTPRIO resource limit. set_rtlimits needs to be setuid root but it only
runs at elevated priviledges when setting the resource limits. Furthermore,
the users who are permitted to use set_rtlimits are controlled through a
hardcoded central configuration file (/etc/set_rtlimits.conf), as are the
programs those users can run via set_rtlimits and the maximum realtime and
nice priorities the users can request for each program. Programs must be
specified using absolute paths, so a malicious user can't just run their own
ardour binary, for example.
There is no homepage for this yet; simply grab the source from
http://www.physics.adelaide.edu.au/~jwoithe/set_rtlimits-1.0.0.tgz
Documentation is by way of the included README and manpage.
Note that this is not polished software. It's not autoconf-ised, although
hopefully it won't require too much tweaking to compile on a variety of
systems. It probably isn't written in a very portable way, and although it
poses no security issues to the best of my knowledge (beyond the usual
issues with setuid root programs and realtime priorities) it has not been
extensively audited. Having said that it gets the job done for me and might
be useful for others. My time is limited at present which is why the rough
edges remain.
Development was done under Slackware 10.0 running kernel 2.6.12-rc5. Using
this program I have successfully run Ardour 0.9beta29 and muse 0.7.2pre1
with Jack 0.99.73 under 2.6.12-rc5 for short periods.
Bug reports, improvements, suggestions and patches are welcome; send to the
email address included in the tarball documentation.
Regards
jonathan
Hello everybody!
We are a group of students at "Freie Universitaet Berlin".
As part of our computer science studies we are going to do
a survey facing the use of design patterns in communication.
Examples of design patterns are "Abstract Factory",
"Singleton", "Composite", "Iterator" and "Listener".
If you know what we are talking about, you are welcome to
take part in our survey.
It takes about 5 minutes to fill out the form.
Just jump to:
http://study.beatdepot.de
If you agree, we will send you the results of our survey.
Thanks in advance for your participation!
And sorry for the interruption of your discussion.