-
MediaCentral 2024.2 – Now available! (03/07/2024)
From an
enhanced editing experience with audio waveforms to quicker ways to search and
more capability for newsroom producers, MediaCentral 2024.2 boosts the adoption
of MediaCentral | Cloud UX for existing customers.
MediaCentral 2024.2 is now available for sale.
Some
of the new features in MediaCentral 2024.2 include:
Audio
waveforms:
Users editing
sequences and news sequences can now enable waveforms in the timeline for a
better audio editing experience. This is a major step
forward in the editing experience in MediaCentral, meaning more users can use a
web browser for editing, rather than a thick client requiring dedicated
hardware.
Rundown
app improvements:
The Rundown app now
enables users to print stories and to increase the font size, increasing
adoption and a move away from the thick iNEWS client. This simplifies the
hardware estate which a customer has to run and support, saving them time and
manpower effort to maintain.
New
search capabilities:
Now users can right clip on the folder
to run a search in the Browse app. Easily searching directly in a folder may
seem a small thing, but it is a major timesaving feature, and one which was
previously only available in legacy products.
-
Avid MediaCentral | Cloud UX feature packs – Released (February 8, 2024)
Avid MediaCentral Cloud UX feature
packs has been released as of February 8th, 2024. Below are versions
and ReadMe of the feature packs that were released recently:
What’s Fixed in v2022.3.25:
- Bug Number:
MA-6833, MA-6851, MA-6853, MA-6902. If you use Ctrl + drag and drop to
create a copy of a story text in the Rundown app that includes production
cues, the duplicate might be created with cues that have identical anchors
IDs instead of unique IDs.
- Bug Number:
MA-6896, MA-6897. Copying and pasting production cues or MOS objects with
production cues into a segment of another story causes the story to become
corrupted and a story lock error message to occur.
What’s Fixed in v2023.7.7:
- Bug Number:
JP-9033. (Multi-Site only) If a user creates a Browse favorite for a
Remote site through a web browser (Chrome), the remote site is incorrectly
visible to a user that accesses MediaCentral Cloud UX through a panel —
such as the MediaCentral | Panel for Media Composer, or the MediaCentral |
Panel for 3rd Party Creative Tools.
- Bug Number:
MA-6833, MA-6851, MA-6853, MA-6902. If you use Ctrl + drag and drop to
create a copy of a story text in the Rundown app that includes production
cues, the duplicate might be created with cues that have identical anchors
IDs instead of unique IDs.
- Bug Number:
MA-6850. Reloading a queue with stories after entering an invalid value in
a RUNS production cue will no longer prevent stories from loading.
- Bug Number:
MA-6894. Previously, users would sometimes experience a noticeable lag
when moving or removing a bulk of stories, with sequences attached, from a
queue with more than 200 stories in it.
- Bug Number:
MAM-19869. The Location Service returns wrong endpoint types for
"Local" types.
- Bug Number:
MTTO-4251. The Collaborate app fails to send summary emails, even if the
Email Settings are correctly configured in the Configuration Settings app.
- Bug Number:
MX-9680. In the Storyboard tab, when you click in a marker comment and
start typing or removing characters, the current cursor position is
ignored and the edits are applied to the end of the comment.
- Bug Number:
SAK-3109. Continuous MediaCentral Sync jobs might get stuck in a Running
state if the remote import metadata step fails.
Both 2022.3.25 & 2023.7.7 can
be found on the Avid Download Center
under Avid MediaCentral LTM
2022.3.25 under Previous
Releases/Patch
2023.7.7 under Current
Releases/Patches
What’s Fixed in v2023.12.1:
- Bug Number:
CCUX-9080. After upgrading MediaCentral Cloud UX from version 2023.7 to
2023.12, the Acquire clip manager pod fails to start in some cases.
- Bug Number:
JP-9015. When accessing MediaCentral Cloud UX through panels, such as
theMediaCentral | Panel for Media Composer, or the MediaCentral | Panel
for 3rd Party Creative Tools, the Browse app inappropriately displays
remote modules for sites connected through a Multi-Site environment.
- Bug Number:
MX-9646. In the Avid MediaCentral | Panel for 3rd Party Creative Tools, if
you open an asset from the Search app, the Storyboard tab shows an
"Asset is not loaded" message.
- Bug Number:
MX-9680. In the Storyboard tab, when you click in a marker comment and
start typing or removing characters, the current cursor position is
ignored and the edits are applied to the end of the comment.
- Bug Number:
PLAD-877. As documented in the MediaCentral Cloud UX Installation Guide,
the avidctl tools hoverscrub-clean script fails to clean the Hoverscrub
cache due to a change in folder structure.
- Bug Number:
PRS-2667. The platform-locations feature pack is only installed when the
AWS Elemental (aws-elemental) feature pack is installed. Now, the
platform-locations feature pack is also installed when the AWS S3 Storage
Connector (awsstorage), Azure Storage Connector (azure-storage) or GCP
Storage Connector (gcp-storage) feature packs are installed.
2023.12.1 can be found on the Avid Download Center under Avid MediaCentral
Patches
-
MediaCentral | Production Management Media Indexer 2022.3.5 – Released 12/11/2023
Great news… MediaCentral | Production Management
Media Indexer 2022.3.5 is now available in the Avid Download Center (Login and password required).
Software Location: MediaCentral |
Production Management Media Indexer 2022.3.5 files can be found in the Download
Center under Avid MediaCentral LTM/Previous Releases/Patches
What’s Fixed in 2022.3.5: The following have
been fixed.
Interplay Access Fixes:
- Bug Number: IPI-3501. There was an unexpected issue with the
Interplay Access 2022.3.4 (macOS only) installer where users were unable
to launch 2022.3.4 Interplay Access on macOS Ventura (13.4.0). This
release provides a new Interplay Access (macOS) installer that fixes this
issue.
Media Indexer Fixes:
- Bug Number: SAK-2954. We have updated ActiveMQ to a version that
fixes a remote code execution security issue.
- Bug Number: IPI-3445. Media Indexer will not trigger Format
Independent (FI) indexing for some files during a full reindex.
- Bug Number: IPI-3518. Media Indexer 2022.3.4 does not create
enough CLASSIC Indexing workers, meaning the worker count is different
compared to previous versions. This results in slow indexing
- Bug Number: IPI-3521. There is an issue where two different Media
Indexers are indexing some files with missing data for the CLASSIC
approach. The file is present in the CLASSIC index, but there is no
Quality Descriptor (no value) for the New Qid field.
For example, one Media Indexer will put
the file in the index, but will have a NULL value for the New Qid field when
checking into the Storage Browser/Search. The other Media Indexer will put the
file in the index, but if you check in the Storage Browser/Search for the path,
you will see that the Quality Descriptor is missing, with error “Quality
Descriptor not found!”
These problems are causing issues in
MediaCentral Cloud UX, as it is unable to relink to this file and displays a
“Media Offline” message.
Transcode Fixes:
- Bug Number: IPI-3472. When transcoding a sequence with unrendered
subcap-effects, the transcoder ignores the “letter spacing” setting. After
transcoding, 'letter spacing” looks like it's set to a value of -1 or 0.
- Bug Number: IPI-3444. When attempting to Transcode an UHD 50p XAVC
Intra Class 300 CBG to proxy H.264 720p50 800kbps, Transcode will generate
the following error message:
Exception: FatalProc() Assertion
failed: IndexDuration() <= IndexEntryCount(),
fileName=s:\coresw\ame\src\msm\mxfmappersegmented.c, line=254
- Bug Number: IPI-3190. When transcoding to the H264 “CONSOLIDATE”
profile for the subclips, there is a relink fail error that results in a
slowdown of transcodes of subclips to Consolidate / Transcode from Access
including many that report relink fails and aborts.
Installation and Configuration:
- Bug Number: RELENG-3176. When unzipped, the Production Management
installer might include long file path names that are incompatible with
some versions of Windows. If you need to copy unzipped installation
packages from one location to another, Windows 10 and Windows 2016 provide
a registry setting that allows for these long path names.
You can find this setting under:
Computer Configuration > Admin Templates > System > FileSystem >
Enable Win32 long paths
ReadMe: The new
ReadMe for MediaCentral | Production Management 2023.3.5 can be found here.
-
Where have the posts gone?
Is it just me or is there only 1 post in here now? (well, 2 now!)
Thanks
-
Mediacentral production 2022/2023 Media Indexer performance
Hi Mediacentral production users.
I have also raised these question to support and in the ACSR mailing list.
While Avid indicated the Mediacentral production + Media composer (and dynamic relink) were solved, it seems there are still some issues although things are a lot better then 1-2 years ago.
In general I see 2 issues
1. Media Indexer threads set for each worker are not consistent with nr of logical processors. In 2022.3.x the number of threads for the classic scanning and indexing workers and mongodb scanning worker are set too low. mongodb indexing worker is set too high. This is supposedly corrected in 2023.7 media indexer. However while classic scanning worker and mongodb scanning worker are now set to the same amount as the nr of logical processors, classic indexing worker and mongodb indexing worker are still set with double the threads of the available logical processors. As far as I know this was never the case in Media Indexer 2021.3.4 and lower. This is currently being investigated by support.
2. Microsoft windows 2019 server seems to have 1 or more performance issues impacting both local and network file transfers. This is observed on Dell r630 SUU 2023.5 applied windows 2019 server all updates applied. File transfers of large files, read and write, reach 113MB/s through 1GB connections. Folders with small amounts of files (which are expected to be much slower) can cause large variations in file transfer time when copying to a windows 2019 server network share.
Comparing to copying files to a Synology storage shows large differences up to 50% shorter duration = 200% average speed. However when doing multiple attempts, a single attempt can be almost as fast as the synology. It's not consistent. Observered differences between the Synology and a Windows share is that windows shares use SMB v3.1.1 while Synology uses SMB v2.
I became aware of this due to increased backup times of the Interplay Archive database. Backup duration on 2012r2 server (latest update in 2018) to a share on 2012r2 (latest update in 2018) took 3 hours. After update of server hosting file share to 2019 server backup time increased to 67 hours. After update of Mediacentral production Archive engine backup times to file share remained 67 hours. Tested backup to local storage on Archive engine which took 5 hours. Backup to Synology Storage takes 'normal' 3 hours.
In general after updating all Dell r630 2012r2 servers to 2019 server + Dell SUU 2023.5, servers feel normally responsive in explorer. All applications also function normally and no obvious perforance problems are observed in any user interface.
However, both Media composer 2022.12.4 and Cloud UX 2022.3.16 produce occasional sluggish behavior, especially when total system load increases. Saving a sequence and dragging clips into a sequence can all of a sudden take much more time than normal. I have spoken to a few Mediacentral users around the globe and they report having performance related cases open with Avid support.
Through this post I would like to learn if more people experience similar problems and have cases open with Avid support. Feel free to react to this post or email me directly.
Jeroen van Eekeres
-
Issue & fix -- for Cloud UX 2020.4.x sites
|