WMV rendered in AE-CS3 looks gray in PowerPoint 2007

I've been trying to produce a wmv from Adobe After Effects CS3 to insert into a PowerPoint presentation. Both the video and the powerpoint presentation have a white background. The problem is that is seems like no matter how I tweak the settings in the encoder for WMV the colors come out washed out and the white background comes out gray. I've tried making all the whites 253,253,253 thinking maybe it was an issue with the gamut differences between tv and screen, but that didn't help, it's still gray.
I'm practically pulling my hair out on this one. I thought wmv was suppose to work pretty well with PowerPoint? Are there specific settings I need to tweak somewhere to make this work?

Actually I already tried that and while it did fix the background issue, it made the rest of the video look bad. From what I've read its not designed for highly animated videos, which mine is, so even at a higher quality it seems to stutter and the images appear to be at a lower color depth.
Maybe I'm setting it wrong?

Similar Messages

Two pages look gray in preview mode, wont' export

Two pages in my document (a science text for kids) suddenly "went gray." They look fine in normal mode, but in preview mode the pages look gray like the background, except for the imported images which still have a white background. When I try to export and make a PDF file, those two pages come out as blank pages. I tried to delete the pages but they won't delete. When I click on the first page in the PAGES side bar, it takes me to the first page of the document and when I click on the second one, it takes me to the last page. I have no idea what keys I might have accidentally pressed. I don't even know the correct terms for the problem. Does anyone know what is going on? (This is a really important document for my business and is 250 pages long.)

See both Remove minor corruption by exporting and Replace Your Preferences and try rebooting your system.

Top half of video is missing on imported WMV files. Running CS3 & Win XP Professional

Top half of video is missing on imported .WMV files. I'm running CS3 Adobe Premier Pro with Win XP Professional OS
Hi all,
I just installed my Adobe Premier Pro CS3 for the very first time. I then IMPORTED a WMV file into the Project Frame and then Dragged & Dropped it into the Time Line. All the windows (or Frames) Project Frame, Source Frame and the mini-Project Frame show this video with the top half missing. I’m running Win XP Professional with the latest Service Packs installed.
Please Help.
Thanks
Derek

After Searching the net for a while here, I found a solution to the "Half Screen" problem!
The half screen video problems seen while trying to play WMV files in my CS3 Adobe Premiere Pro program seems to have been due to a recent Windows software Security update made to it’s Windows Media Player programming. As soon as I removed that update, my WMV files now show normally within Adobe Premier Pro.
If you wish to uninstall this Windows Patch / Security Update on Win XP Machines:
No#1 Prior to removing/un-installing the file, shut off "Windows Automatic Updates" and set update preferences to manual. Thus in the future you can select which Updates you want to instal (and which one not to instal) *remember to ignore the KB2834904 update in the future! That is at least until Widows fixes this Security Update / Patch.
A) Go to "Add/Remove Programs" in Control Panel
B) In the Add/Remove Programs, check the "Show Updates" box located at the top of that window
C) Scroll down to "Windows XP Software Updates" and within that section, scroll down to "Security Update for Windows Media Player" KB2834904 (mine was dated 7-10-2013)
D) Click on the REMOVE button and re-start your system.
If using Win 7 Operating System: to remove this Patch / Security Update the file to remove is: KB2803821 - In Windows 7, go to "Add/Remove Programs" in Control Panel, click on the "View installed updates" link in the left sidebar, search for KB 2803821 and click REMOVE.
Good luck everyone!
Derek

Black Looks Gray?

I am needed to make black brush strokes but the black looks gray and the default black seems to be gray. I have tried all I could think but can't figure out how to fix it! Any help would be appreciated!
Thanks,
Rachel

Rachel,
Is it a 100% K in a CMYK document? If so, you may need to use a rich black, possibly/prefereably based upon the CMY colour combination used, and avoiding overdoing it; the maximum total ink coverage depends on the paper of intended use.
If it is an RGB document, you may ensure that it is R/G/B = 0/0/0.

Pixellation in WMV renders

I've got another question for my fellow playheads.
I've been rendering my projects out as WMVs in Premiere Pro CS4, and while most of
the video comes out fine, in some spots, it comes out excessively pixellated.
I'm working with HD 1920x1080 sequence settings, 24 fps.
I've noticed that this usually happens in spots that are set up as follows:
Video Track 3:   [Transition][PNG-------------------------------------------------------][Transition]
Video Track 2:                      [Transition] [M2TS---------------][Transition]
Video Track 1:   [Transition][JPG--------------------------------------------------------][Transition]
Here are some screenshots of said glitchiness:
http://img704.imageshack.us/img704/5650/glitchy1.jpg
http://img194.imageshack.us/img194/1263/glitchy2.jpg
http://img202.imageshack.us/img202/8786/glitchy3.jpg
And here are my render settings.
http://img576.imageshack.us/img576/6143/glitchysettings.jpg
Will increasing the Bitrate solve this? I tried going from an average video bitrate of 1250
and a peak video bitrate of 1500 to an average video bitrate of 1500 and a peak video
bitrate of 2000, and it really didn't fix much. The next step is bumping it up to 3k - 4k,
though this could prove problematic due to file size constraints.
As always, much thanks in advance!

