Forum Replies Created

Page 1 of 4
  • Mark Dagostino

    October 29, 2025 at 7:17 pm in reply to: DO NOT UPGRADE!!!

    I forgot to add: I run an M2 Ultra, Sequoia 15.7.1

  • Mark Dagostino

    October 29, 2025 at 7:15 pm in reply to: DO NOT UPGRADE!!!

    Hi. Would you mind explaining why? I’ve been working with Premiere for years and have had very few minor issues with 2025.

  • Thanks, Mads. I work on a Mac and Premiere has not been a project-stopping problem for me. The captioning issue is a small inconvenience, but it gets me 90% of the way there and usually requires only about 5 minutes to fix mistakes. For my workflow, still better than having to send it out or use a third-party program, (for security reasons it takes forever to get any app approved for use on my workstation). Going back to the early days of Media100, I was never an Avid fan, but hopefully that works out for you. I’ve dabbled in DaVinci and I hear lots of praise.

  • Thanks for the fast and spot on reply., Ivan. I selected the caption and the properties window and it was blank. After your reply I decided to restart the program and, voila it works! Gremlins:)

  • Mark Dagostino

    August 18, 2024 at 12:54 pm in reply to: Ingesting footage and batch renaming

    Thanks, Mads. I tried Bridge years ago when it first came out. Prelude at the time was far simpler and a very efficient way to batch rename and create customized metadata fields all I. One program. There was no reason to get a third party program or use the more time-consuming metadata window in premiere. I wonder why they gave up on such a useful program.

  • Mark Dagostino

    August 15, 2024 at 8:00 pm in reply to: Ingesting footage and batch renaming

    Thanks, Ivan. When Prelude work it was elegant in that it batch renamed and allowed user-generated metadata fields.

  • Maybe make a nest of the three tracks and cut from that single track?

  • I import using Prelude without transcoding and found that it started doing that a few updates ago. It brings in all the subfolders, content/clips, for the .mxf files. When I import I get the same as you. My workaround has been to take the .mxf files out of the clips folder and move them to my top level footage folder for that project and that works to keep the renamed filenames when importing. I’m not sure why this happens now but it’s a pain. My other workaround is to transcode to .mov files. These import with proper filenames nicely. Not the ideal answer. Hopefully someone from Adobe will chime in.

  • Mark Dagostino

    March 4, 2022 at 10:54 pm in reply to: Closed Captioning

    I’ve been using the closed captioning function inside Premiere 2022 and it works nicely and is easy to use. I also have used rev.com. They are fast and very inexpensive. I’ve had turnaround sometimes in under an hour.

  • Mark Dagostino

    May 17, 2021 at 1:24 pm in reply to: Why do frames display instead of timecode?

    Sorry for not answering. I’ve just switched to a new system and wasn’t receiving notifications. It seems the new system with Premiere updated solved. Thanks:)

Page 1 of 4

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy