[ 07-nOV-07 ] MochaV1.0.1 -RC1

Introduction
This release note accompanies a bug fix release candidate of Mocha version 1.0.1 -RC1. The release is available for Windows (XP/Vista), Linux and Mac platform (OSX).

New Features
Safety Zones Positioning.
In order to improve user feedback when positioning reference point’s Mocha introduces a new concept of safety zoning whereby a user is made aware when a reference point is positioned in an ideal location. A line is drawn from the selected point to indicate the level of safety.

Limitations
Safety zoning still is in its infancy and may not be able to provide 100% accuracy when several reference points exist on the same corner of the surface area. The purpose is to generally provide training and guidance to get the most of the adjust track.

Proximity Warning
An extension of the safety zone system: A proximity warning indicates when a reference point is positioned too closely to another reference point: which can lead to undesired results.

Bug Fixed in this release

Reference points lose positioning when a keyframe is for a single point is created on top of a keyframe for the four points
All reference points lose positioning, when a user creates a keyframe for an individual point, where a master keyframe for all reference points already exist.

_There is a drift in the adjust track, when attempting to use the four corners of the surface as a master position. _
Setting the reference points on the surface edges and adjust tracking causes the entire surface area to drift when adjust tracking

_Creating more than three new reference point on a single corner causes the adjust track to corrupt. _
The adjust track is unable to handle more than several new reference points on the same corner of the surface area. The surface shape will corrupt upon adjusting.

Basic Forward workflow does not work correctly when manipulating only one point
When attempting to manipulate a single reference point the surface area collapses during intricate adjust track sessions.

Adjust track drifts during perspective changes
During intricate perspective shifts the adjust track drifts even though the initial track can handle the perspective shift.

_Deleting an active ‘new’ reference point during a backwards workflow will cause the application to terminate _
Creating a new reference point (backwards) and then deleting the point causes the application to immediately terminate

Manipulating multiple reference points causes the adjust track to corrupt the surface area.
Manipulating multiple reference points (where several reference points exist on each corner)

Adding, deleting and then adding a new reference point causes the application to crash
If the u[/u]ser adds a new reference point to a corner, then deletes the reference point only to add it again the application will immediately terminate

Moving two reference points in close proximity to one another causes the surface area to corrupt upon adjusting
Moving two reference points in close proximity to one another and then progressively adjusting any drift will cause the surface area to corrupt.

Creating new reference points and positioning them at a significant distance from the existing reference points causes the surface to corrupt when adjusting
Creating new reference points and positioning them at a significant distance from the existing reference points causes the surface to corrupt when adjusting

Creating three reference points backwards causes the adjust track to drift
Component Affected:

Cycling between three or more backwards points causes the surface area to drift from the tracked layer

Deleting a newly created reference point on each corner of the surface area will cause the adjust track surface to drift
Deleting a newly created reference point on each corner of the surface area will cause the adjust track surface to drift. When playing back the adjust track

An uneven number of points on each corner cause the surface area to corrupt during intricate tracks.
An uneven number of points on each corner cause the surface area to corrupt during intricate tracks.

Reference points cannot be referenced if the points move out of the frame and back in again.
During the adjust track reference points can move out of the frame and back in again (If the shot is shaky or has high levels of panning) this is very common) once a point moves out of frame the adjust track is effected: Even when the point is deactivated or deleted

The master reference zoom window does not update when the active reference point changes
The master reference zoom window does not update when the active reference point changes

_Reference points corrupt the surface area if they are placed adjacently to other reference points. _
Placing a reference point adjacent to other reference points in the application. Will cause the surface area will corrupt during the adjustment process.

Using the backwards workflow with multiple points causes an issue when cycling through reference points as the order of reference points used is lost
Using the backwards workflow with multiple points causes an issue when cycling through reference points as the order of reference points used is lost

Exporting to after effects has a long delay when there are multiple key-frames in the data.
Exporting to after effects has a long delay when there are multiple key-frames in the data. The delay would also cause random crashes on the Mac.

_Opening a project file that’s contains over 100 keyframe causes a long delay, which may lead to a crash. _
Opening a complicated project file that contains more than 100 keyframes causes a long delay in process sing the file, which could eventually lead to a crash.

Opening NTSC interlaced footage, loads up the file sequence in an incorrect order
Opening NTSC interlaced footage, loads up the file sequence in an incorrect order

Opening NTSC interlaced footage, loads up the file sequence in an incorrect order
Opening NTSC interlaced footage, loads up the file sequence in an incorrect order

Opening interlaced footage as progressive footage causes PAL sequences to be loaded incorrectly.
Opening interlaced footage as progressive footage causes PAL sequences to be loaded incorrectly.

_Layers disappear if they are deactivated and then reactivated _
Opening interlaced footage as progressive footage causes PAL sequences to be loaded incorrectly.

Project file corrupted when referencing logo and clips
There is a random issue whereby referencing clips causes the project to be unable to relink footage, and requires the user to have to change the footage name in order to link a project against a clip.

_Creating 8 point or more (using a forward workflow) will cause the application to return points stabilize error each time the reference point is moved. _
A stabilization error occurs when creating 8 or more reference points. The application returns a stabilization error when attempting to position, or to create any further points.

Re-tracking a sequence severely reduces performance.
Re-tracking a sequence severely reduces performance.

Tracking a sequence where the spline is close to the edge causes the spline to drift if a single spline point moves off the image area
Tracking a sequence where the spline is close to the edge causes the spline to drift if a single spline point moves off the image area

Exception randomly occurs when attempting to use a preview background image (Mocha Logo)
An exception occurs when attempting to use a preview background (this issue occurs randomly – as a memory issue) this will cause the application to throw an exception error in the UI.