Skip to content

V1.7.16: Support of OpenTimelineIO for Blender 3.1
Compare
Choose a tag to compare
@werwack werwack released this 25 Apr 00:03
· 214 commits to main since this release
v1.7.16
91f24eb

Note:
This version of the add-on now support Blender 3.1 and higher. OpenTimelineIO wheels for every OS have been integrated into the package.

1.7.16 (2022-04-24)

Camera HUD:

  • Exposed the size of the shot names displayed over the cameras in the viewport
    in the add-on Preferences panel as well as in the Features panel preferences
  • Fix: The name of the shots is not displayed anymore for hidden cameras

1.7.15 (2022-03-30)

Project:

  • Improve support for sequence names when using the project settings
    In the Project Settings panel the shot name template has been replaced by 3 identifiers,
    one for the project or act, one for the sequence and one for the shot.

    In the main panel the name of the sequence, when the project settings are used, is now
    set thanks to a dedicated dialog box.

Tools:

  • Improve the shot tool named Create Specified Number of Shots

OTIO:

  • Improve support for custom sequence names
  • Clean code for otio and xml exporters

Fixed:

  • FPS variable issue when rendering and when exporting and importing edit file
  • Issue in rendered sequence video name: the name of the take was not added
  • Issue in OTIO export: the exported take was not the current one
  • Issue in Reset Render Settings: initial values were not all restored

Doc:

  • New page for naming of entities

Dev:

  • Improved output messages with logger
  • Added patch V1.7.15 to ensure the data compatibility
  • Refactored the Render Settings properties initialization

1.7.12 (2022-04-24)

  • Integration of a Windows wheel for OpenTimelineIO for Python 3.10.
    This package will be installed on the user Blender Python environment if no
    wheel can be downloaded from the network.

1.7.11 (2022-03-22)

  • Support for Blender 3.1 and Python 3.10

Fixed:

  • Fixed implicit conversions from float to integer for some Blender parameters because this is not
    supported anymore with Python 3.10

  • Fixed float framerate values: now non-integer framerates such as 29.97 are supported thanks to a
    new set of functions in utils.py: convertFramerateToSceneFPS, setSceneFps, getSceneEffectiveFps

Assets 3
Loading