Digital Camera Systems LDT-R2 and LDT-V Series are multi purpose lens encoding systems that can be used for injecting lens data into the RED Family, Panavision DXL, and Sony Venice as well as internal recording for Film cameras and other digital cameras that do not support injection recording. The LDT-V Series can also live stream lens data into virtual production software such as Unreal Engine either wired or wirelessly (LDT-RX1 reciever required for wireless data transmission).
The LDT-R2 and LDT-V Series reads the Focus, Iris and Zoom motor movements from a FIZ motor controller unit and translates this information into human readable encoded data.
This lens metadata can be written directly into the raw camera files in real-time (injection recording) or recorded onto a MicroSD card (Internal SD recording), this can also be streamed live for use in Virtual Production (VP) applications.
This manual is divided into three main sections depending on how the metadata is being recorded. Please go to the appropriate chapters.
Please note, the LDT-V Series has all the functionality of the LDT-R2 but with additional streaming capabilities. In order for the manual to be succinct, the LDT-R2 is referenced when describing functions and features of both models, whereas the LDT-V Series is referenced when it only applies to the LDT-V Series.
- Preston MDR3/MDR4
- Preston HU3
- Preston HU4 (Limited functionality see here)
- Arri LCUBE
- Cmotion Camin
- Cmotion DXL Module
- Tilta Nucleus-M
- Smart Lenses with a port
- Red Camera Family
- Panavision DXL
- Sony Venice
- All Cameras when internally recording
LDT-V Series Compatibility
- As above
- DCS Unreal Engine Plugin
- Disguise
- Stage Precision
- Aximmetery
Please contact DCS for more information if your device is not listed here.
1 | Power - 6-pin 0B Lemo | 6 | Back Button |
2 | Timecode - 5-pin 0B Lemo | 7 | Joystick |
3 | ENC - 6-pin 0B Lemo | 8 | MDR - 4-pin 0B Lemo |
4 | Memory slot for MicroSD Card | 9 | Serial - 4-pin 0B Lemo |
5 | LCD Screen | 10 | Camera - 4-pin 0B Lemo |
1 | Power - 6-pin 0B Lemo | 7 | Back Button |
2 | Ethernet - 5-pin 0B Lemo | 8 | Camera - 4-pin 0B Lemo |
3 | ENC - 6-pin 0B Lemo | 9 | Serial - 4-pin 0B Lemo |
4 | Memory slot for MicroSD Card | 10 | MDR - 4-pin 0B Lemo |
5 | LCD Screen | 11 | Timecode - 5-pin 0B Lemo |
6 | Joystick | 12 | Antenna (not pictured - LDT-V2 only) |
Name | Type | Description | Cable Codes |
---|---|---|---|
PWR | 6-pin 0B Lemo | Power and Shutter Pulse/Rec Tally connector | RUNA, RUNPV, RUNPVY, RUNV, PWRA, PWRC |
CAM | 4-pin 0B Lemo | Digital camera connection port | DXL, RED, C/i T |
ENC | 6-pin 0B Lemo | Lens data encoder connection port for LDT-E Series | ENC |
TC | 5-pin 0B Lemo | Timecode input port | TCD, TCDYA, TCDYB, TCDYC |
MDR | 4-pin 0B Lemo | Preston MDR Serial connection port | MDRP |
SERIAL | 4-pin 0B Lemo | Serial passthrough connection port | CT |
ETH (LDT-V Series Only) | 5-pin 0B Lemo | Ethernet connection port | EVP |
All DCS cables are categorized using a code and a bend relief color for each of the cable types. Cables have two default lengths, 12 or 18 inches and the connector type can be straight (S), right angle (R), or anglissimo (O). Custom cables can be made upon request.
Code | Bend Relief Color | Type Port Name |
LDT-R2 Rec Mode | Description |
---|---|---|---|---|
RUNA | Grey | 6-pin 0B Lemo to 3-pin S102 Fischer PWR |
Film, SD card | RUNA connects the LDT-R2 PWR port to a 3-pin RS socket that provides shutter pulse and power for the unit. If LDT-R2 Rec Mode is set to Injection Recording, RUNA can be used as a power cable. If using the Panavision DXL please use the PWRB cable. |
RUNPV | Grey | 6-pin 0B Lemo to 10-pin 2S Lemo PWR |
Film, SD card | RUNPV connects the LDT-R2 PWR port to a Panavision Millennium XL2 or other Panavision film cameras. The 10-pin socket on the camera provides shutter pulse and power for the LDT-R2. If the shutter pulse is sent to the camera from a Preston MDR, a Panavison 10-pin splitter box must be used on the camera end. |
RUNPVY | Grey | 6-pin 0B Lemo to 10-pin S2 Lemo and 10-pin 1B Lemo PWR |
Film, SD card | RUNPVY is a Y cable. It is the same as the RUNPV, but it also connects the 10-pin socket on the camera to a Preston MDR-3 and MDR-4. This lets the shutter pulse travel from the MDR-3 to the camera and LDT-R2 without using a Panavison 10-pin splitter box. |
RUNV | Grey | 6-pin 0B Lemo to 4-pin Hirose PWR |
Venice, SD card | RUNV connects the LDT-R2 PWR port to the 4-pin Hirose socket of the Sony Venice that provides record tally and power for the unit. |
PWRA | Black | 6-pin 0B Lemo to 2-pin 0B Lemo PWR |
RED ET, DXL ET, Any Cam Cooke /i | PWRA provides power to the LDT-R2 from a 2-pin 0B Lemo 12v power source. |
PWRB | Black | 6-pin 0B Lemo to 3-pin S102 Fischer PWR |
DXL ET, Film, SD | PWRB connects the LDT-R2 PWR port to a 3-pin RS socket on a Panavision DXL and provides shutter pulse and power for the unit |
PWRC | Black | 6-pin 0B Lemo to 3-pin S102 Fischer PWR |
RED ET, DXL ET, Any Cam Cooke /i | PWRC provides power to the LDT-R2 from a 3-pin S102 Fischer 24v power source. |
DXL | Grey | 4-pin 0B Lemo to 7-pin 1B Lemo CAM |
DXL, Element Technica | DXL cable connects the LDT-R2 to a Panavision DXL. It injects the encoded data into the RAW file. |
RED | Grey | 4-pin 0B Lemo to 4-pin 00 Lemo CAM |
RED, Element Technica | RED cable connects the LDT-R2 to a RED camera. It injects the encoded data into the RAW file. |
C/i T | Yellow | 4-pin 0B Lemo to 4-pin 0B Lemo CAM |
Any Cam, Cooke /i | C/i T cable connects the LDT-R2 to any camera that supports the Cooke/i protocol e.g. Sony Venice. It injects the encoded data into the RAW file. |
ENC | Green | 6-pin 0B Lemo to 6-pin 0B Lemo ENC |
Any mode | ENC cable connects the LDT-E Series to the LDT-R2. For more information read: Using a Lens Data Encoder |
TCD | Brown | 5-pin 0B Lemo to 5-pin 0B Lemo TC |
Film, SD card | TCD sends the timecode signal from a timecode generator to the LDT-R2. |
TCDYA | Brown | 5-pin 0B Lemo to 5-pin 0B Lemo & 5-pin 0B Lemo TC |
Film, SD card, RED, SD card | TCDYA sends the timecode signal from a timecode generator to the LDT-R2 and another device, for example, the Panavision DXL. |
TCDYB | Brown | 5-pin 0B Lemo to 5-pin 0B Lemo & BNC TC |
RED, SD card | TCDYB sends the timecode signal from a timecode generator to the LDT-R2 and a RED camera with a BNC timecode input connector. |
TCDYC | Brown | 5-pin 0B Lemo to 5-pin 0B Lemo & RED Sync TC |
RED, SD card | TCDYC sends a timecode signal from a timecode generator to the LDT-R2 and a RED camera with a Sync timecode input connector. |
MDRP | Blue | 4-pin 0B Lemo to 4-pin 0B Lemo MDR |
Any mode | MDRP cable connects the LDT-R2 to a Preston MDR3/MDR4 serial port. Also provides power. |
EVP | Yellow | 5-pin 0B Lemo to RJ45 ETH |
Virtual Production | EVP connects the ETH port of the LDT-V Series the RJ45 connector of a computer. |
SML | Yello | 4-pin 0B Lemo to 4-pin 0B Lemo MDR |
Any mode | SML connects the MDR port of the LDT-V Series to the port of a smart lens. |
CT | Orange | 4-pin 0B Lemo to 6-pin 1B Lemo SERIAL |
Any mode | CT cable connects the Preston MDR3/MDR4 serial port with a CineTape. This cable connects to the LDT-R2 Serial connector if the Preston MDR serial ports are in use. |
The LDT-R2 is equipped with one button and a joystick.
The blue button is the back button | ![]() |
The joystick is used to navigate the menus (up, down, left and right) | ![]() |
Press the joystick in to access the Menu or select an option | ![]() |
Full menu structure can be found in Appendix 1: Menu Structure
The GUI of the LDT-R2 will automatically flip when the unit is physically turned over. However, if for rigging purposes the orientation of the screen needs to be fixed then auto-flip can be turned off and an orientation can be selected manually:
Choose: Menu > Settings > Advanced > Flip GUI > Auto / No / Yes
The homepage comes up when the LDT-R2 powers up. There are four pages.
Depending on the REC Mode selected, the homepage layout differs.
System Status This page is to check the status of the SD Card and the Preston Connections |
![]() |
Selected lens Once a lens is loaded, it will be possible to check the lens details here |
![]() |
Lens details Once a lens is encoded the screen will display a real time readout of the three axis’. Push the back button to switch between units measured (feet/metres) |
![]() |
Motor Status From this page the motor connection can be checked: - None: No motor detected - Caling: Motor is calibrating - OK: Motor is ready |
![]() |
On the homepage: joystick Up/Down controls the brightness of the LDT-R2 screen.
DCS ships all units with the latest firmware, but we are constantly working on new features and fixes, so it is highly recommended that you check the firmware is up to date before starting.
Menu > Info
,On a computer:
On the LDT-R2:
When updating the firmware, it is important that the following steps are followed.
To restore the factory default settings:
Menu > Advanced > Factory Defaults
The required settings will need to be selected on the LDT after this.
DCS recommends any Class 10 MicroSD card. 16gb will be enough capacity for a day’s worth of recording.
When using Internal Sidecar Recording, the SD Card MUST be formatted each day after the data has been backed up.
This can either be done on the LDT-R2 itself or on a computer.
On the LDT-R2:
Menu > Advanced > Format SD Card
On a computer:
CLIPS
and FIRMWARE
It is essential that all Preston MDR and HU firmware is updated prior to building any lens tables or F-Maps. There is a known issue where auto lens select will not work when the Preston units are not updated.
The Preston HU4 can be used with the LDTs - but does not work with auto lens select. If the production wishes to use auto lens select then please use a HU3.
All F-maps must be made on one hand unit and shared to the other units.
Save all F-Maps to the "Other > User" folder to ensure auto lens select feature works.
If no serial port is available on the MDR, the LDT-R2 has a serial loop through port to connect 3rd party devices. Connect the 3rd party device to the serial port of the LDT-R2 and ensure loop through is enabled:
Menu > Settings > SERIAL port > MDR LOOP
There is a known issue between the CineRT and LDT-R2 where data will not show up when connected. If this happens, check the CineRT is set to
Serial Out > MDR
. If this does not resolve the issue, connect everything up as normal then power cycle the LDT-R2.
The LDT-R2 can record and the LDT-V Series can record and stream data from smart lenses with an external port. Lens tables are not required when using these lenses as all data is passed from the lens to the LDT.
A smart lens must be powered from the camera in order to send data to the LDT.
Push the joystick in to enter the menu, use the back button to go back.
Menu > Settings > Advanced > Data source > Pull from lens
Please ensure the handset it running the latest available firmware
Push the joystick in to enter the menu, use the back button to go back.
Menu > Settings > Advanced > Data source > Pull from Nucleus-M
The motors must then be linked to the correct FIZ axis.
Menu > Motor/LDE setup > Focus
Menu > Motor/LDE setup > Iris
Menu > Motor/LDE setup > Zoom
From here MOT 1 - MOT 4 can be selected in accordance to the motor mapping that is set on the Nucleus-M controller.
The motor direction can be set to normal or reverse if required.
Refer to this section if you are recording data externally from the LDT-R2. This mode is only available for digital cameras.
In this chapter you can find details on how to set up a camera in order to record metadata into the raw file headers, depending on the system you are running.
For the RED V-RAPTOR please follow the instructions here.
There is known issue with the RED Camera that stops lens data being displayed. Please ensure that the camera is running firmware 7.02 or later.
In order to enable the LDT-R2 to talk to the camera and to write and display lens metadata, the ET Protocol must be selected:
Menu > Settings > Setup > Communication > Serial
Ctrl Protocol
select: Element Technica
To avoid lenses interfering with the LDT, the smart lens mount needs to be disabled:
Menu > Settings > Setup > Lens
Enable Power to Lens
and Auto-Detect PL Lenses
Don’t worry if the menu is grayed out. This means a smart lens mount is not fitted to the camera.
In order to display lens data as an overlay on an SDI monitor, do the following:
REDMAG
Menu > Settings > Display > Monitor Control > Overlays
On Media
overlay to In Camera
Menu > Settings > Display > Monitor Control > Monitor Setup
Please note that if you require a longer RED cable, the maximum working length is 6ft.
Push the joystick in to enter the menu, use the back button to go back.
Menu > Settings> MODE > RED, Element Tech
Menu > Settings > Advanced > Data source > Local Table
Menu > Settings > Advanced > Data source > Pull from LCUBE
Follow the instructions above omitting the Preston MDR rigging and Data Source
setting. Use the rigging and settings found here to complete set-up.
Please note as the LDT-R2 needs a CTRL port to inject data. If port is not available then A RED Expander Blade (or similar product) is required.
RED V-Raptor running 1.3.1(beta) onwards supports injection recording.
RED Komodo running 1.7.5 onwards supports injection recording.
No settings are required to enable lens data injection - plug the LDT-R2 to the camera following the set-up instructions below.
To enable lens data as an overlay please apply the following communication settings:
MENU > Communication > Connections > Serial > Baud rate = 115200
and,MENU > Communication > Connections > Serial > IP Address = 169.254.1.1
Camera must be power cycled to see the affect of the changes.
Then apply the following settings:
V-RAPTOR
In order to display lens data as an overlay on an SDI monitor, do the following in the V-Raptor menu:
Monitoring > SDI 1/2 > Overlay
> Toggle to Green (enabled)Monitoring > SDI 1/2 > Overlay Mode > Technical
Please note that if you require a longer RED cable, the maximum working length is 6ft.
Push the joystick in to enter the menu, use the back button to go back.
Menu > Settings> MODE > RED, RCP2
Menu > Settings > Advanced > Data source > Local Table
Menu > Settings > Advanced > Data source > Pull from LCUBE
Follow the instructions for Preston above omitting the Preston MDR rigging and Data Source
setting. Use the rigging and settings found here to complete set-up.
There is known issue with the Panavision DXL that stops lens data being displayed. Please ensure that the camera is running firmware 1.01.1 or 1.0.2.3.
In order to enable the LDT-R2 to talk to the camera and to write and display lens metadata, the ET Protocol must be selected:
Menu > Network > Serial
Ctrl Protocol
select Element Technica
.To avoid lenses interfering with the LDT, the lens mount needs to be disabled:
Menu > Setting > Setup > Lens
Disable lens mount
Don’t worry if the menu is grayed out. It means a smart lens mount is not fitted to the camera.
In order to display lens data as an overlay on an SDI monitor, do the following:
REDMAG
Menu > Settings > Display > Monitor Control > Overlays
On Media
overlay to In Camera
Menu > Settings > Display > Monitor Control > Monitor Setup
Please note that lens tables do not need to be built on the LDT-R2 in this configuration as lens data is pulled from the Cmotion or WCU4 handset.
Do not connect an LDT-E Series to the LDT-R2 in this configuration as it will clear incoming lens data.
Push the joystick in to enter the menu, use the back button to go back.
Menu > Settings> MODE > DXL, Element Tech
Menu > Settings > Data source > Local Table
Menu > Settings > Advanced > Data source > Pull from LCUBE
Menu > Settings > Data source > Pull from DXL cmotion
Follow the instructions for Preston above omitting the Preston MDR rigging and Data Source
setting. Use the rigging and settings found here to complete set-up.
In order to inject data into the body of the camera a specialist lens mount is required. Please discuss with the rental house your options or contact DCS directly.
Depending on the lens mount being used, ensure any physical switch is set to EXT.
Sony Venice does not require any setting up to accept the Cooke /i information coming from the 4-pin or 9-pin LEMO installed on the lens mount.
In order to display lens data as overlay on a SDI monitor, do the following:
Menu > Monitoring
Setup
Lens Status
and check Info
If there is no lens data on the monitor or camera when a lens table is loaded on the LDT-R2, check the following setting on the Sony Venice body:
Long press
Menu
>Technical
>Lens Configuration > PL Mt Interface Position > Top
.
If using the 9-pin Sony Venice smart mount, there is a dip switch on the side which can select "LENS" and "EXT". It is recommended this be set to "LENS" under normal operation. In this setting, data from a smart lens will overide the LDT data from the port. To deactivate the smart lens pins select "EXT".
Push the joystick in to enter the menu, use the back button to go back.
Menu > Settings> MODE > Cooke /i
Menu > Settings > Data source > Local Table
Follow the instructions above omitting the Preston MDR rigging and Data Source
setting. Use the rigging and settings found here to complete set-up.
All cables MUST be connected before the camera turns on.
If any cables are unplugged, or the LDT is rebooted while the camera is on, the camera MUST be power cycled.
The LDT MUST be powered directly from the battery/power plate and NOT from the camera.
The required setting can be accessed by holding the Menu button for 2 seconds.
Menu > Technical > Lens Configuration > Lens 12pin > ON
In order to display lens data as overlay on a SDI monitor, do the following:
Menu > Monitoring
Setup
Lens Status
and check Info
If there is no lens data on the monitor or camera when a lens table is loaded on the LDT-R2, check the following setting on the Sony Venice body:
Long press
Menu
>Technical
>Lens Configuration > PL Mt Interface Position > Top
.
Push the joystick in to enter the menu, use the back button to go back
Menu > Settings > MODE > Venice 12pin
Menu > Settings > Data source > Local Table
Menu > Settings > Data source > Pull from LCUBE
Follow the instructions above omitting the Preston MDR rigging and Data Source
setting. Use the rigging and settings found here to complete set-up.
Refer to this section if you are recording data in the LDT-R2. This mode is available for all types of cameras. LDT-R2 requires shutter pulse or record tally from the camera in order to start recording data.
A constant external timecode source must be provided to the LDT-R2 by a timecode generator. The LDT-R2 will not receive timecode directly from a camera. This is by design as timecode is lost when going off speed.
Encoded data is recorded on the MicroSD card.
The SD Card MUST be formatted each day after the data has been backed up.
Please make sure to backup the MicroSD data on a computer after each shooting day in order to avoid data loss.
Frame by frame (FbF) data is recorded onto the MicroSD card’s CLIPS
folder, as a CSV file type. Everytime the camera runs, a new CSV file is created.
The CSV file is matched to the timecode. A new line gets created at every timecode interval.
Read ‘Appendix 2: Internal Recording - CSV File Structure’ to learn more about it.
Select the desired projects FPS.
Menu > Settings> Project FPS
23.98FPS, 24FPS, 25FPS, 29.97FPS, 30FPS
Project FPS must match Timecode FPS.
If running multiple LDT-R2s at once, setting the corresponding camera index is advised.
Menu > Settings> Camera index > A, B, C, ...
Set the roll number on the LDT to the corresponding roll loaded on the camera. This does not require removing or changing the SD card. To set the roll number:
Menu > Settings> Roll > 001, 002, 003, ...
It is essential to change the roll on the LDT every time the roll is changed on the camera so they match. This information is used to link the data in post production.
When Internal Recording is set, the LDT-R2 changes the Lens Details homepage to fit the TC and REC icons.
After connecting the timecode cable from a timecode generator device into the TC port on the LDT-R2, the Lens Details homepage will show a stable TC icon meaning that the LDT-R2 is receiving a good timecode. A flashing TC icon means that the LDT-R2 is receiving timecode but at the wrong FPS, change the LDT-R2 or the timecode generator project FPS to match. No TC icon means that the LDT-R2 is not receiving any timecode, check the cable direction if using a unidirectional timecode cable.
When recording a REC icon will pop-up under the TC icon.
If the LDT-R2 cannot receive a record trigger from the camera, then recording can be controlled from a Preston HU3.
To enable the Preston start/stop functionality, on the LDT-R2:
Menu > Settings > Mode > MDR, SD Card
To verify the LDT-R2 is recording:
When manually starting and stopping the LDT-R2 it is important to limit the clip lengths to match those being recorded by the camera. Recording all day (for instance) can result in loss of data.
If the LDT-R2 cannot receive a record trigger from the camera or the the Preston HU3, recording can be manually started and stopped from the device itself when in any SD Mode.
To verify the LDT-R2 is recording:
When manually starting and stopping the LDT-R2 it is important to limit the clip lengths to match those being recorded by the camera. Recording all day (for instance) can result in loss of data.
This funtion is allows the user to check that clips are recording to the SD Card as expected.
Menu > Browse clips
When using Internal Sidecar Recording, the SD Card MUST be formatted each day after the data has been backed up.
Arri film cameras are equipped with a 3-pin RS power out which provides power and shutter pulse for the LDT-R2.
Push the joystick in to enter the menu, use the back button to go back.
Menu > Settings> MODE > Film, SD card
Menu > Settings > Advanced > Data source > Local Table
Menu > Settings > Advanced > Data source > Pull from LCUBE
Follow the instructions above omitting the Preston MDR rigging and Data Source
setting. Use the rigging and settings found here to complete set-up.
When using Internal Sidecar Recording, the SD Card MUST be formatted each day after the data has been backed up.
Panavision XL2 cameras are equipped with a 10-pin Lemo connector which provides power and shutter pulse for the LDT-R2.
Alternatively, Panavision provides a splitter box to duplicate the 10-pin lemo on the camera. If available, use the RUNPV (gray) cable to connect the 10-Pin Lemo on the camera to the LDT-R2 PWR. Plug the MDR 3 as per usual.
Push the joystick in to enter the menu, use the back button to go back.
Menu > Settings > MODE > Film, SD card
Menu > Settings > Advanced > Data source > Local Table
Menu > Settings > Advanced > Data source > Pull from LCUBE
Follow the instructions above omitting the Preston MDR rigging and Data Source
setting. Use the rigging and settings found here to complete set-up.
DCS always advise to use injection recording on RED cameras. However, if the production requires frame by frame data to be recorded internally on the SD card of the LDT-R2 follow the procedure below.
When using Internal Sidecar Recording, the SD Card MUST be formatted each day after the data has been backed up.
RED cameras can send out Rec Tally from the CTRL port. In order to allow the LDT-R2 to receive a recording signal from the camera and to write metadata, the RED Command Protocol (RCP) must be enabled.
Menu > Setting > Setup > Communication > Serial
Ctrl Protocol
select RED Command Protocol
Push the joystick in to enter the menu, use the back button to go back.
Menu > Settings > MODE > RED, SD card
Menu > Settings > Advanced > Data source > Local Table
Menu > Settings > Advanced > Data source > Pull from LCUBE
Follow the instructions above omitting the Preston MDR rigging and Data Source
setting. Use the rigging and settings found here to complete set-up.
When using Internal Sidecar Recording, the SD Card MUST be formatted each day after the data has been backed up.
When setting up the Raptor & Komodo please use the camera's factory default IP address shown below to communicate with the LDT-R2. This will allow the LDT-R2 to receive a recording signal from the camera to write metadata.
Menu > Communication > Serial > Baud rate: 115200
Menu > Communication > Serial > IP: 169.254.1.1
Push the joystick in to enter the menu, use the back button to go back.
Menu > Settings > MODE > Komodo, SD card
Menu > Settings > Advanced > Data source > Local Table
Menu > Settings > Advanced > Data source > Pull from LCUBE
If using the LDT-V Series for virtual production with the RED Komodo and Raptor it is important that none of the network IP addresses in the LDT-V Series Network menu are set to 169.254.x.x. This address range is used by the Komodo and Raptor, and will cause an IP conflict between devices.
DCS always advise to use injection recording on the Panavision DXL camera. However, if the production requires frame by frame data to be recorded internally on the SD card of the LDT-R2 follow the procedure below.
When using Internal Sidecar Recording, the SD Card MUST be formatted each day after the data has been backed up.
The Panavision DXL is equipped with a 3-pin RS AUX power out which provides power and shutter pulse for the LDT-R2.
Push the joystick in to enter the menu, use the back button to go back.
Menu > Settings> MODE > SD Card, RED
Menu > Settings > Data source > Local Table
Menu > Settings > Data source > Pull from LCUBE
Menu > Settings > Data source > Pull from DXL cmotion
Menu > Settings> MODE > SD Card, RED
Follow the instructions above omitting the Preston MDR rigging and Data Source
setting. Use the rigging and settings found here to complete set-up.
DCS always advise to use injection recording on the Sony Venice camera. However, if the production requires frame by frame data to be recorded internally on the SD card of the LDT-V Series follow the procedure below.
When using Internal Sidecar Recording, the SD Card MUST be formatted each day after the data has been backed up.
Please note this set-up requires an LDT-V Series as it requires an ethernet port on the LDT. The LDT-R2 cannot support this set-up.
If simultaneous data streaming and recording is required - this set-up cannot support a wired connection for both. Please use the LDT-V2 wireless for data streaming and the ETH port to connect the camera.
There is a known issue when the LED light on the Venice is blinking due to low battery. This blinking send pulse triggers to the LDT. This will lead small clips being generated while filming. It is essential that battery level is checked between take and changed when close to low to maintain the integrity of the lens data. Please note that the LED blinking when the mag is running low does not create the same issue.
The LDT-V Series gets the start/stop trigger and filenames from the ethernet port of the camera.
Technical > Network > Setting > LAN
Technical > Network > LAN > DHCP > Off
Technical > Network > LAN > IP Address > 192.168.2.50
Technical > Network > LAN > Subnet mask > 255.255.255.0
Technical > Authentication > User name > admin
Technical > Authentication > Password > ABCD1234
Push the joystick in to enter the menu, use the back button to go back.
Menu > Settings > MODE > SD Card, Venice
Menu > Settings > Advanced > Data source > Local Table
Menu > Settings > Advanced > Data source > Pull from LCUBE
If the IP Address of the camera was changed, the settings on the LDT-V2 must be altered to reflect this.
Menu > Settings > Network > DCS streaming > Venice
From here you can alter the:
Follow the instructions above omitting the Preston MDR rigging and Data Source
setting. Use the rigging and settings found here to complete set-up.
DCS always advise to use injection recording on an ALEXA Camera, for the Mini and Mini LF use the LDT-M2 and for large body ALEXAs use the LDT-A2. However, if the LBUS port on the lens mount (on the Mini and Mini LF) is unavailable or the production requires frame by frame data to be recorded on an SD card, please use the LDT-V Series following the procedure below.
When using Internal Sidecar Recording, the SD Card MUST be formatted each day after the data has been backed up.
Please note this set-up requires an LDT-V Series as it requires an ethernet port on the LDT. The LDT-R2 cannot support this set-up.
If simultaneous data streaming and recording is required - this set-up cannot support a wired connection for both. Please use the LDT-V2 wireless for data streaming and the ETH port to connect the camera.
In order for the LDT-V Series to receive the start/stop signals, and file names from the camera the ALEXA Mini/Mini LF/35’s Network setting have to be set to the following:
Menu > System > Network/Wifi > LAN IP Mode > Static
Menu > System > Network/Wifi > LAN Static IP > 192.168.0.100
The ALEXA 65, LF SXT, XT do not requre changes to their network settings.
Push the joystick in to enter the menu, use the back button to go back.
Menu > Settings > MODE > SD Card, Mini LF
Menu > Settings > MODE > SD Card, Alexa
Menu > Settings > Advanced > Data source > Local Table
Menu > Settings > Advanced > Data source > Pull from LCUBE
If the IP Address of the camera was changed, the settings on the LDT-V2 must be altered to reflect this.
Menu > Settings > Network > DCS streaming > Mini LF
From here you can alter the:
Follow the instructions above omitting the Preston MDR rigging and Data Source
setting. Use the rigging and settings found here to complete set-up.
The LDT-R2 can record lens data in for other cameras not outlined here. In this instance, internal recording must be used and a timecode supplied. More information about internal recording can be found here.
When using Internal Sidecar Recording, the SD Card MUST be formatted each day after the data has been backed up.
When using the LDT-R2 with a camera not supported by DCS, recording will have to be manually triggered and stopped. This can be done on the LDT-R2 device itself or on the Preston Hand Unit - follow the links for more information.
Push the joystick in to enter the menu, use the back button to go back.
Menu > Settings> Mode > Film, SD card
Menu > Settings > Advanced > Data source > Local Table
Menu > Settings > Advanced > Data source > Pull from LCUBE
Follow the instructions above omitting the Preston MDR rigging and Data Source
setting. Use the rigging and settings found here to complete set-up.
The LDT-V Series can live stream data to the DCS Unreal Engine Plugin. Information on installing and setting up the plugin can be found here:
https://support.dcs.film/DCSUnrealEnginePlugin
DCS also has a lens data emulator to assist with initial set-up and troubleshooting. Instructions on where to find this and how to set it up can be found here:
https://support.dcs.film/en/LDT-Emulator/DCSLDTEmulator
If manually moving the lens axes or using a motorised remote focus system other than a Preston MDR or ARRI LBUS system, the LDT-E Series can be attached to the lens to report lens movement back to the V Series. More information on setting up the LDT-E Series can be found here.
Depending on the production’s requirements, the LDT-V Series can stream, stream and inject or stream and record lens data.
The LDT-V2 can support both wired and wireless connections. The LDT-V1 is a wired only solution.
The DCS wireless system requires a DCS receiver (LDT-RX1), it cannot be paired with 3rd party routers or products. Contact DCS for more information.
The LDT-V2 contains a powerful transmitter module that works at sub Wi-Fi frequency. This will cut through the wireless noise of a busy set to deliver excellent results when paired with the LDT-RX1 receiver unit. Manual for the LDT-RX1 can be found here.
All other rigging and settings found in the manual should be followed with the exception of connecting an EVP cable which is not required for wireless streaming.
The LDT-V2 transmits at all times so does not need to be toggled on or off.
The frequency can be changed between 2200mhz and 2500mhz. It is set to 2405mhz by default. To adjust this setting manually:
Push the joystick in to enter the menu, use the back button to go back.
Menu
> Settings
> Freq
> XXXX
Please note that if frequency is changed on the LDT-V2 the corresponding frequency will need to be changed on the LDT-RX1, details here.
If only streaming data to the DCS Unreal Engine Plugin the LDT-V Series is camera agnostic. The LDT-V Series can get lens movement information from 3 sources; A Preston Follow Focus System (lens tables required), an LDT-E Series encoder (lens tables required) or a smart lens (no lens tables required).
Push the joystick in to enter the menu, use the back button to go back.
Menu > Settings > Data source > Local
Menu > Settings > Data source > Pull from Lens
Menu > Settings > MODE > Virtual Production
It is possible to enable streaming when using the injection or internal recording features of the LDT-V Series. Rigging and settings are specific to the camera it is being used on. Please find the camera specific instructions for rigging and set-up in the injection or internal recording sections.
In addition to those instructions also do the following:
Follow recording/camera rigging instructions in the relevant section and,
Push the joystick in to enter the menu, use the back button to go back.
Menu > Settings > Data source > Local
or Pull from Lens
for smart lenses.Menu > Settings > MODE >
(Please consult the relevant section)In order to stream live lens data to the DCS Unreal Engine Plugin please ensure the following settings are configured.
Menu > Settings > Network > Remote IP >
Set to the IP of the target machine,Menu > Settings > Network > Remote Port >
The default DCS port is 33322.Menu > Settings > Network > Local IP >
User defined (change if the DCS Unreal Engine Plugin is set to something different or there is other traffic on this port),Menu > Settings > Network > Router IP >
User defined,Menu > Settings > Network > Netmask >
User defined,Menu > Settings > Network > DCS streaming > Service > On
To stream data from an LDT-V Series to multiple sources:
Menu > Settings > Network > Multicast > on
Menu > Settings > Network > Remote IP >
Change to a multicast address IP within the range of 224.0.0.0 to 239.255.255.255 e.g 239.0.0.1To control what data is sent to the target machine the LDT-V Series can enable/disable certain data on the device.
Menu > Settings > Advanced > DCS Protocol > RAW encoder > Disable/Enable
Menu > Settings > Advanced > DCS Protocol > Tilt/Roll > Disable/Enable
Regarding issues with connecting the LDT-V2/LDT-RX1 to network equipment:
The DCS devices auto negotiate on Ethernet upto a rate of 100Mbps. The network equipment must be able to negotiate down to this rate. Equipment limited to 10G/1Gbps may require additional interfacing.
Creating a lens table is essential to the encoding process. It requires inputting the relevant lens information (lens name, brand, serial number etc.) and then inputting all of the marks from the axis’ (focus/iris/zoom) for each lens. The following guide explains this process.
Before creating the first lens table, please review and adjust the following settings accordingly.
Data source should always be set to Local Table. If for some reason it has been set to Pull from Remote please change it back to Local Table.
Pull from remote is an advanced feature and should only be used when advised by someone from DCS.
Menu > Settings > Advanced > Data Source > Local table / Pull From Remote
If enabled, Auto Lens Select will automatically change the lens on the LDT-R2 when the F-Map is changed on the Preston Hand Unit 3 (HU3).
Lens details can be manually added (F-Map OFF), however the LDT-R2 can pull the lens details from the Preston HU3 library to streamline this process and keep the naming convention for the lens tables consistent with what is in use on the HU3 (F-Map ON). Go to the Using Auto Lens Select and F-Map chapter for further information regarding using this system during the show.
It is essential that all Preston MDR and HU firmware is updated prior to building any lens tables or F-Maps. There is a known issue where auto lens select will not work when the Preston units are not updated.
All F-maps must be made on one hand unit and shared to the other units.
Save all F-Maps to the "Other > User" folder to ensure auto lens select feature works.
Please note that the auto lens select feature is not available with the HU4 handset currently.
Depending on the focus puller’s needs, the LDT-R2 has two modes on which a lens can be loaded during the day and encoded in the unit. This will dictate how a lens is encoded and the interaction with the LDT-R2 during the day.
Auto Lens Select automatically changes the lens on the LDT-R2 when the lens is changed on the Preston HU3. In order to use Auto Lens Select, the Focus Puller must use F-Mapping on the Preston HU3 and MDR-3.
There is no need for F-mapping to stay on during a shot, and can be turned off right after the lens is loaded; the selected lens will stay loaded on the LDT-R2 till a new lens is selected on the Preston HU3. In fact, the only details required from the F-Map by the LDT-R2 are the brand, name, focal length, serial number and type of the lens. As the lens tables are created on the LDT-R2 the F-Map lens tables only need to be partially completed.
When creating a new lens table, by selecting the desired lens on the Preston HU3, this will auto-populate the lens brand, lens name, lens type, focal length and serial number to the LDT-R2.
If F-Map is disabled, when creating a new lens table on the LDT-R2, the lens brand, lens name, lens type, focal length and serial number needs to be manually entered. When a lens is changed on the camera, the new lens needs to be manually selected on the LDT-R2.
The LDT-R2 cannot currently support auto lens select with the HU4. It is recommended that all hero F-Maps are initially generated on HU3 if looking to use auto lens select. If a HU4 is the only available please see Adding a New Lens Without Using F-Map.
To ensure that Auto Lens Select works on all devices when using multiple cameras follow this workflow:
It is recommended at the beginning of each new job that all F-Maps are cleared from the HU3 to avoid duplicating lenses.
Turn on Auto Lens Select
Menu > Settings > Auto Lens Select > On
Mount a new lens to the camera. On the Preston MDR press the calibrate button. This will calibrate the LDT-R2 as well. Once calibration finishes, on the Preston HU3 create a new F-Map of the lens attached to the camera. If the lens has already been F-Mapped, select it on the Preston HU3. In the LDT-R2 menu:
Menu > Add Lens
The LDT-R2 will display a message with the name of the lens. If the lens name matches the lens mounted on the camera and the one loaded on the Preston HU3.
ACCEPT
to proceed.Lens details will auto-populate. Proceed to Creating a New Lens Table chapter.
Please note the HU4 may provide incorrect lens names and serial number even when auto lens select and F-mapping are turned off. If a lens name is provided when adding a lens on the LDT-R2 please select the 'other' option and input the correct details.
Turn off Auto Lens Select
Menu > Settings > Auto Lens Select > Off
Turn off F-maps on the Preston HU3/HU4
Mount a new lens to the camera and calibrate:
Menu > Calibrate LDT-E
Once calibration finishes, from LDT-R2 menu:
Choose: Menu > Add Lens.
Select an existing brand from the list, or input a new one if it isn’t listed.
To add a new brand, use the joystick up/down to scroll through the available characters. One click for a single increment, hold for rapid scroll. Click right to type the next character.
Once complete, press the back button to go back to the brand list and select one to proceed.
Select Prime or Zoom accordingly to the mounted lens on the camera.
Select an existing lens or add a new lens name if it isn’t listed.
To add a new lens name, use the joystick up/down to scroll through the available characters. One click for a single increment, hold for rapid scroll. Click right to type the next character.
Once complete, press the back button to go back to the brand list and select one to proceed.
Add a new focal length or focal range depending on the mounted lens on the camera.
Type the new focal length or focale range. Use the joystick up/down to scroll through the numbers. One click for a single increment, hold for rapid scroll.
If it is a zoom lens, click right to finish typing the focal range.
Once the focal length or focal range is entered, press the back button to go back to the focal range list and select one to proceed.
Enter a new lens serial number. use the joystick up/down to scroll through the available characters. One click for a single increment, hold for rapid scroll. Click right to type the next character.
Once the serial number is entered, press the back button to proceed.
Mapping a new lens table is crucial to ensuring that the data encoded throughout the production is precise.
When mapping a lens, a methodical process needs to be adopted on both the remote lens control side and on the LDT-R2 side. As standard practice, DCS suggests to enter a mark point on the LDT-R2 for each engraved mark and let the LDT-R2 interpolate the rest of the data.
Ensure that the lens calibration happens without any motor slip. When moving the lens axis with a remote handset, mark alignment should always be achieved from the same direction to avoid slack on the lens.
In order to retain the full precision of the focus knob, we recommend turning off F-Mapping during the creation of new lens tables.
Establish which direction will be used on the Preston HU3 and on the Single Channel Handset (SCH) for the run of show (close focus, infinity, wide open iris, close iris, wide zoom, tight zoom). DCS suggests keeping it consistent throughout the whole set of lenses.
Do not move Preston Motors or change direction while encoding the lenses unless required by rigging purpose.
As a general practice, when mapping a lens on the LDT-R2, always keep close focus on the left, wide open iris on the left and wide zoom on the left. An example below. If the physical movement of a lens axis is the reverse of the other lenses, then map it in the opposite direction on the LDT-R2 to avoid having to reverse motor directions each time this lens is recalled.
Make sure to never change the F-Map on the Preston HU3 while mapping a lens on the LDT-R2.
Please check the motor direction on the LDT-R2 is on Normal before proceeding.
To check the motor direction
Menu > Motor direction
More information regarding motor direction go to Changing the Motor Direction chapter
Once all the lens information is entered, select either ‘Focus’, ‘Iris’ or ‘‘Zoom’ (if a Zoom lens is being used) axis to start mapping the lens.
Use the Preston focus knob to move through the span of the axis, the dot on the LDT-R2 display will move along the horizontal line. Ensure the dot reaches each end of the line. If not, check if there were any slips during calibration or disable F-Map on Preston HU3.
Set the units of measurement for focus by pushing the joystick UP. Choose metres or feet.
Set the lens to the closest focus mark.
On the LDT-R2 press the joystick to enter the first mark, a pop up window will ask you to select the focus value.
Use the joystick to select the required value:
LEFT / RIGHT
moves between pre-populated numbers: 0’ 1”, 3’ 0”, 10’ 0”, 30’ 0”, 100’ 0”, INF
UP / DOWN
for fine adjustments.Push the joystick to confirm selection.
Proceed for each desired engraved focus mark.
Once completed, push the back button to go back to the Edit Lens Table menu.
Use the Preston HU3 slider or Preston SCH to move through the span of the iris axis, the dot on the LDT-R2 display will move along the horizontal line. Ensure the dot reaches each end of the line. If not, check if there were any slips during calibration.
If a Single channel iris handset is being used we strongly recommend you use it to make the maps.
Set the lens to wide open.
On the LDT-R2 press the joystick to enter the first mark.
A pop-up window will ask you to select the T-Stop value, use the joystick to select the required value:
LEFT / RIGHT
moves between stops: T0.7, T1, T1.4, T2, T2.8, T4, T5.6, T8, T11, T16, T22, 32, T45, T64, T90
UP / DOWN
for fine adjustments,Push the joystick to confirm selection.
Proceed for each desired engraved iris mark.
Once completed, push the back button to go back to the Edit Lens Table menu.
Use the Preston Microforce to move through the span of the axis, the dot on the LDT-R2 display will move along the horizontal line. Ensure the dot reaches each end of the line. If not, check if there were any slips during calibration.
A map can be created without the Microforce but it’s very important that the Zoom Direction has been checked before you make the map, so we would recommend using the Microforce.
Set the lens to wide zoom.
On the LDT-R2 press the joystick to enter the first mark.
A pop-up window will ask you to select the zoom value, use the joystick to select the required one:
LEFT / RIGHT
to increase/decrease by 10mm,UP / DOWN
for fine adjustments.Push the joystick to confirm selection.
Proceed for each desired engraved zoom mark.
Once completed, push the back button to go back to the Edit Lens Table menu.
Prior to saving the lens map we suggest testing its accuracy. This can be done by pushing down the joystick when in one of the axes to enter the test window. Compare what is displayed here with the engraved marks on the lens to ensure the table is accurate.
Press the back button to go back.
The LDT contains a pre-built Lens Table intended for troubleshooting purposes.
Menu > Edit Lens > DCS Zoom test 11-110 (1)
This can only be selected with Auto lens select turned off.
Once all the required values have been encoded, click on ‘SAVE’ to save the lens table.
A message will prompt upon successful completion.
A lens table can be edited. New points can be added, existing points can be removed or a lens table can be permanently flipped.
Menu > Edit Lens
If a point gets added by mistake or needs repositioning it can be removed.
In order to delete an existing point push the joystick to the left. Move the controller to the desired point. Push the joystick to remove the point.
Press the back button to go back.
If an axis map needs to be permanently reversed push the joystick to the right, then push the joystick to confirm.
If a map needs to be temporarily reversed we suggest to reverse the direction of the motor.
Menu > Motor direction
Camera operators may wish to manually control the zoom (or other axis) instead of using a motor that feeds data to the MDR. A lens enoder can be used with a motor, or in replacement of, allowing the LDT-R2 to still gather the lens movement data.
DCS has its own brand lens data encoder called LDT-E Series. These are plug and play devices so there is no need to create a new or separate lens table when using them.
Note: the direction of the motor might need to be reversed: please go to the Changing the Motor Direction chapter.
A video tutorial explaining the set-up of the LDT-E1 can be found here
The LDT-E Series have a manual switch to set the axis to Focus, Iris or Zoom.
If using an LDT-R2/LDT-V Series without a Preston system:
Menu > Calibrate LDT-E
If using an LDT-A2/LDT-M2 with a Preston system:
If using an LDT-R2/LDT-V Series with a Preston system:
Then manually rotate the axis which is attached to the Lens Data Encoder from one end, pause for a second, then rotate to the other end. The LDT-E Series should now show as calibrated in the on-screen display.
If for rigging purposes a lens motor or lens encoder need to be reversed:
Menu > Motor direction
and select Reverse
on one of the axes.Specific data can be shared between LDT-R2's and the LDT-V Series to save time and ensure consistency across multiple set-ups.
Lens tables can be shared between all LDTs with a Micro SD slot. Please note that lens tables made using the LDT-A2 and LDT-M2 on the ARRI LDA system are a different file format and cannot be shared to the LDT-R2/V Series (and vice versa).
The LDT-R2 saves individual lens tables as .XML files to the MicroSD card. If multiple LDT-R2s are being used, these lens tables can be shared between devices.
Insert the MicroSD Card with the lens tables on into a computer,
Copy the .XML files from the "LENSES" folder onto the hardrive,
Insert a formatted MicroSD card (how to format a MicroSD card for the LDT-R2),
Copy the .XML files to the "LENSES" folder on the new MicroSD card.
Backup the "LENSES" folder when any new lenses are added to the on the MicroSD card to avoid data loss in case of corruption.
All settings of a unit can be downloaded to the MicroSD card and uploaded to a different unit to mirror all settings.
Config files can only be shared between specic models. I.e. LDT-R2 config files will work with LDT-R2 units, but LDT-V1 config files will not work with LDT-V2 units.
When uploading config files to a unit all original settings of that unit will be lost. Either back-up the original config file or make a note of device specific settings such a network addresses and camera index.
To save the config file:
This will save a text file called 'Config' on the Micro SD. If a config file is already on the MicroSD it will overwrite it.
To share the config file with a different unit:
Each .XML file is named after the lens brand, focal length and last 3 digits of the serial number. Examples:
AOZ24987.XML
Angenieux Optimo Zoom 24-290mm sn.11218987
CVZ25324.XML
Cooke Varotal Zoom 25-250mm sn.5640324
ZU135767.XML
Zeiss UltraPrime 135mm sn.8185767
AS047211.XML
ARRI Signature Prime 47mm sn.9899211
If the user decides to not use F-Map, the lens database can be organised as a list or as folders.
It is essential that a test is done for each workflow established on the show before shooting. The tests involve shooting with the LDTs set-up, followed by a round trip of the data where the metadata (however recorded) is married to the EXRs so it is available for vendors in post. This should be coordinated between VFX, Camera, the Lab, Pulls house and Vendors. The goal of these tests are to provide reassurance that all data will be accurate when recieved by vendors and to catch any issues in the pipeline.
DCS can be involved in any pipeline discussions either by attending an initial meeting or being looped into emails if additional support is required. Email info@dcs.film.
Below are the descriptions of how to do the camera portion of the tests.
Allow approximately one hour per camera type being used on the production.
The test will involve recording the metadata with a camera and recording a separate feed from the camera with an overlay to verify the data is correct at the final stage of the test. We recommend using a zoom lens (if any are being used during the shoot) in order to check all three axes.
Three tests are recommended and will involve recording a visual source of the data in the camera with the LDT-R2 recoding the metadata as a sidecar to verify the data is correct at the final stage of the test. DCS recommend using a different lenses for test one and two and a zoom lens specifically for the third racking test (if any are being used during the shoot) in order to check all three axes.
Menu > Settings > Camera Index
Set to T or what letter the test mags are labelled with,Menu > Settings > Roll
and set to the current test magIt is very important that the clip number of the camera mag and LDT clip number match at all times. Do not run the camera without the LDT attached.
For Each test a written visual representation of the FIZ values is required, for instance a clapper board with the lens values written on it.
After completing the tests remember to set the Camera Index on the LDT-R2 back to the corresponding camera letter.
Please be aware that the extreme values in the CSV/EXR during the racking test may exceed the values in the image slightly. Most lenses have hard stops that go further than the values written on the lens. This is normal and should only flag an issue if the values far exceed the values displayed on screen.