Hello Lists,
I don't know, where ich can fix my little problem. Maybe i 've missed some
explanations and/or haven't read my mails good enough. anyway, i try to
install a linuxbox for audio on slackware
i have installed slackware and patching the kernel 2.6.14 vanilla with
patch-2.6.14-rt2. Then i installed the set_rtlimits1.1.0 software, because
Slackware has no PAM.
First. this must be all for audio in realtime , is this right??
then i have to set the setuid. aus root i have done
bash-3.00$ su
Password:
bash-3.00# chmod ugo+s /usr/local/bin/jackd
bash-3.00# exit
bash-3.00$ ls -la /usr/local/bin/jackd
-rwsr-sr-x 1 root root 206476 2005-11-01 15:23 /usr/local/bin/jackd
bash-3.00$ whoami
soundroom
bash-3.00$ jackd -dalsa&
[1] 3202
bash-3.00$ jackd 0.100.0
Copyright 2001-2005 Paul Davis and others.
jackd comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
JACK compiled with System V SHM support.
loading driver ..
creating alsa driver ... hw:0|hw:0|1024|2|48000|0|0|nomon|swmeter|-|32bit
control device hw:0
configuring for 48000Hz, period = 1024 frames, buffer = 2 periods
nperiods = 2 for capture
nperiods = 2 for playback
bash-3.00$ ps -aux
[..]
root 3202 0.0 0.4 10472 2380 pts/1 S 12:03 0:00 jackd -dalsa
root 3203 0.0 0.4 10472 2380 pts/1 R 12:03 0:00 jackd -dalsa
root 3204 0.0 0.4 10472 2380 pts/1 S 12:03 0:00 jackd -dalsa
root 3205 0.0 0.4 10472 2380 pts/1 S 12:03 0:00 jackd -dalsa
root 3206 0.2 0.4 10472 2380 pts/1 S 12:03 0:00 jackd -dalsa
[..]
bash-3.00$ jack_lsp
JACK server not running
why i can't use jack an normal user? what have i missed? why there are 5
processes of jack? is this a secure way? do i need every application as suid?
How about a software which can combine the outputs coming from
two receivers tuned to the same station?
Typically with short-wave receivers (tuned to distant radio station)
there are problems. With two or more receivers (perhaps located at
different cities and connected via Internet!) the problems can be
reduced and the station signal restored. This kind of signal
restoration must be known already in other contexts.
Strange, I recently read a recent (2000+) paper. They praised
(like having a patent on them) two innovations: (1) an audio editor
could handle non-audio signals, e.g., RF signal, ultrasound, etc.,
and (2) the above kind of receiver combination. The innovation (1)
was discussed at 1997/98 here or elsewhere, and I invented the
innovation (2) at 1993.
Juhana
--
http://music.columbia.edu/mailman/listinfo/linux-graphics-dev
for developers of open source graphics software
Dear all,
this should have come one month earlier, but such is life..anyway:
This mail is to announce the calls for papers/music/etc for the 4th
International Linux Audio Conference (LAC2006).
See http://lac.zkm.de/2006 for more information.
LAC2006 will take place 27-30 April 2006, again at the ZKM | Institute for
Music and Acoustics in Karlsruhe, Germany.
We have tried to simplify things a little bit since LAC2005. There are
calls for papers, demos, workshops, and music. The former category BOFS
has been merged with the workshops. There is no call for project notes
anymore; instead we have the call for demos now. The call for posters
has been discarded.
We hope everybody agrees that this is an improvement and we are looking
forward to many interesting submissions for LAC2006!
Please feel free to forward this email to anybody who is interested.
Thank you for reading!
Frank Neumann and Goetz Dipper
***********************************************************************
Call for Papers
We invite submissions of papers addressing all areas of audio
processing based on Linux and open source software. Papers can focus
on technical, artistic or scientific issues and can target developers
or users. This includes (but is not limited to) the following
categories:
* Computer Music
* Music Production
* Instruments
* Drivers and Sound Architecture
* Audio Distributions
* Generic (Usage, Documentation etc.)
The conference is held in english, so all papers and presentations
will have to be done in english, too.
Length of a paper is 4-8 pages. Papers have to include an abstract
(50-100 words). The abstract will be published separately on the
conference website once the paper has been accepted. Also, papers
should include up to 5 keywords.
In general talks should take 20-30 minutes followed by 5 minutes
discussion.
Please notify us if you need a special technical setup. The technical
standard setup will be:
* microphone (head set)
* projector with XVGA input (resolution 1024x768)
* stereo speaker setup with mini jack input
If you are not able to bring your laptop along with you, please notify
us in advance.
How to submit
* File format is PDF, formatted for A4 paper. Make use of the
templates for paper formatting available at:
http://lac.zkm.de/2006/downloads.shtml
* See our check list to ensure that you do not forget to enclose
all necessary information:
http://lac.zkm.de/2006/submission_instructions.shtml
* Send your paper and all necessary information by 8 Jan 2006
via email to this address: lac2006 at zkm dot de
* You will be notified by 19 Feb 2006 whether your paper has been
accepted. The reviewers may ask you to modify your paper in
order to be accepted. The deadline for the final version is
March 12, 2006.
Important Dates
08 Jan 2006: Paper submission deadline
19 Feb 2006: Notification of acceptance
12 Mar 2006: Final version deadline
27 - 30 Apr 2006: Conference
***********************************************************************
Call for Demos
This is the only new category of LAC2006. You do not need to write a
whole paper, but rather a short abstract only (50-100 words). This
category is mainly thought for software demos. Be aware though that in
case of too many submissions papers take priority over demos.
See section "Call for Papers" for info on the duration of talks and
the technical setup.
How to submit
* See our check list to ensure that you do not forget to enclose
all necessary information:
http://lac.zkm.de/2006/submission_instructions.shtml
* Send your abstract and all necessary information by 8 Jan
2006 via email to this address: lac2006 at zkm dot de
* You will be notified by 19 Feb 2006 whether your submission has
been accepted.
Deadline for submissions is 08 Jan 2006.
***********************************************************************
Call for Workshops
With respect to their content workshops do not differ from talks:
Workshops can have technical focus as well as artistic or scientific
focus. Workshops can be targeted to developers as well as users. See
section "Call for Papers" for more info on this.
The shape of the workshop is completely up to you. E.g. it can be
tutorial-like ("how to write an ALSA driver/ a jack application/ a
LADSPA plugin/ etc.") or it can be BOFS-like (e.g. a meeting of
like-minded users and/or developers to exchange experience and
knowledge about a specific topic), or it can be anything in between.
Workshops can take place in seminar rooms or in a public space like
the ZKM cafe. Depending on the location, attendance might be limited
to ca 10 people.
There is no deadline for submitting workshops. However, we strongly
encourage you to submit early. It will be more likely to get a free
slot and it will be easier for attendants to know about the workshop
if it is published on the conference website. If you expect the
attendants to prepare their laptops for your workshop (e.g. by
installing some software) or if there are other requirements, please
note so in your abstract.
How to submit
* See our check list to ensure that you do not forget to enclose
all necessary information.
http://lac.zkm.de/2006/submission_instructions.shtml
* Send an abstract (ca. 50-100 words) and all necessary
information via email to this address: lac2006 at zkm dot de
* The abstract will be published on the conference website once
the workshop has been accepted (not before 27 Feb 2006 though).
***********************************************************************
Call for Music
There will be some concerts during the conference. We are looking for
music that has been produced completely or mostly under Linux and/or
with open source software:
* "Serious" compositions, to be played in a concert-like context
* Electronica, Chill-Out, Ambient etc., to be played in a less
formal, "party-like" context.
Additionally you are welcome to give a talk about your piece. We
encourage you especially to show how you made the piece using open
source software. Please send a short abstract (ca. 50-100 words) if
you want to give a talk.
If you want to participate, send your composition(s) to this address:
LAC2006 - Call for Music
ZKM | Institut fuer Musik und Akustik
Lorenzstr. 19
D-76135 Karlsruhe
Germany
Make use of one of the following media formats:
* Media: Audio-CD, DVD or CD-ROM
* File formats: aiff or wav
* Channels: mono, stereo or multi-channel
* Samplerate: 44.1, 48, or 96 kHz
* Resolution: 16 or 24 bit
Include the following items with your submission (in English):
* Requirements (speaker setup, instruments etc.)
* A filled-out and signed printout of the form available here:
http://lac.zkm.de/2006/downloads.shtml
For the printed programme and to be published online and on the
conference CD, in continuous text (no table or list please):
* A short commentary on the composition(s) (each ca. 150 words)
* A short Curriculum Vitae (ca. 100 words)
Deadline for submissions is 08 Jan 2006.
A jury will select the compositions that will be
performed/played. Furthermore, the jury will give out three prices to
participants to contribute to their travel expenses.
Besides artistic criteria and technical reasons, these criteria apply
for the selection:
* Tape pieces or pieces which are performed by the composer
herself will generally have more chances to get included.
* If we get more pieces than we can include in the programme,
composers who are attending the conference are preferred.
Terms and conditions for participation can be found in the form
mentioned above. This form includes among other things:
* I will receive no fees whether my composition is played or not.
* GEMA fees (in case of performance) will be paid by ZKM.
* The material I send to ZKM will not be returned.
Additionally to this Call for Music, there will be an open stage
called
"Plug & Chill - The Linux Jam Night"
at Saturday night (29 Apr 2006), where attendents of the conference
are invited to perform their pieces in a less "official"
context. There is no deadline for this, so people can decide during
the conference if they want to participate.
However if you already know that you want to participate do not
hesitate to inform us. Send us an email to lac2006 at zkm dot de and
include a description of your equipment and a short characterisation
of your music (keywords only).
During the conference it is possible to register at the info
desk. Note that there is a time limit for "Plug & Chill". If we have
received too many registrations already you might not get a slot.
Contributions to "Plug & Chill" should not exceed 10 min.
There will be a room at ZKM where people can meet during the
conference and rehearse for "Plug & Chill".
***********************************************************************
hello,
i would like to mix several (up to six) s/pdif sources in the digital
domain. the problem is, that every source has its own clock and possibly
different sample rate. is there any software that can open several
non-synchronized sound cards at the same time? iirc there was a patch
for jackd for drift compensation, but i cannot find it in anymore and
i'm also not sure if that would help.
Minidisc 44100.17 ==S/PDIF==> Sound Card 1 ==> Audio App \
\
Laptop 48000.23 ==S/PDIF==> Sound Card 2 ==> Audio App --> D/A (96khz)
/
DAT 48000.09 ==S/PDIF==> Sound Card 3 ==> Audio App /
Hello,
just tried to update my installation of fst-1.6 to the newest (now beta!)
wine. But there are several problems:
the options to winebuild have changed and so in fst/Makefile the build-command
must be changed:
- the target must be renamed to "$(fst_exe_MODULE).spec.o:" cause winebuild
creates an assembler file that can't be processed by the implicit rule
".c.o:" -- but the new winebuild can create the ".o" file directly.
- "the executable must be named via the -F option" -- to get rid of this
winebuild error message the option '-F' must be inserted just before
$(fst_exe_MODULE)
With this modifications the build creates the libfst.so successfully but when
linking fstconfig with libfst there are two missing symbols:
./libfst.so: undefined reference to `__wine_spec_exe_entry'
./libfst.so: undefined reference to `__wine_spec_init_ctor'
Unfortunately the wine documentation is not updated to this new behaviour and
I was not able to figure out what to do. When building the intermediate
assembler source (just undo the extension change for the .spec.o) and looking
at it, the two symbols are destination marker: The first is just an address
in an internal table and the second is the target of a jump command.
I can't find any suggestions what to additionally link to libfst to satisfy
this unresolved references ...
Is there an updated version of libfst? Or someone with more wine knowledge,
who can solve this problems?
By further investigation I found a workaround that builds libfst but at least
ardour gives a "memory access fault" (Speicherzugriffsfehler):
Unpack the distribution
cp fst/libfst.spec.c fst/libfst.spec.c_backup
./configure
make
cp fst/libfst.spec.c_backup fst/libfst.spec.c
This uses the prebuilt libfst.spec.c but maybe this doesn't match the current
wine version ...
I have build ardour with "VST=1" and it only starts without "memory access
fault" when giving the option "-V"
Thank you
Uwe Koloska
gentoo
vanilla kernel 2.6.10
coldplug-20040920
hotplug-20040923
fxload-20020411
midisport_fw-0.5.0
to make this short....
I installed by following the instructions here...
http://alsa.opensrc.org/index.php?page=USBMidiDevices
I installed the midisport about a month ago and got it
working. I was using kde at the time. I uninstalled
kde and switched to windowmaker. Now the midisport
doesn't work I reinstalled the above packages. still
no luck. I even reinstalled kde. nothing.
any ideas on this one?
-Mike Fisher
__________________________________
Start your day with Yahoo! - Make it your home page!
http://www.yahoo.com/r/hs
Apparently my soundcard selecting skills are poor.
I thought that a USB card would be nice so that I could use it on
different machines. The M-Audio Audiophile USB had good specs and usb
audio was supposed to work ok.
After much googleing I seem to have the device recording 24/96k audio
but its only with arecord.
Trying to start jack (V 0.99) it whines that my format is not
supported. And if I choose plughw I get XRUNS.
How much work will it be to get jack to work with S24_3BE?
--
Richard A. Smith
I've written a simple patch to add info on the real-time capabilities
of LADSPA plugins in CheeseTracker.
I know I seem to be the only CheeseTracker user on the lists, but just
in case...
http://blog.dis-dot-dat.net/2005/10/cheesetracker-patch.html
--
"I'd crawl over an acre of 'Visual This++' and 'Integrated Development
That' to get to gcc, Emacs, and gdb. Thank you."
(By Vance Petree, Virginia Power)
Hello,
Could someone please remove 'joesgarage79(a)cs.com' from the subscription list ?
The last weeks I get a bounce from AOL for every message posted...
--
FA
I'm going to convert my fathers record collection over to CD. Doing
some google research.
According to http://www.tracertek.com/newway.htm they claim the "new"
and best way to do LP to CD is to use a flat preamp, record at 24bit,
96kHz and then apply the RIAA curve in software after the fact.
Either before or after the DeNoise, De-Click, etc depending. I've
also seen a few other sites that say the same type things.
tracertek sells doze software to do the whole ball of wax but I'd like
to use Linux.
I haven't found any RIAA filters yet so I guess I'm looking at
writeing one. So does anyone have any information on where to find
the official RIAA curve to make a plugin from?
They also recommend using a pink-noise record to calibrate your setup
and then adjust the curve so it matches your system.
--
Richard A. Smith
