Tweak Software Support

Alan Trombla Apr 29 Knowledge Base

RV 6 Release Notes

CAVEATS and KNOWN ISSUES (last updated 5 May 2015)
As usual we'll update this page, including known issues, throughout the release process, so you can subscribe to this forum thread if you want to get notification of newly discovered issues or additional releases in this series.
  • These notes list all changes since RV 4.2.4. Complete release notes from the RV 4 release series are also available; please see this page.
  • Please report bugs or other issues via email to support@tweaksoftware.zendesk.com.

Version 6.2.3 (RELEASE - 16 Jun 2015)

PLEASE NOTE: RV 6.2.3 uses Python 2.7; if you require Python 2.6, please use RV 6.0.3, which is identical except for Python version.

NEW
  • SMPTE VC-3 Codec (DNxHD) enabled for mio_ffmpeg.

  • PySide Python Modules Distributed for linux only, these modules should be considered alpha, for testing purposes only.

  • Support 12-bit DPX files with unpadded scanlines.

  • RVLS now accepts one or more Session Files as input. In that case, it will report information about the media referenced by the Session File.

  • RVLS has a -o command line option to specify an output file.

  • Environment variable TWK_SERVER_PORT_FALLBACK_COUNT can be set to determine the number of ports RV will try when looking for an open port to listen on for a network connection. The default is to try 10 ports.

  • RVCDL node with node.file property will automatically update CDL values from files of type CCC, CC, or CDL.

FIXED
  • Increase Timeline Magnifier render performance when there are many marked frames.

  • RV could crash after saving a Display Profile containing a LUT

  • Exporting a movie or frame sequence when using a Display LUT could cause a crash.

  • Adding additional nodes to a PipelineGroup containing a LUT could cause the LUT to have no effect.

  • Screening Room: Media with timecode could confuse the sequence setup so that frame numbers did not match sequence frame numbers.

  • Screening Room: Sometimes the correct (current) Version would not highlight in the Screening Room panel.

  • Screening Room: The main view "step left/right" hotkeys were broken when the Screening Room browser was visible.

  • RVLensWarp node: the "center" parameter for the OpenCV distortion model was not used correctly.

  • Complicated PipelineGroup contents, especially PipelineGroups within PipelineGroups, could cause a crash.

  • The -strict command-line flag would cause RV to exit if it could not acquire an rvsolo license. Now it correctly enters the unlicensed state in that case.

  • Two AJA Kona video modes ("10 Bit YCrCb 4:2:2" and "Stereo Dual 10 Bit YCrCb 4:2:2") could not be stored as preferences.

  • A sequence of EXRs wherin all the files did not have the same set of layers could cause a crash.

  • Remote sync could fail on string properties with "/" characters in their values.

  • Some Python headers were missing from the distribution.

  • Multi-byte unicode filenames would prevent mov and avi files from loading.

  • Mattes now render below text and rectangle overlay objects defined in the same RVOverlay node.

  • Geometric resize combined with bit-depth reduction of 16-bit planar images could cause a crash.

  • Custom PipelineGroup contents that include both OCIO nodes and a user-defined custom node could cause a crash.

  • True location of Python site-packages directory was not being added to system path.

  • The disted pyconfig.h included macros specific to the internal build system.

  • In sessions with many paint/annotation strokes, adding new strokes could get very slow.

  • RVSDI: improved output frame rate calculation and display.

Version 6.2.2 (RELEASE - 5 May 2015)

PLEASE NOTE: RV 6.2.2 uses Python 2.7; if you require Python 2.6, please use RV 6.0.2, which is identical except for Python version.

FIXED
  • Use of OpenColorIO could cause a crash (all platforms).

Version 6.2.1 (RELEASE - 29 April 2015)

PLEASE NOTE: RV 6.2.1 uses Python 2.7; if you require Python 2.6, please use RV 6.0.1, which is identical except for Python version.

