Bug in CS4???

Seems like there is a problem with ScriptArgs and UTF-8 in IDS4. Because it does not handle UTF-8. Norwegian characters, and alle other non standard seems to not work. Did the same thing with IDS3 and there it worked. Is this a bug?

Please note that the thread: http://forums.adobe.com/thread/482342 contains more information.
But in short I am experincing lack of extended characters on a Windows Vista (and on win 2003) with IDS CS4 6.0.3.557. The webservice call contains utf-8 encoding of character "æ" (is in hex: C3 83) , but the string read by indesign javascript contains wrong characterencoding = "<6d3f>"
regards Peter

Similar Messages

Placed PDF made in Quark bug, InDesign CS4 XP

Hi,
I've just been bitten by the bug that causes characters to drop out when you create a PDF from an InDesign CS4 document that has a placed PDF made in Quark.
Has it been resolved? I looked at the update notes to 6.0.2 and 6.0.3 and couldn't see anything about it.
This is fairly urgent for me. If it hasn't been resolved, are there any workarounds?
Thank you,
Ariel

You may be right... but it didn't seem relevant at the time, since I rarely receive Quark files, so I probably phased out.
Anyway, the 6.0.2 for InDesign CS4ME does not fix the issue. I thought it might. And what a story it was to upgrade (which I just did this evening). Apparently, the 6.0.2 upgrade only works for a later build of IDCS4 (something like 6.0.0.421). I had the earlier build (something like 6.0.0.270). And the only solution was to completely uninstall InDesign, download the latest Demo on the Winsoft site (800MB. Took me around 2 hours). Install that. Then download the update and install that as well.
And it didn't even fix the issue!
The only positive side is that all my preferences survived the trauma intact!
Ariel

Wow! Major bugs in CS4

I just finally upgraded to DW CS4 and found some very surprising bugs. My computer is brand new running Win 7, so the bugs are pretty much confirmed.
1. to switch and image source, when i double click on the image in design view, and select another image file in the window, nothing happens. the old image is not replaced.
2. when i insert a new div layer, in the div popup box, i select a class, but no matter what i choose it always selects the first class name in the list. i have to go back in a second time and choose the class and that works.
3. when setting up a new site, i click on the folder icon to select my root folder, navigate to the folder, select it, but my site folder never shows up in folder path. it stops at the main folder on my pc. for example, it should be "C:\Users\Me\Main Folder\Site Folder", but instead it shows "C:\Users\Me\Main Folder\". i have to manually type in the sites folder on the end. now this works fine for the images folder, just not root.
i have searched quite a bit and haven't found much on these bugs, so people must just be living with them and chalking it up to Adobe typical bugs.
these are pretty big issues and if Adobe is going to continue to produce buggy software, they should lower their prices.
if anyone has any hacks to fix these bugs, i would appreciate it.
thanks in advance.

dsmflash wrote:
On my pc with vista in CS3, you opened the root folder and hit select, and that set it as root. now you have to go one folder beyond, which makes no sense...but hey, its Adobe.
You obviously didn't bother with keeping Vista up to date. This problem exists in all versions of Dreamweaver (not just CS4) in Windows 7, Vista SP3, and whatever the latest SP version of XP is.
It's a pity Adobe hasn't posted a patch for it, but the problem was triggered by a change in Windows.

Spacebar Scrolling Bug/Feature - CS4

Hi guys, recently upgraded to CS4 - loving it, so far - but I have come across a feature/possibly a bug that I'd like to switch off.
The best way I can explain it is this: When I have a tool selected, pressing the spacebar + another tool's hotkey (ie, if I have Magic Wand selected, pressing Spacebar + B, or, if I have Brush selected, pressing Spacebar + W) and then dragging the mouse causes the picture to zoom out a little ways, and pan with the spacebar.
I often accidentally press these button combinations while trying to pan around and change tools at the same time, and it's quite annoying when the panning throws me off. I took a look in preferences, but couldn't find anything to do with this, nor could I find a shortcut I could disable (since spacebar is not allowed in shortcuts).
I just updated to 11.0.1, and the zoom thing is still happening.
Any suggestions? Thanks.

