FrameFixer

FrameFixer is a tool designed for detecting scene changes and also for finding and replacing bad frames. Optical scene detection has algorithms optimized for both video and still image sequences.  FrameFixer can also find black frames, flash frames, and duplicate frames.  Upon completion of the initial scan, markers can be added to the timeline at the detected frame locations.  Replacement options include the use of adjacent "good" frames and also interpolated frames using optical flow techniques.  In addition to replacement of single frames,  there is an option to replace multiple adjacent frames.  Replaced frames may be added back to a new track or added to the same track.  Replaced frame are added to an event group to insure that they can be moved together.

1. What to Analyze .

a. Selected Events  Multiple events may be selected from a single track.

b. Loop Region  If selected, the loop region will be scanned.

c. Project  If selected, the entire project will be scanned.

2. Analysis Options  

a. Interlaced.  If ticked, creation of interpolated frames will be optimized for interlaced video.

b. Temporary Resize. If ticked, project settings will be temporarily changed to 1280 x 720 to speed up processing.  Upon completion of the initial scan, project settings will be changed back to the original frame size

3. Optical Scene Detection .

a. Type of footage  Detection algorithms have been optimized for normal video footage as well as a montage of stills. 

b. Set Threshold  Scene change algorithms are by no means perfect given the variety of video source material.  If the threshold is set too low, frames will be missed.  Set the threshold too high and there will be false positives. 

c. Add Markers To Timeline  After the scan is completed, a text file is created of timecodes of predicted scene change locations.  If checked, markers will be added to the timeline at predicted scene change locations.  If unchecked, marker times can still be imported from the saved text file.

d. Save Detailed Threshold Log  If checked, a detailed threshold log will be saved which can be of value in determining the proper threshold for one's footage.  To view the detailed log, click the folder icon    and the log will be opened in your default text editor.  Make sure that the text editor of choice is associated with the ".log" extension.  For each frame the following information is provided: (1) change in pixel luma to next frame; (2) change in pixel luma from previous frame; (3) average luminance; (4) the computed detection measure; and (5) "Frame detected" if the computed detection measure exceeds the threshold.   Here is an example log.

e. Analyze  Starts the scanning and detection process.

f. Re-Analyze    Re-analyzes the data without re-scanning.  This can be a time saver for trying different threshold values. 

g. Delete Markers  Deletes markers from the timeline.  Note that the markers to be deleted will depend on the selected setting in What to Analyze.  If "Project" is selected, all markers will be deleted, regardless of whether they were created during the detection process.

h. Split at Markers  The video track will be split at the selected marker locations.

i. Unsplit Events  Split events will be "unsplit" or "healed". 

4. Bad Frame Detection

a. Type of Frame  Video footage can be scanned for three types of "bad" frames: (1) black frames; (2) flash frames such as found from a camera flash; and (3) duplicate frames which are often found when editing variable frame rate footage.

b. Set Threshold  Bad frame detection algorithms are by no means perfect given the variety of video source material.  If the threshold is set too low, frames will be missed.  Set the threshold too high and there will be false positives.

c. Add Markers To Timeline  After the scan is completed, a text file is created of timecodes of predicted scene change locations.  If checked, markers will be added to the timeline at predicted bad frame locations.  If unchecked, marker times can still be imported from the saved text file.

d. Reference Frames .  The number of frames used in computing a running average of luminance values for use in flash detection.

e. Save Detailed Threshold Log  If checked, a detailed threshold log will be saved which can be of value in determining the proper threshold for one's footage.  To view the detailed log, click the folder icon    and the log will be opened in your default text editor.  Make sure that the text editor of choice is associated with the ".log" extension.  For each frame the following information is provided: (1) change in pixel luma to next frame; (2) change in pixel luma from previous frame; (3) average luminance; (4) the computed detection measure; and (5) "Frame detected" if the computed detection measure exceeds the threshold.   

f. Analyze  Starts the scanning and detection process.

g. Re-Analyze    Re-analyzes the data without re-scanning.  This can be a time saver for trying different threshold values. 

h. Delete Markers  Deletes markers from the timeline.  Note that the markers to be deleted will depend on the selected setting in What to Analyze.  If "Project" is selected, all markers will be deleted, regardless of whether they were created during the detection process.

i. Add Duplicates  A duplicate frame either just before or just after the bad frame will be inserted.  The bad frame is actually "removed" from the event and the duplicate inserted.  The new frame is added to the event's group so that it can be moved with the event.

j. Remove Dups  Removes the duplicates added and "heals" the original event. 

5. Replace Bad Frames

a. Select Frame  There are three options: (1) 1st Dup - the first duplicate frame will be replaced with an interpolated frame; (2) 2nd Dup - the second duplicate frame will be replaced with an interpolated frame; and (3) Multiple frames - replaces multiple adjacent frames.  The third option requires that the user create a loop region around the frames to be replaced as follows: the in point should be placed at the start of the previous "good" frame and the outpoint should be placed at the end of the next "good" frame.  At the moment, the minimum loop length is 3 frames and the maximum length is 10 frames.  The success of replacing multiple frames will to a large extent depend upon motion content. 

b. How to Add Back  There are two options: (1) New Track.  The interpolated new frames will be added to a new track titled "FrameFixer".  Use of this option is recommended if one wants to create a mask so that only parts of the frame are replaced.  (2) The interpolated new frames are added to the same track.  In both cases, the new frames are added to the event group so that it can be moved.

c. Choose Codec  There are two lossless options: (1) Magic YUV and (2) UtVideo.  Since only a few frames are being rendered, the added storage requirement is minimal.

d. Start  Begins replacement processing.

e. Cancel  Exits the script without processing.

Close Menu