CS5 Encore Animated Menu Rendering Problem

Anybody who could help! I am still experimenting but haven't find the solution (either very simple, or a serious bug ). Here is the problem: If I do any edit on the menu after setting the poster frames and/or inserting a motion (avi) or still (wav) background and re-render the menu, it plays the audio but shows the highlights only on a black background. Before rendering, all the (non-moving) background and/or the button pictures can be seen. For a simple experiment, I use the  "NTSC Blank Menu" from the "General" Set in the Library panel with the "Drive-in Video Button". My only solution at this point is to start from the beginning with the Blank Menu and copy everything from the non-functioning menu, and insert the background and/or the button pictures (via the poster frame selection), but do not touch anything at this point, and render it, it works as it supposed to. I checked the layers in Photoshop and there is no difference between the functioning and non-functioning menu layer sets. (It points to the animation part as a possible culprit in Encore.) Also, I couldn't find any way to just remove/reinsert the background/button pictures and make it work. This might even be a quirk only with this menu? I would greatly appreciate any suggestion. - Laci.

Hi LaciG,
I just encountered the same problem tonight. So I knew exactly what you were refering to.  I tried several approaches to work around this issue including erasing the motion menu background source file and re-importing in and starting the menu from scratch again and neither worked.  Eventually I did find a work around here it goes:  First I erased the buggy menu and motion menu source file (AVI).  Next  I copied the whole Encore project file and renamed it.  Then I copied and renamed the avi file I used as the motion menu.  After this I went in and used the template menu I originally used but renamed it in the asset list.  Like you said when ever you mess with the menu like changing the chapter timeline poster or such, it messes up the render.  So I made sure everything was the way it needed to be then added the AVI to the motion menu.  I re-rendered and it worked.  I know this is convoluted but it works, I guess this a good start but I may work on finding out what specific step it was in the process that did it.  I had a similar problem in CS4 but could never figure out how to fix it and now that I have Windows 7 using CS4 Encore was a nightmare so I switched to CS5 and ran into the same bug as you. Well I hope this helps

