@zzzzzz9125 is correct. Apply the Picture in Picture effect to the camera in the media pool.

There's at least one other way. If your project is finished and ready for render, you can nest your finished project in a new project. With this method, Pan/Crop is at the media level.

Thanks to all. John, that sounds counterintuitive, I will have to try it.

@John-Lenihan One more way is to use the Stereoscopic 3d Adjust FX. That has rotate and crop and a bunch of other things. Your project does not need to be stereoscopic to use that FX.

There's at least one other way. If your project is finished and ready for render, you can nest your finished project in a new project. With this method, Pan/Crop is at the media level.

That seems like the most logical solution.

@John-Lenihan said: "that sounds counterintuitive"

Believe it or not, this is not the first time I've heard that phrase. I'll give you a hint:

@Robert Johnston

Every time I do one of these, I learn more than anyone else.

@John-Lenihan said: "that sounds counterintuitive"

Believe it or not, this is not the first time I've heard that phrase. I'll give you a hint:

I have edited a long video of 4 cameras. I realize now that one of the cameras was 1 degree tilted. I can use pan and crop to fix the one event. But I would like to do it at the media level. I don't see any way.

@john_dennis I think @John-Lenihan wants to correct the titled source media BEFORE starting editing and not correcting each used part of that media separately at the timeline. Using the PIPFX or Stereoscopic 3D AdjustFX as mediaFX indeed solves that issue. You just correct the source media once and every used part of it at the timeline is correct tilted.

thanks John_dennis and 3point, I was easily able to solve my problem using the pipfx at the media level and rendered. I had never seen the pipfx before and appreciated it immediately. It does seem unsymetrical that Vegas doesn't have the pan/crop at the media level, only the track and event level.

Once I get this project off my plate, I will do an experiment with John dennis idea.

@John-Lenihan  ... if you want to direct comments/thanks to specific forum members such as :

thanks John_dennis and 3point,

... you can use keyboard Shift+@ and a list will appear with the user names of recent forum members who have commented - then just select the user name and the user name will appear as a blue link as it does to your user name in this comment. Just FYI.

EDIT: Just typing a user name in a post/comment without a link does not guarantee that the forum member will see it unless they happen to access that thread again.

John dennis, I just watched your video. That would not help me. I have 4 cameras multicammed. I only want to rotate one of the cameras out of the four.

@John-Lenihan said: "I only want to rotate one of the cameras out of the four."

Drop the file from the offending camera into a new Vegas Pro project. Apply the rotation using Pan/Crop to the media on the timeline and save a project as media name_rotated.veg.

In Project Media of your production project, replace the offending media with the newly created media name_rotated.veg.

@3POINT

I am aware of the desire to work at the media level and I appreciate the economy of effort gained by fixin' the rotation in one stroke and having it apply to all places where that media is used.

This morning, while under the influence of 12 ounces of very strong coffee made from arabica beans from a single origin (Columbia), the only kind I allow myself to ingest, I came to the conclusion in my previous post.

Adding to the laundry list of different ways to fix the problem:

Drop the file from the offending camera into a new Vegas Pro project. Apply the rotation using Pan/Crop to the media on the timeline and render to a lossless intermediate file (like Pro Res) called media name_rotated.MOV.

In Project Media of your production project, replace the offending media with the newly created media name_rotated.MOV

Set it up and create a subclip.

@3POINT

I am aware of the desire to work at the media level and I appreciate the economy of effort gained by fixin' the rotation in one stroke and having it apply to all places where that media is used.

This morning, while under the influence of 12 ounces of very strong coffee made from arabica beans from a single origin (Columbia), the only kind I allow myself to ingest, I came to the conclusion in my previous post.

Adding to the laundry list of different ways to fix the problem:

Drop the file from the offending camera into a new Vegas Pro project. Apply the rotation using Pan/Crop to the media on the timeline and render to a lossless intermediate file (like Pro Res) called media name_rotated.MOV.

In Project Media of your production project, replace the offending media with the newly created media name_rotated.MOV

That's the way I "would" have done it a few years ago, until @john_dennis taught me the beauty of nesting.

When one takes into account the intended hierarchy of Vegas functions, some of which must come before pan/crop in order to work properly, one can appreciate the simplicity of the nesting solution.

Also agree about Columbian agriculture.

I avoid nesting as much as possible because it unfortunately makes editing and rendering in Vegas much slower. Despite it's a nice feature for making complex projects simpler...I use nesting rarely and only for short complex animations.

I find nesting to be very awkward and slow like 3POINT mentions. I avoid it and would rather pre-render if I need that type of function.

@3POINT @DMT3

I appreciate the aversion to nesting that others might have. One reason that I don't have the same objections is that I used nested blocks and external references in AutoCAD long before there was a Vegas Pro. The idea of pre-rendering to an intermediate vs nesting represents a trade-off of computer resources. Nesting uses more CPU-GPU and potentially less disk space every time the clip is played. In order to be lossless, pre-renders are likely to use more disk space and time on the front end of a project. I've done both.

In the 1990s, with complex drawings, sometimes I could go to the break room and get a cup of rot-gut company-supplied coffee while AutoCad regenerated all the nested blocks in my projects.

@john_dennis I am used to doing the way After Effects does. You have multiple projects open and can interact between them or keep them separate.

It's just the dramatic loss of preview and renderspeed that keeps me away from using nesting. Nesting itself is a powerful tool, especially since it's not necessary anymore to open a second instance of Vegas to edit the nested veg.

There's at least one other way. If your project is finished and ready for render, you can nest your finished project in a new project. With this method, Pan/Crop is at the media level.

If what you're after is to get all the benefits of pan/crop on all of a particular media without the performance penalty of nesting, just drop the whole clip onto the timeline and apply pan/crop before you split it. Subsequent splits will get the starting pan/crop setting automatically applied to each piece. Only downside is tweaking pan/crop later. That would require applying the tweak to all the clips if you want consistency. The best way to do that would be to save the tweak in a pan/crop preset. Personally I like working with Pip Fx better than Pan/Crop... dragging it in front of Pan/Crop in the event FX chain gets it the same optimal quality.

Has anyone actually "tested" the horrifying cost of render speed in nested projects versus the the time it takes to render the material twice?