Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy Blu-ray M2V Compression Madness

  • Blu-ray M2V Compression Madness

    Posted by Tommy Nuckels on March 9, 2013 at 3:59 am

    Hey folks… Got a weird one.
    On a few projects, when I use compressor to make an M2V for Blu-rays… Around an hour in, the video falls apart. Though, only for a min or two. Then things are back to normal.

    It’s weird, I’ll run the same project on several different machines… Different bit-rates… And the same to very similar results each time. I’ve even gone so far as changing drives, software versions, presets. Nothing.

    The only thing that worked for me. Was to run it out of the Kona card on one system, into another… And no more issues.

    If you can help… I’ll owe you many-a-backrubs. (Nothing Creepy)

    Thanks for reading.
    -Tommy

    Tommy Nuckels replied 13 years, 6 months ago 4 Members · 7 Replies
  • 7 Replies
  • Steve Eisen

    March 9, 2013 at 4:20 am

    m2v is for DVD. For best results, use h.264 for Blu-ray.

    Steve Eisen
    Eisen Video Productions
    Vice President
    Chicago Creative Pro Users Group

  • Michael Gissing

    March 9, 2013 at 4:41 am

    Bluray can be either mpeg2 or H264.

  • Nick Meyers

    March 9, 2013 at 6:06 am

    sounds like the problem might be in your source file.
    how did you generate it?
    is it self contained?
    or ar you making the m2v from your FCP timeline?

    nick

  • Tommy Nuckels

    March 12, 2013 at 5:56 pm

    It’s coming from FCP, and sent to compressor for the most part.
    The only common thread, seems to be they were colored in Di Vinci. But, it’s not all Di Vinci outputs.

    Doing h.264 does seem to solve it. But, that takes a fair bit longer then M2vs… And I’m kicking out an average of 450mins of Blu-rays a week.

    It’s by far, the weirdest issue I’ve had in years.

  • Nick Meyers

    March 13, 2013 at 1:37 am

    “It’s coming from FCP, and sent to compressor for the most part.”

    as in “Send To Compressor” from the timeline?

    if yes, then my guess is that is the problem,
    and you should export a self contained QT movie, check the problem area, and then run that though Compressor.

    nick

  • Michael Gissing

    March 13, 2013 at 2:02 am

    What codec are you rendering from da Vinci Resolve?

    I think Nick is on the right track. It is always better to output a self contained QT with current settings. Apart from anything else it means FCP is free to edit while Compressor can do its encoding in the background. It is also a more reliable way to go and offers a file you can check to see if it is a problem coming from FCP.

  • Tommy Nuckels

    March 13, 2013 at 5:44 pm

    Not sure what’s being used with Di Vinci, I’ll have to check that out on future projects.
    Rendering out to a QT isn’t really an option. It takes too long, and I usually only have 5-6 hours to get the kids out the door. I’m just going to have to stick to H264 for anything colored in Resolve.

    Thanks all for your help / input.

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