January 22, 1998
From: Dan Timis <timis(a)museresearch.com>
To: <linux-audio-dev(a)music.columbia.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by roar.music.columbia.edu id gA55dDA19818
Subject: [linux-audio-dev] Job in the Bay Area (Menlo Park)
Sender: linux-audio-dev-admin(a)music.columbia.edu
Errors-To: linux-audio-dev-admin(a)music.columbia.edu
X-BeenThere: linux-audio-dev(a)music.columbia.edu
X-Mailman-Version: 2.0.13
Precedence: bulk
Reply-To: linux-audio-dev(a)music.columbia.edu
List-Help: <mailto:linux-audio-dev-request@music.columbia.edu?subject=help>
List-Post: <mailto:linux-audio-dev@music.columbia.edu>
List-Subscribe: <http://music.columbia.edu/mailman/listinfo/linux-audio-dev>,
<mailto:linux-audio-dev-request@music.columbia.edu?subject=subscribe>
List-Id: The Linux Audio Developers' Mailing List <linux-audio-dev.music.columbia.edu>
List-Unsubscribe: <http://music.columbia.edu/mailman/listinfo/linux-audio-dev>,
<mailto:linux-audio-dev-request@music.columbia.edu?subject=unsubscribe>
List-Archive: <http://music.columbia.edu/pipermail/linux-audio-dev/>
X-Original-Date: Mon, 4 Nov 2002 21:35:37 -0800
This may not be a perfect fit with Linux Audio Developers, but there is
no Linux Audio Administrators list. If you are not interested directly
you may know someone who is.
Here it is:
----------
Advanced Systems Programmer  Job Requirements
Muse Research, a startup music and audio products company located in
Menlo Park, is looking for a self-motivated and creative Systems
Programmer. Muse is developing cutting edge software/hardware devices for
musicians and needs your Linux and system administration skills.
Responsibilities
Linux Maintenance:
€ Keep customized Linux build up to date and adapt it to hardware
requirements
€ Make sure our Linux is optimized for performance and provides the tools
users need
€ Work with hardware driver contractors to install their drivers and
verify their work
€ Work with hardware team to develop shell scripts or find programs to
test hardware functionality
System Administration:
€ Perform light administration on small office LAN
€ Help with software installation and hardware troubleshooting
€ Set up and maintain web based applications  a bug database, CVS, etc
Steve wrote:
> Date: Sun, 3 Nov 2002 16:39:02 +0000
> From: Steve Harris <S.W.Harris(a)ecs.soton.ac.uk>
> Yeah, I'm thinking we're not tackling it right, if behringer can knock out
> a virtual amp harware box for E150 it can't the that cycle hungry.
There's a good chance I could get my hands on a Behringer V Amp 2 for as
long as I need it. If I did, I'd be able to run whatever signal I liked
through it and try different amp/speaker settings, different gain levels,
etc. and produce a lot of data that would hopefully be of use in trying to
produce some sort of "amp modelling" ladspa plugin.
I'm open to suggestions as to what would be the most useful things to
measure, and what to vary across measurements.
My first thoughts were:
- a range of pure tones, say starting at 440Hz and going up 3 octaves,
- ~5 gain levels,
- ~5 amp/speaker simulations,
That'd give us 100 "data points" to work with when it comes to testing our
models.
Comments anybody?
Stuart
Hi all,
I'm just trying to tweak SpiralSynthModular's threads to be a bit more
efficient, and I can't seem to find much info regarding thread priorities and
such.
I have two threads, a GUI one and an audio one. I can hand the audio thread
over to Jack which works fine, but I'd also like to be able to run ssm in
normal user mode and standalone without jack. I think I have two questions:
1. Is there any way to prioritise the threads running as a normal user
(SHED_OTHER) my man pages suggest not, which is quite annoying. Should I
"nice" the GUI thread down in priority?
2. What is the correct setup for SHED_FIFO? What priorities should I run the
audio and GUI threads at, and should the GUI thread use SHED_FIFO too?
Thanks for putting up with my ignorance :)
Dave
: www.pawfal.org :
How did this end up here?
Anyway based on the discussion had so far in this thread I have updated
the JACK user Howto to be more precise and yet somehow broader and
muddier at the same time :)
--
Patrick Shirkey - Boost Hardware Ltd.
For the discerning hardware connoisseur
Http://www.boosthardware.comHttp://www.djcj.org - The Linux Audio Users guide
========================================
"Um...symbol_get and symbol_put... They're
kindof like does anyone remember like get_symbol
and put_symbol I think we used to have..."
- Rusty Russell in his talk on the module subsystem
>I wouldn't go as fas as to blame any developers for this. ALSA is being
>integrated in the mainline kernel and that by itself should keep
>everyone busy.
>I think its somehow the duty of the people who figured out how to
>configure it in an easy way to write it up (cfr. Patricks quicktoots
>section).
>I'm willing to do just that.
>The question is, what is the best place to write these things up ?
>Do I start to work on Debian specific documentation, or is it better
to >help on some general alsa documentation ?
I think it would be best to have this info in the alsa-docs.
Here's what I consider still needed to make the alsa-docs complete:
- A paragraph on using alsaconf.
- Anything that is distro specific. Although it might be better to make
a page for this which people can add notes to.
- Any info on using the controls for cards that have them. Specifically
adat, wordclock, optical. I would like to have a section in the template
for this but don't have any cards that use these so cannot test myself.
--
Patrick Shirkey - Boost Hardware Ltd.
For the discerning hardware connoisseur
Http://www.boosthardware.comHttp://www.djcj.org - The Linux Audio Users guide
========================================
"Um...symbol_get and symbol_put... They're
kindof like does anyone remember like get_symbol
and put_symbol I think we used to have..."
- Rusty Russell in his talk on the module subsystem
work with Linux ?
> Tim Goetze <tim(a)quitte.de> writes:
>
> there's a difference though: the usb 1 ms is jitter, there's no way
> to reconstruct the original timing. this in contrast to midi, where
> you can extrapolate the exact event time quite well (provided you're
> looking at a stream of mostly isolated events). oh well, most people
> think 1 ms is below human perception limits anyway.
People who are into this topic might want to take a few minutes
to review Appendix C.1 (pp 66-70) of the MWPP draft:
http://www.cs.berkeley.edu/~lazzaro/sa/pubs/txt/current-mwpp.txt
It basically describes the three methods MWPP provides for coding
timestamps onto MIDI commands when packetizing a MIDI stream. The
goal is that whatever your MIDI source is (a MIDI 1.0 DIN jack,
an algorithmic composition program, etc), one of these three
methods will be the right one to capture the timing as best as
can be, into an RTP packet. Feedback is welcome on the topic,
we're starting to close in "Last Call" for the document, but
there is still a few months left ...
-------------------------------------------------------------------------
John Lazzaro -- Research Specialist -- CS Division -- EECS -- UC Berkeley
lazzaro [at] cs [dot] berkeley [dot] edu www.cs.berkeley.edu/~lazzaro
-------------------------------------------------------------------------
Hi,
I meant of sending midi events from the master keyboard via USB to the PC
which runs an internal soft-synth/sampler.
In that case USB should improve timing because of the bigger bandwidth,
(but will add 1msec of latency due to USB1 polling mechanism as far as I can
understand).
Correct me if I'm wrong.
cheers,
Benno
You wrote:
-----
> Ok if the Edirol keyboards support standard MIDI then there shouldn't be any
> problems using them under Linux, but since USB has a much bigger bandwidth
> than serial MIDI, I that the timing for notes that belong to large chords is
> more precise. Can someone confirm this ?
Not really, unless you are spreading those chords on several separate midi
outputs. If it just one, then it determines the bandwidth available.
Getting things faster to the interface will do nothing because it still
has to send the bytes to the external synth at the same old slow 31250
baud speed.
-----
--
http://linuxsampler.sourceforge.net
Building a professional grade software sampler for Linux.
Please help us designing and developing it.
there has been a massive spam attack against linux-audio-dev yesterday.
expect longer round-trip times and even more anal filtering while i'm
tracking this down.
regards,
jörn
--
Jörn Nettingsmeier
Kurfürstenstr 49, 45138 Essen, Germany
http://spunk.dnsalias.org (my server)
http://www.linuxdj.com/audio/lad/ (Linux Audio Developers)
get the new "blue" version of rtsynth from:
www.linux-sound.org/rtsynth/
enjoy,
Stefan
P.S. An updated jackified version will follow as soon as i can
test it on my machine in RT mode.
_________________________________________________________________
Internet access plans that fit your lifestyle -- join MSN.
http://resourcecenter.msn.com/access/plans/default.asp
> AFAIK the Oxygen8 does not behave as a standard usb midi device, it uses a
> "Midiman protocol" instead, so the standard drivers don't know what to do
> with it. If you connect it and do an lsusb -v you don't see much...
Ok if the Edirol keyboards support standard MIDI then there shouldn't be any
problems using them under Linux, but since USB has a much bigger bandwidth
than serial MIDI, I that the timing for notes that belong to large chords is
more precise. Can someone confirm this ?
BTW: the Midiman site lists Linux as an OS in their driver search page but
nothing comes up when searching for product drivers.
Is their stance very closed ? Do they not even release specs ?
cheers,
Benno
--
http://linuxsampler.sourceforge.net
Building a professional grade software sampler for Linux.
Please help us designing and developing it.