Dan,
That would be my first step in the process.
Also, I'll be that a few users, like Ann Bens, who does do a fair amount of WMV Export, will have some comments there too.
Though I do not see it mentioned that often any more (maybe PrPro has gotten better in later versions with WMV Export?), but going back a bit, many swore by Windows Media Encoder (free from MS) for WMV Export. Might be worth a look too.
Good luck, and give those users a moment to find this post. For instance, Ann and Harm Millaard, are in Holland, so they are usually around here at different times, than folk like me, who are in AZ, USA.
I'll follow along to see if things improve for you, and also what they say about the Export settings.
Hunt

Valid svg file not rendered properly Illustrator CS3: Place or File open messes up svg

Hi I have a svg file for a chemical molecule that is validated as valid SVG by the w3c validator. Firrefox, google chrome and inkscape , as well as other svg applications open and render the file just fine.
However adobe illustrator renders the characters in the file some 600% bigger than they need to be.
This seems to be a bug in the svg rendering , given that the svg file works in the other programs mentioned. Can anyone tell me how to get the molecule read in correctly into Adobe Illustrator
. I am attaching a screenshot of the molecule as read into Adobe Illustrator and the svg file itself. I am using Adobe Illustrator CS3 on Windows XP
Thanks
Hari
The svg file is :
<?xml version="1.0" encoding="UTF-8"?>
<svg xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" width="300pt" height="300pt" viewBox="0 0 300 300" version="1.1">
<defs>
<g>
<symbol overflow="visible" id="glyph0-0">
<path style="stroke:none;" d="M 0.5 1.765625 L 0.5 -7.046875 L 5.5 -7.046875 L 5.5 1.765625 L 0.5 1.765625 Z M 1.0625 1.21875 L 4.9375 1.21875 L 4.9375 -6.484375 L 1.0625 -6.484375 L 1.0625 1.21875 Z M 1.0625 1.21875 "/>
</symbol>
<symbol overflow="visible" id="glyph0-1">
<path style="stroke:none;" d="M 0.921875 -7.296875 L 3.015625 -7.296875 L 5.671875 -2.296875 L 5.671875 -7.296875 L 7.453125 -7.296875 L 7.453125 0 L 5.359375 0 L 2.703125 -5 L 2.703125 0 L 0.921875 0 L 0.921875 -7.296875 Z M 0.921875 -7.296875 "/>
</symbol>
<symbol overflow="visible" id="glyph0-2">
<path style="stroke:none;" d="M 0.921875 -7.296875 L 2.796875 -7.296875 L 2.796875 -4.515625 L 5.578125 -4.515625 L 5.578125 -7.296875 L 7.453125 -7.296875 L 7.453125 0 L 5.578125 0 L 5.578125 -3.09375 L 2.796875 -3.09375 L 2.796875 0 L 0.921875 0 L 0.921875 -7.296875 Z M 0.921875 -7.296875 "/>
</symbol>
<symbol overflow="visible" id="glyph0-3">
<path style="stroke:none;" d="M 2.875 -1.375 L 6.09375 -1.375 L 6.09375 0 L 0.796875 0 L 0.796875 -1.375 L 3.453125 -3.734375 C 3.691406 -3.941406 3.867188 -4.148438 3.984375 -4.359375 C 4.097656 -4.566406 4.15625 -4.78125 4.15625 -5 C 4.15625 -5.34375 4.039062 -5.617188 3.8125 -5.828125 C 3.582031 -6.035156 3.273438 -6.140625 2.890625 -6.140625 C 2.597656 -6.140625 2.273438 -6.078125 1.921875 -5.953125 C 1.578125 -5.828125 1.207031 -5.640625 0.8125 -5.390625 L 0.8125 -7 C 1.238281 -7.132812 1.65625 -7.238281 2.0625 -7.3125 C 2.476562 -7.382812 2.882812 -7.421875 3.28125 -7.421875 C 4.15625 -7.421875 4.832031 -7.226562 5.3125 -6.84375 C 5.800781 -6.457031 6.046875 -5.921875 6.046875 -5.234375 C 6.046875 -4.835938 5.941406 -4.46875 5.734375 -4.125 C 5.523438 -3.78125 5.09375 -3.320312 4.4375 -2.75 L 2.875 -1.375 Z M 2.875 -1.375 "/>
</symbol>
<symbol overflow="visible" id="glyph0-4">
<path style="stroke:none;" d="M 4.25 -6.0625 C 3.675781 -6.0625 3.226562 -5.847656 2.90625 -5.421875 C 2.59375 -5.003906 2.4375 -4.410156 2.4375 -3.640625 C 2.4375 -2.867188 2.59375 -2.269531 2.90625 -1.84375 C 3.226562 -1.425781 3.675781 -1.21875 4.25 -1.21875 C 4.820312 -1.21875 5.265625 -1.425781 5.578125 -1.84375 C 5.898438 -2.269531 6.0625 -2.867188 6.0625 -3.640625 C 6.0625 -4.410156 5.898438 -5.003906 5.578125 -5.421875 C 5.265625 -5.847656 4.820312 -6.0625 4.25 -6.0625 Z M 4.25 -7.421875 C 5.414062 -7.421875 6.332031 -7.082031 7 -6.40625 C 7.664062 -5.738281 8 -4.816406 8 -3.640625 C 8 -2.460938 7.664062 -1.535156 7 -0.859375 C 6.332031 -0.191406 5.414062 0.140625 4.25 0.140625 C 3.082031 0.140625 2.164062 -0.191406 1.5 -0.859375 C 0.832031 -1.535156 0.5 -2.460938 0.5 -3.640625 C 0.5 -4.816406 0.832031 -5.738281 1.5 -6.40625 C 2.164062 -7.082031 3.082031 -7.421875 4.25 -7.421875 Z M 4.25 -7.421875 "/>
</symbol>
</g>
</defs>
<g id="surface0">
<rect x="0" y="0" width="300" height="300" style="fill:rgb(100%,100%,100%);fill-opacity:1;stroke:none;"/>
<path style="fill:none;stroke-width:1.2;stroke-linecap:butt;stroke-linejoin:miter;stroke:rgb(0% ,0%,0%);stroke-opacity:1;stroke-miterlimit:10;" d="M 229.460938 201.945312 L 211.867188 194.640625 "/>
<path style="fill:none;stroke-width:1.2;stroke-linecap:butt;stroke-linejoin:miter;stroke:rgb(0% ,0%,100%);stroke-opacity:1;stroke-miterlimit:10;" d="M 211.867188 194.640625 L 194.273438 187.339844 "/>
<path style="fill:none;stroke-width:1.2;stroke-linecap:butt;stroke-linejoin:miter;stroke:rgb(0% ,0%,0%);stroke-opacity:1;stroke-miterlimit:10;" d="M 227.890625 195.792969 L 213.8125 189.949219 "/>
<path style="fill:none;stroke-width:1.2;stroke-linecap:butt;stroke-linejoin:miter;stroke:rgb(0% ,0%,100%);stroke-opacity:1;stroke-miterlimit:10;" d="M 213.8125 189.949219 L 199.738281 184.109375 "/>
<path style="fill:none;stroke-width:1.2;stroke-linecap:butt;stroke-linejoin:miter;stroke:rgb(0% ,0%,100%);stroke-opacity:1;stroke-miterlimit:10;" d="M 259.703125 178.773438 L 244.582031 190.359375 "/>
<path style="fill:none;stroke-width:1.2;stroke-linecap:butt;stroke-linejoin:miter;stroke:rgb(0% ,0%,0%);stroke-opacity:1;stroke-miterlimit:10;" d="M 244.582031 190.359375 L 229.460938 201.945312 "/>
<path style="fill:none;stroke-width:1.2;stroke-linecap:butt;stroke-linejoin:miter;stroke:rgb(0% ,0%,100%);stroke-opacity:1;stroke-miterlimit:10;" d="M 194.273438 187.339844 L 191.800781 168.453125 "/>
<path style="fill:none;stroke-width:1.2;stroke-linecap:butt;stroke-linejoin:miter;stroke:rgb(0% ,0%,0%);stroke-opacity:1;stroke-miterlimit:10;" d="M 191.800781 168.453125 L 189.324219 149.5625 "/>
<path style=" stroke:none;fill-rule:nonzero;fill:rgb(100%,100%,100%);fill-opacity:1;" d="M 188.394531 182.230469 L 200.152344 182.230469 L 200.152344 192.445312 L 188.394531 192.445312 Z M 188.394531 182.230469 "/>
<g style="fill:rgb(0%,0%,100%);fill-opacity:1;">
<use xlink:href="#glyph0-1" x="191.007812" y="190.988281"/>
</g>
<path style="fill:none;stroke-width:1.2;stroke-linecap:butt;stroke-linejoin:miter;stroke:rgb(0% ,0%,0%);stroke-opacity:1;stroke-miterlimit:10;" d="M 189.324219 149.5625 L 219.566406 126.390625 "/>
<path style="fill:none;stroke-width:1.2;stroke-linecap:butt;stroke-linejoin:miter;stroke:rgb(0% ,0%,0%);stroke-opacity:1;stroke-miterlimit:10;" d="M 189.261719 143.214844 L 213.453125 124.675781 "/>
<path style="fill:none;stroke-width:1.2;stroke-linecap:butt;stroke-linejoin:miter;stroke:rgb(0% ,0%,100%);stroke-opacity:1;stroke-miterlimit:10;" d="M 157.941406 127.960938 L 173.632812 138.761719 "/>
<path style="fill:none;stroke-width:1.2;stroke-linecap:butt;stroke-linejoin:miter;stroke:rgb(0% ,0%,0%);stroke-opacity:1;stroke-miterlimit:10;" d="M 173.632812 138.761719 L 189.324219 149.5625 "/>
<path style="fill:none;stroke-width:1.2;stroke-linecap:butt;stroke-linejoin:miter;stroke:rgb(0% ,0%,0%);stroke-opacity:1;stroke-miterlimit:10;" d="M 219.566406 126.390625 L 254.757812 140.996094 "/>
<path style="fill:none;stroke-width:1.2;stroke-linecap:butt;stroke-linejoin:miter;stroke:rgb(0% ,0%,0%);stroke-opacity:1;stroke-miterlimit:10;" d="M 219.566406 126.390625 L 213.222656 108.429688 "/>
<path style="fill:none;stroke-width:1.2;stroke-linecap:butt;stroke-linejoin:miter;stroke:rgb(0% ,0%,100%);stroke-opacity:1;stroke-miterlimit:10;" d="M 213.222656 108.429688 L 206.875 90.46875 "/>
<path style="fill:none;stroke-width:1.2;stroke-linecap:butt;stroke-linejoin:miter;stroke:rgb(0% ,0%,0%);stroke-opacity:1;stroke-miterlimit:10;" d="M 254.757812 140.996094 L 257.230469 159.882812 "/>
<path style="fill:none;stroke-width:1.2;stroke-linecap:butt;stroke-linejoin:miter;stroke:rgb(0% ,0%,100%);stroke-opacity:1;stroke-miterlimit:10;" d="M 257.230469 159.882812 L 259.703125 178.773438 "/>
<path style="fill:none;stroke-width:1.2;stroke-linecap:butt;stroke-linejoin:miter;stroke:rgb(0% ,0%,0%);stroke-opacity:1;stroke-miterlimit:10;" d="M 250.214844 145.433594 L 252.195312 160.542969 "/>
<path style="fill:none;stroke-width:1.2;stroke-linecap:butt;stroke-linejoin:miter;stroke:rgb(0% ,0%,100%);stroke-opacity:1;stroke-miterlimit:10;" d="M 252.195312 160.542969 L 254.171875 175.652344 "/>
<path style="fill:none;stroke-width:1.2;stroke-linecap:butt;stroke-linejoin:miter;stroke:rgb(0% ,0%,0%);stroke-opacity:1;stroke-miterlimit:10;" d="M 254.757812 140.996094 L 269.878906 129.410156 "/>
<path style="fill:none;stroke-width:1.2;stroke-linecap:butt;stroke-linejoin:miter;stroke:rgb(0% ,0%,100%);stroke-opacity:1;stroke-miterlimit:10;" d="M 269.878906 129.410156 L 285 117.820312 "/>
<path style=" stroke:none;fill-rule:nonzero;fill:rgb(100%,100%,100%);fill-opacity:1;" d="M 253.828125 173.664062 L 265.585938 173.664062 L 265.585938 183.878906 L 253.828125 183.878906 Z M 253.828125 173.664062 "/>
<g style="fill:rgb(0%,0%,100%);fill-opacity:1;">
<use xlink:href="#glyph0-1" x="256.4375" y="182.421875"/>
</g>
<path style=" stroke:none;fill-rule:nonzero;fill:rgb(100%,100%,100%);fill-opacity:1;" d="M 265.046875 112.625 L 304.957031 112.625 L 304.957031 123.015625 L 265.046875 123.015625 Z M 265.046875 112.625 "/>
<g style="fill:rgb(0%,0%,100%);fill-opacity:1;">
<use xlink:href="#glyph0-1" x="273.914062" y="121.53125"/>
<use xlink:href="#glyph0-2" x="282.413971" y="121.53125"/>
<use xlink:href="#glyph0-3" x="290.913879" y="121.53125"/>
</g>
<path style="fill:none;stroke-width:1.2;stroke-linecap:butt;stroke-linejoin:miter;stroke:rgb(0% ,0%,100%);stroke-opacity:1;stroke-miterlimit:10;" d="M 206.875 90.46875 L 187.832031 90.953125 "/>
<path style="fill:none;stroke-width:1.2;stroke-linecap:butt;stroke-linejoin:miter;stroke:rgb(0% ,0%,0%);stroke-opacity:1;stroke-miterlimit:10;" d="M 187.832031 90.953125 L 168.789062 91.4375 "/>
<path style="fill:none;stroke-width:1.2;stroke-linecap:butt;stroke-linejoin:miter;stroke:rgb(0% ,0%,100%);stroke-opacity:1;stroke-miterlimit:10;" d="M 203.195312 95.640625 L 187.960938 96.03125 "/>
<path style="fill:none;stroke-width:1.2;stroke-linecap:butt;stroke-linejoin:miter;stroke:rgb(0% ,0%,0%);stroke-opacity:1;stroke-miterlimit:10;" d="M 187.960938 96.03125 L 172.726562 96.417969 "/>
<path style=" stroke:none;fill-rule:nonzero;fill:rgb(100%,100%,100%);fill-opacity:1;" d="M 200.996094 85.359375 L 212.753906 85.359375 L 212.753906 95.574219 L 200.996094 95.574219 Z M 200.996094 85.359375 "/>
<g style="fill:rgb(0%,0%,100%);fill-opacity:1;">
<use xlink:href="#glyph0-1" x="203.609375" y="94.117188"/>
</g>
<path style="fill:none;stroke-width:1.2;stroke-linecap:butt;stroke-linejoin:miter;stroke:rgb(0% ,0%,0%);stroke-opacity:1;stroke-miterlimit:10;" d="M 168.789062 91.4375 L 163.363281 109.699219 "/>
<path style="fill:none;stroke-width:1.2;stroke-linecap:butt;stroke-linejoin:miter;stroke:rgb(0% ,0%,100%);stroke-opacity:1;stroke-miterlimit:10;" d="M 163.363281 109.699219 L 157.941406 127.960938 "/>
<path style="fill:none;stroke-width:1.2;stroke-linecap:butt;stroke-linejoin:miter;stroke:rgb(0% ,0%,100%);stroke-opacity:1;stroke-miterlimit:10;" d="M 157.941406 127.960938 L 139.980469 134.308594 "/>
<path style="fill:none;stroke-width:1.2;stroke-linecap:butt;stroke-linejoin:miter;stroke:rgb(0% ,0%,0%);stroke-opacity:1;stroke-miterlimit:10;" d="M 139.980469 134.308594 L 122.019531 140.65625 "/>
<path style=" stroke:none;fill-rule:nonzero;fill:rgb(100%,100%,100%);fill-opacity:1;" d="M 152.0625 122.855469 L 163.820312 122.855469 L 163.820312 133.070312 L 152.0625 133.070312 Z M 152.0625 122.855469 "/>
<g style="fill:rgb(0%,0%,100%);fill-opacity:1;">
<use xlink:href="#glyph0-1" x="154.675781" y="131.609375"/>
</g>
<path style="fill:none;stroke-width:1.2;stroke-linecap:butt;stroke-linejoin:miter;stroke:rgb(0% ,0%,0%);stroke-opacity:1;stroke-miterlimit:10;" d="M 122.019531 140.65625 L 111.171875 177.179688 "/>
<path style="fill:none;stroke-width:1.2;stroke-linecap:butt;stroke-linejoin:miter;stroke:rgb(10 0%,0%,0%);stroke-opacity:1;stroke-miterlimit:10;" d="M 90.632812 119.054688 L 106.328125 129.855469 "/>
<path style="fill:none;stroke-width:1.2;stroke-linecap:butt;stroke-linejoin:miter;stroke:rgb(0% ,0%,0%);stroke-opacity:1;stroke-miterlimit:10;" d="M 106.328125 129.855469 L 122.019531 140.65625 "/>
<path style="fill:none;stroke-width:1.2;stroke-linecap:butt;stroke-linejoin:miter;stroke:rgb(0% ,0%,0%);stroke-opacity:1;stroke-miterlimit:10;" d="M 111.171875 177.179688 L 73.085938 178.148438 "/>
<path style="fill:none;stroke-width:1.2;stroke-linecap:butt;stroke-linejoin:miter;stroke:rgb(0% ,0%,0%);stroke-opacity:1;stroke-miterlimit:10;" d="M 111.171875 177.179688 L 122.757812 192.300781 "/>
<path style="fill:none;stroke-width:1.2;stroke-linecap:butt;stroke-linejoin:miter;stroke:rgb(10 0%,0%,0%);stroke-opacity:1;stroke-miterlimit:10;" d="M 122.757812 192.300781 L 134.34375 207.421875 "/>
<path style="fill:none;stroke-width:1.2;stroke-linecap:butt;stroke-linejoin:miter;stroke:rgb(0% ,0%,0%);stroke-opacity:1;stroke-miterlimit:10;" d="M 73.085938 178.148438 L 60.390625 142.226562 "/>
<path style="fill:none;stroke-width:1.2;stroke-linecap:butt;stroke-linejoin:miter;stroke:rgb(0% ,0%,0%);stroke-opacity:1;stroke-miterlimit:10;" d="M 73.085938 178.148438 L 62.285156 193.839844 "/>
<path style="fill:none;stroke-width:1.2;stroke-linecap:butt;stroke-linejoin:miter;stroke:rgb(10 0%,0%,0%);stroke-opacity:1;stroke-miterlimit:10;" d="M 62.285156 193.839844 L 51.484375 209.53125 "/>
<path style="fill:none;stroke-width:1.2;stroke-linecap:butt;stroke-linejoin:miter;stroke:rgb(0% ,0%,0%);stroke-opacity:1;stroke-miterlimit:10;" d="M 60.390625 142.226562 L 75.511719 130.640625 "/>
<path style="fill:none;stroke-width:1.2;stroke-linecap:butt;stroke-linejoin:miter;stroke:rgb(10 0%,0%,0%);stroke-opacity:1;stroke-miterlimit:10;" d="M 75.511719 130.640625 L 90.632812 119.054688 "/>
<path style="fill:none;stroke-width:1.2;stroke-linecap:butt;stroke-linejoin:miter;stroke:rgb(0% ,0%,0%);stroke-opacity:1;stroke-miterlimit:10;" d="M 60.390625 142.226562 L 23.867188 131.378906 "/>
<path style=" stroke:none;fill-rule:nonzero;fill:rgb(100%,100%,100%);fill-opacity:1;" d="M 83.882812 113.757812 L 97.382812 113.757812 L 97.382812 124.34375 L 83.882812 124.34375 Z M 83.882812 113.757812 "/>
<g style="fill:rgb(100%,0%,0%);fill-opacity:1;">
<use xlink:href="#glyph0-4" x="86.882812" y="122.835938"/>
</g>
<path style="fill:none;stroke-width:1.2;stroke-linecap:butt;stroke-linejoin:miter;stroke:rgb(0% ,0%,0%);stroke-opacity:1;stroke-miterlimit:10;" d="M 23.867188 131.378906 L 19.433594 112.851562 "/>
<path style="fill:none;stroke-width:1.2;stroke-linecap:butt;stroke-linejoin:miter;stroke:rgb(10 0%,0%,0%);stroke-opacity:1;stroke-miterlimit:10;" d="M 19.433594 112.851562 L 15 94.328125 "/>
<path style=" stroke:none;fill-rule:nonzero;fill:rgb(100%,100%,100%);fill-opacity:1;" d="M 0.980469 89.03125 L 29.019531 89.03125 L 29.019531 99.617188 L 0.980469 99.617188 Z M 0.980469 89.03125 "/>
<g style="fill:rgb(100%,0%,0%);fill-opacity:1;">
<use xlink:href="#glyph0-2" x="7.210938" y="98.109375"/>
<use xlink:href="#glyph0-4" x="15.710846" y="98.109375"/>
</g>
<path style=" stroke:none;fill-rule:nonzero;fill:rgb(100%,100%,100%);fill-opacity:1;" d="M 37.464844 204.238281 L 65.503906 204.238281 L 65.503906 214.824219 L 37.464844 214.824219 Z M 37.464844 204.238281 "/>
<g style="fill:rgb(100%,0%,0%);fill-opacity:1;">
<use xlink:href="#glyph0-2" x="43.695312" y="213.3125"/>
<use xlink:href="#glyph0-4" x="52.195221" y="213.3125"/>
</g>
<path style=" stroke:none;fill-rule:nonzero;fill:rgb(100%,100%,100%);fill-opacity:1;" d="M 120.316406 202.125 L 148.371094 202.125 L 148.371094 212.710938 L 120.316406 212.710938 Z M 120.316406 202.125 "/>
<g style="fill:rgb(100%,0%,0%);fill-opacity:1;">
<use xlink:href="#glyph0-4" x="126.550781" y="211.203125"/>
<use xlink:href="#glyph0-2" x="135.184586" y="211.203125"/>
</g>
</g>
</svg>
w3c validation report:
The uploaded document "adenosine.svg" was successfully checked as SVG 1.1+IRI, XHTML5+ARIA plus MathML 2.0 (experimental). This means that the resource in question identified itself as "SVG 1.1+IRI, XHTML5+ARIA plus MathML 2.0 (experimental)" and that we successfully performed a formal validation using an SGML, HTML5 and/or XML Parser(s) (depending on the markup language used).

