> Message: 2
> Date: Mon, 25 Jul 2005 07:59:12 -0700
> From: <eviltwin69(a)cableone.net>
> Subject: Re: [linux-audio-user] Opening up the discussion
> To: A list for linux audio users
> <linux-audio-user(a)music.columbia.edu>, Wolfgang Lonien
> <wolfgang(a)lonien.de>
> Message-ID: <1122303552_36501(a)S4.cableone.net>
> Content-Type: text/plain
>
>
>
> On Mon, 25 Jul 2005 12:54 , Wolfgang Lonien <wolfgang(a)lonien.de> sent:
>
> >-----BEGIN PGP SIGNED MESSAGE-----
> >Hash: SHA1
> >
> >Christoph Eckert wrote:
> >
> >> The latter one is the target group we're discussing. Users who
> >> already know about audio, audio synthesis and audio
> >> processing.
> >
> >Hi Christoph,
> >
> >so this includes *me*? As I explained in an earlier post, I did MIDI
> >when we were still using DOS, but audio was (at that time) far without
> >reach - with *any* operating system. Audio was still pre-ADAT, so we're
> >talking 24-track tape machines...
> >
>
> >The first versions of Cubase (on Atari and later on PC) I saw *were*
> >somewhat fire&forget, so I see the point of the whole discussion (I
> >think). Is it easier nowadays? If we speak only Linux, then maybe (with
> >regards to DeMuDi and the planet), but if we see the big picture and
> >think about the time in between and the demand of a "simple" musician
> >who wants to plug & play, then there maybe is a point to that article on
> >O'Reilly.
> >
>
>
> Let's get back to the original premise of the article - Ardour is difficult
> to use without reading some documentation. Let's also get another thing straight
> - Cubase is a toy. It is *not* Pro Tools.
I entirely disagree. I'm not sure if you have used Cubase since Sx1,2,3
appeared, but I respectfully say you do not know what you are talking
about.
I use Cubase professionally almost every day. Please point out one area
(apart from proprietary DSP hardware support) where Cubase appears as a
toy compared to pro tools. I mean, PT only got proper automatic plugin
delay compensation in v6.4 in 2004. How the hell did people mix a drum
kit on the thing before that? (Well, they didn't. That, coupled with the
problematic integer mixer summing is why most people used to use an
analog desk with PT).
Sure, there are things I feel are done better in Ardour, but there are a
hell of a lot of useful features in Cubase that make recording and
editing a joy, particularly when time is limited. And these are not
features to make it easier for a newbie, they are the kind of thing you
discover after a few years of using it.
> Ardour is designed to do the same
> kinds of operations that Pro Tools (full blown, ridiculously expensive version)
> does. No one, to my knowledge, including experienced analog audio engineers,
> ever walked into a studio and started running Pro Tools from scratch without
> reading some of the documentation. I personally don't care how easy Cubase,
> GarageBand, Cakewalk, and other simple audio applications are. I want a full
> scale, multi-track recording system that will do all, or nearly all, of the
> things that Pro Tools does. Could Ardour be made more intuitive? Probably. Is
> that a major problem for anyone who wants to do serious audio work. No. Let's
> at least compare apples to apples here.
I think that for every person asking for Ardour to be easier, there is
another saying 'Noooo, pleeese! Proper multitracking on Linux at last!
This works reliably! I can use it professionally in my studio! Don't
mess it up, for gods sake!!!'.
In my humble opinion, that's not a danger. Seeing Pro Tools as the alpha
and omega all of audio DAWs, however, is. Because, though it is popular,
it ain't the best or fastest software for everyone, amateur or pro.
I do prefer it to the unbelievably obtuse and tedious Logic and DP
though. :)
I don't find Ardour hard to use, and am surprised when a Cubase user
would suggest it is. The steps to set up a session and begin recording
are pretty much identical on both. The problems for me with Ardour are
when I do something that intuitively *should* work, (like selecting
multiple clips and dragging a fade handle should affect the fades on all
the selected clips).. and it does not. Or drawing a box around multiple
automation points and dragging them all up and down...
That what people mean by 'intuitive' and 'easy to use'.
The problem as I see it is that people go through the palava of
installing Ardour, Jack etc, and are then faced with a multitrack.
No beats, no preset samples, no tracker style looper/arranger, the only
way you are going to get good music out of the thing is if you record it
into it. To my mind, that is how it should be, but for many people it's
a cold awakening to the fact that *you* make the music, not the
computer, and they simply don't know what to do next.
BTW, CCRMA has made the installation issue irrelevant as far as I'm
concerned. Many thanks to all involved. Sorry for the long rant.
>
> Jan
>
>
>
>
>
>
> users should -never- be -required- to get trained before the
> instrument will work.
"Never" is a really big word, even without emphasis.
I really hope that you mean musical instruments, not surgical instrumets
as well. ;)
Phil Mendelsohn
--
Dept. of Mathematics, 342 Machray Hall
U. of Manitoba, Winnipeg, Manitoba, Canada R3T 2N2
Office: 446 Machray Hall, 204-474-6470
http://www.rephil.org/ phil at rephil dot org
Hi,
I built a 2.6.12.2 and I see a very confusing thing: I do not
get any capture level on my USB audio card (Terratec Aureon
USB). The monitor channel works (so I know there is at least
a signal coming into the card).
I booted into 2.6.11.7 and it works fine. I remembered the
mixer settings and set them accordingly in 2.6.12.2, but no
luck. Anyone a wee small hint on this issue?
Thanks & best regards
ce
Wolfgang Lonien <wolfgang(a)lonien.de>
> Hi Christoph,
>
> so this includes *me*? As I explained in an earlier post, I did MIDI
> when we were still using DOS, but audio was (at that time) far without
> reach - with *any* operating system. Audio was still pre-ADAT, so we're
> talking 24-track tape machines...
Just to pick a nit:
Audio predates MIDI by about 30 years. Being out of reach I'll agree
with, for sure!, but there were tube D/A converters being built in the
late 50's at MIT (meaning the resistor ladder type guts, not any
"audiophile" type of thing). Tom Stockham and the Soundstream were
pre-MIDI, there were various things going on in Europe, and the Synclavier
was doing sampling and resynthesis (not sampling playback as we know it)
before MIDI.
MIDI was '84, and coincides roughly with the release of the Ensoniq Mirage
-- the first sampler for under $10,000, but there were a lot of expensive
computer systems (standalone or general purpose) that knew something about
audio.
Cheers,
Phil Mendelsohn
--
Dept. of Mathematics, 342 Machray Hall
U. of Manitoba, Winnipeg, Manitoba, Canada R3T 2N2
Office: 446 Machray Hall, 204-474-6470
http://www.rephil.org/ phil at rephil dot org
I have just upgraded to alsa 1.0.9 and the midi controllers on my
evolution mk-249C no longer work.. Has something changed with the alsa
config files? Anyone else see this problem? I can't find anything of help
by googling..
Any help would be appreciated!
All the best,
James
Esben Stien <b0ef(a)esben-stien.name> said:
> Brett McCoy <idragosani(a)chapelperilous.net> writes:
>
>> There's nothing wrong with having a dedicated machine for a studio.
>
> No, but it's not required in any way.
In my opinion, having a dedicated machine or not could be taking as
precisely the difference between a "professional" and an "amateur." (if I
recall a previous thread.)
Another way of looking at it would be that a pro keeps his/her machine so
busy that they need another one just to deal with non-audio stuff. That's
what happens anyway...
Cheers,
Phil Mendelsohn
Chief Engineer
Hotdish Mastering
Hi Well here we go on the 64 bit stuff.
Just installed studio64 and ran Ardour and jamin.
Any known tweaks I need to do? I'm running an Ahthlon 3600 64 with one
gig of ram on the third HD (80 Gig) along with Fervent software on the
other HD (B) and er (cough cough!!) some XP thing (hda) for the missus
you know!!
cheers
Bob
Hydrogen v0.9.2 is out!
____Features____
_General_
* Very user-friendly, modular, fast and intuitive graphical interface based on
QT 3.
* Sample-based stereo audio engine, with import of sound samples in .wav, .au
and .aiff formats.
* Support of samples in compressed FLAC file.
* Internal sequencer and mixer
* Pattern-based sequencer, with unlimited number of patterns and ability to
chain patterns into a song.
* Up to 64 ticks per pattern with individual level per event and variable
pattern length.
* 32 instrument tracks with ADSR, volume, mute, solo, pan capabilities.
* Multi layer support for instruments (up to 16 samples for each instrument).
* Ability to import/export song files.
* Unique human velocity, human time, pitch and swing functions.
* Multiple patterns playing at once.
_Other_
* JACK, ALSA, PortAudio and OSS audio drivers.
* ALSA MIDI and PortMidi input with assignable midi-in channel (1..16, ALL).
* Import/export of drumkits.
* Export song to wav file.
* Export song to midi file.
____Changes____
* New graphics
* Bug fix in export song (using JACK driver)
* Bug fix in export song (wrong samplerate)
* Follow playhead in song editor
* Automatic audio driver selection
* New PortAudio and PortMidi drivers
* Mac Os X port
* Pattern size increased: up to 4 bars
* Random pitch variations
* New instrument editor
* ADSR for instruments
* Low pass filter
* Insert/delete a range of patterns in song editor
* ...and much more ;)
Source tarball and binary linux installer are available at
http://www.hydrogen-music.org
Happy drumming
--
Alessandro Cominu (aka comix)
by Kjetil Svalastog Matheussen <k.s.matheussen@notam02.no>
http://www.notam02.no/radium/
INTRODUCTION
------------
E-radium is Radium and a special version of E-UAE.
Radium is a midi music editor for the amiga and E-Uae is an amiga
emulator.
CHANGES
-------
0.61b -> 0.61c:
-Use the X mouse pointer instead of the amiga mouse pointer. Much
more responsive and smoother.
-Added support for the 1280x960 screen mode. (oops)
-Removed one buzy-loop which I had overlooked when merging two sources,
and increased the idle rate to 20. UAE shouldn't use 50% cpu when idle
anymore.
-Removed use of /dev/rtc. It was not ment to be used.
-Automatically set the window-position at 0,0. No need to see
both the unix window borders and amiga screen borders at once.
Configuring a fullscreen is now a lot less work.
-Lower the use of gfx-mem from 32megs to 16megs to boost the cpu-performance.
(I think)
-Higher the amount of z3 memory from 16megs to 32 megs. 16 megabyte
was far to little as radium often ran out of memory.
-Added "make install"
-Upgraded radium from 0.61b to 0.61c. From Radiums changelog:
-Don't scrollplay when scrolling more than one line up or down.
-Added shortcuts for inserting exactly one line (Left Alt + down)
and deleting exactly one line (Left Alt + up).
-Switched keybindings for continue block (Right Shift + Space) and
continue song (Right Shift + Right Alt + Space).
-Put back the old running-scripts and such that I forgot to include
in the previous release. Shouldn't be that hard to run radium now.
-And other smaller fixes.
Hi,
after having bought a Midisport 8x8 I had reverse engineered
the sysex commands to configure the offline patches. I also
wrote a small shell script to configure it.
These days I have written a small Qt-program to do so. You can
download it from here:
http://sysexxer.sourceforge.net/files/MidischbochtPanel.tar.gz
It's the first program I ever wrote, so don't expect too much.
Please do not send feature requests, there are so many things
I'd like to add but I still have to learn a lot about
programming.
If I continue working on it, then one of the next versions
will be a complete rewrite because the code is so dirty and
inelegant ;-) . But my goal was to write code that is useful
for me.
Hope you like it,
ce