NEW
  • Licensing RV Via Shotgun Use your Shotgun username and password to get full RV functionality. Some answers to expected questions:

    • The current licensing style is always configurable via the License Manager item on the File menu.

    • The RV (and RV-SDI) version 6.0 executables support both licensing systems (standard Tweak licensing and licensing via Shotgun).

    • RV-SDI can be licensed via Shotgun only at sites using "Super Awesome" support.

    • There’s no requirement that a given site use only one style of licensing.

    • RV licensed via Shotgun is functionally identical to RV licensed the usual way.

    • A user can switch from Tweak-standard to via-Shotgun licensing and back (the choice is stored as a preference).

    • At a facility where standard Tweak RV licensing is set up and working, there will be no change when the user runs RV6 (they will be able to try out via-Shotgun licensing by selecting a menu item if they wish).

    • Licensing RV via Shotgun does not produce any requirement to use Shotgun for other purposes. For example, users may license RV via Shotgun, but not use Screening Room.

    • A user who authenticates RV via Shotgun username/passwd once, and then runs RV at least once a week, will not have to authenticate again. (The original authentication will be refreshed on each run, assuming that the Shotgun server is accessible, and the username/passwd is still valid).

    • Similarly, an RV user who authenticates via Shotgun will be able to use RV "offline" (when the Shotgun server is unavailable) for 30 days, starting from the most recent "online" use.

    Intro video and additional Shotgun setup details available here, and complete RV licensing details here.

  • Media Export with no RVIO License Using RVIO to export media from RV will be allowed as long as RV is licensed (with any licensing scheme). Usage of RVIO "on the farm" (IE unassociated with any local RV process) will still require a standard Tweak license.

  • RVX Functionality in RV The functionality previously available only in the RVX executable will now be available in RV (we will no longer distribute RVX). This includes the use of unsigned custom GLSL shader nodes.

  • Experimental Stereo Disassembly RVPackage to support "disassembly" of top-and-bottom or side-by-side "squeezed" stereo media. (Details in Packages preferences.)

  • Experimental LatLong Viewer RVPackage allows the addition of a LatLong Viewer node for viewing un-warped lat-long (spherically-mapped) media. Shader courtesy The Mill! (Details in Packages preferences.)

  • Per-frame meta-data display from RED R3D movie files.

  • RVSDI: additional supported Kona4/IO4K video modes (UHD 60Hz, etc).

  • RED R3D SDK updated to version 5.3b2 (Jan 2015).

  • The Color Channel Select package can display luminance via the l hotkey.

  • An option on the File/Export menu to export an "RVIO-Ready" Session file, with the current display copied into the "Output" transform that RVIO will use.

  • Improved support for multi-byte encodings in filenames, etc.

  • Quicktime Timecode/ReelName metadata can now be read and written.

  • ARRI Raw SDK updated to version 5.0 (4.6 on Linux because ARRI does not distribute libs compatible with our CentOS 5 target. Please let us know if you need a 5.0 build for linux.)

  • IOARI_ARGS environment variable can set the ARRI Raw decode color space with --colorspace (details here)

  • Quicktime reader supports movies with ICC profile in COLR atom.

  • RVOverlay node supports softer stereo window drawing (details here).

  • RVIO supports ARRI LogC target with -outlogc command-line flag (you can specify LogC EI parameter with -outlogcEI).

  • FFMpeg updated to version 2.6.1.

  • Limited MXF containers support.

  • Additional movieproc type "syncflash" for testing audio/video sync.

  • Custom LUT Package: Added autoload support to source LUT/CDL slots.

  • Sources Details: display files-space CDL settings.

FIXED
  • When viewing a user-defined merge node, zooming the view would appear to affect only one of the merge inputs.

  • If the underlying Audo system supplies a device called "default" selecting it in RV’s preference would not "stick".

  • A Layout view in tiled ("packed') mode containing media with different aspect ratios sometimes did not "frame" correctly.

  • Several problems associated with audio range and offset; in particular a global offset could conflict with a source-level offset causing missing audio.

  • OpenEXR: DWA compression bug (https://github.com/openexr/openexr/issues/156).

  • On the Python Event class, the methods relativePointer and timeStamp did not work.

  • Some quicktimes written by Nuke would not show the first frame when displayed in RV.

  • For quicktime timecode calculations, use frame rate from timecode track, rather than video track.

  • Combining a multi-frame leader with an image overlay could cause RVIO to crash.

  • Opening the preferences dialog could cause the OpenEXR decoder thread count to be reset to 1.

  • Occasional crashes when reading Session Files containing complicated PipelineGroups.

  • Insufficient precision in ASCII session files could cause drift in FPS values.

  • In some cases an RV3-version session file containing annotation paint strokes was not loaded into RV4 correctly.

  • The Annotation mode was consuming some events (like "frame-changed"), and interfering with other modes (like Screening Room).

  • Creation of new Display Profiles was broken.

  • Session Manager "New Node by Type" drop-down automatically populated.

  • Crash when clearing session during rendering.

Seth Rosenthal July 9, 2009 Announcements

The Tweak Helpdesk is part of our effort to support our growing community of users.

The simplest way to communicate with Tweak is to send email to:

support@tweaksoftware.zendesk.com

This will automatically create a new help request, and you will receive a reply with a link to your ticket. You can follow progress on the ticket here at the helpdesk or you can simply reply to the emails for that ticket.

Or you can use our forums to post questions, comments, feature requests or share tips with our growing community of RV users. 

The Tweak Team