Still image proxy to high-res files

Offworlder wrote on 1/3/2017, 4:58 PM

Specific to doing pan and scan within Pro, I would like to use placeholder 1920x1080 still image files for the rough-cut and then be able to reference the high resolution files during the final edit, will Pro reference these proxy files, much like Avid?

Thanks,
Gilbert
 

Custom workstation build: ASRock X99 WS LGA-2011, Intel i7-6850K 15M Broadwell-E 6-Core 3.6 GHz , Toshiba OCZ RD400 SSD NVMe M.2 512GB, G.SKILL TridentZ 32GB DDR4, EVGA GeForce GTX 1080 FTW ACX 3.0, 8GB GDDR5X, 8TB Raid 0, 5TB backup/hot swap, NZXT Phantom 630 case. Vegas 14, Resolve 12.5, Affinity Photo - lots of cooling <g>

Comments

balazer wrote on 1/3/2017, 5:11 PM

As far as I know you can't swap a video for a still image in Vegas Pro.  You can swap a video for another video, and it will be a transparent swap if both videos have the same resolution and frame rate.

Vegas Pro has a built-in proxy function.  It will transcode the video to 720p MPEG-2 and use that in place of the original video whenever you set the preview mode to Draft or Preview.  It works quite well in my experience.  Can you use that?

Offworlder wrote on 1/3/2017, 5:21 PM

Hi, sorry if I was not clear. In the case of the pan/scan, it would be only still images and not a swap of a video file for a still image. I want to reference a high-res still image proxy file so I can do the move with the low-res file while roughing it out.

Thanks

Custom workstation build: ASRock X99 WS LGA-2011, Intel i7-6850K 15M Broadwell-E 6-Core 3.6 GHz , Toshiba OCZ RD400 SSD NVMe M.2 512GB, G.SKILL TridentZ 32GB DDR4, EVGA GeForce GTX 1080 FTW ACX 3.0, 8GB GDDR5X, 8TB Raid 0, 5TB backup/hot swap, NZXT Phantom 630 case. Vegas 14, Resolve 12.5, Affinity Photo - lots of cooling <g>

Video_flaneur wrote on 1/3/2017, 5:28 PM

I'm not sure if this would work but you could give it a try.

Make a Vegas project using your low res file. Drop this project on the timeline of your current project and do your pan/crop. When you are happy go back to the subproject and swap the low res file for your high res one.

Laptop: Surface Pro 6: Windows 11 Pro Version 23H2, Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz   2.11 GHzIntel(R) Core(TM) i7-8650U CPU @ 1.90GHz   2.11 GHz; 16GB RAM, 1TB internal SSD
2 external monitors, 5TB external drive, wireless keyboard and mouse

(planning to upgrade to a more powerful graphics laptop when cashflows allow)

Vegas Pro 22 (Build 239); Vegasaur Toolkit 4.0.1; ProDad Mercall v.4; HitFilm Pro Version 2021.1; Acid Pro 11; Sound Forge Pro 18;

Musicvid wrote on 1/3/2017, 5:50 PM

All generated media properties would need to be reconformed post-edit?

Sounds risky to me.

Offworlder wrote on 1/3/2017, 6:02 PM

Other option is to do all moves in AE and import. The rub of course is timing in/out for each move and given I am calling in a favor it would of course be better to edit in program, if an option less the images go to crap when I render.

If on the other hand I could do those moves in Resolve or Avid and import back into Pro, that might be worth investigating.

Custom workstation build: ASRock X99 WS LGA-2011, Intel i7-6850K 15M Broadwell-E 6-Core 3.6 GHz , Toshiba OCZ RD400 SSD NVMe M.2 512GB, G.SKILL TridentZ 32GB DDR4, EVGA GeForce GTX 1080 FTW ACX 3.0, 8GB GDDR5X, 8TB Raid 0, 5TB backup/hot swap, NZXT Phantom 630 case. Vegas 14, Resolve 12.5, Affinity Photo - lots of cooling <g>

NormanPCN wrote on 1/3/2017, 6:27 PM

Hi, sorry if I was not clear. In the case of the pan/scan, it would be only still images and not a swap of a video file for a still image. I want to reference a high-res still image proxy file so I can do the move with the low-res file while roughing it out.

Thanks

You can do you pan/crop on a lower res file to rough things out and then swap the file to a higher res one and you pan/crops will function properly. I've done this. What I did was rename folders. I had originals in one folder and the resized ones in another. I just renamed the folders and Vegas just started using the differently sized image files when the project was opened. My project was always at the same settings.

By default Vegas auto conforms media frame size to the project frame size. If you turn that off then things like this will not happen automatically.

 

john_dennis wrote on 1/3/2017, 11:28 PM

The pictorial view of the method NormanPCN describes...

Red Prince wrote on 1/4/2017, 12:44 AM

The pictorial view of the method NormanPCN describes...

I suspect not. What I suspect is that he would first change the name of the LoRez (or whatever you called it) to something else, e.g., ProjectPics, import that to Vegas and do all the editing. Then he would close the project, rename ProjectPics back to LoRez, followed by renaming HiRez to ProjectPics, open Vegas and render.

Doing it that way is much simpler than what you did because that way Vegas is always looking for the ProjectPics folder without needing to ask you where all the media is.

