Brian Boyko
August 3rd, 2009, 04:44 PM
I haven't tried this yet, but theoretically, it SHOULD work. Has anyone ever considered doing anything like this - or tried anything like it, and if so, does it work?
----------
Problem: You wish to telecommute, but one of the responsibilities of your job is high definition video editing. You are limited to a 5Mbit down, 256k up DSL connection between home and office.
Possible Solution
Requires:
One Workstation Located on the Home Office LAN: ("LOCAL")
One Laptop located at the telecommuting site: ("LAPTOP")
A Virtual Private Network between the two.
Windows Remote Desktop
A copy of Sony Vegas Pro on both "LOCAL" and "LAPTOP."
Assuming the raw footage somewhere on the Home Office LAN where LOCAL can access it, I then remote desktop into the LOCAL, and drag the source files from the LAN to LOCAL's hard drive.
I then open LOCAL’s Vegas Pro application, and render out all the raw footage into two files: a high definition file at 1920x1080 & 25Mbps called [filename]_HD_Proxy.m2t, and a low definition file at 480x270 at 512kbps called [filename].m2t. One hour of this footage would result in a file that is about 225 MB. Not small, but certainly downloadable via a 5Mbps broadband connection. (roughly 6-10 minutes, actually.)
On LAPTOP, I download only the low definition file, where I cut, crop, color correct, and add graphics to the small file. I then save my edits in a Vegas source file.(“.veg”).
I then upload the .veg file (which would be about 100-300 KB), from LAPTOP to LOCAL, copying it to the same directory as the low and high definition video files. I load up Sony Vegas on LOCAL via Remote Desktop, opening the .veg file I just sent. It should load up perfectly, using LOCAL’s copy of the low definition [filename].m2t. This is just to check that the project isn't missing anything important. I then close Vegas on LOCAL.
At this point, I rename [filename].m2t to [filename]_LD_Proxy.m2t and rename [filename]_HD_Proxy.m2t to [filename].m2t on LOCAL. Relaunching the .veg file should result in Sony Vegas replacing the low definition video clips with high definition video, including all of its cuts. I then render on LOCAL, and placed the finished rendered file on the LAN for the company to access.
------------
Basically using proxy editing to get around problems with bandwidth, rather than CPU speeds. What do you think. Would this work?
----------
Problem: You wish to telecommute, but one of the responsibilities of your job is high definition video editing. You are limited to a 5Mbit down, 256k up DSL connection between home and office.
Possible Solution
Requires:
One Workstation Located on the Home Office LAN: ("LOCAL")
One Laptop located at the telecommuting site: ("LAPTOP")
A Virtual Private Network between the two.
Windows Remote Desktop
A copy of Sony Vegas Pro on both "LOCAL" and "LAPTOP."
Assuming the raw footage somewhere on the Home Office LAN where LOCAL can access it, I then remote desktop into the LOCAL, and drag the source files from the LAN to LOCAL's hard drive.
I then open LOCAL’s Vegas Pro application, and render out all the raw footage into two files: a high definition file at 1920x1080 & 25Mbps called [filename]_HD_Proxy.m2t, and a low definition file at 480x270 at 512kbps called [filename].m2t. One hour of this footage would result in a file that is about 225 MB. Not small, but certainly downloadable via a 5Mbps broadband connection. (roughly 6-10 minutes, actually.)
On LAPTOP, I download only the low definition file, where I cut, crop, color correct, and add graphics to the small file. I then save my edits in a Vegas source file.(“.veg”).
I then upload the .veg file (which would be about 100-300 KB), from LAPTOP to LOCAL, copying it to the same directory as the low and high definition video files. I load up Sony Vegas on LOCAL via Remote Desktop, opening the .veg file I just sent. It should load up perfectly, using LOCAL’s copy of the low definition [filename].m2t. This is just to check that the project isn't missing anything important. I then close Vegas on LOCAL.
At this point, I rename [filename].m2t to [filename]_LD_Proxy.m2t and rename [filename]_HD_Proxy.m2t to [filename].m2t on LOCAL. Relaunching the .veg file should result in Sony Vegas replacing the low definition video clips with high definition video, including all of its cuts. I then render on LOCAL, and placed the finished rendered file on the LAN for the company to access.
------------
Basically using proxy editing to get around problems with bandwidth, rather than CPU speeds. What do you think. Would this work?