• DSOF-25391 - The MIDI Beat Clock Timecode Transport, when set to Metronome mode, now holds at the end of a section when in Playing to End of Section playmode
• DSOF-26439 - Fixed an Access Violation that sometimes occurred when starting a project with pre-configured video ins
• DSOF-26631 - More than 8 RenderStream streams in Mesh Mapping no longer cause black outputs
• DSOF-26721 - Fixed an issue where RenderStream duplicated one stream across outputs

• DSOF-26759 - Added machine name to time readout in the Readout module
• DSOF-26760 - The RenderStream Receive health widget is now resizable
• DSOF-26674 - Increase I/O limit for Designer licence to 6GByte/s

• DSOF-26632 - Fixed an issue where UV mappings were not applied accurately in Mesh Mapping mode
• DSOF-26677 - Fixed an issue where arrowing a Blur layer into video layer degraded the quality of the arrowed media
• DSOF-26678 - Fixed an issue where we, ‘Timed out while transmitting Art-Net packet’ when setting Tracking Recorders mode to Play
• DSOF-26737 - Made Artnet packet sequence count per universe instead of globally
• DSOF-26756 - Fixed an issue where Prop surfaces were masking surfaces behind them when in Add blend mode

The size of the Designer installer for r27.3 (build number 183205) and a number of custom branches exceeded the available RAM permitted as part of the reimaging process. This caused the reimaging process to stop and prevented the user from booting the Disguise media server into Windows. 

We removed r27.3 (build number 183205) from our website. This has now been resolved in r27.3.1, which is otherwise identical to r27.3.

• DSOF-9390 Lux Transparency Support

Non-opaque blend is now supported in Lux mode.

• DSOF-24027 TCP Indirection Controller

There is now a TCP variant of the Indirection Controller, in addition to the existing variant which uses UDP. It works like a UDPIndirectionController with a key value pair list and when the user sends a TCP message with a new key it causes the indirection to switch.

• DSOF-24933 HTTP Sockpuppet

In addition to control via OSC, Sockpuppet now supports control via the HTTP protocol. This makes Sockpuppet more easily controllable by web-based control interfaces and other networked components that utilize HTTP protocols.

The sockpuppet commands are sent to the director, from which the animation values are applied in sync across all machines in the session.

Patching a layer

1. Create a layer in d3 that you wish to patch.
2. Right click layer and select Patch to HTTP

API Overview

HTTP sockpuppet exposes the following HTTP API endpoints, currently under the experimental namespace which is not documented at developer.disguise.one. See http://127.0.0.1/docs/experimental for the Swagger documentation. Note that as these APIs are in the experimental namespace, they may be subject to change before promotion to the non-experimental namespace.

API Usage Workflow

Expected usage of APIs are as follows;

1. Call sockpuppet/easingfunctions to get list of possible easing functions
2. Call sockpuppet/patches to get list of possible patches
3. Using data from sockpuppet/patches, use /sockpuppet/live to make changes to the patch, and therefore the layer. Send to the director only, or controlling understudy.

Live changes sent to the director will be played back in sync across the session with a 2 frame delay.

• DSOF-4156 Shortcut to Expand all/Collapse all groups

The following keyboard shortcuts expand and collapse all groups:
CtrlAlt= (expand)
CtrlAlt- (collapse)
In addition, there is a new Collapse All Groups button in the right click menu of the track which collapses all supergroups and smart groups.

• DSOF-19079 Make strobe layer less intense when created

When a strobe layer is created the rate is now 1hz by default.

• DSOF-23033 Sequencing: Add hot key for layer 'fit to contents'

When a layer is selected using the key bind 'CTRL + SHIFT + F' it will fit layer to contents
The key bind is noted in the 'F1' Shortcut menu.

• DSOF-23439 FolderWatcher abort logs are unclear (e.g. if d3service fails to clean up) 
• DSOF-25049 Add text to manual observation alignment widget explaining initial alignment

We have added text in the Manual Observation widget that explains to users that if a wireframe is not visible, then the user should increase the Stage Render Opacity and adjust the Solved Position and Rotation until the alignment objects are in view.

• DSOF-25224 DSE accounting for surface normal relative to projector

We have added functionality to the Dynamic Blend workflow which accounts for the surface normal relative to the projector. When users edit the ‘Cutoff angle’ in the Dynamic Blend section of each projector and the relative angle of the projector and the surface normal exceeds this value, then we remove the contribution of that projector and use projectors with a better view instead.

• DSOF-25614 DSE: promote "dynamicSoftEdgeFullRes" to user-editable per-projector option

The option switch dynamicSoftEdgeFullRes has been promoted to a user-editable per-projector option. This enables the soft edge resolution to vary per projector rather than set across the whole project. In the projector settings, the “Dynamic Blend” section has a “Resolution factor” field 1/16, 1/8, 1/4, 1/2 and Full. 1/16 is the default for best performance. The "Resolution factor" changes DSE resolution, affecting blend quality (it is visible).

• DSOF-25623 DSE: re-organise Dynamic Blend section to hide less-used settings

The Projector Dynamic Blend section now has an Advanced Blend Setting sub-section with less frequently used options, to save on screen real estate.

• DSOF-25657 Make crash reporting disabled by default

Crash dumps are created when an unhandled exception occurs. This incurs a brief stall while the dump is generated. This behaviour is now opt-in and disabled by default. It can be enabled by one of the following two methods:

1. Option in Designer.  d3 > Advanced > Enable Crash Reporting > On / Off

When On, it generates a dump file on the local machine when an Access Violation thrown.
When Off, it doesn't generate a dump file on the local machine when an Access Violation thrown.

1. Advanced Project Setting > Option Switch: enableCrashReporting is Project Wide and depending which machine has the Access Violation thrown, it will generate a dump file on that specific machine.

• DSOF-25922 Keyboard modifiers for fine and coarse control of feed warp points

When on a KVM or on a laptop trackpad it tends to be easier to use a keyboard than use the cursor. Using the keyboard means the points move really slowly though. Adding modifiers means easier control of points without the movement being forced to be one slow speed. The following modifiers have been added:
- Holding Ctrl while moving feed warp points with arrow keys causes them to move in smaller increments

- Holding Shift while moving feed warp points with arrow keys causes them to move in larger increments

• DSOF-26395 Allow users to use field of view for XR calibration when focus encoder unreliable

If a tracking system is not sending a reliable focus encoder value, it can be preferable to disable it and use the field of view instead as a basis for XR calibration. Now, when the focus encoder value in the camera tracking source is disabled, it will be overwritten by the horizontal field of view if the focal length value is enabled

This value is shown as the zoom value when doing XR spatial calibrations, and is also used as the zoom encoder value when interpolating calibrated lens poses during operation

When overriding, the field in the tracking source is highlighted red, with the help text explaining why it is overridden. Similar highlighting and help text is also shown when the field is locked from the spatial calibration. All the equivalent of above is also true for focus encoder, overriding with focus distance where available.

• DSOF-7470 Removing resources doesn't work in session (previously Remove missing media on editor machines resets on reconnecting to session)
• DSOF-8134 - Fixed an issue where population masks with alpha gradients were not respected in the Lux renderer
• DSOF-23636 - Dynamic Soft Edge:  Fixed an issue a banding effect on blended region when brightness changed
• DSOF-23747 - fixed a CHECK_LOGIC error when launching RenderStream for mesh mapping with no screens
• DSOF-23788 - Fixed an issue where mesh mapping frustum jitters when following a camera
• DSOF-24891 - Fixed an issue where Tracking History would cast time to float and back, potentially causing minor issues for long running projects
• DSOF-25012 Fixed an issue where the installer had no 25G/100G rivermax licence files if offline
• DSOF-25036 - Fixed an issue where mesh projection would give strange viewpoints when a camera is very close to screen
• DSOF-25046 - Fixed an issue where graphics semaphores would not be released properly on Nvidia machines.
• DSOF-25101 - Fixed an issue where 'StageEditor' object had no attribute 'onResourceChanged' error when opening Stage Editor Menu.
• DSOF-25157 - Fixed an issue where the QuickAlign/AR alignment tool would inaccurately select vertices
• DSOF-25195 - Arri Lds driver: removed "sensor height" field to avoid overwriting aspect ratio
• DSOF-25358 - Fixed TrackedPoint labels  being incorrectly offset
• DSOF-25576 Dynamic Soft Edge: Fixed an issue where a profile would not be created if the empty project was created after d3 version was updated
• DSOF-25648 - Fixed an issue where OscDevice 'receiving' attribute did not match the true state
• DSOF-25856 - Fixed GraphicsDebugger log missing newline
• DSOF-25859 - QuickCal: Fixed an issue where rendering lineup was very slow for large meshes
• DSOF-25871 QuickCal: Fixed an issue where occlusion calculation for hidden markers was incorrect
• DSOF-25878 QuickCal: Fixed an issue where mouse-over help text was not shown for some settings
• DSOF-25919 - d3service: Fixed an issue where getThisMachine() would mix up machine Range and Model in API v1 response
• DSOF-25940 - Improved the resolution of the disguise logo in the installer 
• DSOF-26162 - Quest 3 headset now works properly with d3
• DSOF-26199 - Improved performance of DMX screen
• DSOF-26580 - Fixed a RenderStream workload crash on launch with Exception: ILLEGAL_INSTRUCTION

• Added support for VX 3 server type
• DSOF-26613 - "d3-events" EventLog now included in System Diagnostics

• DSOF-24757 - Fixed an issue where focus distance showed negative values in the object
  tracking mode
• DSOF-26575 - Fixed an issue where 2.5D assets incorrectly said it was at zero depth

• DSOF-26470 IP VFC: inform a user when no SFPs are connected

When using an IP-VFC card, we have added error reporting into the feed scene in the form of a tooltip for the ‘Sync Mode’ button. 

When a user is using the PTP option in sync mode, if there is no compatible 25Gb SFP in Port 1 on the IP-VFC then the sync mode button will turn red and a message will state the Disguise media server and VFC slot number which has the invalid configuration as seen below:

When a user is using the  EXT option in sync mode, if there is no compatible single or dual SDI SFP in Ports 3 and/or 4 on the IP-VFC then the sync mode button will turn red and a message will state the Disguise media server and VFC slot number which has the invalid configuration.

• DSOF-26538 IPVFC - change PTP_LOCKED mode name to PTP_SYNC

When using IP-VFC, we have changed the name of the PTP sync mode located under the Sync Info tab in the IP-VFC control widget from PTP_LOCKED to PTP_SYNC

• DSOF-26571 TrackJump - increase maximum section number from 32 to 1000

• DSOF-26139 - Changed the wording of "Replace with another Mapping" button to “Replace with selected Mapping”, and a tooltip with further explanation has been added to video layers

• DSOF-22638 - Fixed a video memory leak when mapping/unmapping video inputs
• DSOF-24199 - Fixed a hang that could occur on shutdown due to in-flight HTTP requests
• DSOF-24760 - Fixed an issue where object tracking mode for camera focus distance did not account for object hierarchy
• DSOF-25317 - Fixed occurrences of `toFree.addr4 != 0` error messages when using RenderStream
• DSOF-26140 - Fixed an issue when key-framed, Mapping Replacement names only updated after refresh of layer
• DSOF-26168 - Stage Render Layer - Fixed an issue where screens in 'Frontplate' layer mapped to the backplate showed up red
• DSOF-26339  - Fixed an issue where Dynamic Soft Edge did not affect Actors in session
• DSOF-26361 - Fixed an issue where the ‘Find/replace usages’ widget did not have a scrollbar when it extended offscreen
• DSOF-26377 - Fixed a shader errors being thrown when using radial mapping
• DSOF-26410 - Fixed an Access Violation using Blur layer

• DSOF-23937 IPVFC: Device names in NMOS are more descriptive

When using the IP-VFC in ST 2110 mode, we have changed the NMOS device label so that it clearly states the slot that it is occupying on the Disguise media server, for example ‘Slot 1’. In previous releases, the NMOS device label of each IP-VFC would be ‘Disguise Port 0’. 

We have also changed the NMOS node label to be the user-defined name, which is often changed from the Windows name to match the role in which it occupies within the d3net session i.e. Actor01.

• DSOF-25640 - Fixed an issue that occurred when as an Editor, you were not prompted to join a session when opening project file
• DSOF-26138 - Fixed an issue where asset sync in RenderStream did not sync deleted files
• DSOF-26350 - Fixed console spam caused by setting a placeholder clip on a videoin
• DSOF-26391 - Fixed an issue where LayerStack was not being applied to video input

• DSOF-25853 - Fixed an Access Violation that occurred after changing plates meshes within a 2.5d asset, and then undoing changes with ctrl + z clicked quickly several times
• DSOF-25991 - Fixed an issue where malformed PSN data when recorded could not be played back and caused other device recordings to fail
• DSOF-26094 - Fixed an issue where RenderStream Compressed caused d3 framerate drops
• DSOF-26097 - Fixed an issue where Device Recordings would intermittently appear empty if continuously receiving data and jumping through sections on the timeline
• DSOF-26157 - Fixed an issue where the Editor moved forward in the timeline rather than following the Director's timeline after unlock and lock to Director
• DSOF-26185 - Fixed issue where itu709 setting in gamma mode corrupted the display of certain files
• DSOF-26208 - Fixed 2.5d assets included in project diag resulting in very large file sizes
• DSOF-26288 - Fixed an issue where the DPX feed export yielded an unexpected colour space shift
• DSOF-26305 - Fixed an OmniCal lenscalibrator crash on startup due to a DLL issue
• DSOF-26319 - Fixed an issue where d3 could intermittently crash to desktop if a connection was lost while sending a failed HTTP Request

• DSOF-23762 Ability to see usages of mappings
• DSOF-25935 Replace all usages of a mapping

The above two improvements are accessible via the 'Find/Replace Mapping Usages' button in the Mapping editor.

• DSOF-23946 Remove "CodeMeter USB Mode" check from installers
• DSOF-24291 Show Designer software version in UI

We have added the Designer software version in the bottom right of the UI next to the machine name.

• DSOF-25256 Machine List in Monitoring Manager should be alphabetical

We have made the Machine List alphabetical within the Monitoring Manager window, found by left clicking on the FPS in the lower right hand corner of the track.

• DSOF-25700 Warn the user when the audio codec in their embedded audio is not supported

We have added a notification to warn the user that an unsupported audio codec is recognised when using embedded audio, and to convert the audio codec to either ‘sowt’ or ‘twos’.

• DSOF-25873 Define a certain degree of a cylinder mapping

We have added an Arc field to allow users to choose the degree, (0 to 360,) of coverage on a Cylindrical Mapping. This option is the same as the Arc field on the Spherical Mapping

• DSOF-25936 Auto-select first enabled layer in feed warp editor

In previous releases, when a user left-clicked the + button under Deformation layers - found within the Edit Warp Menu in the feed view - the first deformation layer was selected, even if the deformation layer had been disabled. In r27.1 the first deformation layer that is selected is the first one within the stack that is enabled.

• DSOF-26029 OmniCal: export unstructured point clouds (without invalid points)

We have enabled users to be able to export unstructured point clouds when using OmniCal. Structured point clouds directly correspond to the 2D grid output by projectors, and will include invalid points as NaN values. These values are usually those that were not visible to enough cameras or where 3D reconstruction failed. Unstructured point clouds provide no invalid points as NaN values within the export.

 This can be found in the Advanced section in OmniCal Calibration and clicking on ‘Save PointCloud’. This will save four PCD files for each projector grid within the Optical Stage Plan folder:

• Aligned and unaligned (as captured)
• Structured and unstructured 

• DSOF-21670 DMX String: Now defaults to 1 fixture

We have changed the default behaviour of new DmxStrings to one fixture.

• DSOF-24032 - Fixed an issue where an 'Indirections' object had no attribute 'role' - d3net Manager
• DSOF-24561- Fixed an issue when starting a RenderStream workload, RMAX receiver was being attached/detached several times
• DSOF-25904 - Sockpuppet: Fixed an issue where moving the Frame Index value caused stuttering and jumping of playhead in Video Clip
• DSOF-25950 -  Asset preview for 2.5D beach asset no longer clashes
• DSOF-25987- Fixed an issue where adjusting prediction would break spatial mapping
• DSOF-26146 - Added feedback when active latency automatic calculation is higher than the manually set active latency override
• DSOF-26247 - Fixed an  Access Violation when starting DSV video in preview
• DSOF-26251  - Fixed an Access Violation opening Virtual Reality Navigator editor
• DSOF-26290 - Fixed an issue where MAC addresses stored in NetworkAdapter were wrong
• DSOF-26137 - Fixed an issue where UE would crash on launch when a single fragment was too large
• DSOF-26562 - Fixed an issue where pre-multiplied alphas did not look correct in 2.5d workflows
• DSOF-26250 - Fixed an Access Violation when using VR headset

r27 introduces a number of improvements specific to Disguise media servers with a Matrox SDI capture card installed. These include:

• Mixed frame rate support - users can now work with any combination of video resolution formats and refresh rates across each video input. This resolves the outstanding TA-19: Matrox Video capture cards advisory found here
• Ultra low latency mode - we have reduced the video latency when running in ultra low-latency mode from 4 frames per second to 3 frames per second at 30Hz, 50Hz and 60Hz
• General performance improvements

These improvements are only available when running Designer software version r27 and above alongside the following OS builds - all of which are available to download on disguise.download/#hardware or https://disguise.cloud/account/software/os-downloads:

• DSOF-21761  Support for mixed frame/ refresh rates which are not related
• DSOF-24646 - Fixed an issue where 1080psf  29.97 VideoIn  on a gx3 gave half quadrant artefacts
• DSOF-24666 - Fixed an issue with interlacing modes other than discard did not work
• DSOF-25337 - Fixed capture buffer delay sporadically being too large resulting in tearing
• DSOF-25394 - Fixed interlaced capture on driver 10.4.101.1269 having fields in the wrong order
• DSOF-25460 - Fixed an issue when using Quad coupled mode, losing inputs 2-4 would result in a black frame
• DSOF-25465 - Fixed an issue where only the 12G-enabled ports hold onto the last frame if input was removed

• DSOF-26466 -  Fixed an issue where RenderStream Proxy did not show up on Director if both 25g connectors were active
• DSOF-26550 - Fixed an issue where a duplicate process was started when clicking quickly on the start or restart workload button

• DSOF-25851 - Fixed Manage Renderstream Workloads not working reliably

• DSOF-26273 - Fixed console spam with 'Updating Scene Due to Change in Resource' every time feed scene is changed

• DSOF-25410 - Updated the way proxy and non-proxy streams are filtered in health status widget
• DSOF-25448 Receive Health status in the RenderStream layer editor should no longer report "Frames Dropped Recently" for Proxy streams.

• DSOF-23229 - Fixed an issue where the current status of RenderStream was not shown under ‘Network’ tab within d3manager
• DSOF-23266 - RenderStream Workload widget does now automatically shrinks
• DSOF-23889 - Fixed an issue where d3manager did not update network share location when changing d3 projects folder
• DSOF-23890 - Fixed an isse where d3manager did not update network shares if not running as admin / elevated
• DSOF-24449 - Fixed an issue wher eRenderStream uncompressed streams intermittently only rendered black
• DSOF-24474 - Fixed an issue where Heap corruption in Rivermax cleanup code caused a crash in touchdesigner
• DSOF-24475 - Fixed a CL_OUT_OF_HOST_MEMORY error on vx using RenderStream
• DSOF-24622 - Fixed an issue where workloads could occasionally get stuck in awaiting requests
• DSOF-24648 - Fixed an intermittent flickering issue when starting RenderStream
• DSOF-24706 - Fixed an issue that occurred when using an uncompressed Unreal RenderStream, some actors showed RECV 0
• DSOF-24707 - Fixed an issue where an exception occured when trying to remove a channel mapping
• DSOF-24715 - Fixed an issue where actors crashed whilst starting and stopping workload
• DSOF-24838 - Fixed an issue where pool usage was not shown for assets using the default channel name
• DSOF-24855 - Fixed d3 heap corruption and a crash to desktop with RenderStream compressed in LibGpuVideoCodec (AMD 22.Q2)
• DSOF-24918 - Fixed an issue that occurred If the drive that d3manager was pointed at disappeared, launching d3 remotely on that machine would default to another drive
• DSOF-24943 - Improved RenderstreamSystem system speed when updating statistics about many streams
• DSOF-24974 - Fixed an issue where starting and stopping a render stream workload reduce performance of the director
• DSOF-24984 - Fixed an issue where launching d3manager with a missing d3 projects folder would result in the next project folder from the list being launched
• DSOF-25009 - Fixed an issue where adding samples to an uninitialized graph descriptor caused an exception
• DSOF-25023 - Fixed a crash on director when receiving proxy streams
• DSOF-25028 - Fixed an issue where if d3service crashed while RenderStream is running, all renderstream processes on that machine will no longer be controllable via d3net
• DSOF-25039 - Fixed an intermittent issue where streams were occasionally never received
• DSOF-25096 - Fixed an issue where calling an invalid API endpoint can intermittently caused a crash to desktop
• DSOF-25113 - Fixed an issue where 16K or higher screen couldn’t use blur layer even using enableSLC switch
• DSOF-25136 - Fixed an Access Violation can occur when moving the playhead out of a RenderStream layer after the GUI had been reloaded during development.
• DSOF-25137 - Fixed an issue where Renderer Graph was not accessible via the Workload details GUI
• DSOF-25183 - Fixed an issue where a video layer missing media highlight no longer updated as frequently to changes in sequencing
• DSOF-25185 - Fixed an issue where a vx occasionally dropped all received frames with RenderStream Uncompressed
• DSOF-25237 - Fixed an issue where missing media scenarios with a Bitmap layer caused notification spam: Corrupt keyframe, please check sequencing
• DSOF-25327 - Fixed an issue where Feed Mapping Editor still opened and is interactable even if the feed mapping is "Locked"
• DSOF-25338 - Reduced active time of "Packets dropped recently" 
• DSOF-25556 - Fixed an issue where editing Feed Warps intermittently did not take effort on actor machines in session, but the control points did move
• DSOF-25568 - Fixed an issue where RenderStream failed to initialise due to an exception, rs_initialise returns success
• DSOF-25629 - Fixed an error when launching project on actor, "Current d3projects folder not available on machine..."
• DSOF-25631 - When opening d3 manager "Run Project" buttonis now populated with the "current" project
• DSOF-25765 - Fixed an issue where Understudy takes over but does not indicate on director, sometimes failing to trigger matrix failover
• DSOF-25829 - Fixed RenderStream Failover
• DSOF-25892 - Improved Track widget updates when RenderStream workload status is updating
• DSOF-25893 - Improved receive health widget
• DSOF-25932 - Fixed an issue where workload state intermittently got stuck in "Launching"
• DSOF-26095 - Fixed an issue where some RenderStream uncompressed streams failed to start on the director when using an actor controller to run many streams
• DSOF-24245 - Fixed an indefinite hang/crash due to exhausting video memory
• DSOF-25905 - Fixed an issue where mesh mapping fragments teared when the engine origin is changed in real-time

• DSOF-25476 - Fixed an issue where Projection Screens could be inactive on Editors when animated with Animate Object Preset
• DSOF-25569 - Fixed stYpe Focus Distance not being used
• DSOF-25930 - Fixed an issue where 2.5D assets did not auto-extract on Actors
• DSOF-25983 - Fixed Black Magic Video Hub 3g no longer receiving commands
• DSOF-26026 - Fixed a topological sort error for 2.5D assets and plates
• DSOF-26093 - Fixed an issue where 2.5D had an error parsing depth map when an image was fully transparent

• DSOF-21902 - Fixed an issue where projects failed to load with error: m_delayDsp
• DSOF-23674 - Fixed an issue where video layers used in Layer Stacks were previewing the second to last requested media
• DSOF-25485 - Fixed an issue where pop-ups from session widget flickered back and forth between being on top and behind of the session widget
• DSOF-25499 - Fixed an issue with ncam tracking
• DSOF-25880 - 2.5D assets no longer have lower selection priority than displays
• DSOF-25912 - Fixed an issue where Device Recordings did not play back captured PSN data correctly
• DSOF-25943 - Fixed an issue where d3 was unable to import proxy files it had just made of versioned fragment replacement video clip
• DSOF-25949 - 2.5D - Depth maps no longer interpreted incorrectly
• DSOF-25976 - Fixed an issue where Perspective Mappings only appeared n Director, not Actors
• DSOF-25990 - Moved Variable Timecode implementation behind the option switch 'forcePIDTimecodeChase
• DSOF-26027 - Fixed an issue that occurred when using sockpuppet bank editor, using NONE did not respect transition times
• DSOF-26028 - Fixed an issue that occurred when switching from a NONE clip in a sockpuppet video layer the frame counter did not reset on the clip
• DSOF-26051 - Fixed an issue where machines with capital letters in their hostname did not show VFC status information

• Added support for vx2+

• DSOF-25920 2.5D - Fixed an issue where changes in z-offset for plates with depth maps don't get saved to 2p5d file

• DSOF-24939 - Fixed an Access Violation when selecting the tracker delay calibration thumbnail
• DSOF-25649 - Video mode Inframe - Fixed an issue where a sockpuppet video layer playing audio caused d3 performance to drop
• DSOF-25869 - Fixed an issue where transparent screens had a black background in non-UV regions in an upgraded project
• DSOF-25898 - Fixed an issue when using 2.5d where an artifact was present in parsed depth maps containing narrow non-alpha columns
• DSOF-25926 - Fixed an issue where the GUI was black when starting Designer on a server when Parsec Virtual Display Adapter is installed

New 2.5D Workflow

The new 2.5D workflow is also covered in the Disguise User Guide, together with a demonstration video, here.

What is 2.5D?

2.5D workflows bridge the gap between traditional 2D video plates and full 3D generative scenes.  By building up a scene with layers of images or video plates, with the possibility to add depth or shaping to the plates, users can quickly create a realistic-looking scene with parallax. 2.5D assets can be saved as .2p5d files and shared across projects or created using external integrations such as Cuebric to harness the power of generative AI to optionally create the image or just to speed up the process of image segmentation using AI.

What has changed?

2.5D has been possible with Designer prior to 26.3, however, it required the manual creation of plates using a projection surface per plate, manually applying specific settings to each plate, and the use of a StageRender layer. With r26.3, 2.5D has been made a first-class citizen in Designer with its own layer type and the concept of a 2.5D asset. This dramatically increases the usability and speeds up the workflow, as well as making it more intuitive and less error-prone.

In addition, the Cuebric integration speeds up the pipeline between the creative and volume control stages of the end-to-end workflow.

How-To

The following instructions assume an LED and MRset have already been set up in the Designer project

To set up a 2.5D asset from an existing .2p5d file:

1. Copy the .2p5d file to objects/2p5DFile in the project folder
2. Add a 2.5D layer to the timeline
3. Click on the asset field in the 2.5D layer. The copied 2p5d file should appear in the list of assets
4. Click on the asset to select it, it should then load and be visible in the stage
5. Select the desired 3D mapping in the 2.5D layer, e.g. MR set backplate
6. To reload the asset from the file and overwrite any local changes, click ‘Reload from file’ under Import/Export in the 2.5D asset editor

To create a new 2.5D asset from scratch:

1. Add a 2.5D layer to the timeline
2. Click on the asset field in the 2.5D layer, and create a new 2.5D asset
3. Add a new 2.5D plate to the ‘plates’ field in the 2.5D asset
4. Under ‘Layer Stack’ in the plate editor, click ‘Add Video’ to add a video or image to the plate
5. Continue adding plates and modifying their properties until the desired scene composition is achieved
6. Select the desired 3D mapping in the 2.5D layer, e.g. MR set backplate
7. To export the asset for use in other projects, click ‘Export to file’ under Import/Export in the 2.5D asset editor. The exported .2p5d file will appear under objects/2p5DFile in the project folder.

Modifying 2.5D asset properties:

• The 2.5D asset is an Object which can have its offset and rotation set by changing the values in the editor or moving the white box in the visualiser. Doing so changes moves all the plates to change the origin point of the 2.5D scene. It is recommended that the origin is set roughly in the middle of the range of movement of the camera, to achieve the most realistic-looking parallax.
• The ‘Field of view’ and ‘Maximum depth’ fields can be adjusted to scale the total area encompassed by the 2.5D scene. This can be used to ensure that the edges of the plates are not seen when moving the camera within its expected range.
• Plates can be added to or removed from the asset using the +/- buttons in the ‘Plates’ field. Plates are ordered by depth, and reordering the plates in the list will update the plates' depth to reflect their new positions.
• The Import/Export settings can be used to load or save .2p5d files. When loading files that contain depth maps, the ‘Depth map minimum override’ setting can be used to change the minimum distance from the origin, represented by full white in the depth map.

Modifying 2.5D plate properties:

