Forum Replies Created

Page 2 of 2
  • Robin Rudy

    July 15, 2008 at 2:24 am in reply to: QT file dimensions/ codec and Streamclip export

    Thanks, Richard.

    MacBook Pro / Intel Core 2 Duo / 2.2 GHz /
    2 GB memory / 800 MHz / FCP 5.1

  • thanks. but I should not export from fcp and make an m2v initially– first i need to make a quicktime, is this correct? thanks. or can i just export from fcp into compressor to make the m2v and then import this into dvdsp?

    MacBook Pro / Intel Core 2 Duo / 2.2 GHz /
    2 GB memory / 800 MHz / FCP 5.1

  • Rafael thanks.

    I’m sorry if this sounds like an obvious Question but:

    I am exporting via fcp to compresor making a quicktime and then bringing this into dvd sp, right? DVD sp will convert thie quicktime into an m2v, and then burn is this correct?

    Thanks so much.

    MacBook Pro / Intel Core 2 Duo / 2.2 GHz /
    2 GB memory / 800 MHz / FCP 5.1

  • Thanks. I made the qt in compressor and then brought it into dvdsp. Tried to burn, and DVD will not burn — error “bit rate too high.”

    Do you have any suggestions– should i just do a 1 pass vbr when making the quicktime to lower the bit rate? is this how I would lower the bit rate?

    or should I bring the QT I made into compressor to create the m2v?- would this affect the bit rate?

    Thanks again for any help, I am hopeful my questions are clear.

    MacBook Pro / Intel Core 2 Duo / 2.2 GHz /
    2 GB memory / 800 MHz / FCP 5.1

  • Hi, ok, thanks… for some reason I am confused, will check on the thread in the am…

    ok so i am using compressor twice?
    once from the timeline in fcp via compressor make a quicktime, this is converting the master ntsc into a pal qt?

    then import this new pal qt into compressor again to make m2v?

    isn’t is possible to import the new pal qt made via compressor into dvd studio pro?

    thanks again.

    MacBook Pro / Intel Core 2 Duo / 2.2 GHz /
    2 GB memory / 800 MHz / FCP 5.1

  • Thanks, ok, so I would just go ahead and nest the 3:2 sequence into a newly created pal sequence.

    Additionally, do I need to have anamorphic and 4:3 footage on 2 separate tracks so they are encoded separately when sending to compressor?

    With the tests I have done thus far, the 16:9 and 4:3 footage have different letterboxing ratios in the compressor preview; I have compensated for this via cropping in the inspector in compressor.

    And is it possible to simply export from a dv ntsc timeline with 4:3 and 16: 9 footage in a 3:2 sequence into compressor and select the compressor advanced format conversion option, changing/ reencoding in compressor from dv ntsc to pal?

    Once in compressor:

    should I create an mpeg 2 or a quicktime?
    should I be using DV PAL or PAL Anamorphic?

    as an mpeg2
    video format: pal
    aspect ratio 16:9
    quality 2 pass vbr

    and if exporting as a quicktime, should video be interlaced or progressive?

    I’ve also researched that the frame controls should be changed :
    custom
    resize filter: best
    output felds: same
    deinterlace: better
    rate conversion: better

    Thanks for any help. I truly appreciate it!

    MacBook Pro / Intel Core 2 Duo / 2.2 GHz /
    2 GB memory / 800 MHz / FCP 5.1

  • Hi Paul,

    Thanks. This makes sense. Problem is, when I am looking at other sequences with the same set up that have not been rendered ther e is *no* pixilation. And before the render, during playback, this “sequence 5” did not look pixilared at all. I also find it curious, that when I go to previous edits of this now rendered sequence, that are saved in different project files, say, from a week ago, they too look pixilated. It is as if this one render in this one sequence has corrupted the media file? But when I go to the QT in capture scratch and scrub through them — the QT does not look corrupted.

    All the Best,
    RRudy

    MacBook Pro / Intel Core 2 Duo / 2.2 GHz /
    2 GB memory / 800 MHz / FCP 5.1

Page 2 of 2

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