Pixellation in WMV renders

I've got another question for my fellow playheads.
I've been rendering my projects out as WMVs in Premiere Pro CS4, and while most of
the video comes out fine, in some spots, it comes out excessively pixellated.
I'm working with HD 1920x1080 sequence settings, 24 fps.
I've noticed that this usually happens in spots that are set up as follows:
Video Track 3:   [Transition][PNG-------------------------------------------------------][Transition]
Video Track 2:                      [Transition] [M2TS---------------][Transition]
Video Track 1:   [Transition][JPG--------------------------------------------------------][Transition]
Here are some screenshots of said glitchiness:
http://img704.imageshack.us/img704/5650/glitchy1.jpg
http://img194.imageshack.us/img194/1263/glitchy2.jpg
http://img202.imageshack.us/img202/8786/glitchy3.jpg
And here are my render settings.
http://img576.imageshack.us/img576/6143/glitchysettings.jpg
Will increasing the Bitrate solve this? I tried going from an average video bitrate of 1250
and a peak video bitrate of 1500 to an average video bitrate of 1500 and a peak video
bitrate of 2000, and it really didn't fix much. The next step is bumping it up to 3k - 4k,
though this could prove problematic due to file size constraints.
As always, much thanks in advance!

Dan,
That would be my first step in the process.
Also, I'll be that a few users, like Ann Bens, who does do a fair amount of WMV Export, will have some comments there too.
Though I do not see it mentioned that often any more (maybe PrPro has gotten better in later versions with WMV Export?), but going back a bit, many swore by Windows Media Encoder (free from MS) for WMV Export. Might be worth a look too.
Good luck, and give those users a moment to find this post. For instance, Ann and Harm Millaard, are in Holland, so they are usually around here at different times, than folk like me, who are in AZ, USA.
I'll follow along to see if things improve for you, and also what they say about the Export settings.
Hunt

