Skip to main content
katherinestrain
Participant
February 14, 2019
Question

Subclips losing their out points/odd behavior

  • February 14, 2019
  • 6 replies
  • 623 views

I'm working on a showreel and my first pass is to pull subclips out of the footage I have(I use restrict trims to subclip boundaries). I place them in useful bins for organizing.  Now I can quickly go through a bin and scrub the thumbnails and only see the footage I will use.  This is all working fine but randomly when I reload a project all the subclips go wacky.  Suddenly the out point of the subclips is lost.  The thumbnail now has a length listed that is from the in point of the clip to the end of the video it came from.  When I scrub the thumbnail is mostly black for the full length.  If i open it in the source viewer it has the sub clip and then just black for the length of the original video it came from.  I can fix the problem by editing every subclip and toggling "use restrict trims to subclip boundries" off and then on again.  Obviously not ideal when you have a hundred or more subclips.  Particularly when it could all break again the next time I load the file.  Anyone run into this or have a logic to whats triggering it that I have yet to find?

6 replies

Participant
February 25, 2025

I'll reply with steps here.  This happens on all version of Premiere from the the latest all the way back at least to 2018.  It also happens in both windows 11(latest update) and Mac (macbook pro m4 latest OS) in my tests.  Most of my experience is in windows however on intel processors with Nvidia Quadro graphics cards. Best I can tell this is not hardware dependant.  It is a bug caused by premiere needing to relinking footage

 

- Create a new project and import a number of video clips.  In my recent tests these were MP4 files with H264 of various resolutions but mostly 1080 30 and 24p.

- Create a number of short subclips from those videos that include both audio and video.  It doesn't matter if you choose to restrict subclip boundaries or not. You will need quite a few subclips as when things go wrong it doesn't seem to always do it to all clips but just some.  In my latest test this morning I created 8 subclips and only a couple went wrong.  In other tests all of them break.

- Save the project and now move the project or the footage to a new location so that when you re-open you get the re-linking dialogue. If premiere can find the files on its own then the problem is less likely to show up.

- upon re-linking look at your subclips as thumbnails in the bin.  If you hover scrub now at least some of the subclips will likely have large black sections in the thumbnail because the audio out point has shifted to the full length of the original file but the video out point is still where you set it.

-  You can fix the clip by going into the subclip properties and toggling "restrict times to Subclip Boundries"

 

This has been a huge issue with subclip workflows on long lasting projects that you are handing between editors in different locations.  The benefit of the subclip is getting that scrubbable thumbnail that you can hover over to see all the content at a glance.  I use this as fast and efficient way to create libraries of clips for sizzle reels. Once this happens though you go to hover and see mostly black in the scrub.  And since there is no hotkey for the restrict trims toggle you are forced to use multiple clicks and a mouse move to actually fix each clip.

jamieclarke
Community Manager
Community Manager
February 25, 2025

Hi @katherinestrain -  Thanks for submitting your bug report. We need a few more details to try to help with the issue.
Please see, How do I write a bug report?


Sorry for the frustration.

Participant
February 23, 2025

This is an old Thread but this bug still exists.  If you create subclips with both video and audio and then at some point have to relink due to the path to the footage changing, the audio loses its in and out points so you end up with a subclip that is as long as the original clip that just shows black except where the in and out points are for the video track.  Toggling “Restrict Trims to Subclip Boundaries” fixes the issue and restores the in an out for the audio but since there is no hotkey for that this becomes a massive issue if you have lots of subclips.

Legend
February 14, 2019

Kinda sounds like a bug.

katherinestrain
Participant
February 14, 2019

To be more specific its the audio portion of the subclip that is losing its outpoint while the video portion still has it.

Inspiring
February 11, 2020

I’ve been doing some Premiere scripting and believe I’ve run into the same bug. 

 

When using “projectItem.getProjectMetadata()” you get all of the column data in the project bin for any item, and the “Restrict Trims to Subclip Boundaries” setting affects the values of start, end, in point and out point.

 

Both of these subclips are from the same 10 second master clip, trimmed to 4-8 seconds with IO points at 5 and 7 seconds.  The first one has “Restrict Trims to Subclip Boundaries” unchecked, the second has it checked.

test_25fps_1280x720.mov.Subclip001
mediaStart : 00:00:00:00
mediaEnd : 00:00:10:00
mediaDuration : 00:00:10:01
videoInPoint.value : 00:00:05:00
videoInPoint.max : 1778112000000 (7 seconds in ticks)
videoInPoint.offset : 0
videoOutPoint.value : 00:00:07:00
videoOutPoint.min : 1280240640000 (5 seconds in ticks)
videoDuration : 00:00:02:01
__________________________________

test_25fps_1280x720.mov.Subclip002
mediaStart : 00:00:04:00
mediaEnd : 00:00:08:00
mediaDuration : 00:00:04:01
videoInPoint.value : 00:00:05:00
videoInPoint.max: 762048000000 (3 seconds in ticks)
videoInPoint.offset : 1016064000000 (4 sec offset in ticks)
videoOutPoint.value : 00:00:07:00
videoOutPoint.min: 7264176640000 (1 second in ticks)
videoDuration : 00:00:02:01

So the restricted clip has the IO points at 1-3 seconds, while the unrestricted (unchecked) clip has the IO points at 5-7 seconds…but only where expressed as ticks.  The timecode is identical, though.

 

This error(?) directly relates to the in and out points moving when you reload an ‘unrestricted’ subclip.  IO points are re-calculated, perhaps, using the wrong data.