|
Forum Index | Read LUG: Policy/Rules Messages Threads Digests | Post New Message | Search!
Hey all,
I've been using both Logic & DP for quite some time now-- primarily for
scoring to picture
these days. For whatever reason, each has had its advantages for particular
projects, for
me.
However-- I'm now trying to make the switch to *just* Logic, to make my
workflow a little
quicker.
There are 2 functions that I use regularly in DP that I just can't seem to
get working quite
right in Logic, and I'm wondering if someone can guide me-- I've scoured the
manuals,
and still I'm coming up short.
1) Tuplets. That is, if I want to put in a quick run in MIDI step record--
in DP, I can specify
a particular note value ("5 in the place of 1 eighth note" for
example, or "7 in the place of
one quarter note"). In Logic, I don't seem to be able to do this. In
the Matrix editor, I only
seem to be able to type in values of 1, 2, 4, 8, 16 and so forth. If I want
to type in a 7-
tuplet or some odd figure like that with step record, how would I go about
doing that?
2) Accurate *destructive* audio lengthening. If I have a piece of audio,
and I want to
destructively lengthen it by a fraction of a percent-- with pinpoint
accuracy-- how can I
do this? In most cases i want to lengthen the file 0.1% (effectively
transposing it down
0.1%), so I can have my 24fps frame rate match up with someone's 23.98
project.
I've tried the "Time & Pitch Machine"-- but unless I'm
mistaken, if I try to lengthen it by
0.1% in that window, it will try to compensate for the pitch difference, and
the conversion
will take an inordinately long time. I really just want an old-school
transposition--
lengthen the file 0.1%, and not worry about the downward transposition-- for
the sake of
a quick conversion. If I try to use the "Classic" algorithm, I
can't get the accuracy of 0.1%,
since I have to transpose by cents, and the tempo percentage values jumps
past 0.1%.
Thanks, all-- this group has been helpful before, so thanks for everything!
Adam
Adam wrote:
> 1) Tuplets. That is, if I want to put in a quick run in MIDI step
record-- in DP, I can specify
> a particular note value ("5 in the place of 1 eighth note"
for example, or "7 in the place of
> one quarter note"). In Logic, I don't seem to be able to do this.
In the Matrix editor, I only
> seem to be able to type in values of 1, 2, 4, 8, 16 and so forth. If I
want to type in a 7-
> tuplet or some odd figure like that with step record, how would I go
about doing that?
This can be done in the score editor.
> 2) Accurate *destructive* audio lengthening. If I have a piece of
audio, and I want to
> destructively lengthen it by a fraction of a percent-- with pinpoint
accuracy-- how can I
> do this? In most cases i want to lengthen the file 0.1% (effectively
transposing it down
> 0.1%), so I can have my 24fps frame rate match up with someone's 23.98
project.
>
> I've tried the "Time & Pitch Machine"
Try changing "Free" to "Classic"
HTH, Bill
On 04.03.2007, at 21:28, Adam wrote:
> I've tried the "Time & Pitch Machine"-- but unless I'm
mistaken, if
> I try to lengthen it by
> 0.1% in that window, it will try to compensate for the pitch
> difference, and the conversion
> will take an inordinately long time. I really just want an old-
> school transposition--
> lengthen the file 0.1%, and not worry about the downward
> transposition-- for the sake of
> a quick conversion. If I try to use the "Classic" algorithm,
I
> can't get the accuracy of 0.1%,
> since I have to transpose by cents, and the tempo percentage values
> jumps past 0.1%.
Right, the Classic mode works with transposition only.
I think in your case the "Harmonic Correction" is responsible for
a
tonal change. I have that usually off because it sounds better. It is
not only a question of conversion speed.
I just tried the following settings on a 4 min vocal track:
Tempo Change (%): 0.1
Transposition (Cent): Free, 0
Harmonic Correction: Off
Harmonic Shift (Cent): 0
It took 1:27
The same action with harmonic correction on took 1:37
Well, there is a difference although it is not day and night.
BUT - The speed depends on the type of algorithm. I used the Serato
"Pitch 'n Time LE" algorithm. Just out of curiosity I tried the
same
with Logic's "Any Material" setting and needed 4:52 for the same
selection. Actually the selection is one of 9 takes in cycle mode,
the complete original file is 9x4 min (44.1 kHz, 24 Bit).
I would suggest not to guess what could be faster but rather try on a
short part and use the method with the best sound.
___
Peter Ostry
Forum Index | Read LUG: Policy/Rules Messages Threads Digests | Post New Message | Search! Forum Index | Read LUG: Policy/Rules Messages Threads Digests | Post New Message | Search! © 1994-2008, All Rights Reserved. |