The second stable release (0.9.0) of JAMin - the JACK Audio Mastering
interface is now available for download.
JAMin is a GPL-licensed, realtime mastering processor designed to
bring out the detail in recorded music and provide a final layer of
polish. Every effort has been made to ensure a clean, distortion-free
signal path. All processing elements use linear-phase filtering to
eliminate phase distortion.
JAMin runs on Linux using the JACK Audio Connection Kit, a low-latency
audio server. JACK connects multiple applications to a single sound
device, and also share audio among themselves. We rely on other JACK
applications (like ardour, ecasound, or rezound) for playback and
recording.
Homepage
http://jamin.sourceforge.net/
Download
http://prdownloads.sourceforge.net/jamin/jamin-0.9.0.tar.gz?download
New dependencies (since jamin-0.8.0)
swh-plugins >= 0.4.6 <http://www.plugin.org.uk>
liblo >= 0.5 <http://plugin.org.uk/liblo>
(optional, for OSC scene change control)
All other dependencies remain unchanged, the README file has a
complete list.
Usage instructions
http://jamin.sourceforge.net/Using_JAMin.html
Changes since jamin-0.8.0
* Limiter improvements:
-- uses new fast lookahead limiter (LADSPA:1913) from the
swh-plugins >= 0.4.6. The old limiter had some undesirable
sonic artifacts.
-- changed order of final gain and limiter stages.
* OSC control for scene changes:
-- accepts "osc.udp://localhost:4444/jamin/scene" messages
-- new `jamin-scene' command sends them
-- new jamin-cont plugin (LADSPA:1912) sends scene change
messages to the JAMin process via OSC.
(This plugin works with ardour, ecamegapedal and
applyplugin, but segfaults in jack-rack when removed.)
* Increase number of scenes from 6 to 20
* GUI improvements
-- extensive context-sensitive help
-- color editor for highlights and text
-- options pulldown menu for spectrum, crossfade, and EQ
* Better bypass control
-- specific bypass controls for EQ and limiter
-- separate Active/Solo/Bypass for each crossover band
* Global state settings saved in XML file.
* Expanded Russian translation
* Many bug fixes.
--
joq
http://sourceforge.net/projects/liblo/
Theres a mailing list, liblo-devel.
For those who dont know, liblo is a GPL'd implementation of the OSC
protocol, which is a Remote Procedure Call language, designed for audio
software.
http://www.cnmat.berkeley.edu/OpenSoundControl/
I feel that liblo is now mature enough to stand on its own, so I'm moved
it to sourceforge. I welcome help and advice from anyone who feels like
giving it, though I do want to stop the API getting too sprawly.
The current state is that I've just added UNIX domain and TCP transport
support, but they are a bit rough around the edges.
The current contents of the TODO list are:
* Bundle support [needs NTP, argh]
* Add source address to received messages
* More/better regression tests
* More/better example code
* Normalise URI handling [needs discussion]
* GTK/Qt/etc. tie code [maybe belongs in another library]
* OSC pattern matching [still not sure about this one]
* Rendevous/OpenWhatever (eg. howl) service discovery [low priority]
* Add a JACK transport layer [maybe, low priority]
* Make TCP work to spec (currently the TCP server only reads the 1st packet
from every conneciton) [low priority]
Cheers,
Steve
(not the "feature complete" release I was planning, but the list
of changes is enough to warrant a new beta number)
Changes since 0.9beta18.4:
* optimization flags patch from rob holland
* drag-n-drop onto the editor track area where there is no track
creates an appropriate track (or multiple, if appropriate)
* URL-decode drag-n-dropped filenames
* numlock can no longer mess up region dragging
- if numlock generates whatever "Meta" is supposed to be
then Ardour changes its notion of what Meta is.
- if you see a warning about this in the terminal at
startup, you should fix your keyboard map using xmodmap
or equivalent
* remove debugging output from process() tree
* removed VST audiomaster callback debugging output
* UI for VST plugins now offers presets
* VST plugins now save and restore their state
- "chunk"-using plugins are not yet supported
* initial tempo and meter markers cannot be moved, even after
editing
* when cleaning up, prompt user about
each unused playlist (options are
delete, keep, cancel cleanup)
* never decrease the number of panning buffers
* Can't create a new session on top of an old one anymore. It didn't
overwrite the old session, but you would get 2 master tracks and
whatever was in the template, if any.
* freezing tracks
- implementation of freeze completely redone
- unfreeze now works across invocations of ardour, so you
can freeze, exit, restart and unfreeze.
- freeze hides any insert editors, makes rec-enable
and redirect display widgets insensitive and
locks the new region.
- freeze can be used over and over again
* reworked relationship between bounce + freeze
* removed "Loop Region", renamed "Loop Selected Region" as "Loop
Region" because of click-selects selection model
* finally made solo button in mixer strip have the same font size
as other buttons
* removed edit history button and associated code from editor track
* removed "automation style" buttons since they did nothing
* more automation line + point patches from gerard
* fix a couple of valgrind complaints
* region trimming now obeys ignore-snap modifier
* search unused playlists in Session::playlist_by_name()
* added 2-phase unserialization mechanism (Session::StateReady signal)
* empty playlists assigned to correct diskstream at startup
* removed some debug printfs and some dead code
* make Shift_R work like Shift_L
* fix crashing bug with zero-length fade ins
* internationalize all editor operation strings
* transport control is insensitive when there is no session
* fix problems with "region->fill track" where region is at or
beyond current session end
* new mixer strips use the current default width setting
* always save to snapshot
* snapshotting changes the current snapshot to whatever was saved
* delete click_io object at session close, thus allowing new
sessions to load correctly
* fix problem with code ordering in normalize-region operation
(undo after normalize-then-cut will now do the right thing)
* force selection.clear() in file selection browsers when widget
selections are cleared
* committed patches so that ardour now compiles with gcc-3.4. There were
several patches from multiple people. So please let me know if I missed
one.
* patch from nick_m that fixes a problem with the editor-mixer
button.
Greetings:
CC'd to the LAD list. Some developers there are not subscribed to LAU.
It's nothing personal, they appear to like us users just fine, but the
added mail traffic turns into a time sink for them. :)
Best,
dp
davidrclark(a)earthlink.net wrote:
>Greetings all,
>
>Can anyone tell me what the REAL process for getting jack_fst installed
>is?
>
>For fst-1.6:
>
>fixheaders needs to be run from the $HOME/fst-x.x/vst directory as
>"../fixheaders" not from the $HOME/fst-x.x directory as advised by Dave
>Phillips (http://www.djcj.org/LAU/quicktoots/toots/vst-plugins/).
>Small problem... Like Dave said, this stuff isn't for rank beginners.
>
>mkinstalldirs, called from Makefile, was missing. I copied the one
>supplied with Hydrogen. Annoying problem.
>
>
>For jack_fst-1.2:
>
>fixheaders, used above, does not actually fix the headers. gcc doesn't
>understand the initializer. This is what I'm not sure about: How to emulate
>C++ for struct VSTFileTypes initialization. Although I've written a bunch
>of code for C++ classes, I've written virtually nothing for structs in C.
>Lines near 918 in aeffectx.h need to be further modified. This appears
>to be yet another "audioMaster" -related problem.
>
>Thanks for your attention and any info.
>
>Regards,
>Dave.
>
>
>
>
>
P..S to the previous message:
Many thanks to Fred Gleason of Salem Radio Labs http://www.salemradiolabs.com/
for his assistance with this release.
regards
Eliot Blennerhassett
AudioScience Inc.
See the release notes and get the tarball from here
http://www.audioscience.com/internet/download/linux.htm
Many updates to specific card features, plus support for Linux kernel 2.6.x.
Also on the same page can be found the patch for alsa 1.0.5a
(I know, I'm lagging behind)
regards
Eliot Blennerhassett
AudioScience Inc.
Hi,
One of the things that I came away from the meeting in Germany with was
a sense that the LASH protocol used for client<->server communication
needed to be better defined, both on the wire and in the api. What is
really necessary is a network protocol and api designed to allow
high-level ideas like sessions to be represented in a simple format.
The properties that I had been working on have become gobjects and what
was to be a new networking system is a seperate, gobject-based library
to provide a high-level networking api (eg, session_scan(),
session_join(), etc)
The TLA OSC has been banded about quite a bit, and this is not out of
the question; it would be in a set of usable lower-level protocols (or
perhaps the set :)
Bob
--
Bob Ham <rah(a)bash.sh>
/-\
\ / Gay Whales
X Against Racism
/ \
Hello,
An updated version (1.0.1) of libclalsadrv is now available on
<http://users.skynet.be/solaris/linuxaudio>
Changes w.r.t. 1.0.0:
snd_pcm_prepare() is no longer called when the alsa device is
started, only when it is restarted after an xrun. This seems
to solve some problems with 2.6 kernels. Thanks to Matthias
Nagorni and Takashi Iwai for finding this out.
--
FA
Thorsten Wilms:
>
> Additions to the Announcement:
>
> Holding down ctrl freezes the precision axis, so
> only the value can be changed.
>
> Holding down shift freezes the value axis, so
> that you can scale the fan up without worying
> about unintended value change.
>
>
> There will be a context menu with copy, paste,
> (reset to) default, center, previous value
> (like undo).
>
>
> Sine the standard middle click action will not
> work that good with sliders, we thought about
> using it for reset to default or center. But
> we would like to see some standardization here,
> so what other actions are assigned to middle
> click in other (linux) audio apps, and what
> does everybody think about this?
>
I don't think you should use the middle button for anyting.
With scroll-button mouses (which everyone should use), the
middle button is very unconfortable. What about
some creative use of the scroll-wheel instead? The obvious
use is of course to change the value with the scroll-wheele.
I think that would be nice.
>
> There have been some drawing errors happening
> when moving the fan out to one side and then
> the other in one go. But they are actualy hard
> to trigger, so please stress test the demo and
> report to Pete, so we might find out where the
> problem lies.
>
I can't trigger that, but the flickering is annoying.
How about double-buffering the thing?
Another thing, in some situations, I think I would prefer
that the fan is always at maximum size. Could that be
made as an option in the API?
Besides from that, very very nice! I'm thinking about using
it in my configuration code for SND. But the flickering
needs to be fixed.
--