Similar Messages

  • Pixel dimensions not rendering correctly with Extract Assets?

    Was really excited to hear about extract assets and have been trying to set up a new workflow but am having some difficulty. My PSD is set up ay 2x size, so I need to create 1x-sized assets. My 1x-sized assets are rendering with a 1px white line around them and I can't figure out why this is happening? I have tried both with the .5x button selected and also speccing the required pixel dims in the layer name, and both produce the same result.
    In my layer name I have: [email protected]%, 498x440 filename.jpg-85%
    The resulting asset is 500x442px and has a 1px white line around it
    What am I doing wrong?

    Hi can you email me your PSD file? My email ID is: [email protected]

  • WMV Rendering problems happened out of nowhere

    I've had no problems with AE before. I'm using a photo slideshow template with some nice transitions and effects. Worked just fine when I exported it to WMV for months. In fact I've rendered the same eact file several times. However I wanted to make one final picture change and now all of a sudden when I render it to WMV, the footage is slow, choppy and very distorted. I tried rendering it to Quicktime and it seemed to work. So did H.264 but it was low quality.
    I even opened up other AE projects and they all now render choppy, distorted video when output to WMV (it never did that before!). Not sure what happened because I didn't change anything in the settings at all. I've even tried uninstalling and re-installing, and it still renders out the same slow, choppy, distored video for WMV. I'm at a complete loss!
    Please help

    Either a Windows Update changed some Media Player components or you updated/ changed the graphics driver. Verify the files on another system. If they play fine there, then investigate these things on your own system.
    Mylenium

  • Graphics are Pixelated During a Rendered Playback

    I am editing 720x480 DVCPro-NTSC footage in 720x480. I have an intro that is all graphics. When I play back, the graphics are noticeably pixelated...even after it is rendered. Is there a filter or setting I should apply to correct the problem?

    I think I might have solved my own problem. I added a De-interlace filter to my logos and text and they look better. The De-interlace was set at "Flicker Filter Max".
    Does anyone know why this problem happens?
    I'm editing the video in 720x480 and a video in 1280x1080. They use the same logo that I built. I built the logo in a 1280x1080 sequence. The logo looks great in 1280x1080, but pixcelated in the 720x480 (mainly around the edges). Any answers to that?

  • FCP text is ultra-pixelated even after rendering. How do i fix it?

    I've been working with FCP for a while now and this is an issue I've had a few time before. Sometimes it happens and sometimes it doesnt. thing is, i dont do anything differently from time to time. But its been happening every time lately. Even after I render, the text in FCP is very pixelated. It looks nice when im in the program, in my canvas, but then i view it full screen or export and the text looks terrible. Also, I've been using livetype files that are fully rendered and look great in livetype and after i render them from livetype, but the same thing happens. Am i missing something? Please help. I edit a show called Seesmix and it has happened pretty much every time with this show. I export it as .mp4. So if you want to see what im talking about, you can check out the show on youtube... http://youtube.com/profile?user=seesmix.
    thanks for reading and please help!

    i've seen your video and your text seems fine to me. are you planning to ever have this broadcast on television? if so then there may be an issue. but if everything is webcast then it looks fine. i'd tell you to view everything on an NTSC monitor before air but i'm not sure if you are going to need it.
    you mentioned that when you 'watch it full screen' that the text looks bad. do you mean full screen on youtube or fullscreen on your comp monitor? how big of a monitor is it? everything will look like garbage if you expand it beyond the size that it was intended for. it's like, HD stops being HD if you look at it on a huge monitor. pixels get larger and you lose definition.

  • Pixelated Footage AFTER rendering

    I shot my footage on the Panasonic HVX and when I imported it to my project, everything was fine. BUT, whenever I make an adjustment to the footage that requires rendering, the footage comes out (after the render) VERY pixelated.
    I set my sequence settings correctly (DVC Pro HD 720p60), I've tried outputting, and I've tried changing the rendering settings. AND I've worked on 3 different computers. NONE have worked.
    Any help? It'd be GREATLY appreciated

    is this happening on any effect applied to any clip or is it more specific?

  • How to Decrease Pixelations on WMV Output with PE3, PE4, or PE7?  Settings?

    Hi everyone, Hope someone has a reason for this.
    Doing some .MOV conversion to WMV. I have found some variations depending on computer and platform. I'm not satisfied with the results using Flip4Mac, PE3 or PE7 (see below).
    I have found the best results by using QT pro to first convert the .MOV file to .MP4. Then using PE4 on my quad-core Desktop to convert to WMV with the following settings:
    Video Tab:
    Codec: WMV 9
    Allow interlaced processing box (unchecked)
    Encoding passes: 2
    Bitrate: Variable unconstrained
    Width: 640
    Height 480
    Frame Rate 12
    Pixel aspect: square 1.0
    Decoder Complexity: Auto
    Keyframe interval: 5
    Buffer Size: Default
    Average Video Bitrate 928
    Audio Tab:
    Audio Codec: WMA 9.2
    Encoding Passes: 2
    Bitrate Mode: Variable Unconstrained
    Audio format: 48kbps, 44khz stereo VBR
    Audiences tab
    Compressed
    Average kbps: variable
    The big question is that I'm trying to repeat this quality using PE7 or PE3. I have been unable to do this despite using the exact same settings with a trial version of PE7 with the Windows XP on my BootCamp and VMWare. I've gone line by line with the Export Settings. I even downloaded the WMP 11 to make sure that wouldn't change the encode.
    The only thing that is different is the audio codec (9.2 on PE4 and 9 on PE7).
    Any thoughts as to why the PE4 would be pretty good (not as good as the original .MOV of course) but the PE7 would be very pixelated and grainy with the same settings? Also Flip4Mac is not very good either.
    Just trying to avoid creating the .MOV on MacBook, then needing to run the conversion on desktop and then move back.
    Thanks.

    That's strange. I responded earlier and the whole message got trashed. Hence the test post before retyping the entire thing again.
    Thanks for the reply.
    The video clip is a single screen capture video clip. This is what I've found by playing around with this more.
    The original clip resolution is greater than 640x480. If I use QT Pro to convert the original clip to 640x480 and then use either Flip4Mac or PE7, then the resolution looks good.
    Just trying to figure out if should keep all workflow on the MacOS side. There are several different version of Flip4Mac. $49 gives me 640x480, but if I ever want to make it slightly larger then I would need to go with the $99 or HD version.
    I also tried to export to AVI with QT Pro and the import with Windows MovieMaker but it didn't work really good. I liked the simplicity (since PE7 hogs a lot of resources especially through VMWare).

  • Pixel Bender not rendering preview

      After I have been using Pixel Bender for a while it will stop rendering a preview of the adjustments that have made.  This will occur with any type of file of any size.  It doesn't matter what filter I am in or go to once I get a blank screen, it stays that way.  I can see a preview again if I zoom far out so that the image is really small (12% or smaller) and then I can increase the size to see it at full size again.  The only way to fully correct this issue is to restart my computer.  Shutting down Photoshop and restarting it does not solve the issue. 
    My setup:
    Windows 7 64-bit
    Photoshop CS5 64-bit
    XFX Nvidia 8800 GTX  768 MB
    Intel Q6600 2.4GHz

    I'm assuming that this only happens if you are in GPU mode? If you switch to CPU mode does it still happen? If you make some changes and then click "OK" are those changes applied to your original image even if the preview stopped working?
    Shutting down Photoshop should fix the issue because the GPU driver is really tied to the process. Are you using transparent windows in Win7? Do those stop working when this happens?
    Sorry for all the questions, we haven't seen this issue before.
         Kevin

  • Another vote for restoring H.264 and WMV rendering support

    Hello!
    I love the new features which have been added to Adobe CC 2014.
    However, removing the ability to render H.264 (MP4) or WMV essentially makes the program useless for me.
    Adding AME to the workflow process is a considerable time-waster.
    If anything, I'd think new program versions would add support for more render formats, not remove them?
    If you could add H.264 and WMV support back in, I'd really appreciate it?
    Thanks.

    XDude.com! wrote:
    Hello!
    I love the new features which have been added to Adobe CC 2014.
    However, removing the ability to render H.264 (MP4) or WMV essentially makes the program useless for me.
    Adding AME to the workflow process is a considerable time-waster.
    If anything, I'd think new program versions would add support for more render formats, not remove them?
    If you could add H.264 and WMV support back in, I'd really appreciate it? Thanks.
    I think if you run side-by-side tests using AME and transcoding while the render is taking place you'd see the AME route is actually slightly faster.
    But there is a far more compelling reason for the functions to have been separated and that has to do with how After Effects is used by most, not all, of its intended audience. Comps and effects sequences are expected to be pieces of larger projects and not necessarily to be self-contained clips. From a production workflow, having the full rez version of an AE project on a drive and then using it in a transcoder like AME or Compressor to export many different codecs at once is far more efficient. But only for one reason: I have the master AE clip and can do anything with it. If I export directly out of AE to, say H.264, I cannot use that clip directly in most of the other applications my AE clips go through on their way to release.
    The perceived convenience of being able to go directly to H.264 from AE is not really rendering, it's a process of transcoding. And that's complicated by the number of adjustments available to any codec's processor, adjustments that will dramatically affect the compressed file's appearance and size.

  • WMV rendered in AE-CS3 looks gray in PowerPoint 2007

    I've been trying to produce a wmv from Adobe After Effects CS3 to insert into a PowerPoint presentation. Both the video and the powerpoint presentation have a white background. The problem is that is seems like no matter how I tweak the settings in the encoder for WMV the colors come out washed out and the white background comes out gray. I've tried making all the whites 253,253,253 thinking maybe it was an issue with the gamut differences between tv and screen, but that didn't help, it's still gray.
    I'm practically pulling my hair out on this one. I thought wmv was suppose to work pretty well with PowerPoint? Are there specific settings I need to tweak somewhere to make this work?

    Actually I already tried that and while it did fix the background issue, it made the rest of the video look bad. From what I've read its not designed for highly animated videos, which mine is, so even at a higher quality it seems to stutter and the images appear to be at a lower color depth.
    Maybe I'm setting it wrong?

  • One pixel difference between rendered video and composition

    I have a non-standard dimensions (767 x 454) in my composition, but the finished render becomes (766 x 454). Does video generated need to have even-numbered dimensions? If not, how can I get it use to 767?
    Thanks,

    Depends on the CoDec. Most compression methods involving visual compression (MPEG etc.) are indeed based on multiples of 2, 4, 8, 16 and so on, so this is normal. Only algorithms that only use compression on the binary level do not suffer this limitation (QT Animation, PNG etc.) but even then you can find many who are locked into specific resolutions and field settings because they provide optimized routines for standard broadcast resolutions such as e.g. the Avid CoDecs do.
    Mylenium

  • Text rendering on MacBook Pro differs from PowerBook.

    It appears that various applications use a different text rendering technique on the MacBook Pro than on the Powerbook. Camino for instance uses sub-pixel rendering on the PowerBook but standard anti-aliasing on the MacBook Pro. So do Word and MSN and others.
    At first I thought it had something to do with the app being universal or not. But Camino is supposed to be a universal binary.
    Anyone has a clue about why this difference?
    (You can easily see if sub-pixel or standard rendering is used by zooming in with option-cmd-8. Standard rendering has only shades of gray. Sub-pixel rendering uses colors. More on OS X text rendering can be found here: http://daringfireball.net/2003/11/panthertextrendering.)

    First, I wonder - does it look good or bad? Or, is this simply a comment that it is different?
    Second, and I'll bet this is your answer, is that the difference is most likely due to the type of video card being used. I notice that nothing effects rendering of fonts like the type of video card.
    I am interested because I will be doing lots of text work on my MBP, and would like to know if there is an issue with this. I had a notebook (Toshiba) about three years ago that the text was soft and nothing I could do would make it sharper. I ended up dumping the notebook and getting something else. MS Cleartype seems to work to some degree in Windows machines, but I don't see anything like that on my PB. However, the PB is fine as it...
    Bob

  • Html -- less than a whole pixel

    I am trying to align an image height as "17.2" pixel but iphone renders the image height as 17 pixel. Is there any way I could get it to work for less than a whole pixel value. I minimally tried adjusting the border etc..
    thanks,

    yes,
    it is sure a problem
    i want to know also.

  • Pixelated jpg image files

    Muse 7.2, OSX 10.9.2
    I have inline images and a gallery slideshow on a site.  Some of these images are extremely pixelated on the rendered web page.  All the images were sized in Photoshop to the exact pixel dimensions and saved as  saved-for-web jpegs in Photoshop.
    Several of the inline images have been on my site for about a year and only recently appear pixelated.  I'm making some edits to my site but have not touched any of the images that are now pixelated.  Also, I have embedded the links to all images so Muse need not search through my computer for the image source files.
    I did replace one pixelated inline image with the same source file, but with a different file name.  For some reason this image now renders properly.  However this technique did not have any benefit on several images in a slideshow gallery that has both thumbnails and full size image.
    What's your opinion why these images appear pixelated, and what suggestions might overcome the trouble?
    Best regards,
    Tim

    Zak,
    A second thought on pixellated images.  Currently I have overcome the problem by replacing all the affected images with a replacement image (the same original) but using a different file name.  These same images are used elsewhere in the site, but at different sizes.  Likely the file name was the same as the images that became pixellated.
    The odd thing is that other images that have not pixellated have the same treatment.  In several places (pages) the images are the same with the same file name but at a different size.
    I have not made this site active yet but these odd problems have made for lots of extra work to sort out.  You can see this site at:  www.fractalfotos.com/debV3/index.html
    Thanks, Tim

  • Small screen rendering bug

    There is a very subtle rendering bug when overlapping text.
    I'm not sure if this bug is worth fixing, as depending on how
    Mars rendering is implemented, it could be very difficult to fix.
    When overlapping to sections of text, the anti-aliased pixels
    will compound between overlapping lapping lines. This leads to a
    slightly "heavy" look at the point of overlap. This most affects
    double-layered / slightly-offset text used for shadowing, as the
    outlines of the two text areas match closely. It affects screen
    presentation and not print.
    The easiest way to demonstrate this bug is to copy and paste
    a text node multiple times into the SVG document. The rendered text
    will darken each time, until eventually, the text has a hard,
    jagged outline. The affect is easiest perceived with smaller font
    text because the ratio of anti-aliased pixels to 100% "solid"
    pixels is greater.
    The preferred behavior in this case would be to pick the
    darkest color point for that pixel from among all the overlapping
    anti-aliased pixels for each channel of color. The resulting
    anti-aliased pixel layer would then need to be blended as normal
    with any other overlapping layers... This could be tricky, but I
    think it would increase the overall quality of screen
    rendering.

    Unfortunately, this bug is pretty much beyond our control.
    Pixel-level rendering issues like this are handled entirely within
    the Acrobat core -- our plugin parses Mars SVG, converts it into
    Acrobat-friendly data structures, and then hands everything 'over
    the wall' for the Acrobat core to render.
    We have some control over the renderer's low-level settings,
    and I hope to exploit that in the next major release of the Mars
    plugin to take care of some other pixel-level rough-rendering bugs
    we've been seeing. However, this particular bug looks way too
    subtle for us to address with the level of renderer access we're
    given ...

Maybe you are looking for