If svg is not a reliable format for this purpose I need to use eps or ps or pdf as the format for the content.
SVG is "reliable", you just need to make it Illustrator SVG, which much to the chagrin of most users is a completely different thing than web-compliant SVG. Hence people use Inkscape as an intermediate workflow in such cases. If you simply save the file from AI, you can easily see what changes it makes and how it likes the formatting and entities so if you have control over the source code of your app, I don't see what would be the difficulty an adjusting it??? I mean, EPS and PDF won't negate that fact, either - to render correctly in AI, it needs to follow its somewhat odd way of handling some format specs. You could produce a PDF that is 100% perfect as per the spec, but it could still look like crap in AI, so I'm realyl not sure what you are trying to prove here...
Mylenium

Slow rendering compared to CS3

I'm sure this has been addressed somewhere in this forum already, but was hoping for any new suggestions.
In a nutshell..simple renders and exports to wmv/quicktime/ etc. of mostly :30 second clips, with not a lot of transistions or effects take an enormous amount of time. Frequently almost an hour in AME..same clips in 32 bit cs3 a couple of minutes. Longer times with maximum render quality checked, which I would expect. Any help appreciated. I'm wondering if Windows 7 might be a part of the problem, but have tried all the tricks to improve performance. I must be missing something..realize that the 4600 card is not Mercury enabled.
Thanks in advance.
Windows 7
Nvidia Quadro 4600
HP xw 9400
dual core 3.2GHZ
16 GB ram

