That worked! I never noticed that refresh icon on that block. Thank you! Accomplished what I set out to. ... View more

Thanks, @Mathias Moehl !   So, workaround - any way to write a script that changes the values of an effect on a clip?   In this case, I want to use the crop effect at 50% left crop. ... View more

Hi @mattchristensen . Did the information I provided give you any insight into the issue? ... View more

Hi @mattchristensen ! Thanks so much for your prompt reply. We're not planning to go to 2025 yet because we like to stay a year behind unless there's a compelling reason to update sooner that specifically addresses our workflow.  2023 has been absolutely wonderful to us.   Workstation... Windows 10 Pro verseion 22H2 Intel Xeon Gold 6242R CPU @ 3.10GHz 3.09GHz 96GB Ram 64-bit operating system, x64-based processor   I installed Premiere 2025 beta on this machine and experienced the same issue. The file that takes 26 seconds to Scene Edit Detect in Premiere 2023 took five minutes in Premiere 2025 (so even a bit longer than 2024). At the risk of muddying the troubleshooting waters... I, and other users, have also noticed that 2024 was slower to save and quit than 2023. Often hanging for a bit.   Thanks for your time on this! Sam ... View more

Hey @mattchristensen ! My team finally updated from Premiere 2023 to Premiere 2024. We use scene edit detection daily, and have noticed it's quite slower in 2024.6.4. The same file took 4 minutes to scene edit detect in 2024, versus 26 seconds in Premiere 23.4.0. We have recreated this error on three of our machines, all running of the same network/san, etc. Any tips? ... View more

Thank you, @Kevin-Monahan . The Clip Isage Metadata column reflecting usage across an entire Production would be HUGE for my team. ... View more

Hi @Mathias Moehl    Yes, The solution you provided in that old thread worked in every case, except when the in-point was zero. I believe in the case of zero, it was still displaying frame 1. You can see from that comment's last thread that I made the modification you just mentioned and got it to work. If you'd like more clarity on that to troubleshoot this current issue, I can revisit it. It's been a while and I've used that old script a lot since then.   To answer your question - I was refering to the timecode in-point of each clip, not the start time in the sequence. Start time in the sequence did not seem to be impacted. If it matters, these are three clips that are stacked on top of each other, so the sequence start-time of each clip is the same.    The new assets are all long enough. They are exact copies of the original assets, in different sizes (16x9, 1x1, ect).   Random question - is it possible the Premere setting 'match frame sets in-point' has any impact on this? The editor who first experienced this had that setting unchecked, and believes that has something to do with it. I'm skeptical of that.   Thanks again and sorry I wasn't more clear in my last response.  ... View more

Hi @Mathias Moehl and @Bruce Bullis    Thanks so much for weighing in. Not sure where to go from here, so let me know if you have any ideas. Very 'bug-like' behaviour indeed, and was replicated multiple times on two machines, on a large number of sequences. All clips affected by script went to in-point :19 on the export, and after restarting Premiere. Weird!   @Mathias Moehl - to answer your question about the test block. That is a block you and I created together to solve a rounding issue that was creating inaccurate in-points.   Doesn't <=0 mean less than or equal to zero? So subtracting to a negative number would never happen? Interesting though that two of the clips should have had an in-point of :20 and ended up with :19, but the third clip was a full 8 frames off, which lead me away from this being the issue during testing.   Here is our conversation on that, in case you're curious. It was a brilliant solution on your part! https://community.adobe.com/t5/premiere-pro-discussions/automation-blocks-clone-enable-and-replace/m-p/14905630#M532280 ... View more

Hi @Mathias Moehl  Thanks for your reply. Apologies, I didn't explain myself well. I am only selecting one sequence clip and one project item at a time.   So in my example, the user has run the script three times.   The most confusing things to me are... Why does the sequence look one way, and the export another way? Why does the project change after closing and re opening it? Why did all three clips in-point happen to change to frame 19 after reopening the project? That's an awesome script you wrote though, and I'll probably use it in the future! ... View more