Dhakkel wrote:
I often accidentally press these button combinations while trying to pan around and change tools at the same time, and it's quite annoying when the panning throws me off.
If you must change tools in mid-pan, try disabling Flick Panning in Preferences > General.

CS4: Editable Region locked in design view - weird bug in CS4?

Hi,
I've the following issue to report: My template based webpages contain 3 editable regions. One of them (cText_m0) refuses editing in desgin view though it's editable (colored code) in code-view. Neither ALT+click nor doubleclick helps.
URL of one of the pages afflicted: http://www.schule.suedtirol.it/Lasis/r3.htm
The problem did not occur in DW-Versions minor to CS4.
Is there an issue with the page or with DW CS4?
Thanks for helping me.
Regards
Harald Angerer

On Fri, 3 Apr 2009 09:29:57 +0000 (UTC), "Janine_Trumel"
<[email protected]> wrote:
> Sorry, I cant quite see why the first line of code is
causing the problem.
Regarding the XML declaration that Nancy suggested omitting,
the XHTML
specs suggest using the line, but it is not required if the
page uses
either UTF-8 or UTF-16 character encoding. See
http://www.w3.org/TR/xhtml1/#strict
where is says in part, "An XML
declaration is not required in all XML documents; however
XHTML document
authors are strongly encouraged to use XML declarations in
all their
documents. Such a declaration is required when the character
encoding of
the document is other than the default UTF-8 or UTF-16 and no
encoding was
determined by a higher-level protocol."
IE only pays attention to the DOCTYPE if it is the very first
thing in the
page. Put anything before the doctype and IE will drop to
quirks mode.
That's just an IE bug that you'll have to live with.
Gary

Colour Profile Bug in CS4 32 bpc Mode?

This has been confirmed on both Mac and PC by different users
(this topic was confirmed on another list before posting here).
One may be working on an image that has a different colour profile
than set as default in colour settings. For example, colour settings
has Adobe RGB while the current document is in ProPhoto RGB. If the
ProPhoto RGB (16 bpc) file is taken to 32 bpc mode, the status message
reports that the file is in a modified linear space based on the input
profile. One may then perform USM, for example and then return to 16
bpc or 8 bpc mode.
Here is the bug: Once the ProPhoto RGB file is returned to 16 or 8
bpc, it now has the working RGB space tagged of Adobe RGB, rather than
the original ProPhoto RGB as input before 32 bpc conversion. This is
not just a tagging issue, the numbers have been converted to working
RGB rather than the input ICC that was tagged to the image prior to
entering 32 bpc mode.
ICC tagged image operations have been divorced from colour settings
since version 6, the document can reside in a space that is
independent of colour settings. I can't recall other operations that
change the files colour space and tag without user intention.
If using 32 bpc edits, to preserve the input space, one either has to
change their colour settings to match the document or convert the
document to working RGB.
So why this reversion to working RGB and not the document RGB - bug or
design feature/limitation? Did CS3 work this way, is it only my
version of CS4?
I have searched the help notes, this forum and other Adobe support docs,
however I could not find this issue documented.
Sincerely,
Stephen Marsh

Can anyone post a supporting argument for the current behaviour (design or bug). While in 32 bpc Photoshop "knows" what the original profile is (it is listed as being in a linear state), while on default conversion to lower bit depth the data is converted to working RGB, rather than the document RGB prior to conversion (if different to working RGB). Am I missing something - is this a good thing, should this be behaviour be changed?
OK, topic drift it is!
Buko/progress, it is not so much bit depth in this case, it is gamma encoding - or lack thereof. 32 bpc mode processes in linear gamma, which can have an effect on some operations for certain receptive image content (tonal moves, USM, interpolation etc).
As one example, some links to linear resampling can be found in the comments at this blog:
http://forensicphotoshop.blogspot.com/2008/11/resize-smaller-part-2.html
I prefer the 32 bpc route to linear processing rather than the alternative, which is 16 bpc and a hacked custom RGB profile set to gamma 1.0.
I don't like linear USM for output sharpening (nasty dark halo artifacts). However, for subtle capture/acquisition sharpening linear USM may be preferred for certain images. I generally sharpen with blend if sliders limiting the intensity of the light halo, which comes close to one aspect of linear sharpening (light halo reduction). This can also be achieved by blending the USM in two separate layers, set to darken and lighten blending with reduced opacity.
While on USM and gamma, there are some L* based RGB working spaces such as L*RGB or the new ECI RGB which behave the same way as Lab mode Lightness channel sharpening (when set to Luminosity blend). As the response of the Lightness channel is different to linear gamma and standard gamma encoded spaces, for some image content one may be preferred over the other as the processing space.
I would still like to explore the original topic/post before submitting a bug report. How do you think things should work?
Regards,
Stephen Marsh

Click button applescript statement bug in CS4?

I tried to GUI script the Photoshop CS4. Click button statement does not work for me on any of Photoshop CS4 dialogs.
Here is an example script:
tell application "Adobe Photoshop CS4"
    activate
end tell
tell application "System Events"
    tell process "Adobe Photoshop CS4"
        click menu item "New..." of menu "File" of menu bar item "File" of menu bar 1
        delay 1
        click button "Cancel" of window "New"
    end tell
end tell
The same script works perfectly in CS6, but not working in CS4. Is it a known issue?
Thank you.

GeorgePowell,
> Yeh I have already done that. The whole button has the
instance
> name "button", have you downloaded the fla to see for
your self?
I downloaded your file and am able to reproduce the error
message you're
seeing. I'll have to dig into it more to determine what's
going on, but it
*might* be something related to the way CS4 handles "Export
in first frame"
in the component's properties dialog box.
Interestingly, I can save your file for CS3, open it in
Flash CS3, and
compile it just fine ... so it would appear that you might
indeed have
discovered a CS4-specific bug. I'll get in touch with someone
on the Adobe
Flash team today and share this file.
In the mean time, you can still experiment with the
principle of moving
from scene to scene -- as long as you don't use a component.
Instead, draw
a quick shape, convert it to a button symbol, and swap out
your component
button for the button symbol in both scenes. Make sure your
instance names
are in place, and it should work just fine for you (it does
for me with your
file).
David Stiller
Co-author, Foundation Flash CS4 for Designers
http://tinyurl.com/5j55cv
"Luck is the residue of good design."

Restrict Access behaviour still has redirect bug in CS4

I have just upgraded to Dreamweaver CS4 and see that there is still a PHP error in the code for this behaviour, which if used out of the box will never redirect authorised users to the page they came from.
The lines which read:
if (isset($QUERY_STRING) && strlen($QUERY_STRING) > 0)
$MM_referrer .= "?" . $QUERY_STRING;
Should be:
if (isset($_SERVER['QUERY_STRING']) && strlen($_SERVER['QUERY_STRING']) > 0)
$MM_referrer .= "?" . $_SERVER['QUERY_STRING'];
Does Adobe have any plans to correct this old bug?
Ed

I reported the bug to Adobe some time ago, and understand that it will be fixed in the next release.
You can fix it easily yourself by editing lines 43 and 44 of RestrictAccess_main.edml:
if (isset($QUERY_STRING) && strlen($QUERY_STRING) > 0)
$MM_referrer .= "?" . $QUERY_STRING;
In Windows, the file is located in C:\Program Files\Adobe\Adobe Dreamweaver CS4\configuration\ServerBehaviors\PHP_MySQL. It's in the same location in the Applications folder on a Mac.

Bug Illustrator CS4 module Geometry.aip

