Looks great in viewer & fully rendered.  Then = Crazy Export!  ***???

Ok, so I have this great video and I've fully rendered it and played it back in the viewer and everything is great.
I export it via compressor as a quicktime movie.
PROBLEM: In the QT edition some things aren't "working" - like there is a clip i had cropped which is no longer cropped and text is slightly moved. Is this random?? Did i do something wrong?? Help!!!

Check if you're export setting matches your sequence setting.
Then delete all the render of the sequence via the "render manager tool", because they might be some corrupted media.
Try to re-export after that.

Similar Messages

  • Images look great in viewer and terrible in canvas

    I made some map animations in Motion and Keynote. They plook perfect in the Viewer window but terrible in the Canvas window. I have a 480i DV/NTSC timeline. As far as I know, all my settings are correct.
    The problem is that colors look blocky in the canvas window. Is there any way to get the Canvas window to display images as cleanly as they are displayed in the Viewer window of FCP7?
    Is there anything I should do to these images in Photoshop to prep them for FCP?
    Thanks very much in advance,
    - Nick
    Message was edited by: Nicholas Natteau1

    The Viewer just shows whatever you have in its native state.
    Moving the clip or image to the Canvas forces it to display at the resolution and color space of the codec used in the Sequence setting.
    FCP works best with still images that were saved in the TIFF format. PNG will also give good results. You should always use images with a RGB color space.
    The problem is that colors look blocky in the canvas window.
    The images very likely need to be rendered, then they will look much better.
    Consider also that the Canvas always shows a low res proxy. This is less demanding on system resources for real time playback. To see what you really have requires connecting a calibrated, broadcast monitor or at the very least, an excellent TV.
    Is there anything I should do to these images in Photoshop to prep them for FCP?
    Unless you need to zoom and pan the images, open one of Photoshop's Film & Video presets that matches the pixel dimensions of your FCP timeline settings. Paste your images into the preset template and use the transform tools to scale them to the right size.

  • Titles look GREAT in FCP; lousy and pixellated upon Export

    I've read a couple of threads that seem to be related...I don't believe that type size is my issue...my smallest size is 16 pixels. the video is 720 x 480 ntsc.
    but my titles, set in Andale Mono, look perfectly crisp and well-rendered in FCP. I have rendered all clips and transitions.
    I'm stumped. Any thoughts?
    thank you!
    r

    The problem is not in your type (although 16 point is too small for TV).
    If you open one of you quicktime movies in Quicktime Player and go to menu Window>Show Movie Inspector, you will see that your 720X480 movie is not being displayed in 720X480, it is crunched into 655 X 480 or something like that.
    Hence the distorted image which is most easily seen in graphics.
    Why quicktime does this I don't know for sure but I think it has something to so with the square/round pixel thing.
    If you take one of you exported movies and import it back to FCP you will see the graphics look fine.
    To deliver the movie in quicktime (for what ever reason you have), and make it look good, you should go through Compressor.
    Hope this helps.

  • Edited video is exporting blurry as matched source, but looks great in the monitor before export?

    I've pulled in 5 videos and clippled them up to create a 50 second reel showing short segments of each. The video is for an HTML 5 embed on a website so it's at an odd size (235x162).
    Everything looks great when viewing the editable composition within Premiere (and I've tried this in After Effects as well), but when I go to export the video ends up blurry no matter if I match the source or fiddle with the settings.
    I'm guessing something is going on due to sourcing from multiple video files that are in different wrappers and codecs? If so, why would I be able to edit so cleanly (and render in program), but cannot export at the same quality??
    If it's the codec issue, what's the best format to convert all of these to if it's exporting to an HTML 5 video (if that last part even matters)?
    Does anyone have experience with the best settings for exporting .mp4 h.264 for web use? I want to get this thing small in file size, but still good quality.
    Here's a rundown of the imported videos I've been clipping up assuming its an issue with one of them (audio does not matter, we're not exporting it):
    MPEG4, AVC, Variable rate, Progressive
    Quicktime MPEG-4, AVC,  Progressive
    Quicktime MPEG-4, AVC, Progressive
    MPEG-4, AVC, Variable rate, Progressive
    Quicktime MPEG-4, Sorenson 3, Not progressive but I'm not seeing what it is
    Thank you!

    Hi Collin,
    Try 1 pass VBR instead of 2 pass VBR in the encoding settings.
    Hope that helps,
    Kevin

  • QuickTime Reference Movies of Fully-Rendered Timeline Taking Forever

    Sometimes when I attempt to export a fully-rendered timeline as a reference QuickTime (NOT self-contained), the "Writing Audio and Video" bar takes over an hour (for an 8-minute project) and results in files sizes of many GBs. Has anyone else experienced this?
    Thanks,
    Zap

    If your Sequence isn't fully rendered before you export, the reference movie will have to perform the render ... taking extra time and it includes those renders as part of the reference file (hence the larger than expected file size).
    To avoid this, make sure the Sequence is fully rendered PRIOR to exporting.
    -DH

  • FCP 7, viewer clear, but canvas and export blurry

    Started with screen recordings provided to me that made using quicktime 10
    took quicktime 10 screen recordings and converted them to prores422 HQ in compressor (settings from compressor below)
    imported into FCP 7.
    They look great in viewer, reasonably sharp and crisp, but them very blurry in canvas and when I export to quicktime movie (not using quicktime conversion). Been using FCP 7 a couple years but my knowledge in many aspects is sub professional.
    Tried creating a new sequence to get the sequence to match the settings of the quicktime prores422 screen capture movies but to no avail. The settings of the sequence are not the same as the screen capture movies...I even tried to change the sequence settings but no luck (then exited FCP without saving so as not to screw anything up).
    Im probably breaking basic rules here...any help is greatly appreciated.
    Thank you!!!
    Compressor settings for file conversion above:
    Name: Apple ProRes 422 for Interlaced material (High Quality)
    Description: Apple ProRes 422 10-bit video with audio pass-through. Settings based off the source resolution and frame-rate.
    File Extension: mov
    Estimated size: 412.09 MB
    Audio: multi-track passthrough
    Video Encoder
    Format: QT
    Width: (100% of source)
    Height: (100% of source)
    Selected: 1440 x 900
    Pixel aspect ratio: Square
    Crop: None
    Padding: None
    Frame rate: (100% of source)
    Selected: 15.002
    Frame Controls: Automatically selected: Off
    Codec Type: Apple ProRes 422 (HQ)
    Multi-pass: Off, frame reorder: Off
    Automatic gamma correction
    Progressive
    Pixel depth: 24
    Spatial quality: 50
    Min. Spatial quality: 0
    Temporal quality: 0
    Min. temporal quality: 0

    Here is additional information on the problem.
    My sequence includes mostly screen captures, but also some other video (settings below) and some JPEGs.  The other video and the JPEGs look fine...both in canvas and when I export sequence to quicktime.  The screen captures look terrible...text is very blurry.  Same screen captures look fine in my viewer, just goes awry when in canvas and export.
    Format of screen capture clips (quicktime 10 screen capture > compressor prores 422 HQ):
    1440x900, apprle prores 422 HQ, data rate 5.6 MB/S, pixel aspect square, field dominance none, composite normal.  Started with 4 files of the screen capture from compressor, then edited them into many little pieces in FCP...the size of those files post compressor are around 2GB each.
    The sequence (by default) had settings of:
    frame size: 720x480 NTSC DV 3:2
    pixel aspect ratio: NTSC - CCIR 601 / DV 720x480
    field dominance lower(even)
    quicktime compressor settings: apple prores 422 LT
    Vast majority of clips are the same as screen capture clips.  But just in case its part of the problem, I have also have a couple video clips of that have settings:
    frame size:  720x480
    compressor:  DV/DVCPRO - NTSC
    data rate 3.6mb/s
    pixel aspect: NTSC - CCIR 601
    field dominance: Lower/even
    also have a couple JPEGs, their settings are:
    frame size 2500x2084
    compressor: photo-jpeg
    field dominance: none
    Thank you!!!  I've been using final cut a while, but don't think I would have gotten anywhere without the help and generosity of people that are way beyond my knowledge and skills.  I am happy to provide any more info.  I really appreciate it.

  • When using Live View, site looks great, browser testing goes crazy

    I am creating a new website (and I am really unexperienced with Dreamwaver CS5).  But when I check my site using "Live View" everything looks great, the way it is supposed to.  Then when I go to test it in my browswer (Primary browser is Chrome) it goes crazy:  I at first noticed that I had saved one copy as an .asp but then resaved it to .xhtml  I did delete the first line of code already that the .asp file created as it kept giving me an error on line 1.
    Then I tried to do a spry drop-down menu bar, which I have deleted since I thought I was doing something wrong with that and I should just stick to what I half-way know.
    If I were to preview the template page it gives me this error:
    This page contains the following errors:
    error on line 150 at column 76: error parsing attribute name
    Below is a rendering of the page up to the first error.
    Here is line 150:
        if (a[i].indexOf("#")!=0){ d.MM_p[j]=new Image; d.MM_p[j++].src=a[i];}}
    If I were to test the index.xhtml page in the browser, it ignores most images (all but one), and the first nav-bar (an editable region) appears to the left instead of under the header.  The layout is totally ignored and everything is on the left-hand side of the screen instead of in a two column layout.
    I am not testing this on a server just off of my computer.
    I am assuming that the error has something to do with the .asp file I first did and when I resaved it, since I don't know what I would be looking for, is still in there screwing it up.
    Here is the code from the template page:
    <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
    <html xmlns="http://www.w3.org/1999/xhtml">
    <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
    <!-- TemplateBeginEditable name="doctitle" -->
    <title>Midwest Window Brokers | Page</title>
    <!-- TemplateEndEditable -->
    <!-- TemplateBeginEditable name="head" -->
    <!-- TemplateEndEditable -->
    <style type="text/css">
    <!--
    body {
              font: 100%/1.4 Verdana, Arial, Helvetica, sans-serif;
              margin: 0;
              padding: 0;
              color: #000;
              background-image: url(/images/bkg.jpg);
              background-repeat: repeat;
    /* ~~ Element/tag selectors ~~ */
    ul, ol, dl { /* Due to variations between browsers, it's best practices to zero padding and margin on lists. For consistency, you can either specify the amounts you want here, or on the list items (LI, DT, DD) they contain. Remember that what you do here will cascade to the .nav list unless you write a more specific selector. */
              padding: 0;
              margin: 0;
    h1, h2, h3, h4, h5, h6, p {
              margin-top: 0;           /* removing the top margin gets around an issue where margins can escape from their containing div. The remaining bottom margin will hold it away from any elements that follow. */
              padding-right: 15px;
              padding-left: 15px; /* adding the padding to the sides of the elements within the divs, instead of the divs themselves, gets rid of any box model math. A nested div with side padding can also be used as an alternate method. */
              text-align: left;
    a img { /* this selector removes the default blue border displayed in some browsers around an image when it is surrounded by a link */
              border: none;
    /* ~~ Styling for your site's links must remain in this order - including the group of selectors that create the hover effect. ~~ */
    a:link {
              color: #060;
              text-decoration: none; /* unless you style your links to look extremely unique, it's best to provide underlines for quick visual identification */
    a:visited {
              color: #666;
              text-decoration: underline;
    a:hover, a:active, a:focus { /* this group of selectors will give a keyboard navigator the same hover experience as the person using a mouse. */
              text-decoration: none;
    /* ~~this fixed width container surrounds the other divs~~ */
    .container {
              width: 960px;
              background: #FFF;
              margin: 0 auto; /* the auto value on the sides, coupled with the width, centers the layout */
    /* ~~ the header is not given a width. It will extend the full width of your layout. It contains an image placeholder that should be replaced with your own linked logo ~~ */
    .header {
              background-color: #FFF;
    /* ~~ These are the columns for the layout. ~~
    1) Padding is only placed on the top and/or bottom of the divs. The elements within these divs have padding on their sides. This saves you from any "box model math". Keep in mind, if you add any side padding or border to the div itself, it will be added to the width you define to create the *total* width. You may also choose to remove the padding on the element in the div and place a second div within it with no width and the padding necessary for your design.
    2) No margin has been given to the columns since they are all floated. If you must add margin, avoid placing it on the side you're floating toward (for example: a right margin on a div set to float right). Many times, padding can be used instead. For divs where this rule must be broken, you should add a "display:inline" declaration to the div's rule to tame a bug where some versions of Internet Explorer double the margin.
    3) Since classes can be used multiple times in a document (and an element can also have multiple classes applied), the columns have been assigned class names instead of IDs. For example, two sidebar divs could be stacked if necessary. These can very easily be changed to IDs if that's your preference, as long as you'll only be using them once per document.
    4) If you prefer your nav on the left instead of the right, simply float these columns the opposite direction (all left instead of all right) and they'll render in reverse order. There's no need to move the divs around in the HTML source.
    .sidebar1 {
              float: right;
              width: 300px;
              background: #ffffff;
              padding-bottom: 10px;
    .content {
              padding: 10px 0;
              width: 650px;
              float: right;
    /* ~~ This grouped selector gives the lists in the .content area space ~~ */
    .content ul, .content ol {
              padding: 0 15px 15px 40px; /* this padding mirrors the right padding in the headings and paragraph rule above. Padding was placed on the bottom for space between other elements on the lists and on the left to create the indention. These may be adjusted as you wish. */
    /* ~~ The navigation list styles (can be removed if you choose to use a premade flyout menu like Spry) ~~ */
    ul.nav {
              list-style: none; /* this creates the space between the navigation on the content below */
    ul.nav li {
              border-bottom: 1px solid #666; /* this creates the button separation */
    ul.nav a, ul.nav a:visited { /* grouping these selectors makes sure that your links retain their button look even after being visited */
              padding: 5px 5px 5px 15px;
              display: block; /* this gives the link block properties causing it to fill the whole LI containing it. This causes the entire area to react to a mouse click. */
              width: 160px;  /*this width makes the entire button clickable for IE6. If you don't need to support IE6, it can be removed. Calculate the proper width by subtracting the padding on this link from the width of your sidebar container. */
              text-decoration: none;
              background-color: #DDDECB;
    ul.nav a:hover, ul.nav a:active, ul.nav a:focus { /* this changes the background and text color for both mouse and keyboard navigators */
              background: #ADB96E;
              color: #FFF;
    /* ~~ The footer ~~ */
    .footer {
              padding: 10px 0;
              position: relative;/* this gives IE6 hasLayout to properly clear */
              clear: both; /* this clear property forces the .container to understand where the columns end and contain them */
              background-color: #DDDECB;
              font-size: small;
    /* ~~ miscellaneous float/clear classes ~~ */
    .fltrt {  /* this class can be used to float an element right in your page. The floated element must precede the element it should be next to on the page. */
              float: right;
              margin-left: 8px;
    .fltlft { /* this class can be used to float an element left in your page. The floated element must precede the element it should be next to on the page. */
              float: left;
              margin-right: 8px;
    .clearfloat { /* this class can be placed on a <br /> or empty div as the final element following the last floated div (within the #container) if the #footer is removed or taken out of the #container */
              clear:both;
              height:0;
              font-size: 1px;
              line-height: 0px;
    #h-navbar {
              font-weight: bold;
              height: auto;
              font-size: 18px;
              line-height: 50px;
              background-image: url(/images/navbar2.jpg);
    #h-navbar1 {
              background-image: none;
              background-repeat: repeat-x;
    -->
    </style>
    <script type="text/javascript">
    function MM_preloadImages() { //v3.0
      var d=document; if(d.images){ if(!d.MM_p) d.MM_p=new Array();
        var i,j=d.MM_p.length,a=MM_preloadImages.arguments; for(i=0; i<a.length; i++)
        if (a[i].indexOf("#")!=0){ d.MM_p[j]=new Image; d.MM_p[j++].src=a[i];}}
    function MM_swapImgRestore() { //v3.0
      var i,x,a=document.MM_sr; for(i=0;a&&i<a.length&&(x=a[i])&&x.oSrc;i++) x.src=x.oSrc;
    function MM_findObj(n, d) { //v4.01
      var p,i,x;  if(!d) d=document; if((p=n.indexOf("?"))>0&&parent.frames.length) {
        d=parent.frames[n.substring(p+1)].document; n=n.substring(0,p);}
      if(!(x=d[n])&&d.all) x=d.all[n]; for (i=0;!x&&i<d.forms.length;i++) x=d.forms[i][n];
      for(i=0;!x&&d.layers&&i<d.layers.length;i++) x=MM_findObj(n,d.layers[i].document);
      if(!x && d.getElementById) x=d.getElementById(n); return x;
    function MM_swapImage() { //v3.0
      var i,j=0,x,a=MM_swapImage.arguments; document.MM_sr=new Array; for(i=0;i<(a.length-2);i+=3)
       if ((x=MM_findObj(a[i]))!=null){document.MM_sr[j++]=x; if(!x.oSrc) x.oSrc=x.src; x.src=a[i+2];}
    </script>
    </head>
    <body onload="MM_preloadImages('/images/home2.jpg')">
    <div class="container">
      <div class="header"><a href="/index.xhtml"><img src="../images/heading.jpg" alt="Midwest Window Brokers, Windows, Siding, Roofing, 605-791-5352" name="Insert_logo" width="950" height="200" align="right" id="Insert_logo" style="background: #FFFFFF; display:block;" /></a>
        <div id="h-navbar1"><a href="/index.xhtml"><img src="/images/home.jpg" alt="home" width="159" height="51" id="Image1" onmouseover="MM_swapImage('Image1','','/images/home2.jpg',1)" onmouseout="MM_swapImgRestore()" /></a><a href="/windows.html"><img src="/images/services.jpg" width="151" height="51" alt="services" /></a><a href="/freebay.xhtml"><img src="/images/specials.jpg" width="153" height="51" alt="specials" /></a><a href="/gallery.html"><img src="/images/gallery.jpg" width="152" height="51" alt="gallery" /></a><a href="/roofing.xhtml"><img src="/images/order.jpg" width="152" height="51" alt="order" /></a><img src="/images/blank.jpg" width="75" height="51" /><img src="/images/facebook.jpg" width="38" height="51" alt="facebook" longdesc="http://facebook.com/midwestwindowbrokers" /><img src="/images/twitter.jpg" width="37" height="51" alt="twitter" longdesc="http://twitter.com/midwestwindow" /><img src="/images/google.jpg" width="42" height="51" alt="google+" longdesc="http://https://plus.google.com/u/0/b/108071947231835835141/108071947231835835141/posts" /></div>
      <!-- end .header --></div>
      <!-- TemplateBeginEditable name="navbar" -->
      <div id="h-navbar">
        <div id="h-navbar2">  Content for  id "h-navbar2" Goes Here</div>
      </div>
      <!-- TemplateEndEditable -->
      <div class="sidebar1">
        <ul class="nav">
        </ul>
        <p> <div id="wufoo-z7x3k1">
    Fill out my <a href="http://midwestwindow.wufoo.com/forms/z7x3k1">online form</a>.
    </div>
    <script type="text/javascript">var z7x3k1;(function(d, t) {
    var s = d.createElement(t), options = {
    'userName':'midwestwindow',
    'formHash':'z7x3k1',
    'autoResize':true,
    'height':'601',
    'async':true,
    'header':'show'};
    s.src = ('https:' == d.location.protocol ? 'https://' : 'http://') + 'wufoo.com/scripts/embed/form.js';
    s.onload = s.onreadystatechange = function() {
    var rs = this.readyState; if (rs) if (rs != 'complete') if (rs != 'loaded') return;
    try { z7x3k1 = new WufooForm();z7x3k1.initialize(options);z7x3k1.display(); } catch (e) {}};
    var scr = d.getElementsByTagName(t)[0], par = scr.parentNode; par.insertBefore(s, scr);
    })(document, 'script');</script></p>
        <!-- end .sidebar1 --></div>
      <!-- TemplateBeginEditable name="Body" -->
      <div class="content">
        <h1>Instructions</h1>
        <p>Be aware that the CSS for these layouts is heavily commented. If you do most of your work in Design view, have a peek at the code to get tips on working with the CSS for the fixed layouts. You can remove these comments before you launch your site. To learn more about the techniques used in these CSS Layouts, read this article at Adobe's Developer Center - <a href="http://www.adobe.com/go/adc_css_layouts">http://www.adobe.com/go/adc_css_layouts</a>.</p>
        <h2>Clearing Method</h2>
        <p>Because all the columns are floated, this layout uses a clear:both declaration in the .footer rule.  This clearing technique forces the .container to understand where the columns end in order to show any borders or background colors you place on the .container. If your design requires you to remove the .footer from the .container, you'll need to use a different clearing method. The most reliable will be to add a &lt;br class=&quot;clearfloat&quot; /&gt; or &lt;div  class=&quot;clearfloat&quot;&gt;&lt;/div&gt; after your final floated column (but before the .container closes). This will have the same clearing effect.</p>
        <h3>Logo Replacement</h3>
        <p>An image placeholder was used in this layout in the .header where you'll likely want to place  a logo. It is recommended that you remove the placeholder and replace it with your own linked logo. </p>
        <p><span style="font-size: 18px; color: #C00; font-weight: bold; font-style: italic;">Logo Replacement</span></p>
        <p> Be aware that if you use the Property inspector to navigate to your logo image using the SRC field (instead of removing and replacing the placeholder), you should remove the inline background and display properties. These inline styles are only used to make the logo placeholder show up in browsers for demonstration purposes. </p>
        <p>To remove the inline styles, make sure your CSS Styles panel is set to Current. Select the image, and in the Properties pane of the CSS Styles panel, right click and delete the display and background properties. (Of course, you can always go directly into the code and delete the inline styles from the image or placeholder there.)</p>
        <h4>Backgrounds</h4>
        <p>By nature, the background color on any div will only show for the length of the content. This means if you're using a background color or border to create the look of a side column, it won't extend all the way to the footer but will stop when the content ends. If the .content div will always contain more content, you can place a border on the .content div to divide it from the column.</p>
        <!-- end .content -->
      </div>
      <!-- TemplateEndEditable -->
      <div class="footer">
        <p class="footer"><strong>  <em>References Available!</em>     We accept cash, check, Visa, Discover, MasterCard</strong></p>
          Copyright 2012 Midwest Window Brokers Inc. All Rights Reserved.
        <!-- end .footer --></div>
      <!-- end .container --></div>
    </body>
    </html>

    I had saved one copy as an .asp but then resaved it to .xhtml 
    I'm assuming this is a static web site.  Rename (F2) all your pages with .html or .htm extension. 
    .xhtml is not a valid extension.
    Nancy O.

  • What are the best instagram video settings using Compressor 4?  The outputs I have created look clean HD in camera roll.  When I view video in instagram preview it looks great, but then when i post it the quality gets blurry. Any advice?

    I have read that you should resize the frame to 640 by 640 or 1000 x 1000, and have tried both.  I shot the footage on canon 70d using 720p60fps, and edited the footage with iMovie.  Its been frustrating to see the finished product look great on iPhone, iPad, or mac but once i post the video- the quality gets blurry when you focus on the faces that are in focus.  My footage is basketball action shots from a high school game.  Any advice would be huge, I been looking for an answer to this for a month. 

    Simple export a ProRes 422 file, upload that by itself.  Facebook, Vimeo, YoutTube, etc, all compress the video themselves.  So don't compress it first, just upload it and let them do their own compression.

  • Why does my page look great in design view and to the left in live view?

    I just created a new page using a fluid grid layout and in "design" view it looks great but in "live" view or on a browser preview the wording all goes to the left.  What I am doing wrong?  I also have another question which may relate to the first.  I  have four templates. Do I create a new named .css file for each new template or continue using the same layout.css file for all templates? Since I created a new .css file for every template maybe it is causing confusion.  Thanks in advance.

    If this is what you want, rework your HTML so all three images are in the same div and adjust your css to  narrow the scroll down image and on Order jpg, vertically align top, 30px margin.
    <div id="header">
    <div id="pic1">
    <img src="Thumbs/Scroll-Down.jpg" alt="More Pictures">
    <img class="goldborder" src="NewImages/englilshivymain.jpg" alt="">
    <a href="#OrderHere2">
    <img alt="Order Here" src="Thumbs/OrderHere.jpg">
    </a>
    <br>
    English Ivy (Detail)
    </div>
    <div id="pic4">

  • Design View is Terrible but the Webpage Looks Great

    My HTML webpages look great on my web server. However, when I
    open a webpage in Dreamweaver the Design View looks nothing like
    the page posted to my website. This is really frustrating since it
    makes edits more difficult to perform. I'm using Contribute to edit
    webpage since they uploaded to Contribte and display correctly.
    Can anyone out there assist me in fixing the Design View in
    Dreamweaver?

    Clancy:
    You layout plan is pretty strange. I guess I would never do a
    layout that
    way, honestly. It will take me some time to study what you
    have done....
    Anyhow, what happens if you add "margin:0 auto;" to pfm2?
    Murray --- ICQ 71997575
    Adobe Community Expert
    (If you *MUST* email me, don't LAUGH when you do so!)
    ==================
    http://www.dreamweavermx-templates.com
    - Template Triage!
    http://www.projectseven.com/go
    - DW FAQs, Tutorials & Resources
    http://www.dwfaq.com - DW FAQs,
    Tutorials & Resources
    http://www.macromedia.com/support/search/
    - Macromedia (MM) Technotes
    ==================
    "Clancy" <[email protected]> wrote in message
    news:[email protected]...
    > "Murray *ACE*" <[email protected]>
    wrote:
    >
    >>> 2. Dreamweaver (8) design view is quite buggy.
    If you nest tables about
    >>> three
    >>> deep, or use CSS to define table styles (among
    others), the display is
    >>> likely to
    >>> be way off.
    >>
    >>Baloney. Show me an example of this, please.
    >
    > One case where IE6 does what I expect it to do (though
    perhaps not what
    > CSS says
    > it should do), and Dreamweaver doesn't, is shown at:
    >
    >
    http://www.corybas.com/Cydalba/Test/Test_page_a.php
    >
    > The two tables class pfm and class pfm2 are both
    formatted in CSS, but
    > aligned
    > centre in HTML. In IE6 (at least) they are centred on
    the screen, whereas
    > Dreamweaver shows them both aligned left.
    >
    > A case of a complex table which frequently throws
    Dreamweaver into
    > hysterics is
    > shown at:
    >
    >
    http://www.cybec.com.au/Trinity.htm
    >
    > You will probably say (with considerable justification)
    that this page is
    > too
    > complex, but quite often when I'm editing it, design
    view goes sproing,
    > and
    > expands the display to several screen widths. The first
    few times this
    > happened
    > I assumed I had done something stupid, and spent a
    considerable amount of
    > time
    > backtracking, but now I am fairly certain that it is
    just another of
    > Dreamweaver's annoying bugs and just ignore it. The next
    time I reload
    > the page
    > it usually displays correctly.
    >
    > The trouble with this sort of thing is that it destroys
    your confidence
    > both in
    > Dreamweaver and in your own site, as you think that what
    you are doing is
    > correct but you can never be entirely certain.
    >
    > There are several other bugs in Dreamweaver relating to
    mixed HTML and
    > php. I
    > have some screenshots displaying these, and I will post
    these later.
    >
    > Clancy

  • Hi there. I shot with a nikon d7000. The clips look great on the viewer but quite bad on canvas (also after its been exported) I converted my clips to apple pro res 422 using mpeg streamclip. The size I used was 1920 x 1080. How can I fix these?

    Hi there. I shot with a nikon d7000. The clips look great on the viewer but quite bad on canvas (also after its been exported) I converted my clips to apple pro res 422 using mpeg streamclip. The size I used was 1920 x 1080. How can I fix this?

    This is the clip:
    This is the sequence:
    I know they both should match. Question is, should I re convert the clips in mpeg using different size settings? Or should I change the sequence settings? how?
    Thanks A LOT.

  • I have created several templates and they look great in live view, however they look like crap when actually tried to set up a webpage based on the template. Help!

    I have created sevedral templates and they look great in the live view, however they look like plain HTML text when I try to create a webpage based on the template. HELP!

    This forum is about the Cloud as a delivery process, not about using individual programs
    If you start at the Forums Index https://forums.adobe.com/welcome
    You will be able to select a forum for the specific Adobe product(s) you use
    Click the "down arrow" symbol on the right (where it says All communities) to open the drop down list and scroll

  • SonyAVCHD video looks great in iMovie11 or iDVD7.1.2. When I burn a DVD it's terrible. If I freeze frame I see squares. The picture has poor contrast. I've viewed DVD on my 6-year-old, 24 in. intel 2.16 GHz iMac, and on TV. Help!

    I just bought a very good quality Sony AVCHD camcorder. I also just upgraded my computer from Tiger to Snow Leapord. My iMac is a 6-year-old, 2.16GHz Intel 2 Duo, with a 24 inch screen and 3GB Ram.
    My Sony camcorder HD video looks great in iMovie11 and in iDVD7.1.2., but when I burn a DVD "professional" it looks terrible. If I look at a freeze frame on the DVD I see image made-up of squares. The picture has poor contrast. It looks as bad as poor quality VHS. Do I need to get a new iMac to make this work? Is it possible to make a sharp, clear DVD from AVCHD footage with a 6-year-old iMac like mine?

    That thread helped for a time.  But now it seems as though my computer is back to slow again.  But, some of the jargon is over my head as well.  Not sure I knew quoite everything they were talking about.  But thanks a lot for that, it helped I probably just need to reread it and follow the instructions again.  Thanks so much.

  • Why do images within a PDF look jagged when viewed in Acrobat Pro 10.1.6?

    Using a MacBook Pro running Mac OS version 10.7.5 with NVIDIA GeForce GT 650M 1024 MB graphics card. High-resolution source images look fine in other software, and embedded images in a PDF look fine when viewed on Google Drive, but curves and diagonal lines look jagged when viewed in Acrobat Pro 10.1.6. Checking smoothing options in Preferences only adjusts the position of the jagged edges; it neither enhances nor ameliorates them.
    I created a sample PDF to illustrate the problem I'm having. Created in illustrator, exported to PNG and converted to PDF. Here is a screenshot of the source PNG side-by-side with the PDF I created from it:
    Please note that when I preview the PDF in Finder, and when I view the PDF in Chrome using Google Drive, the image looks fine. Here's a link to the sample PDF:
    http://www.sendspace.com/file/77f5m6
    Any assistance is appreciated. Thanks!

    Unfortunately, as I mentioned in my original post, I've already tried toggling smoothing options. They don't make the jagged edges go away—they just change them slightly. In some cases, as with the sample file provided, it does help smooth the art out, but it never looks as good as it did going in, in a recent project, toggling smoothing options didn't affect the appearance of the image at all. Zoom does not appear to relieve the artifacting.
    A little clarification: this PDF was created from a flat PNG, but I have had this issue with PNGs and TIFFs as well, generated by both Photoshop and Illustrator. To reiterate, the PDFs display fine in other software—Finder preview looks great, and the same file viewed in my browser via Google Drive looks as intended as well. A colleague was able to replicate this issue in Acrobat on his Windows machine. This appears to be a rendering issue specific to Acrobat with regards to the files I use it to create.

  • CS6 Design view not rendering styles, tried typical fixes already

    I'm using Dreamweaver CS6 on Windows 7. I hand code everything but like to look in design view from time to time. Everything was working fine until a couple days ago it stopped rendering my css styles and now looks like this (see first image), but an actual preview in the browser looks fine. Under the style rendering menu screen media and display styles ARE currently checked. I have tried turning them off and then back on. I have tried deleting preferences from the registry. My files are linked to a template, I have tried removing the linked style sheet and then adding it again. Oddly I do see css styles in the preview of the actual template file but not the linked files. Any suggestions on what else I can try?

    Most likely code related.  Assuming your Template.dwt is correctly located inside the Templates folder in your site's root, and your site is properly defined, and the style sheet file is in another folder called Styles,  the expected path in your Template.dwt file would be this with leading dots and slash.
    Template.dwt
    <link rel="stylesheet" type="text/css" href="../Styles/stylesheet.css">
    And the child page spawned from that Template and saved to your site root would contain this link path with no leading dots or slash.
    childpage.html
    <link rel="stylesheet" type="text/css" href="Styles/stylesheet.css">
    It goes without saying that DW doesn't adjust link paths for you unless a) your site is properly defined and b) you've saved your child page and named it.
    Hope this helps,
    Nancy O.

Maybe you are looking for

  • Voice Memos ceased working after iOS 6.0.2 upgrade

    Voice Memos launches then crashes in one second on my iPhone 5, ios 6.0.2.  This began after the latest ios upgrade for iPhone 5. I have done a hard reset; a restore iPhone and the standard Voice Memos does not function anymore. Does anyone have a so

  • Itunes 7 BIG PROB HELP NEEDED

    The first time i downloaded 7.0 i got all the way to the end and it worked but i could never open it so i just deleted itunes completley and so now i download it and it says..."this is already a file do you want to replace it?" I hit yes...than this

  • I have a problem, am i going to lose all my files ?

    Hello, I have a lot of pictures on my Ipod. But since i'm coming back from holidays, my ipod doesn't work anymore ! I still can use it and listen to music, but when i plug it, windows ask me to format it, and itunes doesn't recognize it... I wanted t

  • My tv says no signal when my apple tv is plugged in.

    I tried a different HD cord and plugging it into a different HD port still the same thing whats wrong with it? my blue ray player works fine with ether cord and ether HD port? can you help me please.

  • Finding iphone 5c without icloud or app installed

    Hi Im hoping someone amazing can tell me how I can find my iPhone 5c I lost it on Friday night at some stage (in my own house nonetheless) but I can't find it anywhere and wondering if maybe someone accidentally took it home with them, since we were