• The plate depth can be changed by modifying the z offset value, or by dragging the plate in the visualiser. If the option ‘Scale with depth’ is ticked, the scale and x/y offsets will automatically be adjusted with depth so that the plate looks the same when viewed from the asset origin. If ‘Scale with depth’ is not ticked, the scale and x/y offsets will not change, so the plate will appear smaller as it moves further away.
• By default new plates will be scaled to match the total field of view of the asset. However, the scale values can be adjusted in the 2.5D plate editor to change the scale. Similarly, the x and y offsets can be adjusted to move the plate position.
• The plate’s mesh can be changed to add depth to a layer and make the parallax effect more realistic. Some .2p5d files will contain depth maps, which will be converted to meshes when importing. To remove the depth from the plate, the standard rectangle mesh can be selected instead.
• The plate Layer Stack is used to set up the layers appearing on the plate. To quickly add an image or video to the plate, use the ‘Add Video’ button. Otherwise, layers can be created as normal and stacked to create effects such as blur or colour adjust. Note that these layers can’t be keyframed, see ‘Advanced Workflows’ for methods to keyframe layers on plates.

Advanced workflows:

The 2.5D layer and assets are designed to provide a user-friendly way to quickly create 2.5D scenes which are portable between projects. The standard workflow should allow for the majority of use cases, however, more advanced workflows can also be achieved by combining 2.5D assets with other tools in Designer.

• Generally, images, videos, and effects should be added to plates using the plate Layer Stack. However, this does not allow for keyframing within these layers. To keyframe content on plates, layers should be added to the timeline as normal. Content can be mapped to 2.5D plates from the timeline similarly to any other display.
• 2.5D assets and plates are both Objects, so it is possible to animate them from the timeline, or parent assets to other objects which are controlled using tracking data
• The ‘Stage render layer’ which was used for 2.5D workflows prior to r26.3 still functions as it did previously, so it is still possible to use the old workflow if desired.

Cuebric Integration

Cuebric is a web-based tool for creating 2.5D scenes with the help of AI. For more information visit https://cuebric.com/.

With r26.3, 2.5D scenes can be exported from Cuebric and imported into Disguise. At the time of writing, the Cuebric scene is exported from Cuebric by clicking on “Plug & Play 3D” in the Segmentation view under the Depth option. Once exported, follow the instructions in the section above on “To set up a 2.5D asset from an existing .2p5d file”.

When the Cuebric export includes AI-generated mapping depth information, Designer will auto-generate a 3D mesh from the depth data to add shape to the plates.

To remove the depth mapping from the plate, the standard rectangle mesh can be selected instead in the plate properties.

For a video explanation of the Cuebric to Disguise end-to-end workflow, click here.

• DSOF-17618 - HDR processing of Notch content
• DSOF-25812 - Branding updates

• DSOF-25844 - ResourceTransport: Fixed an Undefined Behaviour copying "UID not found Reason" list

• DSOF-24356 - Fixed an issue where inserting time that would push layers beyond the end of a track did not extend the track
• DSOF-25007 - Fixed 'Invalid t: > track length' error when dragging to the end of timeline that had a video that was a frame long at the end
• DSOF-25595 - Fixed an issue that occurred when global crossfade pairing with audio layers caused stuttering and hangs when jumping around timeline
• DSOF-25637 - Fixed an issue where "Director is under heavy load" notification did not always clear
• DSOF-25663 - Fixed an issue where the compose layer would sometimes display black when being shifted horizontally
• DSOF-25691 - Fixed an issue where matrix commands sent to a Blackmagic Smarthub 12g sometimes didn’t set the configuration correctly

• DSOF-23262 - Fixed an issue where the Bank Editor widget resized when adding a new bank, hiding all of the slots in the top half of the widget
• DSOF-24284 Fixed an issue where the RenderStream Assets List text was drawn partly outside of widget
• DSOF-25151 Fixed an issue where using some blend modes while SLC was active stretched and compressed the content
• DSOF-25644 Fixed audio not looping when Locked and Paused At end point
• DSOF-25685 - Fixed API issue where a malformed d3 version would cause an internal error
• DSOF-25701 - Fixed an issue where a brighter line of content showed in some SLC configurations
• DSOF-25711 Fixed an issue where Mesh Policy rendered black frames when the Unreal Project in film/video & live events mode

• DSOF-24937 - Fixed an issue where SaveOnDelete Resource Transport commands shouldn't blocked Resource Transport if a resend failed
• DSOF-25413 - Default Variable Timecode Implementation

• DSOF-25050 - Fixed an issue where right clicking a Screen of DMX lights on an editor while in a 2 machine or more session stopped DMX outputting
• DSOF-25186 - Fixed an issue where remote installation occasionally failed to start d3service with 'Entry Point Not Found' errors on RX servers
• DSOF-25420 Fixed an issue where the Position Receiver Axis could not use "Set" button for input ranges

• DSOF-25507 - Fixed an issue seen in AMD machines, where SLC affected output when using Stage Render layer

• DSOF-22666 - Fixed an issue where d3 would hang due to a network security sweep
• DSOF-24346 - Added logging to Live Update option switch
• DSOF-24360 - Fixed an issue where RenderStream Uncompressed only received texture parameters on the first adapter
• DSOF-24786 - Fixed an issue where installing HDMI VFC REV E cards in a system after having QSDIVFC cards installed caused d3 to stall when loading
• DSOF-25156 - Added DCS sensor width manual column
• DSOF-25283 - Fixed an issue where project templates caused an error during install
• DSOF-25440 - MatroxApi now warns the user when there is driver and SDK version are mismatched
• DSOF-25468 - Fixed an issue where Arri LDS device was not parsing raw encoder values for zoom or focus distance
• DSOF-25527 -  lenscalibrator.exe is now code-signed

• DSOF-25401 - Fixed an issue where it was not possible to select objects after opening 'Points' separator in Rigid Body Tracking Source editor
• DSOF-25423 OmniCal: Fixed an issue where editing the camera plan in upgraded pre-r23 projects froze d3
• DSOF-25450 OmniCal: Fixed Rig Check workflow

• DSOF-24126 - Fixed an issue where MidiBeatClock jumped backwards in the timeline when set to Loop Section
• DSOF-25089 - Arri Lens Data System version 102 is supported in addition to version 103.
• DSOF-25244 - Fixed an issue where the Sockpuppet video layer media did not turn black when 'None' is selected
• DSOF-25335 - Fixed existing TransportJumpCommands being broken broken when upgrade to r26.0
• DSOF-25401 - Fixed an issue where it was not possible to select objects after opening 'Points' separator in Rigid Body Tracking Source editor

• DSOF-24932 - Fixed an issue where Deltacast vx4+ video input group 2 is duplicated

• DSOF-17119 - Fixed an issue where the PSN receiver assigning to rotation.x and rotation.z would not doing full 360
• DSOF-24221 - Fixed an issue where it was not possible to open the port editor of QSDI with 'NoneType' error
• DSOF-25068 - Fixed an issue with installing fonts when the user had a space in their user folder name
• DSOF-25120 - Fixed an issue where RenderStream download_buffers did not release its download queue on destruction
• DSOF-25121 - Fixed an issue where starting and stopping a RenderStream workload reduces performance of WorkloadManager on the director

• DSOF-25123 - We have implemented a preview feature that allows d3 to chase timecode at non-standard framerates. This can be used for example to adjust the playback speed of video in line with a DJs adjustments to the BPM of a track.To utilise this preview feature you can enable the option switch "forcePIDTimecodeChase". Chasing LTC or any kind of timecode will smoothly follow adjustments to timecode playback while this is set.If you perform large timecode jumps you may find that the playhead will fast-forward to get to the new timecode rather than immediately jump to that point.If you have feedback about this new preview feature please let us know via our support@disguise.one email so that we can take that into account for the finished implementation.

• DSOF-23668 - PreComps - Fixed an issue where clicking Effect or Generative layer caused feed blur
• DSOF-24802 - Fixed an issue where a video layer with speed ‘0’ was interpreted ambiguously.
• DSOF-24835 - Fixed an issue where deleting a VirtualLineup layer mapped to a camera's perspective after timeline focus was taken away from the layer and then returned causes Access Violations
• DSOF-24921 - Fixed an issue where an Object Tracking error blocked Spatial Calibration when not receiving Tracking data
• DSOF-25037 - Fixed an issue where the TrackingMarker output showed incorrectly when using feed map with SLC
• DSOF-25146 - Reduced the amount of wireframes shown in QuickAlign alignment widget

• DSOF-16666 Simple FBX mesh support

The FBX file format can now be successfully imported into Designer as a single mesh, meaning that users can now export models without the need for conversion from their respective 3D tool of choice. These can be used in the schematic, lux and heatmap renderers. Any FBX mesh will be imported with global positions, and non-triangulated meshes are triangulated on import. FBX files imported with up to 3x UV maps are supported. 

It is important to note the following mitigations with this feature:

• Object hierarchies found within the FBX file in Designer are currently not supported

FBX file format support can be used with the option switch enabled. To access, right click on a project folder in d3manager, select ‘Advanced project settings’ and then select ‘enableFbxMeshImport’. Please contact product-team@disguise.one for feedback on this feature.

• DSOF-22271 TransportJumpCommand locations should use time adjusted by timecode tag when using timecode location

When making a TransportJumpCommand in the TransportControl module, the location value has the option of being set with ‘CUE <cue>’ or timecode. 

In previous releases, when there are timecome tags on the track that a user wants to specify a location on, the timecode displayed in the GUI is based on the timecode tags, but the location that the TransportJumpCommand uses does not take the timecode tags into account.

In r26, the location for TransportJumpCommand now uses the time adjusted by timecode tags when using the timecode location. 

• DSOF-23321 Show RenderStream proxy stream status in the GUI

We have added RenderStream proxy information in the RenderStream Editor widget.

• DSOF-23699 Make list/grid view selection for media/texture browsers persistent

In previous releases, the behaviour of the media and texture browser in Designer was not persistent when a user would switch between grid view and list view. In r26 we have made the selection of grid or list view in the media/texture browser to remain persistent across all machines running in a session.

• DSOF-23810 Add FBX ASCII format for Shot Recorder export

Users can now export data from the Shot Recorder to the FBX ASCII format.

• DSOF-24041 XR: improve usability of Tracker Delay UI

We have made a number of changes to the Tracker Delay UI. These include changing the overlay colour from magenta to red to signify when no tracking data was captured, or the delay is set to too low or too high. We have also introduced help text in a number of areas of the UI to provide instruction on the Tracker Delay process.

• DSOF-24066 Alert the user when video lookup times becomes unstable or if errors are high

We have added a visible notification within the UI to notify users that the video receive delay is set incorrectly during the spatial calibration process when working with MR Sets. The calibration will be highlighted in red, and hovering over the row with a mouse will explain that there is a video receive delay error and to perform the delay calibration again. 

• DSOF-24089 DSV capture: minor performance optimisations
• DSOF-24090 DSV capture: add dropped frames detection
• DSOF-24099 Shorten RenderStream workload/stream friendly names for the UI

In previous releases, RenderStream workloads and streams were identified within the UI through a 64 bit unique ID to enable users to reference each stream. In r26 we have shortened the RenderStream workload names to make it more straightforward for a user to reference each RenderStream workload.

• DSOF-24153 Expressions: if expressions are broken, the layer they are used in should change colour as well as the parameter

In previous releases, if an incorrect Expression had been written then this would be flagged to the user by turning the parameter orange in colour. 

In r26 we have included the layer that is using the Expression to also change to red in colour so that the user is notified that the Expression is incorrect. If the layer is in a group, then the group will turn red when the layer it contains turns red.

We have also included an error message on the layer via a tooltip. If a user corrects the Expression then the layer will return to its default colour.

• DSOF-24160 Better texture buffer management for LogicalVideoInDevice
• DSOF-24166 Make list editors stickyable

In r26 we have enabled users to pin ListEditors to the Designer UI by clicking the pin in the top left hand side of each ListEditor as seen in the image below.

• DSOF-24271 Change default location for d3 Projects to D:Drive after reimaging a disguise media server

In r26 we have changed the default location for d3 Projects to be in the D:Drive after reimaging a disguise media server. In previous releases, a user would be pointed towards the Documents folder whereas all Designer projects should be located in the D:Drive.

• DSOF-24375 Include display master brightness in the feed UI

We have included the master brightness of LED screens and projectors within the feed UI. This can be seen as a percentage underneath the name of each screen, as shown in the screenshot below.

• DSOF-11028 - Fixed an issue where an embedded audio in a video layer would drift out of sync from the playhead either over time or due to frame drops
• DSOF-17926 - Fixed an issue where setting a value with '=' in an expression locked the value to the conditional value
• DSOF-21117 - EventTransportMidiNote Personality Train is no longer offset in GUI
• DSOF-21827 - MultiTransport Manager: Fixed an issue where  Editors would respond to timecode cues when the Director’s transport had been disengaged
• DSOF-22783 - Clarified active latency mismatch error
• DSOF-22876 - RenderStream: Fixed a stall / crash to desktop when modifying ClusterAssigner options while sending remote texture
• DSOF-22900 - Fixed an issue where pre-capture in spatial calibration did not work when multiple cameras are using same video input
• DSOF-23276 -  It is no longer  possible to rename a group to an empty name, which then prevented opening group options widget
• DSOF-23281 - Fixed an Access Violation in the input manager when using keyframe editor with multi-layer selection
• DSOF-23315 - API: Fixed /sequencing/changeindirections only matching classes not subclasses
• DSOF-23367 - Fixed the keywidget timeline repositioning to the timeline playhead rather than the time indicator when moving between control parameters, thus losing view of keyframes being edited
• DSOF-23645 - Fixed an issue where Actors and Understudies were not showing frame rate at Startup until open the session widget
• DSOF-23661 - Fixed an issue where the missing media window could go off screen
• DSOF-23710 - Fixed an issue where FBX data from disguise shot recorder doesn't import correctly in 3rd party software (UE, Maya)
• DSOF-23749 - Fixed being unable to filter by resolution in list editor
• DSOF-23841- Monitoring manager improvements
• DSOF-23848 - OmniCal: Fixed an issue where NUL was logged instead of integer value 0 for "projectorSimulationOptions"
• DSOF-23898 - Fixed an issue where user made video-in resource used in layers would generate content table fails
• DSOF-23934 - Fixed an issue where d3 switching between full screen and windowed would sometimes caused a crash to desktop
• DSOF-23955 - Inconsistent version tags no longer cause a crash to desktop
• DSOF-24036 - Fixed DSE not work with Face Culling
• DSOF-24088 - DSV capture: Fixed capture failure leading to shortening of capture buffer
• DSOF-24093 -Stop on TC Lost Behaviour is now consistent between director and editor
• DSOF-24105 - Fixed an issue where timecode tags where the frame number is the same as the number of frames per second caused the playhead to show the wrong time
• DSOF-24116 - Fixed an issue where versioning down a file used in smart group versions down every file used in that smart group, regardless of version number
• DSOF-24127 - OmniCal: UI Clarified when Multi-Pose is disabled because of missing cameras
• DSOF-24133 - Fixed an Access Violation when attempting to Empty Trash for LED Screen and Projection Surface
• DSOF-24168 - Fixed an issue where users could not create string literals in expressions
• DSOF-24189 - Fixed an issues ehre Go To Timecode ( Ctrl + / ) went to timecode plus a frame when used after a timecode tag
• DSOF-24204 - Fixed video is not being in sync when an actor rejoined the session
• DSOF-24209 - Fixed frame drops when moving between multiple video clips with audio
• DSOF-24214 - Fixed remote installs of d3 stalling
• DSOF-24269 - Fixed an Access violation when trying to write more than one mpeg-4 feed movie if using an unsupported resolution
• DSOF-24278 - Fixed an Access Violation in VideoInSystem::render when GPU driver had crashed
• DSOF-24343 - Fixed an issue where sockpuppet changes were not actually being applied to an audio layer
• DSOF-24384 - Trial: Fixed an issue where a write compacted package on exit will leave project file empty
• DSOF-24385 - Fixed an issue where an unreadable shader source directory could stop shader cache creation
• DSOF-24429 - Fixed an issue where audio underran at the start of videoclip with audio
• DSOF-24439 - Fixed Text Module failing to update text on project restart
• DSOF-24445 - Groups are now red when they are created containing layers which are already red
• DSOF-24454 - Installer: Fixed d3 Installer hanging when d3 is running the background
• DSOF-24462 - Fixed an issue where every string rendered to screen was copied 1x more than required
• DSOF-24466 - Fixed RSCompressedVideoIn not calling shutdown(), bypasses videoInShutDown actions
• DSOF-24507 - Fixed an issue where ResourceTransport was blocked on Actor / Understudy machines after FeedRect edits
• DSOF-24520 - ResourceManager: search() now includes matching files on disk
• DSOF-24521 - ResourceManager: Fixed remove() calling removeResourceAction twice
• DSOF-24529 - Fixed an issue where the List View and Grid View highlight icons were reversed
• DSOF-24553 - Fixed widget suggestion text being unnecessarily copied
• DSOF-24573 - Fixed an issue where ObjectDeformationSettings::remove used single parameter erase call when used with std::remove_if
• DSOF-24588 - Fixed a virtualCam error when starting a RenderStream workload
• DSOF-24605 - Fixed an error notification "m_cameras.front() == cam" being produced during spatial calibration
• DSOF-24805 - XR: Fixed being Unable to create a Legacy Observation
• DSOF-24806 - Fixed an issue where removing feed rectangle on output threw error: 'Machine' object had no attribute 'feeds'
• DSOF-24807 - Fixed errors thrown when trying to duplicate a feed rectangle
• DSOF-24815 - RenderStream:  Fixed Uncompressed workloads failing to start
• DSOF-24819 - Fixed an issue where users were unable to duplicate multiple feed rectangles in the feed view
• DSOF-24841 - Fixed remote install failing on RX
• DSOF-24847 - Improved LED Screen List Editor duplicate names handling
• DSOF-24956 - Fixed an issue where a combination of Matrox VX2 director and Deltacast VX4 or VXUnderstudy caused “Unable to create video capture stream” error notifications.
• DSOF-25099 - Fixed an issue d3preview caused an Access Violation on opening file

• DSOF-23415 - Overlay message added to alert user "live update ready" if live update recovers
• DSOF-25061 - Fixed an issue where OSC expressions may fail to update with more than one OSC input device until the device list was re-ordered
• DSOF-25122 - Fixed an issue where d3manager showed "no license" popup on disguise servers in some situations
• DSOF-25130 - Fixed an issue seen where an indefinite capture freeze could occur when moving between capture card inputs

• DSOF-24101 - Unified "dropped frames" counting across all videoin classes
• DSOF-24349 - Implemented IMvVideoConnectorNotification for inputs to receive status updates in console

• DSOF-24301 - Fixed an issue where consecutive timeouts on capture cards would abort the thread and not restart it
• DSOF-24443 - Fixed an issue that occurred when a capture card input was unplugged and replugged, all inputs would freeze for a few seconds before recovering
• DSOF-24549 - Fixed Matrox thread 1A Aborting thread due to repeated time out
• DSOF-24552 Fixed an issue where output would get stuck if the video input signal was lost and recovered
• DSOF-24693 - Fixed an issue where checkInputSignalChanged was causing main thread to hang
• DSOF-25115 - Fixed an issue where the capture thread could occasionally crash with an Access Violation while configuring a quad input
• DSOF-23828 - Fixed an issue where setting EDIDS to unmanaged/force off did not work as intended
• DSOF-25064 - Fixed an issue where Mellanox licence failure was not reported as an error on gx3 servers
• DSOF-25070 - Fixed an issue where Canon ACES input transforms were not selectable in the UI

• As part of r25.2.2
• DSOF-23391 - Fixed an Access Violation when opening 'Manage Old Media'
• DSOF-24694 - Fixed an issue where the frontplate was not aligned correctly when in minimal latency mode
• DSOF-24889 - Fixed an issue where OSC Expressions did not working properly after loading snapshot
• DSOF-24985 - Fixed an issue where use of Renderstream texture parameters would eventually cause a crash
• As part of r25.2.3
• DSOF-24726 - Fixed a “No video in texture for videoin_1.mov -” warning error on Video Input device
• DSOF-25031 - Fixed issue related to manual AR calibration
• DSOF-25040 - RenderStream: Fixed multiple Access Violations when starting a workload with proxy streams
• DSOF-25044 - Fixed an issue where Rotation Delay for tracking sources was not updated
• DSOF-24761 - Fixed an issue where Indirection Media didn't indicate that it is a value set by indirection when the value is None

• DSOF-23505 - Fixed an Access Violation that occurred if the Capture Setup widget was open while a capture is in progress
• DSOF-24762 - Fixed an issue where the GUI framerate fraction caused some strange widget behaviours
• DSOF-24888 - Fixed an issue where the Focus distance and Aperture would stick to 0 after an MR set observation
• DSOF-24922 - Fixed an issue where the sensor width was erroneously overridden by spatial calibration
• DSOF-24950 - Fixed an Access Violation when importing objects
• DSOF-24965 -  Fixed an issue where long entries in the debug window would cause a ‘<NULL>’ notification to appear.

• DSOF-24386 - Fixed an issue where an error stating permission was denied [Error 13] when opening project from d3 Manager
• DSOF-24424 - Fixed a delay when launching a project from d3 Manager and Designer opening
• DSOF-24594 - Improved the speed of NDI source discovery
• DSOF-24758 - Fixed an issue where missing dependencies caused Notch Blocks to not load.: “Unable to load error: Error 0x7e: The specified module could not be found”
• DSOF-24808 - Fixed an issue where 12G SDI input limit was reached even using 3G
• DSOF-24814 - Improved audio prefetching limit logging
• DSOF-24816 - RenderStream: Fixed an issue where framerate plummets and/or workload crashes when un/assigning texture parameters
• DSOF-24928 - Fixed a memory leak in RenderStream Uncompressed with Texture Parameters

• DSOF-24204 - Fixed an issue where video was not in sync when an Actor rejoined the session
• DSOF-24799 - Fixed an Access Violation when trying to add a MIDI device

• DSOF-23458 - Fixed  IO stalling due to too many concurrent read operations
• DSOF-23645 - Fixed an issue where Actors and Understudies were not showing frame rate at startup until opening the session widget
• DSOF-24130 - Fixed an issue where the tooltip didn't render text but could grow too tall when you have groups within group
• DSOF-24295 - Fixed an issue where timecode was sometimes ignored when track jumping
• DSOF-24576 - Fixed an Access Violation when stopping uncompressed RenderStream workload on an rx
• DSOF-24595 - Fixed an issue where it was not possible to create a group in an existing group
• DSOF-24734 - Fixed an issue where it was not possible calibrate tracking delay when using object rather than camera tracking source
• DSOF-24748 - Fixed lens calibration not being applied when using Object tracking source
• DSOF-24751 - Fixed an issue where camera focus distance and aperture were usable as layers
• DSOF-24752 - Fixed an issue where d3net session between servers containing different capture card types threw "Unable to create video capture stream" errors and spammed the console continuously

• DSOF-24681 - Improved performance of getContentViewpointsForFragment

• DSOF-24399 - Fixed an Access Violation encountered when using multi transport
• DSOF-24439 - Fixed an issue where the Text Module failed to update text on project restart
• DSOF-24672 - Fixed an issue that occurred when leaving a video layer with embedded audio in "at-endpoint" loop mode  resulted in a hang
• DSOF-24678 - Tracking marker no longer has aliasing at the edge of meshes

• DSOF-24610 - Fixed an issue where RenderStream channels with higher load factor composited behind other channels
• DSOF-24600 - Improved virtual camera stability

• DSOF-22915 - Fixed a crash on exit when DxDevice was lost
• DSOF-24500 - d3service no longer crashes on close
• DSOF-24507 - Fixed an issue where ResourceTransport blocked on Actor / Understudy machines after FeedRect edits
• DSOF-24523 - Fixed ACCESS_VIOLATION 0x280 while renaming the stage from an Editor
• DSOF-24558 - Fixed an issue where  Heap Corruptions caused a crash to desktop
• DSOF-24560 - Fixed an Access Violation when using the 'Removing Virtual Head' option in the FeedHead widget

• DSOF-24186 - TrackingMarker layer now shows red on output when the LED is blocked by another LED in camera view

• DSOF-23300  - Fixed an issue when a signal was lost, video input format did not go to "None" 
• DSOF-24422 - Improved Camera movement in Unreal Engine 5.2 with DirectX12
• DSOF-24531 - Fixed an issue with 12g input on capture cards where it would report “input limit reached” and prevent capture

• DSOF-23420 - Fixed an issue where media which was present on the machine was reported as missing in d3
• DSOF-23859 Fixed - Access Violations when failing to create WebBrowser in Text Layer
• DSOF-23964 - Fixed an issue where DeltaCast Video Input (Capture) Group 1 & Group 2 were flipped
• DSOF-24156 - Fixed an issue where artefacts appear over RenderStream
• DSOF-24393 - Keyframes: Fixed an issue where setTimeQuantised had missing checks which could result in keyframes with the same time
• DSOF-24437 - Fixed an Access violation in folderwatcher causing d3service to be broken silently
• DSOF-24473 - Fixed Access Violations in RenderStreamModule editor running RenderStream Assets with widgets open and crossfades on timeline
• DSOF-24483 - Fixed an Access Violation when programming renderstream layers

• DSOF-23423 - Fixed an issue where placeholder images appear on output for the first frame after a patched videoin becomes active
• DSOF-23692 - - Fixed an issue with IPVFC with no SFP, sometimes launched d3 with a blank GUI
• DSOF-23783 - Fixed an issue where VariableVideoPlayer: "Invalid frame calculated"/ "start != end" notification showed on sharp speed changes
• DSOF-23983 - Fixed an issue where layers with a video keyframe that fell before their start were not prefetched properly
• DSOF-24277 - Fixed an issue where UDP Camera Switching caused frame drops and dirty switches in a session
• DSOF-24376 - Fixed an issue where the background flashed when switching Video layer media via DMX
• DSOF-24288 - Fixed a performance hit caused by unnecessary domain copies

DSOF-21756 Support for Invisible: real-time markerless mocap by move.ai

For details on how to use real-time markerless motion capture with Invisible by move.ai,  please visit: https://help.disguise.one/en/Content/Workflows/Motion-Capture/Invisible/Invisible-Overview.htm

DSOF-23201 Improve lens tracking source workflows

In r25 we have made a number of improvements to the camera tracking workflow within Designer. 

To add a tracking source to a camera:

1. Under Devices, add a PositionReceiver
2. In the PositionReceiver under Drivers, add the relevant tracking driver and set it up to receive tracking data
3. Engage the position receiver
4. Create a Camera in the Stage
5. Under the Camera Settings, select tracking source. This should have been automatically generated by the driver once tracking data started to be received
6. Data from the tracking source should start overwriting the values in the camera

General UI Improvements

We have now highlighted values in the camera that have been overridden when using external tracking sources or spatial calibrations. We have also added tooltips that indicate to the user that each value has been overridden.

We have also added an ‘Open Driver’ button to go straight to the driver from the tracking source, and vice versa we have added an ‘Open Tracking Sources’ button in the driver to go to the tracking source to improve navigation.

Added receive time smoothing to tracking sources

Within the tracking source, we have added a number of new options. The first is the ‘Smooth receive time’ box, which when turned on smooths out the tracking data received by disguise, but may add a small amount of latency. This was previously an always-on option but can now be optionally turned on or off by the user.  

Added the ability to disable particular axes in tracking sources

The Values box can be expanded to provide all values being provided within the tracking source, and these will be highlighted in green. There are also check boxes next to each value to allow users to untick values that they don’t want passed through to the tracking source. These values will change within the camera when unticked, and can be edited by the user manually within the camera. 

To toggle values applied from the tracking source:

1. From the Camera, open the Tracking Source editor
2. Expand the Values separator
3. Values highlighted in green are being received from the tracking source. Values with a dark grey background are not being received. Values with a light grey background are received but toggled off
4. Untick the checkbox to stop the value being applied in the camera
5. Tick the checkbox to apply values again

We have also added a ‘Delays’ option within the tracking source to apply lens delay offset if required.

In previous releases, if users had a tracking source that failed to send a particular value then we would have used a dummy value on the camera. In r25 we now leave the value that has been provided by the tracking source and will not replace them with a dummy value.  

Lens focus parameters for tracking sources

We have also added parameters for controlling focus and depth of field parameters. This has currently been implemented for RenderStream Unreal Engine assets only. Within the Unreal project, the user has to select the ‘CineCamera’ for the channel. 

To use lens focus parameters:

1. Set up a RenderStream layer with an Unreal asset, with a channel created from a CineCamera
2. Map the channel to a Camera or MR set backplate or frontplate
3. Start the RenderStream workload
4. Adjust the ‘Focus mode’ under Camera / Physical / Lens / Focus. There are three options:

1. Disabled - no depth of field. Focus mode is disabled by default
2. Manual - use this mode to turn on the feature. Focus distance and aperture can be adjusted manually to adjust the depth of field. These can also be received from tracking sources which provide them
3. Object Tracking - select an object in Designer to calculate the focus distance from. The aperture will be changed manually or received from tracking data, and the focus distance will be controlled by tracking the specific object within your scene

5. Adjusting the lens focus parameters in the camera should cause the depth of field effect to change in Unreal Engine

Tracking Smoothing graph

We have added tracking smoothing graphs to help debug tracking issues. The lines in the graph can be interpreted as follows:

