page updated 1 November 2007
version 0.0.2.0 beta
Issues ... Bugs ... Other
Things I think I know about.
- CCCP or Combined-Community-Codec-Pack-2007-07-22.exe when installed causes
FilmCutter to fail when attempts to validate the program with Microsoft's
Application Verifier. The logs shows a "Critical section
over-released or corrupted" message, whatever that actually means.
I have tracked the crash to a problem with DirectShow's graph builder
interface when the code tries to release an IPin pointer or use
DirectShow's renderfile method.
This may mean nothing as FilmCutter runs fine until the Application
Verifier is introduced into the process. Please note that as of
this writing I have no idea what part of the above codec pack causes
- The video scene editor mode has some viewer issues when using multi-video
windows, if the main window becomes small enough the buttons will be
covering some of the video window.
- The video scene editor mode of the program has an automatic minimum
size. The code has a small bug so if the vertical height is small
enough, each time the windows are refreshed the width of the main window
will shrink. Increasing the height of the window will prevent the
aberrant width shrinkage till I can fix it.
- The lexer doesn't do "" "" or """ """ properly
- When a video window gets covered it fails to repaint properly on some
occasions. This is not so much a bug as a lack of code to properly
detect when a window is covered.
- There is an issue with drag and drop sources and targets. Drag and
drop editing is working in the editor window. FilmCutter as a source,
dropping to another application is working. FilmCutter as a drag
target is not working. There is an issue with AviSynth com library
use which is patched in FilmCutter but not fully resolved or understood.
Items below have been addressed in the next version and should be included
in the current or next alpha if there is one -
The following is a list of things I am working on but because of a lack of
time or their lack of importance are still with us or are not included yet.
- .Net plug-in functions really slow things down, hope they don't become a
- An audio enhancement "global OPT_UseWaveExtensible = true" which causes
AviSynth 2.58 to output audio in the WAVEFORMATEXTENSIBLE format is
functional. Sadly it is not working properly in a Direct Show Player
like Media Player Classic or avsFilmCutter, the audio does not work.
VirtualDub can read the scripts and see the audio. FilmCutter's save
audio as wave function reads the WAVEFORMATEXTENSIBLE format but still
outputs the older version WAVEFORMATEX.
- I hope to place the save wave thing in its own thread, someday.
- WAVEFORMATEXTENSIBLE output support for save wave
- Direct audio encoding, no intermediate file
If while working with a project you switch to the script editor to look
at either your source or the project output script or if you open a
project file while in the script editor view / mode switching to the
video scene editor will reset the editors frame rate to 1.00 fps, just
makes the time displayed for the edits wrong and total time is wrong
to. Edits are frame based so the project is not effected.
Just save and then reopen the file while in the scene editor mode / view.
- Thank you Fizick:
A serious bug, programming error has be detected. My aggressive manor
in dealing with a memory leak lead me down the path of shame. FilmCutter
will crash when switching between script editor and any other view that
involved loading a viewer with video. Works fine of my system, but
not on many others. Code was around in version 15 and not 13, at
least a year.
- Thank you, Jon Scruggs:
The frame number can be driven pass the last frame number in the current
version of the interface, by either the slider or shortcut keystrokes
such as PageDown (framerate * 100) or Alt+PageDown (framerate * 1000).
What should happen is that the frame loaded into the viewer should be the
current or last frame if current frame number is greater than last frame
number. Single frame advance works as it is suppose to.
- Thanks you, Jon Scruggs:
Jon has discovered a frame rate and numbering error when switching from
the script editor to the video scene editor. A recent rewrite of the
get frame-rate routines forced a rewrite of the video viewer loading
functions. The loading functions where not updated though out the
- More growing pains, the time display in the scene editor is very
- Font selection is not persistent between sessions.
- On exit FilmCutter prompts the user to save the file if it has been
modified. Answering the question by clicking yes canceled the
- The file modified flag is very messed up when using a project.
User is getting lots of file not saved messages,
- Line numbering as an option.
avsFilmCutter © 2005 - 2007 Robert Clark