Bonjour,
Depuis 2 jours, j'ai un bug sous Illustrator CS4 car il me met une alerte au lancement indiquant qu'il n'arrive pas à charger le module geometry.aip et donc je ne peux pas dessiner de carré ou de rond. J'ai essayé de mettre à jour la suite Adobe mais le problème perdure.
Quelqu'un a t il une idée ?
Merci

You have to provide system information and otehr details. Modulkes/ plug-ins not loading usually depends on external influences such as the install being damaged, virus scanners blocking files, permissions issues and an assortment of otehr potential problems...
Mylenium

Weird font bug in CS4 with 321impact

Hi,
Being using the font 321Impact for a lot of work in Photoshop etc. works fine. Just come to use the font in InDesign (cs4) but
when ever I type words like 'confidence' or 'finding' the f and i characters disappear! This only happens with the letter combination
fi and fl - this is driving me nuts! The font works perfectly well in everything else and the characters don't disppear. I thought it
was a display issue, but the characters print out missing. Instead of 'confidence' it comes out 'con dence' with the letters missing.
Here's the link to the font:
http://www.fontstock.net/15103/321impact.html
Has anyone one else had a similar problem and knows how to fix it!
Many thanks in advance

The font has no ligature support apparently. Turn them off.
Bob

BUG IN CS4 API

Just wanted to let everyone know. The StandardGetDirectoryDialog function in the sADMBasic suite does not function correctly. Adobe confirmed this to me when I filed a help request with them.
Right now it just gives you back "parent-of-directory-you-asked-for/garbage".
Anyone else notice this? Anyone got a work-around? Happy coding!
-Bill

UPDATE!!!! BUG ONLY ON MAC SIDE!
I left out something really important. The bug is only on the MAC side. The call to the StandardGetDirectoryDialgog WORKS on the WINDOWS, but does NOT WORK for the MAC. Sorry! Important bit of information left out there.
It doesn't look like I can edit the subject line to include this information. Bummer.

Really big stupid bug in CS4!

Try this:
1. Open a image with one and only background layer.
2. Duplicate this layer.
3. Go to the duplicated layer.
4. Hold down SHIFT and doubleclick on the image with the cursor tool.
This will crash photoshop CS4 with latest update. I think CS4 is released to early.

