On Sun, Jul 7, 2013 at 1:47 AM, rosea.grammostola <
[email protected]> wrote:

> On 07/06/2013 08:20 PM, J. Liles wrote:
>
>>
>>
>>
>> On Fri, Jul 5, 2013 at 1:38 AM, rosea.grammostola
>> <[email protected] 
>> <mailto:rosea.grammostola@**gmail.com<[email protected]>>>
>> wrote:
>>     Also, using the mouse as editing point doesn't look very accurate to
>>     me. Afaik Ardour has a small line in the 'mouse point' so you can
>>     see precisely where you split something. An other way could be using
>>     a editing marker line or the playhead.
>>
>
>  The only reason I can think that you'd want to make the track height go
>> any taller than it already does is that you're trying to look at a weak
>> signal. What you probably want is normalize (point the mouse and hit N)
>> or, for the best results, to increase the gain on your audio interface
>> when recording. I've never seen a program other than a sample editor
>> that allowed tracks to get any taller than non timeline does--and non
>> timeline is not a sample editor. Generally, one wants to have
>> consistently normalized regions on all tracks of the timeline, and then
>> adjust to taste in the mixer.
>>
>> Note that you can change the snap-to setting, even turning it off.
>>
>> You know that a region has been split because the source name is
>> displayed in the lower left hand corner of each region. A line would
>> just obscure some number of samples of audio.
>>
>>
>>
> Thanks, clear enough. Only you did not comment on the accuracy problem
> with the 'mouse hand' for editing, setting loop points etc.
>
>
Well, that's what the grid snap is there for. It's sample-accurate when it
snaps. And for anything else, just zooming in is sufficient.That being
said, I do have plenty of editing operations in mind to add (been thinking
about doing something with 4-point editing), but the truth of the matter
is, I've been using non timeline to record and arrange music for many years
and never run into a situation where the existing editing operations were
not adequate.  Loop points are indeed the most sensitive, but after you set
the point, you can ctrl+shift+drag to 'pan' the audio within the region to
find the perfect loop.

Reply via email to