If you can't find what you're looking for, email
support@thefoundry.co.uk.
FurnaceCore 4.1v1
This is a new release of Furnace, now rebranded as FurnaceCore with lots of bug fixes.
Release Date
28 October 2009
Requirements
- FCP 6.0 or FCP 7.0
- Mac OS X (tested on 10.5 Leopard)
- Foundry FLEXlm Tools (FFT) (5.0v1 or later) for floating license support.
New Features
- The plug-ins help dialogs now have an Enter Serial Number button at the bottom of the dialog. This button launches a web browser to get a license key for the plug-ins. For more information, see Activating FurnaceCore on page 7 of the User Guide.
- F_DeNoise and F_Kronos now have a Deinterlacing Method parameter at the end of their controls. This parameter is useful when applying the plug-ins to fielded footage in order to produce progressive footage. It is also needed when using progressive footage with these two plug-ins. For more information, see F_DeNoise Parameters on page 22, F_Kronos Parameters on page 42, and Using Progressive Footage with F_Kronos and F_DeNoise on page 14 of the User Guide.
Improvements
- Furnace has been rebranded to FurnaceCore.
- FurnaceCore will now render a watermark of dots rather than a black screen with a red cross should no valid license be found.
- The plug-ins now appear in the Effects > Video Filters > FurnaceCore menu with their version number after their name. For example, F_Kronos now appears as F_Kronos (4.1). This allows you to have different versions of the plug-ins available on the same machine.
Bug Fixes
- Fixed issues relating to C++ object instances used as Objective C members. The construction and destruction of the C++ objects was not properly done (or at least undefined). This could potentially have led to memory and resource leaks.
- BUG ID 7250 - Some FurnaceCore plug-ins would introduce softening of the image, and possibly also a downward shift. These issues have been addressed.
- BUG ID 7541 - Inconsistent results in F_Kronos. This bug caused minor differences in the output of F_Kronos on each render. The results should now be consistent.
- BUG ID 8149 - Furnace would crash with High Precision YUV renders. This has been fixed.
- BUG ID 8151 - F_DeFlicker had motion estimation artifacts on the final frame. This has been fixed.
- BUG ID 8208 - F_DeNoise would show blue artifacts on 10-bit YUV High precision renders. This has been fixed.
- BUG ID 8506 - F_DeNoise and F_Kronos would cause Final cut Pro to hang and eventually crash when scrubbing rapidly on the timeline. This has been fixed.
- BUG ID 8597 - The sampled grain result in F_ReGrain was different in the final render. This has been fixed.
- BUG ID 8782 - ReGrain was missing its Show (Result/Grain Plate) option. This has been fixed.
- BUG ID 8957 - FCP scaling resulted in incorrect grain sample scale in F_ReGrain, which would adversely affect results. This has been fixed.
- BUG ID 9236 - F_DeFlicker would produce blank output images if the input images were too small. This could occur, for instance, if the render quality setting of the output seqence was low, and the image in the viewing canvas was zoomed out. This has been resolved by not further downsizing the images DeFlicker uses internally. In extreme cases where the input images are still too small (smaller than 64x64 pixels), a user message is set.
- BUG ID 9291 - A double memory deallocation in F_ReGrain could cause the plug-in to crash. This has been fixed.
Known Bugs and Workarounds
- A note on the viewing Canvas in Final Cut Pro:
In Final Cut Pro, there are two options for viewing the results of an applied effect:
1) You can either scrub along the timeline directly, in which case you need to wait a bit before processed frame results are shown, or
2) you can first render out the clip or sequence (by using Cmd+R, or by selecting one of the Render options in the Sequence menu), and then you can scrub and see results immediately.
It is often the case - particularly when zooming in on frames - that the viewing Canvas will display the result of on-line rendering (a) differently from the result of off-line rendering (b). In particular, footage rendered out (b) is often displayed so that the frames appear to have been slightly softened or deinterlaced. This is merely a Final Cut Pro display issue - the footage exported to file should be fine.
- Advanced effects may require access to multiple different frames on the timeline. There is a known issue in Final Cut Pro, whereby it will intermittently issue such effects with invalid frames.
In these rare instances where Final Cut Pro has malfunctioned, FurnaceCore will display an error message. These error messages differ (depending on the way in which the frame is invalid), but will typically state that a program error related to an incorrect frame fields or frame sizes has occurred. When this occurs, you can generally safely ignore and close the error messages, and continue with your work.
You will only encounter this when scrubbing along un-rendered footage, and changing parameters rapidly. These errors are temporary, and do not apply when the clip been rendered out (by using Cmd+R, or by selecting one of the Render options in the Sequence menu), and also do not apply when exporting or saving your final footage.
Apple is aware of this bug in Final Cut Pro, and will be investigating a solution to the problem in due course.
- BUG ID 8670 - When using plug-ins that have a clip well in their controls (for example, F_ReGrain), you may get poor results if you drop a new clip in without clearing the old one. This is because the plug-in may fail to re-analyse the clip. As a workaround, you should always clear the old clip first before applying a new clip. To do so, right-click on the clip well and select Clear.
- BUG ID 8688 - When rendering fielded footage, F_DeNoise and F_DirtRemoval plug-ins fail to render both fields for the final frame. One field is therefore transparent. Until this is remedied, it is recommended that you remove the last frame from the processed clip or sequence. To clearly see whether a field is transparent in the final frame, the Canvas viewer's zoom level should be set to 100%. At this zoom level, the Canvas viewer's background colour (white, black, or checkered) will show through the unrendered lines.
- BUG ID 8778 - The grain sample box for F_ReGrain can be offset from the user-clicked position, depending on the dimensions of the grain clip. The current workarounds are to either
- click further away from/nearer to the centre of the image, until the grain sample box is where you need it to be, or to
- enter the offset for the grain sample box manually by typing it in.
- BUG ID 8780 - ReGrain does not deinterlace the noise sample before use.
- BUG ID 8958 - Integer sliders, such as F_DeFlicker's Window Size, behave as though they are floating point sliders. This does not affect the result of the effect. For example, the effect of changing an integer slider from 1 to 1.1 will still apply the effect with a parameter value of 1. Unfortunately, changing the slider to 1.1 will result in the effect to be reprocessed - thereby wasting time - even though there was no real change.
Furnace 4.0v2
This is a maintenance release of Furnace to fix a bug.
Release Date
19 November 2008
Requirements
- FCP 6.0 (tested on 6.0.4)
- Mac OS X (tested on 10.5 Leopard)
- Foundry FLEXlm Tools (FFT) (5.0v1 or later) for floating license support.
New Features
There are no new features in this release.
Improvements
There no no improvements to existing features.
Bug Fixes
Fixed plug-in crashes caused by Mac OS X (Leopard) incompatibility with built-in FLEXlm 10.8 licensing module. Upgraded FLEXlm module to 10.8.6 to fix these crashes.
Known Bugs and Workarounds
There are no known bugs.
Furnace 4.0v1
This is the first release of Furnace targeted at Final Cut Pro. These are 32 bit plug-ins.
Release Date
11 September 2008
Requirements
- FCP 6.0 (tested on 6.0.4)
- Mac OS X (tested on 10.5 Leopard)
- Foundry FLEXlm Tools (FFT) (4.0v8 or later) for floating license support.
New Features
There are seven plug-ins in this release.
Improvements
This section will describe improvements to existing features in later versions.
Bug Fixes
This section will describe fixed bugs in later versions.
Known Bugs and Workarounds
There are no known bugs.