Leopard - CS3 - Interface/Gamma issue

Hello there, switched to 10.5(.4) on a MacPro today and now check this out, it's only in Photoshop. Illy and Indesign and Bridge are fine. No other applications are affected.
If you profile/calibrate your display (with professional software) to Gamma L* - darkish, grey boxes appear in the Photoshop dialogue windows.
http://img297.imageshack.us/my.php?image=leopardphotoshop11zg0.png
If you use Gamma 1.8, the Apple default, Photoshop looks perfekt. With Gamma 2.2 they're barely noticable (pretty much only if you know they're there).
All the other settings you can choose like temperature, luminance, chromatic adaption, profile-type etc. don't influence Photoshop-windows in this way - but as soon as you change the gamma those boxes appear.
I would very much like to know how you guys deal with it - do you profile your display to 1.8/2.2 OR do you use L* and live with the boxes OR have you profiled your display properly but you don't have this nuisance? (!?)
Any help/info would be greatly appreciated.

b So here's what I think happens (+ my idea to solve the grey-boxes issue):
Some applications use the monitor-profile to draw their interface. Like Photoshop and Graphic Converter. (The only 2 I've installed, I'm sure some video-editing-applications, even players are concerned that's maybe the reason some people think it's 'random'). I think these apps do so to immediately can reflect a change in the profile, without restart.
Now Mac OS X Leopard seems to not allow these applications to do so in certain parts of the interface. (Must be a new feature!) The window itself is drawn by the OS. That's the reason only elements like the text and buttons are affected.
And the problem is that the OS uses its 'Generic RGB Profile.icc' which contains Gamma 1.8. So if you calibrate your display with Gamma L* (which you really should do and most profiling-software does by default) those grey boxes appear in said applications.
The solution is easy. Replace the system-rgb-profile with one that supports L* - like the eciRGB profiles.
To do so you have to rename the .icc file in finder but also edit the information inside (which can be done with the ColorSync Utility). Then copy it to the System/Library/ColorSync/Profiles folder.
After that the grey boxes dissapear and everything is back to normal. There's some difference in the tabular data like the CMM and a chroma-entry, so you might want to re-write your display-profile just to make sure everything's alright.
I haven't seen anything yet but could imagine that the rendering of webpages in safari might be affected. Or rather some webbrowsers' without colour management. (I'm just guessing.)
b Problem 1:
Some Adobe apps can see that the current system-profile is identical to your working-space-rgb and reset your rgb-choice to the Generic RGB profile after a restart. (Without changing the 'Colormanagement SYNC'd icon/setting.) This probably could cause trouble if you export or open files.
b Solution:
Use a different profile for your system than your Adobe-RGB setting. I used the 'L-Star RGB v2' for the system and the 'eciRGB v2' for Adobe. They're technically identical but for some reason Photoshop and esp. Illustrator now respect my choices and don't reset anything. Works fine for me. (!)
b Problem 2:
Besides the aforementioned chroma-entry in the Apple default profile (which loss shouldn't cause any issues) there's also the localisation information. Because the profile is named differently in different languages of OS X. I haven't found anything causing trouble (probably because if the profile isn't found it resets back to the english version by default).
b Solution:
This would be easy if someone knows about a .icc file editor. If we could add those localised names from the Apple profile no application would ever know. I've only found hexadecimal editors but won't put something like that on my machine, especially since everything works fine.
I hope Apple comes up with a real solution soon, this seems like too much of a hack - considered the delicate nature of colour management.
If you read this and know what I'm talking about and disagree or know any reasons why one would not want to do this - please speak up! I'm sure I'm not the only one who would like to know.

Similar Messages

Interface/Gamma issue - Display profiling

If you profile/calibrate your display (with professional software) to Gamma L* - darkish, grey boxes appear in some application-windows. Never happend in Tiger so I figure it's a Leopard issue.*
If you use Gamma 1.8, the Apple default, Photoshops windows (in my case) look perfekt. With Gamma 2.2 they're barely noticable (pretty much only if you know the boxes are there).
All the other settings you can choose while profiling - like temperature, luminance, chromatic adaption, profile-type etc. don't influence windows in this way - but as soon as you change the gamma those boxes appear.
I would very much like to know how you guys deal with it - do you profile your display to 1.8/2.2 (like a CRT) OR do you use L* and live with the boxes OR have you profiled your display properly/with L* but you don't have this nuisance? (!?)
Any help/info would be greatly appreciated.

*So here's what I think happens (+ my idea to solve the grey-boxes issue):*
Some applications use the monitor-profile to draw their interface. Like Photoshop and Graphic Converter. (The only 2 I've installed, I'm sure some video-editing-applications, even players are concerned that's maybe the reason some people think it's 'random'). I think these apps do so to immediately can reflect a change in the profile, without restart.
Now Mac OS X Leopard seems to not allow these applications to do so in certain parts of the interface. (Must be new, that's why there were no issues with Tiger) The window itself is drawn by the OS. That's the reason only elements like the text and buttons are affected.
And the problem is that the OS uses its 'Generic RGB Profile.icc' which contains Gamma 1.8. So if you calibrate your display with Gamma L* (which you really should do and most profiling-software does by default) those grey boxes appear in said applications.
The solution is easy. Replace the system-rgb-profile with one that supports L* - like the eciRGB profiles.
To do so you have to rename the .icc file in finder but also edit the information inside (which can be done with the ColorSync Utility). Then copy it to the System/Library/ColorSync/Profiles folder.
*After that the grey boxes dissapear and everything is back to normal.* There's some difference in the tabular data like the CMM and a chroma-entry, so you might want to re-write your display-profile just to make sure everything's alright.
I haven't seen anything yet but could imagine that the rendering of webpages in safari might be affected. Or rather some webbrowsers' without colour management. (Just a theory, hopefully not...)
*Problem 1:*
Some Adobe apps can see that the current system-profile is identical to your working-space-rgb and reset your rgb-choice to the Generic RGB profile after a restart. (Without changing the 'Colormanagement SYNC'd icon/setting.) This probably could cause trouble if you export or open files.
Solution:
Use a different profile for your system than your Adobe-RGB setting. I used the 'L-Star RGB v2' for the system and the 'eciRGB v2' for Adobe. They're technically identical but for some reason Photoshop and esp. Illustrator now respect my choices and don't reset anything. Works fine for me.
*Problem 2:*
Besides the aforementioned chroma-entry in the Apple default profile (which loss shouldn't cause any issues) there's also the localisation information. Because the profile is named differently in different languages of OS X. I haven't found anything causing trouble (probably because if the profile isn't found it resets back to the english version by default).
Solution:
This would be easy if someone knows about a .icc file editor. If we could add those localised names from the Apple profile no application would ever know. I've only found hexadecimal editors but won't put something like that on my machine, especially since everything works fine.
*I hope Apple comes up with a real solution soon, this seems like too much of a hack - considering the delicate nature of colour management.*
*If you read this and know what I'm talking about and disagree or know any reasons why one would not want to do this - please speak up! I'm sure I'm not the only one who would like to know.*
This is pretty much mirrored on the Adobe forums btw.

QT Motion Jpeg gamma issue

I jumped from using CS3 to CS5 so this may have popped up in CS4 and everyone else figured it out already.
I used to deliver files in QT Motion JPEG codec. However in CS5 when I output in that format everything looks washed out as though there is a gamma issue when playing back in QuickTime, or other editing software. If I open that QT file back up in After Effects it looks fine.
I'm not using color management, just an out-of-the-box installation at the moment.
I switched to delivering in QT Animation codec which solved the problem but the filesize was overkill for this particular project.
Any help is appreciated!

This did fix the problem asuming I want to bring the footage back into after effects. When I do that everything matches.
But...
If I open the original source footage up with QuickTime, or in a 3rd party editing application and compare it to the AE render made with "Match Legacy After Effects QuickTime Gamma Adjustments" and also compare to a render made without that setting turned on I get very different results
The original source looks good, but both renders look equally incorrect (washed out like a gamma problem)
Is After Effects adding a pripriatary tag to the output file that only AE is resepecting when it's loaded back in?
Thanks!

More Gamma Issues

Today, I wanted to focus on the current state of RAM Preview.
Last week, I went through exhaustive testing of color accuracy through an After Effects workflow, with source material generated out of Final Cut Studio 2 & 3, all 1920x1080 29.97i. I performed tests through After Effects CS3, CS4, and CS5. In all cases, we used both Tektronix 601A and The results were eye-popping.
After going through your notes about the recent gamma issues, I made your recommended changes to the Interpretation Rules, as well as the MediacoreQTGammaRulesCSx, along with the proper color management settings (Rec 709).
Setup:
MacPro 3GHz 8-core (MacPro2,1)
16GB of RAM
AJA Kona 3 v.7.5.1 or v.8 drivers
OS 10.5.8
QT 7.6.4
In the case of CS3, gamma accuracy simply can not be had either via RAM Preview nor via rendered files. In CS4, one can clearly see that Adobe did a very good clean up job on gamma accuracy but those fixes are limited to rendered files. RAM Preview using the QuickTime Output Component through an AJA Kona xx card aren’t even close when looking at Gamma. As a result, black levels are several IRE too low. If we use the AJA Adobe Plug-ins for 7.5.1, I can get accurate Gamma BUT I can’t get real-time frame rates if I use a Project bit depth > 8bit.
So I have a choice, inaccurate Gamma or bit limited RAM Preview. So why is running a project in 8-bit mode bad? Banding and color skew. Most camcorder acquisition formats are 8bit YUV. Doing conversions from 8bit YUV to 8bit RGB are simply bad. You are converting from a scaled color space in which your usable levels are 16-235 (YUV) over to 0-255 (RGB). As a results, you are going to have plenty of errors. By converting to a 16-bit RGB space, those errors are virtually eliminated.
Now we both know that RAM Preview desperately needs a “do-over” and has for years. But, it is what we have today and our clients desperately need a solution that offers both gamma accuracy and real-time frame rates in 16 & 32bit modes.
Thank you for listening

I tried the three solutions noted on the page, but none of them actually "address" what my problem is. I could not find the directory in the registry, nor could I create one. Is there any last-ditch attempt or solution? I was told I could turn the "time" back on my computer, though I don't want to lose my information or run the risk of nothing happening. For now, thanks for your help.
ADVICE WELCOME!

CS3 Photoshop Layers issues? Snow leorard??

Since recently loading new snow leopard we are having issues in our Photoshops. Mostly noticed in the Layers pallete. Which will not allow us to right click to select and element on a layer. It moves the entire folder of above elements as a group. Some machines will not allow to right click on an element to find that individual layer any longer.
Any knowledege on issues with the compatibility with Photoshop cs3 and snow leopard 10.5?? Any help or solutions?
thanks!!

Sorry, hindsight is 20/20, but I paid $170.00 for the system pgrade and personally I like it -- A LOT -- with the CS3 Photoshop exception. I personally have run into no other "bugs" or issues in my workflow, other than this one. I am hoping someone out there has run into the same issue and come up with a fix, which is why I posted.
Perhaps I am assuming too much here, but I don't believe this to be an "Apple" issue, but rather an "Adobe" issue. Why do all the other modules in CS3 load fine on install? Why does a trial of Photoshop CS4 load with no problem. It doesn't make sense to me that others are running CS3 Photoshop on Snow Leopard and I can't. Something is amiss here.
I have used Adobe products for almost 20 years and have been very loyal to them. I keep my programs as updated as possible and have purchased legal upgrades along the way for everything that I use, which is not pocket change to be sure! But, as of a couple of years ago (actually starting with CS3, which gave me issues on install many years ago in Tiger), I have had nothing but issues and problems. No other programs give me issues, which really sucks since Adobe is such a major part of my workflow.

Interface freezing issues and hard drive replacement

Hi, I have an Imac. It was getting slow and kept getting a long time lag on typing etc. So I bought snow leopard, backed up and wiped and reinstalled the lot. Then it started freezing - from moment one (literally). I could move my mouse and stuff was still running but I couldn't click on anything or select anything or get any response at all. Sometimes it would "white out". Only solution was forced reboot.
So I called apple, rand disk utility, kept showing disk errors - file 334576 should be file 334575 etc. Fixed them - they came back after each freeze. So they said its a hardware error.
Took it to shop. They reinstalled and no errors showed in the tests - but then it kept freezing when they tried to use it. Eventually they settled on a hard drive error - fitted a new one (money paid), it didn't freeze in 48 hours of tests and use. They said that if it keeps freezing it must be an intermittent motherboard problem. TBH I'm not convinced because, though it was slow before SNOW, it wasn't freezing!
Anyway, I took it home, put my stuff back on, was fine -
next day, froze twice in 2 mins - once, rebooted, then again, froze instantly before dock had fully popped up! (It seems to freeze in movement a lot - like task switching or dock popping etc).
It was then that I stumbled upon this term online "interface freezing issues" which seems to have been an initial issue with the imac, and there were some early posts about snow too. The problem is exact, if you minus this hard drive error issue, which MAY have been separate problem (cause by shorts caused by excessive cat hair inside computer).
I have read that external drives etc can be a cause, but not heard usb mentioned, only flywire - I have a dual USB port external drive for time machine. But really, this freezing is entirely since snow.
Can I solve this problem?
Do apple acknowledge this problem?
SHould I uninstall it and ask for my money back?
I would like solid, conclusive answers if possible - from people with direct experience. I work online and am also a writer - i am BEYOND dependant on this mac (especially as my partner is seriously ill and I am the sole income just now).
thankyou for reading
Anna
Anyway - ran disk utility - but no errors this time. Which is good.

As for the taking apart part. I'm not too worried. I've read quite a bit on the subject and watched a couple youtube videos. Also, i've taken a iBook G4 apart to it's core to replace that hard drive and did it without a hitch.
I'm a little unsure about the interface for the Optical Drive. From what i've read the HD is a SATA connection. While, the Optical Drive connection is IDE. Is that normal for one computer to have both?
I found two drives both around $100 for each. One is SATA the other is IDE.
SATA
http://www.pioneerelectronics.com/PUSA/Products/BusinessProducts/Blu-rayDisc+DVD Writers/DVDComputerWriters/DVR-TS08
IDE
http://www.newegg.com/Product/Product.aspx?Item=N82E16827118021
Also, the HD from Newegg that I posted above, runs at 3GB/s. I've remember reading somewhere that my iMac will only run the drive at 1.5GB/s. Is that true?

FCP 6 & SL Gamma issues

I seem to have a problem with gamma in FCP6 on snow leopard. Rushes in QT are fine, but appear very dark in FCP. I have read on Creative Cow forums that the fix is to upgrade to FCP 7 (!!) but I was rather hoping I could avoid this extra expense just now.
Any other suggestions? I don;t understand why FCP6 would not display colours correctly.
Is there a user setting I need to adjust in FCP? I can see a difference between setting the play back gamma to "accurate" and "approximate". Does this mean that QT is not displaying gamma correctly? Would be nice to get both to match.
Thanks

ajophoto wrote:
Any other suggestions? I don;t understand why FCP6 would not display colours correctly.
The COW thread you linked to explains that FCP adjusts the gamma to approximate what it would look like on a broadcast monitor which causes problems with Snow Leopard as it changes the default gamma profile of the OS. I cannot confirm whether or not this is fixed in FCP 7.
I seem to have a problem with gamma in FCP6 on snow leopard. Rushes in QT are fine, but appear very dark in FCP. I have read on Creative Cow forums that the fix is to upgrade to FCP 7 (!!) but I was rather hoping I could avoid this extra expense just now.
Why does it matter if you are offlining? Even if you had FCP 7 and it fixed the gamma issue, I would still not recommend relying on it for accurate image reproduction.
Is there a user setting I need to adjust in FCP? I can see a difference between setting the play back gamma to "accurate" and "approximate". Does this mean that QT is not displaying gamma correctly? Would be nice to get both to match.
There is no setting in FCP, only "Final Cut Studio color compatibility" in QuickTime 7. But there is still some discrepancy between the two, even on Leopard. I never rely on this.

Gamma issues !

Hi there Adobe folks
This is just a follow up post to see if any movement has been made on the gamma issue front.
Basically importing footage into AE and then exporting results in unpredictable shifts in brightness, appearing either darker or lighten than they appear in the composition window or even when played in the Quicktime player - as well as suffering a colour cast change.
So at the moment I am on a iMac i7 with CS4 AE and OS X 10.6.4 - and AE is almost unusual for me as I may spend hours carefully colour correcting a pieces of footage only to have my output look completely different, I have used AE professionally for over 10 years now and have never had these issues, when I used to render my final piece (usually as uncompressed or as Animation set at 100% Q) the resultant file is identical to what you see in the composition window - everytime, without failure.
Now trying to get the output look anything like the composition window seems next to impossible, I am not the only one suffering this problem, I was working in London last week at a fairly well known studio and their compositors have all but given up on AE for this very problem, we even - at one stage - ended up working in Photoshop (!!) to get around this problem.
So, any news on possible solutions out there yet ?
Cheers for any input.

Musings on a disaster . . .
Worked my way through all the literature - some of it comes reasonably close to addressing the gamma / colour shift problems (after a lot of reading and testing and failing and frustration), nothing seems to correct it absolutely . . . . which ultimately renders After Effects unusable as a professional tool (up to CS4 at least - I have not upgraded to AE5 as the upgrade appears to be prohibitively expensive).
I understand that the real villain in all this is Apple/Quicktime, but it shocks me that Adobe (with AE) have not taken a much more robust approach to resolving this problem.
Most of the tools I used to depend on and trust on for my day to day work are very simply useless now, what point is there in sitting with a client for 6 hours grading a piece of footage only to find yourself unable to deliver what the day's work achieved, why bother using Colour Finesse when leaving the 'full interface' mode to view your work in the composition window you see a differing version - and so on.
What is more frustrating is that this problem simply did not exist a version or two ago, I happily spent well over a decade (professionally) being able to concentrate on making things appear as I wanted them to and then being able to deliver just that - this has seemingly gone.
Literally put, After Effects is broken.
I really appreciate all the help I have got from this forum in trying to resolve this, but nothing has come close enough that it could be considered a solution, it's simply no good telling a client: "It's a bit washed out and the colour is a little bit more red than we wanted, but it's pretty close".
So . . . . solutions (more correctly compromised work arounds) - I hope these might be of some help to others stranded on Adobe/Apple island.
Basically I suspect my requirements at output are much the same as others who do this for a job, firstly a master output for delivery/broadcast/tape - and a compressed output for client proofing.
For the compressed non-master - I used the latest x264 codec - simply download it (Google is your friend) - install it and ignore all those other codecs that you have used over the years - this actually works pretty well, your AE render looks identical to your AE composition (100% identical) when played back in QT7 - and only a little washed out when played back in QT10 (much less washed out than other codecs).
For the master output - forget the days of being able to render to 'uncompressed' and know all is well - those days are seemingly gone. But you can still come fairly close to rendering something to a lossless format that looks reasonably close to your composition if you stick to 'Animation' or 'ProRes' - the reason I am not more specific here is that your success would seem to depend on the particular project - sometimes ProRes get's 90% of the way, other times it looks overly saturated and Animation get's you closer - so experiment, but these two high-quaility codecs can often get fairly close.
(*ProRes is not, of course, 'lossless' - but in the circumstances if it renders closer to the look of your composition than Animation it is not a terrible compromise).
On a final note: I used to work at a post/facilities house in London (UK) who have used AE since at least 1998 (when I first worked for them) - I was freelancing there last week and they seem resigned to After Effect's death as a professional tool and are now looking at other compositing environments.
Additionally I managed a small coup recently in being able to steal a small piece of work (a single scene from an upcoming Christmas TV ad for UK TV**) from another major - perhaps the biggest, most respected - London post house - they floundered in being able to convincingly replace an actors face with a (much happier) replacement (using Inferno) - the Director handed me the scene - I got it to work really well, he much preferred my result, I was pretty happy with taking on a major facilities house and beating them - but the process of delivery was simply embarrassing, they used my (After Effect's) erratic output to - I suspect - win back some face at not being able to do the scene as well - after much battling with After Effects the decision was to use my render as a guide only for the Inferno operator - such was the inability of several professionals to output an identical file.
After 15 years in this game that was f*&king disappointing and not a little bit embarrassing as I am sure you might imagine.

Mac OSX: Flash CS3 Font Install Issues

Hi,
I have a Mac Powerbook G4 with OS X installed and Adobe CS3.
I've installed a font. The font works in Photoshop and Illustrator
but not in Flash CS3. Why? I've put the font in the Library/Fonts
folder and the User/Fonts folder and it still doesn't show up in
Flash. Apparently this is a problem for a number of people see
another forum here:
MAC
OSX: Flash CS3 Font Install Issues Forum
Please let me know what to do to fix this. I need to be able
to work with the font in all three applications Flash, Photoshop
and Illustrator.

Hi davidd61713525,
Sorry for not getting back to you sooner.
Unfortunately, it looks like something is wrong with the file system and the installer can't see the root drive to install to. A Google search returns numerous results affecting various products and the recurring theme is that something is wrong with the disk. There are many recommendations from various sources, but nothing definitive.
Here's a similar thread over on the Apple forums:
Broken Installer Permissions | Apple Support Communities
And a similar older one:
http://forums.macrumors.com/showthread.php?t=1203509
I would try the following options:
Try using the PKG installer. This is used Mac SysAdmins to install Flash Player within their organization and uses a slightly different installer path, which may or may not work.
Some people have had success with disk and permissions repair some have not. You can try running a disk and permissions repair. After the disk and permissions repair is complete, reboot the system and try to install again using either the online installer (get.adobe.com/flashplayer) or the offline installer, posted at the bottom of the Installation problems | Flash Player | Mac page in the ‘Still having problems’ section.
If these options do not work, I'd reach out to Apple support to see if they have a suggestion. If you do find a resolution to this, please let me know. I'll be happy to share it with people that encounter the problem in the future.
Maria

In PP Interface related issues the role of functional consultant

In PP Interface related issues what is the role of functional consultant . what is the approach steps to analyse and resolve the issues in XI, interface, idoc, etc.,

For issues relating to interfaces, a functional person would need to diagnose what is causing the issue & thereby informing the technical person where to fix it, if the issue is due to system setup.
As regards to the steps, I just wish there was a manual which read something like
10 steps on how to analyze....
unfortunately there is none that I have come across or even if one is ever written on those lines will be very specific, so not much of use for your need. A good approach would be to have a clear understanding of what the interface is supposed to do, which would assist you in fixing the issues.

Interface scripring issue

Hi all.
Just playing with extendscript toolkit and ps cs5, i Have an issue with javascript based panels.
Both my attempts and toolscript samples ebete a New window object is created as panel or window disappear as Sion as shown.
Otherwise modals persist (the script us dispenser and my window not garbaged).
How to solve the problem?
ThNk's, Andrea

Oh yeah the mouseover->layer creation is not a problem but only a practical
situation. The answer is "JS cannot be used to create panels"... thank's
it's as i doubt :/
A solution could be using Adobe Configurator 2.0 to draw the panel and JS
for code automation... i just discovered it on Labs: i'll try for a while.
2012/1/18 c.pfaffenbichler <[email protected]>
Re: interface scripring issue created by c.pfaffenbichler<http://forums.adobe.com/people/c.pfaffenbichler>in
Photoshop Scripting - View the full discussion<http://forums.adobe.com/message/4148576#4148576>

I have to downgrade from Yosemite to Snow Leopard because of compatibility issues with some of my software. Can I use PS Elements 12 with snow leopard?

I have to downgrade from Yosemite to Snow Leopard because of compatibility issues with some of my software. Can I use PS Elements 12 with snow leopard?

PSE12 became a 64 bit app for the first time on Mac. The recommended system requirements are Mac OS X v10.7 through v10.8.
Are you not able to use lion or Mountain Lion?

Premiere Pro CS3-CONSTANT Memory issues when editing/rendering/exporting

Alright, as said in the title I am currently using Adobe Premiere Pro CS3, and my issues are horrendous
No matter what, within 10 minutes of editing, Premiere will warn and then crash because of memory issues, starting with the message:
"Adobe Premiere Pro is running very low on system memory; please save your project and proceed with caution"
Also, whenever I try to export this project, within 800 frames of a 7000 frame project (currently), it displays the message:
"Error Compiling Movie", and then the previous message above if that hasn't already happened before
And eventually, the program will crash out of nowhere, with random windows errors
Here's my specs:
Intel i7 920 Processor
6 GB DDR3 RAM
Nvidia 480 GTX
750 watt power supply
24" Dell Ultrasharp Monitor
Now, I've noticed that whenever Premiere is getting close to crashing, my RAM gets up to around 4.7 GB being used, and then it crashes.
I have already gone into Edit-Preferences and tried switching from Performance to Memory; that hasn't fixed anything
I noticed that when I was just running my video over and over again, it stayed stable at 4 GB or so, so maybe its a rendering issue?
I have already tried lowering my number of processes running at any given time, including my antivirus program (Kaspersky) and even explorer, but it still crashes no matter what.
========================================================================================== ========
This is a SERIOUS issue for me, as even with all the normal crashes I could finish the video; but now I cannot even export my video at ALL without it crashing, and I have a plenty strong-enough computer to handle this, so what gives?
Please help

Ok, well this has been getting me nowhere
I tried importing (both my CTRL-X method, and literally importing the project), and now the program won't even RENDER the footage, it just errors out at 800 frames (just like exporting)
What is going on???
I used to use Premiere Pro 2.0 all the time, on a separate computer, but I have 6 GB of RAM, is this really impossible???
EDIT:
And now, even after finally getting it to render (by saving after rendering before what crashed, and then starting it up and rendering again), all my footage looks like crap XP

Interface freeze issue with Flash Projector

I am facing an interface freeze issue with Flash Projector running a flex state based application. A Flash Projector exe was generated from a standalone flash player ver 10.2. The target machine on which the problem occuresd has 10.3.
Basically "screen freeze" means that the user interface is running as usual on Flash Player, but it's not responding to any user input (like button presses). But if we alt-tab to another application, the state changes in the Flash player. There is display with buttons on the screen, but touching the buttons or doing anything else - it did not respond. Rebooting the computer fixes the problem.
Can you suggest why this is happening? Is there any known bug in Flash Player.
The problem is this is being hard to reproduce on the developer workstation as it doesn't happen always. But it happens quite often on the target machine running an Intel Atom N270. What debugging steps can you suggest?
Problem Description : http://www.youtube.com/watch?v=z25oV9QWRyk

First, thanks for the video. Having this always makes it much easier to understand the problem. A couple of recommendations. First, if you feel like this might be a player bug, please add a new bug report over at bugbase.adobe.com and if possible please include any sample code or swf's that can help us reproduce the problem internally. Linking the video would also be great. In addition, would you mind reposting this question over on the Flash Professional forums? This forum is primarily for end users, the Pro forums will get you in touch with a wider developer audience who might have additional feedback.
Thanks,
Chris

Interface Scenarios - Issues / Messages tab

Hi,
How can I activate the Issues / Messages tab of the Interface scenarios? The tab is available but I cannot enter any issues or messages as I can do under Configurations.
Any inputs are appreciated.
Many thanks,
Dharmi

Hi Dharmi,
I see what you mean but this is not possible for this node. Even if you create subnodes under Interface Scenarios, Issues/Messages cannot be entered here as per other nodes.
Possibly you could try linking a node or document to the Interface Scenarios node and assigning an Issue/Message to the original node above.
Regards,
-Rohan

Leopard - CS3 - Interface/Gamma issue

Similar Messages

Maybe you are looking for