September 16th 2024
AtomOS 11.10.00 Firmware Release Notes
Ninja V
Installation Instructions
Atomos recommends that your Ninja V is plugged into mains power before commencing the firmware update.
- Insert a compatible, formatted SSD into the Docking Station.
- Unzip the downloaded file and copy the ATOMNJV.FW file to the root of the SSD.
- Eject the SSD (according to operating system guidelines).
- Insert the SSD into the Ninja V.
- If you have an Atomos Connect accessory ensure this is connected to your device before powering on, as the module firmware will also need to be updated as part of this FW release.
- Power on the Ninja V and the firmware update process will begin automatically.
- If your Ninja V is already powered on, you will be prompted to perform the firmware update when a drive containing new firmware is inserted.
- Once the update is complete, your Ninja V will power itself down.
- Power your Ninja V back on and the device will automatically start updating the Atomos Connect accessory.
- To verify if the firmware update was successfully completed, navigate to the main menu and scroll to the info tab.
Note: Once firmware 11.10.00 is successfully installed on the Ninja V, the unit may reboot to update the Atomos Connect firmware. Do not interrupt the firmware installation process.
New Features
AtomOS 11.10.00 introduces a new way to pair your Atomos device to the Frame.io Camera to Cloud service, directly through the AtomOS user interface. It also includes a number of bug fixes and stability improvements.
Pair to Frame.io Camera to Cloud directly from your Atomos device
On-device pairing procedure
- Connect your Atomos Connect-enabled to the Internet, either via Wi-Fi or Ethernet.
- Navigate to the Connect tab in the main menu and select Frame.io as the Connect mode for your device.
- You'll now be presented with a QR code on the left of the menu screen, which takes you directly to the Frame.io App (if it's installed on your Phone), or the https://app.frame.io/ URL if you prefer configuring your projects via the web browser.
- On the right side you'll see a 6-digit-code, with a 120-second timer underneath. This indicates the duration that this pairing code is valid for.
- To pair your Atomos device to a Frame.io C2C Project, enter the Frame.io App, or access the web app via the browser.
- Create a new project with C2C Connections enabled, or enable C2C Connections for existing projects you might already have.
- After choosing your project, head to the C2C Connections tab and select the "Add new device" option.
- Enter the 6-digit-code displayed from your Atomos device's Connect menu into Frame.io's input field and authorize its connection to the Frame.io project you've previously selected via the Frame.io App or web page.
Notes on the Camera to Cloud Recording Mode Configuration
Once the pairing process is completed, your Atomos device presents you with a new menu page that allows you to review your Frame.io pairing status, and it also allows you to configure the recording settings of your device.
- Under Recording Mode, you have the option to switch your device into Single or Dual Record mode. In Single mode, you can upload high quality "deliverable" H.265 files, whilst in Dual mode your device records a high-quality ProRes, or Avid DNx file to the SSD, all whilst generating a smaller file size Proxy which is uploaded to Frame.io in the background.
- The Max Resolution settings is used to define the Resolution of the files you're going to upload.
- Under Quality, you can either choose the LQ (3 Mbit/s), MQ (8 Mbit/s), HQ (15 Mbit/s) or the Custom settings.
- When selecting Custom quality, there will be a button that takes you to a separate page that allows you to dial-in various parameters to fine-tune the specifications of the files you want to upload. Those include Bit Depth (8 or 10-Bit), Bitrate (1-30 Mbit/s), Gop Length, and the option to enable or disable B-Frames.
Bug Fixes & Improvements
- Reduced the delay when switching from Record to Playback mode (and vice versa) when H.265 is selected as the recording codec.
- Resolved an issue that could cause the RTMP streaming output to be interrupted after ~15 minutes.
- Resolved an issue where the Network Role in the Sync Config menu got reset from Client to Server after rebooting the device.
Known Limitations to be resolved in future releases
- It may take up to 10 seconds for Wi-Fi and Ethernet connections to re-established when users switch between record and playback mode. Please allow the system time to automatically reconnect to your network.
- The Pause and Resume playback controls may not be selectable when trying to play back H.265 clips that were recorded with B-frames enabled.
- In some rare instances, A/V Sync drift may be observed whilst the device in NDI RX mode.
- When starting a stream using Wowza in SRT Listener mode, it may occasionally take up to two minutes to detect this device's SRT output.
- Network Record Control is not available when H.265 is selected as the record format.
- Live Streaming is only available when using standard YCC 422 video inputs, and when the record codec is set to either ProRes or DNx. If ProRes RAW or H.265 are selected as the record codec, streaming isn't available.
- If the user boots into ProRes RAW recording mode with a YCC SDI Input, the monitoring image may be incorrect. Monitoring and Recording whilst outputting a RAW signal to the Ninja V in ProRes RAW mode will work as expected.
- If switching between different camera models whilst HDMI Compatibility mode is selected, ensure that you reboot the Ninja V before connecting a new camera.
- In playback mode, selecting the first ProRes RAW file to view, some artifacts may be visible. These are not present in the recorded file and will not appear on any clips played after the first selected clip
- Sluggish performance when using two AtomRemote apps connected to a single Atomos Connect. Please only pair one AtomRemote app per device.