Does trimming in "Media managment" transcode or just copy?

If I choose "Copy" in Media Management and select "Used media and trim keeping [ ] frame handles", will the result be transcoded from the original or will it be losslessly trimmed? If the latter, how does this actually work with Long GOP codecs such as H264/H264?

It would be great if this is actually lossless because transcoding into something which avoids generational loss such as DNxHR would actually increase the size rather than reduce it since the source is in a mix of H264 and H265.

For many formats it’ll do lossless trimming, but not for all.
GOP formats will be extended to the next I-frame.

For many formats it’ll do lossless trimming, but not for all.
GOP formats will be extended to the next I-frame.

Are you saying that H264/H265 will be lossless and will be "rounded up" to the next I-frame beyond the specified number of frames? Or are you saying you don't know the specifics for this case? Is this documented anywhere?

(Sorry for the hammering of question)

Are you saying that H264/H265 will be lossless and will be "rounded up" to the next I-frame beyond the specified number of frames? Or are you saying you don't know the specifics for this case? Is this documented anywhere?

I just tried it on a H.264 and the answer is it transcoded. You can try this yourself by doing the following:

1/ New timeline
2/ Place a sample clip on the timeline. Trim both the start and end so it's only about 30 seconds long.
3/ Perform a media management on that timeline with 25 frame handles.

4/ import the new copy and place the new clip on top of the existing one, but offset to start 25 frames earlier.
5/ Set the Composite Mode to "Difference"
6/ Play the timeline.

If the 2 clips are identical all you will see is blackness over the section where the clips overlap. Any differences will show up as white.

ResolveMediaManagement.jpg (127.48 KiB) Viewed 906 times

Are you saying that H264/H265 will be lossless and will be "rounded up" to the next I-frame beyond the specified number of frames? Or are you saying you don't know the specifics for this case? Is this documented anywhere?

I just tried it on a H.264 and the answer is it transcoded. You can try this yourself by doing the following:

1/ New timeline
2/ Place a sample clip on the timeline. Trim both the start and end so it's only about 30 seconds long.
3/ Perform a media management on that timeline with 25 frame handles.

4/ import the new copy and place the new clip on top of the existing one, but offset to start 25 frames earlier.
5/ Set the Composite Mode to "Difference"
6/ Play the timeline.

If the 2 clips are identical all you will see is blackness over the section where the clips overlap. Any differences will show up as white.

ResolveMediaManagement.jpg

That's a shame. I wonder how it can be so fast then?

That's a shame. I wonder how it can be so fast then?

The strange thing is that there are sections where it is black. I'm wondering if it's just generating new I-frames.

I suggest you try it with one of your own files to see if you get the same result.

Yes, it's important that you try with your own files. As I wrote, it doesn't apply to all codecs and formats.
And then, I didn't use it anymore with most GOP files under 17, since we simply have much more storage now. We used it for a huge doc, starting under 15 and continuing under 16, but I don't even remember at which point we trimmed the footage. Files were ProRes 4K out of a Ninja and H.264 out of a Sony A6000 then.

Currently I only use it for R3D and BRAW and it works fine there. Actually, it's the only way to export these codecs from DR anyway. Oh, and files out of a Sony Z-150 in H.264 in an MXF wrapper are trimmed without transcoding too. I checked with Media Info, where you see the encoding library. Yes, they are expanded to the next I-frame. Oh, and we use Studio.

That's a shame. I wonder how it can be so fast then?

The strange thing is that there are sections where it is black. I'm wondering if it's just generating new I-frames.

I suggest you try it with one of your own files to see if you get the same result.

I tried this myself and it seems to be lossless indeed, both on H264 and H265. However, I disregarded the number of frames that I specified and just aligned it by eye until it was black. Then it was black for every frame, except sometimes when seeking through the timeline but I'm just assuming this is due to imprecise rendering when seeking to allow it to be smoother. When the seek head is "resting", it's always black.

Your result might have been caused by the fact that it seems to round up to the nearest I-frame which causes the specified number of handle frames to be inaccurate. However, I feel like this is desired behavior. I care less about the exact number of handle frames as long as there are enough of them, what's important is that there no quality loss.

Of course that's expected behavior, since exact trimming would cause re-encoding of one GOP on either end in most cases.