Corrupted video and rendering problems

Before I upgraded the software (FCP 5.0.3 to 5.0.4, and the latest OS X update) I could capture and export movies with no problems. Using the “File>Export>Quicktime Movie” option set to “Use current settings” provides the disastrous results of digital garbage flashing on the screen like psychedelic Lego blocks every couple of seconds at random intervals. They appear at different points with every export. It’s like it’s taking an I-frame from a Jackson Pollack painting. I tried using the following codecs (Sorry if I’m using the wrong terminology, I’m a PC head making my first steps into the Mac universe): Apple Intermediate Codec, DV NTSC 48 KHz (the project’s setting), DV50 NTSC 48 KHz, MPEG IMX 8-bit NTSC – 50 MB/s – 48KHz and the Uncompressed 8-bit NTSC 48 KHz all with similar hideous results. So why does the video look so bad?
Also when I try to render my files the progress bar flashes on the screen for about a second and then goes away, leaving my timeline with the same red bar across the top (AKA unrendered). Are these two problems related?
I hope that is a detailed enough description of my plight to inspire an answer. Thanks in advance.

Yes, I have tried it in a new sequence and a new project but nothing has changed. What I am trying to do is take our catalog of "How to" videos from the miniDV tapes and create DVDs using DVDSP4 since nobody buys VHS anymore. All I'm doing is capturing the 25+ minute project and trimming off the wasted spaces at the beginning and the end. Two cuts, that's it. I'm not reassembing anything and this is becoming a bigger project than the original editing. I had captured the original video I am currently working with before the OS upgrade with no problems and it looks fine on anything I use to view the Quicktime file with. But when I export to anything besides Compressor all I get is junk when Compressor decides not to give ma a "Quicktime Error: 0". What is that about? Anyone?
Also, the tutorial on preview rendering is good and I learned quite a bit. Unfortunately nothing worked on solving my problem. The progress bar still flashes on the screen and when it hits 0% completed it disappears leaving everything unrendered. Grrrr.
Thanks again.