• Lookup offset (ms) - this is the time in milliseconds between the smooth tracking data that we are looking up, and the latest data received. This should almost never go below zero, as that would mean that we have received the tracking data too late to be able to smooth it. If it is consistently much greater than zero, this means that we are adding unnecessary additional latency whilst waiting to receive smooth data
• Index delta - the change in index of the tracking data that we look up in the buffer across each frame within Designer. If the tracking frame rate is twice the Designer frame rate, this would be around 2. The smoothness of this line shows the success of the receive time smoothing. We are aiming for a consistent index offset between each packet of tracking data that we look up
• Received delta - the change in the receive time of the tracking data of each frame. This shows us how smooth the tracking data would be without receive time smoothing. It can be compared against the ‘Index delta’ line to check that receive time smoothing is working
• Instantaneous smooth data delay (ms) - indicates how far we would have to look in the buffer to ensure that we have received tracking based on the latest received packets. This is aggregated over time to give a stable lookup time
• Local smooth data delay - the maximum smooth data delay for this specific machine
• Global smooth data delay - the maximum smooth data delay over all machines. This is particularly relevant when we are redistributing tracking data across machines. It should provide a consistent period to look back in the buffer to ensure that we have smooth tracking data

DSOF-7571 BlackTrax: Implement BlackTrax Centroid calculations

We have implemented centroid tracking sources into the RTTrPMDriver within the PositionDriver devices. This means that we can now receive centroid data within disguise for Blacktrax tracking systems.

DSOF-22936 Add ARRI LDS as a device driver for receive lens data native from Arri Cameras

We have added Arri LDS within the PositionReceiver devices so that users can receive metadata from Arri cameras into disguise - that being focal length, aspect ratio, vertical and horizontal field of view, sensor size, aperture, and focus distance.

DSOF-22279 Ensure Quad-SDI VFC output signal is not interrupted after configuration

In previous releases, the output from a Quad-SDI VFC card would be interrupted if a project would be restarted within Designer

In r25, if a user was to restart a project within Designer then the output from a Quad-SDI VFC card would be the same resolution as it was before the project was restarted. This prevents the signal being interrupted upon restarting a project within Designer.

The only time that an output will be interrupted from a Quad-SDI VFC will be if a disguise media server was restarted or powered off, or when apply feed settings is executed.

DSOF-22410 Support focus and iris data in FBX export from shot recorder

In r25 we have added both aperture and focus distance to the default parameter collection for new cameras within the Shot Recorder feature. These properties can also be set within the Shot Recorder FBX export. 

DSOF-22460 Keep last-known camera position if camera tracking drops

In previous releases, when camera tracking is lost, the camera will revert back to 0,0,0. In r25, the camera tracking will remain at the last tracked camera position.

DSOF-22672 Make common base project for d3api and d3service

DSOF-22837 Write functionality to clear up exported glb, movie and metadata files

We have added an improvement to the Previz Link within Designer in r25 to clear up disk space by deleting old export files related to Previz that are no longer being used by any other application. Any export file that is still being used will not be deleted until the next time a clean-up takes place, where again we will only delete export files that are no longer being used by any application. 

DSOF-22937 Move nginx logs to d3 app data directory instead of in program files

In r25, nginx logs have been moved from the program files path to C:\Users\d3\AppData\Local\d3\nginx

DSOF-22995 GUI: The layer editor should move to front open keyframe editors when it gains focus

In previous releases, when working on a large timeline that overlaps on-screen with a layer editor, if a user was to click on the layer editor to focus on it, the layer editor widget would be foreground but the keyframe editor would be behind the timeline. In r25, when a user brings a layer editor into focus, the keyframe editor will now foreground with it. 

DSOF-23002 Sequencing: On project upgrade, disable sequencing for all fields which are not sequenced

In previous releases, if a project was upgraded from a version of Designer that did not support the Keyframe Toggle (before r20.0), all fields were set to have Keyframes enabled. This required a significant amount of tidying to be able to benefit from the Keyframe Toggle. In r25, we have enabled any fields that only have 1 frame and therefore no sequencing should have the Keyframe Toggle automatically set to off on project upgrade.

DSOF-23110 Videoins with placeholder images should have the resolution of the placeholder.

In previous releases, when adding a Videoin for a placeholder image, the video would be set to the last resolution of the video input received by disguise. In r25, if a Videoin is added with a placeholder image, the video will be set to the resolution of the placeholder image that is used. The Videoin will override the placeholder image resolution when it is available.

DSOF-23245 Optimize DmxScreenRead layer

In previous releases, it was reported that the DmxScreenRead layer was impacting the performance of Designer. We have now optimised the layer.

DSOF-23336 IP VFC SDP file paths should be discoverable

We have added a ‘Copy SDP path to clipboard’ button within the IP-VFC settings menu. This includes the SDP path that can be copied and added onto a ST 2110 receiver device, such as the Megapixel Helios.

DSOF-23646 GET activetransport API should return the selected track for each transport

We have enabled the ActiveTransport API to return the currently selected track for each transport. This can be found within the GET activetransport API, where we have included a currentTrack property that indicates the current selected track of a given transport. 

DSOF-23756 Add double dot RS plugin version to schema JSON

We have added a new RenderStream release naming convention to include double dots for plugin-specific hotfixes. This can now be seen within the Designer GUI.

DSOF-23808 Implement support for Arri Alexa LogCv4 to ACES workflow

DSOF-23927 Allow user to copy/paste notifications

Users can now copy and paste notifications from Designer without having to open the console.

DSOF-19735 - Fixed an issue where snapshots failed to create after the snapshot widget was closed

DSOF-19736 - Fixed: If a snapshot has failed to create, an access violation was displayed if a widget was opened while taking a snapshot

DSOF-20435 - Fixed an issue where the  CPUMonitor did not respect poll unit/interval settings

DSOF-20791 - Fixed an issue where "Edid port invalid errors" on applied feed settings

DSOF-21510 - Improved the efficiency of Text Layers

DSOF-21687 - Fixed an issue where Media Distribution did not report correct size for image sequences

DSOF-21694 - Fixed an issue that occurred when undoing a creation of a group with the widget open displayed a "not in list" error

DSOF-21839 - Fixed an issue where projects started with a Masking object appearing until the stage is brought into focus

DSOF-21988 RenderStream: Fixed an issue where Designer would hang when stopping a workload

DSOF-22109 - Fixed an issue where list indirections were not triggering multitransport

DSOF-22756 - Fixed an issue that occurred after deleting a Skeleton object from Stage and its Stick Man was still visible

DSOF-22780 - Fixed an issue where it was not possible to open the rollback window of 2 objects at the same time

DSOF-22781 - Fixed an issue where duplicating group with video transition layer

DSOF-22798 - Video Input Patch Editor: Fixed an issue where the format field was not refreshed upon project startup

DSOF-22812 - Fixed an unnecessary error continuously being thrown when an empty texture parameter was assigned

DSOF-22846 - Fixed an issue that occurred when disengaging the Position Receiver, the status didn't work as expected

DSOF-22916 - Fixed framerate drops on solo with section on the timeline

