http://www.notam02.no/arkiv/src/
ABOUT
-----
jack_capture is a small simple program to capture whatever
sound is going out to your speakers into a file.
This is the program I always wanted to have for jack, but no
one made. So here it is.
USAGE
-----
jack_capture [-f filename] [ -b bitdepth ] [-c channels] [ -B bufsize ]
Filename is by default auotogenerated to something like "jack_capture_<date+exact_time>.wav"
Bitdepth is by default FLOAT.
Channels is by default 2.
Bufsize is by default 262144.
ACKNOWLEDGMENT
--------------
Mostly based on the jackrec program in the jack distribution
made by Paul Davies and Jack O'Quin. Automatic filename generation
code taken from the timemachine program by Steve Harries.
--
I've got a DVD-A disc with residue on it, which won't wash off, and
which causes a lot of skipping. If this were a CD, I'd just use
cdparanoia to rip it, then burn a fresh copy. Does anyone know of
something like that for Linux? FWIW, I put the disc in my DVD+/-RW
drive (Lite-on, if it matters) and its type wasn't recognized.
Thanks....
--
Kevin
On Tuesday 31 January 2006 20:28, linux-audio-user-request(a)music.columbia.edu
wrote:
> >Also a problem in 2.6.14. I am not using udev or devfs but have
> > explicitely created /dev nodes (old fashioned way and far far too many
> > entries, but ... always worked before).
> >
> >Newer kernels boot with many undefines. They seem to correspond to stuff
> > in the sound core modules. Do I now need to explicitely load these or
> > soundcore.ko on boot up (i.e. placing them in /etc/modules--somewhere
> > along the line, snd_seq_midi had to be placed there!). Anybody doing
> > this? (Guess it wouldn't hurt to try it.)
> >
> >Easy enough -- didn't work. It is as if these modules are not exporting
> > their symbols correctly.
>
> Made a kernel with alsa sound support compiled in! I also compiled in the
> "generic" devices. Result: NO UNDEFINED. My three (a set ncards = 3) became
> dummy, virmidi and the ensonic. The ensonic did not play, however, but the
> alsa restore on bootup failed because of the 1st two. Kmixer settings are
> restored but have no effect.
>
> So I am trying to build it with just the alsa core compiled in and
> hopefully the three cards will be the mpu401, usb-audio and ensonic loaded
> as modules as before. Wish this did not take so long to try out :-
Was not so bad. No more undefines and get my UM1 usb and the ens1371 just
fine. snd=mu401 does not load with same error as in 2.6.12 kernels!
The audio plays through the ensonic just fine.
I used to be able to "cat" the midi from the UM1 cat /dev/midi1 but this did
not work.
Since I had no midi out, I could not try playing MIDI or "thru"ing the
keyboard using jackqtl to connect the UM1 to the mpu401.
So ...
1. Debian stock kernels are not built with alsa's core. I needed to roll my
own for this.
2. The mpu401 problem remains from 2.6.12.
On Tue, 31 Jan 2006, Lee Revell wrote:
> What in the hell is PMCD?
It seems to be (though today was the first I ever heard of it myself):
* PMCD: is an acronym for a "Pre Master CD", when used for the
manufacturing or replication of CD's. The "Master" in which is
referred, in manufacturing terms is a "Glass Master"
(http://www.asimusic.com/mastering.html)
It doesn't seem to me that any specific software is required, so much
as specific conditions be met when creating the CD.
--
----------------------------------------------------------------------
Sylvain Robitaille syl(a)alcor.concordia.ca
Major in Electroacoustic Studies Concordia University
Faculty of Fine Arts / Music Department Montreal, Quebec, Canada
----------------------------------------------------------------------
Hello list!
A little bit off topic, mainly addressed to guitarists or technicians on
this list:
The guitarist of the band I play with has a weird problem with his floor
Digital Delay made by BOSS Roland.
As I remember, it is a stereo delay, maybe the 4th version BOSS sold.
The foot switch in it behaves not as usual because if the effect is turn
on, it does not turn off when you hit it once again.
I don´t know if the switch itself is a momentary ( maybe surely it is )
and how it stays in the mode it is ( maybe a simple flipflop ?? ).
Does anyone of you know where I can get a circuit diagram of this effect?
I found a diagram about my old DX7II really easy in the past, but that´s
really old and off topic indeed.
Thanks in advance,
Marius
I am stuck in a dialog box of the export session to file in ardour.
I forgot to put a filename for the export and ardour came back with
"ardour can't open export file ..... (system error)"
Ok, fine. But, it won't let me close that dialog box, nor will it let me
"stop export" when pressing that button in the "ardour: export" dialog box.
No other menus are working - kinda locked out. (although I can type a
new filename in the export window - but nothing really works"
I hate to loose my session. Any ideas?
>Also a problem in 2.6.14. I am not using udev or devfs but have explicitely
>created /dev nodes (old fashioned way and far far too many entries, but ...
>always worked before).
>Newer kernels boot with many undefines. They seem to correspond to stuff in
>the sound core modules. Do I now need to explicitely load these or
>soundcore.ko on boot up (i.e. placing them in /etc/modules--somewhere along
>the line, snd_seq_midi had to be placed there!). Anybody doing this? (Guess
>it wouldn't hurt to try it.)
>Easy enough -- didn't work. It is as if these modules are not exporting their
>symbols correctly.
Made a kernel with alsa sound support compiled in! I also compiled in the
"generic" devices. Result: NO UNDEFINED. My three (a set ncards = 3) became
dummy, virmidi and the ensonic. The ensonic did not play, however, but the
alsa restore on bootup failed because of the 1st two. Kmixer settings are
restored but have no effect.
So I am trying to build it with just the alsa core compiled in and hopefully
the three cards will be the mpu401, usb-audio and ensonic loaded as modules
as before. Wish this did not take so long to try out :-)
Hi Thorsten. I can't find your original posting for this tune, but it's quite
interesting.
I picture myself as a lab technician standing in a lab, with some very weird
and wonderfull processes running, producing very weird and wonderfull sounds.
Halfway through your tune, I, the lab tech, decide to join in with the sounds
in the lab using your whistling.
it sort of reminds me of an old black and white film. The man in the white
suit. Starring Alec Guiness (who was the man in the white suit). Mind you. he
didn't join in with all the weird and wonderfull sounds from the processes
running in his lab.
It's interesting how you can listen to a new piece of music and connect it to
something you have heard in the past.
BTW: I'm still working my way through your archives on dialup. Just started on
December_97.ogg. Nigel.
Hi All:
I'm an analog muso (30 years+) and a Linux user (5 years+), but am totally
new to doing audio on Linux (or any other OS).
I've got heaps of stuff installed on a laptop running Fedora 3 (ALSA,
JACK, Hydrogen, Muse, Rosegarden, SooperLooper,
CheeseTracker and a lot more) but unfortunately most of it doesn't work
yet. This is almost certainly because I don't
understand ALSA and/or JACK properly. Also MIDI, I'm really in the dark as
to what it is, what it does and how it works.
I know sound works because I can play .wav samples in XMMS. Without
starting JACK, Hydrogen runs and plays demos just
fine as well.
But as for Muse, Rosegarden, SooperLooper and CheeseTracker, no go. With
SooperLooper and CheeseTracker, I can load
samples/instruments and "play" patterns and everything appears to work (I
can see things such as level meters etc moving
as expected) except no sound ever emanates from the speakers.
For example, SooperLooper. First I create a virtual soundcard (hw:1) and
start JACK with 'jackd -d alsa'. JACK starts
ands runs fine. Then I start SooperLooper, load a sample (.wav file) and
off it goes apparently just fine but without
sound.
I have tried to connect SooperLooper and CheeseTracker (both on port 128)
to JACK as follows but to no effect. The examples below show what I did
for SooperLooper
What am I doing wrong? I know the answer will probably be simple!
TIA, Mick
[michael@laptop ~]$ aconnect -o
client 72: 'Virtual Raw MIDI 1-0' [type=kernel]
0 'VirMIDI 1-0 '
client 73: 'Virtual Raw MIDI 1-1' [type=kernel]
0 'VirMIDI 1-1 '
client 74: 'Virtual Raw MIDI 1-2' [type=kernel]
0 'VirMIDI 1-2 '
client 75: 'Virtual Raw MIDI 1-3' [type=kernel]
0 'VirMIDI 1-3 '
client 128: 'sooperlooper' [type=user]
0 'sooperlooper '
[michael@laptop ~]$ aconnect 72:0 128:
[michael@laptop ~]$ aconnect -lo
client 72: 'Virtual Raw MIDI 1-0' [type=kernel]
0 'VirMIDI 1-0 '
Connecting To: 128:0
client 73: 'Virtual Raw MIDI 1-1' [type=kernel]
0 'VirMIDI 1-1 '
client 74: 'Virtual Raw MIDI 1-2' [type=kernel]
0 'VirMIDI 1-2 '
client 75: 'Virtual Raw MIDI 1-3' [type=kernel]
0 'VirMIDI 1-3 '
client 128: 'sooperlooper' [type=user]
0 'sooperlooper '
Connected From: 72:0
[michael@laptop ~]$ aconnect -x
[michael@laptop ~]$ aconnect 128: 72:0
[michael@laptop ~]$ aconnect -lo
client 72: 'Virtual Raw MIDI 1-0' [type=kernel]
0 'VirMIDI 1-0 '
Connected From: 128:0
client 73: 'Virtual Raw MIDI 1-1' [type=kernel]
0 'VirMIDI 1-1 '
client 74: 'Virtual Raw MIDI 1-2' [type=kernel]
0 'VirMIDI 1-2 '
client 75: 'Virtual Raw MIDI 1-3' [type=kernel]
0 'VirMIDI 1-3 '
client 128: 'sooperlooper' [type=user]
0 'sooperlooper '
Connecting To: 72:0
--