CS5 has been optimized to use SSE4.1+ instruction sets to the max, much more that with CS3. Now this is guessing, because I just don't know the intricacies of CSx, but it may well be that optimizing that code can have negative effects on the performance of CPU's that don't fully support SSE, meaning AMD.
Second, the memory management has been seriously overhauled, and the result is that the page file is used to minimal degrees as long as it can be avoided, but the downside is that latencies when swapping from RAM to VRAM and vice versa increase.
Now, it all seems incredible that CS5 will be slower than CS3, but there are so many things going on under the 'hood', that it is hard to give a solid and understandable explanation. Maybe Steve can enlighten us a bit, but he pretty busy right now, so you may have to wait a bit.
FYI, not every new update or version is faster than previous ones. Sometimes the performance decreases because bugs were removed, stability improved, or other not directly discenrible features added.
Another thing you should not forget is that support for multiple formats has increased significantly, as has added functionality. These were induced by popular demand, but the downside is that it increases the overhead of the program, reducing responsiveness. IMO Adobe should now stop to add esoteric supported formats for mobile phones, mobile toilets, and other not video related gadgets and improve further on the basics. They have done a tremendous job with CS5 and I hope they continue in this way and not spend efforts to accept even more formats.

My vector drawings in illustrator cs3 look pixelated plz see screenshot

