FCP has Motion file rendering problems
I am using FCP Studio 2 on a Dual-core 2.66GHz Intel Xeon Mac Pro.
I am importing Motion projects into my FCP timeline and have been getting problems.
When I first imported motion projects into my 720p24fps timeline they rendered clean. Now occassionally they either need to be re-rendered, not all of them, or they render and then when played FCP gives me the Unrendered screen when it is rendered in the timeline.
This is the most current problem. I have chosen within my FCP timeline to send a video file to motion to process the green screen. After processing the GS in Motion I save the project and return to FCP. In FCP I rendered the video files, including the motion file, in my timeline and some of them worked great. My recent render however has produced hits in my motion graphics background layer while retaining clarity in my Motion GS video.
Does anyone have any idea as to what I might be experiencing?
I have screen shots.
Thanks,
-Tim
Dual-Core Intel Xeon Mac OS X (10.4.1)
Okay, so here is what I did to fix the hits that are occuring in my Motion files within my FCP timeline.
I had to cut out the underlying Motion project background from behind my green screen Motion treated foreground. Then I reapplied the Motion project background layer and re-rendered. Now, it's working.
So Motion and FCP dev teams, is this common or is it something I'm doing wrong? If you have time of course.
Thanks,
-Tim
Dual 2ghz G5 Mac OS X (10.4.2)
Similar Messages
-
Raw file rendering problems with Canon EOS 5D in Aperture 3
Since upgrading to Aperture 3, I have had serious problems with the rendering of Canon EOS 5D (not Mark II/III) RAW files. With Aperture 2, both the preview and full-sized images looked basically the same as the original images as displayed on the camera's display, without any adjustments.
With Aperture 3, each preview images initially look fine after import, but when Aperture re-renders it from the RAW file (e.g. when displaying the full-size image), the colors are drastically intensified, and the hue is shifted generally towards green/blue. I've checked the RAW Fine Tuning, and it is set to the defaults. If I turn the default RAW Fine Tuning settings all the way down, the image is still not at all like the preview from the camera - it becomes much darker and stays too blue/green, with washed-out colors.
A friend with a Canon EOS 5D MkII also recently upgraded her Mac from Aperture 2 to 3, and hasn't experienced any problems. We've tried importing RAW files from my (non-MkII) camera to her Mac (with the default RAW Fine Tuning settings), and get the same results as with my own Mac (i.e. strange colors), so the problem seems to be related to the camera model.
I've also noticed that scanned greyscale tiff images (including images that were originally imported under Aperture 2) are changed when first displayed by Aperture 3 - they become darker and more contrasty, with lots of information lost in the shadow areas.
I've also tried removing Aperture preferences, Aperture itself, and re-installing from download, with no change in the problem. (Aperture is the current latest version, 3.3.2.)
Has anyone experienced similar problems?I'm having the same problem.
iMac running Mac OS X Lion 10.7.4 and Aperture 3.3.2. Workflow is importing through Canon's DPP and then using referenced images in Aperture. The images look great in LR4, or Canon's DPP but are flat and dingy in Aperture.
There's a free preset that goes part way to fixing it at http://theapertureblog.com/2011/02/10/my-aperture-workflow-for-working-with-cano n-5d-mark-ii-files/
but as good as this fix is, it doesn't quite do the trick. [not being a hater, and not saying I can do better]
I just got back from shoooting 1,500 images with a 5DMii and a T2i using Canon 24-105L IS, 70-200 2.8L, 50 1.8 and a Sigma 120-400 and the T2i images are not just better, they're in a different league.
I've tried shooting in Faithful, Neutral and also toggling these presets in different ways and still can't get Aperture to match what I see on the camera's screen or in other Apps. I love the interface and DB of Aperture, but what's the point of using it if it doesn't produce and awesome image in the end? -
RAW file rendering problems with Pentax-k5
Since a few weeks I have serious problems with the raw rendering in aperture 3.4. I have done everything to solve this problem, but until now without succes. I have upgrade with mountain lion OS X 10.8.2 and I use the latest version of aperture 3.4.3 RAW 402 build 672.6.
Does anyone have this problem to? Or do you know how to solve this problem?
Regards
Jan K.Jan,
that may be the same problem as discussed in this thread. Do you use in-camera settings to enhance your pictures? these will not be captured in the raw processing that Aperture does, but the pentax software understands the in-camera settings:
Image Previews In Aperture 3 - Canon 5D MK2
Regards
Léonie -
Has the re-rendering problem been fixed?
Does anyone know if the issue of when you close FCPX, and then reopen it later, needing to re-render parts of a project that had already been renedered, has been fixed?
I'm using 10.0.4 and still seem to be dealing with this annoying issue all fo the time.Yes, this is happening to me also, but did not attach much importance to it. Wonder if I am doing something wrong or whether the FCPX is at fault!
Hope we will be enlightened in this matter soon.
BTW, I have been also facing this issue of the render process going on and on. Have been asked earlier to trash preferences but am yet to do it because I do not understand how to do it and am afraid that by doing something wrong I may lose all of my work.
Hope Mr. Andy Nick will bring about a video in this matter and upload the same. If he or someone else were to do this video and teach how to go about this job step by step, such a person will be doing newcomers like me to know exactly what I should do. -
Blurring of text once motion file is imported to FCP
I've been experiencing this problem for a while now. I guess this could have been posted in the motion forum as well. When I create a simple text screen (black solid background) in Motion it looks as it should, but when I import that same file into FCP the text seems to lose a lot of quality and becomes blurred. Sometimes the quality is so bad that the crosses on T's and the dots on I's are not visible!
Both motion & fcp projects are set to 25fps. When I open Motion to start a new project I normally leave it to default (pal dv i think)
I'm sure this can easily be corrected so if anyone can point me in the right direction it would be appreciated.
AlexStill receiving a number of Motion to FCP problems.
Not only is the text blurring when imported into FCP but motion files with for instance a particle emitter/behaviour (such as stars moving towards frame) is taking nearly 2 hours to render & even then when i go to play the file in fcp the timeline freezes with a 'dropped frames' pop up appearing.
Help?! -
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> -
Hi!
I finished a clip with text animation in motion and imported it in fcp. And as always it´s problematic. In fcp my motion file isn´t playing at all, neither in dvd 3. I have to finish this project next week!!!!!!! Help!
Mel"Always" implies you have never been able to get Motion to work properly so it wouldn't be prudent to try stuff against a deadline. GEt out the Getting Started book and run it again. Now that you know your way around the interface, you can concentrate on the format settings and procedures.
"Problematic" doesn't help us help you. Frame rate, alpha, image quality, aspect ratio, color space? Try adding some descriptive information.
Without knowing what you think you're seeing, these problems are usually user issues because Motion only does what you tell it to do. So, go over your settings again and make sure the project specs match your FCP specs for image size and frame rate. Check the properties of the movie you've imported into FCP.
bogiesan -
"Wobbly"/un-interlaced images when transferring Motion file to FCP
I'm at wit's end here. I did a short 10 second intro for a press reel in Motion that is pretty basic and looks good in Motion (it's just images from the show flying across the screen, with a cloud emitter as background). The problem is that when I import it into Final Cut Pro, the images get all jittery and wobbly. It looks as if they are going in and out of different interlacing stages, which makes no sense.
The images were taken from the theater's website, and I have have tried them both in JPG and PSD formats. They are all being scaled down from the original size a touch after I import them into Motion (would that be the problem? Didn't think to try that...). As I said, they look fine and clear in Motion, but when I export into a Quicktime movie or render it and play it back in Final Cut Pro, they get all jaggedy/wobbly (for lack of a better technical term). Stills exported from the Motion file look fantastic in Photoshop (and in Final Cut Pro when I use them as background) but a paused image in Final Cut Pro looks very jagged.
I've tried everything I can think of, and even upped all the render settings in the project, to no avail. Any ideas/suggestions?I have tried exporting from Motion using the Animation settings, per the suggestion of other threads, which made it look really good when I opened it in Quicktime, but it still is jerky and the resolution is dreadful in Final Cut Pro, even when viewed through a Firewire connected monitor (the settings I have in Final Cut Pro are the DV NTSC 48 khz basic settings...720X480, pixel aspect NTSC-CCIR 601, Field Lower (even)[I tried 'none' for fun and no change], 29.97, compressor: DV/DVCPRO-NTSC, quality 100%. I've played with the video processing settings, using Motion FIltering as 'best' and rendering in RGB, to no avail).
I have tested it with photos that are 300dpi instead of 72dpi, and while that seems to have made a slight difference, the pictures still move across the screen in a jagged/wobbly format (the final picture looks great when it reaches the endpoint and just sits there)
As for the motion settings, as I said, I have tried exporting it using the Animation setting (which made it look great in Quicktime) and using Field to "none" and nothing has changed once I import it and render it in FCP.
It's a simple 10 second file created in DV/NTSC. Very few bells and whistles. -
FCP - Massive file size problem.
So I've been exporting out a 21min sequence out of fcp 7. In past edits and on the same project file, the export has been fine, rendering out at a healthy 6gb. But recently the final file size has become 29gb. This is obviously not right. My question is, what is going on and how can I fix it?
The only thing that has changed is I've done a color grade (from Color). So some of the files are different, but the new color graded clips aren't any bigger than the origianl ones, so I don't think thats the problem.
Another random thing that happend is: When exporting I give the file a name, e.g. Helloworld And I select show file extension. The weird thing is when it's completed its export, the file name then becomes Hellowordmov.mov I have not idea where that extra mov is coming from, (and it doesnt appear when I select show file extension). What is going on here?
Below are my sequence settings. I chose File - Export - Quicktime Movie... And keep it on Current Settings.
Any help is much appreciated.The Digital Rebellion Video Space Calculator shows 28.23 GB.
http://www.digitalrebellion.com/webapps/video_calc.html?format=prores_422_hq_108 0&frame_rate=f25&length=21&length_type=minutes -
Motion Files: Not Recognized in FCP 5.0.4.
Seemingly out of the blue, my version of FCP 5.0.4. is not recognizing the Motion files that I've imported into a project.
(My G5 tower was recently into the shop for a new hard drive, and updates were done on all software. So theoretically, this shouldn't be an issue.)
Motion is running fine on it's own. The problem appears to lie with Final Cut Pro.
Any suggestions for fixing the problem?
Thanks.
FCP 5.0.4., Motion 2.0.1., Mac OS X 10.4.11.Final Cut Studio installs lots of components at system level, many of them are in folders that are normally invisible to regular users and often don't have names that can be directly associated with FCS.
When the shop performed the Archive and Install, those components were left in the Previous System folder. The contents of Previous System are rendered inert by Archive and Install, so a lot of important files that FCS needs are no longer accessible.
Delete the FCS apps in your Applications folder, they are useless. Delete the entire Previous System folder. Reinstall FCS from the original disks and run Software Update to get your Pro apps to current versions.
Bill the shop for loss of earnings. -
Final Cut renders motion files, but displays them as blank
I ran into a problem today with final cut. I had a clip I wanted to stabilize, so I selected the clip, right clicked, and sent to a motion project, stabilized the clip all fine in motion, saved it, and returned to final cut. Like it is supposed to, the click reappeared, but as the motion file. It needed to be rendered, so i rendered just that clip, and then tried to play it back, and everything was blank in that clip. There was audio, and no video. I would like to figure out why its blank.
Any suggestions, I'm running the latest version of final cut and everything is up to date.
Your assistance is greatly appreciated, and happy new year!
Message was edited by: markklassenalmost impossible to tell from here. First thing to try is to export the clip from Motion, render it from Motion, and open that movie. If it's blank, well, you've got a problem with the source media and we start with a long list of other questions. You'll probably solve this yourself by trying to make the process as simple as possible, open a new project, import a short clip (SmoothCam tends to analyze the entire source clip unless you know how not to do that), and process it from FCP, there's no need to send it to Motion for SmoothCam.
bogiesan -
I've seen posts related to this elsewhere, but no answers, so here's my boggle:
For a long time I enjoyed great interraction between fcp and motion. I used motn files in the fcp timeline, exported to motion, etc. All with no problems. I'm not a daily user of either, so it's tough to pinpoint a date or update that caused the problem.
One day .motn files stopped being importable.
Dragging into the bin gives me: "File Error: Unknown File"
Using Apple-I doesn't work because the motion files are grayed out.
Same deal if I'm trying to reconnect to .motn files - grayed out.
To frustrate issues further, other G5s in the office don't have a problem.
I've tried deleting FCP from the applications folder, as well as anything that says FCP in Library \Application Support, as well as any references to motion. I've done this twice and reinstalled, but the problem won't go away.
Does anyone have any ideas? I'm at my wit's end. How do I fully uninstall FCP Studio? Is it something deeper? Is this going to take a format? Help Please.
G5 Dual 2.0 Mac OS X (10.4.3) 3GB Ram, Plenty of Disk SpaceIf this problem has suddenly occurred usually it requires reinstalling Motion.
-
Is there any easier way to edit imovie files that have been exported as mov file then added to FCE 4?? As every move I make has to be rendered and takes forever??? Also my recording is going out of focus without me touching the camera, why has this happened any idea what causes this??
iMovie '08, Mac OS X (10.5.8), FCE 4My daughter has had her Razr for about 9 months now. About two weeks ago she picked up her phone in the morning on her way to school when she noticed two cracks, both starting at the camera lens. One goes completely to the bottom and the other goes sharply to the side. She has never dropped it and me and my husband went over it with a fine tooth comb. We looked under a magnifying glass and could no find any reason for the glass to crack. Not one ding, scratch or bang. Our daughter really takes good care of her stuff, but we still wanted to make sure before we sent it in for repairs. Well we did and we got a reply from Motorola with a picture of the cracks saying this was customer abuse and that it is not covered under warranty. Even though they did not find any physical damage to back it up. Well I e-mailed them back and told them I did a little research and found pages of people having the same problems. Well I did not hear from them until I received a notice from Fed Ex that they were sending the phone back. NOT FIXED!!! I went to look up why and guess what there is no case open any more for the phone. It has been wiped clean. I put in the RMA # it comes back not found, I put in the ID #, the SN# and all comes back not found. Yet a day earlier all the info was there. I know there is a lot more people like me and all of you, but they just don't want to be bothered so they pay to have it fix, just to have it do it again. Unless they have found the problem and only fixing it on a customer pay only set up. I am furious and will not be recommending this phone to anyone. And to think I was considering this phone for my next up grade! NOT!!!!
-
Uninstall FCP for rendering problem? Then re-install?
I keep loosing my render files. I think the problem started when I installed an update for FCP. Now, the render files disappear. I'll render, but then they go away.
I've seen posts with others having this same problem. Would un-installing FCP work? Of course, I'll back up my video on an external drive - just in case. Then I'll re-install my FCP, hoping that this will solve my disappearing render files.
If you'd like more details to my rendering problem, here's the post I put up a few days ago that describes in greater detail what's happening...
http://discussions.apple.com/thread.jspa?threadID=1394901&stqc=true
Do you think un-installing would work?Hi JGD 500, and a warm welcome to the forums!
I noticed there is no mention of hardware space - should there be? This information doesn't show up anywhere in the disc utility diagnostics/profile - leading me to the thing the harddrive is busted - but the hardware test found no problems.
Yes, I believe if it can't see the HD, it won't test it or even mention it.
I've seen several Notebook HDs die within a years time, they've always been the worst HDs, but I think the pressures of today's world are making them even worse. -
How do I include Motion files in FCP "media manager" exports?
All files with a .mtn do not transfer correctly when I use media manager to duplicate a project: I get the red-dotted frame and even when I try to reconnect the frame, once rendered, remains black. I was wondering if there is a way to export Motion files there were created by exporting from FCP and "embedded" in Motion.
Thank you for the help!~/Titles.localized/Show Effects/Show/Lower 3rd/Lower 3rd.moti“ is the Motion file that is being used. I was able to replace the file and when I open a project all of the lower thirds are there except they are all missing the names and titles. I
I parsed through the .fcpevent file and found the following which seems to set the title in the effect. Its pointing to an object with an id of 2. But how do you get the title in the new Motion file to be the same object so that it will fill in correctly??
<parameter name="Object" id="2" flags="8589938704">
<parameter name="Text" id="369" flags="8606777344">
<text>Andrew and Claudia</text>
</parameter>
<parameter name="Render Text" id="360" flags="8590000146" default="0" value="0"/>
<parameter name="Face Camera" id="352" flags="8589934610" default="0" value="0"/>
<parameter name="Layout Method" id="314" flags="12901744656" default="1" value="1"/>
<parameter name="Right Margin" id="324" flags="12901679120" default="1024" value="1024"/>
<parameter name="Top Margin" id="325" flags="12901679120" default="100" value="100"/>
<parameter name="Path Options" id="329" flags="8589938704">
<parameter name="Shape Source" id="339" flags="77326254096" default="0" value="0"/>
<parameter name="Align to Path" id="333" flags="8589934610" default="1" value="1"/>
</parameter>
</parameter>
Maybe you are looking for
-
File deleted from file manager
By mistake I deleted a file from phone memory in the file manager. Is to important to have all the orgianal files in the file manager or do I reload the software. What do I do. i have a E 7.
-
I keep filling my internal HD and am looking for ways to create more space. The particular set of files that interests me is the computername.sparsebundle file. This file is 261 GB of my 300 GB HD. The file path is Users> .computername (folder) > .co
-
Need Script to disconnect Mailbox of disabled users
Hi, i have found this Script on Website but i'm not able to modify it for our Exchange Server 2010. I get Error The Windows PowerShell snap-in 'Microsoft.Exchange.Management.Powershell.Admin' is not installed on this machine an the mail contains a TX
-
HI, I have captured the ex invoice in gr and later posted the vendor ex inv in J1IEX and a/cing entry has created for part 2 and part 1 also updated.. no issues.. But when display the vendor ex invice in J1IEX it has the status as "IN PROCESS" why it
-
Hi All, How canwe find all SAP modules are being used in my SAP system. Please let me know is there any program to find the same. regards, Pravin.