copy sequence content Ah yes! Inserting clips using the in-out point and start-end time at sequence is something I've been experimenting with. I'm still trying to figure out how to get them inserted onto the proper tracks. Sequence Audio Settings I looked at that, as well. And I could only find Audio Channel type in the 'get property' block, not the 'set property' block. Am I missing something? ... View more

Wow! We found a bug. Cool! Yup. I found away to identify the asset and impliment it using different criteria. There's always a way. Thank you! ... View more

Excellent! That worked when I wrapped that entire section in the command you suggested...   ... View more

\theprojectname.prproj\The_Project_Item.tif   theprojectname.prproj still being the project the sequence lives in, not the project the project item lives in. ... View more

Sorry, I didn't specify. It's returning the name of the project where the sequence lives, not the clip. The clip lives in a different project within the Production (not in the root bin, either). That seems to be what's tripping me up. ... View more

Thanks for your reply, @Mathias Moehl  I tried this to see if it would retrieve the information, but it just came back with \theprojectname.prproj   ... View more

Thank you! That path with project allowed me to make progress. Is there a way for Automation Blocks to retrieve the parent bin of a sequence clip when the sequence clip lives in different project than the sequence? I know what project the clip will be in, but the exact bin varies depending on what assets I'm trying to swap out and would need to be retrieved by the current clip in the sequence. ... View more

Excellent! That worked. Thanks @Mathias Moehl! And my typical workflow usually consists of the standard and DM files being in different bins, so that will be great!   Just out of curiousity - is there a way to differentiate even if they happen to be in the same bin? I looked in the documentation you provided but none of the examples there would seem to do the trick. ... View more

@Mathias Moehl  That didn't work at first so I played around with the math and found something that works! Check it out...       Getting there! Some more questions to come but for now I just wanted to tell you the good news and say thanks for your help!   ... View more

Hi @Mathias Moehl. Hope you're well Little snag.   3.9e-10 works with every in-point I've tested EXCEPT the very first frame of the asset. If the in-point of the clip is the first frame, we see the original issue where it's displaying the second frame until I nudge the clip in any direction (timecode overlay displays correctly). What do you think? ... View more

I found the magic number: 3.9e-10. Not 3.8, Not 4.0 - but exactly 3.9. Nice one!   Thank you so much! This script has come so far since we started working on it together. I have some modifications to make in the naming conventions and some questions on the variants of this script, but I think I'll save that for next week.   Thanks again! ... View more

This is interesting. Now I'm seeing the correct thing visually, but the timecodes don't match. The nudge trick bumps the timecode back into place. Any ideas? I'll need both the timecode and the visual to match. ... View more

That worked! You do amazing work. Moving forward! ... View more

Hi @Mathias Moehl . Here is a one-minute video that explains the (potential) bug and suggests a workaround. This particular issue so fundamental to the suite of tools I am building, so I am incredibly thankful for your time...     ... View more

Thank you so much, @Mathias Moehl !   Your script gave me the insight I needed to take mine further. I'm nearly there, with currently one command I can't figure out how to execute. The attached script takes the active sequence and does the following...   -Clones active sequence -Renames clone based on active sequence name, with two changes to the name -Moves clone to a different folder -Activates 'bug' on cloned sequence -Replaces Blue_close.mov from Active Sequence with Green_close.mov on cloned sequence   What I can't figure out how to do is make Green_Close have the same in-point as Blue_Close. Green_Close starts at frame 0 no matter what frame Blue_Close starts on in the original timeline. I've attached my script (with an attempt at the in-point replication that doesn't work). Below is a google drive link to a small Adobe Production (the whole package is only 10MB) that I prepped for testing if that is of any interest to you.   https://drive.google.com/drive/folders/1EyTovNMuAL9tse5-vWbEtZrhGECDrPOJ?usp=sharing ... View more