**** Notice the side of the girls hair its very serrated and somewhat blurry as well look down at her arm at the very bottom
I am using a mac os x version 10.5.8 and have been using Illustrator cs3 that I purchased for about 2 years and its never had this problem till now. I've just recently noticed a few days back that my vector drawings created in illustrator are looking serrated on the edges of my drawing, and this jagged serrated line goes all along the sides of the vector image and doesn't seem to go away when I zoom in or out......
And from what I know vector drawings created in illustrator can be resized and never pixelate but i don't know why its doing this.
I've searched online for all the possible remedies but nothing seems to get rid of that serrated line which makes my images look fuzzy on the sides.
I've made sure that I'm in preview and not pixel preview but that didn't work.
I went to my illustrator preferences to make sure that anti-aliasing is checked but that didn't seem to fix it either.
I went under the effects menu and clicked on Document Raster Effect Settings and changed that to 300ppi but that didn't do it either.
And also when I take my vector drawing from illustrator into photoshop, the serrated lines become more evident. I don't know what to do. The strange thing is that when i print the images out from my printer, the serrated edges don't show up.
But here's the thing: when I open up my past work that I created in illustrator when I wasn't having this problem, for some reason they are also now showing up with that serrated line on the edges, its really weird!!!!!
I've tried everything except for reinstalling the software, but just wanted to know if someone could help me before I tried this step or knew of something that might have gone wrong.
I also downloaded illustrator trial version cs5 today, and its doing the same thing as my illustrator cs3!!!!
Plz help!!!

