In this video, I dive deep into a persistent issue that has been plaguing Avid Media Composer users, especially those who work with takes that overlap or go "back to ones" over the same portion of the script. Back in 2019, I reported bug MCCET-3289 to Avid Support, and despite being declared fixed in Avid's 2018.12.10 Readme, the bug still lingers.
(Avid clip bin, script bin and MXF media as seen in the video have been uploaded to:
drive.google.c... )
Back in 2019, Daniel Huber (who was with Avid at the time) watched as I did a screen share session where I demonstrated this bug. I explained and demonstrated as clearly as I could this issue, but to no avail. Avid marked MCCET-3289 "fixed," but it was not.
The official description of the issue is as follows: "Find Script button selects more than expected when more than one take is present." But what does "more than one take is present" really mean in this context? It refers to situations where a director shoots a take (say take 1) and then initiates several "back to ones" or back to the middle within that same take. These go-backs reset the action to a portion of the script that has already been lined by that take, necessitating the creation of sub-takes lines for the same take. When these sub-takes are integrated into a script, and I click the "Find Script" button on one of them, I'd expect it to highlight only the specific line in question. However, the bug manifests as a larger area being selected, spanning a chunk of the scene instead of just the intended line. This lack of precision in script-based editing becomes frustrating when I want to navigate from a clip back to the script bin, as a vast portion of the script ends up highlighted.
If you've encountered this bug or have insights into potential workarounds, I encourage you to share your experiences in the comments below. Together, let's shed light on this Avid Media Composer conundrum and work towards a more precise and efficient editing experience. But most important, we have to make Avid understand this phenomena, because by declaring it fixed four years ago, they clearly did not.
6 окт 2024
