Awake 1.2 32/64-Bit Beta build 39402

Deprecated Awake Builds
1

Fixes and updates:

Fixed a bug where Motion-Depth Blur would crash in some cases if a motion image was not provided.

Corrected some error messages being printed to the Console.

Fixed a bug where the Stereo Stack/Unstack was not propagating Left/Right watermarks correctly.

Threading of the Stereo Stack/Unstack operators.

Fixed a bug in Content Aware resize where the “Keep Aspect Ratio” option would cause a loop of self invalidation and reprocessing of the input image.

Removed the experimental CUDA option from the EdgeAwareFilter as it was unstable and also causing conflicts.

Fixed the EdgeAwareFilter so that it will load correctly in Fusion 6.0.

Changed the behaviour of the “Relative” mode in Frequency blur when using “Scale Blur using Pixel Aspect Ratio” so that it actually uses the correct aspect values.

Some minor UI changes from “Frantic” to “Prime Focus”.

Changed the grid solve in the GridCalibration to support and save anamorphic data, which shouldn’t affect any existing functionality. This is accessible from the UI via a slider allowing the user to specify the ‘Anamorphic Pixel Squeeze’. The appropriate anamorphic information is saved to the calibration file for use in the Lens Distort plugin.

Changed the LensDistortion algorithm to allow for overscan and non-square pixels, which shouldn’t affect any existing operation. In both ‘User’ and ‘File’ mode, ‘Crop/Overscan’ can be enabled in the UI and allows the user to adjust the X/Y size of the image. The plugin currently assumes when removing distortion that the crop values are larger than the original image, and that when applying distortion, the user takes care to reduce the image size to the original dimensions. If this is not the case, then the distortion results will not be accurate. The ‘Anamorphic Pixel Squeeze’ can be manually adjusted in ‘User’ mode.

Several changes to Motion Depth Blur:

  • Fixed artifacts that can appear when “Antialiased Velocity” option is on.
  • Added “Antialiased Depth” checkbox in addition to “Antialiased Velocity”.
  • Set default for “Antialiased Velocity” checkbox to on, since having it on now technically works for both anti-aliased velocity maps, and certain (most) cases of aliased velocity maps.
  • Changed “Brightness Weight” so that values less than 1 still work when “Apply Normalization” is off. Output with “Brightness Weight” less than 1 will look slightly different than before.

Several UI changes to Motion Depth Blur:

  • Organized controls into three tabs instead of two (Motion, Depth, Alpha).
  • Added “Enable Motion Blur” option to allow disabling of motion blur.
  • Added “Completely Opaque” option to set all alpha to 1.
  • Renamed “Alpha Patcher” to “Alpha Increase”, moved to Alpha tab.
  • Renamed “Minimum Brightness Weight” to “Brightness Weight”, moved to Alpha tab.
  • Moved “Apply Normalization” to Alpha tab.
2

Hi,

I have a problem about MotionDepthBlur interface on Fusion x64 6.0 build 511.
Once I drag scale velocity parameter, control slider move without asking.
It follow mouse. I can’t stop dragging until one more click on slider knob.

Sorry my poor english. Do you understand?

Thank you.

3

Hi,

I understand perfectly :slight_smile: Unfortunately, I don’t know what could be causing the problem, and I’m unable to reproduce the bug in Fusion 5.31. (And, I don’t have access to Fusion 6 right now.)

Is the slider still usable? If you can, let me know whether or not the “size” sliders have the same problem in other Awake plugins (e.g. Frequency Blur, Edge Aware Filter)

-Derek

4

Hi Derek,

Thank you for your replay.

I found Frequency Blur has same problem. Blur size slider is strange.
Others are fine!

Thank you.
Hideki

5

Any update on this? Super freaky to have Frequency Blur accidentally get Blur Size set to 3000.

6

Hi Chad,

Yes, there is no response.
Say, what happened to plane 1.3?

Hideki

7

I tried the sliders in Fusion 6 finally, and luckily I’m getting the weird sticky behaviour too. Haven’t pinpointed the root of the problem yet, but I’ll try and get it fixed after the weekend :slight_smile:

8

Afterwards, were you able to solve it?
Very long week end!

9

Just looked into this again, but wasn’t able to solve it unfortunately. Don’t know what could be causing it, but I’ll likely do more investigating after a few other higher-priority bugs are fixed :slight_smile:

-Derek

10

I’ve found out what’s causing it now… but not sure yet if there’s a nice way to fix it. This is a pretty weird bug… it seems the line of code that changes the name of the Blur Size X slider is what’s causing the problem… and I still can’t explain why EdgeAwareFilter works and the other plugins don’t.