Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Adobe Premiere Pro What format does CS6 prefer from DR-HD100?

  • What format does CS6 prefer from DR-HD100?

    Posted by Bob Gale on October 21, 2013 at 7:35 pm

    Hi,

    We migrated earlier this year from Avid Liquid Chrome to Premiere Pro CS6. We still shoot SD (budgeted for HD next year) on a JVC GY-DV500 recording to a DR-HD100 DTE through DV cable.

    The Chrome liked AVI Type 2 files best (meaning no rendering required). The same files on CS6 require rendering. Does anyone know what CS6 likes best, or looks best?
    The choices on the HD100 are: Raw DV, AVI Types 1 and 2, Canopus AVI, Matrox AVI, MXF, OP-Atom; Quicktime; Avid OMF, Quicktime 24p, AVI Type 2 24p, and Pinnacle.

    I can do some testing if no one knows, just thought I’d try here first.

    Thanks,
    Bob

    Bob Gale replied 12 years, 6 months ago 2 Members · 4 Replies
  • 4 Replies
  • Tim Kolb

    October 22, 2013 at 9:21 pm

    I haven’t edited DV in some time so I haven’t really had any experience with DV footage inside recent versions of Premiere Pro.

    If you are on a Windows machine, I’m a little surprised that you have to render the AVI 2 files frankly.

    How are you creating your edit sequence?

    TimK,
    Director, Consultant
    Kolb Productions,

    Adobe Certified Instructor

  • Bob Gale

    October 24, 2013 at 7:57 pm

    Tim,

    Thanks for the reply.

    My sequences have the same properties as the video files: 720 x 480, 0.9091 pixel aspect ratio, editing mode is DV NTSC, 29.97 fps)

    Interestingly, when I check the properties of the files from the HD100, the ‘type’ is listed as Matrox AVI even thought the unit is set to record AVI Type 2.

    Also, the video files I have that don’t need rendering are clips I digitized through the Liquid Chrome from MiniDV tapes before we had the HD100. The extension on these clips is .dif, and they are listed as a ‘QuickTime Movie’ files. Otherwise, the image size, frame rate and pixel aspect ration are the same.

    This is not a problem for me really, as render times are very reasonable, I was just curious about why I need to render these clips at all.

    Thanks,
    Bob

  • Tim Kolb

    October 24, 2013 at 8:39 pm

    It’s the Matrox wrapper…meant to be realtime with Matrox hardware once upon a time.

    Back in the day these wrappers all read as being foreign unless you had the manufacturer’s decoder installed…usually on their card.

    AVI2 should run with no red line…though I can’t believe you’d have to render much as the format is so small and lightweight for any modern computer…the red line doesn’t mean you HAVE to render, it just warns you of a perceived setting mismatch between the media and the sequence or of the application of enough effects that they may not be able to be rendered in realtime for preview…

    I just play through most things with a red line, but I do recall that Matrox wrappers could be problematic back in the day, particularly when rendering from AE to a Matrox DV wrapper for use on a Matrox DV timeline…this seemed to be an issue periodically.

    I thought that Focus Enhancements used to have a piece of software you could use to rewrap media from these recorders if it’s an issue…

    TimK,
    Director, Consultant
    Kolb Productions,

    Adobe Certified Instructor

  • Bob Gale

    October 24, 2013 at 9:03 pm

    I should have been more clear on what I meant by ‘render’. I’m getting a yellow render line, not a red one, so I’m not having any issue with playback. Even the red lined clips usually play back nicely.

    I was just trying to figure out why I was not getting any colored lines with the same clips in Liquid Chrome that are yellow in Premiere. And also making sure I was selecting the recording format in the HD100 that Premiere likes best.

    Is AVI type 2 as good a choice as any of the others?

    Thanks,
    Bob

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