Video bounce to same as source h264 Problem

[Carl Sealove]

This will only work if you have the very first frame of the video selected as part of the bounce. (Please see screenshot). Not very helpful, as more often then not bounces need to be done to show scenes or part of the file, not starting from the first frame. But I guess this is a promising first step.

MacbookPro M1MAX - 64GB Ram - 8TB SSD
Mac Os Ventura 13.6.3
PT Ultimate 23.12.0.136

[its2loud]

Originally Posted by Carl Sealove

This will only work if you have the very first frame of the video selected as part of the bounce. (Please see screenshot). Not very helpful, as more often then not bounces need to be done to show scenes or part of the file, not starting from the first frame. But I guess this is a promising first step.

MacbookPro M1MAX - 64GB Ram - 8TB SSD
Mac Os Ventura 13.6.3
PT Ultimate 23.12.0.136

Bounce to h.265. Done and done. Stop worrying about h264

[Carl Sealove]

Thanks for your response. I wish it was that simple.

h265 is not supported for bounce same as source. (Plz see the screenshot)
I receive h264 (or DNX) from editorial.

Just did a test for a 24 fps/48k PT Session using h264 video:
1) bouncing "same as source" from 1st frame for 1 minute took 5.5 seconds
2) bouncing for 1 minute from any place else in the session took 20.8 seconds
3) bouncing for 1 minute from h264 to h265 (same as source not allowed) took 22.4 seconds
So I am hoping AVID will please provide same as source with h264 from any point in the session (not needing to include the first frame). Would be a HUGE time saver over the course of a show.

Thanks!

[Darryl Ramm]

Maybe I'm lost but how does Avid provide same as source from an arbitrary video file location here? h.264 is typically lossy encoded, you can't just cut the file at that point, and copy it to an output, you need to reencode/transcode it.

[BScout]

Originally Posted by Darryl Ramm

Maybe I'm lost but how does Avid provide same as source from an arbitrary video file location here? h.264 is typically lossy encoded, you can't just cut the file at that point, and copy it to an output, you need to reencode/transcode it.

You can edit/export from any frame in h264. Lots of editors do it (the old QuickTime engine did it.) The first frame is re-written to include all the intercompression info. It’s not re-render because it’s just collecting the info for that frame and not re-compressing it (quality is the same)

[Carl Sealove]

Thanks for the clarification BScout.
I certainly do not understand all of the technical details, but bounce to video "same as source" was available with h264, DNX and I believe a few other formats until a year or two ago when it was broken, no doubt due to the EOL of Quicktime. It worked from whichever frame you designated as the start, up through the frame where the end of the bounce was designated. Useful for bouncing scenes to preview score and sound design for directors, execs, etc. Worked very well. Saved a TON of time!

They have it partially working now as long as you start at the first frame, which is not practical for demonstrating scenes that occur later.

[Darryl Ramm]

Originally Posted by BScout

You can edit/export from any frame in h264. Lots of editors do it (the old QuickTime engine did it.) The first frame is re-written to include all the intercompression info. It’s not re-render because it’s just collecting the info for that frame and not re-compressing it (quality is the same)

OK thanks! I never clued in that this was happening in other situations, I imagine even that is fun given the h.264 complexity and versions there, and is what is holding Avid up.

[moogboy100]

So AVID basically lied to us about the reintroduction of this, as the feature hasn't really been reintroduced if it's actually this half-assedly implemented?

[smurfyou]

Originally Posted by moogboy100

So AVID basically lied to us about the reintroduction of this, as the feature hasn't really been reintroduced if it's actually this half-assedly implemented?

It's more likely they don't understand how we use it. So the thought of only bouncing part of a video wasn't considered.

I've also just been using H265. But I'm not on 2023.12 yet.

[its2loud]

Originally Posted by Carl Sealove

Thanks for your response. I wish it was that simple.

h265 is not supported for bounce same as source. (Plz see the screenshot)
I receive h264 (or DNX) from editorial.

Just did a test for a 24 fps/48k PT Session using h264 video:
1) bouncing "same as source" from 1st frame for 1 minute took 5.5 seconds
2) bouncing for 1 minute from any place else in the session took 20.8 seconds
3) bouncing for 1 minute from h264 to h265 (same as source not allowed) took 22.4 seconds
So I am hoping AVID will please provide same as source with h264 from any point in the session (not needing to include the first frame). Would be a HUGE time saver over the course of a show.

Thanks!

IMO You really shouldn’t be using h264 in your timeline anyway. Convert your videos to DNX. Bouncing to h265 is quick enough for me. Allows me to get up and walk around for a minute and get some steps in. I don’t need to be constantly sitting in the chair.