Mark Knecht wrote:
>davidrclark(a)earthlink.net wrote:
>
>> Perhaps something more basic should be said about JAMin versus DX/VST
>> plugins and that is that JAMin is NOT A PLUGIN. Yes, it can be used
>> in that manner, but that isn't what it is designed for.
I love using JAMin on drum sub mixes myself. One of the things I really
like about jack is that you can use entire other applications as inserts
very flexibly in Ardour, like using pd as an insert and having it return
both to the same channel and other busses as well. Or even back into
channels on another instance of Ardour for total confusion. :)
>
>
>Dave,
> It's possible that part of the picture is that in the Windows/Mac
>Pro Tools area the Waves tools (and others that I don't use) that
>provide much the same function as Jamin ARE plugins. (See Waves Masters
>suite of tools.) Some people use this strategy, and others use tools
>like Sound Forge as a post processor, like Jamin is today.
>
> Both models are pretty common really.
>
> Supporting your point, though, I don't know of a single tool that
>operates in both modes. Sound Forge isn't a plugin and something like
>the very new Waves L3 UltraMAximizer/MultiMaximizer doesn't run in
>stand-alone mode.
I think T-Racks works in both ways. It was stand-alone first, then it
had a VST plugin version.
>
> (Wanna see a CPU hungry plugin then give the L3 a try!) ;-)
I've not used that yet. One thing that looks cool is the 'seperation'
control, where you can adjust the amount of interaction between the
compressors in the bands. Looks handy.
>
>- Mark
Most of the linux machines around here are currently redhat or fedora, so most of what I have to say is related to these.
It seems that every time I install something I have to look in /etc/rc.d/rc3.d to be sure it didn't install something I didn't want there. It's one thing that just because I asked the install program at insatllation that I wanted everything installed; but it's another that I _don't_ want all of those daemons running. I just want the programs installed, I'll decide when they'll run :)
This brings me to the cron stuff.
Files and directories to watch out for/modify in /etc:
crontab cron.d/ cron.hourly/ cron.daily/ cron.weekly/ cron.monthly/
These places sure can be full of extra garbage if not cleaned up after an install.
I don't see any pressing need to have anything run from cron.hourly on the machines around here; so I have nothing running there. Same with cron.weekly and cron.monthly.
Once a day starting at 7AM when I can't possibly be awake, the cron jobs happen in the order that I want them to sight unseen.
Most of the startup times(or whether things start at all) can be set up in the crontab file. Sometimes I modify the contents of the above directories to suite my needs instead. The only other thing I look out for are things in the cron.d/ like sysstat, which I also tweak the times on if I leave it on at all.
Tracey.
> On Mon Aug 9 13:32:31 2004 Alastair Couper wrote:
> > While we're on the subject, could anyone point to a tutorial or
something
> > similar that covers mastering? Big subject, I know, but I am
wanting to
>
> I found the 'Articles' section at <http://www.digido.com> to be
> a good starting point.
>
> But, of course, they're trying to sell the book.
The book is well worth reading IMO - Bob Katz knows his stuff. I'd also
add that the Mastering Webboard is worth seeing. I've been lurking
there for a couple of years now and learned a lot. The board is
frequented by some fairly big names in the industry (including
Massenburg, Meadows, Collins, Faulkner, Katz, etc.). Topics are many
and varied but are always informative e.g. recently there was a
discussion about when linear phase is preferable to minimum phase and
vice versa.
Greg
Greg
___________________________________________________________ALL-NEW Yahoo! Messenger - all new features - even more fun! http://uk.messenger.yahoo.com
I am looking into getting a decent microphone, but am having a hard time
wading through all the obviously subjective yet passionately held opinions
that I see in various reviews. I am skeptical that a $1000 mic is 5 times
better than a $200 mic. How much of what I read and hear is simply an arms
race for professional studios ? In talking to pro friends with their
multi-k$ mic/preamps, it seems to end with: "It was either that, or give
the money to the gov in taxes."
Any links to info much appreciated.
Hi Mark,
Hope you're doing well.
The item that prompted my posting was one in which the performance of DX/VST
plugins under Windows was compared unfavorably with JAMin under Linux. I
didn't get the impression that the poster was discussing mastering tools,
but I suppose that's possible.
Some users who may look at JAMin and think it's supposed to be a plugin
rather than appreciate that it was specifically designed for something
else, despite the fact that it's displaying a representation of a
real-time 1024-point FFT, or so it would seem.
----------------------
Designing a mastering tool as a plugin may have a slight advantage for
ease-of-use, but it seems to me a relatively larger disadvantage in
that the interface would have to follow plugin restrictions, which
may be rather limiting. I like the JAMin developers' design here.
Philicordia mentioned using JAMin on submixes. I think that's great; but
I'm sure he knows exactly what the tool actually is. I also appreciate his
mentioning that because that's often where I have problems. That 3-D reverb
stuff I'm working on acts almost like an expander on certain material. Under
certain conditions, it also acts as a low-pass filter.
Best regards,
Dave.
There is a killer Soft synth under <place favorite pseudonym for
proprietary monopolistic OS here> win-dohs! It comes in VST and DXi
format. It is Edirols Hyper canvas that runs to GM2 spec and has good
control and functionality in the likes of Steinberg, Cakewalk, etc.
I'm wondering if it could be run under FST or VST_server and used in
<place favorite Open Source OS distro here> Linux in conjunction with
Muse or Rosegarden or other sequencer apps?
Anyone by remote chance messed with this? I will be doing some
experimenting but I have not even got VST server to work properly yet.
Thanks
I am going to buy a new laptop, and I would like suggestions,
recommendations, and anti-recommendations. I did check the archives
first, and I found similar posts, but they're from 2002.
I want one that is very linux compatible, and want to use it for audio
(and video and openGL 3D acceleration as well?) I have no idea what
laptops are capable of these days. Probably everything, for the right
price. I am probably thinking in the range of $1200.
Eventually I'll get external inputs and outputs for (multitrack?)
audio (and video?). USB or firewire or whatever is good now. I could
use recommendations on those, too. :-)
I want to run an XP/linux dual boot, probably debian.
Acoustically quiet would be nice, too.
I currently have a Thinkpad 600E. I like that I can buy replacement
parts on eBay and repair it myself when it breaks. I *don't* like
that it has broken so many times. But I have always been able to fix
it myself. My friend's Dell was not too difficult to repair, either.
I've tried Libranet ("Debian based") and I like what I've experienced
so far, though everything is dreadfully slow on my 600E. I don't mind
trackpoints at all, but I've never used a touchpad long enough to like
it, so I might just not know what I'm missing.
I know there are a lot out there. I am wondering what experience you
have with specific brands and models. I know about
linux-on-laptops.com, but I am focusing on audio, so thought this
would be a good place to ask. What laptops do you own and how do they
fit the above qualifications?
On Monday 09 August 2004 11:33, linux-audio-user-request(a)music.columbia.edu
wrote:
> The second stable release (0.9.0) of JAMin - the JACK Audio Mastering
> interface is now available for download.
Problem with Jamin is that is a process to process thingie. Another program,
eating precious CPU cycles, must be playing and pre-processing the audio to
feed Jamin. I just do not have the CPU guts to run this way. Under that other
OS, I can run this type of software as a standalone (file-to-file) or DX/VST
plugin OK. The three-process (playing app, jack, Jamin, jack) system is just
not efficient.
A standalone or LDASCP Jamin would be worthwhile for those of us with older
equipment.
actually, I believe Jenna says "gulp"
;)
-------
NQuit
www.nquit.com
-------
----- Original Message -----
From: John Check
Sent: 8/9/2004 3:40:08 PM
To: linux-audio-user(a)music.columbia.edu
Subject: Re: [linux-audio-user] Re: OT: Microphone info
> On Monday 09 August 2004 01:02 pm, Jack Bowling wrote:
> > On Fri, Aug 06, 2004 at 07:42:45AM -0700, Mark Knecht wrote:
> > <snip>
> >
> > > <hehe!!> It's a sad state of affairs when Britney cannot make everyone
> > > happy! ;-)
> >
> > Gack...SPIT!!!!
>
>
> Hehe, you know what Jenna Jameson says ;)
>
> Sorry guy, it was too easy
Perhaps something more basic should be said about JAMin versus DX/VST
plugins and that is that JAMin is NOT A PLUGIN. Yes, it can be used
in that manner, but that isn't what it is designed for. It's designed
for putting a very fine polish on an otherwise-finished product.
Using it as a DX/VST plugin is like eating a TV dinner on fine china.
You're welcome to do it, but doing that doesn't make the china any more
durable or the TV dinner taste any better. Inevitably it's going to
cost more to use fine china in everyday use, too, assuming most people
would break a lot of it like I would...
BTW, I think that JAMin is an *outstanding* product. I think it'll
improve my recordings substantially. I'm thinking of using it at the
front end, too --- as an analysis tool. I think I can get a lot better
picture of what I'm in for with a given recording setup --- where the
problems are going to be, etc. Any steps I can take at an earlier stage
I would rather do then than later. (Lest there be any misunderstanding,
I'm not talking about USING JAMin to address these problems, just to
identify them. I WILL use it at the very end to fix whatever is left.)
Thanks very much to all on the JAMin team. Great work.
Regards to all,
Dave.