Thanks gents!
not sure what kind of scanner it is, but I'll askI'd guess a line scanner,
because as Jeff noted the frameline was off for a handful of frames around the
splices.
In fairness my splices were pretty dodgy, as they pointed out (with pix to
prove the point) - all the splices are cut not on the frameline but rather
within the image frame.
In some cases the film looks to be torn rather than have a clean cut
the film was not spliced together in a way that the two pieces touch one
another, but rather there is a sizable gap between them and the tape does not
reach the edge of the frame.
the material has a number of perforations that are damaged from a previous play
through a projector. Many of the perforations are FULL of tape
so I'm def guilty of some very punk editing - I think if I re-splice and clean
it up I'd get better results... to be continued!cheers Moira
moiratierney.net vimeo.com/moiratierney
On Wednesday, May 29, 2024 at 02:44:09 PM EDT, Jeff Kreines
<[email protected]> wrote:
Jeff Kreines
Kinetta
[email protected]
kinetta.com
Sent from iPhone.
> On May 29, 2024, at 6:46 AM, Scott Dorsey <[email protected]> wrote:
>
> What WERE they scanning them on? A line scanner should be able to take
> some pretty awful splices.
> --scott
And it will typically distort the geometry of the frame several frames away
from the bad splice because the encoder sprocket reading out the scan lines is
typically offset from the aperture by up to a foot. Frame height will vary.
Called the “waterfall effect.”
That’s why line scan scanners like the Spirit or Rank or Scanity have big
problems with any splices and with shrunken film.
An area scan scanner may jump at a bad splice but if overscanned that’s easily
fixed in Resolve.
--
Frameworks mailing list
[email protected]
https://mail.film-gallery.org/mailman/listinfo/frameworks_film-gallery.org
--
Frameworks mailing list
[email protected]
https://mail.film-gallery.org/mailman/listinfo/frameworks_film-gallery.org