Similar Messages

  • Pixelated video and upscaling problems with ringing artifacts on Youtube since Flash player 10.3

    Pixelated video and upscaling problems with ringing artifacts on Youtube since Flash player 10.3. Flash palyer 10.2 was the last version without the listed problems.
    For anyone interested you may see here what 'ringing artifacts' means : http://en.wikipedia.org/wiki/Ringing_artifact
    More about Image artifacts/errors related to video scaling here :  http://en.wikipedia.org/wiki/Video_scaler
    Test configuration :
    Windows 7 x64
    Intel HD Graphics with lastest available drivers from manufacturer.
    Any solution from Adobe?

    Could you please open a new bug report on this over at bugbase.adobe.com?  Please post back with the URL so that others affected can add their comments and votes.
    Thanks,
    Chris

  • Spry Menu Bar 2.0 (1.0) - Handling of widget generated CSS, placement and rendering problems in CSS

    Hello:
    I wanted to repost my question to re-frame the issue based on what I have learned thus far.
    I am working on a website that has been developed using the Spry Menu Bar Framework UI (2.0) I.0, that has some peculiar rendering problems that affect IE 6 in particular.  The CSS is reprinted below.
    In particular, when I post the widget generated CSS in the head as it is orginally situated by the framework, the menu bar works fine.  However, it seemed to me that I should be able to reduce page weight (an important consideration considering my target population) by placing it in the general style sheet governing the entire site.
    When I place the styles at the beginning of the style sheet the menu doesn't render at all in any of the browsers (IE 6+, Firefox, Opera, Safari, Netscape, etc.) as it conflicts with the general rules governing links that appear later in the style sheet.  When I place the styles specific to the Menu bar at the end of the style sheet, then the menu bar renders properly in all browsers except IE 6.
    The odd thing is that the only way to ensure that the menu bar works in IE 6 is to keep the menu related styles in the head of each page.  This raises problems related to page weight (not an insurmountable consideration if no other solution can be found) but still an issue.  Likewise I need to support IE 6, again given the target audience/population.  The issue obviously has something to do with specificity, but I am not certain that is the only consideration at work here.  I have not tried the !important selector in regard to the menu, as IE 6 seems to only partially support this.
    Thanks in advance for any advice or insight that can be provided.  Thanks in particular to Martin for his contributions to my earlier question related to this issue.
    Steve Webster.
    The CSS governing the horizontal menu bar is as follows:  (currently the following CSS is embedded in the head of the web page)
    <style type="text/css">
    /*  -- Begins Spry Menu Widget 2.0 (1.0) Horizontal menu bar Custom styles --  */
    /* BeginOAWidget_Instance_2141544: #MenuBar */
    /* Settable values for skinning a Basic menu via presets. If presets are not sufficient, most skinning should be done in
       these rules, with the exception of the images used for down or rightpointing arrows, which are in the file SpryMenuBasic.css
         These assume the following widget classes for menu layout (set in a preset)
       .MenuBar - Applies to all menubars - default is horizontal bar, allsubmenus are vertical - 2nd level subs and beyond are pull-right.
        .MenuBarVertical - vertical main bar; all submenus are pull-right.
       You can also pass in extra classnames to set your desired top levelmenu bar layout. Normally, these are set by using a preset.
        They only apply to horizontal menu bars:
            MenuBarLeftShrink - The menu bar will be horizontally 'shrinkwrapped' to be just large enough to hold its items, and left aligned
            MenuBarRightShrink - Just like MenuBarLeftShrink, but right aligned
            MenuBarFixedLeft - Fixed at a specified width set in the rule '.MenuBarFixedLeft', and left aligned. 
            MenuBarFixedCentered -  - Fixed at a specified width set in the rule '.MenuBarFixedCentered',
                            and centered in its parent container.
            MenuBarFullwidth - Grows to fill its parent container width.
        In general, all rules specified in this file are prefixed by #MenuBar so they only apply to instances of the widget inserted along
       with the rules. This permits use of multiple MenuBarBasic widgets onthe same page with different layouts. Because of IE6 limitations,
        there are a few rules where this was not possible. Those rules are so noted in comments.
    #MenuBar  {
        background-color:transparent;
       font-family: Arial, Helvetica, sans-serif; /* Specify fonts on onMenuBar and subMenu MenuItemContainer, so MenuItemContainer,
                                                    MenuItem, and MenuItemLabel
                                                    at a given level all use same definition for ems.
                                                    Note that this means the size is also inherited to child submenus,
                                                    so use caution in using relative sizes other than
                                                    100% on submenu fonts. */
        font-weight: normal;
        font-size: 17px;
        font-style: normal;
        padding:0;
    /* Caution: because ID+class selectors do not work properly in IE6, but we want to restrict these rules to just this
    widget instance, we have used string-concatenated classnames for our selectors for the layout type of the menubar
    in this section. These have very low specificity, so be careful not to accidentally override them. */
    .MenuBar br { /* using just a class so it has same specificity as the ".MenuBarFixedCentered br" rule bleow */
        display:none;
    .MenuBarLeftShrink {
        float: left; /* shrink to content, as well as float the MenuBar */
        width: auto;
    .MenuBarRightShrink {
        float: right; /* shrink to content, as well as float the MenuBar */
        width: auto;
    .MenuBarFixedLeft {
        float: left;
        width: 80em;
    .MenuBarFixedCentered {
        float: none;
        width: 80em;
        margin-left:auto;
        margin-right:auto;
    .MenuBarFixedCentered br {
        clear:both;
        display:block;
    .MenuBarFixedCentered .SubMenu br {
        display:none;
    .MenuBarFullwidth {
        float: left;
        width: 100%;
    /* Top level menubar items - these actually apply to all items, and get overridden for 1st or successive level submenus */
    #MenuBar  .MenuItemContainer {
        padding: 0px 0px 0px 0px;
        margin: 0;     /* Zero out margin  on the item containers. The MenuItem is the active hover area.
                    For most items, we have to do top or bottom padding or borders only on the MenuItem
                    or a child so we keep the entire submenu tiled with items.
                    Setting this to 0 avoids "dead spots" for hovering. */
    #MenuBar  .MenuItem {
        padding: 10px 10px 10px 4px;
        background-color:#000088;
        background-image:url(../ACLCO%20Graphics%20-%20Web%20site%20Parts/Nav igation%20Bar%20Segment-Dark.png);
        background-repeat:repeat-x;       
    #MenuBar  .MenuItemFirst {
        border-style: none none none none;
    #MenuBar .MenuItemLast {
        border-style: none none none none;
    #MenuBar  .MenuItem  .MenuItemLabel{
        text-align:center;
        line-height:1.4em;
        color:#ffffff;
        background-color:transparent;
        padding: 0px 18px 0px 5px;
        width: 10em;
        width:auto;
    .SpryIsIE6 #MenuBar  .MenuItem  .MenuItemLabel{
        width:1em; /* Equivalent to min-width in modern browsers */
    /* First level submenu items */
    #MenuBar .SubMenu  .MenuItem {
        font-family: Arial, Helvetica, sans-serif;
        font-weight: bold;
        font-size: 15px;
        font-style: normal;
        background-color:#000088;
        padding:0px 2px 0px 0px;
        border-width:0px;
        border-color: #cccccc #cccccc #cccccc #cccccc;
        /* Border styles are overriden by first and last items */
        border-style: solid solid none solid;
    #MenuBar  .SubMenu .MenuItemFirst {
        border-style: none;
        padding: 0px;
    #MenuBar  .SubMenu .MenuItemFirst .MenuItemLabel{
        padding-top: 0px;
    #MenuBar .SubMenu .MenuItemLast {
        border-style: none none none none;
    #MenuBar .SubMenu .MenuItemLast .MenuItemLabel{
        padding-bottom: 10px;
    #MenuBar .SubMenu .MenuItem .MenuItemLabel{
        text-align:left;
        line-height:1em;   
        background-color:transparent;
        color:#ffffff;
        padding: 10px 10px 10px 10px;
        width: 240px;
    /* Hover states for containers, items and labels */
    #MenuBar .MenuItemHover {
        background-color: #2E35A3;
        background-image:url(../ACLCO%20Graphics%20-%20Web%20site%20Parts/Nav igation%20Bar%20Segment%20Light2.png);
        background-repeat:repeat-x;
    #MenuBar .MenuItemWithSubMenu.MenuItemHover .MenuItemLabel{
        background-color: transparent; /* consider exposing this prop separately*/
        color: #ffffff;
    #MenuBar .MenuItemHover .MenuItemLabel{
        background-color: transparent;
        color: #ffffff;
    #MenuBar .SubMenu .MenuItemHover {
        background-color:#2E35A3;
    #MenuBar .SubMenu .MenuItemHover .MenuItemLabel{
        background-color: transparent;
        color: #ffffff;
    /* Submenu properties -- First level of submenus */
    #MenuBar .SubMenuVisible {
        background-color: transparent;
       min-width:0%;  /* This keeps the menu from being skinnier than theparent MenuItemContainer - nice to have but not available on ie6 */
        border-style: none none none none;
    #MenuBar.MenuBar .SubMenuVisible {/* For Horizontal menubar only */
        top: 100%;    /* 100% is at the bottom of parent menuItemContainer */
        left:0px; /* 'left' may need tuning depending upon borders or padding applied to menubar MenuItemContainer or MenuItem,
                        and your personal taste.
                       0px will left align the dropdown with the content area of theMenuItemContainer. Assuming you keep the margins 0
                        on MenuItemContainer and MenuItem on the parent
                        menubar, making this equal the sum of the MenuItemContainer & MenuItem padding-left will align
                        the dropdown with the left of the menu item label.*/
        z-index:10;
    #MenuBar.MenuBarVertical .SubMenuVisible {
        top: 0px;   
        left:100%;
        min-width:0px; /* Do not neeed to match width to parent MenuItemContainer - items will prevent total collapse */
    /* Submenu properties -- Second level submenu and beyond - these are visible descendents of .MenuLevel1 */
    #MenuBar .MenuLevel1 .SubMenuVisible {
        background-color: transparent;
        min-width:0px; /* Do not neeed to match width to parent MenuItemContainer - items will prevent total collapse*/
        top: 0px;    /* If desired, you can move this down a smidge to separate top item''s submenu from menubar -
                    that is really only needed for submenu on first item of MenuLevel1, or you can make it negative to make submenu more
                    vertically 'centered' on its invoking item */
        left:100%; /* If you want to shift the submenu left to partially cover its invoking item, you can add a margin-left with a
                    negative value to this rule. Alternatively, if you use fixed-width items, you can change this left value
                    to use px or ems to get the offset you want. */
    /* IE6 rules - you can delete these if you do not want to support IE6 */
    /* A note about multiple classes in IE6.
    * Some of the rules above use multiple class names on an element forselection, such as "hover" (MenuItemHover) and "has a subMenu"(MenuItemWithSubMenu),
    * giving the selector '.MenuItemWithSubMenu.MenuItemHover'.
    * Unfortunately IE6 does not support using mutiple classnames in aselector for an element. For a selector such as '.foo.bar.baz', IE6ignores
    * all but the final classname (here, '.baz'), and sets thespecificity accordingly, counting just one of those classs assignificant. To get around this
    * problem, we use the plugin in SpryMenuBarIEWorkaroundsPlugin.js to generate compound classnames for IE6, such as 'MenuItemWithSubMenuHover'.
    * Since there are a lotof these needed, the plugin does not generate the extra classes formodern browsers, and we use the CSS2 style mutltiple class
    * syntax for that. Since IE6 both applies rules where
    * it should not, and gets the specificity wrong too, we have to order rules carefully, so the rule misapplied in IE6 can be overridden.
    * So, we put the multiple class rule first. IE6 will mistakenly apply this rule.  We follow this with the single-class rule that it would
    * mistakenly override, making sure the  misinterpreted IE6 specificity is the same as the single-class selector, so the latter wins.
    * We then create a copy of the multiple class rule, adding a '.SpryIsIE6' class as context, and making sure the specificity for
    * the selector is high enough to beat the single-class rule in the "both classes match" case. We place the IE6 rule at the end of the
    * css style block to make it easy to delete if you want to drop IE6 support.
    * If you decide you do not need IE6 support, you can get rid of these,as well as the inclusion of the SpryMenuBarIEWorkaroundsPlugin.jsscript.
    * The 'SpryIsIE6' class is placed on the HTML element by the script in SpryMenuBarIEWorkaroundsPlugin.js if the browser isInternet Explorer 6. This avoids the necessity of IE conditionalcomments for these rules.
    .SpryIsIE6 #MenuBar .MenuBarView .MenuItemWithSubMenuHover .MenuItemLabel /* IE6 selector  */{
        background-color: transparent; /* consider exposing this prop separately*/
        color: #ffffff;
    .SpryIsIE6 #MenuBar .MenuBarView .SubMenu .MenuItemWithSubMenuHover .MenuItemLabel/* IE6 selector  */{
        background-color: transparent; /* consider exposing this prop separately*/
        color: #ffffff;
    .SpryIsIE6 #MenuBar .SubMenu .SubMenu  /* IE6 selector  */{
        margin-left: -0px; /* Compensates for at least part of an IE6 "double padding" version of the "double margin" bug */
    /* EndOAWidget_Instance_2141544 */
    /* Ends Spry Menu Bar Widget 2.0 (1.0) Horizontal Menu Custom styles */
    </style>
    The CSS governing the site generally is reproduced below:  (my belief is that it is the a:link, a:visited,  a:hover, a:active styles that may be in conflict).
    @charset "utf-8";
    body  {
        font: 100% Verdana, Arial, Helvetica, sans-serif;
       min-height: 0; /* This is necessary to overcome the "haslayout" bugthat is found in Windows 7 in conjuction with IE8.  For Moreinformation see: URL -- http://reference.sitepoint.com/css/haslayout.html */
        margin: 0; /* it's good practice to zero the margin and padding of the body element to account for differing browser defaults */
        padding: 0;
        text-align:center; /* This allows for the centering of the container and overcomes a bug inherent in IE 5 */
        color: #000000;
        list-style-image: none;
        background-color: #FCFCFC;
    h1,h2,h3,h4,h5,h6 {
    color:#000066;
    a:link {
        color: #151A96;
        text-decoration: underline;
    a:visited {
        text-decoration: underline;
        color: #1B8DCD;
    a:hover {
        text-decoration: none;
        color: #F30A0A;
    a:active {
        text-decoration: underline;
        color: #151A96;
    #container {
        width: 960px;   
        margin: 0 auto; /* the auto margins (in conjunction with a width) center the page */
        text-align: left; /* this overrides the text-align: center on the body element. */
        background-image:
        url(../ACLCO%20Graphics%20-%20Web%20site%20Parts/Website%20Midsection %20_960.png);
        background-repeat: repeat-y;
    #header {
           padding: 0;  /* this padding matches the left alignment of the elementsin the divs that appear beneath it. If an image is used in the #headerinstead of text, you may want to remove the padding. */
            width:960px;
            height:332px;
            background-image:
            url(../ACLCO%20Graphics%20-%20Web%20site%20Parts/Website%20Header_960 .png);
            background-repeat:no-repeat;
    #header h1 {
        margin-right: 0px; /* zeroing the margin of the last element in the #header div will avoid margin collapse - an unexplainable space between divs. If the div has a border around it, this is not necessary as that also avoids the margin collapse */
        padding: 0; /* using padding instead of margin will allow you to keep the element away from the edges of the div */
        display:none;
    #header img {
        display: none;
    #Main_nav_contents {
        padding: 0;
        margin-top: 0px;
        height: 39px;
        width: 950px;       
        padding-top: 275px; 
        padding-left: 39px;
        z-index: 3; 
    #MenuBarVertical {
        margin-bottom: 50px;
        padding-top: 50px;
        padding-bottom:200px;
        padding-left: 15px;
        padding-right: 15px;
    .mainContent_left {
       margin: 0;/* the right margin on this div element creates the columndown the right side of the page - no matter how much content thesidebar1 div contains, the column space will remain. You can removethis margin if you want the #mainContent div's text to fill the#sidebar1 space when the content in #sidebar1 ends. */
        padding-left:30px;
        padding-right:20px; /* remember that padding is the space inside the div box and margin is the space outside the div box */
        width: 600px;
        float: left;
    .sidebar_right {
        float: right; /* since this element is floated, a width must be given */
        width: 270px; /* the actual width of this div, in standards-compliant browsers, or standards mode in Internet Explorer will include the padding and border in addition to the width */
        margin-top: 30px;
        margin-left:0;
        margin-right:10px;
        font-size:90%;
    .mainContent_right {
        margin-left: 10px;
        padding-left:30px;
        padding-right:20px;
        width: 600px;
        float: right;
    .sidebar_left {
        float: left; /* since this element is floated, a width must be given */
        width: 270px; /* the actual width of this div, in standards-compliant browsers, or standards mode in Internet Explorer will include the padding and border in addition to the width */
        margin-top: 30px;
        margin-left:30px;
        margin-right:0;
        overflow: hidden;
        font-size:90%;
    .main_content_centered {
        width: 650px;
        margin-left: 155px;
    .main_content_centered_header {
        margin-left: 75px;
    .sidebar_textbox {
        margin: 0px;   
        width: 260px;
        padding: 2px;
    .sidebar_textbox_header {
        width:255px;
        height:58px;
        background-image:url(../ACLCO%20Graphics%20-%20Web%20site%20Parts/Por trait%20Textbox%20Header.png);
    .sidebar_textbox_background_middle {
         width: 255px;   
        padding-top: 12px;   
        padding-bottom: 10px;
        background-image:url(../ACLCO%20Graphics%20-%20Web%20site%20Parts/Por trait%20Textbox%20Middle.png);
        background-repeat: repeat-y;
    .sidebar_textbox_content {
       /* The width and padding are set as follows to accomodate quirks inbrowser rendering and to ensure that text is contained within thebackground of the text box */
        width: 230px;
        padding-left: 20px;
        padding-right: 40px;
    .sidebar_textbox_footer {
        width:255px;
        height:64px;
    background-image:url(../ACLCO%20Graphics%20-%20Web%20site%20Parts/Port rait%20Textbox%20Footer.png);
    #issues_menu a:link {
        color: #151A96;
        text-decoration: none;
        font-weight:bold;
    #issues_menu a:visited {
        color: #151A96;
        font-weight:bold;
        text-decoration: none;
    #issues_menu a:hover {   
        color: #F30A0A;
        font-weight:bold;
        font-style: oblique;
        text-decoration: none;
    #issues_menu a:active {
        color: #151A96;
        font-weight:bold;
        text-decoration: none;
    #archives {
        padding-top: 15px;
        padding-right: 15px;
        padding-bottom: 20px;
        padding-left: 0px;
    .landscape_textbox {
        width: 500px;
        margin-right: 0px;
        margin-left: 30px;
        padding-top:35px;
        padding-bottom: 25px;
        font-style: normal;
        font-weight: normal;
    .landscape_textbox_hdr {
        width:500px;
        height:38px;
        margin:auto;
        padding:0;
        background-image:
    url(../ACLCO%20Graphics%20-%20Web%20site%20Parts/Landscape%20Textbox%2 0Header.png);
    .landscape_textbox_middle {
        width:auto;
        margin:auto;
        padding-top: 12px;
        padding-bottom: 12px;
        background-image:url(../ACLCO%20Graphics%20-%20Web%20site%20Parts/lan dscapte%20Textbox%20Middle.png);
        background-repeat:repeat-y;
    .landscape_textbox_content {
        width:450px;
        padding:25px;
    .landscape_textbox_ftr {
        width:500px;
        height:44px;
        margin:auto;
        padding:0;
        background-image:url(../ACLCO%20Graphics%20-%20Web%20site%20Parts/Lan dscape%20Textbox%20Footer.png);
    #footer {
        padding: 0; /* this padding matches the left alignment of the elements in the divs that appear above it. */
        width: 960px;
        height: 222px;
        background-image:
        url(../ACLCO%20Graphics%20-%20Web%20site%20Parts/Website%20Footer%20_ 960.png);
        background-repeat:no-repeat;
    #footer p {
       margin: 0px; /* zeroing the margins of the first element in the footerwill avoid the possibility of margin collapse - a space between divs */
        padding:0px; /* padding on this element will create space, just as the the margin would have, without the margin collapse issue */
        text-align:center;
        margin-left: 50px;
        margin-right: 50px;
        padding: 10px;
        font-size: small;
    #footer h5 {
    text-align:center;
    .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 */
        float: left;
        margin-right: 8px;
    .clearfloat { /* this class should be placed on a div or break element and should be the final element before the close of a container that should fully contain a float */
        clear:both;
        height:0;
        font-size: 1px;
        line-height: 0px;
    .dropcap {
        display: block;
        float: left;
        line-height: 80%;
        font-size: 250%;
        font-weight: bolder;
        color: #000066;   
        padding: .03em .1em 0 0;
    .red_arrows {
        list-style-position: outside;
        list-style-image: url(../ACLCO%20Graphics%20-%20Web%20site%20Parts/Arrow%20Large.png);    
    .blue_bullets {
        list-style-position: outside;
        list-style-image: url(../ACLCO%20Graphics%20-%20Web%20site%20Parts/Bullet%20Medium%20Fu ll.png);   
    .attention {
        color: #F30A0A;
        font-size:x-large;
        font-family: Georgia, "Times New Roman", Times, serif;
        font-style: italic;
        font-weight:900;
    .attention_small {
        color: #F30A0A;
        font-size:large;
        font-family: Georgia, "Times New Roman", Times, serif;
        font-style: italic;
        font-weight:900;
    .table {
        table-layout:fixed;
    .blue {
        color: #00F;
    #container .mainContent_left p .blue {
        color: #0303A0;

    Hi Nancy:
    The specific code that I am referring to is the CSS code governing the styling of the spry menu widget that only works in IE 6 if, and only if, it remains in the head of the web page.  If removed and placed in a stylesheet, the IE plugins fail to compensate for the IE 6 "gap" bug.  As I said, it doesn't make sense to me that, assuming specificity is addressed, that these can not be included in an external style sheet.  I am looking for a) an explanation why they must remain embedded in the web page; and 2) any means by which I might be able to export them.
    I will reproduce the specific css style (code) below:  it should also be visable through reveal source --
    Thanks again, Steve Webster.
    The CSS governing the horizontal menu bar is as follows:  (currently the following CSS is embedded in the head of the web page)
    <style type="text/css">
    /*  -- Begins Spry Menu Widget 2.0 (1.0) Horizontal menu bar Custom styles --  */
    /* BeginOAWidget_Instance_2141544: #MenuBar */
    /* Settable values for skinning a Basic menu via presets. If presets are not sufficient, most skinning should be done in
       these rules, with the exception of the images used for down or rightpointing arrows, which are in the file SpryMenuBasic.css
         These assume the following widget classes for menu layout (set in a preset)
       .MenuBar - Applies to all menubars - default is horizontal bar, allsubmenus are vertical - 2nd level subs and beyond are pull-right.
        .MenuBarVertical - vertical main bar; all submenus are pull-right.
       You can also pass in extra classnames to set your desired top levelmenu bar layout. Normally, these are set by using a preset.
        They only apply to horizontal menu bars:
            MenuBarLeftShrink - The menu bar will be horizontally 'shrinkwrapped' to be just large enough to hold its items, and left aligned
            MenuBarRightShrink - Just like MenuBarLeftShrink, but right aligned
            MenuBarFixedLeft - Fixed at a specified width set in the rule '.MenuBarFixedLeft', and left aligned. 
            MenuBarFixedCentered -  - Fixed at a specified width set in the rule '.MenuBarFixedCentered',
                            and centered in its parent container.
            MenuBarFullwidth - Grows to fill its parent container width.
        In general, all rules specified in this file are prefixed by #MenuBar so they only apply to instances of the widget inserted along
       with the rules. This permits use of multiple MenuBarBasic widgets onthe same page with different layouts. Because of IE6 limitations,
        there are a few rules where this was not possible. Those rules are so noted in comments.
    #MenuBar  {
        background-color:transparent;
       font-family: Arial, Helvetica, sans-serif; /* Specify fonts on onMenuBar and subMenu MenuItemContainer, so MenuItemContainer,
                                                    MenuItem, and MenuItemLabel
                                                    at a given level all use same definition for ems.
                                                    Note that this means the size is also inherited to child submenus,
                                                    so use caution in using relative sizes other than
                                                    100% on submenu fonts. */
        font-weight: normal;
        font-size: 17px;
        font-style: normal;
        padding:0;
    /* Caution: because ID+class selectors do not work properly in IE6, but we want to restrict these rules to just this
    widget instance, we have used string-concatenated classnames for our selectors for the layout type of the menubar
    in this section. These have very low specificity, so be careful not to accidentally override them. */
    .MenuBar br { /* using just a class so it has same specificity as the ".MenuBarFixedCentered br" rule bleow */
        display:none;
    .MenuBarLeftShrink {
        float: left; /* shrink to content, as well as float the MenuBar */
        width: auto;
    .MenuBarRightShrink {
        float: right; /* shrink to content, as well as float the MenuBar */
        width: auto;
    .MenuBarFixedLeft {
        float: left;
        width: 80em;
    .MenuBarFixedCentered {
        float: none;
        width: 80em;
        margin-left:auto;
        margin-right:auto;
    .MenuBarFixedCentered br {
        clear:both;
        display:block;
    .MenuBarFixedCentered .SubMenu br {
        display:none;
    .MenuBarFullwidth {
        float: left;
        width: 100%;
    /* Top level menubar items - these actually apply to all items, and get overridden for 1st or successive level submenus */
    #MenuBar  .MenuItemContainer {
        padding: 0px 0px 0px 0px;
        margin: 0;     /* Zero out margin  on the item containers. The MenuItem is the active hover area.
                    For most items, we have to do top or bottom padding or borders only on the MenuItem
                    or a child so we keep the entire submenu tiled with items.
                    Setting this to 0 avoids "dead spots" for hovering. */
    #MenuBar  .MenuItem {
        padding: 10px 10px 10px 4px;
        background-color:#000088;
        background-image:url(../ACLCO%20Graphics%20-%20Web%20site%20Parts/Nav igation%20Bar%20Segment-Dark.png);
        background-repeat:repeat-x;       
    #MenuBar  .MenuItemFirst {
        border-style: none none none none;
    #MenuBar .MenuItemLast {
        border-style: none none none none;
    #MenuBar  .MenuItem  .MenuItemLabel{
        text-align:center;
        line-height:1.4em;
        color:#ffffff;
        background-color:transparent;
        padding: 0px 18px 0px 5px;
        width: 10em;
        width:auto;
    .SpryIsIE6 #MenuBar  .MenuItem  .MenuItemLabel{
        width:1em; /* Equivalent to min-width in modern browsers */
    /* First level submenu items */
    #MenuBar .SubMenu  .MenuItem {
        font-family: Arial, Helvetica, sans-serif;
        font-weight: bold;
        font-size: 15px;
        font-style: normal;
        background-color:#000088;
        padding:0px 2px 0px 0px;
        border-width:0px;
        border-color: #cccccc #cccccc #cccccc #cccccc;
        /* Border styles are overriden by first and last items */
        border-style: solid solid none solid;
    #MenuBar  .SubMenu .MenuItemFirst {
        border-style: none;
        padding: 0px;
    #MenuBar  .SubMenu .MenuItemFirst .MenuItemLabel{
        padding-top: 0px;
    #MenuBar .SubMenu .MenuItemLast {
        border-style: none none none none;
    #MenuBar .SubMenu .MenuItemLast .MenuItemLabel{
        padding-bottom: 10px;
    #MenuBar .SubMenu .MenuItem .MenuItemLabel{
        text-align:left;
        line-height:1em;   
        background-color:transparent;
        color:#ffffff;
        padding: 10px 10px 10px 10px;
        width: 240px;
    /* Hover states for containers, items and labels */
    #MenuBar .MenuItemHover {
        background-color: #2E35A3;
        background-image:url(../ACLCO%20Graphics%20-%20Web%20site%20Parts/Nav igation%20Bar%20Segment%20Light2.png);
        background-repeat:repeat-x;
    #MenuBar .MenuItemWithSubMenu.MenuItemHover .MenuItemLabel{
        background-color: transparent; /* consider exposing this prop separately*/
        color: #ffffff;
    #MenuBar .MenuItemHover .MenuItemLabel{
        background-color: transparent;
        color: #ffffff;
    #MenuBar .SubMenu .MenuItemHover {
        background-color:#2E35A3;
    #MenuBar .SubMenu .MenuItemHover .MenuItemLabel{
        background-color: transparent;
        color: #ffffff;
    /* Submenu properties -- First level of submenus */
    #MenuBar .SubMenuVisible {
        background-color: transparent;
       min-width:0%;  /* This keeps the menu from being skinnier than theparent MenuItemContainer - nice to have but not available on ie6 */
        border-style: none none none none;
    #MenuBar.MenuBar .SubMenuVisible {/* For Horizontal menubar only */
        top: 100%;    /* 100% is at the bottom of parent menuItemContainer */
        left:0px; /* 'left' may need tuning depending upon borders or padding applied to menubar MenuItemContainer or MenuItem,
                        and your personal taste.
                       0px will left align the dropdown with the content area of theMenuItemContainer. Assuming you keep the margins 0
                        on MenuItemContainer and MenuItem on the parent
                        menubar, making this equal the sum of the MenuItemContainer & MenuItem padding-left will align
                        the dropdown with the left of the menu item label.*/
        z-index:10;
    #MenuBar.MenuBarVertical .SubMenuVisible {
        top: 0px;   
        left:100%;
        min-width:0px; /* Do not neeed to match width to parent MenuItemContainer - items will prevent total collapse */
    /* Submenu properties -- Second level submenu and beyond - these are visible descendents of .MenuLevel1 */
    #MenuBar .MenuLevel1 .SubMenuVisible {
        background-color: transparent;
        min-width:0px; /* Do not neeed to match width to parent MenuItemContainer - items will prevent total collapse*/
        top: 0px;    /* If desired, you can move this down a smidge to separate top item''s submenu from menubar -
                    that is really only needed for submenu on first item of MenuLevel1, or you can make it negative to make submenu more
                    vertically 'centered' on its invoking item */
        left:100%; /* If you want to shift the submenu left to partially cover its invoking item, you can add a margin-left with a
                    negative value to this rule. Alternatively, if you use fixed-width items, you can change this left value
                    to use px or ems to get the offset you want. */
    /* IE6 rules - you can delete these if you do not want to support IE6 */
    /* A note about multiple classes in IE6.
    * Some of the rules above use multiple class names on an element forselection, such as "hover" (MenuItemHover) and "has a subMenu"(MenuItemWithSubMenu),
    * giving the selector '.MenuItemWithSubMenu.MenuItemHover'.
    * Unfortunately IE6 does not support using mutiple classnames in aselector for an element. For a selector such as '.foo.bar.baz', IE6ignores
    * all but the final classname (here, '.baz'), and sets thespecificity accordingly, counting just one of those classs assignificant. To get around this
    * problem, we use the plugin in SpryMenuBarIEWorkaroundsPlugin.js to generate compound classnames for IE6, such as 'MenuItemWithSubMenuHover'.
    * Since there are a lotof these needed, the plugin does not generate the extra classes formodern browsers, and we use the CSS2 style mutltiple class
    * syntax for that. Since IE6 both applies rules where
    * it should not, and gets the specificity wrong too, we have to order rules carefully, so the rule misapplied in IE6 can be overridden.
    * So, we put the multiple class rule first. IE6 will mistakenly apply this rule.  We follow this with the single-class rule that it would
    * mistakenly override, making sure the  misinterpreted IE6 specificity is the same as the single-class selector, so the latter wins.
    * We then create a copy of the multiple class rule, adding a '.SpryIsIE6' class as context, and making sure the specificity for
    * the selector is high enough to beat the single-class rule in the "both classes match" case. We place the IE6 rule at the end of the
    * css style block to make it easy to delete if you want to drop IE6 support.
    * If you decide you do not need IE6 support, you can get rid of these,as well as the inclusion of the SpryMenuBarIEWorkaroundsPlugin.jsscript.
    * The 'SpryIsIE6' class is placed on the HTML element by the script in SpryMenuBarIEWorkaroundsPlugin.js if the browser isInternet Explorer 6. This avoids the necessity of IE conditionalcomments for these rules.
    .SpryIsIE6 #MenuBar .MenuBarView .MenuItemWithSubMenuHover .MenuItemLabel /* IE6 selector  */{
        background-color: transparent; /* consider exposing this prop separately*/
        color: #ffffff;
    .SpryIsIE6 #MenuBar .MenuBarView .SubMenu .MenuItemWithSubMenuHover .MenuItemLabel/* IE6 selector  */{
        background-color: transparent; /* consider exposing this prop separately*/
        color: #ffffff;
    .SpryIsIE6 #MenuBar .SubMenu .SubMenu  /* IE6 selector  */{
        margin-left: -0px; /* Compensates for at least part of an IE6 "double padding" version of the "double margin" bug */
    /* EndOAWidget_Instance_2141544 */
    /* Ends Spry Menu Bar Widget 2.0 (1.0) Horizontal Menu Custom styles */
    </style>

  • Episodes with corrupted video and sound

    I have a season pass for Chuck season 3, and i have reported errors on some of the episodes where the end is corrupted so the picture freeze and sound is just noise.
    Unfortunately the support wont help, they just say that i cant get a refund (i never asked for refund, just for a new download of the file) are there anywhere i can contact when support wont help?

    Hi,
    What operating system are you on?
    Does this only happen with the nightly or can you reproduce this on other browsers as well?
    Are videos playing on the other tabs?
    To confirm what you are seeing:
    12 youtube pages are open by the time you get to 12 or 13 the video and audio are corrupted?
    Thanks

  • SOLUTION to video and sound problems

    I know this seems like a very long process, but it actually doesn't take too long (at least with music videos), and it's well worth having the audio and video ligned up properly. So hope it works for you all, let me know how it goes :)
    i know a lot of people around are having problems with the video and audio not being together when using converters with mpg files. i've been trying different settings all day and i've come up with the conclusion that muxed mpg files WILL NOT have the audio in sync no matter what settings you use.
    HOWEVER, you can download a small, FREE program VirtualDub (which can be downloaded at http://virtualdub.sourceforge.net/). (it requires NO INSTALLATION, which is brilliant)
    so, once you've got this program opened:
    1. first put your muxed video into there (drag it or "file>open file")
    2. then go to "video>compression" and select "microsoft MPEG-4 Video Codec V2" and then press "OK".
    3. after that, go to "file>save as AVI", select where you want to save it and then press OK.
    NOW you have a non-muxed video file, that you can convert using any of the regular converters (Xillisoft, Videora.. etc.) Personally i use Xillisoft's IPod Video Converter, and ta da, you know have a correctly sync'ed audio and video file compatible with the ipod.
    hope it helps everyone else
    P4   Windows XP Pro  
    EDIT: oh yeah, and after you have your converted file using Xillisoft or Videora, you can delete the AVI file and keep the original if you want.

    hmm.. ok.. well perhaps you might need the codec installed on your computer.. this is strange i thought it was default..
    can you try telling me what options you do get in there? and i'll search to see if you can download it.. OR you can try just selecting another one, i think at this point it doesn't really matter which one, as long as you use one, because an uncompressed AVI is absolutly HUGE. so try another one from the list (preferabley one that says 'no known restrictions' i think) and let me know if the sound is still good after youthen convert again using videora or xillisoft

  • Video and audio Problem

    I have a 5g ipod 30 gig. Sometimes when I play video files, and then try to go back to the menu and select an audio file, both of the files will play. This results in a terrible sounding, distorted sound where I can here the audio from both the video and the song/audiobook. I mean that once I play the audio file, the video file resumes as well so I can hear the sound on both of them. Has anyone else had this problem? Should I send the ipod back to Apple and get it fixed/replaced. Thanks in advance for your help

    PLEASE HELP ME

  • XRPM missing ivew and rendering problem

    Hi, guys:
    I am working with a RKT 2008 system and facing some XRPM issues. Would any of you be so kind to give me some comments or hints if you got?
    Iview 'task' is missing.
    Rendering problem happens whereever a chart or graphic is supposed to be created.
    Thanks very much in advance and kind regards,
    Robert

    I see you followed Jerry's advice to post over here, and haven't got any responces, so I'll at least try to get a little more information into the discussion.
    Since the document prints to pdf correctly, but not to the actual printer, it seems likely that it is a print driver issue. In the Numbers discussion on the issue, the original person with the issue was using a HP printer with a postscript driver. Since the HP support site was not very clear about whether a driver for that printer on Mavericks even existed, and the recommendation for a generic driver was for a PCL driver, not postscript, I suspect that they were not using a recommended configuration. It would probably be helpful to know the details about your printer and print driver.
    Do you have access to more than one printer to test this on?
    The new versions of Numbers and Pages are doing something strange in terms of how they copy tables to the system clipboard; the pdf version is no longer available, only bitmap images. Print to pdf, however seems to still get the pdf data. I don't think this should have anything to do with the data getting to the print driver, but it does seem consistent with your results.

  • Video and audio problem, please help!

    Every time I stream a video or play a DVD, the video and sound freezes for about ten to twelve seconds continously. It is very irritating and rather inconvenient.
    Does anyone have any idea why? I just switched to a Mac and am loving it so far. I would hate to have to take my laptop in.

    Toggle Linked selection. Shift-L. Or press the button over by snapping in the top right of the timeline,
    -Jake

  • Hey Music Video And Song Problem

    Hey I was wondering If there is an Option That I am missing or a bug but for my iPhone i have one playlist that has some songs and music videos combined in it. On my iPhone when i click on songs all of the music videos and songs come up but when play a music video i don't get the video and i just get the Sound. but in the video section i just get the Music Videos. is there a way to get rid of the music videos in the songs section.
    Thanks.

    You would need to remove the music videos from the playlist in itunes and re-sync the iphone.
    If that does not help, there is a checkbox, called include music videos, on the music tab in itunes, when the iphone is connected, that you can uncheck.

  • Video and sound problem

    I have HP Pavilion Sleekbook 15-b001ee and windows pro 8.1 when i try to play youtube or any other video the device freeze for like 5 minutes,my drivers are up to date and my windows also up to date,my internet speed is 10 mb

    khaer199 wrote:
    I have HP Pavilion Sleekbook 15-b001ee and windows pro 8.1 when i try to play youtube or any other video the device freeze for like 5 minutes,my drivers are up to date and my windows also up to date,my internet speed is 10 mb
    What broswer are you using and does it have the flash player plugin and silverlight updated as well as Java?? You left out alot of other info that might tell others where to look to diagnosis the problem. Also what do you mean other video? Where are those video on the computer or internet streaming? So give more details as to the sight will inform others to test where the problem is coming from.
    I am a Volunteer to help others on here-not a HP employee.
    Replies aren't online 24/7 because of Time Zone differences.
    Remember in this Day and Age of Computing the Internet is Knowledge at your fingertips if you choose understand it. -2015-

  • Capturing HDV and Rendering Problem

    I am using FCP 5.1.4 and a Sony HC1 HD Camcorder. Evidently I have screwed up some settings because now I run into a minor issue with being forced to render all video when clips are placed into a sequence.
    My current project setting (using Easy Setup) are for HDV-1080i50. There are no apparent setting for the video capture for the camcorder (I do have the camcorder HDV Conversion set to "Off").
    Whenever I drag a captured clip into a sequence it requires rendering. I didn't used to have to do this so am wondering what settings I got screwed up along the way.
    Thanks,
    Carl

    real simple question but check the sequence settings. What does it say?
    With FCP if you create a new project, then change the Easy Setup, Sequence 1 will be from the old Setup. Change your Easy Setup first and then create a new sequence.

  • Video and Webcam problems

    Hey
    I decided to restore my Macbook 2008 black model because i wanted it fresh.
    I backed up all of my files, restored it with the CDs. I ended up having to manually install my iLife because for some reason it didn't automatically install during the process.
    Everything worked fine, i transferred all of my information back to the computer.
    Unfortunately, I'm having problems now with the iSight, Mic, and Video player.
    The iSight and Mic work for Photobooth, Google voice and all those applications.
    The main application that it doesn't work with is Tokbox and i really want to use the webcam and mic for Tokbox.
    Secondly, video isn't playing when I'm watching a video online from Yahoo or Myspace. I can watch Youtube videos perfectly and Vimeo videos, but when i click a link that's from yahoo, it doesn't show. it shows a little person crying and says "Sorry video cannot be played". Myspace videos have the myspace symbol with a red triangle saying "error".
    My girlfriend can play the same video from yahoo no problem on her computer.
    is there anything i can do to fix the Tokbox issue and Yahoo/Myspace video issue?
    Bottom line:
    Problem 1: iSight does NOT work with Tokbox, but it does with all other applications.
    Problem 2: Mic does NOT work with Tokbox, but it does with all other applications.
    Problem 3: Yahoo and Myspace videos come up with an error, but NOT Youtube and Vimeo.
    here is an example link to the video I'm trying to watch from yahoo. it's a drama sight but the videos are streamed from Yahoo and Myspace
    http://www.mysoju.com/fated-to-love-you/episode-12/part-1/
    Thanks so much.
    PS: I HAVE already tried resetting the SMC or whatever by unplugging everything, removing the battery, and holding the power for 5 secs and then putting everything back and turning it on. Still no go.
    Message was edited by: ieatsheeet

    I have a Macbook Pro and I was having very similar issues where my iSight would not work with certain applications like TokBox and TinyChat. TinyChat actually gave me the answer so I figured I'd post it here to save everyone else the headache.
    The problem was actually Google Voice and Video. I had to uninstall it by going to Macintosh Hard Drive > Library > Application Support > Google and running the uninstaller in that directory called GoogleVoiceAndVideoUninstaller.
    Once I uninstalled that everything started working just fine.
    Hope that helps!

  • IChat video and audio problems Mac to Mac

    My associate and I have just set up video chatting with iChat, AIM accounts, and Logitech Quickcam Vision Pro cameras. I have a 12" G4 Powerbook and he has a late-model G5. We are both connecting to internet via Airports, with cable at my end and DSL at his end. After going through many discussion postings, we adjusted our settings so that Quicktime streaming was set to 1.5mbps, log on to AIM was on port 443 rather than 5190, iChat video bandwidth was set to 500, and Internet sharing was off on both machines. We can now see and hear one another, but the sound quality is very poor (we tried Skype, too, and the sound quality is much, much better) and the images we see of one another are very fuzzy and jerky (very slightly better than Skype, and our local images are very sharp and smooth). Worse, the image I see of him disintegrates (pixelates, horizontal lines, etc.) most of the time; he can see some of this on his local image of himself. The disintegration does not occur on Skype. We would rather use iChat, but obviously cannot with these conditions. I have seen no description of anything like this in any of the first 15 or so pages of discussions. Help!

    Hi,
    If Quicktime is at 1.5Mbps and you get this try the Bandwidth Setting at NONE.
    WE suggest the 500 setting fro a couple of reasons.
    Two ISPs, Comcast and Road Runner, practice Data Stream Management to combat File Sharing apps. This reduces the Internet Speed they supply to try and make these applications unworkable.
    Unfortunately they can not distinguish between those Apps and iChat in an A/V chat which is also Peer-to-Peer and sending lots of data in both directions.
    Other ISPs practice "Fair Usage" Policies and restrict the Bandwidth (And therefore speed) during High Use periods (but never say when those periods are).
    The effect is the same as the Comcast/Road Runner issue.
    If NONE still does not work try one of the other two setting in-between NONE and 500kbsp.
    iChat does use a large amount of processor and Video card time and processing.
    It pays to make sure you are not rendering some iMovie item or other high Processor use App.
    AS iChat can be effected by Bandwidth issues Sharing the Connection you have with another computer that is downloading or streaming something from the 'Net can be an issue.
    It may pay him to look in Activity Monitor (Applications/Utilities) and see what is using the Processor (Set it to All Processes then click the CPU column to re-arrange the list). Anything over about 20% may effect iChat. (vcencoder in lower case is part of iChat)
    8:12 PM Friday; January 30, 2009

  • Slow preview of videos and rendering

    i am trying to make a project and whenever I add a video file and try to preview it the video is slow. it runs only for a second then goes every 5 second one frame would pass. I finished the project and just thought if I encode it the video will turn out fine but it had the same problem.
    If anyone can help thanks.

    Jake,
    Your camera likely uses MJPED compression. This is common for many Nikon sitll cameras.
    There are three common MJPEG CODECs, Morgan, Lead and Main Concept. I think Morgan is freeware and the other two need to be purchased. Any one of these *should* go a long way to correcting your issues.
    It would be a good move for Nikon to include a CODEC for whatever flavor of MJPEG they use. Seems that the new D-90 is using yet another flavor.
    As Harm points out, the AV output from a still camera is really meant for viewing, and not for editing. This is *possibly* why Nikon has not taken the correct route - they assume that the footage will not be edited. The lack of current CODECs will likely plague users of newer still cameras, as the mfgr continues to improve on their end, but not share these improvements.
    You might also pick up a bunch of tips and ideas from the Adobe Premiere Elements forums. Just search them for "MJPEG," and have a good read. More folk seem to be trying to use still camera AV footage in those programs, Elements.
    Hunt

  • Freezing and rendering problems

    Hi all,
    I run an eMac PPC with OS 10.3.4. It is about three years old. I switch power off each night and restart every morning with automatic login for myself. Lately I have the following problems:
    1. The system sometimes (read: often nowadays) freezes a very short time after boot-up. I can move the mouse and perhaps select something, but then everything freezes and I have to reboot with the on-off switch. If the system does NOT freeze a very short time after booting, I can usually do a day's work without serious problems.
    2. Mail crashes quite frequently. This could of course be a separate problem.
    3. Sometimes the Mac screensaver, which shows a selection of photographs zooming in slowly, has problems rendering the pictures. I see a lot of flickering small rectangles in the pictures. The desktop picture (which is steady, not zooming) has no trouble of this kind.
    4. Sometimes there are tiny errors on the screen: small short lines where they should not be, small pieces of a line or characters missing. In these cases usually also problem 3 shows up.
    Are these problems related? Can reinstalling the system help? Can monitor problems cause system freezes? Please tell me this is not a hardware problem...
    Greetings,
    Sjaak

    Not that you want to hear this, but it's probably a hardware problem.
    2004 eMacs had an issue with a batch of capacitors that went bad, leaking and bulging, consequently causing issues with graphics, freezing and power exactly as you have described.
    Fortunately Apple recognised the problem and initiated a repair extension program on the affected models. To see if you qualify check your mac against the details here http://www.apple.com/support/exchange_repair/emac.html to see if you qualify.
    I have the same issues, and have found a workaround that's doing great until I can get my machine to a service centre, in order to ease the problem boot the mac in safe mode (hold down shift) and log in as admin. navigate to system then library and find all the graphics drivers (I can't remember where) and delete all the nvidia and old ati ones (basically leaving only those that are correct for your machines card). I've lost some graphical abilities but otherwise everything is great.

Maybe you are looking for