19 May
2004
19 May
'04
5:08 a.m.
Hi,
I'm trying to compile 'timemachine' on my system and I keep running into
this problem in the ./configure script:
------------------------------------------------------------------------
checking for jack >= 0.80.0... Package jack was not found in the
pkg-config search path.
Perhaps you should add the directory containing `jack.pc'
to the PKG_CONFIG_PATH environment variable
No package 'jack' found
configure: error: Library requirements (jack >= 0.80.0) not met;
consider adjusting the PKG_CONFIG_PATH environment variable if your
libraries are in a nonstandard prefix so pkg-config can find them.
------------------------------------------------------------------------
I'm using the tarballs of timemachine-0.2.4 and
jack-audio-connection-kit-0.98.1.
Both packages are in the same directory level
(/I/Useful_Stuff/AudioTools/) with the detarred source directories
under that.
So, I'm wondering I am, how do I get timemachine to find jack?
Is the problem that the jack package name is actually
'jack-audio-connection-kit'?
If yes, how would I fix that in timemachine's configure script?
And how do I adjust the PKG_CONFIG_PATH environment variable if
that's really what I'm supposed to be doing?
Thanks in advance for any help!
Toodles,
~Jos~
Jos Laake
Coon Valley Net Works
coonvalley (dot) net
josmusic (dot) com
19 May
19 May
6:44 a.m.
On Wed, 19 May 2004 00:00:58 -0700
Jos Laake <jos(a)radiks.net> wrote:
Hi,
I'm trying to compile 'timemachine' on my system and I keep running into
this problem in the ./configure script:
------------------------------------------------------------------------
checking for jack >= 0.80.0... Package jack was not found in the
pkg-config search path.
Perhaps you should add the directory containing `jack.pc'
to the PKG_CONFIG_PATH environment variable
No package 'jack' found
configure: error: Library requirements (jack >= 0.80.0) not met;
consider adjusting the PKG_CONFIG_PATH environment variable if your
libraries are in a nonstandard prefix so pkg-config can find them.
------------------------------------------------------------------------
I'm using the tarballs of timemachine-0.2.4 and
jack-audio-connection-kit-0.98.1.
Both packages are in the same directory level
(/I/Useful_Stuff/AudioTools/) with the detarred source directories
under that.
Did you do "make install"? If you didn't you need to do that.
The "make install" command will install Jack in the /usr/local tree.
You then need to check that pkg-config can find jack:
pkg-config --modversion jack
If that fails, you might need to do:
export PKG_CONFIG_PATH=$PKG_CONFIG_PATH:/usr/local/lib/pkgconfig
The "pkg-config --modversion jack" should then print the jack version
and you will be ready to configure timemachine.
HTH,
Erik
--
+-----------------------------------------------------------+
Erik de Castro Lopo nospam(a)mega-nerd.com (Yes it's valid)
+-----------------------------------------------------------+
A good debugger is no substitue for a good test suite.
--
--
+-----------------------------------------------------------+
Erik de Castro Lopo nospam(a)mega-nerd.com (Yes it's valid)
+-----------------------------------------------------------+
A good debugger is no substitue for a good test suite.
21 May
21 May
6:27 a.m.
On Wed, 19 May 2004 00:00:58 -0700
Jos Laake <jos(a)radiks.net> wrote:
>I'm trying to compile 'timemachine' on
my system and I keep running into
>this problem in the ./configure script:
Erik de Castro Lopo wrote:
Did you do "make install"? If you didn't
you need to do that.
The "make install" command will install Jack in the /usr/local tree.
You then need to check that pkg-config can find jack:
pkg-config --modversion jack
If that fails, you might need to do:
export PKG_CONFIG_PATH=$PKG_CONFIG_PATH:/usr/local/lib/pkgconfig
The "pkg-config --modversion jack" should then print the jack version
and you will be ready to configure timemachine.
Hey, thanks Erik! This ^^ did the trick... and then it choked on
'sndfile'. So I got that and compiled it... And then it choked
on 'ladcca' so I got that and compiled it... and then it worked.
Or at least it compiled and I brought it up with JACK and made
connections with 'qjackctl'. At that point, 'timemachine' appeared
to work, the meters were movin' it was writin' ".wav" files...cool.
Until I tried to play one of the '.wav' files. When I try to play
it with 'alsaplayer' I get this:
Audio File Library: '/home/jos/tm-2004-05-13T05:30:06.wav':
unrecognized audio file format [error 0]
Audio File Library: invalid file handle [error 1]
Audio File Library: '/home/jos/tm-2004-05-13T05:30:06.wav':
unrecognized audio file format [error 0]
Audio File Library: invalid file handle [error 1]
...and then 'alsaplayer' hangs real bad and I gotta go kill it.
I tried to play them in 'xmms' as well and it won't even load them.
Here's a link to one of the 'timemachine' generated files:
http://www.josmusic.com/splut/tm-2004-05-21T00:59:56.wav
Any clues anybody?
Thanks in advance!
~Jos~
7:02 a.m.
On Fri, 21 May 2004 01:19:18 -0700
Jos Laake <jos(a)radiks.net> wrote:
Hey, thanks Erik! This ^^ did the trick... and then
it choked on
'sndfile'. So I got that and compiled it... And then it choked
on 'ladcca' so I got that and compiled it... and then it worked.
Or at least it compiled and I brought it up with JACK and made
connections with 'qjackctl'.
Which is why so many people prefer Debian, AGNULA and DeMuDi which
have many more pre-packaged audio apps that the standard Suse/Redhat/
Mandrake etc.
At that point, 'timemachine' appeared
to work, the meters were movin' it was writin' ".wav" files...cool.
Until I tried to play one of the '.wav' files.
Sorry, this file is not a WAV file, its a W64 file. W64 is a file format
which originates with the SoundForge people and allows files bigger than
4Gig (the limit of standard WAV files). libsndfile read and writes these
quite happily. To play the file, use sndfile-play (probably installed
when you installed libsndfile).
When I try to play it with 'alsaplayer' I get
this:
Audio File Library: '/home/jos/tm-2004-05-13T05:30:06.wav':
Your copy of alsaplayer seems to be using libaudiofile instead of
libsndfile. I know alsaplayer does support libsndfile, but your copy
might not have libsndfile support compiler in.
I tried to play them in 'xmms' as well and it
won't even load them.
Xmms will load and play these files if you use the xmms_sndfile
plugin:
http://www.mega-nerd.com/xmms_sndfile/
Erik
--
+-----------------------------------------------------------+
Erik de Castro Lopo nospam(a)mega-nerd.com (Yes it's valid)
+-----------------------------------------------------------+
A good debugger is no substitue for a good test suite.
--
--
+-----------------------------------------------------------+
Erik de Castro Lopo nospam(a)mega-nerd.com (Yes it's valid)
+-----------------------------------------------------------+
A good debugger is no substitue for a good test suite.
22 May
22 May
12:11 a.m.
Hey, thanks
Erik! This ^^ did the trick... and then it choked on
'sndfile'. So I got that and compiled it... And then it choked
on 'ladcca' so I got that and compiled it... and then it worked.
Or at least it compiled and I brought it up with JACK and made
connections with 'qjackctl'.
Which is why so many people prefer Debian, AGNULA and DeMuDi which
have many more pre-packaged audio apps that the standard Suse/Redhat/
Mandrake etc.
23 May
23 May
7:52 a.m.
New subject: [linux-audio-user] Timemachine file playback problems
Erik de Castro Lopo wrote:
Sorry, this file is not a WAV file, its a W64 file.
W64 is a file format
which originates with the SoundForge people and allows files bigger than
4Gig (the limit of standard WAV files). libsndfile read and writes these
quite happily. To play the file, use sndfile-play (probably installed
when you installed libsndfile).
So I recompiled 'alsaplayer'. It still works on all the
things it used to work on, and it now loads all the soundfiles
from 'timemachine' and appears to be playing them. But
what I get is silence. I don't get it. Timemachine's little
meter is bouncing away in sync with the input, which implies
that it's getting a signal. So what I see so far is that one
of three things could be happening:
A) 'timemachine' is not really recording properly but writing
the file correctly
B) 'timemachine' is recording okay, but not writing the file
correctly.
C) 'alsaplayer' isn't reading/interpreting the file correctly.
Anybody got any good guesses on what to check next?
Thanks for any input,
~Jos~
When I try to play it with 'alsaplayer' I
get this:
Audio File Library: '/home/jos/tm-2004-05-13T05:30:06.wav':
Your copy of alsaplayer seems to be using libaudiofile instead of
libsndfile. I know alsaplayer does support libsndfile, but your copy
might not have libsndfile support compiler in.
8:36 a.m.
New subject: [linux-audio-user] Timemachine file playback problems
On Sun, 23 May 2004 02:44:37 -0700
Jos Laake <jos(a)radiks.net> wrote:
So I recompiled 'alsaplayer'. It still works
on all the
things it used to work on, and it now loads all the soundfiles
from 'timemachine' and appears to be playing them. But
what I get is silence.
Here is a sceen shot of your file loaded into Conrad Parker's Sweep
(which uses libsndfile for file I/O):
http://www.mega-nerd.com/tmp/a.png
Much of the file is silence and even the lowest part is at -12dB.
I don't get it. Timemachine's little
meter is bouncing away in sync with the input, which implies
that it's getting a signal. So what I see so far is that one
of three things could be happening:
A) 'timemachine' is not really recording properly but writing
the file correctly
Maybe, but unlikely.
B) 'timemachine' is recording okay, but not
writing the file
correctly.
Very unlikely.
C) 'alsaplayer' isn't reading/interpreting
the file correctly.
Even more unlikely. To prove this is not the case, why not load
the file into an editor like sweep, normalise it, save it and then
try playing the new file with alsaplayer.
Anybody got any good guesses on what to check next?
Why not start with a known good audio source, record it with
timemachine and then try playing the timemachine recorded
part with alsaplayer.
Erik
--
+-----------------------------------------------------------+
Erik de Castro Lopo nospam(a)mega-nerd.com (Yes it's valid)
+-----------------------------------------------------------+
A good debugger is no substitue for a good test suite.
--
--
+-----------------------------------------------------------+
Erik de Castro Lopo nospam(a)mega-nerd.com (Yes it's valid)
+-----------------------------------------------------------+
A good debugger is no substitue for a good test suite.
9:11 a.m.
New subject: [linux-audio-user] Timemachine file playback problems
Erik de Castro Lopo wrote:
On Sun, 23 May 2004 02:44:37 -0700
Jos Laake <jos(a)radiks.net> wrote:
Okay, so I took a snippet that I know plays just fine.
It's a .wav file and can be found at:
http://www.josmusic.com/splut/mikriff.wav
I play it through 'alsaplayer' with its outputs routed via
JACK to both 'timemachine' and the alsa outputs. The signal
shows up on the 'timemachine' LED Meter and the soundclip is
heard correctly at the output. I click on the 'timemachine'
window to capture the last 10 seconds. 'timemachine' writes
this output file:
http://www.josmusic.com/splut/tm-mikriff.wav
This file appears to be silent when played in 'alsaplayer'
(same configuration that worked above). It is also silent
when played in 'xmms' with 'sndfile' support and 'alsa'
output. (This configuration also plays the original file
just fine.)
That's what I've got so far. It's looking more like an output
file problem to me.
~Jos~
So I recompiled 'alsaplayer'. It still
works on all the
things it used to work on, and it now loads all the soundfiles
from 'timemachine' and appears to be playing them. But
what I get is silence.
Anybody got any good guesses on what to check
next?
Why not start with a known good audio source, record it with
timemachine and then try playing the timemachine recorded
part with alsaplayer.
11 a.m.
New subject: [linux-audio-user] Timemachine file playback problems
On Sun, 23 May 2004 04:02:55 -0700
Jos Laake <jos(a)radiks.net> wrote:
If you want me to look at a file I would appreciate it if you
could keep the file to 500k of less.
This file appears to be silent when played in
'alsaplayer'
(same configuration that worked above). It is also silent
when played in 'xmms' with 'sndfile' support and 'alsa'
output. (This configuration also plays the original file
just fine.)
Both xmma and alsaplayer are probably using their own WAV loading
code and only using libsndfile for the W64 stuff. If thats the
case, the WAV code can be wrong, but the W64 stuff wrong.
That's what I've got so far. It's looking
more like an output
file problem to me.
The file loads into Sweep without a problem:
http://www.mega-nerd.com/tmp/tm-mikriff.png
and also plays without a problem. Sweep uses libsndfile for WAV
and W64.
Sweep is at :
http://sweep.sf.net/
Erik
--
+-----------------------------------------------------------+
Erik de Castro Lopo nospam(a)mega-nerd.com (Yes it's valid)
+-----------------------------------------------------------+
A good debugger is no substitue for a good test suite.
10:58 p.m.
New subject: [linux-audio-user] Timemachine file playback problems
Erik de Castro Lopo wrote:
On Sun, 23 May 2004 04:02:55 -0700
Jos Laake <jos(a)radiks.net> wrote:
If you want me to look at a file I would appreciate it if you
could keep the file to 500k of less.
Sorry, I'll keep that in mind.
Both xmma and alsaplayer are probably using their own
WAV loading
code and only using libsndfile for the W64 stuff. If thats the
case, the WAV code can be wrong, but the W64 stuff wrong.
The file loads into Sweep without a problem:
http://www.mega-nerd.com/tmp/tm-mikriff.png
and also plays without a problem. Sweep uses libsndfile for WAV
and W64.
Okay, this was good information. I loaded the file into
'Audacity' and hey, whaddya know! It's totally valid there
and sounds just fine. So, that's a big help. That tells
me my snippets *are* getting collected. Cool.
Still, that brings up a couple of questions to toss out to
the list:
1) Whassup with 'alsaplayer' & 'xmms' that they're not getting
these .w64 files read in properly? If they're using 'libsndfile'
(and 'alsaplayer' even sez right on the 'faceplate' that it is)
why can't they play them when 'Sweep' and 'Audacity' (also using
'libsndfile') can play them just fine?
2) Why is 'timemachine' saving it's recordings in this unpopular
file format? And why does it call them '.wav' files if they're
really '.w64' files? Is it possible to get 'timemachine' to save
out plain ol' '.wav' files so I can preview them without shutting
down JACK to load 'Audacity'?
Just questions. No pressure. ;-)
Heaps of thanks to Erik de Castro Lopo!
~Jos~
24 May
24 May
6:49 a.m.
New subject: [linux-audio-user] Timemachine file playback problems
On Sun, 23 May 2004 17:50:46 -0700
Jos Laake <jos(a)radiks.net> wrote:
Okay, this was good information. I loaded the file
into
'Audacity' and hey, whaddya know! It's totally valid there
and sounds just fine. So, that's a big help. That tells
me my snippets *are* getting collected. Cool.
Still, that brings up a couple of questions to toss out to
the list:
1) Whassup with 'alsaplayer' & 'xmms' that they're not getting
these .w64 files read in properly?
We still don't know if they are actually using libsndfile or their
own native code. In xmms, it is pssouble to disable the xmms native
WAV reader so that may be worth a try.
If they're using 'libsndfile'
(and 'alsaplayer' even sez right on the 'faceplate' that it is)
They still might not be using libsndfile correctly. I know of at
least one bug in xmms_sndfile that i haven't had a chance to
fix yet.
why can't they play them when 'Sweep' and
'Audacity' (also using
'libsndfile') can play them just fine?
2) Why is 'timemachine' saving it's recordings in this unpopular
file format?
My guess is that they would like to be able to write files larger
than 4Gigabytes which is the theoretical limit of WAV files. In
addition, many WAV file readers incorrectly refuse to read WAV
files larger than 2Gig.
And why does it call them '.wav' files if
they're
really '.w64' files?
You need to ask the authors of timemachine :-).
Is it possible to get 'timemachine' to save
out plain ol' '.wav' files so I can preview them without shutting
down JACK to load 'Audacity'?
I think Sweep has preliminary jack support (might need patches)
which might solve that problem.
Heaps of thanks to Erik de Castro Lopo!
Damn, I really should get myself a paypal account :-).
Erik
--
+-----------------------------------------------------------+
Erik de Castro Lopo nospam(a)mega-nerd.com (Yes it's valid)
+-----------------------------------------------------------+
A good debugger is no substitue for a good test suite.
--
--
+-----------------------------------------------------------+
Erik de Castro Lopo nospam(a)mega-nerd.com (Yes it's valid)
+-----------------------------------------------------------+
A good debugger is no substitue for a good test suite.
26 May
26 May
5:37 p.m.
New subject: [linux-audio-user] Timemachine file playback problems
On Sun, May 23, 2004 at 05:50:46PM -0700, Jos Laake wrote:
2) Why is 'timemachine' saving it's
recordings in this unpopular
file format? And why does it call them '.wav' files if they're
really '.w64' files? Is it possible to get 'timemachine' to save
out plain ol' '.wav' files so I can preview them without shutting
down JACK to load 'Audacity'?
Because some people wanted to record files that are longer than 2GB, if
you're using 8 channels you hit that limit pretty quickly, but even for
stereo its a problem.
The .wav and not .w64 was just a bad decision when I made the release that
started using WAV64. I plan to add a flag to force .wav files and make the
extension for W64's .w64.
There is no good solution unfortunatly, but at least this way the
timemachine users will pester application authors that dont support W64 :)
- Steve
7581
days inactive
7588
days old
linux-audio-user@lists.linuxaudio.org
11 comments
4 participants
participants (4)
-
Erik de Castro Lopo -
Fernando Pablo Lopez-Lezcano -
Jos Laake -
Steve Harris