I dont think so. Here is the report:
Date/Time: 2009-02-25 16:01:44.592 +0100
OS Version: 10.4.11 (Build 8S165)
Report Version: 4
Command: Adobe Photoshop CS4
Path: /Applications/Adobe Photoshop CS4/Adobe Photoshop CS4.app/Contents/MacOS/Adobe Photoshop CS4
Parent: WindowServer [109]
Version: 11.0.1 (11.0.1x20090216 [20090216.r.522 2009/02/16:17:00:00 cutoff; r branch]) (11.0.1)
PID: 947
Thread: 0
Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_INVALID_ADDRESS (0x0001) at 0x73c00000
Thread 0 Crashed:
0 <<00000000>> 0x73c00000 0 + 1941962752
1 com.adobe.Photoshop 0x00315264 0x1000 + 3228260
2 SH2Selective.8li 0x12782074 Filter__14cPSEventFilterFUlP5_ADsclPv + 676
3 com.adobe.Photoshop 0x002d7c78 0x1000 + 2976888
4 com.adobe.Photoshop 0x0008ed0c 0x1000 + 580876
5 com.adobe.Photoshop 0x0008b998 0x1000 + 567704
6 com.adobe.Photoshop 0x0007fab4 0x1000 + 518836
7 com.adobe.Photoshop 0x000828d4 0x1000 + 530644
8 com.adobe.Photoshop 0x00082b58 0x1000 + 531288
9 com.adobe.Photoshop 0x00845010 0x1000 + 8667152
10 com.adobe.Photoshop 0x0007fe5c 0x1000 + 519772
11 com.adobe.Photoshop 0x002c26d8 0x1000 + 2889432
12 com.adobe.Photoshop 0x002c2b10 0x1000 + 2890512
13 com.adobe.Photoshop 0x00003d7c 0x1000 + 11644
14 com.adobe.Photoshop 0x00003a80 0x1000 + 10880
Thread 1:
0 libSystem.B.dylib 0x9003248c wait4 + 12
1 com.apple.Foundation 0x92be378c _waitForTermination + 40
2 libSystem.B.dylib 0x9002b908 _pthread_body + 96
Thread 2:
0 libSystem.B.dylib 0x9002bfc8 semaphore_wait_signal_trap + 8
1 libSystem.B.dylib 0x90030aac pthread_cond_wait + 480
2 com.adobe.amt.services 0x0991ef58 AMTConditionLock::LockWhenCondition(int) + 56
3 com.adobe.amt.services 0x09919b70 AMTThreadedPCDService::PCDThreadWorker(_AMTThreadedPCDService*) + 104
4 com.adobe.amt.services 0x0991effc AMTThread::Worker(void*) + 48
5 libSystem.B.dylib 0x9002b908 _pthread_body + 96
Thread 3:
0 libSystem.B.dylib 0x9000af48 mach_msg_trap + 8
1 libSystem.B.dylib 0x9000ae9c mach_msg + 60
2 ...ple.CoreServices.CarbonCore 0x90baaa48 TS_exception_listener_thread + 112
3 libSystem.B.dylib 0x9002b908 _pthread_body + 96
Thread 4:
0 libSystem.B.dylib 0x9002bfc8 semaphore_wait_signal_trap + 8
1 libSystem.B.dylib 0x90030aac pthread_cond_wait + 480
2 ...ple.CoreServices.CarbonCore 0x90c04484 MPWaitOnSemaphore + 184
3 MultiProcessor Support 0x0c967a8c dyld_stub_strcmp + 210933580
4 ...ple.CoreServices.CarbonCore 0x90bc6734 PrivateMPEntryPoint + 76
5 libSystem.B.dylib 0x9002b908 _pthread_body + 96
Thread 5:
0 libSystem.B.dylib 0x9002bfc8 semaphore_wait_signal_trap + 8
1 libSystem.B.dylib 0x90030aac pthread_cond_wait + 480
2 ...ple.CoreServices.CarbonCore 0x90bc6924 MPWaitOnQueue + 224
3 AdobeACE 0x02632a8c dyld_stub_sqrtf + 39235724
4 AdobeACE 0x02632410 dyld_stub_sqrtf + 39234064
5 ...ple.CoreServices.CarbonCore 0x90bc6734 PrivateMPEntryPoint + 76
6 libSystem.B.dylib 0x9002b908 _pthread_body + 96
Thread 6:
0 libSystem.B.dylib 0x90040df8 mach_wait_until + 8
1 libSystem.B.dylib 0x90040bc4 nanosleep + 388
2 com.adobe.PSAutomate 0x1db6312c ScObjects::Thread::sleep(unsigned) + 144
3 com.adobe.PSAutomate 0x1db63234 ScObjects::Thread::wait(unsigned) + 56
4 com.adobe.PSAutomate 0x1db51818 ScObjects::BridgeTalkThread::run() + 436
5 com.adobe.PSAutomate 0x1db635d4 ScObjects::Thread::go(void*) + 316
6 libSystem.B.dylib 0x9002b908 _pthread_body + 96
Thread 0 crashed with PPC Thread State 64:
srr0: 0x0000000073c00000 srr1: 0x100000000000d030 vrsave: 0x0000000000000000
cr: 0x44004204 xer: 0x0000000000000000 lr: 0x00000000002e381c ctr: 0x0000000073c00002
r0: 0x00000000002e380c r1: 0x00000000bffff210 r2: 0x0000000000182f9c r3: 0x0000000000750072
r4: 0x000000001ef683a0 r5: 0x0000000000000000 r6: 0x0000000000000000 r7: 0x0000000000000000
r8: 0x000000001efcd6b0 r9: 0x0000000000000500 r10: 0x0000000090bb0584 r11: 0x00000000bffff1e0
r12: 0x0000000073c00002 r13: 0x0000000000000000 r14: 0x0000000000000000 r15: 0x0000000000000000
r16: 0x0000000000000000 r17: 0x0000000000000000 r18: 0x0000000000000000 r19: 0x0000000000000000
r20: 0x00000000bffff63c r21: 0x0000000005672980 r22: 0x0000000094cbdedc r23: 0x0000000000000001
r24: 0x00000000bffff650 r25: 0x000000000d1ddf18 r26: 0x00000000736c6374 r27: 0x0000000000000ee0
r28: 0x000000000d1dded8 r29: 0x000000000d1dde70 r30: 0x00000000bffff2fc r31: 0x0000000000000500
Binary Images Description:
0x1000 - 0x1e00fff com.adobe.Photoshop 11.0.1 (11.0.1x20090216 [20090216.r.522 2009/02/16:17:00:00 cutoff; r branch]) (11.0.1) /Applications/Adobe Photoshop CS4/Adobe Photoshop CS4.app/Contents/MacOS/Adobe Photoshop CS4
0x2453000 - 0x24bdfff AdobeXMP /Applications/Adobe Photoshop CS4/Adobe Photoshop CS4.app/Contents/Frameworks/AdobeXMP.framework/Versions/A/AdobeXMP
0x24cb000 - 0x24e8fff AdobeBIB /Applications/Adobe Photoshop CS4/Adobe Photoshop CS4.app/Contents/Frameworks/AdobeBIB.framework/Versions/A/AdobeBIB
0x24f1000 - 0x24f6fff com.adobe.AdobeCrashReporter 2.5 (3.0.20080806) /Applications/Adobe Photoshop CS4/Adobe Photoshop CS4.app/Contents/Frameworks/AdobeCrashReporter.framework/Versions/A/AdobeCrashReporter
0x2605000 - 0x2707fff AdobeACE /Applications/Adobe Photoshop CS4/Adobe Photoshop CS4.app/Contents/Frameworks/AdobeACE.framework/Versions/A/AdobeACE
0x2722000 - 0x2744fff AdobeBIBUtils /Applications/Adobe Photoshop CS4/Adobe Photoshop CS4.app/Contents/Frameworks/AdobeBIBUtils.framework/Versions/A/AdobeBIBUtils
0x2750000 - 0x276ffff AdobePDFSettings /Applications/Adobe Photoshop CS4/Adobe Photoshop CS4.app/Contents/Frameworks/AdobePDFSettings.framework/Versions/A/AdobePDFSettings
0x2787000 - 0x27aefff AdobeAXE8SharedExpat /Applications/Adobe Photoshop CS4/Adobe Photoshop CS4.app/Contents/Frameworks/AdobeAXE8SharedExpat.framework/Versions/A/AdobeAXE8SharedExpa t
0x27be000 - 0x27d9fff libicudata.dylib.36.0 /Applications/Adobe Photoshop CS4/Adobe Photoshop CS4.app/Contents/Frameworks/ICUData.framework/Versions/3.6/libicudata.dylib.36.0
0x27dc000 - 0x27f1fff com.adobe.LogTransport 1.0 /Applications/Adobe Photoshop CS4/Adobe Photoshop CS4.app/Contents/Frameworks/LogTransport.framework/Versions/A/LogTransport
0x3008000 - 0x3430fff com.adobe.linguistic.LinguisticManager 4.0.0 (7863) /Applications/Adobe Photoshop CS4/Adobe Photoshop CS4.app/Contents/Frameworks/AdobeLinguistic.framework/Versions/3/AdobeLinguistic
0x34e0000 - 0x36d6fff AdobeOwl /Applications/Adobe Photoshop CS4/Adobe Photoshop CS4.app/Contents/Frameworks/AdobeOwl.framework/Versions/A/AdobeOwl
0x3747000 - 0x3b37fff AdobeMPS /Applications/Adobe Photoshop CS4/Adobe Photoshop CS4.app/Contents/Frameworks/AdobeMPS.framework/Versions/A/AdobeMPS
0x3bc0000 - 0x3ec7fff AdobeAGM /Applications/Adobe Photoshop CS4/Adobe Photoshop CS4.app/Contents/Frameworks/AdobeAGM.framework/Versions/A/AdobeAGM
0x3f7a000 - 0x4211fff AdobeCoolType /Applications/Adobe Photoshop CS4/Adobe Photoshop CS4.app/Contents/Frameworks/AdobeCoolType.framework/Versions/A/AdobeCoolType
0x428d000 - 0x4327fff libicucnv.dylib.36.0 /Applications/Adobe Photoshop CS4/Adobe Photoshop CS4.app/Contents/Frameworks/ICUConverter.framework/Versions/3.6/libicucnv.dylib.36.0
0x4353000 - 0x4

