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>

Similar Messages

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 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

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?

[Solved] Default interface routing issues

I have two network interfaces connected to my newly installed ArchLinux server, one LAN and one WAN connection. The trouble is that all traffic that is trying to connect to the wan interface gets no response, while the LAN connection work without any issue.
I am using udev to change my interfaces to lan0 and wan0, and i use netcfg to load the diffrent profiles.
Lan0 uses a static local ip 192.168.0.118 with 192.168.0.2 as gateway
Wan0 uses dhcp with dynamic ip from my ISP.
When i manually bring down my lan0 interface all my traffic goes through wan0 correctly, and it even responds to external calls.
So i belive the issue lies somewhere in the local routing?
I am trying to post all config files needed directly.
/etc/rc.conf
# /etc/rc.conf - Main Configuration for Arch Linux
# LOCALIZATION
# LOCALE: available languages can be listed with the 'locale -a' command
# LANG in /etc/locale.conf takes precedence
# DAEMON_LOCALE: If set to 'yes', use $LOCALE as the locale during daemon
# startup and during the boot process. If set to 'no', the C locale is used.
# HARDWARECLOCK: set to "", "UTC" or "localtime", any other value will result
# in the hardware clock being left untouched (useful for virtualization)
# Note: Using "localtime" is discouraged, using "" makes hwclock fall back
# to the value in /var/lib/hwclock/adjfile
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# Note: if unset, the value in /etc/localtime is used unchanged
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
LOCALE="sv_SE.UTF-8"
DAEMON_LOCALE="no"
HARDWARECLOCK="UTC"
TIMEZONE="Europe/Stockholm"
KEYMAP="sv-latin1"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"
# HARDWARE
# MODULES: Modules to load at boot-up. Blacklisting is no longer supported.
# Replace every !module by an entry as on the following line in a file in
# /etc/modprobe.d:
# blacklist module
# See "man modprobe.conf" for details.
MODULES=()
# Udev settle timeout (default to 30)
UDEV_TIMEOUT=30
# Scan for FakeRAID (dmraid) Volumes at startup
USEDMRAID="no"
# Scan for BTRFS volumes at startup
USEBTRFS="no"
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="yes"
# NETWORKING
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
HOSTNAME="weed-devil"
# Use 'ip addr' or 'ls /sys/class/net/' to see all available interfaces.
# Wired network setup
# - interface: name of device (required)
# - address: IP address (leave blank for DHCP)
# - netmask: subnet mask (ignored for DHCP) (optional, defaults to 255.255.255.0)
# - broadcast: broadcast address (ignored for DHCP) (optional)
# - gateway: default route (ignored for DHCP)
# Static IP example
# interface=eth0
# address=192.168.0.2
# netmask=255.255.255.0
# broadcast=192.168.0.255
# gateway=192.168.0.1
# DHCP example
# interface=eth0
# address=
# netmask=
# gateway=
#interface=eth0
#address=
#netmask=
#broadcast=
#gateway=
# Setting this to "yes" will skip network shutdown.
# This is required if your root device is on NFS.
NETWORK_PERSIST="no"
# Enable these netcfg profiles at boot-up. These are useful if you happen to
# need more advanced network features than the simple network service
# supports, such as multiple network configurations (ie, laptop users)
# - set to 'menu' to present a menu during boot-up (dialog package required)
# - prefix an entry with a ! to disable it
# Network profiles are found in /etc/network.d
# This requires the netcfg package
NETWORKS=(sluggy local)
# DAEMONS
# Daemons to start at boot-up (in this order)
# - prefix a daemon with a ! to disable it
# - prefix a daemon with a @ to start it up in the background
# If you are sure nothing else touches your hardware clock (such as ntpd or
# a dual-boot), you might want to enable 'hwclock'. Note that this will only
# make a difference if the hwclock program has been calibrated correctly.
# If you use a network filesystem you should enable 'netfs'.
DAEMONS=(syslog-ng !ufw !network net-profiles @alsa crond dbus sshd lircd sensors mysqld @ddclient @hddtemp httpd samba stunnel sabnzbd sickbeard)
/etc/network.d/sluggy
CONNECTION='ethernet'
DESCRIPTION='A basic dhcp ethernet connection using iproute'
INTERFACE='wan0'
IP='dhcp'
## for DHCPv6
#IP6='dhcp'
## for IPv6 autoconfiguration
#IP6='stateless'
/etc/network.d/local
CONNECTION='ethernet'
DESCRIPTION='A basic static ethernet connection using iproute'
INTERFACE='lan0'
IP='static'
ADDR='192.168.0.118'
GATEWAY='192.168.0.2'
output of route -nl
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 192.168.0.2 0.0.0.0 UG 0 0 0 lan0
0.0.0.0 85.24.137.1 0.0.0.0 UG 203 0 0 wan0
85.24.137.0 0.0.0.0 255.255.255.0 U 203 0 0 wan0
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 lan0
I have had this server running Ubuntu for the past 2 years with the same setup on the NIC's and there everything worked, so I guess i have become a little lazy.
*EDIT* Updated my post with "code" block instead of quote
Last edited by kurri (2011-11-01 22:07:14)