Similar Messages

  • Encore CS4 Flash Rendering Problem

    Here’s the problem, when I render to flash it comes out with a choppy slideshow and audio. If I render as a regular DVD it comes out perfectly. Can someone tell me what’s wrong?
    Thanks

    Sorry i cant wait for CS5 to comeout, i upgraded from cs3 hoping cs4 fixed alot of the problems in encore.
    Here is a lik to how it is pausing when played back. http://www.koushins.net/flash_problem/
    I realy need to find a fix for this.

  • Encore CS4 menu button problems

    I just started using Encore CS4 and I made a menu for a video.  The menu was taken from the library, but I added another button by typing text, then right clicking the text and selecting the choice to make the text into a button.  When I burned it to DVD, the text button had no highlight, so I could not choose it when the DVD was played in my DVD player.  When the DVD was played in my computer, I could choose the text button and it worked fine, it just didn’t work in my DVD player.   So, my question is: how do I create a menu button in Encore (from scratch and not from the library) that has a highlight when selected on my DVD player?
    Also, is there a good source for freeware buttons and menus that I could download and use in Encore?

    I don't fully understand what I did, but it is now working.  That is, I created a new button and the highlight works just fine.  If I look at the layers tab, the new button and the old button have the same layers.  I guess I could open them into Photoshop, but I have never used PS, so was hoping I could do this all in Encore.  Guess now is a good time to learn PS.

  • Is it possible to export your animated menu from adobe encore into adobe flash with the intention of

    Is it possible to export your animated menu from adobe encore into adobe flash with the intention of using that menu for a website or phone app??

    encore is used to create dvds.  it does export anything that you could load into flash:  http://helpx.adobe.com/encore/kb/file-formats-supported-encore-cs5.html

  • 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>

  • Subtitle problems CS5 encore 5

    Hi
    Does someone have an explanation for me on a subtitle issue I seem to have wtih CS5/ Encore 5 inbuilding a DVD.
    I have a single timeline, 4 chapters, each in a different chapter playlist. 16:9 format, 2 audio tracks, 2 subtitles tracks.
    When the DVD is made the preset combinations of audio and subtitle play correctly EXCEPT the subtitle 2 that is NOT displayed . On the DVD remote of 4 different players it show that Subtitle track 2 is selected but it is not visible on the screen. If I preview it in Encore it works fine but once built it falls apart...
    any suggestions on hwat I might be doing wrong?
    Peter

    Try this search in the meantime.
    http://forums.adobe.com/search.jspa?resultTypes=&dateRange=all&peopleEnabled=true&q=subtit le&containerType=&container=&containerName=Encore&username=&rankBy=date&numResults=15

  • DVD Remote "skip" Function Doesn't Work for Blu-ray Projects (CS5 Encore)

         I have graduated from SD to HD and I need help.
    I just finished my first HD project in CS5, burned it to a Blu-ray disk and immediately encountered a problem: the skip forward and the skip backward remote functions don’t work. (I have encountered several other problems on the way to get here but I solved those with the help of the manual and by browsing this forum ). In this project, I am doing exactly what I have done in my previous SD projects (where this function works):
    In CS5 Encore, I added “Chapter Points at Intervals…”.
    On the timeline Properties Panel, I kept the default selection “Operations: All Permitted” (that includes “Search for Chapter” in the “Permitted User Operations” menu).
    In the “Project Preview” window, clicking on the “Next Chapter” or “Previous Chapter”, the function is executed correctly.
    Still, after burning the blu-ray disk and pressing the “skip forward” or “skip backward” buttons on the Blu-ray player (Panasonic DMP-BD65) remote, the “Operation is not permitted” message appears. (This very remote button function works on all my SD projects.)
    More background info: I am also using Encore Chapter Markers from the PrPro project linked with Adobe Dynamic Link, chapter marker End Actions (Jeff’s The Focal Easy Guide to Adobe Encore DVD 2.0, pp. 178-180), and Bill’s advice on using the “dip to black” transition to avoid the ~1 second gap between chapters in the Chapter Playlist that I use to play all chapters.  The following observation may be unrelated: in Encore’s Monitor Panel, the “Step Forward” button with pressing the Alt key does not move the CTI to the next GOP mark. The “Step Forward” or “Step Backward” functions (without pressing the Alt key) work (moving the CTI one frame)..
    At this point, I desperately need the Forum’s help.
    Thanks,
         - Laci.

    Up to now I worked only with standard definition projects and outputted them
    to DVDs. This is my HD project. My problem is that I am a bit confused with
    the proper (and simple) settings for a blu-ray project. Your
    questions/comments imply that I am making a "DVD project" - but then, how
    can I burn it to a BD?
    Here is what I am doing, and please, let me know if/where I am making my
    mistake:
    1.       On the camcorder the recording format is set to "AVCHD 1080/60i
    HA".
    2.       In the CS5 PrPro new project:
    a.       General > Capture Format: HDV
    b.      New Sequence > Sequence Preset > AVCHD > "AVCHD 1080i30 (60i)".
    3.       In Encore: File >  Project Settings > Basic:
    a.       Authoring Mode: "Blu-ray"
    b.      Transcode Settings: "Codec: MPEG-2; Dimensions: 1920 x 1080; Frame
    Rate: 29.97, Fields: Upper Field First, Audio Transcoding Scheme: Dolby
    Digital, Maximum Audio/Video Bitrate: 15.0 Mbps"
    c.       In the "Default Transcode Settings" window, the Blu-ray tab is
    highlighted. (There, I could change the codec from MPEG-2 to H.264 -
    according to some articles it would give slightly better quality in certain
    circumstances - I don't know.)
    d.      On the Encore Project Panel, right clicking on the sequences, and
    choosing "Transcode Settings" from the menu, I get a window that says "DVD
    Transcoding" and "Blu-ray Transcoding". In the Blu-ray Transcoding section,
    I choose Codec: MPEG-2, Dimension 1920x1080, Frame Rate: 29.97, Quality
    Preset: Automatic Using Project Settings.
    e.       Going into the "Edit Quality Presets", I change the "Export
    Settings Preset" to "1920x1080i 29.97 Maximum Quality" (from the 1280x720)
    4.       Now, in the Project Panel, under the Blu-ray Transcode Settings I
    see: "1920x1080i 29.97 Maximum Quality MPEG-2".
    Are these the correct settings for a high quality Blu-ray project? I am
    re-transcoding the project with these settings to see if I still get the bad
    transitions.
    Thanks for your advice,
    Laci.

  • Motion Menu Renders Interlaced

    Related to this topic http://forums.adobe.com/message/5716612#5716612 which refers to Blu-ray, but I am using DVD. It sems like the same issue. I don't know if this is a DVD limitation, or if it's an Encore one. No matter what, my motion menu renders interlaced and it looks pretty terrible. Is this something I can correct?
    Preview within Encore after rendering the menu.
    Actual video

    Burn and disk and test on a TV. Use a player that handles progressive. I don't know what you will see, but don't trust Encore preview.
    See this thread:
    http://forums.adobe.com/message/1803390#1803390
    I think it was bluray, but Encore will re-transcode motion menus if you mess with them at all. And I think I recall some users having the problem you are describing. The workaround is burning everything in the menu to the motion background except for the highlight layers themselves.

  • For all of you who are having Motion Menu render problems - try this

    Just humour me for a minute.
    I have another Sonic application, and a known bug in the Motion Menu rendering applies to 29.97DF projects only.
    IE, NTSC.
    Often the video in a motion menu will fail to mux.
    There are workarounds though.
    1 - Make sure your GOP structure is 15 at most
    2 - Make certain the frame length of your video file is divisible by the GOP structure. IE, it must be a multiple of 15 frames.
    3 - if these both fail, reduce the bitrate of the video 500kbps at a time until it muxes. Most will work at 7,000, some need to be 6,000 and there are even times when you need to go as low as 4000.
    Try it - Encore uses a Sonic Authorcore, so it's worth a look.

    >Are you saying that NTSC 29.97 divided by 15 is okay?
    Not really.
    What I am saying is that your movie frame length should be divisible by the GOP structure with a GOP of 15.
    With NTSC video, you can have GOP lengths
    i up to
    18, but it is not mandatory to go to 18 - 15 is a perfectly acceptable figure. You could use a GOP of 12 if you really wanted to. What this means is typically the number of frames between I-Frames.
    MPEG-2 encoding (AKA "Moving Pictures by Educated Guesswork") P & B frames work something like this:
    i P-frames provide more compression than I-frames because they take advantage of the data in the previous I-frame or P-frame. I-frames and P-frames are called reference frames. To generate a P-frame, the previous reference frame is reconstructed, just as it would be in a TV receiver or DVD player. The frame being compressed is divided into 16 pixel by 16 pixel macroblocks. Then, for each of those macroblocks, the reconstructed reference frame is searched to find that 16 by 16 macroblock that best matches the macroblock being compressed. The offset is encoded as a "motion vector." Frequently, the offset is zero. But, if something in the picture is moving, the offset might be something like 23 pixels to the right and 4 pixels up. The match between the two macroblocks will often not be perfect. To correct for this, the encoder computes the strings of coefficient values as described above for both macroblocks and, then, subtracts one from the other. This "residual" is appended to the motion vector and the result sent to the receiver or stored on the DVD for each macroblock being compressed. Sometimes no suitable match is found. Then, the macroblock is treated like an I-frame macroblock. The processing of B-frames is similar to that of P-frames except that B-frames use the picture in the following reference frame as well as the picture in the preceding reference frame. As a result, B-frames usually provide more compression than P-frames. B-frames are never reference frames.
    In short, the I-Frame is the full description reference frame. A P frame is also a reference frame but describes the difference between the last I-Frame & itself. A good analogy is when you are on the telephone & describing what you see to a friend. The initial background description (The street, the sky, what you can see etc) would be an I-Frame. Then you describe a person walking down the street - that would be your P-Frames, as you are only describing the i changes
    in the scene.
    The bitrate can also affect things - I mentioned this too, and if a motion menu will not mux, first make sure that the film length is divisible by the GOP, and that the GOP is 15.
    If it
    i still
    won't mux, drop the bitrate by factors of 500 until it will.

  • Accordion menu rendering in Chrome

    Hi,
    i have a rendering problem with chrome:
    www.fluentcommunity.com
    the main website menu (accordion) renders well in mozilla and explorer, but if you try to open it in chrome since few weeks it does not render properly.
    Can you please direct me how to fix it?
    thank you!

    I tried to check the menu , but dont see the mentioned issue. I believe you have already fixed that.
    Thanks,
    Sanjit

  • Background video in animated menu.

    Have searched around the forums but can't find a definite answer to this.
    I created an animated menu in After Effects with a background motion loop video.
    Total length of 30 secs with button highlight appearing after 13 secs.
    If I set the loop point in Encore for approx 14 secs the animated menu and button highlightetc all works ok
    but the motion video in the background also stops at this point.
    I assume this is probably correct but if not can anyone tell me what I might be doing wrong?
    Alternatively, if it is correct, are there any tricks which would allow the background video loop to continue for the full 30secs?
    Hope I have explained this clearly enough.
    Thanks .

    Did you use any of these? If not, take a peek to see if you did it right. (I'm wondering if your still menu is covering the motion in AE.)
    Here's encore help:
    http://help.adobe.com/en_US/encore/cs/using/WSA5513911-0AD1-440c-BDAD-2E0E806B425E.html
    Here's an adobe tutorial on using AE for EN menus:
    http://www.adobe.com/designcenter/video_workshop/?id=vid0258
    From the After Effects help:
    http://help.adobe.com/en_US/aftereffects/cs/using/WS3878526689cb91655866c1103906c6dea-7e45 a.html

  • Animation menu is not showing

    I have Photoshop CS6 Extended . In that Animation menu is not showing . Only the 3D menu is available.
    Kindly help me to fix this issue.

    Do you mean the Timeline?  The Animation menu in CS5 changed to the Timeline in CS6.

  • Need solution on rendering problem

    Hi..
    I have two queries.
    1)Say if i have 3 portlets in a page.
    If a user have access to any one portlet ,that page should be displayed.But if user dont have access to all the 3 portlets then the entire page should not be displayed.
    Similarly..In a book...if all the pages dont have entitlement to the user,then book should not be displayed dynamically.
    2)In the main menu,say we have 3 books.
    Book1 have 4 pages as dropdown menu...in which one page1 is entitled to user B.
    When user login..in the main menu..book1 name is shown ..but the drop down menu to display page 1 is not coming..but when i visit the other pages and come back..it is correctly showing the drop down..
    Do any one have an idea..of why this rendering problem is comming and how to achieve both 1 and 2 of above problems.
    A quick response is much appreciated...
    Thanks
    Joshika

    1) BookBackingContext bbc = BookBackingContext.getBookBackingContext(request);
    List children = bbc.getPageBackingContexts(); // this returns only entitled children
    check the size of the list and if zero set the book as not visible / not active / return false from pre-render (i cant recollect which one works now). As before setting the union of the entitlements on the book is the easiest soln
    Do you mean given a userName get his entitlements ? I dont think this is easily possible - there is no direct api anyway(especially considering the fact that say entitlements can depend on session values so how would you get the entitlements for a different user given that he may not have logged in, much less know the current values in his session)
    If your entitlements are only based on Groups/ Users then you can essentially derive this information.
    If it is based on UUP then you can derive this information if you are willing to hardcode the knowledge of the entitlement rule in code.
    If it is complete dynamic and uses all the features
    You might try
    a. Use HTTPServletRequestWrapper to spoof the request especially its principal and pass it to the API's. This probably might not work because it depends on the bea implemention whether it gets the subject from the thread and not from the request
    b. Use IdentityAssertion and make a Separate HTTPRequest to say a custom servlet/jsp which will return you the logged in user's entitlements. the identity assertion spoof's the user you are interested in . Again this wont work for entitlements that are defined using Session / Request Property Sets.
    regards
    deepak
    regards
    deepak

  • CS5/Encore crash dumping/Bluescreen occasionaly ???

    OS: Windows 7 Pro 64-bit
    App: Adobe Premiere Pro CS4 and CS5
    This may be more of a "CS5 Encore" issue, but basically
    I am Building a BD from PPro CS5 from:
    "File -> Adobe Dynamic Link -> Send To Encore" , ...
    So, half-way through the build/encoding process (while creating a BD, or DVD image file) it crashes my system. ?
    (I have successly done this, with the same work project in CS4 without these annoying crashes ?)
    Anyone else run into this within CS5 ?
    Here's the error output after it comes back up:
    "Problem signature:
      Problem Event Name: BlueScreen
      OS Version: 6.1.7600.2.0.0.256.48
      Locale ID: 1033
    Additional information about the problem:
      BCCode: 50
      BCP1: FFFFF6837FFC6DC0
      BCP2: 0000000000000000
      BCP3: FFFFF80002D038CA
      BCP4: 0000000000000005
      OS Version: 6_1_7600
      Service Pack: 0_0
      Product: 256_1
    Files that help describe the problem:
      C:\Windows\Minidump\070310-20919-01.dmp
      C:\Users\rick\AppData\Local\Temp\WER-33727-0.sysdata.xml
    Read our privacy statement online:
      http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409 the online privacy statement is not available, please read our privacy statement offline:
      C:\Windows\system32\en-US\erofflps.txt"
    If
    Any ideas as to how to analyse the above dump files ?
    Thanks.
    Rick.

    Ya thanks, there is a way to start Encore and
    "import" your work project from Adobe Premiere Pro CS5, without CS5 running.
    But I honestly thought once in Encore, PPro would/or SHOULD just "shut-down" its memory/cpu usage,..., but I guess that is not the case as easily as it might be. -hence "dynamically linked -as in lets ALL buy MORE CPU's and Memory -yes, Bill, loves us.
    I will try just Encore alone next time.

  • Can I upgrade my CS5 Encore to CS6 Encore?

    Hello. My CS5 Encore has let me down. It keeps on forcing a Close Down after trying lots of options. When I get my movie into Encore timeline either via Dynamic Link or Media Encoder, the Monitor Panel is blank. If I then click the Play button, the whole program freezes and forces a Close Down. I am on Windows 7. I have tried both Bluray and MPEG2 formats in PAL.
    I have the full CS5 Premiere Pro Suite and want to know if I can upgrade just the Encore part of the suite to CS6 and if so, how? I do not wish to subscribe to monthly CC payments so would really appreciate your feedback. 
    Thank you. Janice

    Hello Ann John and Richard and anyone else who may be interested in helping with my problem. I have re-installed and upgraded my Adobe programs. Some had errors so I quit and tried again 12hrs later. Same message, however, the errors only related to After Effects, Bridge, Extension Manager, Illustrator, Pixel Bender Toolkit, Flash Professional, Photoshop and Photoshop Camera Raw. Would there be any connection to my problem if these programs have not upgraded fully?
    I have created a short video with audio and tried all of the export options through Dynamic Link and Media Encoder. I have Imported the movie into Encore also. Each time I can get the 1 minute movie into the Encore program. I can get the movie into the Timeline if I go File Export Timeline or if I go through Dynamic Link. I can't get it into the Timeline if I Export as an Asset, create a Timeline and try dragging the Video and Audio files down into the Timeline. On all of these options I am not able to see any of my movie in the Monitor Panel which is open-and that seems to be the issue. As soon as I attempt to get anything displayed in the Monitor Panel, Encore freezes and is forced to close down.
    Hoping someone can help solve this problem as it is very very frustrating.
    Cheers.
    Janice

Maybe you are looking for