I was experiencing the exact same thing in Illustrator CS5. There was a pixelated edge on a vector drawing that was showing up. At first I assumed it was an anti aliasing setting or pixel preview or document raster settings as you did. Then because all else failed I was about to assume it was a screen artifact or bug of some kind.
However, the upon further analysis I found the solution-and it was right under my nose. I had applied an effect to the vector object (an outer glow) and–because I was going to scale it down drastically from the size I had originally drawn it at –I had gone to the object menu and expanded the appearance of the object which caused my outer glow effect to become a rasterized shape underneath my original object.
To remedy this: I simply zoomed in on the pixlelated object, selected it, ungrouped it, selected the top vector object path, nudged it to the right–REVEALING THE RASTERIZED SHAPE BENEATH!
So I would reccomend you try two things:
First select the view menu and choose "Outline" (command or control Y), then look to see if you have any solid "blocks" -this could indicate a rasterizing of some sort has taken place underneath your vector objects. To get back to regular display just choose "overprint from the view menu.
Secondly, you could select the vector object that appears pixelated and then check in the "Appearance Panel" to see if an effect (such as a drop shadow or outer glow) has been applied ,possibly inadvertently. Because just the applying of an effect will cause a "pixelated, jaggy edge" when viewed at high zoom percentages, or indeed any resolution for that matter.
Hope this helps-