kurri, please edit your post.
When pasting code, please use [ code ] tags https://bbs.archlinux.org/help.php#bbcode
like this
It makes the code more readable and more convenient to scroll through.

Content Library / Web Interface - access issue

BPC Microsoft 7.5 SP6
Windows 2008 R2 server
We have puublished an Excel template as an HTML page to allow (web only users) access to a menuing system and have subsequent access to their individual reports in PDF format. The menu page comes up without errors but I encounter the error "You don't have access" when clicking on a menu option (cells within template). The cells contain an Excel Hyperlink function in conjunction with a EVBNV function to launch this report. (No BPC or excel errors exist within template)
We have created a virtual directory for BPC application in addition to Reports and ReportServer for Reporting Services. We have modified the Site Settings and Folder Setttings in Reporting Services configuration to allow web users to correct role access.Users can access Reporting services Report url without a problem but the web interface does not want to launch/retrieve a pdf file. We have the correct BPC task capabilities and task profiles assigned, insuring they can access and use the content library.
Thoughts?
Thanks in advance.

It appears there is an issue with EVBNV formula and its ability to dynamically pass parameters in HTML format.
IM 0003554460/20111

Printing in Aperture 3 -- Interface & Presets Issues

I very much like the general direction of change in the printing interface, and I can print with satisfaction as to quality in A3, with my primary printer (Epson R1900). But the creation of printing presets seems not to be able to capture final settings made in the Printer dialogue, nor is there a way in the A3 dialogue to pre-access those functions in order to Save in the Preset. This includes turning off the color management in the printer, and setting of expansion of the print to zero when using borderless. I seem to have to reset these for each print I initiate?
In addition, while I can get a change to a Preset to Save between sessions of Aperture, if I have two or more custom presets, the change to any one of them gets made in all of them?
With the first issue, what I am talking about is what in A2 could be accessed in the Aperture print dialogue with the Print Settings button. With that you could access those items that one also sees after you click the Print button, but by doing so via the Print Settings button, those choices could also be encompassed into the Save of the Preset.
For clarity of what is missing, as least for Epson printers, click on the third screenshot in this below O'Reilly link, to enlarge, then you will see the Print Setting button immediately below the name of printer box:
http://blogs.oreilly.com/aperture/2008/06/printing-tips.html
I found this to be the same for all Epson printers, at least. But I see no way to access this in A3. This is not a good development if something akin to the Print Settings button cannot be found in the A3 Print dialogue. If achieving this involves selections for the Default Printer that would impact every app that might use this printer, it would not be handy.
With respect to the saving of Presets, I find this mysterious and either a bug or something simple that I am missing.
Ernie

Ernie,
there seems to be a bug with saving presets, see
http://discussions.apple.com/thread.jspa?threadID=2349173
for more info and workarounds.
Printing in AP3 is a 'two-step' process now - there might have been problems to integrate the various options of printer drivers into the AP interface...
1) AP printing dialog. In AP3 the settings for ColorProfile, PageOrientation, Paper and Printer are saved in the apps preference file, while all other settings can be bound to user-defined presets. This means that changes made to these four will always be reflected to all presets and you will have to check them before you print.
2) System printing dialog. Here you could define presets for those (printer related) options not available in the AP interface anymore (printing and paper quality, etc.) to streamline your printing. The four settings mentioned above are taken over from AP to System dialog.
I must admit that I personally liked the AP2 way much more, but this one seems to be more compatible.
Hope this helps,
Jashe

Interface Controller Issue

Hi,
Hope you can help me on this one. We're trying to use an interface controller to use an external Web Dynpro app in our current Web Dynpro project. Whenever we try to do some context mapping in our Wed Dynpro project, it seems that our Web Dynpro project (during build time) fails to identify context of our component controller (it gives an <insert context node name / context objects here> cannot be resolved errors).
Did anyone experience this error or would anyone know how to resolve this?
Thanks!
Angelo

Hi Angelo,
Please have a look at below document might helps for your issue In[Inter Application Communication and Navigation (Design Time) in WebDynpro|http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/a0ae5f90-1679-2c10-4183-8c64cf932088?quicklink=index&overridelayout=true]
Suppose there are two DC1 and DC2.
DC1 having context node XYZ/attrubute available in DC1 component Controller and interface controller and mapped it properly.
- then build and deploy DC1.
- Now sync sources and sync used DC for DC2
- then click on component name of the DC2 and bind interface controller to component controller and drag n drop context node XYZ to component controller.
- once done then try to re-build and use the contect node XYZ
Hope it will helps
Regards
Arun

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.

Interface determination issue.

Hi Experts,
We are using Idoc(Matmas) to file scenario wherein we are facing the below issue
SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="IF_DETERMINATION">NO_IIF_CASE_ASYNC</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unable to find an inbound interface</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
The condition used in Interface determination is /Zmatmas05/idoc/e1maram/mstae=mw
Please let me know how to rectify this issue.
Thanks & Regards,
Ranganath.

