Nigel O'neill
Forum Replies Created
-
When Vegas starts, look at the splash screen. The version information appears on that. You can also check by going to Help, About Sony Vegas Pro.
My system specs: Intel i7 970, 12GB RAM, ASUS P6T, Vegas Pro 10e (x32/x64), Windows 7 x64 Ultimate, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, Neat Video Pro 2.6
-
Wow! That must have cost a packet to shoot!
It was very well done to get the framing and distance from camera right for every location. Very impressive!
Editing was good, too.
My system specs: Intel i7 970, 12GB RAM, ASUS P6T, Vegas Pro 10e (x32/x64), Windows 7 x64 Ultimate, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, Neat Video Pro 2.6
-
If that was not green screen, he certainly has been to a lot of places! lol!
My system specs: Intel i7 970, 12GB RAM, ASUS P6T, Vegas Pro 10e (x32/x64), Windows 7 x64 Ultimate, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, Neat Video Pro 2.6
-
Could it be that DVDA recompresses the audio, even if you use the DVDA templates in Vegas? My DVDA always seems to do that, and leaves the video alone.
My system specs: Intel i7 970, 12GB RAM, ASUS P6T, Vegas Pro 10e (x32/x64), Windows 7 x64 Ultimate, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, Neat Video Pro 2.6
-
That’s interesting. I tried that before I posted and it did not work. But I was doing a simple single event copy and paste. I did not use the event selection tool.
You have just taught an old dog a new trick. Thanks!
My system specs: Intel i7 970, 12GB RAM, ASUS P6T, Vegas Pro 10e (x32/x64), Windows 7 x64 Ultimate, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, Neat Video Pro 2.6
-
Jim
You can pretty much ignore the ‘advice’ John Bean is providing. It’s annoying when that happens. He probably means well, but does not know when to admit his knowledge is incorrect.
Jim, If you think about it simplistically and logically, your source files are typically captured and compressed at a bit rate much higher than what they eventually get output to on DVD (avg 8 mbps) due to mpeg2 compression. Depending on the container used, it could be anywhere from 16~31 mbps for AVCHD, 24 mbps for HDV or 8 mbps for DV for the source footage. If you were expecting to see a 1:1 relationship between captured video and output video, we would be seeing DVD’s that would be only 30 minutes or less in duration. That’s where DVD mpeg-2 compression comes in.
Another point Stephen may be making is that Windows is quite wasteful when allocating space. Your disk comprises of clusters. If you format it using NTFS and a cluster size of 16kb, that means a 1kb file will consume 16kb on disk.
Lastly, your DVD output size can vary considerably if you use PCM or AC-3 audio in DVDA. The former results in larger DVD output files.
My system specs: Intel i7 970, 12GB RAM, ASUS P6T, Vegas Pro 10e (x32/x64), Windows 7 x64 Ultimate, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, Neat Video Pro 2.6
-
Good tip. Thanks for posting your solution as it can aid others in finding their editing nirvana.
Like Graham, I love Vegas but hate the crashes.
I moved from Avid Liquid to Vegas back in the days of v8 because it was rock solid. Since v10, things have been going downhill for me.
My system specs: Intel i7 970, 12GB RAM, ASUS P6T, Vegas Pro 10e (x32/x64), Windows 7 x64 Ultimate, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, Neat Video Pro 2.6
-
Mac
I have an FX1 as well and have no issues with editing m2t files. They should edit like butter. You say you are using SVP10, but which version? It goes from 10a to 10e. If possible, you should be running 10e.
Pixelation is sometimes caused by dropped frames. Did you notice any during the capture process? Dropped frames can mean two things: you got a bad tape or your FX1 may be in need of a service. Given that the FX1 was released in 2005, it is possible you have dirty heads.
When you say you captured in SD, do you mean DV? Did you down convert in the camera from HDV to DV?
Steve asked whether the footage played back in the camera ok, but you did not answer his question. If the footage is corrupt playing back in the camera, there may be little you can do.
The FX1’s firewire board is very sensitive to voltage fluctuations and I have heard of many an owner who has blown the on-board firewire circuitry when plugging the camera in to do a capture. You board could be on its way out, and is corrupting your captures. A DV line protector is a must with this camera.
When your tape transport mechanism dies (and it will any day now), consider getting a tapeless firewire capture device such as a DataVideo recorder. My Z1P and HC3 tranports have both died and the DataVideo recorder extends the life of what are still very good cameras optically and feature-wise.
btw, pity Sony’s VG-10 and VG-20 are so crippled feature-wise.
My system specs: Intel i7 970, 12GB RAM, ASUS P6T, Vegas Pro 10e (x32/x64), Windows 7 x64 Ultimate, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, Neat Video Pro 2.6
-
You don’t even appear to be able to do a timeline copy between versions either to or from 10 and 11 or vice versa, but you can within subversions e.g. 10a to 10c.
My system specs: Intel i7 970, 12GB RAM, ASUS P6T, Vegas Pro 10e (x32/x64), Windows 7 x64 Ultimate, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, Neat Video Pro 2.6
-
I suggested applying the FX at event level probably because it suits my multicam workflow using Vasst’s Ultimate S Pro. I can individually tweak each event if necessary. In weddings where the white balance can change rapidly as my operators are moving around looking for the best shot, splitting and correcting events is necessary at times. Of course, if I have to make a global change, not having the FX at track level does mean a visit to each event.
My system specs: Intel i7 970, 12GB RAM, ASUS P6T, Vegas Pro 10e (x32/x64), Windows 7 x64 Ultimate, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, Neat Video Pro 2.6