I've had problems using the 1 frame dissolve trick lately. I'm usually on sndx mac 4.0.5. I use to use it by making a 2 frame dissolve add keyframes to all frames at either 0 or 100 foreground and then in effects editor make it a 1 frame dissolve. That hasn't been working for me lately. Did this finally get broken?
--- In Avid-L2@yahoogroups.com, "bouke" <bouke@...> wrote:
>
> Hmm.
> Thinking of that, i've made interlace detection as well. (for my Avatat
> project ...
> But that was only to detect the start of the cadance, as i was dealing with
> raw footage.
> Could make something that does this, but it's probably cheaper to use my
> Recut, have all shots seperated and set the cadance by hand. Not that much
> work...
>
> Bouke
> (who once used a macro to get 24 @ 25, with an added field every 12 frames,
> that was fun in Avid, having the 1 frame dissolve trick every 12 frames.
> Luckily this was only a 2 hour movie...)
>
>
> VideoToolShed
> van Oldenbarneveltstraat 33
> 6512 AS NIJMEGEN
> The Netherlands
> +31 24 3553311
> www.videotoolshed.com
> For large files:
> http://dropbox.yousendit.com/BoukeVahl998172
>
> ----- Original Message -----
> From: "Mark Spano" <cutandcover@...>
> To: <Avid-L2@yahoogroups.com>
> Sent: Tuesday, March 20, 2012 1:23 AM
> Subject: Re: [Avid-L2] Re: [FCP-L] Easy way to remove 2:2:2:4 pulldown?
>
>
> I have the latest rev Mini. Despite what the manual says, it definitely does
> not do shot to shot cadence detection. I don't have access to the big boy,
> so I'm out of luck there.
>
> I appreciate all of the responses, sincerely. Hopefully my complaints to the
> people I'm working for on this get far enough up the chain to at least get
> someone listening.
>
> On Mar 19, 2012, at 7:42 PM, "Terence Curren" <tcurren@...> wrote:
>
> > Terranex. Has shot to shotcadence detection.
> >
> > --- In Avid-L2@yahoogroups.com, Mark Spano <cutandcover@> wrote:
> > >
> > > Thanks for the reminder Jay. Turns out the first few scenes were all the
> > > same cadence, but the cadence broke off from there and became random
> > > based
> > > on the edit. So this was a case of 24p source footage edited into a
> > > 29.97
> > > FCP timeline instead of what I originally thought (24p edit dropped into
> > > a
> > > 29.97 FCP timeline). It all seems so hopeless now.
> > >
> > > I wish people who shoot 24p would edit and color correct at 24p too.
> > > Then
> > > at least I'd get a 24p file and could apply a proper pulldown in my
> > > online.
> > >
> > > So many wishes these days...
> > >
> > > Thanks for the help!
> > >
> > >
> > > On Mon, Mar 19, 2012 at 6:28 PM, Jay Mahavier <jay_mahavier@>wrote:
> > >
> > > > **
> > > >
> > > >
> > > > As a note, if you are needing to do this to a edited sequence it can
> > > > only
> > > > work if the pulldown was applied after the sequence was cut together,
> > > > so
> > > > only if the pulldown is applied on the output. If the pulldown was
> > > > applied
> > > > during original acquisition or during a transcode process then the
> > > > pulldown
> > > > cadence won't be steady. It will shift from 0/5 to 1/6 to 2/7 and so
> > > > forth
> > > > as you come across edit events. So the process I wrote about only
> > > > works
> > > > when the cadence is steady, like on camera source or when applied to
> > > > the
> > > > output of the sequence.
> > > >
> > > > jay
> > > >
> > > >
> > > > On Mar 19, 2012, at 5:02 PM, Mark Spano wrote:
> > > >
> > > > > Not a bad suggestion. I'll give it a go.
> > > > >
> > > > > Thanks Jay.
> > > > >
> > > > >
> > > > > On Mon, Mar 19, 2012 at 5:39 PM, Jay Mahavier <
> > > > jay_mahavier@>wrote:
> > > > >
> > > > >> **
> > > >
> > > > >>
> > > > >>
> > > > >> Well, I don't know what this would do to your audio, but... Capture
> > > > >> or
> > > > >> export to a file sequence, like TIFF or DPX or something. Then
> > > > >> figure
> > > > out
> > > > >> what the pattern is for the repeat frames, 0/5, 1/6, 2/7, etc. Then
> > > > >> from
> > > > >> the terminal go to that directory and delete all the files that end
> > > > >> in
> > > > the
> > > > >> numbers that you want to get rid of. Then use something like Better
> > > > Finder
> > > > >> Rename to renumber the remaining frames to a sequential set and
> > > > >> import
> > > > that
> > > > >> file sequence or make into a QT or whatever.
> > > > >>
> > > > >> Jay
> > > > >>
> > > > >>
> > > > >> On Mar 19, 2012, at 4:27 PM, Mark Spano wrote:
> > > > >>
> > > > >>> I've been wondering this for a while, and have tried in vain to
> > > > >>> find a
> > > > >> way
> > > > >>> to remove 2:2:2:4 pulldown from clips which have had this
> > > > >>> inadvertently
> > > > >>> (read: incorrectly) added. The only thing I have come up with so
> > > > >>> far is
> > > > >>> this process:
> > > > >>>
> > > > >>> - edit out every fifth frame
> > > > >>> - export QT of edited sequence at 29.97
> > > > >>> - conform in Cinema Tools to 23.98
> > > > >>>
> > > > >>> That's fine, but a bit of a pain, even on a thirty second clip.
> > > > >>> Now I
> > > > >> have
> > > > >>> a 55 minute clip. What's the best way? There should be something
> > > > >>> simple
> > > > >>> that does this - I can't find it.
> > > > >>>
> > > > >>> Any help is appreciated.
> > > > >>>
> > > > >>>
> > > > >>> [Non-text portions of this message have been removed]
> > > > >>>
> > > > >>>
> > > > >>>
> > > > >>> ------------------------------------
> > > > >>>
> > > > >>> To learn more about the FinalCutPro-L group, please visit
> > > > >>> http://groups.yahoo.com/group/FinalCutPro-LYahoo! Groups Links
> > > > >>>
> > > > >>>
> > > > >>>
> > > > >>
> > > > >>
> > > > >>
> > > > >
> > > > >
> > > > > [Non-text portions of this message have been removed]
> > > > >
> > > > >
> > > > >
> > > > > ------------------------------------
> > > > >
> > > > > To learn more about the FinalCutPro-L group, please visit
> > > > > http://groups.yahoo.com/group/FinalCutPro-LYahoo! Groups Links
> > > > >
> > > > >
> > > > >
> > > >
> > > >
> > > >
> > >
> > >
> > > [Non-text portions of this message have been removed]
> > >
> >
> >
>
>
> [Non-text portions of this message have been removed]
>
No comments:
Post a Comment