Hello,
Try using double slash in your xPath (for PI7.1) instead of just one, so from
/Zmatmas05/idoc/e1maram/mstae=mw
to
//Zmatmas05/idoc/e1maram/mstae=mw
Hope this helps,
Mark

[SOLVED] XMBC Interface Rendering Issue

Hi all
After upgrading to gnome 3.8 I noticed that my XBMC interface started to behave strangely, mainly the fan art backgrounds started to flicker a couple of times before showing up and sometimes fails to load at all showing the default background image. This happens to other items such as text etc from time to time as well, but not as often. However once starting to play a video everything looks perfectly good.
I think it has to do with that I had to enable SNA for my Intel graphics driver when I upgraded to gnome 3.8 since this happens both in my Gnome session and in my XBMC session, is there anyone who have stumbled upon something similar and can offer me some help with this issue?
Thanks
// Lazze
Last edited by Lazze (2013-05-06 08:04:52)

Seems to have been fixed after fiddling around in the settings pane, not sure exactly what did it but I think it was related to the v-sync settings in menus.

Duplicate Ethernet Interface - Connection Issues

Hi,
Recently, after rebooting, I had a continuous stream of error messages on my login terminal, and I couldn't connect to the network.
[ 669.236979] genirq: Flags mismatch irq 0. 00000080 (eth0) vs. 00015a20 (timer)
[ 670.235840] genirq: Flags mismatch irq 0. 00000080 (eth0) vs. 00015a20 (timer)
[ 671.234701] genirq: Flags mismatch irq 0. 00000080 (eth0) vs. 00015a20 (timer)
# ping www.google.com
ping: unknown host www.google.com
# ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN mode DEFAULT
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT qlen 1000
link/ether de:34:07:d0:d9:29 brd ff:ff:ff:ff:ff:ff
3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT qlen 1000 ## Duplicate interfaces?
link/ether 00:24:1d:a2:f7:c5 brd ff:ff:ff:ff:ff:ff
# ifconfig eth0 up
SIOCSIFFLAGS: Device or resource busy
# ifconfig eth1 up
# dhcpcd eth1
dhcpcd[732]: version 5.6.4 starting
dhcpcd[732]: eth1: sending IPv6 Router Solicitation
dhcpcd[732]: eth1: rebinding lease of 192.168.1.3
dhcpcd[732]: eth1: acknowledged 192.168.1.3 from 192.168.1.1
dhcpcd[732]: eth1: checking for 192.168.1.3
dhcpcd[732]: eth1: sending IPv6 Router Solicitation
dhcpcd[732]: eth1: leased 192.168.1.3 for 2592000 seconds
dhcpcd[732]: forked to background, child pid 780
# ping www.google.com
64 bytes from bom03s02-in-f18.1e100.net (74.125.236.146): icmp_seq=1 ttl=56 time=11.6 ms
After manually configuring eth1, and assigning it an IP, everything works normally. Another bunch of curious messages at boot up were these:
[ 0.271521] pci 0000:01:07.0: BAR 1: error updating (0xfde00000 != 0x000000)
[ 0.271553] pci 0000:01:07.0: BAR 3: error updating (0xfdf10008 != 0x000008)
[ 0.271583] pci 0000:01:07.0: BAR 2: error updating (0x00c001 != 0x00cc09)
What would be a clean way to fix this?
Thanks in advance!

Thanks for the replies.
In an attempt to establish whether it was the computer or the router I plugged in an old speedtouch 510 router which I had lying around - this worked first time, so I guess it's the netgear that is the issue and I will need to reset it and re-enter all the details, unless anyone knows of a quicker way...?

Audition CS6 Mac Won't Play Audio Interface Preference Issue

Hi Im having some problems with Audition CS6 mac. I have the full master collection and only encounter this issue with Audition.
On my Macbook pro
I use my internal speakers/audio or a vrm box audio interface, occasionally Ill use a fasttrack pro to record. My problem occurs after I use the audio interface. When I next open Audition set up for the built in speakers/audio and hit play, it says playing but nothing plays.
When I open Audition after using a external interface going back to my built in macbook audio I get a pop warning that:
"Your systems audio hardware settings have changed. Would you like to go review Audition's audio hardware preferences?"
I click yes, go to that everything is set for internal mac audio,
hit play, says playing bottom left, then just sits there.
I noticed today when it did this, that it if I go into the Audio Channel Mapping Preference, it shows what ever audio interface I used last on the output/not working on it. I am unable to change theses settings.
I reboot after changing audio interfaces, etc.
I can delete my Audition preference files in my user folder and it functions again, but that also entails rescanning all plugins which takes some time.

I just found that removing MachineSpecificSettings.xml in the user/preferences/adobe/audition/5.0/ folder will get it to play again under the internal audio settings. And when I look at channel mapping it shows the internal audio.

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.

Interface scripring issue

Similar Messages

Maybe you are looking for