[Ardour-Users] Hm...

[Thomas Vecchione]

David-

 Concentrating on the 'How do I side of things'... pardon the acronym
but the short answer is, RTFM.  If you expected to dive into emacs or
vi without reading the manual and be able to use it, you are sadly
mistaken.  I am not even really sure what those have to do with
DAWs(Though technically I suppose it might be possible to program a
mode for emacs to do audio editing in).  Heck without reading a manual
I wouldn't even have a clue how to save a file in emacs when I first
started using it.  This is despite many years of experience using many
different text editors.  And yes I have used emacs for quite some
time.  It is not the same as other text or document editors I have
used, I don't expect it to be, so I read the manual.

In this case Ardour's manual for the basics can be found here...
http://en.flossmanuals.net/Ardour

All of what you want to do and how to do it(Even multiple ways to do
it) are addressed right there.

My second question is, have you ever used another DAW at all?  Because
to be honest the ones that I have worked with which include ProTools,
Nuendo, CuBase, and even Live, all work fairly similar when it comes
to multitrack audio sequencing.  They have differences in interface,
but the basic concepts are all there.  Ardour in particular comes
closest to the ProTools way of doing things, but again none of them
would I expect anyone to be able to use without reading the manual
first, and to be honest most people have to be taught the basics of
multitrack digital audio editing and automation before they really
start to get it.  In fact I am teaching that as part of a class in a
few weeks to people that have been doing audio in one form or another
for a while, but are not professionals yet(Are aiming to be however).

        Seablade

On Mon, Aug 30, 2010 at 10:19 AM, David Kastrup <dak at gnu.org> wrote:
>
> I wish I had made a desktop recording of the last three hours or so.  I
> am a new user to ardour2.
>
> Task: take a recorded WAV file, crop a piece away from the beginning,
> pick a point of time where one starts fading out, pick a point of time
> where the fade out is complete (alternatively, just pick the point of
> time where the fadeout starts and specify a fadeout length).
>
> Save the result from the chosen start position to the end of the
> fadeout.
>
> Would you believe that I have not managed yet?  I am amassing project
> directories, since not even "quit without saving" is working: invariable
> a _lot_ of the previous failed project is saved and interferes with the
> new attempt.
>
> So far the only gain adjustment I have found to be possible is from
> start of project to end (meaning that the fadeout starts at the
> beginning of the recording).
>
> It is, in general, impossible to click on any graphical element with the
> intent to change/move/whatever it.  You first, if at all, have to change
> some internal ardour modes around (with obscurely named mode switcher
> buttons or menu entries elsewhere) to facilitate the desired operation.
>
> I had to restart jack+ardour even in order to manipulate a 44.1kHz file
> when jack happened to run at 48kHz sampling frequency.
>
> Of course, leaving another incomplete project (quitting without leaving
> anything just is not possible).
>
> This does not make much user interface design sense.  If I want to
> manipulate the operation at a certain graphic element, I don't want to
> have to move the mouse elsewhere in order to switch into some mode where
> this is even possible.
>
> I mean: I am an Emacs user, and not at all confused by it.
>
> --
> David Kastrup
>
> _______________________________________________
> Ardour-Users mailing list
> ardour-users at lists.ardour.org
> http://lists.ardour.org/listinfo.cgi/ardour-users-ardour.org
>