Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums VEGAS Pro “blinking” pinstripe suits

  • “blinking” pinstripe suits

    Posted by Scott Mitchell on June 10, 2010 at 9:50 pm

    I am having trouble with a talking head video. The speaker is wearing a pinstripe suit. The suit seems to display properly for every keyframe (as expected) but degrades to almost black between keyframes — which results in a “blinking” effect on the entire suit.

    The source looks great (no issue with the source). The h.264 looks bad.

    Source File: Apple ProRes 422 (Full meta info below)
    Encoded as: MainConcept (full meta info below)

    Are there well-known strategies for dealing with this “blinking” problem?

    SOURCE —————————————

    Format : MPEG-4
    Format profile : QuickTime
    Codec ID : qt
    File size : 13.0 GiB
    Duration : 43mn 37s
    Overall bit rate : 42.8 Mbps
    Encoded date : UTC 2010-05-25 04:28:22
    Tagged date : UTC 2010-05-25 04:28:22
    Original source medium : 1

    Video
    ID : 3
    Format : ProRes
    Codec ID : apcn
    Duration : 43mn 37s
    Bit rate mode : Variable
    Bit rate : 40.5 Mbps
    Width : 720 pixels
    Height : 486 pixels
    Display aspect ratio : 3:2
    Frame rate mode : Constant
    Frame rate : 29.970 fps
    Color space : YUV
    Chroma subsampling : 4:2:2
    Bits/(Pixel*Frame) : 3.859
    Stream size : 12.3 GiB (95%)
    Language : English
    Encoded date : UTC 2010-05-25 04:28:22
    Tagged date : UTC 2010-05-25 04:28:22

    Audio #1
    ID : 1
    Format : PCM
    Format settings, Endianness : Big
    Format settings, Sign : Unsigned
    Codec ID : in24
    Duration : 43mn 37s
    Bit rate mode : Constant
    Bit rate : 1 152 Kbps
    Channel(s) : 1 channel
    Sampling rate : 48.0 KHz
    Stream size : 359 MiB (3%)
    Language : English
    Encoded date : UTC 2010-05-25 04:28:22
    Tagged date : UTC 2010-05-25 04:28:22

    Audio #2
    ID : 2
    Format : PCM
    Format settings, Endianness : Big
    Format settings, Sign : Unsigned
    Codec ID : in24
    Duration : 43mn 37s
    Bit rate mode : Constant
    Bit rate : 1 152 Kbps
    Channel(s) : 1 channel
    Sampling rate : 48.0 KHz
    Stream size : 359 MiB (3%)
    Language : English
    Encoded date : UTC 2010-05-25 04:28:22
    Tagged date : UTC 2010-05-25 04:28:22

    Menu
    ID : 4
    Language : English
    Encoded date : UTC 2010-05-25 04:28:22
    Tagged date : UTC 2010-05-25 04:28:22

    TARGET ——————————————

    Format : MPEG-4
    Format profile : Base Media / Version 2
    Codec ID : mp42
    File size : 135 MiB
    Duration : 35mn 26s
    Overall bit rate : 533 Kbps
    Encoded date : UTC 2010-06-08 23:08:02
    Tagged date : UTC 2010-06-08 23:08:02

    Video
    ID : 2
    Format : AVC
    Format/Info : Advanced Video Codec
    Format profile : Main@L3.0
    Format settings, CABAC : Yes
    Format settings, ReFrames : 5 frames
    Codec ID : avc1
    Codec ID/Info : Advanced Video Coding
    Duration : 35mn 26s
    Bit rate mode : Variable
    Bit rate : 489 Kbps
    Width : 594 pixels
    Height : 396 pixels
    Display aspect ratio : 3:2
    Frame rate mode : Constant
    Frame rate : 29.970 fps
    Standard : NTSC
    Color space : YUV
    Chroma subsampling : 4:2:0
    Bit depth : 8 bits
    Scan type : Progressive
    Bits/(Pixel*Frame) : 0.069
    Stream size : 124 MiB (92%)
    Language : English
    Encoded date : UTC 2010-06-08 23:08:02
    Tagged date : UTC 2010-06-08 23:08:02

    Audio
    ID : 1
    Format : AAC
    Format/Info : Advanced Audio Codec
    Format version : Version 4
    Format profile : LC
    Format settings, SBR : No
    Codec ID : 40
    Duration : 35mn 26s
    Bit rate mode : Constant
    Bit rate : 40.0 Kbps
    Channel(s) : 2 channels
    Channel positions : Front: L R
    Sampling rate : 44.1 KHz
    Stream size : 10.2 MiB (8%)
    Language : English
    Encoded date : UTC 2010-06-08 23:08:02
    Tagged date : UTC 2010-06-08 23:08:02

    John Rofrano replied 15 years, 11 months ago 3 Members · 12 Replies
  • 12 Replies
  • Douglas Spotted eagle

    June 10, 2010 at 10:50 pm

    This would suggest one of two (or both) easy possibilities, and could be a few less easy causes.
    Sounds like an interlaced source. If you have access to the source, I’d go there vs dealing with a ProRes conversion.
    Can you double the copy, offset by half a frame, set top to 50% opacity and have that cancel the effect? If it’s screwed up in the conversion, this won’t fix the problem, but that’s one of the first things I’d try.
    Why are you editing MP4 conversion? Might be a resolution issue too.
    Again…can you get your hands on the original source?

    Douglas Spotted Eagle
    VASST

    Certified Sony Vegas Trainer
    Aerial Camera/Instructor

  • Scott Mitchell

    June 10, 2010 at 11:46 pm

    Thanks for the response.

    We were not in charge of the shoot. As far as I (we) know, this is the only source available. We were told that the camera used ProRes as codec for saving the file.

    I am not editing the .MP4. I am editing in Vegas and rendering to .mp4

    Here is a very short snip that demonstrates the issue (if you have the time to take a quick look – 750Kb)

    https://drop.io/vegasfiles202/asset/cw2010-barneyfrank1-mp4

    Password: vegasfiles202

  • Scott Mitchell

    June 10, 2010 at 11:59 pm

    Thanks for the response. Apologies if this shows up twice — I am a new user and my first attempt did not post. Not sure if I was caught in moderation or if there was a tech error.

    We were not in charge of the shoot. As far as I (we) know, ProRes is the best source available.

    I am not editing the .MP4. I am editing in Vegas and rendering to .mp4 using MainConcept.

    I am deinterlacing (at least as far as I know) under Project Settings. I’ve tried both “blend” and “interpolate”

    Here is the file (if you have a moment to check it out)
    https://drop.io/vegasfiles202/asset/cw2010-barneyfrank1-mp4

    Thanks in advance!
    Password is: vegasfiles202

  • Scott Mitchell

    June 11, 2010 at 12:02 am

    Oh…and I should have mentioned…this is ultimately destined to be streamed on the web at 500K. Is bit rate the problem here?

  • Scott Mitchell

    June 11, 2010 at 12:42 am

    OK. So boosting bitrate to 10,000K solves the problem … but not really because I need to get this to 500K.

    Any expert opinions out there re: whether this will be possible?

  • John Rofrano

    June 11, 2010 at 3:40 am

    500K is the Internet setting for 3 years ago. Most YouTube videos are 2 – 3Mbps HD. Have you tried rendering to Sony AVC format with the Internet 4:3 SD 30p template. This defaults to 2.5Mbps.You can try lowering the bit-rate but for 500K I would also lower the resolution to 320×240 which is closer to the Memory Stick QVGA widescreen – 512 Kbps template.

    Your other problem is that this wasn’t shot well for internet delivery. The textured blue background is stealing bits that could be used to render the details in the suit. This should have been shot on a solid background which can be compressed easier with less wasted bandwidth.

    ~jr

    http://www.johnrofrano.com
    http://www.vasst.com

  • Scott Mitchell

    June 11, 2010 at 4:31 pm

    Based on the feedback and my tinkering, this seems like a bitrate issue.

    Interestingly enough, if I use VBR with 500K ave / 500K max instead of CBR at 500K, the video looks MUCH better. This makes no sense (to me) other than the fact that the VBR seems to do a 2 pass encode.

    Indeed, that background was not a good choice. Maybe next year we will have more input into the production instead of post, post, post production.

    Re: 2-3M bitrate. For YouTube = yes. For viewing at home or a small business over a fat pipe / cable modem = yes.

    However, large US based corporations often have limited “functional” bandwidth for their end users. The last 15 clients that I have worked with (all Fortune 500) used 500K as their MAX allowable threshold for RIA apps.

    I’m sure that all of us would agree that best approach is to provide multiple levels of quality and, ideally, smooth streaming. Our current strategy, however, is to get the lowest bitrate looking as good as possible and bumping up bitrate from there.

    While not new to enterprise software and network architecture, I am very new to video encoding. Does the above sound like a reasonable approach?

  • John Rofrano

    June 11, 2010 at 5:56 pm

    Interestingly enough, if I use VBR with 500K ave / 500K max instead of CBR at 500K, the video looks MUCH better. This makes no sense (to me) other than the fact that the VBR seems to do a 2 pass encode.

    Here is why: CBR will use the same bits on every frame even if the frame doesn’t need that many bits to represent it accurately. VBR will use less bits for frames that don’t need it and more bits for frames that do making sure that the average stays at 500K. For low bit rates you will get better encodings using 2-pass VBR.

    However, large US based corporations often have limited “functional” bandwidth for their end users. The last 15 clients that I have worked with (all Fortune 500) used 500K as their MAX allowable threshold for RIA apps.

    Then you might want to drop your resolution down to 320×240. This will give you a better encode at that low bit rate.

    ~jr

    http://www.johnrofrano.com
    http://www.vasst.com

  • Scott Mitchell

    June 11, 2010 at 6:06 pm

    Thanks for the advice re: size.

    I thought that 500K max made sure that it would never use more than that on any given frame. So, in essence, I thought that I was saying “if you don’t need 500K then, don’t use 500K … but never go ABOVE 500K”

    To me, it would seem that this should yield the same (or worse) result than 500K CBR.

  • John Rofrano

    June 11, 2010 at 8:48 pm

    You are correct in your thinking but if you got better results with VBR, I’m thinking that maybe they ignore the max if it’s the same as the average and just use the average. I don’t know this for a fact. Otherwise I agree, if Max and Avg were the same, it should be just like CBR.

    ~jr

    http://www.johnrofrano.com
    http://www.vasst.com

Page 1 of 2

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