|
|||||||||
|
Thread Tools | Search this Thread |
July 28th, 2009, 02:38 PM | #1 |
Regular Crew
Join Date: Jul 2009
Location: OC and LA
Posts: 56
|
Canon 5D Mark ii and Sony Vegas Pro
How is everyone encoding the H264 into Vegas? Are you using MPEG streamclip? I converted a few clips via MPEG Streamclip from H264 to AVI's.
What works for you in Sony Vegas Pro? Canon 5D images....
__________________
Canon DSLR's, C100, C300. FCPX, Sony Vegas Pro. Assorted Nikon, Canon, Zeiss lens. |
July 28th, 2009, 03:02 PM | #2 |
Regular Crew
Join Date: Mar 2003
Location: Netherlands
Posts: 126
|
I'm currently working in Vegas on a rather large project shot with a Mark II.
What I did: I loaded OSX on my pc (yes, the hacked one) and used After Effects C.S 4 to transcode all clips to Apple ProRes 4-2-2 1920x1080 (You can also use Final Cut or Premiere) Those ProRes files can actually be used on Windows (Vegas or Premiere) because Quicktime has a ProRes decoder. Just install the latest quicktime. Playback on Vegas is rather good. I can have realtime 30fps playback with 2 effects loaded! (black & white and contrast / brightness adjustments) However I do have some bad news... for some reasons unknown to mankind, Vegas recently started behaving like its a pre-alpha program or something: Random hangs, out of memory messages when opening projects, unable to open the project the first try (second try it magically works!) Im running the 64 bit version, but the 32 bit version couldn't even open the last 5 saved (by the 64 bit version) projects at all. As a last resort I exported to a EDL and re-imported again. This 'fixed' the problem of the 32 bit version being unable to open the projects saved by the 64 bit version, but the rest of the bugs is still there... Its near being unworkable. But the weird thing is, it worked like a charm until 2 days ago! I even installed an image of WinXP SP3 64 bit (im running Windows 7 RTM) That image was created when there were no problems at all, but even that doesn't help... Needless to say I did try other solutions: Trying Vegas Pro 9.0a instead of 9.0, reinstalling, running as administrator, updating video drivers etc etc... I looks like Vegas just goes totally NUTS when you reach a certain number of clips and/or megabytes of footage... (using ProRes 422 that is) Maybe it works for you, but my advise is to test deeply (load lots of prores 422 clips!) and see what happens! |
July 28th, 2009, 03:31 PM | #3 |
Inner Circle
Join Date: Nov 2005
Location: Elk Grove CA
Posts: 6,838
|
Using NeoScene from Cineform to transcode to edit.
__________________
Chris J. Barcellos |
July 28th, 2009, 04:42 PM | #4 |
Regular Crew
Join Date: Jul 2009
Location: OC and LA
Posts: 56
|
Has anyone compared MPEG stream clip to Neoscene?
Thomas
__________________
Canon DSLR's, C100, C300. FCPX, Sony Vegas Pro. Assorted Nikon, Canon, Zeiss lens. |
July 28th, 2009, 08:13 PM | #5 |
Trustee
Join Date: Sep 2005
Location: Singapore
Posts: 1,498
|
So far Neoscene works well for me. Except V9a x64 doesnt read the avi. V9a x32 and V8c works well
|
July 28th, 2009, 10:09 PM | #6 |
Inner Circle
Join Date: Nov 2005
Location: Elk Grove CA
Posts: 6,838
|
I downloaded streamclip, and converted to an AVI file. I didn't adjust settings for a 2.5 minute clip. I rendered out an AVI file. It seemed pretty clean in playback. File size was 7 gigs though, from a .75 gig original, and it took about 10 or 12 minutes to convert. I did the same file with NeoScene, render in about 1 and half minute to two minutes. Resulting file was 2 gig. Playback was similar to the Streamclip though I think Neoscene result has a bit more range, consistant with NeoScene claim that it adjust level values properly in the conversion process. Neoscene also retimes the footage to 29.97 frps, so on the Vegas time line, it isa bit longer against the streamclip, and the orginal files.
__________________
Chris J. Barcellos |
| ||||||
|
|