Webgui theme not rendering toolbar, does not look like SAPgui for Win

Hello all,
I just installed the ITS 6.20 Patch 20 and when I started the webgui service, the theme that was genereatd does not look like the SAPgui for Windows at all.
All I've got is a gray and blue color theme. The top row is the "SAP Easy Access" header and on the next row are just simple square buttons (Menu, Tools, User Menu, SAP Menu, etc.).
What do I have to do to enable the "richer" look-and-feel like the SAPgui for Windows 6.20? I'm looking to get the toolbar with the paging icons, disk icon, goback, etc.
Thanks,
Mike

Oliver,
You have to disable the Enjoy SAP option.
1. Log in to the Admin service;
2. Open the Configuration | General settings for the ITS instance;
3. Remove the checkmark for the "Enjoy Design" option.
4. Save and restart.
Does this help?
Mike

WMV Rendering problems happened out of nowhere

I've had no problems with AE before. I'm using a photo slideshow template with some nice transitions and effects. Worked just fine when I exported it to WMV for months. In fact I've rendered the same eact file several times. However I wanted to make one final picture change and now all of a sudden when I render it to WMV, the footage is slow, choppy and very distorted. I tried rendering it to Quicktime and it seemed to work. So did H.264 but it was low quality.
I even opened up other AE projects and they all now render choppy, distorted video when output to WMV (it never did that before!). Not sure what happened because I didn't change anything in the settings at all. I've even tried uninstalling and re-installing, and it still renders out the same slow, choppy, distored video for WMV. I'm at a complete loss!
Please help

Either a Windows Update changed some Media Player components or you updated/ changed the graphics driver. Verify the files on another system. If they play fine there, then investigate these things on your own system.
Mylenium

Rendered Nodes in JTree, Look&Feel Problem

Hallo,
I make a small JTree and write my own TreeNodeRenderer which renders in each case a simple JPanel with Titled-Border an 2 JLabels.
If I adjust Metal Look&Feel the rendered Nodes are displayed correctly. (The JPanels size is about 300x200 pixels)
With other L&Fs (windows, motif, plastic from jgoodies) there is only the title of the TitledBorder displayed.
I meet the Problem as i programmed a more complicated JTree with rendered TreeNodes.
Do you know the problem and a solution? I don't want to setting up Metal look for my application.
The following link contains the source of the example in an executable jar file:
http://home.arcor.de/Thomas-Pfaff/treetest.jar
thanks for all answers

I found the answer of my question....
http://onesearch.sun.com/search/clickthru?qt=TreeCellRenderer&url=http%3A%2F%2Fbugs.sun.com%2Fbugdatabase%2Fview_bug.do%3Fbug_id%3D4656280&pathInfo=%2Fonesearch%2Findex.jsp&hitNum=1&col=support-all

Why does the menu look grayed out? ("File, Edit, View, History" etc) It makes them look like they are not going to work. They don't turn black if I click on them either.

Normally, at least in most Windows programs, and I think other OSes too, items that can be used are black, and items in gray are inactive so that they are not available. It's disconcerting to see the menu in gray, even though they work.

