Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Exit
dmehalik
Participant
dmehalik
Participant
Activity
‎May 03, 2025
05:55 AM
@IanB_360 Thanks again for following up. I was a little confused by your last question, so I'm going to try to clarify my issue. You said: "And what you are saying is that the Export out of a 30 fps sequence on a 30 fps clip will result in an export that when brought back in to Premiere does not match the timecode of that same sequence you exported the file from?" And that is exactly correct. The problem is only for 30fps ProRes Exports out of Premiere. It does not matter what the frame rate of the source file is. I can bring a 30 fps clip into my project or a 23.976fps clip into my project... If I export from a 30fps timeline and re-import that export into Premiere, the TC will appear wrong. The problem does NOT occur in a 23.976 timeline or a 24fps timeline. For example, in the project I sent you (https://www.dropbox.com/scl/fi/pbziyx34vxpnd9a0qie79/Copied_TimecodeTestForAdobe.zip?rlkey=qg66si70waq7nnihrc5yn2xya&st=t44xiuqk&dl=0), I exported a mov from a 30fps timeline. Upon re-import the TC is wrong. However, if I were to duplicate that same sequence and change the frame rate to 24fps or 23.976 fps and export/reimport, the problem does not occur and the TC is correct. I am mostly a commercial editor, and almost always work with 23.976 or 24fps timelines and have never had a TC issue. However, I'm currently working on a project for a museum with all 30fps deliverables... and I am seeing this problem throughout--- Again, the source framerate of my media does not matter, only when the timeline framerate is 30fps do the problems start.
... View more
‎May 02, 2025
01:45 PM
Thanks so much, @IanB_360 . I really appreciate you taking the time!
... View more
‎May 02, 2025
11:56 AM
@Warren Heaton 1.00.00.00
... View more
‎May 01, 2025
12:41 PM
Hi @IanB_360 Please find collected project HERE I've outlined, step by step what's happening within the project. Thank you so much for taking a look!!
... View more
‎May 01, 2025
12:00 PM
Hi, Ian! Thanks so much for reaching out! I’d love to! I’m putting out another fire at work right now, but as soon as I have a few minutes, I’ll collect a project to my dropbox for you. Look for it later this afternoon. Thanks! [PII removed by moderator]
... View more
‎May 01, 2025
11:32 AM
yikes, well if that 's the case, I def. don't have the know-how to fix it. I think I'll just have to work around the issue. Thanks for your time!
... View more
‎May 01, 2025
10:34 AM
Thanks for the reply @R Neil Haugen . Well, I can't imagine that it would be a drop frame issue because I'm working in a 30fps timeline and am exporting 30fps.---not 29.97, but maybe I don't have a thorough enough understanding. In terms of "how much" I had thought that everything was consistently off my 3sec17fr... but after doing a lot of tests today, it seems to be inconsistent. One thing I did learn after posting this though: If I "get info" on the file in Premiere, it shows the TC correctly--- even though the TC is incorrect in the source and record monitor overlays. Attached is a screen grab from such a file. ProRes mov with timecode burn exported from Premiere in a timeline set to start at the same time. Resolve shows correct TC, Quicktime shows correct TC, even "get info" in Premiere shows correct TC, but the source/record monitor overlays are wrong... and if I throw a "metadata timecode effect" on, it's also wrong.  
... View more
‎May 01, 2025
07:24 AM
Hi all. Having a source timecode issue that seems specific to the combination of the following: 1) ProRes codec 2) mov's that were originally exported from Premiere or After Effects 3) mov's that were made from a 30 fps timeline Has anyone ever experienced this or know what might be going on? The same mov's show the correct timecode in Quicktime and Davinci Resolve, but always show the incorrect source timecode when brought into Premiere or AE. Also, if I export from Premiere as h.264 instead of ProRes, and reimport, the timecode is also correct. Examples: In all these examples my Timeline start TC is 1.00.00.00 and in all cases export metadata is checked: 1) Timeline is 23.976. Export ProRes422. TC is correct upon re-import 2) Timeline is 30fps (or 23.976). Export h.264 mp4. TC is correct upon re-import 3) Timeline is 30fps. Export ProRes422. TC is off every time **also, if I import an ProRes mov that I know was not created recently (I'm now in Pr 25.1.0) the TC's are correct and, if I import a ProRes mov that I know was not created in Pr/AE (like transcodes from a DIT from a shoot) the TC's are correct. Any ideas?? •Adobe Premiere 25.1.0 •MacOS 12.6.7 •MacStudio (2022) M1 Ultra 128GB memory
... View more
‎Jan 24, 2023
08:12 AM
Hi, Wes, Thanks for the attention! and just want to chime in and say +1 to what Pierre said. If there were just a modifier to drag the keyframe beyond, that should do it... though I can't think of a scenario why you would want to as it means you can no longer see what you're doing to the clip in question.
... View more
‎Jan 24, 2023
07:27 AM
I also wouldn't want the marker dialog to come up automatically (double-clicking works ok for this) but the ability to assign a shortcut to particular marker colors would be a big improvement. For example...As someone else said, markers are handy for assigning moments in musical beats but I like to assign different colors for sections of song (red is intro beats, green is verse beats, white are musical breaks, etc). Right now I have to stop playing the song in order to change colors or go back through at the end. It would be great to just hit a key for each as the song plays.
... View more
‎Jan 24, 2023
06:28 AM
1 Upvote
Also totally agree with Trevor. AutoPatch all the way! Targeting/patching source and timeline, in my mind, is Premiere's biggest weakness... and one of the integral / most often used parts of editing.
... View more
‎Jan 24, 2023
06:28 AM
3 Upvotes
"It would BE a great feature, IF it created the tracks when the user tries to INSERT the clips. It does it now when you OPEN the clip in the SOURCE viewer." Yes! This exactly!
... View more
‎Feb 20, 2021
08:00 AM
Oh, and forgot to mention, also tried trashing Premiere preferences and Updating both Pr and Me to the latest version
... View more
‎Feb 20, 2021
06:10 AM
I recently gave my wife my old MBP (2017 3.1 GHz QuadCore Intel i7 running macOS 10.15.7-Catalina). When she tries to open Premiere 2020 (initially version 14.3.2... and now also version14.9) in her her Mac User Account, it gets stuck on the splash screen at "Loading ExporterQuicktimeHost.bundle". If we log out of her user account, and into mine, Premiere opens. I searched the forums and tried fixes in the following posts: https://community.adobe.com/t5/premiere-pro/premiere-pro-cc-hangs-on-splash-screen-quot-loading-exporterquicktimehost-bundle-quot/m-p/5325903 and https://community.adobe.com/t5/premiere-pro/loading-exporterquicktimehost-bundle/td-p/4171779 People apparantly have been posting about this issue since at least CS6, but I can't seem to find a fix despite about 20 different "solutions" being offered in those posts. Here's everything I tried: • I went to sytem preferences>Security and Privacy>Privacy and gave "Full Disk Acess" to Premiere and Media Encoder • I changed all permissions on Package Contents (and all contents) in Premiere and Media Encoder to read/write for everyone • I uninstalled Flip4Mac • I went to MacHD>Library>Quicktime and deleted AC3MovieImport.component (I was also advised to trash Flip4Mac and Perian, but those were not there) • Right clicking on both Pr and Me apps>Show Package Contents>Plugins>Common and deleting "ExporterQuicktimeHost.bundle" and "ImporterQuicktimeHost.bundle". This did not work in her user account, and then made Premiere freeze on startup in my user account as well, except the freeze point changed to "Loading Player Media Core Bundle" Nothing is working! Can anyone please help? My experience with calling Adobe Support has been frustrating at best, so hoping for some help here. Thanks!
... View more
‎Dec 06, 2020
08:09 AM
Andy, I've experienced this problem consistently over multiple BMD driver releases... and I don't experience the problem if I open Avid or DaVinci Resolve, so I'm pretty sure the problem exists within Premiere.
... View more
‎Dec 05, 2020
11:02 AM
Hi, Andy. Thanks for the response... but this doesn't help either. Same latency.
... View more
‎Dec 05, 2020
11:01 AM
Hi, Kevin. I tried with my control surface (Tangent Wave) completely disconnected from my system. This did not help... and I know that I'm not the only one having this issue. There is a UserVoice thread about it here: https://adobe-video.uservoice.com/forums/911233-premiere-pro/suggestions/39438052-io-hardware-causes-playback-and-pause-delay?tracking_code=b3c1f3a5984466c34565afb4798ed07e I suspect that this is true for many, if not all users, but people don't know about UserVoice or don't bother with it. It is so incredibly frustrating. It's impossible to edit with any sense of rhythm (a huge part of editing), music in particular, when there's a delay after hitting pause. I'm forced to either not use my external monitor (which is not a great compromise for "pro" software), or sorta guess and trim and playback repeatedly.
... View more
‎Dec 03, 2020
03:41 PM
1 Upvote
Hi, Kevin. Thanks for the response. Will do, but could you please clarify what you mean by "without any audio hardware connected"? I did a test where I set output to my MBP speakers and this did not help. You mentioned "Control Surfaces" though??? I do have a TangentWave connected but that should have nothing to do with Audio Hardware, I imagine?
... View more
‎Dec 03, 2020
03:23 PM
1 Upvote
Well Andy, I guess I had given screengrabs that related to my I/O device... which seems to be the problem since when I don't have "mercury transmit" enabled, everything runs snappily. Premiere does not lag unless I'm monitoring with my external reference monitor. I feel that the rest of my settings should be optimized for my system, as far as I understand.
... View more
‎Dec 03, 2020
02:36 PM
1 Upvote
Hi, Ann. "Uutput screen recording" is basically an "aggregate audio device" which enables be to caputre system audio when screen recording as well as my USB mic using the Audio MIDI setup utility on the mac, as well as an app called iShowU Audio Capture. (Screen recordings via Quicktime fail to record audio without doing this, even if you have it set to record system audio). For the record, it doesn't have any affect on my playback responsiveness (as I've tested with this both on and off)... and since the problem existed before I created this setup. I'd always had it set to "external headphones" and the problem existed then, too.
... View more
‎Dec 03, 2020
11:58 AM
1 Upvote
‎Dec 03, 2020
11:50 AM
Hello! I can't seem to figure out if there's some sort of setting I should be adjusting, or if it's just a failing in Premiere... but when I "transmit" playback to my reference monitor (via Thunderbolt to my BlackMagicUltraStudioMiniMonitor>SDI > FSI DM240 monitor) my playback responsiveness is slow in Premiere. I'm not talking about audio sync/offset. I'm talking about when I hit the space bar to play/pause it takes longer to respond. I don't have this problem when doing the same in Resolve or Avid... and the problem goes away if I un-check "transmit" playback and just use my computer monitor to edit. Does anyone have any insight? Thanks in advance! SYSTEM SPECS: •MacBookPro 16" 2019 64GB RAM AMD Radeon Pro 5600M 8 GB/Intel UHD Graphics 630 1536 MB •Premiere CC 2019 (13.1.5) •Blackmagic Desktop Video Setup V 11.6
... View more
‎Jun 24, 2019
03:29 PM
1 Upvote
1) Load your 4k footage 2) Create 1080p (or whatever size proxies) you prefer 3) Work in a 1080p timeline. Resize your footage to fit by using the "Set to frame size" command (NOT "scale to frame size) 4) I recommend duplicating the clip you plan on dynamic-linking on top of itself and then nesting. That way you always have a path back to the original file. Right click the top clip and "Replace with After Effects Composition" 5) In AE, you will now have a 1080p DynamicLinked comp. Your footage should still be 4k (and a proxy should be attached as well), but your comp will be at the resolution you're working in.
... View more
‎Feb 25, 2019
08:45 AM
Thank you! It worked!
... View more
‎Feb 25, 2019
08:24 AM
Hi, I'm having a problem when try to DynamicLink to AE--- comps appear in AE empty. Adobe has an out-dated compatibility chart that doesn't include anything after 2017. I'm using Premiere 12.1.2 and AE 15.0.1. Thanks!
... View more
‎Aug 29, 2018
09:03 PM
Thanks for taking the time, Stan. I will definitely take your advice!
... View more
‎Aug 29, 2018
02:05 PM
Hi, I'm starting a freelance gig on Tuesday and I will be working at an office running on 12.1.1... I've already updated my home workstation to 12.1.2. Just want to make sure I won't have any problems bouncing the work back and forth between their office and home?
... View more
‎May 19, 2018
08:04 AM
Oh please tell me I have something set wrong. This can't possibly be how Premiere works!... If I have a source clip that has more audio tracks than are in the sequence I'm working with (for example my source clip has 4 tracks of audio, my sequence has 1), source patching only shows me A1 of my source unless I go through the extra step to hit the tiny "+" sign on the A1 button. Making matters worse, if I use my keyboard shortcut to deselect all source audio tracks (shift-clicking on A1) without first hitting the plus sign to reveal the rest of the tracks, the rest of the tracks remain selected. I must be missing something. In what scenario would I NOT want to see all the tracks available in the source clip?
... View more
‎May 17, 2018
03:16 PM
1 Upvote
Hi, Kevin--- Thanks for following up. After advice from another forum on Facebook I ended up simply fixed it locally on my hard drive. I went to Documents>Adobe>Premiere Pro. I deleted the 12.0 folder (well, after I backed it up elsewhere just in case) and duplicated the 11.0 folder and renamed it 12.0. That worked for me and I was then able to upload those settings to the cloud for future. Oh, that and I went back a version to 12.0.0 as this was not the only issue I was having. Thanks for your time. I believe I already submitted that bug report.
... View more
‎May 11, 2018
08:08 PM
Hi. I recently updated to Premiere Pro 12.0.0 (waiting on the newest version as I hear a lot of nightmare stories). I'm working in Mac OS 10.12.6 Sierra. After I was unable to import my 2017 settings into the 2018 version using the cloud, I was able to re-establish my settings by duplicating my "11.0" folder and renaming it "12.0" (after backing up the original "12.0" just in case.) However, I'm now not able to sync (upload) my 2018 settings to the creative cloud). I get the following error message: "Syncing failed. There was an error updating the remote files. Please try to download your settings before doing uploads again." Wha? It sounds like it wants me to download settings instead of uploading them which will overwrite the current/good settings. If I open an old project in the 2017 version of the software (2017.1.2) I am able to upload those settings without issue. Is anyone else having this problem or have ideas for a solution? Thanks!
... View more
Get ready! An upgraded Adobe Community experience is coming in January.
Learn more
Copyright © 2025 Adobe. All rights reserved.
AdChoices