At least that’s how I would have approached did and that also is how I read what NormanPCN has said. Of course, your way works, too, I just think what I have described is simpler.

He who knows does not speak; he who speaks does not know.
                    — Lao Tze in Tao Te Ching

Can you imagine the silence if everyone only said what he knows?
                    — Karel Čapek (The guy who gave us the word “robot” in R.U.R.)

john_dennis wrote on 1/4/2017, 1:41 AM

You are correct. It is much easier and quicker to rename folders without Vegas knowing what happened. I got too hung up on how the pictures were resized, and lost sight of KISS.

Red Prince wrote on 1/4/2017, 9:39 AM

Well, at least you made a video explaining the principle behind it. 😉

He who knows does not speak; he who speaks does not know.
                    — Lao Tze in Tao Te Ching

Can you imagine the silence if everyone only said what he knows?
                    — Karel Čapek (The guy who gave us the word “robot” in R.U.R.)

NormanPCN wrote on 1/4/2017, 11:38 AM

I suspect not. What I suspect is that he would first change the name of the LoRez (or whatever you called it) to something else, e.g., ProjectPics, import that to Vegas and do all the editing. Then he would close the project, rename ProjectPics back to LoRez, followed by renaming HiRez to ProjectPics, open Vegas and render.

At least that’s how I would have approached did and that also is how I read what NormanPCN has said. Of course, your way works, too, I just think what I have described is simpler.

That is pretty much what I did. This is a screenshot of the folder as it exists right now.

The "Photos" folder is where Vegas thinks the photos its using are. OrigPhotos are the 12MP originals (4000x3000). Vegas does not perform as smoothly with the 12MP files doing Ken Burns type stuff on each still and I was not do doing any huge crops/zooms so I did not need the high res anyway. I resized to 7MP and performance was very nice (older computer).

If I wanted to use the 12MP files all I need do is rename Photos to something like Photos7mp and rename OrigPhotos to Photos and I am done.

john_dennis wrote on 1/4/2017, 3:06 PM

Because I have lots of better things to do (that I'm avoiding), I reworked the tutorial to more accurately describe the methods being discussed. Everyone has a preference for naming folders, so here's mine. I trust the workflow is more cogent than the first effort.

Even though I've considered the concept, I don't remember ever using it myself.

Red Prince wrote on 1/4/2017, 3:52 PM

Because I have lots of better things to do (that I'm avoiding), I reworked the tutorial to more accurately describe the methods being discussed.

Well done! :)

He who knows does not speak; he who speaks does not know.
                    — Lao Tze in Tao Te Ching

Can you imagine the silence if everyone only said what he knows?
                    — Karel Čapek (The guy who gave us the word “robot” in R.U.R.)

Offworlder wrote on 1/4/2017, 8:55 PM

I appreciate all the input and screen recordings.

What I suspect is that he would first change the name of the LoRez (or whatever you called it) to something else, e.g., ProjectPics, import that to Vegas and do all the editing. Then he would close the project, rename ProjectPics back to LoRez, followed by renaming HiRez to ProjectPics, open Vegas and render.

Doing it that way is much simpler than what you did because that way Vegas is always looking for the ProjectPics folder without needing to ask you where all the media is.

I do have one specific question, if I have two folders, as example named low-res and hi-res with the corresponding images in each what is the reason to change the folder names, if I then point to the other folder back within the program?

 

Custom workstation build: ASRock X99 WS LGA-2011, Intel i7-6850K 15M Broadwell-E 6-Core 3.6 GHz , Toshiba OCZ RD400 SSD NVMe M.2 512GB, G.SKILL TridentZ 32GB DDR4, EVGA GeForce GTX 1080 FTW ACX 3.0, 8GB GDDR5X, 8TB Raid 0, 5TB backup/hot swap, NZXT Phantom 630 case. Vegas 14, Resolve 12.5, Affinity Photo - lots of cooling <g>

NormanPCN wrote on 1/4/2017, 9:20 PM

I do have one specific question, if I have two folders, as example named low-res and hi-res with the corresponding images in each what is the reason to change the folder names, if I then point to the other folder back within the program?

There is no point to other folder command in the program. I know of no command where you can tell Vegas that for any media files it has imported from folder X, please now look for them in folder Y under the same filename.

Vegas imports specific media files and remembers the specific path/folder where the media file was imported from. Renaming the folders has Vegas transparently change hundreds of media files without any futzing around in the Vegas user interface. Of course the files in the separate folders (lowrez, highrez) must be using the same filenames.

Without using the folder name technique, you can always use the relink command in Vegas to point a specific media file to a new media file. If you have hundreds of stills/media that is a very time consuming task.

Offworlder wrote on 1/5/2017, 2:12 AM

Understood and makes sense. In this case there are about two dozen hi-res Tiff's, call them about 25MB on average.

Custom workstation build: ASRock X99 WS LGA-2011, Intel i7-6850K 15M Broadwell-E 6-Core 3.6 GHz , Toshiba OCZ RD400 SSD NVMe M.2 512GB, G.SKILL TridentZ 32GB DDR4, EVGA GeForce GTX 1080 FTW ACX 3.0, 8GB GDDR5X, 8TB Raid 0, 5TB backup/hot swap, NZXT Phantom 630 case. Vegas 14, Resolve 12.5, Affinity Photo - lots of cooling <g>