Fons Adriaensen:
>
> On Wed, Sep 10, 2008 at 05:02:12PM +0200, Kjetil S. Matheussen wrote:
>
>> jack_capture
>> ============
>> jack_capture is a program for recording soundfiles with jack. Its default
>> operation is to capture whatever sound is going out to your speakers into
>> a file. (But it can do a number of other operations as well...)
>
> Very useful, just one remark: for more than 2 channels
> the default should be WAVEX instead of WAV (easy enough
> if you use libsndfile). WAVs with more than 2 channels
> are technically illegal and refused by some software.
>
Thanks for the input. But do you think ch>2 wavex
files are supported by more software than ch>2 wav
files? Because I haven't even heard of wavex files
before... (wavex files are supported in jack_capture
though, "-f wavex" should do the job, thanks to libsndfile)
I posted this exact message to the Vamp forum, noticed the dates of the
last posts, there, and decided to try here instead.
I'm having a most unusual problem compiling the Vamp-SDK on my machine.
This has actually been an on-going problem for some time now. Looking
over the Vamp forums, I see one other person seems to have successfully
compiled and installed Vamp on his 64-bit Ubuntu install, so I'm
wondering what keeps going wrong here.
The first thing I did was to edit the Makefile to install to /usr
instead of /usr/local. That was simple enough. Then when I run make, I
get the following output (notice the error at the end):
-----
g++ -O2 -Wall -I. -fPIC -c -o vamp-sdk/PluginAdapter.o
vamp-sdk/PluginAdapter.cpp
g++ -O2 -Wall -I. -fPIC -c -o vamp-sdk/RealTime.o vamp-sdk/RealTime.cpp
ar r vamp-sdk/libvamp-sdk.a vamp-sdk/PluginAdapter.o vamp-sdk/RealTime.o
g++ -O2 -Wall -I. -fPIC -c -o vamp-sdk/PluginHostAdapter.o
vamp-sdk/PluginHostAdapter.cpp
g++ -O2 -Wall -I. -fPIC -c -o
vamp-sdk/hostext/PluginBufferingAdapter.o
vamp-sdk/hostext/PluginBufferingAdapter.cpp
g++ -O2 -Wall -I. -fPIC -c -o vamp-sdk/hostext/PluginChannelAdapter.o
vamp-sdk/hostext/PluginChannelAdapter.cpp
g++ -O2 -Wall -I. -fPIC -c -o
vamp-sdk/hostext/PluginInputDomainAdapter.o
vamp-sdk/hostext/PluginInputDomainAdapter.cpp
g++ -O2 -Wall -I. -fPIC -c -o vamp-sdk/hostext/PluginLoader.o
vamp-sdk/hostext/PluginLoader.cpp
g++ -O2 -Wall -I. -fPIC -c -o vamp-sdk/hostext/PluginWrapper.o
vamp-sdk/hostext/PluginWrapper.cpp
ar r vamp-sdk/libvamp-hostsdk.a vamp-sdk/PluginHostAdapter.o
vamp-sdk/hostext/PluginBufferingAdapter.o
vamp-sdk/hostext/PluginChannelAdapter.o
vamp-sdk/hostext/PluginInputDomainAdapter.o
vamp-sdk/hostext/PluginLoader.o vamp-sdk/hostext/PluginWrapper.o
vamp-sdk/RealTime.o
ranlib vamp-sdk/libvamp-sdk.a
ranlib vamp-sdk/libvamp-hostsdk.a
g++ -static-libgcc -shared -Wl,-Bsymbolic -Wl,-soname=libvamp-sdk.so.1
-o vamp-sdk/libvamp-sdk.so vamp-sdk/PluginAdapter.o vamp-sdk/RealTime.o
g++ -static-libgcc -shared -Wl,-Bsymbolic
-Wl,-soname=libvamp-hostsdk.so.2 -o vamp-sdk/libvamp-hostsdk.so
vamp-sdk/PluginHostAdapter.o vamp-sdk/hostext/PluginBufferingAdapter.o
vamp-sdk/hostext/PluginChannelAdapter.o
vamp-sdk/hostext/PluginInputDomainAdapter.o
vamp-sdk/hostext/PluginLoader.o vamp-sdk/hostext/PluginWrapper.o
vamp-sdk/RealTime.o
g++ -O2 -Wall -I. -fPIC -c -o examples/SpectralCentroid.o
examples/SpectralCentroid.cpp
g++ -O2 -Wall -I. -fPIC -c -o examples/PercussionOnsetDetector.o
examples/PercussionOnsetDetector.cpp
g++ -O2 -Wall -I. -fPIC -c -o examples/AmplitudeFollower.o
examples/AmplitudeFollower.cpp
g++ -O2 -Wall -I. -fPIC -c -o examples/ZeroCrossing.o
examples/ZeroCrossing.cpp
g++ -O2 -Wall -I. -fPIC -c -o examples/plugins.o examples/plugins.cpp
g++ -static-libgcc -shared -Wl,-Bsymbolic
-Wl,--version-script=vamp-plugin.map -o examples/vamp-example-plugins.so
examples/SpectralCentroid.o examples/PercussionOnsetDetector.o
examples/AmplitudeFollower.o examples/ZeroCrossing.o examples/plugins.o
vamp-sdk/libvamp-sdk.a /usr/lib/gcc/x86_64-linux-gnu/4.2.3/libstdc++.a
/usr/bin/ld:
/usr/lib/gcc/x86_64-linux-gnu/4.2.3/libstdc++.a(functexcept.o):
relocation R_X86_64_32 against `std::bad_typeid::~bad_typeid()' can not
be used when making a shared object; recompile with -fPIC
/usr/lib/gcc/x86_64-linux-gnu/4.2.3/libstdc++.a: could not read symbols:
Bad value
collect2: ld returned 1 exit status
make: *** [examples/vamp-example-plugins.so] Error 1
-----
Is it trying to tell me that libstdc++ is compiled incorrectly on my
machine? It's the one that comes with every Ubuntu 64-bit system. Any
help would be greatly appreciated. Thank you!
My system:
AMD64 X2 with Kubuntu 64-bit, 2.4.24-19-rt kernel, 2GB DDR-800 RAM,
SATA2 hard disks.
Regards,
Darren Landrum
Hi all,
Does anyone else get clicks which occur continuously after getting a
single xrun in jack? (i.e no further xruns are reported, but the audio is
crackling).
I'm setting up an art installation which has to run for hours on end
without intervention, and this seems to be happening after some time
(running jack in realtime mode). I'm using a stock kernel in OpenSuse -
would it help to use a lowlatency one? The audio doesn't need lowlat - I'm
using a buffer size of 1024.
I don't care about the odd xrun - as long as the audio goes back to normal
afterwards, any help gratefully received. This is running in my own
software so there is more than a chance it's something I'm doing wrong.
cheers,
dave
Hi, sorry for the double post, but maybe a user
knows the answer to this...
What is the right way to call fst_init() ?
I have installed fst-1.9 (tried 1.7 - 1.9), and
it runs standalone and loads vst's OK.
However, from within a simple 'hello world' app,
when I call fst_init(), it causes a seg fault.
The seg fault happens early within fst, in the 'wine_premain'
code, at getModuleHandleA().
I have tried that trick of reserving and initializing 1,000,000
stack bytes (taken from from jfst_reserve_memory()). No luck.
I really would like to get this working. Can you help?
Thanks. Tim.
terminator356 <at> users <dot> sourceforge <dot> net.
(Using a different computer)
On Wed, Sep 10, 2008 at 05:02:12PM +0200, Kjetil S. Matheussen wrote:
> jack_capture
> ============
> jack_capture is a program for recording soundfiles with jack. Its default
> operation is to capture whatever sound is going out to your speakers into
> a file. (But it can do a number of other operations as well...)
Very useful, just one remark: for more than 2 channels
the default should be WAVEX instead of WAV (easy enough
if you use libsndfile). WAVs with more than 2 channels
are technically illegal and refused by some software.
Ciao,
--
FA
Laboratorio di Acustica ed Elettroacustica
Parma, Italia
Wie der Mond heute Nacht aussieht !
Ist es nicht ein seltsames Bild ?
i would like to have solution where i can use any headphones and where
there is no bigger latency then 10ms (at least ;).... all pro
solutions are so f* expensive....
Assuming a 7.1/192K/24bit $3:- chip onboard ... What next?
First I will say, it actually will do the planned send and return
to/from the two pieces of stereo outboard equipment I have (that is not
going anywhere,) as well as do separate headphones and monitors. So I
should be a happy camper ...
Suppose one was to face the real world of playing live again? In my
experience this can be a torturous venture into the realms of cheap
lights and the evil thyristors and diacs of this world, all trying to
make their voices heard through my equipment ...
So, how about turning a single unbalanced stereo jack into a single
balanced mono jack by converting a single mono signal to a stereo signal
with inverted phase, would that be a good idea? If so, I believe this
might work in a simalar way on microphone input as well.
If the above holds and we then have two (instead of one) DAC's working
push/pull on the line, would it be possible to take advantage of this?
What I have in mind here is that, the lower you get in the "bittiness",
the more the systenatic errors of distortion will be apparent.
For starters, how about having one the phases at a level slightly below
the other? This should ideally trigger transisitions between absolute
levels at slightly different times for the two phases, giving us an
extra 6dB of useable headroom.
mvh // Jens M Andreasen
Hello all,
I want to know if is there anybody that know anything about open source
implementation of Speaker Recognition[1]
or what kind of tool i can use to develop this kind of tool on linux?
Regards,
Ste
[1]http://en.wikipedia.org/wiki/Speaker_recognition
--
Email.it, the professional e-mail, gratis per te: http://www.email.it/f
Sponsor:
Cerchi un hotel a Riccione, Rimini o Misano Adriatico ? Visita il sito
rivieraparkhotels.it.
Gli alberghi dei parchi divertimento
Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid=8262&d=20080910
Hello everyone!
This is again a bit OT, but still. I have a program with two pthreads. One
pthread is running an audio player on a file repeatedly, the other is waiting
for a signal. If "the other" gets the signal or timeout, then it should tell
the player to stop. Unfortunitely with mplayer kill -15 doesn't have the
desired effect. So I thought:
What if I could make mplayer's stdin available to the program and simply
send character 'q'. But because of pthreads, I left fork and exec* alone and
went with system. Any ideas what to do? If someone knows something nice with
fork and the like, I've seen something with pipes for this. Otherwise the
player-command I call can be called from within a shell script, so I can do
funny things with redirections.
I hope I made myself clear and didn't write too much again... :-(
Kindest regards
Julien
--------
Music was my first love and it will be my last (John Miles)
======== FIND MY WEB-PROJECT AT: ========
http://ltsb.sourceforge.net
the Linux TextBased Studio guide
======= AND MY PERSONAL PAGES AT: =======
http://www.juliencoder.de
This is totally alphabetagamma = unfinished and unpolished software. Release
early - release often is my guide here ;)
Here's the summary:
ProcessPP is the "realisation" of a rather silly idea: A livecoding
environment for C++. As C++ is not interpreted, but compiled, this indeed
does sound like a really silly idea. But the twist is that while “true”
livecoding cannot be done, it can be at least made as easy as possible to try
out new code snippets.
ProcessPP consists of three distinct parts
- procespp: A host application that can load shared objects and execute the
code contained in them
- qprocesspp: A Qt GUI application which serves as an editor for hacking away
functions and to compile them easily into a shared object. Then it tells
processpp to load and run the shared object
- libprocesspp: A shared library which is the “glue” between processpp and
user generated shared object files. Right now it only containes code for the
shared object to find out stuff like samplerate, buffersize, number of
input/output channels, etc..
For illustrative purposes here are the steps involved in making noise:
- File->Open from Template (choose process.template.cc)
- Add some code in the inner loop to make noise
- Process->Run
- Hear the noise!!!
If the above don’t work, take a look at the log in the lower half of the main
window. Often some slight tweaks to the config file
(~/.config/Ugh!/process++.conf) need to be made.
Get it here: http://tapas.affenbande.org/wordpress/?page_id=91
Regards,
Flo
--
Palimm Palimm!
http://tapas.affenbande.org
