Freeze Frame Rendering Problem

I have a problem with the rendering of freeze frames that are part of a one-hour video I created in Final Cut Express 4 when burning the video using iDVD.
I'm exporting the video from FCE to a non-self contained Quicktime movie which I then drop into my iDVD template. One or two of the freeze frames (5 10-second freeze frames and 5 5-second freeze-frames) end up with a vibrating horizontal motion.
This does not occur when I play the video file in Quicktime -- the freeze frame is solid as a rock. I've burned the DVD using all three "quality" settings in the iDVD project settings, from "best performance" to "professional" quality. Every burn ends up with a vibrating freeze frame when played from the DVD.
All the rest of the video is beautiful. I'm not sure if this is a rendering problem or some other setting issue in iDVD. All help or suggestions appreciated.
Mike

IMHO, the best thing you can do is keyframe some motion on your freeze frames. In all likelihood, you are dealing with an interlace issue. A TV screen use an interlaced signal where one line is drawn quickly followed be the second. In motion video, you will never notice interlacing. On a freeze frame however, you will certainly be able to see it. If you add some motion (Ken Burns effect), you can minimize this. You could try keeping the freeze frame... frozen and use a de-interlace filter.
Mike

Similar Messages

Freezing and rendering problems

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

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

Freeze frame glitch- text tracking?

OK, I have made some custom title generators in Motion, but sometimes I need to extend them (without extending the animation speed on the front end) so I add a freeze frame. After upgrading to 10.1.1, I've noticed that sometimes- not every time- the freeze frame renders the text with squished tracking. The generator renders and displays fine, but once it hits the freeze frame, it's squished.
Any ideas/thoughts?

You are correct. You would turn OFF Roll, so that you have a still Title. Then in Effects Control Panel, you would Keyframe the fixed Effect>Motion>Position over time. Let's say that you wish the Title to "roll" from offscreen below. Set the initial Keyframe to that Position, and then decide when you want the Title to pause. Set another Keyframe to that that point on the mini-Timeline, and alter the Position to that desired. Decide how long you want it to "hold," and then set another Keyframe there, leaving the Position alone. Then, go to the end of the Title and set one last Keyframe on that last Frame. Alter the Position to be off-screen at the top. Done.
You can "smooth out" the motion, by adding Bezier controls to each Keyframe. Choices like Ease-Out, and Ease-In will probably work fine. Rt-click the first Keyframe and choose Ease-Out. Go to the next Keyframe (the initial part of the "hold") and Rt-click, choosing Ease-In. Go to the next Keyframe (the end of your "hold"), Rt-click and choose Ease-Out. You probably do not need the Ease-In for that last Keyframe, but if you find that that last "move" is not smooth enough for you, just Rt-click and choose Ease-In.
The little "arrows" in the Keyframe Header will allow you to easily step forward and backward, from Keyframe to Keyframe.
Good luck,
Hunt
PS - before you do the Keyframes, set the Duration for the whole Title first, or you will probably need to move your Keyframes about.

Imovie11 splitting clips and freeze frame problems

I am having a problem with imovie11 splitting cips and using the freeze frame function. When I highlight the clip I want split, it splits a different clip either on the line below it or somewhere else in my project! Also, my freeze frame function freezes the frame where my playhead is BUT doesn't split the clip...so what I'm left with is the entire clip- then the freeze frame - then the continuation after the freeze frame. Is there a fix for this??

Remove any in or out points you have on the timeline. Place the playhead at the frame on the timeline you want to freeze, and then select Modify > Make Freeze Frame, the freeze should appear instantly in the viewer. You can then click the Overwrite button, and the freeze should now be placed on the timeline in the correct place.
Is this not happening?
MtD

Freeze frame with Alpha problem.

I have exported a 3 second graphic with alpha channel from After Effects.
It keys perfectly until I drop on a freeze frame to lengthen it.
There is a luminance drop of about 5% between the AE clip and the freeze
of that clip. The freeze still maintains the alpha but you can see the change in luminance as soon as you apply the freeze to the clip.
I have trashed prefs already but to no avail.
Working in 8 bit uncompressed with a AJA Kona LHe card
Any ideas how to rectify this??

OK, here is the solution. Working in 8 bit, my video processing
was selected to be 'Render in 8 bit YUV' which seems sensible.
The problem with the freeze frames disappears when I select
'Render all YUV material in high precision YUV'
So now we know!! Thanks for the help and advice.