Hi Melaniefromnorth saanich,
Take a look at the Photos User Manual below. Is it possible you were deleting photos from an album and not from your library?
Delete photos and video - Photos Help
https://help.apple.com/photos/mac/1.0/index.html#/pht3bfab2f96
Delete photos and videos
Do one of the following:
Delete a photo from an album, but not from your library: Select the items you want to delete, then press Delete.
Delete a photo from a moment (placing it in the Recently Deleted album): Select the items you want to delete, press Delete, then click Delete.
Delete a photo from a moment or album (placing it in the Recently Deleted album): Select the items you want to delete, then press Command-Delete.
Deleted photos and video aren’t immediately removed from your library; they’re placed in the Recently Deleted album, where they remain for the number of days shown, and then are deleted. You can recover the items before that period of time (see the next task). If you have iCloud Photo Library turned on, the photos may remain in iCloud up to 40 days and then are removed from all your devices that use iCloud Photo Library. If you’re not using iCloud Photo Library, your deleted photos are removed from your Mac only.
Restore recently deleted items
Deleted items remain in the Recently Deleted album for the number of days shown, and then are deleted permanently. You can view recently deleted items and restore them back into your Photos library.
Choose File > Show Recently Deleted.
Select the photos you want to restore.
Click Recover.
To delete recently deleted items immediately, select the items, then click Delete.
If you use Time Machine to back up your computer, you may be able to recover items after they are deleted permanently from your Mac or iCloud.
For more information on using Time Machine, see Restore a Photos library from a Time Machine backup.
Hope that helps,
- Judy

Hardware Rendering=broken preview (CS3)

Hey guys, im new to the forums, but I've recently encountered some strange behavior. I used to have dual monitors setup but only used one in bridge(didnt use the other for previews) and i was able to use hardware rendering just fine. Then i moved and i left the second monitor off and then images started displaying in a weird section of the preview pane, and part of it is translucent.
I enabled software rendering and it fixed the issue(as per in the support site, it said dual monitors can cause this) but the rendering is a bit slow.
How can i get it back working like it used to with hardware rendering?
Computer is:
Athlon 64 x2 6000+(3.01~ghz)
4gb DDR2 667
512 DDR3 Vram(ATI Radeon HD 3850 chip, with recently updated driver)
1tb WD Barracuda boot/cs3 installed on
640GB WD Green Scratch disk
Thanks in advance
-Josh

This is a hardware issue from the video card or driver. You say you updated the driver and if this this the latest one prehaps the old one you had worked better. Migtht try rolling back to the version where it worked. If this does not work you might have to replace the video card for something faster.

Rendering advice in CS3

I have sort of an obscure question. I'm about to submit a feature length animated film to a film festival. They use Withoutabox to upload the film submissions so they can review them. I'm filling out a lengthy submission package right now and am waiting on some information to finish it. I have yet to find any details though on what the file size restrictions are for the digital copy I'm going to upload. I have a feeling the digital version I have on my desktop right now will be too big so I'm looking ahead for advice on what render setting I should use to get a decent quality film with a small file size. Quality is important obviously cuz this is the version that it will be judged by...but I also need to be able to upload it without blowing up their server lol.
I realize this is an odd question to ask when I don't yet know exactly how big or small the file needs to be but I previously had a lot of rendering trouble that wasted a lot of time and I don't have the time before the deadline to waste on rendering trials and errors. If I find out I do indeed need to rerender it I wanna be able to try it ASAP and I'd like to know my best options.

Do they say what frame size they want? If it's suitable for iPod or iPhone or other mobile device, you can use H.264 with a bit rate around 1.5 Mbps (like Apple does). If you need full HD at 1920x1080 then you'll need Blu-ray type bit rates of about 20 - 25 Mbps (or higher).
Obviously, 2 hours of feature film at 1.5 Mbps will be a much easier file to move around than one created at 25 Mbps.
NB: Bit rate and duration are the only factors that affect file size. Frame size doesn't affect it at all. The only thing frame size affects is whether a particular bit rate will look good or not.
Jeff

Another vote for restoring H.264 and WMV rendering support

Hello!
I love the new features which have been added to Adobe CC 2014.
However, removing the ability to render H.264 (MP4) or WMV essentially makes the program useless for me.
Adding AME to the workflow process is a considerable time-waster.
If anything, I'd think new program versions would add support for more render formats, not remove them?
If you could add H.264 and WMV support back in, I'd really appreciate it?
Thanks.

XDude.com! wrote:
Hello!
I love the new features which have been added to Adobe CC 2014.
However, removing the ability to render H.264 (MP4) or WMV essentially makes the program useless for me.
Adding AME to the workflow process is a considerable time-waster.
If anything, I'd think new program versions would add support for more render formats, not remove them?
If you could add H.264 and WMV support back in, I'd really appreciate it? Thanks.
I think if you run side-by-side tests using AME and transcoding while the render is taking place you'd see the AME route is actually slightly faster.
But there is a far more compelling reason for the functions to have been separated and that has to do with how After Effects is used by most, not all, of its intended audience. Comps and effects sequences are expected to be pieces of larger projects and not necessarily to be self-contained clips. From a production workflow, having the full rez version of an AE project on a drive and then using it in a transcoder like AME or Compressor to export many different codecs at once is far more efficient. But only for one reason: I have the master AE clip and can do anything with it. If I export directly out of AE to, say H.264, I cannot use that clip directly in most of the other applications my AE clips go through on their way to release.
The perceived convenience of being able to go directly to H.264 from AE is not really rendering, it's a process of transcoding. And that's complicated by the number of adjustments available to any codec's processor, adjustments that will dramatically affect the compressed file's appearance and size.

WMV rendered in AE-CS3 looks gray in PowerPoint 2007

Similar Messages

Maybe you are looking for