Display Bug in CS4: Gaping Rectangular Holes in the Image

I first discovered this problem when I would open a psd file in Photoshop that I had worked on in Painter 11. There would frequently be, although not always, a large rectangular "bite": an area of the image that was empty, and through which you could see the transparency grid. To further confuse the issue, the hole would either appear, or disappear, at various levels of magnification. Sometimes saving the file as a copy, closing the original, and re-opening the copy would get rid of the hole. Sometimes not.
Initially, I thought this was a Painter bug, because that is consistently how I became aware of it. Now I am not so sure, since it happened today to a file I don't think I ever used in Painter.
Then I entertained the possibility that it might be a graphics card issue, except that it never happens anywhere outside of Photoshop.
Does anyone have a clue? I would be eternally grateful for some clarity.

I just opened a bunch of files with no problem after disabling Open GL.
That just might be the answer. I am keeping my fingers crossed.
THANK YOU.

Possible Bug in CS4 Extended 3D Axis Widget Rotate?

I wrapped a transparent background PNG text image around the sphere, used a mask to subtract the sphere leaving me with a nice "circular" text on a transparent backdrop.
Next, I want to rotate this 360 degrees on the Z axis in the 10 second default timeline with keyframe to log the rotation so I can output single PNG frames. The rotation would be as if the text were painted around a rotating globe which was "tilted" at about 30 degrees, but without the globe.
I can use the manual 3D tools to achieve this, but I can't do it without excessive XY axis "wobble." I can use the 3D Axis Widget to rotate the text perfectly, not only 360 degrees but 720 or 1440, etc. The problem is that when I use the 3D Axis Widget (which allows me to rotate the text without a trace of XY axis wobble), the keyframe doesn't log or record it properly. It's as if only a few degrees of rotation are actually recorded.
Am I missing something, or could this be a bug??
Any help appreciated.....
Best regards,
Lin