Freeze frame problems

I have some freeze frame images in my video and when I imported it to DVD studio pro the freeze frames looked awful. On the TV screen they seem to shake back and forth really quickly. Is it some kind of interlacing problem? How can I make the still frames look good on the TV screen?

Video is interlaced, consisting of two fields that make up one frame. When you view a freeze frame on a progressive scan monitor, like your computer monitor, you'll only see one field. But if you view on an external, interlaced TV monitor, you'd see the problem right away ... which is but one of the reasons why it is strongly recommended that you always have an external monitor connected to view your work WHILE editing in FCP.
You can either choose another frame that didn't contain much motion differences between the two filed, or deinterlace the frame you chose.
-DH

CAPTURE PROBLEM - FREEZE FRAME

Hello
Its me again....see thread ID=1881846. After getting FCE to capture great for the past two days; this morning I now get the freeze frame problem. The audio is great, just a freezed frame from the beginning of what I am capturing. I don't think anything changed since last night. I made a bunch of great captures and then shut down and this morning started up to start more captures.
I searched the forum - disk permissions, took out PERIAN; but now I am at a loss.
What am I missing!
Art

Have you tried trashing your preferences?
http://www.fcpbook.com/Misc1.html
Before you do so, go into your settings and take note of any customization you might have done that you would like to restore once everything is back to normal.
Regards,
Armando.

Freeze Frame problem

I have been trying to add a freeze frame at the end of a movie but the frame created is not at the end and it causes a jump. Is there an easier way to create a freeze frame rather than right clicking

Al is right, you should check with the FCP forum.
But the same happened to me with FCE HD 3.5.
So I have 2 hints:
- was the timeline selected (no clip selected in it) before Make Freeze Frame ?
- as a workaround you can make a temporary sequence were to set the clip(s) with filters, drag this sequence into the main timeline, and apply Make Freeze Frame to that. This worked with me.
Piero

HDV timeline encoded out ProRes422: random freeze frames!

I'm working on a 30 minute piece, shot HDV 1080/30p (Canon XH-A1), in an HDV timeline. I need to deliver on SD DVD, and I've been trying to get a good encode by exporting using Quicktime Conversion, with ProRes 422 (HQ) codec.
Machine is a G5 dual 2GHz, with 4GB RAM, running 10.4.11, FCP 6.0.4, Quicktime 7.5.
I've rendered the project on the timeline (once using ProRes for renders, under Render Control tab, and once using HDV), and exported using Quicktime conversion, using ProRes 422(HQ) and 'current' size. Both times the six or seven hour encode netted me a great looking, huge file (~40GB). Sweet. Except for this problem:
In one file, the whole thing is perfect, except this one spot, where the image is replace for several seconds by a freeze frame from like 10 seconds before the error. The second file does the same thing, in a different spot, only it does it three times instead of one.
I am pretty desperate, with a film festival waiting for this piece. If I can avoid it, I'd rather not tie up the computer with another encode, unless I have some idea it's not going to give me the same (or worse) result. I'd like advice on what to do...
At this point, I'm wondering what if maybe it makes more sense to encode my QT file from HDV instead of ProRes... or maybe scrap that and try to build a frankenmovie by patching together the good bits from the two huge Quicktime files in DVD Studio Pro?
What troubleshooting should I be doing before the next step: Disk Repair, Permissions Repair, Prefs Trashing, etc.?
Anybody seen this problems? What is my next step? Thanks for looking!

FYI - I went through and recreated each freeze frame and it's working now. No idea why it was doing that, but some of the freeze frames were made from setting speed to 0%, others from Modify-Make Freeze Frame, so maybe that had something to do with it. It didn't happen on every freeze frame, but the problems didn't correspond to how the freeze frames were made either, so no clear answer. On second round, I did every single one with the Modify-Make Freeze Frame command, and now it's rendering ok. Fingers crossed.

Render or export substitutes random video for series of freeze frames

I've got a sequence that seems to act ok until I render or export to QT, at which point random motion video is substituted for the freeze frames I edited together to create a sort of stop motion animation. I tried trashing the 3x preferences I know, tried a new sequence, tried a new project, tried digitizing the material again (originally brought in as HDV, but I brought it in as regular old DV after I thought that might be the issue.)
If I keep the series of motion fx simply nested, it acts ok. If I attempt to put a widescreen mask on it, it looks ok until I render. I tried a workaround of exporting the un-masked sequence out to QT to try and bring that back in and mask it, but the QT also fills in with the random motion video bits.
Any ideas? I'd happily trash prefs, etc. again if someone's had a similar prob.

