Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Compression Techniques Encoding Profile Specs – on My Mac?

  • Encoding Profile Specs – on My Mac?

    Posted by Chad Mitchell on March 29, 2007 at 8:34 pm

    Hello Everyone,

    We are working on a video back catalog digitizing project. The final video specs were decided upon by our U.S. counterparts, so I “HAVE TO” follow these specs exactly. They have invested in a StreamZ encoding system to convert our betas into this :

    MPEG2 4:2:2
    720×512 frame (VBI retained)
    Full frame rate (29.97 fps)
    Interlaced (assuming the digibeta tape is interlaced)
    25 Mbps video bitrate
    Audio: MPEG1 Layer 2, 384 Kbps, 48 Khz

    Here is Canada – we don’t have quite as much video to back catalog. Does anyone know if these specs could be met using Final Cut Pro and my Kona LH system? Would I be able to add software like Episode Pro etc. to convert uncompressed 10-bit video into this format? We’re basically just trying to save cash – even at the expense of the process taking longer.

    Much Much thanks,
    chad.

    Juanpipito replied 19 years, 1 month ago 4 Members · 16 Replies
  • 16 Replies
  • Daniel Low

    March 30, 2007 at 11:30 am

    DigiBeta is 8bit, 4:2:2 @ 2:1 compression. Capturing that at 10bit uncompressed is a waste of space and processing.

    On the encoding side I’m not sure either Compressor or Episode (or Digigami) can output 25Mb/s MPEG-2 at 4:2:2. – This is generally only available on hardware encoders.

  • Craig Seeman

    March 30, 2007 at 1:10 pm

    [Danny2007] “On the encoding side I’m not sure either Compressor or Episode (or Digigami) can output 25Mb/s MPEG-2 at 4:2:2. – This is generally only available on hardware encoders.”

    Episode can certainly do MPEG-2 Program streams at 25Mb/s 4:2:2

  • Chad Mitchell

    March 30, 2007 at 1:21 pm

    Thanks for your help and quick responses, Danny and Craig.

    I’m also not familiar with the frame size – although I’m sure it doesn’t matter that I understand it. Could you fill me on what VBI retained means?
    As far as the audio goes – these encoding apps could handle that as well then? And I’d end up with a file containing both video and audio?

    I’ll have to see if I can get the Episode Pro demo installed for a second time – it expired and I never had the chance to try it out properly….

    cheers,
    chad.

  • Craig Seeman

    March 30, 2007 at 1:47 pm

    [Analog Chad] “Could you fill me on what VBI retained means?”

    VBI is Vertical Blanking Interval.

    NTSC is 525 lines including the VBI but that’s not to be confused with pixels.

    In the vertical interval there can be Vertical Interval Time Code (VITC) and Closed Captioning so they may be trying to preserve that information.

  • Daniel Low

    March 30, 2007 at 1:58 pm

    VBI = Vertical Blanking Interval. An area that can hold teletext, VITC timecode and closed captioning.

    Again, I’m not sure if Episode will retain this, or indeed if it’s even ‘captured’ by the Kona card. Craig?

    Audio – yes, no problem, ending up with either a muxed file or seperate audio and video files.

  • Craig Seeman

    March 30, 2007 at 2:08 pm

    If you (Danny) or Chad are willing to FTP (I’ll provide the FTP space) 30 or 60 seconds or so of a file as 8 or 10 bit uncompressed with VITC or CC info, I’ll give this a go around.

  • Chad Mitchell

    March 30, 2007 at 2:24 pm

    Oh man, that would be most excellent. As was mentioned, we weren’t sure if my Kona could capture VITC – but I’d be happy to provide a test file….coming up…

  • Craig Seeman

    March 30, 2007 at 2:42 pm

    If you send me your email address I’ll send you FTP info.

  • Chad Mitchell

    March 30, 2007 at 3:09 pm

    chad dott mitchell att sonybmg dott com

    should do the trick. c.

  • Daniel Low

    March 30, 2007 at 4:16 pm

    This is a great example of how these forums can work!

Page 1 of 2

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