i'm having the same problem here.. running on CS5 Extended.. the 3D Axis, Ground Plane, etc are all greyed out.. 3D -> New Shape From Layer won't give me the 3D Axis and the rendered subject looks 2D.. i've tried all Basic, Normal & Advanced settings but to no avail.. i even updated my graphics driver to the latest driver but still the same...
my specs,
Intel Core i5 2410-M
2GB nVidia GT540M
4GB of DDR3 RAM
i doubt that my graphics card can't handle the 3D rendering, as the updated driver addressed the 3D support for Photoshop CS5.... plz help.. thanx..

Tool panel position bug in CS4

Is any one able to move the tool panel, and then upon reopening PPro, have it where you put it last? I usually like mine on the left side of the timeline, but it's always right under the audio meter when I open PPro, no matter where I put it last. I even created a custom workspace, but it does the same thing.
I know it's a small thing, but to me it's just a bit annoying. Everything else about CS4 is looking good!

Moving the panel does not mark your project as modified, however if you deliberately save your project after moving the panel then it will be where you put it when you re-open your project.
Cheers
Eddie
PremiereProPedia (
RSS feed)
- Over 300 frequently answered questions
- Over 250 free tutorials
- Maintained by editors like
you
Forum FAQ

Bug in CS4???

Similar Messages

Maybe you are looking for