FYI - I went through and recreated each freeze frame and it's working now. No idea why it was doing that, but some of the freeze frames were made from setting speed to 0%, others from Modify-Make Freeze Frame, so maybe that had something to do with it. It didn't happen on every freeze frame, but the problems didn't correspond to how the freeze frames were made either, so no clear answer. On second round, I did every single one with the Modify-Make Freeze Frame command, and now it's rendering ok. Fingers crossed.

How to stop Freeze frame jitter/fuzz in PE3

I used freeze frame to capture a video frame to add titles. During play the freeze frames have jitter or fuzzy look. Is this interlace problem? How do I get a freeze frame (duration 5sec) to look as clean during play as when paused?

Wes,
Usually, the best practice is to critically study the exact Frame, that you Export as a still. Due to the "effective shutter angle" of the camera, one frame might look a lot better, than the one just a frame earlier, or later.
I like to view the Program Monitor (the Preview), at 100% and use the Rendered Timeline, as ATR mentioned. If one is set to Fit (and not to 100%), it's a bit tough to get a good look at the frame.
It also might help to tell us the full details of the AV file that you are using, plus the Project's Preset. There could be an element there, that would improve your output.
Good luck,
Hunt

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>

Follow up to recent posts regarding rendering problems

I've read all posts to Berrett below but can't seem to get my "Flip Video" camcorder (uses MPEG-4AVI) video into FCE without the rendering problem. I've tried to convert in two ways. Using MPEG Streamclip I transferred my video to my desktop using the "export to DV" command. It appears on desktop with a .DV suffix I then imported into browser. After editing in the viewer and trying to insert edit in canvas I get the message " "..clip does not match sequence settings..." I then click yes to change sequence settings and the clip moves to timeline. The video plays but the audio has to be rendered.
Next, I tried converting using the export to quicktime command in Streamclip with sound uncompressed and setting to DV-NTSC. When I insert into FCE and insert edit I get the sound but the picture has to be rendered. What am I doing wrong?
I've been working on this all day and am getting very depressed. Please help. Thanks.
Ed
S

Thanks but I think I tried that without success. I must have a setting somewhere wrong. My audio is fine but I still have to render my video. Using Streamclip to convert to quicktime here are the setting I used in the Movie Exporter dialog box.
Compression: Apple Motion JPEG A
Sound: uncompressed
frame size 720x480 (DV-NTSC)
In FCE my easy setup is
Format: NTSC
Use: DV-NTSC
Help.

Freeze Frame not working

I'm using iMovie 10.0.3. When I try to do a freeze frame of a clip, it just creates a black clip.

Did you place the playhead on the frame of the clip you wanted as a freeze frame and option F on the keyboard or freeze frame in the modify menu? If that gives you a black frame it could be a media problem or an iMovie problem. What's the parameters of the clip? You can open the clip in Quicktime and look in the Inspector window to see the properties.

JTreeTable rendering problems

Hi all!
I have used some clesses to create a JTable containing a JTree, basing on the example in the sun's site. The costructor is:
JFrame frame = new JFrame("TITLE");
JTreeTable table = createTable(); //Creates the treetable
JScrollPane scrollPane = new JScrollPane(table); //it puts the newly created table in a scrollPane
frame.getContentPane().add(scrollPane,BorderLayout.CENTER);
frame.pack();
frame.show();
I have the following problems:
1. If I have not many nodes in the tree, I have a bad renderer effect: the table doesn't fit the whole window but just the upper part of that, at the bottom it's all gray (the JFrame color, I think).Even if I set the JFrame background color to white, I still have that problem.
2. If I don't add the table to the scrollbar, I can't see the headers, but I don't have the problem of the gray panel.
Does anyone know how I can work out this? Has anybody examples of JTreeTables that don't have this rendering problem (with the table fitting the whole window even though they don't have many nodes)?
Feedbacks are welcome, this is really showstopper for me...
Thanks a lot!

Hi there.
Try setting the viewport color of your scrollpane. I don't have my API's on hand but you go something like myScrollPane.getViewport().setBackgroundColor(Color.white);
How does that go for you?
Cheers,
Rachel

Freeze Frame Rendering Problem

Similar Messages

Maybe you are looking for