JACK RELEASE 0.94.0
JACK is a low-latency audio server, written primarily for the GNU/Linux
operating system. It can connect a number of different applications to
an audio device, as well as allowing them to share audio between
themselves. Its clients can run in their own processes (ie. as normal
applications), or can they can run within the JACK server (ie. as a
"plugin").
JACK is different from other audio server efforts in that it has been
designed from the ground up to be suitable for professional audio work.
This means that it focuses on two key areas: synchronous execution of
all clients, and low latency operation.
JACK's webpage is at http://jackit.sf.net .
CHANGES:
Mostly minor, internal changes.
* Added missing extern "C" {} for better C++ support.
* Added missing copyright header.
* Better placement of watchdog check so it doesn't interfere with
freewheeling mode.
* Fixed option parsing problems
* ALSA driver reports actual samplerate, not requested samplerate.
* Handles hardware where playback and capture rates differ better.
* Support for native endian S24_3 format used by USB soundcards.
* jack_metro example ported to new transport API.
* cleaned up prototype declarations for jack_initialize_shm() and
jack_cleanup_shm().
* Eliminated calls to jack_error() when jack_client_new() fails
because the server was not running.
* Eliminated other calls to fprintf() in libjack.
* Won't try and compile iec61883 if libraw1394 is below
version 0.10.0.
* Internal bug fixes.
* Updated documentation.
Taybin Rutkin
>From: tim hall <tech(a)glastonburymusic.org.uk>
>
>I found your english a little hard to understand in this instance. What file
>format are you looking to store your rhythms in? MIDI? wav? something else? I
>would have thought you'd want to store them in a format which could easily be
>transferred between applications, but perhaps I am misunderstanding (?).
Hello. I figured out an analogy: A dish-washer machine has racks shaped
for holding different type of dishes. There is a place for cups and
glasses and a place for plates. To a place meant for a cup, one can
put a glass, a bigger glass, a plastic cup, a coffee cup.
I want make "dish racks" for percussion rhythms. I don't want force
what percussion sounds one eventually uses.
In a sequencer or an audioeditor I could set snap-to labels or marks.
E.g., a "dum" label for a bass percussion. Then I would save these
label sequences to files. A musician could select and load these
label sequences and snap-to the sounds to the tracks.
MIDI is good in that one could easily change the instrument assigned to
all "dum" labels -- in the case where all "dum" sounds are the same.
But we often want have slightly different sounds on each "dum".
MIDI is also good when we want test different rhythms quickly.
Maybe a hybrid system would work better: Named Snap-to labels
and the sounds assigned to the names. First, musician sets sounds to
"dum", "tak" standard labels. Second, musician finds the needed
rhythm. Third, musician renames the labels and assigns different
sounds to the new names. Old names could stay the same if musician
wants to test some other rhythm with the original default sounds.
Two utils are needed: the label track and a name-vs-sound list:
-------------------------
dum tak dum tak tak
-------------------------
dum bdrum.wav
tak snare.wav
Musician may add a new name manually to the list and rename the
labels, or may snap-to a sound to the track.
I would have implemented such a tool to Audacity but Audacity's label
track is not good because the labels cannot be edited. Only the track
"tape" under the labels can be edited: e.g., if one cuts out a piece from
the beginning, the whole rest of the tape moves forward and the label
timings are lost. Also, I could only add labels not remove or move them.
We should standardize the rhythm format so that the rhythms could be
used in any software. So, how to fit the above ideas to existing
systems? Not everyone want use purely my system, I'm sure.
Regards,
Juhana
Hello lists,
I am pleased to announce the initial release of Visecas 0.3.1.
Visecas is a graphical user interface (GTK+) for Ecasound
[http://eca.cx/ecasound], a software package written by Kai Vehmanen
which is designed for multitrack audio processing.
It aims to provide full access to all Ecasound's object by preserving
Ecasound's semantic (which means you do not edit tracks and regions but
chains and audio objects).
Please visit Visecas' webpage at http://visecas.sourceforge.net
This release includes the following features:
* start Visecas as you would start Ecasound (all arguments are
passed on)
* display and control chainsetup's status (valid, connected,
looped, etc.)
* add, remove, rename, mute, bypass chains
* add, remove, attach audio objects
* add, remove, control operators
* control chainsetup position via hscale
* display and control engine status
* edit Ecasound's preferences
Have fun!
Jan
I'm running an HDSP/Multiface on a planet ccrma Redhat 9.0 system. I'm having this problem when I restart alsasound. Below is the readout of `/sbin/service alsasound restart` ... Comments/hints?
Shutting down sound driver [ OK ]
Starting sound driver snd-hdsp [ OK ]
Starting sequencer [ OK ]
Starting sequencer driver snd-seq-midi [ OK ]
Restoring sound driver settings /usr/sbin/alsactl: set_control:799: warning: iface mismatch (2/1) for control #23
/usr/sbin/alsactl: set_control:805: warning: name mismatch (Chn/ADAT Lock Status) for control #23
/usr/sbin/alsactl: set_control:784: failed to obtain info for control #24 (No such file or directory)
[FAILED]
Quite a long time ago now, Richard Bown and I decided we were going to
set up a sort of magazine website for musicians using Linux. It
wouldn't be a developer site or a pro-audio site or even particularly
a technology site, it would just be a site for individuals who were
interested in doing music.
We registered the name linuxmusician.com, and then, inevitably,
contrived to do absolutely nothing at all with it for the next
eighteen months. It became very clear very quickly, as always, that
we simply wouldn't have the time to write a substantial amount of
material for it. The subsequent appearance of the handy QuickToots
site at djcj.org also seemed to reduce the need for some of the
content we'd been hoping to write or solicit.
Recently though we decided that enough was enough, and that we should
just launch the damn thing with the few contributions we could make
plus a community article-submission facility and at the least give it
the chance to flop gracelessly instead of never being launched at
all. So one install of Mambo later, and we present
http://www.linuxmusician.com/
At the moment there is one (1) complete article on there, plus two
brief stubs of articles; there's a links page with hardly any links
yet, and a copy of the bownie.com Guide to Home Recording. We will
continue to post stuff that we come up with, but also if you take a
moment to register you are then very welcome to submit articles,
news, and links. It's not a complete slash/scoop-style community
moderation system; for example, there's currently no comment system
at all. But we're very open to ideas and concoctions that other
people might want to suggest.
Chris
I came across some posts about gdam when I was looking for a Linux
alternative to Ableton's Live. Some of the posts talked about time
stretching, but I can't remember if gdam has time stretching
capabilities or not. Website: http://gdam.ffem.org/
Does Csound offer time stretching?
On Jan 14, 2004, at 5:23 PM, Glenn McCord wrote:
> Is there a loop based editor similar to Sonic Foundry's Acid either in
> existance or under development? What I'm looking for is Acid's ability
> to stretch/compress loops depending on the metronome therefore being
> able to take any loop and use it to any metronome speed. I read Acid
> is a failure under wine.
>
> Thanks.
>
=======================
David A. Hughes
5501 Outley Drive
Mobile, AL 36693
251-662-8197 phone/fax
251-490-4993 cell
davidhughes(a)comcast.net
=======================
I'm not sure exactly where to send something like this.
I'm building a new box for audio work. I let an scp of my 41G of audio
files from my old box to the new one run over night. The transfer took
just under 10 hours and failed on the last few files like this:
warning: Cannot open destination file
192.168.1.9:/mnt/audio/pool/rasox4/rt4b3.wav
warning: Cannot open destination file
192.168.1.9:/mnt/audio/pool/rasox4/rt4b4.wav
warning: Creating destination directory "/mnt/audio/test" failed.(status
= 7)
warning: Cannot open destination file 192.168.1.9:/mnt/audio/test/t0.wav
warning: Cannot open destination file
192.168.1.9:/mnt/audio/test/foo.wav
warning: Cannot open destination file
192.168.1.9:/mnt/audio/test/foo2.wav
warning: Cannot open destination file
192.168.1.9:/mnt/audio/test/foo3.wav
The new box is locked up hard, no keyboard reaction at all, not even
alt-sysrq.
There is a call trace on the screen which I have typed out (and double
checked):
Call Trace:
[<c0185520>] ext3_get_block+0x0/0xa0
[<c0139d7e>] kmem_cache_alloc+0x3e/0x40
[<c01544d0>] alloc_buffer_head+0x20/0x60
[<co1957a2>] journal_write_metadata_buffer+0x42/0x320
[<c01957a2>] journal_commit_transaction+0xcf1/0x1210
[<c0212009>] ip_local_deliver+0xe9/0x250
[<c01ffdb2>] netif_receive_skb+0x152/0x190
[<c01ffe63>] process_backlog+0x73/0x100
[<c01fff64>] net_rx_action+0x74/0x110
[<c011714d>] schedule+0x31d/0x570
[<c0117441>] __wake_up_common+0x31/0x60
[<c0195469>] kjournald+0xc9/0x240
[<c0118a80>] autoremove_wake_function+0x0/0x50
[<c0118a80>] autoremove_wake_function+0x0/0x50
[<c0108e0e>] ret_from_fork+0x6/0x14
[<c0195380>] commit_timeout+0x0/0x10
[<c01953a0>] kjournald+0x0/0x240
[<c0106e49>] kernel_thread_helper+0x5/0xc
Code: 8b 04 87 89 46 14 8b 44 24 2c 3b 50 3c 73 06 49 83 f9 ff 75
<6>note: kjournald[10] exited with preempt_count 1
The new box is:
asus a7v8x-x
athlon xp 2800+
1.5G PC2700 DDR RAM
40G seagate ST340014A
/dev/hda1 2G swap
/dev/hda2 12G ext3
/dev/hda3 empty (reserved for testing demudi?)
/dev/hda4 empty (reserved for linux from scratch?)
160G seagate ST3160021A
/dev/hdc1 ~150G /mnt/audio
mke2fs -j -m0 -b4096 -N500000
linux 2.6.1 (kernel.org sources -- no patches)
preempt on
debian testing (sarge)
minimal install ~150 packages
no X installed yet
Any thoughts?
Thanks,
ERic Rz.
Noticed these on the Debian package list.
1. What is their purpose?
2. What modules are included?
3. Specifically, aside from alsa stuff, jbd and ext3? (I have been trying to
make an initrd to get my ext3 file system working as such to no avail.)
4. Will alsa run without these initrds?