Forum Replies Created

Page 5 of 8
  • Marc Istook

    September 13, 2007 at 5:23 am in reply to: Interlaced Rendering Problem (Vegas 7e)

    That’s not accurate, at least not on my Vegas. When rendering DVD Architect default mpeg2 streams, it’s set to ‘interlaced, bottom field first’.

  • Marc Istook

    September 13, 2007 at 5:20 am in reply to: speeding up footage for time lapse…

    Another tip — decide if you want any motion blur between the frames you’re keeping. If you speed it up 12X, you’re basically throwing away 11 frames and keeping every 12th frame, and Vegas will, by default, add a bit of frame blending between those frames, which might not necessarily give you the time-lapse look you want. If you want to go without those blended frames, right click on your video and select “disable resample”. That way each 12th frame will remain unchanged without unnecessary frame blending added.

  • Marc Istook

    September 13, 2007 at 5:13 am in reply to: Is Vegas 8?

    That doesn’t seem to make sense. P2 workflows don’t just encompass DVCProHD — they also include anything shot using DVCPro50 or DV — both of which you can shoot on Panasonic’s HVX-200 camera on P2 cards, or on regular DVCPro/MiniDV tapes and then ingest to Vegas traditionally. So it would seem to me that it’s not a codec issue — it’s a P2 issue.

    Responding to: —The lack of support for DVCPro HD has zero relationship to Sony selling XDCAM or any other format camcorder.
    Panasonic chooses to whom they’ll give the codec licenses to and whom they’ll charge big bucks.
    If it had anything to do with who is selling what cameras, why do you suppose that Adobe only announced DVCProHD support last week, yet it’s one of the very popular NLE systems? The only reason Adobe now has DVCProHD is because of their acquisition of Serious Magic. Otherwise, one could easily bet the farm that Adobe never would have had DVCProHD support due to the cost of the license. Some manufacturers allegedly paid nothing for DVCProHD licensing. I don’t know if that is accurate or not, but I’m positive regarding the cost of the license to some developers.
    Aside from that, DVCProHD is effectively dead, just like everything else DV-based. AVC-I is their next big thing, as Grass Valley is now J2K and Sony is XDCAM.—

  • Marc Istook

    June 28, 2007 at 8:00 am in reply to: Interlaced Rendering Problem (Vegas 7e)

    Field order can cause big problems, especially when you’re going out to DVD. You might never notice when watching on your computer monitor because your monitor isn’t showing you interlaced video, field by field — it’s showing you the entire, progressive frame.

    If you’re having trouble with your source footage having a different field order than your output (DVD and DV use lower field first), the fix is simple. In your project media window, right click on the media file(s), and scroll down to properties (I think — I don’t have Vegas up right now!). From there, you should be able to find a setting for the field order of your video. If it’s upper field (odd field, I believe) first, simply change it to lower. Make sure to change that for each video file you’re using in your project and you should be good to go.

    I ran into this problem when using some XDcam footage recently in Vegas that I was outputting to DVD. Static shots looked fine, but anything with motion was awful. Oddly enough, Vegas never told me about the field order conflict — with such a common workflow, I’d think there’d be a popup warning, or something that would’ve let me know my source field order didn’t match the output. Anyway, hopefully that helps.

  • Marc Istook

    April 16, 2007 at 3:15 pm in reply to: Vegas and the HVX-200

    Great Ron. Thanks for the advice!

  • Marc Istook

    April 9, 2007 at 3:24 pm in reply to: XDCam and Vegas!

    No, SD. Though I imagine the problem would be the same regardless. Apparently, the PDZ-1 software has output options for Avid and the old Sony BVE-9100s — but those EDLs don’t import properly into Vegas, and when you look at the text files, they don’t contain an absolute reference to the proxy clips. VERY frustrating!!

  • Marc Istook

    April 9, 2007 at 4:08 am in reply to: XDCam and Vegas!

    PDZ saves the “edit list” as an .smi file, which Vegas will not open. And if you open the .smi file in a text editor, save it as a .txt and try to open it in Vegas, it says the file is in an unsupported format.

  • Marc Istook

    April 8, 2007 at 4:27 pm in reply to: XDCam and Vegas!

    I’ll try that. But what option should I choose when exporting? The edl doesn’t look like a text when I saw it in a text editor… I’ll try and keep you posted. Thanks again!

  • Marc Istook

    April 8, 2007 at 2:41 pm in reply to: XDCam and Vegas!

    Thanks for your response… But drag the EDL from where? None of the PDZ-1 export options seem to be an obvious choice for import into Vegas, and I’ve tried saving it in every format and so far, Vegas won’t open any of them. Upon reading the text versions of all these files, none of them contain absolute references to clips (in other words, they reference a clip, but not a filename or hard drive location, etc.). Remember, I’m not saving the EDL to the ProDisc — it’s gotta be saved from the PDZ-1 software somewhere on a hard drive, and so far it doesn’t seem like that works.

  • Maverick,

    It’s quite possible that your mpeg video is flagged somehow at 24p. What kind of footage is it? If it is 24p, and you’re editing on a 29.97 timeline, or vice versa, it’s possible that on a frame-by-frame conversion, the media is getting out of sync. Try playing with the properties box (Alt-Enter) to see if changing the timeline’s layout (from 29.97 to 24p, or vice versa) makes a difference.

    Just a guess… who knows?

Page 5 of 8

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy