Premiere CC h264 rendering problem
Premiere CC is changing aspect ratio of my video, from 4:3 to 109:96, whan rendering in h264. This was not hapening with Premiere CS 5.5.
This solved my problem. But i still don't now why is this happening. I have video that is DV 720:576 PAL pixel aspect 1.0940, when i set same parameters for encoding it changes aspect ration. But when i set pixel ration to square and stretch to fill i get correct result. H264 with correct aspect ratio. It is probably bug with encoder.
Similar Messages
-
Premiere Pro CC rendering problems : can't see my medias anymore
Hello,
I started my first project on Premiere Pro CC, but it looks like PP CC isn't working well concerning rendering, I think I'm going to use my Premiere Pro CS6 again...
Sometimes, the rendering simply stops working : I can't see my output view anymore, only the "Media Pending". Removing media cache, rendering files, no effect. Closing the project and opening it again, still the same. Sometimes I can get the files back by selecting another rendering Engine, but after a few minutes, I loose my medias again.
I've seen the other post concerning preview files lost and the "empty sequence solution', but mine is different : I can't simply get the view back.
The other problem is that when I close PP CC, and try to launch it again, If first have to manually stop the PP CC process, which seems to be crashed as it doesn't completly stop.
OlivierOk, I just met a new problem, with the "unexpected MUTE" bug.
No need to answer my previous problem, I've decided to stop using Premiere Pro CC, which needs to be seriously fixed by Adobe teams. more than 60 euros per month for such a quality is a SHAME.
Let's switch back to PP CS6. -
Adobe Premiere Elements 4 - Rendering Problem
If I create small slide shows in Photoshop Elements 6 (ranging from 59 - 125 JPEG Still Shots with captions and/or added text)I can then send each slide show separately into Premiere Elements 4, make further adjustments and add title pages, I can then render and save as a project.
If I take several of these slide shows as a block and send them to Premiere Elements 4, I get a Premiere Elements window stating "Adobe Premiere Elements is running very low on system memory, please save your project and proceed with caution". So I click OK and save. I then go to render, after 2-4% rendering I get a video Preview Error window with various warnings including, "Out of Memory - Unknown Error" or "Disc write error:- verify drive connections, available disc space and disc access privileges. Then save close and relaunch project".
If I open a slide show project in Premiere Elements 4 and try to add a second slide show to it via the get media button - in the Add Media window I get Look in 4.0 and five folders appear (no icons for projects) I can then look in files of type and there is no listing for .prel files so tried "all files" and the icons for the slide shows appear. I then select a second slide show to add to the first and click open. I now get an Add Media Failure window which gives file addresses and the error reads "File format not supported/ one of the necessary components may not have been installed".
I have run the installation disc again to repair any installation errors but to no avail.
My computer is an Intel core 2 duo 3.16 GHz on an Asus P5Q P45M M/board with Gigabyte GF9600GT Graphics card.750GB HDD & 4GB Ram.
Hope somebody can help.
Bob Smith.Most likely your photos are too large. We recommend using no larger than photos no larger than 1000x750 pixels in size. (The actual file size of the JPEGs has nothing to do with this, since JPEGs can be highly compressed.
http://www.adobeforums.com/webx/.3bb8822c
Resize your photos and you'll see a huge boost in performance. -
Premiere elements 3 rendering problem
Every time I place a shot into the timeline, the thin red render line appears and I need to render the shot, even though I haven't done anything to the shot like grading it or changing it in any way. Now my hard drive is full with all of the rendered shots and I've run out of drive space. I thought premiere only needed to render a shot if it had been changed in some way. Any help would be appreciated.
thanksWhat format are your video clips, if they are anything other than DV-AVI (type 2) or HDV then the clip will require rendering.
You can delete these temporary render files from one of the options at the top of the editing window... cant recall which one off hand. This will clear your harddrive and then you can render to clear the red line over the timeline for smooth playback. -
Hello
I recently stopped making videos to have a break, but now I'm back...but Im encountering strange rendering problem.
I am using Adobe Premiere Pro CC, my PC specs are
Intel core i5 2.8GHz
4GBs RAM
GeForce GTX 760 (Asus OC version)
64 bit Windows 8.1
Now to the problem. I render the video normally, everything normal. But when I play the video back, the audio is in sync at the beginning, then starts to slowly unsync itself as the video progresses.
But it doesn't stop there. The video randomly speeds ahead, and then jumps back about 5 seconds. The video continues for about 30 seconds, speeding up, then skips back again.
I've tried exporting the video & audio separately, but to no avail.
I've tried multiple file formats and bitrates and sizes, same problem.
It should be noted that the video plays fine in the program, just after it's exported, things go bad.
I know this may be hard to fix, but any help appreciated.
If you need any more info, just ask.
Thank you.
Edit: it should be noted that I changed my graphics card recently, that may or may not be the cause.HMm... My video is 30fps but at the end Theres a bit of an Easter egg where an images flashes rapidly, possibly in between frames, could this be the cause?
thanks for your help, though I won't be able to get on my computer for about 15 hours now, I'll keep you updated via my phone. -
Rendering problem in output of Pages 5.1
Has anyone else seen a print rendering problem when trying to print a table in Pages 5.1?
All my text in tables is jagged and lower-resolution than other text:
(Printed from Pages 5.1 (1769) on a HP Color LaserJet CP2025 from a retina MacBook Pro original model running Mavericks 10.9.1.)
To see the problem, you must look at the full size image. Right-click to open it in a new tab.
The type is set to Helvetica 12 pt black.
The borders are set to 0.5 pt black. The top two lines have a border on all sides.
The top line's border is nearly invisible; on the full size image you should see a faint blueish line.
The middle line's box box is supposed to be
 a full box, but it is missing two sides. But at least this hairline renders properly.
The pdf of the same file looks fine on screen, even at high magnification. The problem only shows up in print.
The same problem exists in Numbers (where I first experienced it):
https://discussions.apple.com/message/24695801#24695801I see you followed Jerry's advice to post over here, and haven't got any responces, so I'll at least try to get a little more information into the discussion.
Since the document prints to pdf correctly, but not to the actual printer, it seems likely that it is a print driver issue. In the Numbers discussion on the issue, the original person with the issue was using a HP printer with a postscript driver. Since the HP support site was not very clear about whether a driver for that printer on Mavericks even existed, and the recommendation for a generic driver was for a PCL driver, not postscript, I suspect that they were not using a recommended configuration. It would probably be helpful to know the details about your printer and print driver.
Do you have access to more than one printer to test this on?
The new versions of Numbers and Pages are doing something strange in terms of how they copy tables to the system clipboard; the pdf version is no longer available, only bitmap images. Print to pdf, however seems to still get the pdf data. I don't think this should have anything to do with the data getting to the print driver, but it does seem consistent with your results. -
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
SThanks 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. -
Since numbers 3.1 rendering problem in output
Since I upgraded to Numbers 3.1 all printed output is no more crispy, it looks like a rendering problem. My Number documents consist of normal text elements and tables, sometimes some charts. Scaling on printout is not activated. On the Mac display the problem does not exist, everything seems to be fine, also in large zoom factors. But printing the document produces some kind of unrendered, pixely output, comparable to a screenshot, by far not that crisp as in Numbers 3.0.1. Other applications such as Pages, Word, Excel are not affected, printouts are fine.
What I did so far:
- uninstall and reinstall numbers
- changing, reinstalling the printer driver (HP Color LaserJet 2025 Series), I use the Postscript driver
- converting the Number documents to Numbers '09 and opening them again
- playing and testing with numerous zoom factors
- changing fonts in the Numbers document
... all without any success.
What helped me was:
- Installing Numbers 3.0.1 again using TimeMachine, installed it parallel to Numbers 3.1
- In Numbers 3.1 exporting the Numbers document to Numbers '09
- Opening that document in Numbers 3.0.1
- Printing the document in Numbers 3.0.1 --> Output ist fine and perfect.
It seems to be a rendering problem, only in Numbers 3.0.1. The problem appears in all existing and new Numbers documents on Numbers 3.1.
Here is my infrastructure:
MacBook Air Mid 2013, OS X Mavericks 10.9.1
Numbers 3.1 (1769)
HP Color LaserJet CP2025dn using PostScript
Many thanks for your help!
speckchPerhaps you can see the problem in this version. This is a PRINTING problem. You cannot see it on screen in the pdf.
This is a single Numbers document, printed directly from Numbers (3.1). The font is identical in both lines. The box color is identical (black) and the width of the line is identical (0.5 pt). It was printed on an HP Color LaserJet CP2025.
The upper text is jagged. It may look fine on your screen, but it's not.
This is very obvious if you look at the larger image that is linked to the image above. (Remember, a computer screen is only 72 dpi and this image is optimized for that. Printed text is much higher resolution. So, to get an accurate view on your screen of how jagged the text is when printed, you need to look at it magnified. Right-click on the image above to open the image in a new tab, and you should get the full size.)
Also, the because the upper image is lower resolution (jaggies), the narrow line cannot print accurately. Thus, it appears blueish. When you look at the full-size image, you can see how jagged the line is and the mix of dots (red and blue, predominantly) that was output by the printer. In contrast, the lower text box is smooth and black.
I don't know where the problem lies, but I have not experienced anything like this on any other program I currently use. It's a postscript printer, and I suspect that something's gone wrong in the postscript output associated with tables and the printer is printing the screen view, not the higher resolution printer data. But that's just a guess. And as far as I know, it's not something anyone other than Apple can fix.
And, of course, since you can't see this problem on screen in the pdf, no matter how much you "zoom" in, you won't know if your files will print badly until you test it. Or, worse, your client does.
Bummer. -
h:dataTable re-rendering problem...
hi friends,
In my project i am using JSF and a4j .I am getting re-rendering problem with <h:dataTable> in mozilla it is working fine but in IE6 the dataTable is not re-rendering ..
code is:
<a4j:commandButton value="#{rb.New}" onmouseup="javascript:openModalWindow('/NGL/faces/jsp/circulation /ILLPlaceILLRequest.jsp','','dialogWidth:500px;dialogHeight:500px;status:no;scrollbars:yes;top:200;left:200')" >
<a4j:support event="onmousedown" action="#{requestApprove.newActionPerformed}"/>
<a4j:support event="oncomplete" reRender="illDetails"/>
</a4j:commandButton>
my task is:
when i press the New button another jsp page will open in modal dialog after closing the dialog the table should re-render...
Edited by: Venkat_quill on Oct 30, 2008 3:29 AM
Edited by: Venkat_quill on Oct 30, 2008 3:50 AMthanks for your reply...
I have already tried this case but, the datatable is not re-rendering ...
I got below solutions..
<a4j:commandButton value="#{rb.New}" onmouseup="javascript:openModalWindow('/NGL/faces/jsp/circulation /ILLPlaceILLRequest.jsp','','dialogWidth:500px;dialogHeight:500px;status:no;scrollbars:yes;top:200;left:200')" >
<a4j:support event="onmousedown" action="#{requestApprove.newActionPerformed}"/>
<a4j:support event="oncomplete" action="#{requestApprove.clearData}" reRender="illDetails"/>
</a4j:commandButton>Why i followed this case this i have Add,Edit ,Delete and Refresh action on datatable.In Edit case i need to set some values in the dialog this also working fine with following code..
<a4j:commandButton value="#{rb.Edit}" onmouseup="editRequest()">
<a4j:support event="onmousedown" action="#{requestApprove.editActionPerformed}" reRender="msg,msgmode"/>
<a4j:support event="oncomplete" action="#{requestApprove.clearData}" reRender="illDetails,msg,msgmode"/>
</a4j:commandButton>But this problem is oncomplete event is not working in the Internet Explorer.... -
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. -
ADF 12c Rendering Problems at design time
Hi all,
I am experimenting the following unexpected rendering problems at Design time with JDEV 12c:
- Sometimes a complete page is showed empty or blank but the components exists on the page (you can see them in the structure panel) and the page has no warnings.
- Sometimes I cannot click a component because it is behind the container.
- Sometimes the containers are rendered in other place on the page.
- Sometimes the containers not stretching
I remember some posts about this problem in 11.1.2.x but I think it was not fixed in 12c. For this reason, I have some questions:
What is the "real" memory requirement of Jdev 12c to avoid render problems?
What is the best configuration in jdev.conf?
Is it only a memory issue or Is it also a dependency reference problem? According to a blog post of Frank Nimphius:
Though with Oracle JDeveloper 11g the problem of the IDE not rendering JSF pages properly in the visual editor has become rare, there always is a way for the creative to break IDE functionality. A possible reason for the visual editor in JDeveloper to break is a failed dependency reference, which often is in a custom JSF PhaseListener configured in the faces-config.xml file. To avoid this from happening, surround the code in your PhaseListener class with the following statement (for example in the afterPhase method)
public void afterPhase(PhaseEvent phaseEvent) { if(!ADFContext.getCurrent().isDesigntime()){ ... listener code here ... } }
The reason why the visual editor in Oracle JDeveloper fails rendering the WYSIWYG view has to do with how the live preview is created. To produce the visual display of a view, JDeveloper actually runs the ADF Faces view in JSF, which then also invokes defined PhaseListeners. With the code above, you check whether the PhaseListener code is executed at runtime or design time.If it is executed in design time, you ignore all calls to external resources that are not available at design time.
source:
https://blogs.oracle.com/jdevotnharvest/entry/when_jdeveloper_ide_doesn_t
if it is a known problem, then Why is not fixed in 12c?
Jhon
Jdev 12cJhon, what Frank mentioned can't be fixed from the outside. You or the developers who use phase listens without thinking about the design view are the ones to fix this. Frank provided you with the solution for this.
However, we don't know if you use any self written phase listener. If you don't do this you have another problem. I do see some of your symptoms but can't reproduce them at the moment. As long as we can't reproduce the problem somehow it's difficult to to get a solution.
My advise is to keep your eyes open (add I do) and whenever you can reproduce this behaviour come back and tell us about it. It's hard or impossible to give the 'best' settings for Jdev.conf as they depend on other factors e.g. operating system, memory, other applications running at the same time and many more.
Personally I don't change the parameters as long as I can't put the problems to low memory (which I can't at the moment).
Timo -
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 -
Graphics rendering problem in web dynpro
Hi all,
I have a problem using BusinessGraphics in my web dynpro application. I got the "Graphics Rendering Problem". Reading some foruns, Ive read in some thread that I have to have 5 files under my igs/conf folder of SAP installation, but I have only 2 (gwfchart.tpl and xmlchart.tpl).
One proposed solution is to apply one patch to my igs server.
My question is....
- How do I dowload the patches ? From where ? I couldnt find a download link.
Thanks in advance,Hi,
the corresponding note for the IgsUrl paramter mentioned by Rich is <a href="http://service.sap.com/sap/support/notes/704604">704604</a>.
I think you should check this first before you upgrade your IGS installation. Note <a href="http://service.sap.com/sap/support/notes/931900">931900</a> shows you how to find out the IGS patchlevel. Then you see if your IGS is running (correct) and maybe an upgrade is needed also.
Regards
Matthias -
Business Graphics Tutorial: graphics rendering problem
Hello,
I did the tutorial "business graphics". Deploying the project I get the error: graphics rendering problem
Is there anything first to set up, I forgot?
Thank You, Regards MarioHi Mario,
Go to this link .It contains steps for installing igs
http://help.sap.com/saphelp_nw04/helpdata/en/4b/72d43ac66e1f08e10000000a114084/frameset.htm
After installing igs see whether you can see it on the services in mmc
Hive the listener port as 8030
After the installation go to the default page as given below
http://<server name>:8030
If the igs service is running you will get a default page
After that go to this link and do the sample application
Regards
Rohit
Maybe you are looking for
-
Trying to delete iPhoto 6 thumbsegment.data files crashes Mac OS 10.4
Summary: Whenever I try to delete any of the thumb files from the iPhoto directory on my internal hard drive or my external backup drive, it crashes the computer (screen scrolls dark then says "Have to restart, hold button for several seconds" in mul
-
Iphone 3g Dismiss button stuck. Also no service available. Help?
This is has been doing my head in! I've just bought this iphone from Ebay, upon turning it on you unlock the screen and it comes up with the whole rearranging icons and whatnot. But the dismiss button is stuck and nothing works! People have come up w
-
HELP! Project for school. What is Apples benefits and costs for consumers?
I have a project for school, and I'm focusing it around Apple. Ive done hours of research and cant find anything on the benefits and cost for Apples consumers. Help please?
-
Newest version of Premiere Pro CC 2014 on New Mac Pro, OSX 10.9.5: Everything worked well the last months. Unfortunately, I cannot export media anymore...and no idea why....very frustrating....
-
Relation between Roles and Course/Object ID
hi Please tell me the HR-infotype having roles/position/job in relation with Course/object Id. HRP1000 have only courses . or please tell me how to make relation between two i.e. roles and course/object id S@chin