DSOF-23030 - Fixed an issue where a new section break was not dropped on the exact frame when zoomed out and using ; ` shortcut to move playhead

DSOF-23103 - Fixed an Access Violation when using ctrl+z to undo deleting a layer

DSOF-23107 - Fixed incorrect timestamps on a newly created project within d3manager

DSOF-23127 - Mosys Driver: Fixed an issue where it was possible to edit lens values in the GUI when using Mosys GeneratedCameraTrackingSource

DSOF-23153 - Fixed an issue where Video Inputs was not scrollable

DSOF-23157 - Fixed an issue where Udp::connect error didn't specify which port it failed to bind to

DSOF-23159 - Fixed an issue where ObjectView did not expand according to buckets / subdirectories

DSOF-23179 - Fixed an issue where the VideoIn format field was not serialising correct value with director/actor setup

DSOF-23180 - Fixed an issue where Layer Stack did not affect placeholders in LogicalVideoInDevice

DSOF-23215 - Fixed an issue where Movie Output > Output movie size had options for 2K and 4K export on the MPEG-4 drop-down list despite Designer reporting errors that "d3 designer can only export resolutions up to 2160 pixels" and then failed any export attempt

DSOF-23264 - Fixed an Access Violation when taking a Snapshot after closing Snapshot manager

DSOF-23287 - Fixed an issue where a calibrated camera with no tracking source silently overwrote lens intrinsics

DSOF-23303 - Fixed an issue where the console was spammed when Designer was minimised while running in application mode

DSOF-23319 - Fixed an issue where Designer delayed tracking longer than it needs to when doing receive time smoothing

DSOF-23328 - Fixed an issue where many (Save) Actions were not unsubscribed at d3 shutdown

DSOF-23331 - Added detailed logging on shutdown for still subscribed Actions

DSOF-23332 - Fixed an error at 'MissingMediaDomain: checkMissing'

DSOF-23333 - Fixed an issue that occured when changing SLC sizes would result in an error after configuring feed

DSOF-23342 - Fixed an issue where copying and pasting a layer at the end of the timeline did not extend the track

DSOF-23358 - Fixed an issue where keyframes outside of the highlighted grouping area were not deselected and not included in the keyframe grouping

DSOF-23361 - Fixed an issue when assigning empty VideoInTexture caused a parameter size error

DSOF-23368 - Fixed an issue when selecting a group of keyframes whilst there was already an active group selection in the keywidget added the new selection to the old

DSOF-23422 - Fixed [XR] Spatial Cal not working as expected

DSOF-23429 - Fixed an issue where a "'NoneType' object has no attribute '__base__'" notification was displayed when right clicking on proxy maker with disableProxyMaker option switch enabled

DSOF-23513 - Fixed iPod 6 showing as an option in OmniCal

DSOF-23550 - Fixed an issue where the Patch Assignments Widget could not be opened

DSOF-23558 - Fixed an issue where Telemetry would fail with error "queryLogs failed: Can't find manifest"

DSOF-23566 - Previz link: Fixed an issue where props didn't handle alpha material and textures properly

DSOF-23575 - Fixed an issue where Rotational X value flickered between two numbers in Tracking Source Data when Smooth Receive Time unchecked

DSOF-23581 - Fixed an issue where ‘Cannot create a link without a Resource’ error was displayed when adding the new depth of field parameters to the shot recorder

DSOF-23595 - Fixed an issue where the ‘enable Depth of Field (DOF)’ option check-box in Camera settings has changed to a number field input box

DSOF-23598 - Fixed mesh fragment artefacts in a mesh mapping

DSOF-23611 - Fixed an issue where upper and lower-case letters in names of the Camera Settings were mixed up

DSOF-23613 - Fixed an issue where it was not possible to do secondary observations with trackmen camera tracking system as zoom encoder is always 1.f

DSOF-23620 - Fixed an issue where the prop mesh could not be assigned 'None'

DSOF-23629 - Fixed an issue where Mesh Mapping would jump the camera for a few frames to a different position

DSOF-23666 - Attribute Error: Fixed 'NoneType' object having no attribute 'hidden' when adding a spherical camera

DSOF-23685 - Fixed the Focus field inside Camera widget not working as expected

DSOF-23716 - Fixed a VirtualCam notification error when starting RenderStream with MR set mapping

DSOF-23740 - Fixed an m_renderPoseHistory.empty() Error Notification upon re-opening a project with RenderStream layer

DSOF-23751 - Fixed an error spamming whenever opening the Tracking Source widget of a Skeleton

DSOF-23754 - Fixed an issue where a camera with a tracking source selected and no videoin, opening the camera widget showed an error

DSOF-23777 - Fixed Open Tracking Sources widget not working as expected with Skeletons

DSOF-23783 - Fixed an issue where VariableVideoPlayer: "Invalid frame calculated"/ "start != end" notification was shown on sharp speed changed - check

DSOF-23811 - Removed Skeleton Scale

DSOF-23893 - RTTrPM driver - Fixed an issue where centroid positions had Y / Z positions swapped

DSOF-23899 - Fixed an issue where the Inner Frustum was not visible when using Backplate and Mesh Mapping

DSOF-23963 - Fixed NGINX being set to Manual instead of Automatic in Services

DSOF-23978 API: - Fixed an issue where boolean properties in result of /service/system/detectsystems never returned to 'false'

DSOF-24042 - Fixed an issue where alembic mesh centroid did not match when mesh is far away from origin

DSOF-24049 - Fixed a typo on response to http://localhost/api/session/status/health

DSOF-24083 - Fixed multipleAccess Violations and crashes to desktop when trying to stream 3 channels over RenderStream

• DSOF-22798 - Video Input Patch Editor: Fixed an issue where the format field was not refreshed
  upon project startup
• DSOF-23179 - Video Input Patch Editor: Fixed an issue where the format field did not save the
  correct value with a director/actor setup

• DSOF-23379 - Fixed an issue where the proxy maker made proxies 1 frame short for videos 1 frame short of rounded duration to fps
• DSOF-23559 - Fixed an issue where video inputs dropped out with timeout error
• DSOF-23939 - Fixed an intermittent kMvSynchroStatusCancelledLate error which stopped capture
• DSOF-24155 - Fixed option switch for overriding nDisplay config file in Unreal Renderstream

• DSOF-24070 - Fixed an issue where it was not possible to scroll in larger nested folder structures
• DSOF-24191 - Fixed EX3 and Vx4n machine types being missing from HTTP APIs machine enums
• DSOF-24200 - Resolved an issue introduced that could prevent launching projects when spherical, perspective or parallel projections were in use.

• DSOF-23040 - Fixed an issue where the rsync port conflicted with VPN
• DSOF-23732 - Fixed an issue where the proxy generated by the proxy maker was not recognized
• DSOF-23885 - Improved Camera Switching performance
• DSOF-23899 - Fixed an issue where the Inner Frustum was not visible when using Backplate and Mesh Mapping
• DSOF-24083 - Fixed Access Violations and a crash to desktop when trying to stream 3 channels over RenderStream
• DSOF-24106 - Fixed an issue where OmniCal cameras could not be added to a project on EX 3

• DSOF-24056 - RenderStream Uncompressed: Fixed an error where  "packet/frame dropped recently" message did not clear after a stream recovered
• DSOF-24001 - Fixed an issue where quad link capture displayed a black screen

• DSOF-23566 - Previz link: Fixed an issue where props did not handle alpha materials and textures properly
• DSOF-23748 - Fixed an issue where a hang occurred the first time playing into a layer of content
• DSOF-23758 - Fixed a  d3service crash seen in r23.1.2
• DSOF23023 - Fixed an issue where pucks were not exported properly to glTF

• Added product support for EX 3

• DSOF-23375 - Fixed an issue where the Video Prefetcher was not creating video requests for the next section
• DSOF-23797 - Fixed a crash to desktop seen in r24.0
• DSOF-23829 - Fixed Edit VideoClip button
• DSOF-23878 - API: Fixed transport engage/disengage not applying session wide
• DSOF-23961 - Fixed an issue with heap corruption when hot-reloading shaders
• DSOF-23996 - Fixed an issue where d3 could not run on multiple machines with RPVII cards (vx4+ or vx4n)

• DSOF-23365 - The improved GPU memory management system shipped in r24.0 behind
  the option switch 'useGpuPool' is now enabled by default. It provides reliable stability
  for demanding video playback loads and other high-memory-usage scenarios

• DSOF-23038 AV in "Upload assets" test case in test_cloudserver

• DSOF-23694 - SDI-IPVFC: Fixed an issue where 4096x2160 59.94 10bit failed to enable stream
• DSOF-23725 - Updated Designer API documentation
• DSOF-23900 - Fixed an issue where quitting d3 and re-opening, IPVFC stream was disabled

• DSOF-21119 - GPU fan speed is now programmatically set on vx4+
• DSOF-23479 - Fixed Access Violations that occurred when a mapping indirection is added to a slot in the Bank Editor, and when a new indirection is subsequently attempted
• DSOF-23569 - SDI- IPVFC: VX4 output is no longer tearing or not outputting
• DSOF-23726 - IPVFC - Addressed a 10 second sleep that was causing 'Timed out waiting for output mode change' error notification

• DSOF-23660 - Support Riedel MN-Z-SFP-2T-SDI-12G

• DSOF-23630 - Fixed an issue when #upgrading to r24.0, SDI VFC outputs were forced to 444
  and not 422
• DSOF-23691 - Fixed an issue where using 3D perspective projection did not work when using 3D
  content
• DSOF-23714 - Fixed an issue where using 3D perspective projection did not work when using 2D
  content
• DSOF-23722 - Fixed an issue where 'DisplayList' object had no attribute "printimmediate" when
  opening patch editor

• DSOF-23249 - Fixed an Access Violation on deleting a layer mapped to a pre comp
• DSOF-23253 - IPVFC - Fixed issue with 1280x720@24hz mirror mode and various other formats on gx3 presenting some artefacts on the LED. (PTP)
• DSOF-23345 - Fixed an issue where StageRenderLayer displayed certain proxy levels as if they were proxy-off after opening the feed view
• DSOF-23447 - Fixed a RenderStream crash to desktop when using texture parameters
• DSOF-23487 - Fixed an Access Violation when creating the alignment point when using OmniCal
• DSOF-23514 - Fixed all screens being inactive In VR
• DSOF-23556 - Fixed an issue where DCS focal length was incorrect when sensor sizes were not set to 35mm
• DSOF-23615 - Fixed an issue where MR set plate resolution changed when switching cameras with different overscan
• DSOF-23675 - XR: Fixed a Python error "no attribute 'refreshObservationList' when adding a manual observation
• DSOF-23690 - Fixed an Access Violation in feed view with IP VFC on remote machines, causing grey screen on startup

• DSOF-17848 - With "disableDmxPacketSendWait" on, lost sACN node on network still causes the project to slow to a halt.
• DSOF-17540 - Sequencing changes do not transfer to other machines in session when restoring a snapshot
• DSOF-17193 - Multi User Edit in UE requires preferred sync adapter to be set to a network adapter which is available to all machines
• DSOF-17108 - Current NCAM data implementation used can exhibit unreliable packet timing
• DSOF-16935 - d3 cannot set SDI VFCs to Quad 4K 2SI 23.98, 24, 29.97 or 30Hz
• DSOF-16425 - Renderstream: When using MultiChannelMapping, only one spatial map w backplate is able to change position/rotation
• DSOF-15445 - Editor machines with a user account linked to an Microsoft Account can't join d3 sessions due to permissions errors

Q-SDI VFC Firmware advisory

Background:

SDI VFCs are unable to achieve a guaranteed genlock to an interlaced genlock signal. There is 50% chance there will be a phase offset of 1 field (180 degrees). This is due to the way in which the sync cards for both AMD and NVidia GPUs detect genlock signals.

Firmware version 1.9.0 adds a button to reverse the field, which enables you to revert to the alternate field if genlock is phase offset. To properly use this feature, you will need to have the relevant equipment to be able to measure the phase of the SDI output.

Firmware version 1.9.0 requires the use of r17 or greater.

Impact of Issue:

Any Q-SDI VFC shipped with firmware 1.8.0 or earlier and needing to lock to interlaced Genlock Signal

Affected Hardware:

All Q-SDI VFC shipped with previous firmware versions.

How to determine the current firmware version:

• Populate VFC compatible disguise machine with only the SDI cards you want to check.
• Run vfcfirmwareupdater.exe located at C:\Program Files\d3 Production Suite\build\msvc
• Check Firmware Version

How to update to v1.9.0:

• Populate any VFC compatible disguise machine with only the SDI cards required to be updated.
• Download the VFC firmware update from: https://d3packages.s3.amazonaws.com/vfc/quad_sdi_vfc_v1-9-0.rbf
• Run vfcfirmwareupdater.exe located at C:\Program Files\d3 Production Suite\build\msvc
• Click Choose file and load the downloaded VFC firmware update. The filename should be quad_sdi_vfc_v1-9-0.rbf
• Slots will be automatically selected. Ensure only SDI type cards have this firmware update applied to them.

• Click Update Firmware, the update will start and will take between 10-25 minutes.

• On completion, the Firmware version field will not update until all cards have finished updating and have been re-initialised and detected.

• DSOF-3357 Ability to view waveform of audio in modules

The audio waveform allows users to visualise the audio output of a single layer, a collection of layers or the quantized audio track while working in the keyframe editor. This permits them to add keyframes while taking audio output as a consideration at a glance.

How-To

To visualise the audio waveform of one or more layers:

1. Create one or more audio layers

2. Set the audio track of the layer(s)

3. Open a keyframe editor

4. Right-click in the keyframe editor area to access the options

5. Click on

a. layer to visualise the waveform of the currently opened layer

b. combined to visualise the collective waveform of multiple layers

To visualise the audio waveform of the quantized audio:

1. Add an audio track to the track

2. Open a keyframe editor

3. Right-click in the keyframe editor area to access the options

4. Click on quantised to visualise the waveform of the timeline audio track

Key widget audio waveform modes

Single layer audio waveform

Combined layers audio waveform

Quantised audio waveform

Audio waveform with volume keyframes

Audio waveform in quantised mode with quantised track

• DSOF-7298 Dynamic Layer Naming

This feature allows users to rename layers with dynamic tags that will be automatically replaced in the rename process by specific values in the layer.

How-To

1. When renaming a layer either by right-clicking on the layer or pressing alt+r this feature is available.

2. When renaming the layer you can use words between curly braces to create dynamic tags like this {special tag}

3. Hitting rename on a layer will then automatically replace the text in that tag with special values based on the tags.

4. The tags that are supported are:

a. {type} is replaced by the type of the layer.

b. {index} is replaced by an incrementing index starting from 1. i. You can append a number after \"index\" as the start number (e.g. {index5}).

c. {currentname} is replaced by the current name of the layer.

d. {<field>} will be replaced with the name of the first keyframe in the layer with the name <field> i. Examples: {mapping}, {speed}, {blend mode}. ii. If a field is not present in the layer the {<field>} text will be removed from the final name.

5. Typing in a layer name with mis-matching {} tags will stop renaming and make the rename widget turn red with an explanatory tooltip.

Documentation:

Right-clicking on the field will bring up the documentation as described above as well as text boxes that save the last rename used and places for the user to store renames that are used frequently.

Renaming multiple layers:

When renaming multiple layers the user is presented with a confirmation dialogue that shows a preview of the renames to occur. At this stage the user can either abort or finish the renaming. This dialog can be toggled on and off with a toggle.

• DSOF-11013 Support for YUV 4:4:4 modes from the Quad-SDI VFC card at 1080p when using Firmware 1.9.0

We have enabled support for YUV 4:4:4 chroma subsampling from the Quad-SDI VFC card after updating the firmware to 1.9.0: 1080p30, 1080p29.97, 1080p25, 1080p24, 1080p23.98

• DSOF-14192 Bank Editor detach and attach resource view options

We have enabled users to detach the Resources view from the Bank Editor, making access easier when working with lots of resources. To access this feature, open the ‘options’ menu on the Bank Editor and click on ‘Detach Resource View’. This allows users to have the Resources view separate to the Bank Editor. Each view can be made larger or smaller according to what is required, and users can still drag and drop files into the Bank Editor. The Resource View can be reattached by opening the ‘options’ menu on the Bank Editor and click on ‘Attach Resource View’.

• DSOF-20481 "Apply Matrix Feed Routing" button added to Feed Output

We have added an “Apply Matrix Feed Routing” button in the Feed Output menu. This enables users to send the Matrix In-Out settings and Presets to the corresponding Matrix, and avoid mismatching between Designer and the Matrix. In previous releases, Designer would not send the Matrix In-Out Settings and Presets to the Matrix.

• DSOF-22859 Tell the user which Expression doesn't match any known Resources

In previous releases, when we cannot match a name in an Expressions with any loaded resources, we do a potentially very costly brute-force search as warned in a notification. In r24 we tell the user we now notify the user which name can’t be matched so that it can be fixed.

• DSOF-13096 Projector editor should use checkboxes

We have enabled a check box in the Dynamic Blend dropdown on the Projector editor menu to enable and disable Dynamic Blend, and to Use Snapshot (yes/no).

• DSOF-13485 Improve soft edge gradient with S curve

We have enabled a predefined S curve interpolation that can be used as an option to the linear curve when generating custom softedge textures. This can be found as a ‘S Curve Interpolation’ toggle when creating a SoftEdgeTexture mask editor.

• DSOF-14203 Sockpuppet: auto populate error message to include bank and slot for easy navigation

We have adjusted the error message found when users are notified that there is an Auto Populate Conflict in the Bank Editor within Sockpuppet. The new error message outlines “Bank X / Slot X already contains Media_Name.mov - couldn’t auto-populate older media Media_Name.mov”

• DSOF-15109 OSC output data for 'trackposition' should match Designer timeline

When adding an OSC Event Transport to the current transport, we have enabled the track position from the OSC output data to match the timeline markers within the Designer GUI.

• DSOF-20363 Inconsistent Tag notification should tell users to amend their naming

The ‘Version tag inconsistent’ notification tells users that the folder or file name may need amending.

• DSOF-20382 Ability to override alpha rendering order

In previous releases, when working with two LED or projection surfaces with the blend mode set to alpha, the default behaviour would be that surface 1 would always cover surface 2. In r24 we have enabled a ‘depth sort override’ that enables users to manually override the depth sorting. Objects with lower values will be rendered before objects with higher values.

• DSOF-20581 Add ability to override un-sockpuppeted controls in video layers to take from the video clip instead of from the timeline

Sockpuppet layers expose 4 frames on the layer that are usually set directly on the video clip object when used with a normal video module - those being Frame Index, Trim Frames, Loop In Frame, and Loop Out Frame. These are exposed on the Sockpuppet Video Module in order to control them via Sockpuppet.

We have enabled the ability to set an option switch called overrideUnpatchedMediaFields which mean that the Frame Index, Trim Frames, Loop In Frame and Loop Out Frame fields will be taken from the video clip instead of being directly sequenced when they are not used in Sockpuppet. When these fields on the layer are used in Sockpuppet then they behave as expected and can be controlled by Sockpuppet external controls.

• DSOF-21087 Improve input/output transform widget usability
• DSOF-21351 Allow user to export compositor and output frames to content directory

We have enabled users to capture a single frame from the output or compositor feed so that it can be used as content within a scene. We have added ‘Export Compositor Frame’ and ‘Export Output Frame’ in the Feed View.

• DSOF-21392 Add hotkey for jumping to the end of the track

We have added a hotkey [End] that enables users to jump the playhead to the end of the current track.

• DSOF-21563 Detect when d3service is not running on disguise servers and advise
• DSOF-21711 Add inverse transform for RED Wide Gamut

We have added an option for RED Wide Gamut, a colour space designed to encompass every colour that is recordable by RED’s current and past cameras. This can be found in ACES mode under the list of Output Transforms (ODTs) under ‘Camera’.

• DSOF-21712 Add Gamma 2.6 utility transforms

We have added an option for Gamma 2.6 in the utility output transform list for both Input Transforms (IDT) and ODTs to support users working with projector and LED screens that operate with a gamma of 2.6 in Designer. In previous releases, Gamma 2.2 and Gamma 2.4 were available.

• DSOF-22043 Profiler widget should not bring up the text write-out and graphs on default

We have removed the text write out of the trace and various graphs from the profiler widget, which can be found by pressing CTRL + ALT + P. The widget provides buttons to change the profiler name, start and stop recording, and live monitor which will then bring up the original text write out and various graphs.

• DSOF-22553 Searching in media lists should have the option to behave like a filter

We have enabled users to be able to specify in any objectview how they’d like searching and filtering in all object views to behave. This can be accessed by pressing the little arrow next to the search bar in the object view.

There are two options - Alphabetical Filter and Relevance Search. The option selected will be machine-wide and will not transfer to other editors/controllers in the session. It will also persist through restart.

• DSOF-22741 BRGW fixture We have added the ability for users to add BRG + White (BRGW) fixtures within Designer.
• DSOF-22847 Make sure receive health widget keeps updating between launch of RenderStream

We have enabled the Receive Health widget for RenderStream continues to update when RenderStream is stopped and restarted so that it can be pinned as a way of monitoring the health of RenderStream.

• DSOF-22974 Audio waveform: Keyframe widget options need more context

We have added text labels for each section of the Keyframe widget that describe the section controls for Keyframe Interpolation, Audio Visualisation and Key Mode.

• DSOF-23006 Transport Manager: Incoming clock should be displayed even when transport disengaged

In previous releases, ‘Not engaged’ was shown when the transport was disabled. We have enabled users to see the incoming timecode within the Transport Manager widget. The timecode is shown but greyed out to demonstrate that the timecode status is known. If the timecode clock is running, it will update in the Transport Manager widget. If the timecode clock is not running, the last time received will be shown.

• DSOF-4778 - Fixed an issue where topological sort would find a cycle when duplicating projectors with populated DSE exclude lists
• DSOF-4900 - Fixed projector output mode not being fully synchronised on editor join
• DSOF-14238 - Added a solution to Bank thumbnail spaces preventing Resources list to be seen
• DSOF-15539 - Fixed an issue where fuzzy search did not prefer matches which begin with the search term
• DSOF-16935 - Fixed Designer being unable to set SDI VFCs to Quad 4K 2SI 23.98, 24, 29.97 or 30Hz
• DSOF-17691 - Fixed an issue where alembic mesh was not showing video in LUX renderer
• DSOF-18781 - Fixed the FPS indicator not being centred
• DSOF-18817 - Fixed ADL Function Pointers failing to load
• DSOF-19448 - Fixed the zoom size of bookmark on project restart
• DSOF-19663 - Fixed an issue where event logs generated with system / project diagnostic do not save display information
• DSOF-19889 Fixed inconsistency in the naming of Colour shift between brightness / contrast and hue / saturation
• DSOF-20138 - Disabled "Draw control points on output" by default
• DSOF-20158 - Fixed an issue where directory changes within symbolic link / directory junction were not detected
• DSOF-20159 - Fixed an issue where the projector list editor showed a "visualiser" section that did not exist in editor
• DSOF-20202 - Fixed an issue where DSE Include / Exclude lists could contain the same projector multiple times
• DSOF-20246 - Fixed an issue where soft edge texture output points did not scale with feed rectangle
• DSOF-20567 - Fixed an issue where changing the stream parameters while stopping a stream cause a crash 
• DSOF-20707 - Fixed an issue when using multiple feed scenes, the feed name listed in Feed view did not update when loading a feed scene
• DSOF-20791 - Fixed an issue where "Edid port invalid errors" on applied feed settings
• DSOF-20798 - Fixed an issue where the ACES mode HLG utility showed a black window on videoin
• DSOF-21025 - Fixed OSC Indirection in video asset for change video in not working
• DSOF-21407 - Fixed an error in IdentityDomain when upgrading project
• DSOF-21447 - Multi Feed selection GUI is no longer inconsistent
• DSOF-21457 - Fixed d3manager taking 1-2 minutes to launch after reboot
• DSOF-21483 - Fixed DeltaIn::lockAndCreateStream failing to correctly check if channels have been locked
• DSOF-21536 RenderStream: - Fixed an issue where resetting keyframes on Scene field resulted in "INVALID" selection
• DSOF-21552 - Fixed an issue where selecting Rescan whilst Proxy Maker is running results in errors
• DSOF-21707 - Fixed an issue when starting RenderStream "!fragment.stream.empty()" could occur
• DSOF-21765 - Track Section Fade taking priority over all layers in the section
• DSOF-21768 - Fixed DMX Indirection not affecting layer mapping when assigned
• DSOF-21782 - Installer no longer takes focus to a text field as soon as it launches, taking keyboard input from whatever else the user is doing.
• DSOF-21814 - Fixed an issue where Renderstream Layer using Perspective Map with DMX could get stuck on Awaiting Requests
• DSOF-21921 - d3Manager default column widths improved
• DSOF-22013 - Fixed a 'NoneType' error when duplicating / changing a SpatialCalibrationConfig resources
• DSOF-22174 - Fixed Unused Media Domain not removing DxTexture and Audio from cache
• DSOF-22175 - Fixed an issue where MachineMediaRegistry did not update itself when an Image Sequence was removed from disk 
• DSOF-22231 - Fixed an issue where Videos would sometimes not play the last frame
• DSOF-22236 - Fixed an issue where "Create New Layer" and "Create New Object" lists looped back to the top of the list when scrolling or using arrow keys to select new object
• DSOF-22304 - Fixed an error in IdentityDomain after clearing ingestion history
• DSOF-22322 - Fixed an issue Fuzzy Search sometimes behaved unexpectedly and gave worse matches before better ones.
• DSOF-22350 Spatial Calibration- Fixed error message "!!! Main thread hung due to early render access < DxTexture::movePixels"
• DSOF-22369 - Fixed an issue where OSC Indirection Controllers required that the user specify the object type in the message
• DSOF-22372 - Fixed an issue where DSE did not apply correctly to automated screens using tracking sources
• DSOF-22417 - Fixed an issue where virtual lineup complained about inactive cameras if any camera is not active
• DSOF-22453 - Fixed an issue when using multiple MR sets, the last MR previously opened populate the MR set list
• DSOF-22473 - Fixed an issue where some alembic files appear flipped when loaded
• DSOF-22474 - Fixed the Installer being unable find libprotobuf.dll when installing Designer
• DSOF-22518 - Designer now respects the content viewpoint of RenderStream clients which modify the camera data
• DSOF-22526 - Fixed an issue where the incorrect automatic shutdown message (on exit) when unplugging license was displayed
• DSOF-22544 - Fixed an issue where d3manager disconnected network adapter warning banner was cropped
• DSOF-22548 - Fixed an issue where the CDL layer did not tell the user why it is red
• DSOF-22573 - Alembic mesh: Fixed an issue where imported normals were wrongly assigned
• DSOF-22683 - Fixed Udp::bindToPort error not correctly specifying which port it failed to bind to
• DSOF-22684 - Fixed an issue where the Actor Status Widget' reported OSC devices as offline when not receiving 
• DSOF-22702 Deltacast capture: - Fixed an issue when moving from 1080p to 2048p50, the capture thread would crash repeatedly
• DSOF-22713 - Fixed an issue where reference points could not be unlocked from the reference points management widget
• DSOF-22721 - Fixed the console being spammed with "Warning: Trying to truncate to a negative width"
• DSOF-22728 RT: - Fixed topological sorting found while changing track in attached project
• DSOF-22754 - Fixed an issue where layer naming jumped 322 if the same type of layer is created
• DSOF-22769 - Fixed an issue where a "Project restart required" notification was displayed even when it isn't required
• DSOF-22775 - Fixed an Access Violation when adding the camera (NVIDIA broadcast) option to an input
• DSOF-22779 - Fixed an issue where three virtual VFC heads were created when Split Mode changed from Mirror to Quad
• DSOF-22780 - Fixed an issue where it was not possible to open the rollback window of two objects at the same time
• DSOF-22796 - Matrox capture : Fixed an issue where 'No signal' mapped videoins contribute to 12G/3G limits
• DSOF-22797 - Matrox capture : Fixed valid 12g signal being detected on a 3G port
• DSOF-22813 - Fixed an issue where removing the version tag from the folder name after an Inconsistent Tag notification caused image versions to fail
• DSOF-22825 - Fixed an Access Violation in checkIfCurrentWorkloadHasLostPackets when opening two streams on same render node
• DSOF-22851 - Fixed an issue where it was not possible to set none Keyframe is Resource keyframe editors
• DSOF-22875 - Fixed an Access Violation With fade transtion, when forwardin the playhead in video trigger layer 
• DSOF-22891 - Fixed an issue where RefpointsManipulator shadows based class onFocusChanged() instead of overriding it
• DSOF-22932 - Fixed implereview tool not working with tortoise 6.2 or later
• DSOF-22954 - Fixed FNV hash in fnv.cpp
• DSOF-22970 - Fixed an issue when changing the split mode of a VFC card from Quad to Mirror removed virtual heads
• DSOF-22984 - Fixed "&resource" error when attempting to set "None" resources in layer parameters
• DSOF-22990 - Tracking marker module - Fixed an Access Violation when setting marker image to ‘None’
• DSOF-23059 - RenderStream: Fixed an issue where proxy streams no longer being identifiable
• DSOF-23073 - Fixed an error in 'StreamObject' object when attempting to open log via Show Log button
• DSOF-23092 - Fixed an issue where the camera editor throw an error attempting to add field to "Appearance Separator"
• DSOF-23116 - Fixed being unable to import gui.MediaDistributionWidget
• DSOF-23125 - Fixed an issue where text boxes with nothing in them were invisible until text is entered
• DSOF-23130 - Fixed an issue where the camera did not use DCS provided focal length
• DSOF-23132 - Fixed an Access Violation when media sync fails
• DSOF-23156 - Fixed an issue where 'bounds-check' error was displayed when attempting search with no items
• DSOF-23161 - Fixed an issue where the Ttext field and caret were not visible for empty text fields
• DSOF-23166 - Fixed an issue where Right-click > Add Feed Rectangle in feed view threw error notification "global name 'currentMachines' is not defined"
• DSOF-23172 - Fixed an issue where StreamInfo population in /renderstream/layerstatus needed refactoring
• DSOF-23176 - Trial: Fixed an issue where Feed Mapping output was enabled, but shows red text that outputs are disabled
• DSOF-23185 - [ACES] Fixed an issue where sShader failed to compile when selecting 'Gamma 2.6' as Output Transform
• DSOF-23186 - Fixed an issue where it was not possible to rename groups or layers inside of a group, causing a 'MulticastDelegate' error
• DSOF-23252 RenderStream: - Fixed an issue where the alpha channel from all render nodes was added together
• DSOF-23311- Fixed an issue where the Feed Output was disabled, but did not tell the user why
• DSOF-23320 - Fixed an issue where a Matrox capture card could randomly drop frame during playback
• DSOF-23440 - Fixed an issue where the DisplayManager stopped working after attempting to apply feed settings
• DSOF-23523 - Fixed an issue where disable UnusedMediaDomain by default caused issues
• DSOF-23557 - Fixed an issue with d3 service clean up cloud folder while it iwa empty, causing login and read issue
• DSOF-23655 - Fixed an issue where Metadata fields didn’t't open when right-click on the value box

• DSOF-23093 - Fixed an issue where frontplate mapped content did not respond to AR fades
• DSOF-23183 - Fixed an issue where attempting to edit the Stacking Warp caused "no attribute 'rect'" to be displayed
• DSOF-23395 - Fixed an issue where StageRenderModule proxy levels were incorrect during transition
• DSOF-23404 - Fixed an issue where a  m_file -> codec() error was thrown on the Actor relating to media ingestion
• DSOF-23428 - Fixed an issue where it was impossible to open a workload with an unknown asset
• DSOF-23514 - Fixed screens being inactive in VR

• DSOF-23184 - Restricted range of of PTP domain number for IP VFC card to valid range 
• DSOF-23218 - Fixed IP VFC Cards from misreporting a missing PTP source
• DSOF-23346 - Fixed an issue where the video input patch reported wrong Deltacast card for vx4
• DSOF-23386 - Fixed an Access Violation when receiving Artnet
• DSOF-23408 - Fixed an issue where failing to read corrupt or missing frames from content caused content to stop rendering requiring a project restart

• DSOF-22406 - Fixed an issue where applying 10 bit feed settings on Nvidia disguise only applied to the GUI and not to VFC cards
• DSOF-23141 - Fixed an issue where changing SLC region sizes resulted in error
• DSOF-23151 - Fixed an issue where frames would be dropped when camera switching unless patch editor preview was enabled
• DSOF-23241 - Fixed an issue where Resource Transport was blocked on the director when deleting MidiNote or Playmode Module
• DSOF-23248 - Fixed an issue that occurred when the shelved packet debug widget was open, live update was blocked when splitting a rect in a feed map on editor
• DSOF-23254 - Fixed an issue where RT was blocked when importing a layer that overlaps the end of the timeline
• DSOF-23255 - Fixed Shader compile error when using Live Action Volume with virtual camera
• DSOF-23263 - Fixed an Access Violation when selecting none when importing feeds from table
• DSOF-23270 - Fixed an error when moving feed rectangles between output heads
• DSOF-23272 - Fixed an issue where quickly duplicating a text layer twice and then deleting one on an editor could cause Live Update to become blocked
• DSOF-23273 - DMX Sockpuppet: Fixed an issue where the patch assignment widget doess not update after clicking "Unpatch All Layers" until the DMX patch settings widget was closed
• DSOF-23275 - Fixed an issue where Live Update was blocked after unpatching DMX sockpuppet layer
• DSOF-23242 - When Live Update is blocked on the director this error is now visible in the Actor Status Widget

• Added support for our IPVFC cards, outputting video in ST 2110 Mode*
• *SDI functionality will be added in a future release

• DSOF-18962 - Fixed an issue where Pixelate layer did not work without a mask input
• DSOF-20373 - Fixed an Access Violation after 'Attempt to retrieve slug font data that hasn't been loaded!'
• DSOF-21734 - Performance: Improved FPS for layers
• DSOF-22630 - Rollback: Fixed an issue seen when rolling back a camera to a previous version, the 'from' path changed when the import widget opened
• DSOF-22877 - RenderStream: Fixed an error when attempting to restart workload running an Unreal asset
• DSOF-23016 - Reduced CPU usage when using multiple indirections
• DSOF-23028 - Fixed Dynamic Feed expressions
• DSOF-23058 - Fixed an issue where setup_fonts.py took about ~40 second to convert/copy .ttf and .otf during installation if no fontcache existed
• DSOF-23079 RenderStream: Fixed an error when "truncate log" when attempting to start a workload running Unreal asset
• DSOF-23085 - Fixed feed warp not showing content
• DSOF-23097 - RenderStream: Fixed an issue where RenderStream failed to create workload log file or folder, if the folder did not exist
• DSOF-23139 - Made Output now exports size for mpeg-4 stage movie list of options rather than custom value boxes
• DSOF-23226 - Fixed Track jump module selection of 'current track' does not persisting

• Designer Public APIs

A suite of revamped and extended HTTP APIs for Designer are available in this release.

A new website for full documentation is available at https://developer.disguise.one, including

general guidance, API method documentation and OpenAPI JSON specification download.

The API documentation is also available from within Designer itself, by following the menu option

in d3manager -> Help -> Open API Documentation.

The new APIs fall into two categories: The Service APIs relate to functionality provided by the

d3service runtime and are available whenever disguise is installed on a machine. The Session

APIs relate to the currently running session and as such are only available when the d3 runtime is

running.

The previously existing V1 API, found at /api/v1, should be considered deprecated as of the launch

of the stable API set under the Service and Session APIs.

New API integrations should not target the V1 API and should instead use the APIs documented

under /api/service and /api/session. No new APIs or functionality will be added to V1, however the

V1 API will be maintained for the foreseeable future and we will give notice if we plan to remove it

in the future.

• Export Designer Scene to Disguise Cloud Previz

Previz link allows the user to export their stage and content from Designer, and upload it to disguise drive as a Previz Scene. With a URL to the uploaded Previz Scene, users and disguise show programmers can share the current state of the disguise show without restricting the end customers with baked-in camera angles, or having to install Designer themselves.

How-To

1. Ensure that you are logged in to your disguise cloud account via d3Manager

2. Access the cloud export editor either by:

a. shift-selecting a portion of the timeline, or

b. opening the d3 state editor

3. Select the disguise drive organisation and drive to export the Previz scene to, refreshing the storage information if new organisations and drives have been created

4. Choose to either export the highlighted portion of the timeline, or the whole timeline

5. Click on Export and wait for the progress bar to complete

6. Click “Copy URL to Clipboard” and paste it in the the web browser address bar to open uploaded scene in Previz.

• DSOF-20573 Support exporting stage from Designer in glTF format

We have enabled users to be able to export stages in Designer in gITF to support files to disguise

drive as a Previz scene. Under the stage menu export section, change the extension to either gltf

or glb. The option button will also become available which will contain some material and

compression settings.

● DSOF-23038 AV in "Upload assets" test case in test_cloudserver

• DSOF-18764 - Legacy Video Module doesn’t work with color shift
  • Workaround: Not known
  • Affects Version: r19.1.7
  • Fixed in r21.0

• DSOF-20056 - Tracking Camera frustrum out of sync between Director & Actor with AxisObjectTrackingSource
  • Workaround: Not Known
  • Affects version: r21.0
  • Fix due in r21.0.1

• DSOF-18015 - Intermittent issue - Heap Corruption causing Crash To Desktop
  • Workaround: Not known
  • Affects version: r19.0.1

• DSOF-17848 - With "disableDmxPacketSendWait" on, lost sACN node on network still causes the project to slow to a halt.
  • Workaround: Add a static entry into the local systems ARP table.
    • Open an elevated commant prompt.
    • Find out MAC for IP, could use arp -a to see existing entries in local arp cache.
    • Run netsh interface ipv4 show interfaces to get a list of interface names.
    • Add a new entry to the ARP table netsh interface ipv4 add neighbors "<interface name>" <dest ip> <dest mac>
    • E.g netsh interface ipv4 add neighbors "Wi-Fi" 10.105.1.253 01-02-03-04-05-06
    • Remove entry like so; netsh interface ipv4 delete neighbors <dest ip>
    • Important - Remove entries when done or re-image system!!! Otherwise network issues may occur in the future sending the manually added IP addresses.
  • Affects version: r18.1.7

• DSOF-17540 - Sequencing changes do not transfer to other machines in session when restoring a snapshot
  • Workaround: Not known
  • Affects version: r18.1.2

• DSOF-17193 - Multi User Edit in UE requires preferred sync adapter to be set to a network adapter which is available to all machines
  • Workaround: Often the preferred sync adapter is set to the 25Gb network to facilitate faster sync. Unless all machines in the network have a 25Gb adapter, the preferred sync adapter must be set to another network adapter when multi user edit sessions are running in UE. The adapter can be changed back for when running sync tasks.
  • Affects version: r18.0

• DSOF-17108 - Current NCAM data implementation used can exhibit unreliable packet timing
  • Workaround: Not known
  • Affects version: r18.0

• DSOF-16935 - d3 cannot set SDI VFCs to Quad 4K 2SI 23.98, 24, 29.97 or 30Hz
  • Workaround: Not known
  • Affects version: r18.0.2

• DSOF-16425 - Renderstream: When using MultiChannelMapping, only one spatial map w backplate is able to change position/rotation
  • Workaround: Not known
  • Affects version: r18

• DSOF-16082 - Clustered Rendering: d3service requires restart for asset discovery to work on new Unity executables
  • Workaround: restart d3 service
  • Affects version: r18

• DSOF-15553 - Feed mapping editor shows white screens in a notch layer on first use. In subsequent use it will then show the first pixel
  • Workaround: Not known
  • Affects version: r17.4.9

• DSOF-15445 - Editor machines with a user account linked to an Microsoft Account can't join d3 sessions due to permissions errors
  • Workaround: Create a second local user account
  • Affects version: r17.4.8

• DSOF-12837 - Looping within a section with loop play mode occasionally plays content of first frame in next section
  • Workaround: Not known
  • Affects version: r17.0.2

• DSOF-21313 - Fixed an issue where machines with bluefish cards could spontaneously restart
• DSOF-22986 - Fixed an issue where launching designer would always trigger "VFC outputs may be in an inconsistent state"
• DSOF-23008 - Fixed an issue where live update could become blocked and changes would not propagate through the session
• DSOF-23095 - Fixed an issue where vx4 and vx4+ video inputs do not update when switching Capture Card Variant to Matrox

• DSOF-22680 - Fixed an issue where DMX failover resulted in understudy hang when sending a command with the value "1"
• DSOF-22874 - Fixed an issue where the Fader layer did not work with more than three screens and actors in session
• DSOF-22912 - Fixed a memory leak in the GUI
• DSOF-22968 - Fixed an issue where it was not possible to add layers to layer stacks

• DSOF-22297 - Fixed an issue where it was not possible to set outputs to 10 bit at certain resolutions and frame rates
• DSOF-22409 - Fixed an issue where virtual lineup was not shown when the physical camera is set on the Camera object in non-dedicated director mode
• DSOF-22631 - Fixed an Access Violation when attempting to rollback objects with multiple instances of the same object type exist in the project
• DSOF-22755 - Cue list window no longer causes frame drops

• DSOF-22001 Upgrading project removes RenderStream scene keyframes

• DSOF-22692 - Fixed an issue where a transition from 'None' to media did not respect
  transition time
• DSOF-22878 - Fixed an issue where if a failure to load GPGPU occurred it led to an
  Access Violation and failure to launch project

• DSOF-22032 - Fixed an Access violation when closing Check Cameras window
• DSOF-22034 - Renderstream: Fixed an issue when using 3+ texture parameters into RenderStream resulted in glitchy/scrambled textures
• DSOF-22208 - Fixed the D3NetManager instance no longer being static leading to a potential performance hit
• DSOF-22581 - Fixed an Access Violation when setting then unsetting media in video layer
• DSOF-22636 - Fixed a 'long too big to convert' error when previewing empty videoin
• DSOF-22637 - Fixed an Access Violation when previewing VideoClip with embedded audio
• DSOF-22663 - Fixed an issue where Deltacast capture could not decode specific psf formats

• DSOF-21736 Live Action Volume

Live Action Volume allows users to define a region of an XR stage which contains ‘live action’, e.g. performers and props. All areas outside this volume will be covered with virtual set extension, rather than exposing the filmed LED screens.

The reasons for doing this include:
1. To mask on-stage objects outside the performance region (e.g. cameras, lights).
2. To make more of the frame be taken up by virtual content, which seamlessly blends with the filmed screens within the live action volume.

How-To

To add a live action volume to an XR setup:

1. Create an object (e.g prop, screen etc.)
2. Change the object’s render layer to ‘Live action volume’
3. Set the object’s mesh and more it to the desired location on the stage to contain all the live action
4. Multiple live action objects can be created to cover disconnected regions of live action

Usage notes:

Live action volume objects (along with set extension mask and addition objects) apply globally. All objects in the stage in these layers will automatically modify the set extensions of all MR sets, without needing to be added to the MR set ‘On-stage’ object list.

On-Stage objects positioned behind or in front of a Live Action Volume won’t make them covered by the Set Extension unless they are on the side of it as we only render the Live Action Volume in 2D.

• DSOF-3606 Ability to set non-SMPTE timecode for frame accurate sequencing in any frame rate

We have created an option to set Custom Timeline FPS to support frame accurate sequencing. This is made available in the Timecode Collapsible widget found in the right-click menu for Transport.

• DSOF-11343 Debug log window resize

It is now possible to resize the debug log window, which makes it much more user friendly.

• DSOF-12624 Notify user of new or mismatching VFC firmware

If the VFC firmware is found to be old or mismatching, this is now flagged with a notification stating “Found old VFC firmware”.

• DSOF-15168 All objects should be able to be used as set extension masks/additions without adding as an on-stage object in the MR set

In order to add set extension masks or set extension additions, it is no longer necessary for these to be part of the MR set. All objects in the relevant layers can work as masks or additions, without  needing to be in the MR set.

• DSOF-19189 Show film strip of a clip in the key frame editor

The film strip for a video is now available in the key frame editor. This is useful to get an overview of the content without having to play it through. This feature is disabled by default, and can be enabled by unchecking the “Disable key frame editor film strip” option in the Project Settings.

• DSOF-20495 Add mellanox dumps to system diagnostics

Mellanox crash dumps are now included in the system diagnostics.

• DSOF-20669 Remove blue flash watermark from feed view

The Feed view has been modified so that both the Feed Rectangle and Feed Output behaviour is consistent. In previous releases, the Feed Rectangle would fade to blue while the Feed Output would not fade 

For a non-server Designer machine, the Feed rectangle will fade to blue (on gold release) or purple (on a beta release) every 10 mins. The Feed Output will exhibit the same behaviour.

For any disguise server, the Feed Rectangle shall never fade on a gold release but fade to purple on a beta release. The Feed Output will exhibit the same behaviour.

• DSOF-20844 Indicate which machine is the local machine in d3manager

In d3manager, the local machine is now highlighted in bold. As a user, this is useful when accessing multiple machines via a KVM and needing to know which of the machines listed is the one you are logged onto.

• DSOF-21987 Cloud login improvements

The disguise cloud login functionality within Designer which was released in r22.2 has undergone several quality improvements.

• DSOF-21196 Add ability to customise the API endpoint

• DSOF-21322 MTC layer does not support 29.97 drop frame

The MTC layer for outputting MIDI timecode now supports 29.97 Drop Frame (DF) timecode.

• DSOF-21618 ‘Cue table exported’ pop-up added

• DSOF-21623 Remove ‘HDMI 3840X2160 10bit’ warning

A confusing warning message in Notifications has been removed.

• DSOF-21633 Allow ALT+G to toggle GUI on all machine roles

• DSOF-21652 Don't render set extension mask when set extension alpha = 0

If the set extension alpha is set to zero, the software no longer renders the set extension mask as it is wasted effort. This performance improvement is applicable to VP setups where set extensions are not used.

• DSOF-21738 Virtual object camera visibility setting

The “Virtual Object Alpha” setting in a Camera enables objects which define regions of interest to be displayed in the visualiser with a specified level of alpha. This is useful for objects such as set extension mask/addition layers, live action volumes or 2.5D layers. 

In previous releases, these objects were not rendered to the camera which could make them difficult to interact with. This setting is now enabled by default in the visualiser camera, but not in other cameras. 

The example screenshot below shows layers of a 2.5D scene which have been output to the StageRender layer being displayed as translucent layers with this setting enabled. The setting is found in the Camera object under Stage Render / Render Settings / Object Visibility.

• DSOF-21785 Tidy up camera visibility settings

The settings of a Camera object have been tidied up in order to take up less space on the GUI, and makes it easier to manage.

• DSOF-21971 RenderStream assets which crash on startup leave no information for fault finding

In previous releases, if a RenderStream asset crashed on startup (before even renderstream.dll loads), there was no way to report why it crashed. In r23, this is now captured, and log files are placed in the %LOCALAPPDATA%\d3\renderstream_workloads folder, with a subfolder for the asset name, then “friendly” workload name. 

Each instance is stored into an instance_n.txt file, where n is the instance number within the workload. The log viewer in Designer is able to view the file via the Designer Logs share on the render machine, so access to all logs from assets which failed to start will be available too.

• DSOF-21984 RenderStream host memory applications need to be able to specify pixel format

This improvement is relevant for developers of RenderStream plugins. The pixel format was limited to BGRA8 pixel formats only on all versions of RenderStream up to 1.30. 

From RenderStream 1.31, the engine can now specify the memory it provides in the same way dx apps can use a reasonable selection of pixel formats in the textures they provide to the API.

• DSOF-22039 Add the ability to render 3D content from spherical mappings

Spherical mapping supports a new property called Content Mode which is set to 2D or 3D. When set to 2D, the behaviour is the same as previous releases. When set to 3D, RenderStream and other 3D layer types (StageRender, Notch and Renderstream) will render 6 views of their world in order to build the 6 tiles of a cube in order to generate 360 degree content.

The cube mapping viewpoints will be automatically created for render engines, resulting in 6 workloads - one for each side of the cube - and the resulting content is mapped for 360 degree coverage, i.e. a 360 degree arc around the spherical focal point. This achieves the same observed behaviour as equirectangular content which spherical mappings normally use.

• DSOF-22454 Run -NoVerifyGc Command on RenderStream Launch

RenderStream layers for Unreal Engine now pass through the -NoVerifyGc option by default for Unreal Engine RenderStream workloads. This significantly speeds up the launching of these workloads, without having to put this config in custom configuration.

• DSOF-4472 - Fixed an issue where it was not possible to unsockpuppet tint or access individual RGB values
• DSOF-16022 - Fixed the object selection outline being incorrect in the camera view with overscan
• DSOF-17699 - Video Input textures are now included in the bandwidth estimates
• DSOF-19158 Fixed an issue where it was not possible to add observation while acting as a dedicated director
• DSOF-19378 - Fixed an issue where the RenderStream log was not always copied to Director
• DSOF-19945 [ACES] - Fixed an issue where the VideoIn Preview failed to preview Input Transforms
• DSOF-19965 - Fixed an issue that occurred when transitioning between two pre-comps in Bitmap layer using "Transition time" causes fade from black instead of crossfade
• DSOF-19968 - Fixed an issue where jumping into the currently running RenderStream layer caused a stutter between 50-500ms
• DSOF-20351 - Fixed an issue that occurred when a showfile was transferred between different GUI resolutions, the widget may have drawn off screen
• DSOF-20522 - Fixed an issue where groups of layer starts could jitter when being selected and resized
• DSOF-20524 - Fixed an issue where Designer received invalid comms messages and crash to desktop
• DSOF-20565 - Fixed overscans on RenderStream content creating a clear visual difference to non-overscanned content
• DSOF-20627 - Fixed an issue where d3service presented an offline error on launch despite d3service running
• DSOF-20726 - Fixed issue where Designer issued warning that a Bluefish driver on a Solo is newer than required
• DSOF-20754 - Renamed Automation in the device monitor icons
• DSOF-20867 - Status UI now handles lost device errors during rendering
• DSOF-21007 - Fixed the debug window text is overflowing
• DSOF-21149 - Fixed an issue where previews were not rendered after a restart in VideoIn patch panel
• DSOF-21200 - Setting UI transparency to off is now represented on Understudies
• DSOF-21201 - Designer could crash if using precomps as texture parameters when switching maps in Unreal
• DSOF-21205 - Fixed an issue where UnusedMediaDomain didn't detect media on remote machines on the first project startup
• DSOF-21250 - Fixed an error in CameraCalibrationObservationEditor when undoing creation of a Manual Observation while editor is open
• DSOF-21269 - Fixed an error in the Colour Picker when undoing colour selection
• DSOF-21277 - Improved performance when using multiple videoins and RenderStreams on vx 4 and vx 4+ due to OCL queue synchronisation
• DSOF-21279 - Fixed an issue where RenderStream ‘receive health’ did not report issues with packet receipt
• DSOF-21281 - Fixed an issue where deleting a keyframe ‘before/after’ when using [] as selector did not work correctly
• DSOF-21282 - Fixed an issue where multi-select on parameters, keyframe modified levels together, but deleting before/after only affected the parameters right clicked on
• DSOF-21294 - Spatial Calibration Object - Fixed an issue when selecting a new calibration object the calibration wasn't applied
• DSOF-21312 - Fixed an issue where opening and closing the d3net manager widget within a session displayed a 'multicastDelegate' error
• DSOF-21319 - Fixed an issue where changing API ports resulted in API documentation not being accessible
• DSOF-21347 - Fixed an issue where ACES input transform options were available on RenderStream assets regardless of Colour Management
• DSOF-21356 - Improved console notifications around dedicated directors applying group feeds
• DSOF-21406 - AnimateObjectPreset: Fixed an error in ScreenConfigurationEditor when adding objects to a ScreenConfiguration
• DSOF-21476 - When restarting a RenderStream, "!fragment.streams.empty()" is no longer shown
• DSOF-21525 - Fixed an issue where GUI Update was sluggish on showfile
• DSOF-21538 RenderStream: Fixed an issue where the pool incorrectly reported asset were out of sync
• DSOF-21539 XR: Spatial Calibration "MulticastDelegate: Fixed 'startup error'"
• DSOF-21572 - Fixed an issue where API Query Parameters were not displayed in the Swagger documentation
• DSOF-21576 - Fixed an issue where deleting unused media didn't work for image sequences
• DSOF-21578 - Fixed an issue where removing fields within an Open layer created a Multicast Delegate error
• DSOF-21593 - Fixed an issue where GPU could lose access when playing 1 x 12k and 1 x 8k Notch LC files at the same time
• DSOF-21597 - Fixed an issue where arrows ended up in a wrong state when removed on remote machine
• DSOF-21598 - Layers no longer cause crash on exit
• DSOF-21619 - Fixed an issue where cue table import on section would break when a project is set to 59.94
• DSOF-21635 - Using a 'StageRender' layer with a perspective mapping in 3D content mode no longer fails
• DSOF-21661 - Feeds no longer have a red border in designer mode
• DSOF-21691 - Fixed an issue where pressing CTRL + 1 with a keyframe timeline open caused an Access Violation
• DSOF-21706 - ‘Spatial map’ now behaves like ‘3D perspective map’ when reprojection distance is zero
• DSOF-21732 Fixed a potential Access Violation when undoing undo colour selection in a Palette
• DSOF-21748 - Fixed issue where SLC Region Updates can no longer be called multiple times.
• DSOF-21755 - Mesh Mapping now supports Vulkan image formats
• DSOF-21783 - Fixed an issue where the overscan field was green when tracking system was used
• DSOF-21790 - Fixed an issue where the text layer text font didn't change to imported fonts
• DSOF-21808 - Console no longer spammed when 'Configure' separator is open inside RS workload
• DSOF-21831 - Fixed a d3Manager crash when renaming project folder
• DSOF-21832 - Fixed an issue where SLC regions were available for all videoclips, even when SLC was not enabled for the project
• DSOF-21836 - Fixed an issue where d3Manager crashed on startup if the current project no longer exists in debug 
• DSOF-21841 - Fixed an issue where with "enableWebGL"on, web still reports WebGL disabled
• DSOF-21847 - Fixed an issue where ALt Drag DMX values resulted in incorrect number assignment
• DSOF-21850 - Fixed an issue where props did not work as live action volumes
• DSOF-21851 - Fixed an issue where the media ingestion history window was blank upon opening
• DSOF-21857 - Fixed an issue where importing the FeedRect setting was not available
• DSOF-21873 - Delete All Unused Media API is now more reliable
• DSOF-21897 _ Fixed an issue where the OpticalCalibrator could hang
• DSOF-21899 - OmniCal: Fixed an issue where projector lens distortion did not update if only 3rd order coefficient is set
• DSOF-21934 - Fixed an issue where Unreal exposed Custom Events didn't behave like any other keyframe in d3
• DSOF-21969 - Fixed an issue where links to RenderStream assets using custom extensions didn’'t get launched correctly.
• DSOF-21970 - RenderStream shortcut asset now respects the working folder option
• DSOF-21973 - Fixed an issue where d3Manager licence check didn't account for developer authorisation and blocked d3 from running
• DSOF-21977 _ fixed an issue where there was no way to save & load a RenderStream asset metadata effectively when using shortcuts
• DSOF-22011 -  Export Output Frame from Feeds now export as expected
• DSOF-22032 - OmniCal: Fixed an Access violation when closing Check Cameras window
• DSOF-22033 - Fixed anissue that occurred when a virtual camera points 180 degrees behind the physical camera, the physical view appeared upside down
• DSOF-22037 - Tracking Marker Module - brightness and colour adjustment now work on the markers
• DSOF-22050 API: Fixed an issue the custom d3service http port was not respected
• DSOF-22061 - Fixed an issue where virtual camera positions would reset on restart
• DSOF-22071 - Fixed an issue where  d3 start-up was stuck with a black window sometimes
• DSOF-22085 _ Projectors in blank projects are no longer set to be Hidden
• DSOF-22092 - Fixed an issue where set extension content was disconnected from screens when backplate reprojection distance is zero
• DSOF-22101 - Camera frustum size no longer increases when virtual camera moves
• DSOF-22118 RenderStream: Improved compressed workloads
• DSOF-22126  - Camera visibility settings - upgrading old project now makes virtual objects visible in the visualiser
• DSOF-22132 - Fixed an issue where Workload Status Widget on the RenderStream layer has the wrong scaling for it's list views.
• DSOF-22133 - Fixed an issue where it was not possible to remove MR sets and Mesh Projections from Hierarchy once added
• DSOF-22136 - Fixed an issue where the tracking marker module didn’tn't clip properly for 2D perspective and feed maps
• DSOF-22164 - RenderStream New Mappings are are now visible
• DSOF-22165 - Fixed an issue wher eit was not possible to Adjust Texture Streaming Assigners when Scene Name is too long
• DSOF-22208 - D3NetManager instance is once again static
• DSOF-22213 - Fixed an Access Violation when trying to access the cue list
• DSOF-22233 - Fixed an issue where the incorrect RenderStream Version was reported
• DSOF-22245 - Fixed an issue where DMX lights with fixtures quickly degraded performance
• DSOF-22304 - Fixed an error in IdentityDomain after clearing ingestion history
• DSOF-22372 - Fixed an issue where DSE did not apply correctly to automated screens using tracking sources
• DSOF-22379 - Fixed an issue where the bitmap module displayed the previous keyframe (instead of the current keyframe) when transition time was set to 0
• DSOF-22384 - RenderStream: Fixed an 'Attempt to allocate more than DX_MAXTRISTRIPS' error when Details widget was open with running workload
• DSOF-22387 - MR set output resolution now affects camera plate mapping resolution
• DSOF-22393 - ‘Apply genlock button’ should be greyed out when genlock is applied as it becomes non functional
• DSOF-22413 - Fixed an issue where scaling the grid spacing down on the testpattern layer produced an exception
• DSOF-22433 - Fixed an issue where Go To Timecode did not work with custom (non-SMPTE) FPS when the frame value wass higher than 29
• DSOF-22445 - Fixed an Access Violation when using profiler on local machine 
• DSOF-21722 - Fixed an issue where vx4’s could lose access to the GPU during NotchLC playback
• DSOF-22488 - Fixed Errors when creating / deleting tags and notes on the timeline

• DSOF-21313 - Fixed instability in Solo machines with Bluefish capture cards

• DSOF-22450 Implementation of Deltacast 8x channel capture card

We are now shipping new vx 4+ hardware with Deltacast capture cards. These can be identified within Designer in the following ways:

- Via the dropdown in the machine menu. The capture variant will be automatically selected as seen below:

- Via the available information in the d3manager “help” dropdown as “Capture Card Vendor”. Within this view, we have also included machine type, serial number, backplane model, and VFC card load

We have also enabled any vx 4+ with Deltacast capture be identified in the following ways:

- A note on the vx 4+ label on the rear of the machine indicating Deltacast capture

- Via the OLED in the machine field. Deltacast is listed as (De)

It is important to note that Deltacast capture is unable to decode the following formats:

- 2K DCIpsf30

- 2K DCIpsf29.97

- 2K DCIpsf25

• DSOF-22011 - Fixed an issue where Export Output Frame from Feeds was not exporting at the expected resolution 
• DSOF-22477 - Fixed an issue where nginx was not launched on vx4 or vx4+ resulting in d3 APIs did working
• DSOF-22541 - Fixed an issue where the 'Capture Card Variant' field became permanently uneditable once machine joins the session
• DSOF-22578 Fixed an issue where patching videoin 5-12 as a media source for a layer did not render to the target surface

• DSOF-21308 - Fixed an issue where failed RmaxVideoIn instances would pollute pool
• DSOF-21731 - Fixed an issue where cube LUTs with negative values didn't parse
• DSOF-22300 - Fixed EXR image support
• DSOF-22305 - Fixed an issue where setting the colour space of a colour profile to Rec.709 did not work until project restart
• DSOF-22511 - Fixed an issue where a "No valid Designer licence detected!" popup blocked Trial release from launching

• DSOF-21766 - Created a d3manager link to sample assets on the website

• DSOF-19487- Fixed an issue when applying feed settings, the bit depth changed from 10 to 8 bit
• DSOF-21425 - Fixed an issue when using an Actor as UCRS controller, all machines would intermittently stop receiving streams periodically and recover on their own
• DSOF-21981 API | Fixed CDL failing to connect to Actors | Director not interactively passing Data to Actors
• DSOF-22295 - vx4+ comes pre-populated with Deltacast input options
• DSOF-22321 - Fixed an issue where d3manager failed to send profiler HTTP request under certain network conditions
• DSOF-22345 - Fixed an issue where the diagnostic zip failed to be generated due to locked file

Matrox Improvements

• DSOF-22431 Switch default Matrox clock to input clock
• DSOF-22106 Wrong input patch preset when Matrox unit is set to Actor
• DSOF-22146 Matrox: occasional dropped frame 
• DSOF-22147 Console can spam with thousands of lines of "!!!!! VideoIn texture handle is NULL!" 
• DSOF-22201 Matrox: Tearing seen on capture inputs 
• DSOF-22204 "Matrox: Card incorrectly configured" error seen in Designer when opening a new project
• DSOF-22435 'Unable to create Matrox video input' error when assigning video input

• DSOF-21825 -  Fixed an issue where using a 1D Lut produces an error
• DSOF-22265 - Fixed understudy misreporting timecode as being out of sync with director
• DSOF-22278 - Fixed Renderstream compressed not working on vx4 or vx4+
• DSOF-22301 - Fixed an issue where Renderstream texture parameters were proxied
• DSOF-22345 - Fixed an issue where diagnostic zip files failed to be generated due to locked file
• DSOF-22346 - Fixed an issue where d3 could hang when aborting colour calibration

• DSOF-22220 - Fixed an issue where the frame lock icon in actor status widget was reporting no frame lock
• DSOF-22219 - Fixed an issue where enableGuiFeed option switch resulted in a black feed in feed view.
• DSOF-22016 - Fixed an issue where FrameLatency did not change when switching from Full Speed to Full Speed Low Latency on nvidia machines
• DSOF-20735 - Fixed an issue where Reference Point labels were offset incorrectly in the Visualiser Camera

• DSOF-22180 - Fixed an issue where the failover test channel with an offset of 0 in DMX event transport potentially causes understudy to hang on failover
• DSOF-21837 - Fixed an issue where vx4s fails to apply feeds at 60, reverts to 59.94
• DSOF-21673 - Fixed an issue where the remote profiler failed to take profiles between different machines in the office

• DSOF-22078 - Fixed an issue where Actors were not in sync with Understudy after failover command
• DSOF-21804 - instantaneousModeTime() now behaves like network time in all cases
• DSOF-21721 =- Matrox input now shows as hz, not fps
• DSOF-21713 'FieldAccessor' object has no attribute 'undecoratedName' displays when showing and hiding columns in the projector multi-selects menu
• DSOF-20978 SLC: Fixed multiple errors with invalid frames calculated and outFrames out of bounds when configuring asset regions
• DSOF-20208 - Fixed an issue where the Understudy's timecode was out of sync with Director's timecode

• DSOF-22003 Fixed exception on shutdown that could lead to loss of data on shutdown in rare cases
• DSOF-21957 Fixed an issue where disguise cloud would sometimes fail to log in for certain network configurations
• DSOF-21550 Creating new multiview subregion no longer causes an access violation
• DSOF-21928 Fixed an issue that would cause incoming automation data to glitch when failing over to an understudy.
• DSOF-21926 Folders now correctly appear again  in the media selection object view
• DSOF-21813 GPU profiler monitor now appears correctly again in remote monitors list
• DSOF-21803 Fixed an issue where the Media ingestion history window would make columns disappear if you had text with very long file names.
• DSOF-21788 Text Layer no longer fails to render sometimes upon project restart
• DSOF-21747 Scaling down an output rectangle beyond a certain size no longer makes the preview turn black.
• DSOF-21740 Fixed an issue where Ncam k1 and k2 values when taken from the ncam system by setting the ncam system to send these values directly were the wrong scale.

Matrox Capture Card fixes

• DSOF-21743 Warning notification for Matrox SDK & driver mismatch has been improved. This notification will now only be visible on machines that actually have Matrox hardware installed.
• DSOF-21681 Fixed issue where a Matrox capture card could occasionally fail to create a system topology for specific inputs. Should improve stability of Matrox capture cards when receiving intermittent video signals.
• DSOF-21626 Fixed issue where after project restart on machines including Matrox video inputs could under certain conditions show up black and need to be remapped.
• DSOF-21605 Added support for capturing following Psf formats that were missing on Matrox capture cards:
  • 1080sf 23.98, 
  • 1080sf24, 
  • 1080p47.95 and 
  • 1080p48
• DSOF-21477 - Fixed an issue where noisy signals could cause flashes to black on Matrox input cards with “free running/locked” change notifications. For users that need genlock sync, we have added a ‘matroxInputClockEnabled’ option switch. Having it ON forces the capture card to only use the first connected SDI input as a genlock clock source. Having it OFF defaults the capture card to use its internal clock and not an external one.
• DSOF-21394 - Matrox cards will no longer consume excess memory leading to a machine blue-screen on d3 project close.
  • IMPORTANT NOTE: This issue was related to supporting VITC (Video Timecode) processing on Matrox cards. To resolve it we have disabled VITC by default on machines with Matrox cards. If you want to re-enable it you can find a special option switch you will need to enabled under advanced machine settings called: matroxVITCEnabled

• DSOF-21941 - Fixed an issue where the close button in the cloud authorization popup was misaligned, mostly obscured
• DSOF-21940 - Fixed an issue where the first time sign in banner text can be selected and copied
• DSOF-21936 - Fixed an issue where the first-time login banner in d3manager was too long for the default size of the window, obscuring the hyperlink at the end
• DSOF-21929 - Fixed an issue where d3manager sign-in button stopped working if the sign in page was closed
• DSOF-21927 - Fixed No Data in Feeds - Scopes
• DSOF-21923 - Fixed an issue where the cloud icon did not appear, and was cropped
• DSOF-21870 - Fixed an issue where SLC showed errors with a minimal project
• DSOF-21853 - Fixed an issue where CallStack objects allocated large amounts of stack memory and run a high risk of causing a stack overflow
• DSOF-21846 - Fixed an issue where Unused medias aren't detected when starting new actor&machine project
• DSOF-21844 - RenderStream: Fixed an issue where the alpha channel rendered white when enabled on AMD machines
• DSOF-21830 - Fixed an issue where editor machine was not locating cue on re-engage to director - when using multi transport manager
• DSOF-21794 - Fixed Cam Lens data showing "-nan(ind)" when using MosysF4 protocol but not turning on "F4Lens" switch in Mo-sys.
• DSOF-21759 - Distribute: Fixed an issue where missing Media Domain didn't remove media when a video file changes
• DSOF-21744 - Fixed an issue where zooming out using proxies has no effect
• DSOF-21730 - Fixed an Access Violation when rendering bitmap module in ACES mode while no texture is mapped
• DSOF-21725 XR: Fixed an issue where a stall / minor hang happened at end of Colour Calibration
• DSOF-21485 - Fixed FrameLatency not changing when switching from Full Speed to Full Speed Low Latency
• DSOF-21481 - Fixed an issue where AnimateCameraPreset layer blocked movement for Virtual Cameras when using Relative
• DSOF-20995 - Fixed CUE list editor not resizing to the right correctly
• DSOF-20975 SLC: - Fixed an issue where opening the preview separator in the VideoRegionSet widget before any regions are set caused an error
• DSOF-21935 - Updated the popup when attempting to run a d3 project without a licence to point users toward the cloud licence flow

• disguise Cloud Integration

Designer r22.1 offers login to disguise Cloud through d3manager by clicking on the new “Sign In” button (circled red in the screenshot).

On sign in, you will be prompted to link your machine to your disguise Cloud account by following the on screen instructions. You can link your Designer install to an existing disguise Cloud account, or sign up for a new account.

If your Designer is not licensed, you will be able to acquire a Designer license via the Designer integration with disguise Cloud.

You can return to licence activation by clicking “Account” in the d3manager cloud menu. This will take you to your disguise Cloud account details page which includes Designer license activation functionality.

Further disguise Cloud integrated functionality in Designer will be rolled out over the coming months.

Please note:

The launch of r22 has also coincided with OS 200, both of which are major updates to disguise. The OS includes significant updates for a host of drivers to support the new features in r22, so if you currently own a disguise vx 1, vx 2, vx 4 or vx 4+, please make sure to download the latest OS upgrades for these machines from the Hardware section of our software download page to ensure their compatibility with r22 and future releases.

It is important to note that a project built in r22 will need to have the hardware specified for playback with an OS above 200. Once the hardware is updated to support OS 200 and above, there is no option to roll back to a previous OS version. Please follow this link for the advisory.

Single Large Canvas (SLC) - DSOF-13257, DSOF-12450, DSOF-12958

A Single Large Canvas (SLC) is a practically unlimited canvas that users can operate on without having to manually split canvases (i.e. the displays and mappings) or concern for the mechanics and logic of distributing content over multiple machines or for performance. SLC allows users to focus on the creative side without concern for the practical limitations of large scale projects.

Previously a show going from a small venue with HD screens to a large venue with massive screens had to work around GPU limits - like the max internal resolution of 16384x16384 pixels of GPUs - and manually split content across machines so the increased resolution wouldn’t affect performance.

SLC removes these limitations and allows you to operate on massive content as if it was a single large piece of content, while only processing the content that is being output by each individual machine in the session.

SLC works in conjunction with the Media Distribution feature to make working with video at massive resolutions practical.

If you have a show where SLC might be a required feature then we’d love to work with you. Please contact us at support@disguise.one.

How-To

The new logic is always enabled, but the SLC configuration is hidden and limited to non-SLC resolutions until explicitly enabled.

1. Tick the “enableSLC” option switch in advanced project settings a. The SLC config is now visible under d3->Advanced->SLC configuration b. SLC-aware display types (currently projection surfaces and LED screens) now have their default min/max set to 100,000x100,000 instead of 16384x16384.

2. Create a display larger than 16384x16384 or reduce the “Resolution threshold” in the SLC configuration to enable SLC splitting for that display.

3. Create SLC video content

a. Split video content into regions smaller than 16384x16384 (most codecs only support 8K) and include a region name into each split in the format “_region<region name>” b. Ingest the content and specify the regions inside d3 under <video clip>->Video asset->Regions

Usage notes:
● SLC currently only supports projection surfaces and LED screens. Other displays are still limited to 16k.
● SLC does not currently integrate with any other content than video.
● We have also enabled SLC to be combined with mesh projection in order to split large canvases across multiple machines.

Media Distribution - DSOF-11971

The new Media Distribution feature provides a built-in mechanism to easily ensure that the exact required media files are present on each d3 machine involved in a d3 session. There are two parts to the Distribute system:

1. Sync/copy missing media - copying media used by the d3 project and needed by a machine’s feed mapping.

2. Delete unused media - removing media that is not used by the d3 project.

The power of the Media Distribution feature is its utilisation of the project state for all machines in the session, only distributing video layer media to a machine in the session if the media is mapped to one or more outputs on the machine. e.g. Adding media to a video layer in itself will not make it a candidate media to be distributed to a machine unless the media has been mapped to an output on that machine in the Feed view.

Media Distribution applies to all media types in the d3 project objects folder.

Note that in r22.0, there is no option to use Media Distribution to delete unused media from the Director in case media is later required. We are interested in user feedback as to whether including the Director (or giving the option) would be a useful addition.

Listing missing media and initiating media syncing is also available in r22.0 via a REST HTTP API. Listing unused media and deleting unused media will be available via a REST HTTP API in a subsequent release.

To use the Media Distribution feature

1. On the Director machine, right-click on the d3 menu and select “Media Distribution…” to open the Media Distribution Widget.

2. Expand both collapsible widgets to see the details of what media files are missing and unused copies.

3. “Include Mobile Editors” is defaulted OFF as they may wish to manage their own files, but the option is available.

4. Either click on “Sync” or “Delete” next to each item to sync or delete individual files on the target machines, or alternatively click “Sync All” or “Delete All” to action all the items in the respective tables.
a. For copying large files, it will display the copy progress as a percentage.
b. At the end of a copy, it will display the task state as either “Success” or “Failed”. For delete, the item should just disappear from the table.

5. Click on “Clear Finished Tasks” above the sync table to remove syncs that completed successfully and reset the status on syncs that failed.

The Media Distribution feature has several planned improvements which are not included in r22.0 but planned for upcoming releases:
● Sync and delete tasks by Media Distribution can only be triggered by the Director. Enabling Media Distribution from Editors is planned.
● Password-protected sharing must be turned off for all machines in the network for remote copying and deleting to work. This is the default configuration for disguise servers but may need to be configured for Editors working on non-disguise PCs or laptops. The requirement for this configuration is planned to be removed.
● Syncing of proxies to be included in the distribution feature.
● Performance improvements including:
○ Distribution from one actor to another is routed via the director. This limitation will be removed.
○ Sync and delete is executed over d3net. In a subsequent release, it will be possible to execute media distribution over alternative network adapters.

RenderStream 1.30

RenderStream 1.30 brings us a host of new features including:

● DSOF-20552 RenderStream: backwards compatibility

We have included built-in backwards compatibility into RenderStream to enable third-party applications to still run effectively if the RenderStream API is updated.

● DSOF-20485 RenderStream: API to release image references

● DSOF-19997 Display UE engine version in the Asset

RenderStream assets now show which graphics engine is being used, in addition to the version of that particular graphics engine. On a RenderStream asset, this is now shown in the Engine Name and Engine version fields as seen in the image below.

● DSOF-18049 RenderStream: Vulkan API

We have enabled integration of the Vulkan API, which allows for easier integration of RenderStream into applications powered by Vulcan. This also means that applications built with Vulkan can now be used as both compressed and uncompressed RenderStream assets.

● DSOF-14835 RenderStream: custom asset description/readme

RenderStream assets now have an “Info” field which is filled in from data provided by the graphics engine that is being used.

● DSOF-16148 Fast Spatial Calibration

We have reduced spatial calibration time to less than half the amount taken in previous software releases. For studios with multiple cameras for example, this can result in a time saving of several hours. The Fast Spatial Calibration is enabled by default.

● DSOF-21620 Update missing media API for r22

In r21.4 we removed the missing media API, but this has now been replaced. API documentation can be found either via ‘Open API documentation’ under the ‘help’ section of d3manager, or by accessing http://localhost/docs/v1/index.html on a disguise media server.

● DSOF-21574 Education license should allow 4 VideoIn channels (not just 1)

In previous releases, the education license for Designer only allowed for 1 video capture channel. In r22 we have enabled 4, the same as currently found in standard Designer licenses.

● DSOF-21026 RenderStream: allow pinning of Receive Health widget

We have enabled the Receive Health widget to be pinned when using RenderStream, so that users can see the health status of all RenderStream during a show.

● DSOF-20740 Trigger UE events from d3

In r22 we have enabled support for Unreal Engine events to be triggered from within Designer using the ‘Custom Events’ tab when running RenderStream. This is populated when users add custom events on their level blueprint within Unreal Engine. Custom events can then be exposed as keyframable sequences that can be triggered from the timeline within Designer.

● DSOF-5762 Ability to add a global delay to Audio

We have added a ‘Delay’ field within the editor of each AudioOutPatch resource to support audio teams from having to add delay on their side and be able to accommodate for video latency within the production chain without having to add any further delay. The delay is set to 0 by default, and any delay specified is applied to all audio that is being output on the patch. The delay is applied across all machines within a d3Net session. This will not effect external audio engines like Web, Notch and RenderStream.

● DSOF-21331 Hide live action position marker in Camera when not using old virtual camera workflow

We have hidden the ‘live action position marker’ field in the camera behind the ‘enableLegacyVirtualCameraWorkflow’ option switch. The reason for this is that most of this work is completed within VirtualCameras.

● DSOF-21242 Skip drawing of Point Cloud grid on an Omnical project if max line length is 0

We have made an improvement to Omnical workflows in r22. In previous releases, the ‘Point Cloud max line length’ is only checked before drawing individual lines between point neighbours. This would mean that grid points would need to be drawn even if the threshold is set to 0. We have removed this step in r22, meaning that if the threshold is set to 0 then no lines need to be drawn between the grid points.

● DSOF-21208 Layers that do not exist on a track don't say so in their descriptions

In previous releases, the description of a layer tells users where it is on a timeline, but if it was not on a timeline then it’s either in the list of saved layers or in a layer stack. This could cause confusion to a user when attempting to remove missing media if it was in use in a layer that isn’t on their track, especially if a layer had been exported or removed from a track a long time ago.
In r22 we have added additional logging to a layer to highlight to users where it is located.

● DSOF-21178 Warn user when insufficient overscan used

When using overscan for lenses in a xR workflow, we have enabled a warning to users when the overscan is not sufficient by giving the overscan field a red background, and adding the minimum required overscan values into the overscan tooltip.
● DSOF-21073 Virtual camera: Use live action marker at (0, 0, 0) as default when none selected

In previous releases, when no live action position marker is selected within the Virtual Camera, a reprojection is completed at a constant distance of 3 metres. In r22 we have amended the default distance of a live action position market at (0, 0, 0).

● DSOF-21164 Manual Observations have uninitialised RMS Error field

We have adjusted the Manual Spatial Calibration observation so that its RMS Error field should report as 0.

● DSOF-21088 Make default videoclip input transform utility-sRGB in ACES

In ACES mode, we have enabled the default Input Transform value of every VideoClip resource as being set to ‘sRGB - ITU-R BT.709’

● DSOF-21041 HTTPcontrol module should support HTTP PATCH commands

In r22 we have enabled support for HTTP Patch within the HTTPcontrol module to support integration with partner APIs.

● DSOF-20938 Allow multi-layer editing of multiple group layers or group layers mixed with normal layers

We have enabled a multi-edit layer window, enabling users to select multiple group layers with any number of layers and multi-edit any of them. In previous releases, we only supported the ability to multi-edit a single group layer.
If a single group layer is selected, it will be titled as “Group <Name of Group> of N Layers”, but a multi-select of multiple groups will not include the group names.

● DSOF-20868 Replace reset keyframe icon with a dedicated icon

● DSOF-20807 Add the ability to filter RenderStream assets by source machine to the ResourceView
We have added check boxes in the ResourceView to make it easier to filter specific machine assets as part of the RenderStream workload.

● DSOF-20794 Separate set extension and LED backplates

In r22 we have made it possible in xR workflows to separate the rendering of the backplate into two separate plates - content that goes to the LED screens, and content that goes to the set extension. We have therefore implemented two new render layer options - ‘Back Plate Screens’, and ‘Back Plate Set Extension’.

● DSOF-20782 String Expressions - enable carriage returns

In r21.1 we added a text module which enables users to make a text layer. This can be used to add notes to an output for a rehearsal for example. Fonts can then be downloaded into objects/textfonts as a .ttf file.
Taking this further with Expressions, right-click on the property you want to control within the Text Module. In r22 we have enabled the ability to add a carriage return - used to reset to the beginning of a line of text - into the string. This can be completed by splitting the expression across multiple lines in the input by hitting the enter key as normal as seen below:

● DSOF-20731 Report and adjust RenderStream projects folder path inside d3

In previous releases, the only way to adjust the RenderStream Projects Folder - located in the RenderStreamMachine editor - was via manually editing the machine registry.
In r22, the RenderStream Projects folder is where the current folder path is reported, which is when it appears on the remote machine. When providing a new folder path, it should be the same path reported on the remote machine and should also be going to an existing folder.
In order to do this, d3service must be running on the remote machine with admin privileges, as would be the case when using vx machines alongside rx render nodes for example.
If d3 service is not running with admin privileges, everything will succeed except the creation of a network share for the folder. If this fails, users would need to ensure that d3service is running with admin privileges to complete the step again.
If the folder path provided does not exist on the remote machine, no change will occur.

● DSOF-20700 d3manager: ability to compare two project files

In d3manager, we have added the ability to compare two project files. This can be completed by going to Projects / right-click on project/Show History. Right-click on the history file and click on the ‘Compare to existing’’ option to open a new window to display the current project file alongside the selected history file.

● DSOF-20664 d3manager: rollback functionality

In d3manager, we have added the ability to rollback a project. This can be completed by going to Projects / right-click on project/Show History. Double-click on the history file to receive a confirmation of rollback dialogue. Right-click on the history file and click on the ‘Rollback’ option.
Rolling back a project will replace the current project file with the selected history file, which will be renamed to match the name of the current file. The ‘Date Modified’ will automatically update according to the selected history file. If an overwrite happens, users will see a backup name
<show>rollback<date> appear in the history folder.

In r22 we have enabled

● DSOF-20662 ObjectView: improve subfolder hierarchy UI

In previous releases, when in ObjectView users see a hierarchy of boxes and folders when there are objects in each subfolder. In r22 we have made it clearer that it’s a tree view as seen in the new view below:

● DSOF-20597 RenderStream: use the full asset path

In r22 we have enabled RenderStream assets to use the full asset path within its naming instead of the last directory to avoid assets being overwritten.

● DSOF-20540 VideoClip: ability to preview clip without a layer

Within the GUI, we have enabled users to preview a video without creating a layer in r22. In the VideoClip widget, click on ‘edit video clip / Preview’. The widget also has a ‘Frame’ field that can be used to jump between each frame of the content.

● DSOF-20514 d3manager: dark mode

Dark mode in d3manager is now enabled in r22. Users can change between dark and light modes when selected within the Windows Colours settings.

● DSOF-20482 Add workload-friendly name to RenderStream asset editor

We have added the workload name to the stream editor (located in the Stream widget when starting a RenderStream workload) so that it’s possible to see which stream is related to which workload. In previous releases there was no way of seeing this information.

● DSOF-20320 d3preview: standalone application for previewing files/videoclips

In r22 we have created a simple standalone application called d3preview. This enables users to check whether Designer will support playback of that content, without having to ingest it into a temporary project. This can be completed by right-clicking on any file that Designer supports / Open with / Choose another app /C:\Program Files\d3 Production Suite\build\msvc\d3preview.exe.
We have created a dedicated UI that includes the ability to play/pause/scrub the content via the mouse and spacebar, volume via the mouse wheel and the ability to change scaling/clipping. Users can also use multiple instances of d3preview.

● DSOF-20389 Installer: option to associate supported image/video extensions with d3preview

For d3preview, we have enabled users to preview files in a host of media file formats including
.d/.dpx/.exr/.mov/.tga/hap. To enable this feature, in the Installation Options of d3installer, we have included an option to ‘Associate media files with d3preview’.
When this is enabled, any file with an extension of .d/.dpx/.exr/.mov/.tga/hap will have an option to open with d3preview within its ‘Open with’ action menu.

● DSOF-19737 CDL API (LiveGrade integration)

We have enabled a REST HTTP API in order to receive CDLs into disguise. This is needed in order to integrate with Pomfort LiveGrade. API documentation can be found either via ‘Open API documentation’ under the ‘help’ section of d3manager, or by accessing http://localhost/docs/v1/index.html on a disguise media server.

● DSOF-18892 Upgrade Rivermax to 1.10.20

We have upgraded Rivermax to 1.10.20, which contains performance improvements and Windows GPUDirect support.

● DSOF-9876 Show project version in d3manager

In r22 in the Project view within d3manager we have included an additional column titled ‘d3 Version’ that displays the d3 version each project file was last modified in.

● DSOF-8922 Ability to specify number of proxy levels generated per file

In r22 we have enabled a ‘Settings’ feature within the Proxy Maker widget to enable users to dictate what proxies are needed and how many. We have enabled options to select each available proxy level, which are then generated at the specified levels. The ‘Rescan’ button is then used to rescan internal proxies and determine which need to be created based on the selection.

● DSOF-6784 Ability to reset limits/delete MetaField

In r22 we have included a ‘Reset’ button within each MetaField widget. This button becomes active if any of the fields within the widget are not equal to their default values. Clicking the button will then restore all fields within the widget to their default values. In previous releases, users would have to type in the expected or remembered values.

● DSOF-3941 Ability to reset keyframes to default values

In r22 we have enabled the ability to reset keyframes to default values. This can be used by clicking on the icon located to the right of all keyframable fields across all modules. The reset keyframe button is only active when the field value does not match its default value at the current playhead position.
Selecting the reset keyframe button should reset the field back to its default value at the current playhead position, and should not affect any keyframes not at the current playhead position.

● DSOF-995 WebModule: Control over audio

In r22 we have created an ‘Audio’ toggle located within the editor of each WebBookmark resource. The value of this field will be set to True by default, which means that any content presented by the WebBookmark resource that contains audio will be heard.

If the toggle is set to False by default, any content presented by the WebBookmark resource that contains audio will not be heard.

• DSOF-21624 - Fixed a Rivermax driver mismatch
• DSOF-21608 - All languages no longer load when running d3 with "isDeveloper" set
• DSOF-21588 - Fixed an issue where ActorStatusWidget did not open when RS layers are present
• DSOF-21579 - XR: Fixed a potential hang when running Colour Calibration on non-dedicated Director
• DSOF-21576 - Fixed an issue where deleting unused media didnn't work for image sequences
• DSOF-21567 - Fixed an error in RenderStreamMachine when ClusterPool with 1+ machine assigned and session is active
• DSOF-21566 - Fixed an issue where Setting Director always requested a project restart
• DSOF-21556 - Fixed an issue where - 0 missing media was reported when using same media repeatedly
• DSOF-21555 - Fixed an issue where Mapped Media Domain was not returning all mapped media locations correctly
• DSOF-21538 - RenderStream: Fixed an issue where pool incorrectly reported asset is out of sync
• DSOF-21534 - RenderStream: Fixed a potential can hang when stopping a workload
• DSOF-21533 - Fixed an issue where it was not possible to export OmniCal camera study
• DSOF-21508 - Fixed an issue where rotating a camera in visualizer caused d3 to run extremely slowly
• DSOF-21503 - Fixed a hang on startup if a project has webmodule
• DSOF-21502 - Fixed an exception in Layer Stack
• DSOF-21501 - Fixed an issue where unmapping multiple media files consecutively didn't update the UnusedMediaDomain correctly
• DSOF-21498 - APIEventTransport is now hidden in the UI
• DSOF-21495 - Fixed 'invalid vector subscript' error when using sample RenderStream assets
• DSOF-21494 - Fixed an issue where Horizontal Back and Front Plates caused issues with mapping resolution
• DSOF-21493 - Fixed an issue where SceneOrigin could have its Scale modified through 3D manipulators
• DSOF-21473 - Fixed RenderStream returning invalid scene index
• DSOF-21471 - Fixed an issue where CodeMeter error message ended with a single NUL character
• DSOF-21470 - Fixed Media Distribution Widget saying >1 of the same media is missing
• DSOF-21463 - Fixed a Python exception when changing machine type in d3Net widget to a machine that does not support 10bit
• DSOF-21461 - Fixed Export Projector Study
• DSOF-21456 - Fixed an issue where Directional Lighting created CPU Lock error
• DSOF-21453 - Fixed an issue where DMXPersonality was no longer scrollable
• DSOF-21449 - Fixed an invalid memory access from ManipController on shutdown
• DSOF-21445 - Fixed an issue where SlcRegionManagement::update used reference to map element after it is erased
• DSOF-21443 - Fixed an issue where the OBJReader file buffer wasn't null terminated causing line reading to read uninitialised memory
• DSOF-21406 - Fixed AnimateObjectPreset: error in ScreenConfigurationEditor when adding objects to a ScreenConfiguration
• DSOF-21401 - RenderStream: Fixed scene tab in RS layer mentioning INVALID
• DSOF-21399 - RenderStream: Fixed an issue where Receive Health displayed wrong amount of frames when on Automatic preferred network
• DSOF-21383 - Mesh Projection: Fixed an issue where it was possible to create and add a Projector to your Mesh mapping through the Mesh Mapping widget
• DSOF-21372 - Fixed an Access Violation when adding a point to a Rigid Body Tracking Source
• DSOF-21371 - Mesh Projection: Fixed an issue where changing the res of a display did not change the Bandwidth estimate
• DSOF-21366 - Fixed SharedLibLoader setting an error code if DLL load succeeds
• DSOF-21353 - Added the same EventTransportMSC to both Remote & Local displays a MulticastDelegate error
• DSOF-21352 - Fixed an issue where OSC indirection controllers notify too verbosely when a string is a mis-match
• DSOF-21344 - Fixed an issue where the master volume control did not work with legacy video layers
• DSOF-21342- Fixed an issue where the Media Distribution Widget does not update if cache is different - but cache size is the same
• DSOF-21330 - Fixed an issue where Missing Media Domain reported unused versions of video files as missing
• DSOF-21316 - Fixed an issue where adding objects to an Omnical Plan within a session displays a 'multicastDelegate' error
• DSOF-21312 - Fixed an issue where opening and closing the d3net manager widget within a session displayed a 'multicastDelegate' error
• DSOF-21308 - Fixed Failed RmaxVideoIn instances polluting pool
• DSOF-21298 - Fixed unused Media Domain displaying files that are still in use
• DSOF-21275 - PureLinkMatrix: Fixed a possible access to freed memory in Callback
• DSOF-21270 - Fixed TrackTransitionInfo serialising 'size_t' member (i.e. architecture-dependent size)
• DSOF-21266 - Fixed an issue where edits to layers within layer stacks are not guaranteed to be serialized
• DSOF-21262 - ColourCal: Fixed an issue where the CameraData move-constructor moved camera from itself
• DSOF-21246 - Fixed an issue with Cue Tag selection inaccuracy depending on level of zoom on timeline
• DSOF-21245 - Fixed an issue where mesh projection rendered Notch content at 1x1 px resolution
• DSOF-21230 - Reinstated support for query strings in generated gRPC HTTP routers
• DSOF-21228 - Fixed an issue where opening an Omnical camera widget displayed a 'NoneType' error
• DSOF-21194 - Fixed the VideoTrigger layer
• DSOF-21138 - Improved the RenderStream asset object picker
• DSOF-21136 - Fixed an issue where apostrophes passed into the text module via an expression break rendering
• DSOF-21135 Text Module - Fixed an issue where incomplete expressions on text parameter result in strobing content
• DSOF-21132 Text module - Fixed an issue where alignment breaks when font size exceeds available space on the mapping
• DSOF-21126 - Fixed an "Incorrect shutdown" warning about AssetLauncher channels, when Comms object is destructed
• DSOF-21122 - Fixed an error when keywidget was on focus after resource selection widget is closed
• DSOF-21114 - Fixed an issue where the console cursor offsets vertically as new input lines were added
• DSOF-21107 - Notch blocks no longer create duplicate exposed parameters
• DSOF-21098 - Fixed an issue where the queue of "Apply Feed Settings" and "Apply Genlock" commands caused issue in d3service
• DSOF-21092 - Fixed an issue where d3 stayed on a black screen after resetting EDIDs on a machine following Applying Feed Settings
• DSOF-21090 - Fixed an Invalid Aspect Ratio Console Message
• DSOF-21056 - Fixed an issue where tint did not apply to the VideoTrigger layer
• DSOF-21043 - Fixed an error calling 'pDXGIAdapter3->QueryVideoMemoryInfo' when running d3 on a VM
• DSOF-21042 - Http Response code for NotFound exception is wrong
• DSOF-21034 - Fixed an issue when managed workload is on, any new RenderStream layer would cause an Access Violation
• DSOF-21009 - Fixed a write error when attempting to save d3 with Colour Calibration widget pinned
• DSOF-21005 - Fixed an OmniCal access violation on d3 startup with pinned simulated camera
• DSOF-20999 - Fixed an issue where d3service would should down uncleanly
• DSOF-20996 - Fixed an issue where creating a new setlist or changing a setlist would display a convert error
• DSOF-20959 - Fixed an issue where changing padding while the Cluster Workload widget it's open throws an exception.
• DSOF-20904 - Fixed Undo+redo+undo triggering MulticastDelegate: duplicate add
• DSOF-20903 - Fixed an issue where resetting keyframe wasn't undoable
• DSOF-20902 - Fixed an issue where opening an Omnical camera widget or the capture widget displays a Mulicastdelegate error
• DSOF-20894 - Fixed puffersphere warp layer being impossible to access
• DSOF-20889- Fixed an issue where changing EXT refresh rate on blackmagic sync gen sometimes didn't change on D3 unless user do a cold boot
• DSOF-20887 - Fixed Colour Workflow not being in :  sockpuppetvideomodule
• DSOF-20861 - Fixed DX11 test app getting stuck on "starting..."
• DSOF-20855 - Fixed an issue where Video Trigger Layer could not arrow into Notch Block
• DSOF-20835 - Fixed an issue whereAnimate Object Pre-set was affected by fade on section
• DSOF-20822 - RenderStream: Fixed "invalid map<K,T> key" error after changing "Scene" while running workload
• DSOF-20810 - Fixed an issue where opening the Audio Output Patch editor displays a MulticastDelegate notification
• DSOF-20808 - Fixed an issue where using audio delay doesn't stop audio when the timeline has stopped
• DSOF-20776 - Package: Fixed an issue where trials could modify a project on disk
• DSOF-20775 d3manager: Fixed an Access Violation in Display::activate when clearing ingestion history
• DSOF-20774 - Fixed the auto-save reporting the wrong d3 version
• DSOF-20758 - Fixed an issue where a video file with long a name as new placeholder clip causes input patch editor quick view to crop its width
• DSOF-20715 - CUDA binaries now built for all supported platforms
• DSOF-20714 - RenderStream UI: Fixed an issue where clicking on "Details" button didn't open monitor and shows error
• DSOF-20711 AudioSystem: Fixed a hang and CTD on project launch
• DSOF-20678 Package: Fixed an issue where there was no way to open read-only
• DSOF-20627 - Fixed a d3service offline error on launch despite d3service running
• DSOF-20625 - Fixed an error when opening widget for WebCommandKeyboard resource
• DSOF-20623 - Fixed web layer not working when chromium cache from previous version exists
• DSOF-20602 - AssetLauncher: Fixed custom extensions being broken
• DSOF-20527 - Fixed an issue where the feed output shifted 1px to the left when setting SMPTE timing
• DSOF-20525 - RecordingSystem: Fixed an issue where onAppStarted was called before project loads
• DSOF-20517 - Fixed an issue where users needed to do a cold boot to change between static and dynamic
• DSOF-20489 - Fixed an issue where uninitialised data passed to CUDA 
• DSOF-20463 - Fixed an issue where turning a single version of a video asset off causes all versions to be turned off when EnableSmartGroups option switch is set
• DSOF-20440 - Fixed an issue where RenderStream streams intermittently did not work
• DSOF-20394 - Fixed an issue where translator/locale used/loaded too early
• DSOF-20358 - Fixed an issue where Layer Search sometimes filtered out valid matches
• DSOF-20347 - Fixed an issue where clicking on frame replay OFF/ON created output in the widget.
• DSOF-20346 - RenderStream: Added better error reporting for RenderStream::Core::getImageFrameParameter
• DSOF-20175 - Fixed an issue where DMX surfaces were incorrectly highlighted in red on the stage
• DSOF-20107 - Mesh Rendering - Fixed an issue where mesh mapping allowed Projectors as a target
• DSOF-20105 - Fixed an issue where Play Head Prefetch Loses prefetch key time: []
• DSOF-20079 - Fixed an issue where Virtual lineup layer does not work when a live camera is used
• DSOF-20076 - Fixed an Invalid map<K, T> key error when mapping a video layer to an MR set via backplate
• DSOF-20062 - Fixed an issue where feed mapping mirror flip buttons caused the whole rectangle to turn black
• DSOF-20052 - Fixed an issue where holding the output of a single projector while Dynamic Blend is enabled froze the GUI and made every other output turn black
• DSOF-20050 - Added NatNet Protocol Improvements for Optitrack
• DSOF-20029 - Fixed an issue where precomps did not work
• DSOF-19950 - Fixed an issue where scrubbing through the timeline while paused causes video layers to flicker black
• DSOF-19948 - Fixed an Access Violation when changing surface type
• DSOF-19778 - Fixed an issue where d3 could be launched without d3service running and no notification wwas provided
• DSOF-19643 - Fixed LTC disengage / re-engage on editor machines on network
• DSOF-19627 - Fixed an issue where list editors field sorting did not work for custom columns without a comparator
• DSOF-19616 - Fixed exposure and gamma controls on RenderStream asset
• DSOF-19583 - Widget::subscribeAction no longer used in populate
• DSOF-19344 - OmniCal: Fixed an issue where iIf a calibration had too many outliers, d3 would hang
• DSOF-19127- SimpleHelp.exe no longer uses port 80, blocking d3 from creating a HTTPContext
• DSOF-18814 - Help menu search field is now case insensitive
• DSOF-18185 - Fixed an issue where 16-bit EXR was loaded as 32 bits per channel
• DSOF-16571 - Fixed an issue adding new Scenes to RenderStream asset causes previously keyframed scenes to offset
• DSOF-15428 - Fixed an issue where RenderStream was unable to be used by packaged/cooked UE projects
• DSOF-12656 - Sockpuppet video module: Scale.x and scale.y parameters keep the same range as the regular video moduleDSOF-21675 - GPGPU now prevents the system from attempting to interop when presenting
• DSOF-21642 - Fixed an issue where the camera perspective map generated 2nd view of the frustum upside-down out from the back like a pin hole cam
• DSOF-21534 RenderStream: Fixed an issue where d3 could hang when stopping a workload
• DSOF-21533 - Fixed an issue where it was not possible to export omnical camera study
• DSOF-21520 - Fixed an issue where d3 could not export camera views
• DSOF-21461 - Fixed Export Projector Study not working
• DSOF-21365 - Fixed an Access violation in CEF causing crash to desktop when using Text layer or Web Layer

Please note:

The launch of r22 has also coincided with OS 200, both of which are major updates to disguise. The OS includes significant updates for a host of drivers to support the new features in r22, so if you currently own a disguise vx 1, vx 2, vx 4 or vx 4+, please make sure to download the latest OS upgrades for these machines from the Hardware section of our software download page to ensure their compatibility with r22 and future releases.

It is important to note that a project built in r22 will need to have the hardware specified for playback with an OS above 200. Once the hardware is updated to support OS 200 and above, there is no option to roll back to a previous OS version. Please follow this link for the advisory.

• DSOF-21825 Fixed an issue where using a 1D Lut produces an error
• DSOF-22305 - Fixed an issue where setting the colour space of a colour profile to Rec.709 does not allow you to revert to default

• DSOF-22016 - Fixed an issue where FrameLatency did not change when switching from Full
  Speed to Full Speed Low Latency on nvidia machines
• DSOF-20995 - Fixed an issue where the CUE list editor didn't resize to the right correctly

• DSOF-21784 - Renderstream: Fixed an issue when there is a dmxlight with a fixture in a project, any RenderStream will hit "!!!!!fragment.streams.empty()"

• DSOF-22180 - Fixed an issue where the failover test channel with an offset of 0 in DMX event
  transport potentially causes understudy to hang on failover

• DSOF-21837 - Fixed an issue where vx4s fails to apply feeds at 60, reverts to 59.94

• DSOF-21673 - Fixed an issue where the remote profiler failed to take profiles between different
  machines

• DSOF-22078 - Fixed an issue where Actors were not in sync with Understudy after failover command
• DSOF-21804 - instantaneousModeTime() now behaves like network time in all cases
• DSOF-20208 - Fixed an issue where the Understudy's timecode was out of sync with the Director's timecode

• DSOF-16856 - Sony IDTs no longer appear wron
• DSOF-16841 - All LED Screens now have a hierarchy dropdown again
• DSOF-16834 - d3 trial build now starts properly
• DSOF-16811 - set extension and led LED walls no longer fall out of sync when AR fade is set to 0
• DSOF-16787 - d3service will no longer crash if empty/corrupted file ending in ".uproject" found in Renderstream Projects folder
• DSOF-16765 - Camera switching is no longer broken when frontplate is in minimal latency mode
• DSOF-16744 - rslogs folder is now correctly included in diagnostics
• DSOF-16734 - RenderStream Active Latency no longer causes excessive stuttering when not set to a multiple of the refresh rate
• DSOF-16703 - Mapping Quick Select slots no longer allow for non MultiChannel mappings to be applied on RenderStream layers

• DSOF-16674 - Renderstream workload actions (Start, Stop Sync) will now be greyed out when the corresponding operation is in progress.
  • The Sync button will grey out while there are running sync operations, on completion of all operations (success or failure) the button will no longer be greyed out
  • The Stop button will be greyed out when the workload is not running
  • The Start and Sync buttons will be greyed out when the workload is running
  • The Start button will be greyed out while there are running sync operations

• DSOF-21928 PSN data on failover is now handled correctly by the understudy
• DSOF-21730 Fixed access violation when rendering bitmap module in ACES mode while no texture is mapped

• DSOF-21830 - Fixed Editor machine not being located to cue on re-engage to director - when using multi transport manager
• DSOF-21647 - Fixed Editor machine not being located to cue on re-engage to director
• DSOF-21646 - Fixed an issue where pressing Interact on a web layer causes an Access Violation

• DSOF-21554 - Fixed an Access Violation with FMOD API

• DSOF-21580 - FMOD upgrade reinstatted

• DSOF-21532 - Fixed an issue where TextModule::m_vAlignment was uninitialised

• DSOF-21427 - Fixed an issue where machines that joined a session after it had started didn't listen to indirection changes

• DSOF-21426 - Fixed indirection state not persisting through project restarts

• DSOF-21341 - Corrected vx4+ Capture input labels

• DSOF-21318 - Fixed an issue where Animation and NotchLC videos with embedded audio not handling changes in clip fps

• DSOF-21309 - Improved the speed of the Prefetcher Report

• DSOF-21313 - Fixed instability in Solo machines with Bluefish capture cards

• DSOF-21507 - Fixed an Access Violation on startup when MR set exists in project

• DSOF-21499 - Fixed an issue where playing more than 8 layers of NotchLC or Quicktime Animation codec causes ctd

• DSOF-21478 - Fixed an issue where adding more than 8 Audio layers or assigning more than 8 channels in the audio output patch editor throws Exception Error notifications.

• DSOF-21369: Mesh Projection: Fixed an issue where eyepoints were split in the wrong way when a surface had bigger res than the Max Tile Size

• DSOF-21367 - Fixed a heap corruption causing crashes to desktop
• DSOF-21304 - RenderStream: Fixed an error starting workload via API when Actor controls rendering

• DSOF-21113- Fixed an issue where moving play-head to a specific frame didn't show layer content as expected

• DSOF-21112 - Fixed an issue where changing transport brightness or volume caused playback to go out of sync between machines

• DSOF-21107 - Fixed an issue where Notch blocks created duplicate exposed parameters

• DSOF-20856 - Fixed an issue where remote profiling does not copy the created JSON file

• DSOF-20763 - Fixed Access Violations when swapping source content in Placeholder Clip settings

DSOF-18115 Mesh projection mapping for Renderstream

The “Mesh” projection is a mapping which projects 3D content from an eye point onto the entire mesh of a screen. It is a perspective projection which automatically adjusts its rotation centre and field of view to match the extent of the mesh. It is particularly useful for large-canvas installations or out-of-frustum content in an XR setup.

The main advantages of mesh over perspective mappings are:

• The rotation and field of view automatically adjust to the mesh extent, making it easier to set up a projection encompassing a single screen
• When using Renderstream, the UV-space pixels are streamed, removing the additional bandwidth required to stream rendered pixels which get cut off when projected onto the mesh.

To set up a mesh projection:

• Create and set up a 3D content layer (e.g. a Notch or RenderStream layer).
• Create a new Mesh mapping and select this in the content layer.

• The mapping setup is complete, and we can see our content. An example of a RenderStream layer rendering a Notch block to the screen via a Mesh mapping:

To set up a dynamic eye point which moves around the stage:

It is possible to set up a dynamic, moving eye point rather than keeping the position fixed. There are various ways this can be done, including:

• Parent the mapping to any object in the stage to make the eye point follow that object (offset by the values specified in the eye point field)
• Add a camera to the list of screens for the mapping. Content will not render to the camera. However a new field will appear in the Mesh mapping editor below the eyepoint field called “Follow camera”. If this field is ticked, the eye point will follow the camera position.

• Similarly, an MR set can be added to the list of screens in the mapping. The mapping will then render to the screens of the MR set, and the eye point will follow the active camera of the MR set if “Follow camera” is ticked.

To split the content over multiple machines:

• For Renderstream layers, the content can be split across multiple render nodes as usual by adding multiple machines to the pool. The content for each screen in the mesh mapping will be rendered on a separate machine if available. If more render nodes are available than screens, the content will be split into fragments automatically to spread the load across machines.
• For other layers, the rendering load can be split across machines using “active screen regions” to define separate areas of each screen to render per machine.
• If active screen regions are used in combination with a Renderstream layer, machines will only subscribe to streams which are required for the active regions on that machine. For example, if you are rendering content to a screen with 4 rx and 4 vx machines, you can add the rx machines to the Renderstream pool to split the screen into 4 fragments and set corresponding active regions on the vx machines to receive one stream per machine. Be aware that setting overlap on the Renderstream layer may result in more streams being received per machine.

Scene Origin - DSOF-21037

A SceneOrigin can be used to modify the zero-point of a 3D scene. It represents an offset between the virtual world of the render engine and the real world represented in Designer. SceneOrigins can be shared between mappings, and can be saved and recalled as a way of managing scouted locations for different shots.

To create a SceneOrigin:

• Set up some 3D content with a supported 3D mapping (e.g. Spatial or Mesh)
• Create a new resource in the ‘Scene Origin’ field of the mapping

To modify the origin:

• Change the offset/rotation values to modify the location of the scene origin in d3 space
• Change the Engine offset/rotation values to modify the location of the scene origin in render engine space
• Attach a tracking source to make the origin follow a tracked object in Designer space
• Change the pose mode to change the method used to place the camera into the 3D scene:
  • Scene global: place the origin of the 3D scene within Designer’s stage, rotating around the scene origin
  • Scene local: place the origin of the 3D scene within Designer’s stage, rotating around the chosen location
  • Camera parent: place a virtual parent transform of the camera. Designer stage position has no meaning in this mode.

Tracking Marker Module - DSOF-20500

The tracking marker module generates a repeating pattern of markers on a coloured or transparent background. It is useful for virtual production workflows where some scenes require a green screen, either just within the camera frustum or on the whole of the LED screen. It can be used for both 2D and 3D mappings, and the markers will appear fixed to the screens in both cases.

To use the tracking marker module:

• Add a TrackingMarker layer to the timeline:
• Select the mapping:
  • To cover an entire screen or fixed portion with markers, choose a Direct mapping
  • To display markers within the camera frustum only, choose a CameraPlate or Spatial mapping
  • Other 2D or 3D mappings can also be selected for different workflows
• Change the marker image, size and spacing if required.
• Add a background colour if required. Note that the default is transparent, so alpha will need to be increased to see any colours.
• Use the cropping settings to apply the markers to only a portion of the screen or frustum. The numbers define the distance cropped from each edge, with 0 being no cropping, 0.5 being the middle of the image and 1 being the opposite side.

Improvements

• DSOF-20383 Persist feed view settings

When working in FeedView, we enable the option to change the layout of the feeds and machines. In previous releases, when Designer is restarted, the settings go back to their original state. The view settings in the feed are now stored after a restart.

• DSOF-20279 Ability to delete/rename files in file explorer while d3 is open

In the video file editor, we have added an “unlock” toggle option to enable users to remove or rename files on the disk, making it more straightforward to clean up old media files.

• DSOF-19845 Identification of Matrox or Deltacast capture card on d3manager dropdown

• DSOF-19830 Identification of Matrox or Deltacast capture card on vx OLED

• DSOF-19019 Support for TCD protocol for EzTrack lens data

We have enabled support for the TCD protocol from EzTrack to enable the delivery of intrinsic lens data to be used for green screen and AR workflows.

• DSOF-14079 API - implement Transport Control API

Transport controls are available via HTTP REST API. Details can be found in the OpenAPIdocumentation accessed from d3manager in Help -> Open API Documentation. Note that the d3 HTTP APIs will be unified, expanded and formally released in r22 as APIs version 2.

• DSOF-21134 Improve how generate_api_docs.py ignores temporary swagger files

• DSOF-21038 Remove the option to choose between relative and absolute time in strobe and radar modules

We have removed the option to choose between relative and absolute time in the strobe and radar modules, and have kept the option where the strobe timing was relative to the beginning of the layer.

• DSOF-20815 Enable Machine and Machine Feed editor widgets to be opened directly from Feed View

We have enabled both the Machine Editor widget and Machine Feeds editor widget to be opened in the Feed View. This can be completed by right-clicking on the machine name, in which case the Machine Editor widget will open, or right-clicking on the machine name feed, in which case the Machine Feeds editor widget will open.

• DSOF-20780 Add support for alignment in Text Layer

We have added both vertical and horizontal alignment in the Text Layer.

• DSOF-20764 Create UnusedMediaDomain

The UnusedMediaDomain has been created to cache files that exist on machines but are not mapped anywhere. It also contains a method to delete all but one copy of unused media across the d3 session.

• DSOF-20694 Notify the user that a ShotRecorder's Timecode source needs to be set within the TransportManager

• DSOF-20667 Add separators for Designer licences versus RenderStream licences in d3manager

We have added more visual separation between Designer and RenderStream licences reported in the d3 License section of d3 manager (accessed via d3 manager / help / d3 License)

• DSOF-20592 Add shortcut to be able to specify the name of a new layer when duplicating (CTRL + SHIFT + D)

We have added a shortcut to be able to specify the name of a new track layer and/or layer stack layers. When creating a layer, select it and press CTRL + SHIFT + D. There will be a rename box pop-up to allow renaming the layer from the default name. 

• DSOF-20502 FeedWarp button to limit all points to be inside the image borders

We have created a “Restrict To Bounds” button when using FeedWarp to limit all or selected control points to within the image borders. This can be found when right-clicking on FeedRect, select “Edit Warp” and the “Restrict to Bounds” button can be found. Clicking this button will restrict all points to values between 0 and 1. If a user right-clicked on a control point, clicking the “Restrict to Bounds” button in this instance will restrict all selected points to values between 0 and 1.

• DSOF-20418 Show layer/track name in RenderStream workload UI

We have added the Layer (Track) name option in the RenderStream workload UI to help distinguish between layers with the same asset and pool.

• DSOF-20376 Allow GUI heads to be genlocked if they are the only output head on the machine, and reflect this status in the GUI

We have enabled dedicated director machines to have their GUI heads genlocked from within Designer, even if the VFCs of this machine are not connected or emulated. The previous workflow was to make sure that the VFC cards are all emulated even when they are not connected.

• DSOF-19868 Move display management buttons from feed visualiser to machine editor in Feed View

We have moved the following buttons from the feed view to a new Display Management separator located in the machine editor:

• Apply Feeds
• Apply Genlock - greyed out when no genlock is present, when already applied, or on a Solo
• Remove Genlock - greyed out when no genlock is present, when already applied, or on a Solo
• Refresh - greyed out for AMD machines i.e. vx series
• Reset EDIDS
• Bit Depth Selection - only bit depths that are supported by the machine type are available

• DSOF-19481 Improve AR calibration tool by allowing multiple alignment objects

In previous releases, it was only possible to use one alignment object when doing an AR calibration. As the AR calibration tool also requires at least 6 reference points per alignment object, it meant that only complex surfaces could be used as alignment objects, rather than flat LED or projection surfaces. 

In r21.4 we have made it so that users can use as many alignment objects as are needed in order to align the camera, and therefore be able to use two LED or projection surfaces as an example.

• DSOF-18251 Right-click options for moving layers to top/bottom

To aid compositing in a layer stack, we have added the option to  moving layers to the top or bottom of the stack. This can be completed by right-clicking on a layer, layers, or group layer / move to top OR move to bottom right-click on a layer, layers or group layer.

• DSOF-17002 Create the ability to drag a section break on the timeline with mouse

We have enabled the ability to drag a section break on the timeline with a mouse. If a user hovers the mouse pointer over a section break, the mouse pointer changes to reflect that the section break can be moved. 

Press ALT + drag the mouse to adjust the position of the section break only on the timeline, and CTRL + ALT + drag the mouse to adjust the position of the section break with the tag and note on the timeline. 

• DSOF-17001 Creation of keyboard shortcuts for snapping layer(s) length to section break:

We have created the following keyboard shortcuts for snapping layer(s) to section break:

1. Ctrl + < extend the Start of the selected layers to last section break
2. Ctrl + > trim the Start of the selected layers to next section break
3. Alt + < trim the End of the selected layers to last section break
4. Alt + > extend the End of the selected layers to next section break
5. Ctrl + Alt + </> move the selected layers to last/next section break (length remain the same)

• DSOF-14667 When applying feeds on an actor from a director, the status of the feed application process should be viewable from the director

In a multi-machine setup - in this instance 1 director and 1 actor - when applying feed settings on the actor, the director GUI will show "Applying Feed Settings..." in the machine status area in the feed view. The output icon will also change to blue for status “busy” with "Applying Feed Settings” in the tooltip. The status will return to its previous state and the text in the feed view will disappear once the remote machine has finished applying feeds.

• DSOF-10297 Allow colour depth selection per output and per machine

We have created an additional field in the machine editor in the display management separator called "Machine bit depth". Within this field, there's the option to use the project bit depth as set in the d3 project editor or in the global buttons in the feed view, or to override the project bit depth selection for that machine with 8 bit or 10 bit specifically. Machines not capable of supporting 10 bit will only present 8 bit as an option.

In the event that a machine is set to a type that supports 10 bit, has Project Bit Depth or 10 bit selected, and then the machine type is changed to one that does not support 10 bit, then the selection will show “invalid” until it is changed to a valid selection.

• DSOF-7493 "Insert Time" function now remembers the last typed value

In previous releases, inserting time to the timeline is something that has to be completed over multiple sections, layers and so on. We have enabled it so that the Insert Time field remembers the last value entered.

• DSOF-2134 Output Port selection and multi-edit of resolution

We have enabled the bulk editing of VFC output settings for multiple machines. The settings that can be changed in bulk are EDID Emulation, Split Mode (when supported), Timing Mode and Output Resolution.

• DSOF-20111 Send screen pose data dynamically over Renderstream for Mesh Projection
• DSOF-20026 Add resolution scale factor to Mesh Projection
• DSOF-19975 Include roll angle in perspective matrix for Mesh Projection
• DSOF-19751 Use RenderStream splitting logic to define UV splits for Mesh Projection
• DSOF-19674 Implement overlap for Mesh Projection
• DSOF-19673 Implement padding for Mesh Projection
• DSOF-19672 Implement SLC splitting for Mesh Projection
• DSOF-18671 Warp rendered video to mesh in RenderStream sender
• DSOF-18670 Calculate perspective data for Mesh Projection
• DSOF-18114 Implement basic UV splitting for Mesh Projection
• DSOF-18113 Synchronise surface mesh over RenderStream for Mesh Projection
• DSOF-18112 Create mapping for Mesh Projection

• DSOF-21268 - Fixed a RenderStream Access Violation
• DSOF-21251 Invalid access to DmxDisplay System error on launch
• DSOF-21249 Errors when >1 camera added to spatial map for Renderstream layer
• DSOF-21248 renderstream includes discarded frames in the total 'sent' when calculating receive health.
• DSOF-21247 RenderStream workloads fail with "Send Frame error: 16"
• DSOF-21214 sanitise_xml.py script fails the build if test result file contains certain unicode characters
• DSOF-21195 Assigning a camera to the input of a video_in.mov freezes d3 and displays an Access Violation in the console
• DSOF-21181 Invalid access to RenderStreamSystem error on launch
• DSOF-21175 Assigning/removing media that has been removed by the Media Distribution widget displays an AV
• DSOF-21173 Trying to open a Manual Observation with an Alignment Object assigned displays a 'not defined' error and will not open the widget
• DSOF-21148 - Fixed an issue where d3service shutdown blocked for 8 minutes waiting for rsync.exe to be cleanly closed
• DSOF-21131 - Fixed an Access Violation when opening project if enableActiveRegions set
• DSOF-21061 - Fixed an issue when using the All VFC Devices widget, changing the Spilt would cause the VFC SDI QUAD 4k feed resolution to increase
• DSOF-21059 - Fixed an issue where all VFC Devices widget displayed an out bounds error when the Spilt mode is changed to Quad 4k
• DSOF-21046 - Fixed an Access Violation during “Apply Genlock”
• DSOF-21000 - Fixed LUT Files sync failing between machines when doing Colour Calibration
• DSOF-20970 - Fixed an issue where right-clicking a Port within the All VFC Devices widget opened VFCPortConfig widget
• DSOF-20969 - Fixed an issue where all VFC Devices widget did not remove Ports when changing Split Mode that removes them
• DSOF-20968 - Fixed an issue where the All VFC Devices widget named newly added Ports "VFCPortConfig"
• DSOF-20967 - Fixed All VFC Devices widget not automatically resizing when changing Split Mode
• DSOF-20965 - Fixed All VFC Devices widget showing Split Mode for all VFC types
• DSOF-20963 - Fixed All VFC Devices widget does respecting non-editable fields
• DSOF-20946 - Fixed an issue where update the mesh while RenderStream is running resulted in a wrong overlapping.
• DSOF-20931- Fixed an Access Violation when using Sockpuppet : Strobe Layer
• DSOF-20874 - Fixed Display Management separator in the machine editor not opening
• DSOF-20863 - Fixed an issue where local RenderStream streams may not appear in the Receive Health indicator
• DSOF-20829 - Improved the speed of API calls
• DSOF-20817 - Fixed a Notch Sockpuppet Access Violation on releasing mapping
• DSOF-20816 - Fixed an issue where the node status error would be displayed when starting an Actor while Machine Editor widget is open
• DSOF-20813 - Fixed d3 failing to run when no network connections are active
• DSOF-20809 “D3StateEditor" objects has no attribute "Contents” error when starting a blank project
• DSOF-20802 - Fixed an Access Violation when creating either TimecodeTransportMidiBeatClock or TimecodeTransportTapTempo within a ShotRecorder
• DSOF-20801 - Fixed an issue where driver info of Fixture Instance defaults to “None” every time the machine reboot.
• DSOF-20781 - Moved Text Layer into Generative
• DSOF-20762 - Fixed an issue where, on exit, d3 always logs "saving all resources: done." even if nothing was saved
• DSOF-20751 - Fixed a buffer lock access error when setting a camera to Lux mode
• DSOF-20748 - Fixed an issue where video inputs could not be mapped in quick editor
• DSOF-20746 - Fixed audio output patches in the audio layer only showing up to 12 patches
• DSOF-20745 - Fixed an issue where layers within groups did not correspond with moving to the top or bottom options
• DSOF-20737 - Fixed an error when clicking on “Details” to get log for RenderStream workload
• DSOF-20728 - Fixed an issue where refreshing an Editor showed a “NoneType” object having no attribute “canClose”
• DSOF-20721 - Fixed an Access Violation when scrolling versions number in “Manage Old Media”
• DSOF-20708 - Fixed an Access Violation when unpatching a Video layer from Sockpuppet after it has had its mapping set to None
• DSOF-20681- RenderStream: fixed incorrect options length for Workload Transport Formats
• DSOF-20671 - Fixed D3State menu taking up two rows
• DSOF-20661 - Fixed an Access Violation when creating a Fixture in a DMX Light
• DSOF-20660 - Fixed an issue where exceptions during project sync could lead to data loss
• DSOF-20646 - RenderStream: Fixed an issue where Creating Channel Instances before adding a map would cause an Access Violation
• DSOF-20642 - Web: Fixed a pathing error due to suffix when reloading URL for local file via Interact widget
• DSOF-20638 - Fixed playback framerate issues
• DSOF-20634 - Feed Warp: Fixed DeformStackItem accessing reserved but unallocated memory
• DSOF-20620 - Improved Spatial calibration when running two observations
• DSOF-20610 - Improved SmartGroup functionality
• DSOF-20593 - Fixed Clip information text not updating on versioning toggle
• DSOF-20587 - Fixed an Error when undoing added RenderStream layers
• DSOF-20570 - Fixed an issue where could freeze when applying feed settings
• DSOF-20554 - LumaKeyedVideoIn: Fixed a zero-sized texture being used error
• DSOF-20528 - TestPattern module is now Generative
• DSOF-20527 - Fixed feed output shifting one pixel to the left when set SMPTE timing
• DSOF-20516 - Removed a misleading log entry "Replaced existing hook for Subsystem"
• DSOF-20512 - Fixed SmartGroup Versioning changes affecting assets not in the SmartGroup
• DSOF-20510 - Fixed an issue where waveform scope has graphical artefacts when Scope is resized to be too small
• DSOF-20507 RenderStream: Fixed an Access Violation when attempting to start a workload with the Manual splitting strategy
• DSOF-20504 - Fixed Data Rate reporting
• DSOF-20484 - Objectview: added “found” filter to hide all missing assets
• DSOF-20474 =- Fixed an error after unmapping a placeholder clip
• DSOF-20469- Fixed nginx.exe not starting when running through Visual Studio
• DSOF-20455 - It's no longer possible to open multiple Receive Health widgets for a single Workload
• DSOF-20439 - Improved CameraVideoIn subsystem
• DSOF-20432 - Fixed being unable to use the same video on placeholder clip of different videoin
• DSOF-20427 - Workload editor, Advanced window improvements
• DSOF-20423 - Fixed NotchLC decoding having redundant allocations
• DSOF-20402 - Fixed Clip Duration not updating correctly when toggling between versions
• DSOF-20347 - Clicking on frame replay OFF/ON no longer creates output in the widget
• DSOF-20332 - Fixed the SockPuppet bank windows not resizing
• DSOF-20331 Fixed the SockPuppet Bank Editor not showing the bank lists
• DSOF-20312 - Debug info now available if Rivermax does not initialise
• DSOF-20307 - Fixed a rawTracking.Received error when viewing camera not in stage
• DSOF-20290 - vx4+ - Fixed an issue where applying feeds settings in d3 results in breaking the genlock
• DSOF-20288 - Fixed cycle being detected when undoing the deletion or addition of a manual observation
• DSOF-20287 - Reverse proxy improvements
• DSOF-20276 - TextModule: Fixed an issue where inputs could not be adjusted with a mouse scroll
• DSOF-20259 - RenderStream: Fixed an issue where received health showed the status of machines which are not subscribed to the stream, resulting in “no frames received yet” status
• DSOF-20255 - Fixed an Access Violation when clicking on a video-in preview after removing a live source input
• DSOF-20252 - Fixed an issue where duplicating a GreenScreen added the copy name twice to the “Greens screens” list
• DSOF-20250 - Fixed a pathing error thrown when selecting a local HTML file with whitespace in its path
• DSOF-20238 - Fixed 9-point feed warp selection being rendered incorrectly on outputs
• DSOF-20228 - Fixed audio devices list in Audio Patch not having vertical scroll
• DSOF-20187 - Fixed UserInfoProcessMessageHandler
• DSOF-20180 - Fixed an issue where setting fractional resolutions in surfaces breaks the mapping resolutions
• DSOF-20175 - Fixed an issue where DMX surfaces are incorrectly highlighted in red on the stage
• DSOF-20158 - Fixed directory changes within symbolic link / directory junction not being detected
• DSOF-20116 - Fixed spherical mapping wireframe being misaligned from actual content projection
• DSOF-20103 - Fixed an issue where tearing could occur when having no GUI enabled or emulated
• DSOF-20089 - Fixed an issue where only half of each stream rendered when split into two fragments
• DSOF-20079 - Fixed an issue where virtual lineup layer did not work when a live camera is used
• DSOF-20062 - Fixed an issue where the feed mapping mirror flip buttons caused whole rectangle to turn black
• DSOF-20055 - Fixed an issue where option switches set in Advanced Project Settings did not sync to other machines on initial launch
• DSOF-20052 - Fixed an issue when holding the output of a single projector while Dynamic Blend is enabled froze the GUI and made every other output turn black
• DSOF-20028 - Fixed content roll jumping between 90 degree offsets
• DSOF-19950 - Fixed an issue where scrubbing through the timeline while paused caused video layers to flicker black
• DSOF-19948 - Fixed an Access Violation when changing surface type
• DSOF-19910 - Fixed the perspective matrix being incorrect when eye point is above screen
• DSOF-19698 - Fixed an issue where if Colour Management was disabled or set to Gamma, LUTs had a popup window which is totally empty of controls
• DSOF-19668 - ACES: Improved CDL tooltip
• DSOF-19362 - Fixed an issue where the Pause All feature of graphs caused machine FPS to be reported as 0 (or frozen at last value)
• DSOF-19262 - Fixed a Topological Sort and Access Violation when attempting to undo alignment point in manual observations
• DSOF-19226 - Fixed an issue where DMX Lights were not immediately affected by TargetObject
• DSOF-19168 - fixed an issue where using CTRL+Z to undo a manual observation created an "!!!!! Operation: topological sort found cycle; please send console to support" error
• DSOF-19100 - Fixed an issue where delecting a Chroma Source within a Luma Keyed Input resulted in “Unable to create video capture stream”
• DSOF-18542 - Fixed an Access Violation when layer editor for Notch layer is open across multiple machines
• DSOF-18362 - Fixed an issue where rear projected surfaces did not dynamically blend properly
• DSOF-17496 - Fixed an issue where the d3 network widget would get hidden by d3 state editor
• DSOF-17197 - Changing content version doesn't work with Smart Groups
• DSOF-12262 - Fixed population masks being ignored by DSE
• DSOF-11582 - Fixed setDebugName not limiting strings passed to DirectX SetPrivateData
• DSOF-7081 - Fixed an issue where the fuplicate quantiser title text overlapped with metronome controls
• DSOF-4981 - Added mechanism for using consistent VFC output resolutions when mixing passthrough (DisplayPort/HDMI) and quad VFC cards (Quad SDI/Quad DVI)

Q-SDI VFC Firmware advisory

Background:

SDI VFCs are unable to achieve a guaranteed genlock to an interlaced genlock signal. There is 50% chance there will be a phase offset of 1 field (180 degrees). This is due to the way in which the sync cards for both AMD and NVidia GPUs detect genlock signals.

Firmware version 1.9.0 adds a button to reverse the field, which enables you to revert to the alternate field if genlock is phase offset. To properly use this feature, you will need to have the relevant equipment to be able to measure the phase of the SDI output.

Firmware version 1.9.0 requires the use of r17 or greater.

Impact of Issue:

Any Q-SDI VFC shipped with firmware 1.8.0 or earlier and needing to lock to interlaced Genlock Signal

Affected Hardware:

All Q-SDI VFC shipped with previous firmware versions.

How to determine the current firmware version:

• Populate VFC compatible disguise machine with only the SDI cards you want to check.
• Run vfcfirmwareupdater.exe located at C:\Program Files\d3 Production Suite\build\msvc
• Check Firmware Version

How to update to v1.9.0:

• Populate any VFC compatible disguise machine with only the SDI cards required to be updated.
• Download the VFC firmware update from: https://d3packages.s3.amazonaws.com/vfc/quad_sdi_vfc_v1-9-0.rbf
• Run vfcfirmwareupdater.exe located at C:\Program Files\d3 Production Suite\build\msvc
• Click Choose file and load the downloaded VFC firmware update. The filename should be quad_sdi_vfc_v1-9-0.rbf
• Slots will be automatically selected. Ensure only SDI type cards have this firmware update applied to them.

• Click Update Firmware, the update will start and will take between 10-25 minutes.

• On completion, the Firmware version field will not update until all cards have finished updating and have been re-initialised and detected.

• DSOF-21248 - Fixed an issue where RenderStream included discarded frames in the total 'sent' when calculating receive health

• DSOF-20609 - Fixed multiple Access Violations

• DSOF-20421 - Refactored NotchLCSubSystem to have one decoder per resolution

• Q-SDI VFC Firmware advisory

  Background:

  SDI VFCs are unable to achieve a guaranteed genlock to an interlaced genlock signal. There is 50% chance there will be a phase offset of 1 field (180 degrees). This is due to the way in which the sync cards for both AMD and NVidia GPUs detect genlock signals.

  Firmware version 1.9.0 adds a button to reverse the field, which enables you to revert to the alternate field if genlock is phase offset. To properly use this feature, you will need to have the relevant equipment to be able to measure the phase of the SDI output.

  

  Firmware version 1.9.0 requires the use of r17 or greater.

   

  Impact of Issue:

  Any Q-SDI VFC shipped with firmware 1.8.0 or earlier and needing to lock to interlaced Genlock Signal

   

  Affected Hardware:

  All Q-SDI VFC shipped with previous firmware versions.

   

  How to determine the current firmware version:

  • Populate VFC compatible disguise machine with only the SDI cards you want to check.
  • Run vfcfirmwareupdater.exe located at C:\Program Files\d3 Production Suite\build\msvc
  • Check Firmware Version

   

  

   

  How to update to v1.9.0:

  • Populate any VFC compatible disguise machine with only the SDI cards required to be updated.
  • Download the VFC firmware update from: https://d3packages.s3.amazonaws.com/vfc/quad_sdi_vfc_v1-9-0.rbf
  • Run vfcfirmwareupdater.exe located at C:\Program Files\d3 Production Suite\build\msvc
  • Click Choose file and load the downloaded VFC firmware update. The filename should be quad_sdi_vfc_v1-9-0.rbf
  • Slots will be automatically selected. Ensure only SDI type cards have this firmware update applied to them.

   

  

  • Click Update Firmware, the update will start and will take between 10-25 minutes.

   

  

  • On completion, the Firmware version field will not update until all cards have finished updating and have been re-initialised and detected.

   

  

  • Finally, reboot the system.

• DSOF-21165 - Fixed set extension being mask misaligned with screen when using large distortion & centre shift

• DSOF-21095 - Fixed an issue where UVLookup module had checkerboard cross artefacts on the image

• DSOF-21057 - Fix gpu fan speed not running at 100% while d3 is running to improve performance and stability on a vx4

• Q-SDI VFC Firmware advisory

  Background:

  SDI VFCs are unable to achieve a guaranteed genlock to an interlaced genlock signal. There is 50% chance there will be a phase offset of 1 field (180 degrees). This is due to the way in which the sync cards for both AMD and NVidia GPUs detect genlock signals.

  Firmware version 1.9.0 adds a button to reverse the field, which enables you to revert to the alternate field if genlock is phase offset. To properly use this feature, you will need to have the relevant equipment to be able to measure the phase of the SDI output.

  

  Firmware version 1.9.0 requires the use of r17 or greater.

   

  Impact of Issue:

  Any Q-SDI VFC shipped with firmware 1.8.0 or earlier and needing to lock to interlaced Genlock Signal

   

  Affected Hardware:

  All Q-SDI VFC shipped with previous firmware versions.

   

  How to determine the current firmware version:

  • Populate VFC compatible disguise machine with only the SDI cards you want to check.
  • Run vfcfirmwareupdater.exe located at C:\Program Files\d3 Production Suite\build\msvc
  • Check Firmware Version

   

  

   

  How to update to v1.9.0:

  • Populate any VFC compatible disguise machine with only the SDI cards required to be updated.
  • Download the VFC firmware update from: https://d3packages.s3.amazonaws.com/vfc/quad_sdi_vfc_v1-9-0.rbf
  • Run vfcfirmwareupdater.exe located at C:\Program Files\d3 Production Suite\build\msvc
  • Click Choose file and load the downloaded VFC firmware update. The filename should be quad_sdi_vfc_v1-9-0.rbf
  • Slots will be automatically selected. Ensure only SDI type cards have this firmware update applied to them.

   

  

  • Click Update Firmware, the update will start and will take between 10-25 minutes.

   

  

  • On completion, the Firmware version field will not update until all cards have finished updating and have been re-initialised and detected.

   

  

  • Finally, reboot the system.

• DSOF-21020 - Fixed an issue where Virtual Cameras would offset real cameras on the stage

• DSOF-20896 - Fixed an issue where fonts would appear tiny in the gui

• DSOF-20803 - Fixed an issue where the Set Extension in an MRset would leave a fringe around the LED when lens intrinsics weren’t set

• Q-SDI VFC Firmware advisory

  Background:

  SDI VFCs are unable to achieve a guaranteed genlock to an interlaced genlock signal. There is 50% chance there will be a phase offset of 1 field (180 degrees). This is due to the way in which the sync cards for both AMD and NVidia GPUs detect genlock signals.

  Firmware version 1.9.0 adds a button to reverse the field, which enables you to revert to the alternate field if genlock is phase offset. To properly use this feature, you will need to have the relevant equipment to be able to measure the phase of the SDI output.

  

  Firmware version 1.9.0 requires the use of r17 or greater.

   

  Impact of Issue:

  Any Q-SDI VFC shipped with firmware 1.8.0 or earlier and needing to lock to interlaced Genlock Signal

   

  Affected Hardware:

  All Q-SDI VFC shipped with previous firmware versions.

   

  How to determine the current firmware version:

  • Populate VFC compatible disguise machine with only the SDI cards you want to check.
  • Run vfcfirmwareupdater.exe located at C:\Program Files\d3 Production Suite\build\msvc
  • Check Firmware Version

   

  

   

  How to update to v1.9.0:

  • Populate any VFC compatible disguise machine with only the SDI cards required to be updated.
  • Download the VFC firmware update from: https://d3packages.s3.amazonaws.com/vfc/quad_sdi_vfc_v1-9-0.rbf
  • Run vfcfirmwareupdater.exe located at C:\Program Files\d3 Production Suite\build\msvc
  • Click Choose file and load the downloaded VFC firmware update. The filename should be quad_sdi_vfc_v1-9-0.rbf
  • Slots will be automatically selected. Ensure only SDI type cards have this firmware update applied to them.

   

  

  • Click Update Firmware, the update will start and will take between 10-25 minutes.

   

  

  • On completion, the Firmware version field will not update until all cards have finished updating and have been re-initialised and detected.

   

  

  • Finally, reboot the system.

• DSOF-20997 – Fixed an issue where Multiple MIDI devices reported as "MIDI" making it impossible to select a specific one

• DSOF-20988 - Fixed an issue where virtual cameras did not inherit LUTs of calibrated cameras

• Q-SDI VFC Firmware advisory

  Background:

  SDI VFCs are unable to achieve a guaranteed genlock to an interlaced genlock signal. There is 50% chance there will be a phase offset of 1 field (180 degrees). This is due to the way in which the sync cards for both AMD and NVidia GPUs detect genlock signals.

  Firmware version 1.9.0 adds a button to reverse the field, which enables you to revert to the alternate field if genlock is phase offset. To properly use this feature, you will need to have the relevant equipment to be able to measure the phase of the SDI output.

  

  Firmware version 1.9.0 requires the use of r17 or greater.

   

  Impact of Issue:

  Any Q-SDI VFC shipped with firmware 1.8.0 or earlier and needing to lock to interlaced Genlock Signal

   

  Affected Hardware:

  All Q-SDI VFC shipped with previous firmware versions.

   

  How to determine the current firmware version:

  • Populate VFC compatible disguise machine with only the SDI cards you want to check.
  • Run vfcfirmwareupdater.exe located at C:\Program Files\d3 Production Suite\build\msvc
  • Check Firmware Version

   

  

   

  How to update to v1.9.0:

  • Populate any VFC compatible disguise machine with only the SDI cards required to be updated.
  • Download the VFC firmware update from: https://d3packages.s3.amazonaws.com/vfc/quad_sdi_vfc_v1-9-0.rbf
  • Run vfcfirmwareupdater.exe located at C:\Program Files\d3 Production Suite\build\msvc
  • Click Choose file and load the downloaded VFC firmware update. The filename should be quad_sdi_vfc_v1-9-0.rbf
  • Slots will be automatically selected. Ensure only SDI type cards have this firmware update applied to them.

   

  

  • Click Update Firmware, the update will start and will take between 10-25 minutes.

   

  

  • On completion, the Firmware version field will not update until all cards have finished updating and have been re-initialised and detected.

   

  

  • Finally, reboot the system.

• DSOF-17918 - vx4+ Support

• DSOF-21017 - Fixed an issue where projects with a stage render layer could not launch
• DSOF-20982 - Fixed an issue where Within-Spec NotchLC file playback stuttered
• DSOF-20980 - Fixed the "rsync.exe failed to start" error on server shutdown
• DSOF-20952 - Fixed an issue where MSVCR100.dll was not found when d3service is started (nginx)
• DSOF-20911 - Fixed being unable to select MIDI device in MTC layer on server
• DSOF-20895 - Fixed an issue where ‘manage workloads’ caused new workloads to start continuously
• DSOF-20806 - Fixed node-js Conan package not being fully self-contained and needing an internet connection
• DSOF-20759 - Fixed an issue where a HAP mov file added as New Placeholder Clip did not function properly
• DSOF-20347 - Fixed an issue where clicking on frame replay OFF/ON created output in the widget
• DSOF-20258 - Fixed d3 crashing if the placeholder image and input are the same and the input is removed

• Q-SDI VFC Firmware advisory

  Background:

  SDI VFCs are unable to achieve a guaranteed genlock to an interlaced genlock signal. There is 50% chance there will be a phase offset of 1 field (180 degrees). This is due to the way in which the sync cards for both AMD and NVidia GPUs detect genlock signals.

  Firmware version 1.9.0 adds a button to reverse the field, which enables you to revert to the alternate field if genlock is phase offset. To properly use this feature, you will need to have the relevant equipment to be able to measure the phase of the SDI output.

  

  Firmware version 1.9.0 requires the use of r17 or greater.

   

  Impact of Issue:

  Any Q-SDI VFC shipped with firmware 1.8.0 or earlier and needing to lock to interlaced Genlock Signal

   

  Affected Hardware:

  All Q-SDI VFC shipped with previous firmware versions.

   

  How to determine the current firmware version:

  • Populate VFC compatible disguise machine with only the SDI cards you want to check.
  • Run vfcfirmwareupdater.exe located at C:\Program Files\d3 Production Suite\build\msvc
  • Check Firmware Version

   

  

   

  How to update to v1.9.0:

  • Populate any VFC compatible disguise machine with only the SDI cards required to be updated.
  • Download the VFC firmware update from: https://d3packages.s3.amazonaws.com/vfc/quad_sdi_vfc_v1-9-0.rbf
  • Run vfcfirmwareupdater.exe located at C:\Program Files\d3 Production Suite\build\msvc
  • Click Choose file and load the downloaded VFC firmware update. The filename should be quad_sdi_vfc_v1-9-0.rbf
  • Slots will be automatically selected. Ensure only SDI type cards have this firmware update applied to them.

   

  

  • Click Update Firmware, the update will start and will take between 10-25 minutes.

   

  

  • On completion, the Firmware version field will not update until all cards have finished updating and have been re-initialised and detected.

   

  

  • Finally, reboot the system.

• DSOF-20837 - Fixed feed setting UI display "House sync signal present" rounding 59.94hz to 60hz
• DSOF-20790 - Fixed an issue where a layer name was no longer cut when the layer was resized
• DSOF-20757 - Fixed "Invalid type specifier" while Applying Feed Settings
• DSOF-20720 - Fixed an issue where the UV Lookup Module was pixelating content
• DSOF-20705 - Fixed console spam when feed view is active
• DSOF-20677 - Fixed the text in the DMX monitor being out of alignment
• DSOF-20657 - Fixed an Access Violation when creating an Indirection
• DSOF-20438 - Fixed an issue with applying feed settings at 1080i59.94
• DSOF-20302 - Fixed an Access Violation when performing the unsupported operation of dragging a meta-field min/max from a video module into an open layer

• DSOF - 20565 - Overscan on RenderStream content creates a clear visual difference from non-overscanned content
• DSOF-17848 - With "disableDmxPacketSendWait" on, lost sACN node on network still causes the project to slow to a halt.
• DSOF-17540 - Sequencing changes do not transfer to other machines in session when restoring a snapshot
  - Workaround: Not know
  - Affects version: r18.1.2
• DSOF-17193 - Multi User Edit in UE requires preferred sync adapter to be set to a network adapter which is available to all machines
• DSOF-17108 - Current NCAM data implementation used can exhibit unreliable packet timing
• DSOF-16935 - d3 cannot set SDI VFCs to Quad 4K 2SI 23.98, 24, 29.97 or 30Hz
• DSOF-16425 - Renderstream: When using MultiChannelMapping, only one spatial map w backplate is able to change position/rotation
• DSOF-15445 - Editor machines with a user account linked to an Microsoft Account can't join d3 sessions due to permissions errors
  

  Q-SDI VFC Firmware advisory

  Background:

  SDI VFCs are unable to achieve a guaranteed genlock to an interlaced genlock signal. There is 50% chance there will be a phase offset of 1 field (180 degrees). This is due to the way in which the sync cards for both AMD and NVidia GPUs detect genlock signals.

  Firmware version 1.9.0 adds a button to reverse the field, which enables you to revert to the alternate field if genlock is phase offset. To properly use this feature, you will need to have the relevant equipment to be able to measure the phase of the SDI output.

  

  Firmware version 1.9.0 requires the use of r17 or greater.

   

  Impact of Issue:

  Any Q-SDI VFC shipped with firmware 1.8.0 or earlier and needing to lock to interlaced Genlock Signal

   

  Affected Hardware:

  All Q-SDI VFC shipped with previous firmware versions.

   

  How to determine the current firmware version:

  • Populate VFC compatible disguise machine with only the SDI cards you want to check.
  • Run vfcfirmwareupdater.exe located at C:\Program Files\d3 Production Suite\build\msvc
  • Check Firmware Version

   

  

   

  How to update to v1.9.0:

  • Populate any VFC compatible disguise machine with only the SDI cards required to be updated.
  • Download the VFC firmware update from: https://d3packages.s3.amazonaws.com/vfc/quad_sdi_vfc_v1-9-0.rbf
  • Run vfcfirmwareupdater.exe located at C:\Program Files\d3 Production Suite\build\msvc
  • Click Choose file and load the downloaded VFC firmware update. The filename should be quad_sdi_vfc_v1-9-0.rbf
  • Slots will be automatically selected. Ensure only SDI type cards have this firmware update applied to them.

   

  

  • Click Update Firmware, the update will start and will take between 10-25 minutes.

   

  

  • On completion, the Firmware version field will not update until all cards have finished updating and have been re-initialised and detected.

   

  

  • Finally, reboot the system.

   

• DSOF-20318 Warn when EDID timings don't match
• DSOF-20205 OscControl: rename OscCommand's address to "OSC address" that distinguishes it from the IP Address
• DSOF-20153 More informative "zero-sized texture being used" notification
• DSOF-20098 Improve performance of NotFoundMediaSystem
• DSOF-20083 Make default VFC to be HDMI rather than DVI
• DSOF-19946 Improve Project / Upgrade Load Time
• DSOF-19865 [ACES] CDL functionality outside ACES mode
• DSOF-19785 RenderStream Compressed: increase target bits/sec when using alpha plane
• DSOF-19645 Increase default resolution maximum of VFC cards from 5120x5120
• DSOF-19547 Left-click on layers in the layer stack to immediately open the layer editor
• DSOF-19546 Notes: seen/unseen states
• DSOF-19535 Simplify and fix SlugFont implementation
• DSOF-19318 Add support for alpha in 4:2:2 RenderStream uncompressed format
• DSOF-19065 RenderStream: Include asset schema JSON in diagnostics
• DSOF-18602 Improve process and gpu memory graphs to better represent the state of memory usage
• DSOF-18258 Camera switching control module
• DSOF-18234 API control for shot recording
• DSOF-17374 Expanded LUT file support (including 1D LUTs)
• DSOF-17343 Camera bookmarks for the feed view
• DSOF-16686 Avoid pixelation when doing virtual camera moves through the reprojection plan
• DSOF-12111 Make isCefPaintDirtyRectangles behaviour default and remove option switch
• DSOF-9531 Listing of background tasks
• DSOF-8456 Network status widget should remember its position
• DSOF-8390 Notify the user that joining a session hosted by a different version of d3 is available, but not recommended or supported
• DSOF-4298 Inclusion of timestamp to notifications
• DSOF-4253 Ability to define image sequence frame rate automatically
• DSOF-3477 Selecting FPS for the system time transport control

• DSOF-20666  - Fixed an issue where the virtual camera disappeared from the stage when tracking source is used
• DSOF-20658 - Rendering Regression: Fixed no startup text, and flickering visualiser
• DSOF-20656 - Fixed an issue where exceptions on startup could cause unclean shutdown and risk project corruption
• DSOF-20654 - Fixed transport controls on separate lines from HUD status at 3840 * 2160 with 250% dpi scaling
• DSOF-20621 - Fixed an issue where the recorder icon in d3 state bar had a massive border on addition
• DSOF-20619 - Fixed an issue where 'Show 3D Observations' only showed text labels
• DSOF-20617 - Fixed an issue where spatial calibration produced bad results
• DSOF-20616 - Fixed an issue where spatial calibration didn't run for all screens in MR set
• DSOF-20615 - Fixed an error when clicking 'Reset all Observations' in spatial calibration
• DSOF-20608 - Fixed an issue where text seemed vertically squashed with high dpi scale
• DSOF-20542 - Fixed an issue where Independent Editor could disengage transport on director
• DSOF-20541 - Fixed an issue where there were device conflicts and potential crashes with two device managers
• DSOF-20492 - Virtual camera can no longer be added as a parent camera
• DSOF-20478 - Fixed an issue where values within Patch Assignments widget offset at random
• DSOF-20447 - Fixed an Access Violation when opening DmxPersonality widget
• DSOF-20433 - Fixed an Access violation when removing unassigned streams
• DSOF-20388 - Fixed an error when adding fields of the camera in parameter collection
• DSOF-20380 - Fixed an issue where linking a Collection to a Source created an Arraybox error notification
• DSOF-20365 - Fixed an issue where setting the resolution of a surface referenced by a mesh mapping to zero would cause d3 to hang
• DSOF-20321 - Fixed the Missing Media widget being too narrow to read long filenames
• DSOF-20306 - Fixed an Access Violation when running Colour Calibration
• DSOF-20305 - Fixed an issue where mapping plane/wireframe was not drawn for most geometric mappings
• DSOF-20282 - RenderStream: Fixed an issue where the stream crashes after a while when there is a proxy stream in the assigner
• DSOF-20275 - Fixed an issue where d3 locks up when ingesting large quantities of media
• DSOF-20274 - - Fixed a Python error "Cannot convert from 'int' to 'Colour'" when creating QuickAlign point
• DSOF-20256 - Now ensure clean shutdown of s3 main thread using RAII
• DSOF-20251 - Fixed an issue where it was not possible to open the list editor for Projectors and Cameras
• DSOF-20248 - Fixed an exception when attempting to open the Patch Assignments widget
• DSOF-20182 - Fixed a crash when attempting to jump to the timecode
• DSOF-20154 - AnimateCameraPreset: The copy values button is no longer under the Virtual Camera separator
• DSOF-20148 - Fixed an issue where resizing a module from the very start of the track pushes the module to the right, past the end of the track
• DSOF-20147 - Fixed an issue when adding a new string  into the Slate's input the Take number did not revert back to one
• DSOF-20136 - Proxy streams are now included in bandwidth estimates
• DSOF-20125 - 3D Perspective and parallel projections now use content viewpoint returned from Renderstream
• DSOF-20121 - Fixed an issue where mapping was no longer directed at surface 1 and displayed a "Bad Projection Used" error
• DSOF-20102 - Authorisation: reduced CPU spikes by moving time checks outside of CriticalSection
• DSOF-20077 - Fixed an issue where the console window did not scroll to the end of the log
• DSOF-20069 - VideoIn Fixed unresponsive  UI after being mapped to a stage camera video in
• DSOF-20066 - Fixed an issue where multiple warp editors can be opened for the same feed rectangle
• DSOF-20065 - Fixed an issue where feed mapping buttons have lost their backgrounds
• DSOF-20063 - Fixed an issue where the feed mapping edit multiple table contained parameters that did not apply to feed mappings
• DSOF-20058 - Fixed a crash on startup when the director was set to the local machine
• DSOF-20053 - Fixed an issue where dynamic blend did not work when the projector is using MSAA
• DSOF-20030 - Fixed an issue where ObjectViews that were filtered via search did not display items in relevant order
• DSOF-20020 RenderStream: Fixed Receive Health widget not clearing each time a workload was started
• DSOF-20017 RenderStream: Fixed an issue where tests showed a symbol error about d3renderstreamsend.dll
• DSOF-20007 - Choose Action button is now correctly labelled for RenderStream workloads
• DSOF-19990 - Fixed an issue where Trash Icons overlapped text within devices
• DSOF-19976 - Fixed an issue where "Remove Genlock" did not update the indicator of genlock status on Nvidia Machines
• DSOF-19966 - Bulk edit for videoclips is now laid out better and contains appropriate fields
• DSOF-19957 - Fixed an Access Violation when editing VideoIn Input Transform after defocusing VideoIn
• DSOF-19842 - Fixed an issue where a project could hang at "Scanning Package" upon start
• DSOF-19835 - Improved Renderstream active latency rounding up
• DSOF-19829 - Fixed an issue where 'Power' in a CDL widget brought up the wrong widget of values
• DSOF-19807 Video: Fixed CDL being active when ACES is disabled
• DSOF-19804 - Fixed an issue where the video input patch editor's widget was minimized when stopping a preview
• DSOF-19787 - Fixed an issue where greyed out resource fields could be selected
• DSOF-19697 - Fixed an issue where StageRender layer only works with 3D mappings
• DSOF-19690 - Fixed Timeline Control section containing non-timeline related settings
• DSOF-19687 - Fixed RGB Colour module having Input Transform option in Gamma mode
• DSOF-19638 ACES: Fixed Input Transform field appearing for videoins regardless of Colour Management value
• DSOF-19554 - Fixed thumbnail resolution for certain types of resources
• DSOF-19488 Mesh: Fixed PosIndex comparison operators > and < being incorrect
• DSOF-19280 - Fixed a delay and main thread hang when switching video modes with capture cards
• DSOF-19174 - Fixed Expressions referencing fields of other fields passed by value return garbage
• DSOF-19146 - Fixed an issue when setting Venue to None or Changing Venue removes parent-child relationships from props within it
• DSOF-19025 - Fixed an issue where Video In Placeholder Clips could not be NotchLC files
• DSOF-18996 - Fixed an Access violation when taking shot with no timecode selected
• DSOF-18969 - Fixed an issue where the network widget will always be fully expanded when d3 is started
• DSOF-18669 - Fixed vertical alignment of text not being properly centred
• DSOF-18508 - Fixed Parameter collection UI not showing enum values as a string
• DSOF-18409 - Fixed an Access violation when shot recorder links to 'None' resource
• DSOF-18377 - Fixed multiple Access violations when adding arrowing new parameters into collection
• DSOF-18289 XR: Fixed an issue where it was not possible to remove alignment points when changing mesh of Alignment Object
• DSOF-18271 - Fixed an issue where  importing .dpx files in d3 was giving the wrong colour shift
• DSOF-18241- Fixed n Access Violation if new content is deleted from the Feed view if old content is viewed in the Edit Warp widget
• DSOF-18225 - Fixed an issue where the Mapping field was not controllable via DMX if set to "None"
• DSOF-17605 - Fixed an issue with 10bit feed settings requiring a restart of d3
• DSOF-12071 - Fixed an issue with Video clip editor showing incorrect value for bits per channel for NotchLC clips
• DSOF-9815 - Fixed an issue where fade up/down/hold with an editor in independent mode affected the master

• DSOF-17848 - With "disableDmxPacketSendWait" on, lost sACN node on network still causes the project to slow to a halt.
• DSOF-17540 - Sequencing changes do not transfer to other machines in session when restoring a snapshot
• DSOF-17193 - Multi User Edit in UE requires preferred sync adapter to be set to a network adapter which is available to all machines
• DSOF-17108 - Current NCAM data implementation used can exhibit unreliable packet timing
• DSOF-16935 - d3 cannot set SDI VFCs to Quad 4K 2SI 23.98, 24, 29.97 or 30Hz
• DSOF-16425 - Renderstream: When using MultiChannelMapping, only one spatial map w backplate is able to change position/rotation
• DSOF-15445 - Editor machines with a user account linked to an Microsoft Account can't join d3 sessions due to permissions errors

Q-SDI VFC Firmware advisory

Background:

SDI VFCs are unable to achieve a guaranteed genlock to an interlaced genlock signal. There is 50% chance there will be a phase offset of 1 field (180 degrees). This is due to the way in which the sync cards for both AMD and NVidia GPUs detect genlock signals.

Firmware version 1.9.0 adds a button to reverse the field, which enables you to revert to the alternate field if genlock is phase offset. To properly use this feature, you will need to have the relevant equipment to be able to measure the phase of the SDI output.

Firmware version 1.9.0 requires the use of r17 or greater.

Impact of Issue:

Any Q-SDI VFC shipped with firmware 1.8.0 or earlier and needing to lock to interlaced Genlock Signal

Affected Hardware:

All Q-SDI VFC shipped with previous firmware versions.

How to determine the current firmware version:

• Populate VFC compatible disguise machine with only the SDI cards you want to check.
• Run vfcfirmwareupdater.exe located at C:\Program Files\d3 Production Suite\build\msvc
• Check Firmware Version

How to update to v1.9.0:

• Populate any VFC compatible disguise machine with only the SDI cards required to be updated.
• Download the VFC firmware update from: https://d3packages.s3.amazonaws.com/vfc/quad_sdi_vfc_v1-9-0.rbf
• Run vfcfirmwareupdater.exe located at C:\Program Files\d3 Production Suite\build\msvc
• Click Choose file and load the downloaded VFC firmware update. The filename should be quad_sdi_vfc_v1-9-0.rbf
• Slots will be automatically selected. Ensure only SDI type cards have this firmware update applied to them.

• Click Update Firmware, the update will start and will take between 10-25 minutes.

• On completion, the Firmware version field will not update until all cards have finished updating and have been re-initialised and detected.

• DSOF-20543  - NotchHost: Fixed fields in schema having no sequence set to true incorrectly

• DSOF-20203 -  d3service now ensures rsync is running always once starting

• DSOF-17848 - With "disableDmxPacketSendWait" on, lost sACN node on network still causes the project to slow to a halt.
  
  • Workaround: Add a static entry into the local systems ARP table.

1. Open an elevated command prompt.
2. Find out MAC for IP, could use arp -a to see existing entries in local arp cache.
3. Run netsh interface ipv4 show interfaces to get a list of interface names.
4. Add a new entry to the ARP table netsh interface ipv4 add neighbors "<interface name>" <dest ip> <dest mac>
5. E.g netsh interface ipv4 add neighbors "Wi-Fi" 10.105.1.253 01-02-03-04-05-06
6. Remove entry like so; netsh interface ipv4 delete neighbours <dest IP>
7. Important - Remove entries when done or re-image system!!! Otherwise, network issues may occur in the future sending the manually added IP addresses.
   - Affects version: r18.1.7

• DSOF-17540 - Sequencing changes do not transfer to other machines in session when restoring a snapshot
  
  • Workaround: Not know
  • Affects version: r18.1.2DSOF-18446 - Very large NotchLC content can cause d3 to lose access to GPU device

• DSOF-17193 - Multi User Edit in UE requires preferred sync adapter to be set to a network adapter which is available to all machines
  
  • Workaround: Often the preferred sync adapter is set to the 25Gb network to facilitate faster sync. Unless all machines in the network have a 25Gb adapter, the preferred sync adapter must be set to another network adapter when multi user edit sessions are running in UE. The adapter can be changed back for when running sync tasks.
  • Affects version: r18.0

• DSOF-17108 - Current NCAM data implementation used can exhibit unreliable packet timing
  
  • Workaround: Not known
  • Affects version: r18.0

• DSOF-16935 - d3 cannot set SDI VFCs to Quad 4K 2SI 23.98, 24, 29.97 or 30Hz
  
  • Workaround: Not known
  • Affects version: r18.0.2

• DSOF-16425 - Renderstream: When using MultiChannelMapping, only one spatial map w backplate is able to change position/rotation
  
  • Workaround: Not known
  • Affects version: r18

• DSOF-15445 - Editor machines with a user account linked to a Microsoft Account can't join d3 sessions due to permissions errors
  
  • Workaround: Create a second local user account
  • Affects version: r17.4.8

Q-SDI VFC Firmware advisory

This document outlines:

• Background
• Impact of issues
• Affected Hardware
• How to determine the current firmware version
• How to update to v1.9.0

Background:

SDI VFCs are unable to achieve a guaranteed genlock to an interlaced genlock signal. There is 50% chance there will be a phase offset of 1 field (180 degrees). This is due to the way in which the sync cards for both AMD and NVidia GPUs detect genlock signals.

Firmware version 1.9.0 adds a button to reverse the field, which enables you to revert to the alternate field if genlock is phase offset. To properly use this feature, you will need to have the relevant equipment to be able to measure the phase of the SDI output.

Firmware version 1.9.0 requires the use of r17 or greater.

Impact of Issue:

Any Q-SDI VFC shipped with firmware 1.8.0 or earlier and needing to lock to interlaced Genlock Signal

Affected Hardware:

All Q-SDI VFC shipped with previous firmware versions.

How to determine the current firmware version:

• Populate VFC compatible disguise machine with only the SDI cards you want to check.
• Run vfcfirmwareupdater.exe located at C:\Program Files\d3 Production Suite\build\msvc
• Check Firmware Version

How to update to v1.9.0:

• Populate any VFC compatible disguise machine with only the SDI cards required to be updated.
• Download the VFC firmware update from: https://d3packages.s3.amazonaws.com/vfc/quad_sdi_vfc_v1-9-0.rbf
• Run vfcfirmwareupdater.exe located at C:\Program Files\d3 Production Suite\build\msvc
• Click Choose file and load the downloaded VFC firmware update. The filename should be quad_sdi_vfc_v1-9-0.rbf
• Slots will be automatically selected. Ensure only SDI type cards have this firmware update applied to them.

• Click Update Firmware, the update will start and will take between 10-25 minutes.

• On completion, the Firmware version field will not update until all cards have finished updating and have been re-initialised and detected.

• Finally, reboot the system.

   

• DSOF-20533 - Fixed an issue where CDL didn't pass through alpha
• DSOF-20496 - Fixed an issue where two separate disguise sessions would stop each other's RS Workload
• DSOF-20419 - Fixed an issue where video layer projection was getting set to None and causing access violation
• DSOF-20391 - Renderstream: Fixed an issue where the web API was broken when RenderStream superlayers exist
• DSOF-20390 - Fixed an issue where importing mesh dependency from one project to another broke import
• DSOF-20371 - Fixed an issue where would d3 hangs when RenderStream assets change on the network in a project with lots of assets
• DSOF-20207 - Dynamic Blending Flashing on automation data update
• DSOF-19898 - Fixed an Access violation on notifying NotFoundMediaMessage onNotFoundChanged
• DSOF-20539 - Fixed an issue where d3 could not build when multiple VS versions or Build Tools are installed

• DSOF-17848 - With "disableDmxPacketSendWait" on, lost sACN node on network still causes the project to slow to a halt.
  
  • Workaround: Add a static entry into the local systems ARP table.

1. Open an elevated command prompt.
2. Find out MAC for IP, could use arp -a to see existing entries in local arp cache.
3. Run netsh interface ipv4 show interfaces to get a list of interface names.
4. Add a new entry to the ARP table netsh interface ipv4 add neighbors "<interface name>" <dest ip> <dest mac>
5. E.g netsh interface ipv4 add neighbors "Wi-Fi" 10.105.1.253 01-02-03-04-05-06
6. Remove entry like so; netsh interface ipv4 delete neighbours <dest IP>
7. Important - Remove entries when done or re-image system!!! Otherwise, network issues may occur in the future sending the manually added IP addresses.
   - Affects version: r18.1.7

• DSOF-17540 - Sequencing changes do not transfer to other machines in session when restoring a snapshot
  
  • Workaround: Not know
  • Affects version: r18.1.2DSOF-18446 - Very large NotchLC content can cause d3 to lose access to GPU device

• DSOF-17193 - Multi User Edit in UE requires preferred sync adapter to be set to a network adapter which is available to all machines
  
  • Workaround: Often the preferred sync adapter is set to the 25Gb network to facilitate faster sync. Unless all machines in the network have a 25Gb adapter, the preferred sync adapter must be set to another network adapter when multi user edit sessions are running in UE. The adapter can be changed back for when running sync tasks.
  • Affects version: r18.0

• DSOF-17108 - Current NCAM data implementation used can exhibit unreliable packet timing
  
  • Workaround: Not known
  • Affects version: r18.0

• DSOF-16935 - d3 cannot set SDI VFCs to Quad 4K 2SI 23.98, 24, 29.97 or 30Hz
  
  • Workaround: Not known
  • Affects version: r18.0.2

• DSOF-16425 - Renderstream: When using MultiChannelMapping, only one spatial map w backplate is able to change position/rotation
  
  • Workaround: Not known
  • Affects version: r18

• DSOF-15445 - Editor machines with a user account linked to a Microsoft Account can't join d3 sessions due to permissions errors
  
  • Workaround: Create a second local user account
  • Affects version: r17.4.8

• DSOF-20489 - Fixed an issue where uninitialised data was passed to CUDA
• DSOF-20426 - Replaced ‘RMAX stream framerate may be misconfigured’ error message with ‘RSUC Uncompressed timestamp error, potential issue with multiple streams on network conflicting or duplicate RenderStream processes on render node’
• DSOF-20424 - Fixed an issue where NotchLC decoding did not pool CPU decompress buffers
• DSOF-20412 - RenderStream: Fixed an issue where uncompressed textures were locked/unlocked on the wrong queue
• DSOF-20372 - Fixed an issue where a track with many precomps caused performance issue
• DSOF-20357 - RenderStream: Fixed an issue where OpenGL textures stopped working due to texture id reuse
• DSOF-20344 - RenderStream: Fixed an issue where enabling upscaling flipped the image upside down
• DSOF-20341 - RenderStream: Fixed a crash on rs_shutdown when running OpenGL
• DSOF-20143 - Fixed an issue where the metric monitor always polled per frame, ignores selected poll rate
• DSOF-19941 - Fixed an issue where CPU time overloaded when sending uncompressed video streams
• DSOF-14603 - Fixed an Access Violation and VideoFile Read Error on TGA sequences
• DSOF-8094 - Fixed an issue where speed property has to be in Sockpuppet mode to be able to play layer back

• DSOF-20410 - Fixed an issue where NotchLC playback flickers black under load
• DSOF-20349 - Fixed an issue where vx4s were failing to get 2G/2H input
• DSOF-20333 - Fixed an issue with GUI auto Vsync that caused GUI constantly adjust and stall
• DSOF-20319 - Fixed an issue where NotchLC throttling is performed too late for smaller resolution videos
• DSOF-20314 - Fixed an Access Violation when releasing media file through sockpuppet
• DSOF-20222 - Fixed an issue where Camera frustum movement was delayed by five seconds

• DSOF-19920 - Improved save time on projects with lots of resources
• DSOF-19595 - Improved "DMX changed from status / status" console logging

• DSOF-20219 - Fixed an issue where Quantiser closed and reopened when starting playback
• DSOF-20214 - Fixed an issue where it was possible for Rivermax to deadlock when receiving multiple streams
• DSOF-20213 - Fixed an issue where RenderStream received health reports 'subscribed' after the workload was stopped
• DSOF-20212 Fixed issue where non-director machines would attempt to start actors when deferActorStartup is set
• DSOF-20210 - Fixed an issue where starting RenderStream workloads could stall
• DSOF-20209 - Fixed an issue where RenderStream Streams were fully unsubscribed at workload exit
• DSOF-20128 - Fixed Custom UE engine builds in UE project not getting parsed correctly
• DSOF-20103 - Fixed an issue when having no GUI plugged in or emulated, and output would not Vsync, and cause tearing
• DSOF-20056 - Tracking: Fixed an issue where the camera frustum movement was out of sync between director & actor with AxisObjectTrackingSource
• DSOF-20032 RenderStream: Compressed - Fixed workloads with Alpha flickering on VX4s
• DSOF-19957 - Fixed an Access Violation when editing VideoIn Input Transform after defocusing VideoIn
• DSOF-19826 - Fixed an issue where having two separate disguise sessions would trigger each other's RS Workload Commands
• DSOF-19641 - Fixed an issue where an Actor was 2 frames delayed when the Director jumps on the timeline

Fixed in r21.0.1

• DSOF-20056 - Tracking Camera frustrum out of sync between Director & Actor with AxisObjectTrackingSource
  • Workaround: Not Known
  • Affects version: r21.0

Advisories

• DSOF-18015 - Intermittent issue - Heap Corruption causing Crash To Desktop
  • Workaround: Not known
  • Affects version: r19.0.1

• DSOF-17848 - With "disableDmxPacketSendWait" on, lost sACN node on network still causes the project to slow to a halt.
  • Workaround: Add a static entry into the local systems ARP table.
    • Open an elevated commant prompt.
    • Find out MAC for IP, could use arp -a to see existing entries in local arp cache.
    • Run netsh interface ipv4 show interfaces to get a list of interface names.
    • Add a new entry to the ARP table netsh interface ipv4 add neighbors "<interface name>" <dest ip> <dest mac>
    • E.g netsh interface ipv4 add neighbors "Wi-Fi" 10.105.1.253 01-02-03-04-05-06
    • Remove entry like so; netsh interface ipv4 delete neighbors <dest ip>
    • Important - Remove entries when done or re-image system!!! Otherwise network issues may occur in the future sending the manually added IP addresses.
  • Affects version: r18.1.7

• DSOF-17540 - Sequencing changes do not transfer to other machines in session when restoring a snapshot
  • Workaround: Not known
  • Affects version: r18.1.2

• DSOF-17193 - Multi User Edit in UE requires preferred sync adapter to be set to a network adapter which is available to all machines
  • Workaround: Often the preferred sync adapter is set to the 25Gb network to facilitate faster sync. Unless all machines in the network have a 25Gb adapter, the preferred sync adapter must be set to another network adapter when multi user edit sessions are running in UE. The adapter can be changed back for when running sync tasks.
  • Affects version: r18.0

• DSOF-17108 - Current NCAM data implementation used can exhibit unreliable packet timing
  • Workaround: Not known
  • Affects version: r18.0

• DSOF-16935 - d3 cannot set SDI VFCs to Quad 4K 2SI 23.98, 24, 29.97 or 30Hz
  • Workaround: Not known
  • Affects version: r18.0.2

• DSOF-16425 - Renderstream: When using MultiChannelMapping, only one spatial map w backplate is able to change position/rotation
  • Workaround: Not known
  • Affects version: r18

• DSOF-16082 - Clustered Rendering: d3service requires restart for asset discovery to work on new Unity executables
  • Workaround: restart d3 service
  • Affects version: r18

• DSOF-15553 - Feed mapping editor shows white screens in a notch layer on first use. In subsequent use it will then show the first pixel
  • Workaround: Not known
  • Affects version: r17.4.9

• DSOF-15445 - Editor machines with a user account linked to an Microsoft Account can't join d3 sessions due to permissions errors
  • Workaround: Create a second local user account
  • Affects version: r17.4.8

• DSOF-18466 4K XR Camera Compositing Improvements
• DSOF-18044 Colour Insider Group Improvements
• DSOF-16029 Video Scopes - Vectorscope
• DSOF-19630 Per feed rectangle vectorscopes
• DSOF-16020 Video Scopes - Histogram
• DSOF-16018 Video Scopes - Waveform
• DSOF-19721 Add scope and histogram functions to video inputs and/or virtual cameras
• DSOF-18625 Add ink dropper to colour picker UI
• DSOF-18296 Including the server name in the diag folder
• DSOF-17301 Non-stylised custom colour primaries/transform function idt/odt for ACES
• DSOF-16793 Ability to control Spatial Maps with AnimateObjectPreset
• DSOF-13139 Promote non transparent ui to a project setting
• DSOF-11229 Ability to remove video output sync (genlock) within d3
• DSOF-10146 Add DXGI support for HDR displays
• DSOF-8200 Enable a backface culling option on stage view
• DSOF-5796 Option to force emulation of disconnected outputs (usually DP VFC cards)
• DSOF-5321 Keyboard shortcut for Layer Library