Wierd JSFL bug found in CS6

So I've been struggling with this wierd bug. Basically we have this JSFL script that we use to tag our assets in our FLAs (like, this is a "chair" or a "door", etc...). We decided to move the metadata from stage instances (which use the Element.setPersistentData() method) to the library items themselves (which use the Item.addData() method). This works under certain circumstances, but I'd like to share the wierdness to see if anyone else has experienced this.
When you open an FLA and start tagging, everything works while you still have it open. You can re-add metadata using the libraryItem.addData("tag", "string", "chair") function, remove it, and all that fancy stuff. However, once you close the file and reopen it, any changes you made are now lost.
The wierd bug I found is that this only happens if you save the file normally, or if you use "Save As..." under the CS6 format. If I save as a CS5.5 document, the metadata I'm using will persist when I open/close the FLA. The other wierd thing is that the CS6 file can in fact save the persistent data, it just doesn't save your latest changes (basically if you save CS5.5, then immediately save again with CS6 it works because you saved it as a different format at least once).
Has anyone experienced this before or has any solutions that I should try? I'm testing this on other machines to see if it's only my computer that has this issue, but if anyone has any ideas I'd be happy to hear them. I'm currently using Adobe Flash Professional CS6 v12.0.2.529 to write these scripts.

Hi Bakedbeans,
The issue that your facing exists on CS6 . However on the lastest Flash CC , this bug is not found . The metadata that has been added to the library items are preserved .
Thanks
Saurav

Similar Messages

Bug Found: Illustrator CC *always* merges layers when opening a DXF file - CS6 works properly

Bug Found: Illustrator CC *always* merges layers when opening a DXF file - CS6 works properly. When opening a DXF, CC merges multiple layers into one, even if you have the "Merge Layers" unchecked. Can a forum admin employee get this submitted as a bug report? Thanks.

Thank you Larry. I just submitted this bug report pasted below at the link you provided.
******BUG******
Illustrator CC 17.0.0 *always* merges layers when opening a DXF file, even if you have the "Merge Layers" unchecked.
1. Open a DXF file that contain multiple layers in Illustrator CC 17.0.0
2. Uncheck the "Merge Layers" button.
3. Click OK.
Results: It has merge all the layers into one layer.
Expected results: It should open with multiple layers preserved. Illustrator CS6 works properly.

Bug Found and Fix Found Creative ZEN XFI Style 32 Gig

9Bug Found and Fix Found> Creative ZEN XFI Style 32 Gig?Hello I was having problems getting my MP3 TAGS to show up on a number of my MP3's.
Whenever I loaded my files onto my ZEN it would show up as a Voice under Recordings.
And the file name would be "MIC and the date file created etc..."
I noticed that these files where all starting with the letters MIC at the front of the filename...
For instance: Michael_Jackson_Thriller.mp3?? or? Michael_W_Smith_Let_it_rain.mp3
and so on and so on... ANY file that started with the letters M I C? would be thrown in as a voice recorded file and the TAG would not operate.
I have the latest Firmware on my MP3 Player.
The fix was just to change the file name so it did not start with MIC... so i went and switched Michael Jackson to M.Jackson and also switched Michael W Smith to M W smith.
The tag showed up appropriately and I have had no problems since.
It would be nice if there was another Firmware update so that MP3's could start with the letters MIC also I was hoping to bring awareness to this situation for other users.

=Re: Bug Found and Fix Found> Creative ZEN XFI Style 32 Gig?I did three methods of?loading the files.
I used Windows Media Player to sync the files.
I used Creative Central to transfer the files.
These two methods produced results where the file starting with MIC turned into a voice recordings.
I also had problems just copying and pasting the files (using windows explorer).
I have not had any problems with any other file. I normally use MP3Tag to tag my files.
However i even tried using Windows Media to tag the file and I even tried using Creative Central to tag the files.
I tried as many work arounds as possible. But once i renamed the file it worked.

Possible bug in Photoshop CS6 with app.activeDocument.path.

JavaScript running in Photoshop CS6 under OS X 10.7.5 returns the wrong result for app.activeDocument.path when the file is located on the boot drive. The result is undefined and an error message incorrectly states that the document has not been saved yet. If the file is located on a remote volume, the correct path is returned.
To reproduce this problem, create a new file in Photoshop CS6 on a Mac. Save the file to the desktop. With the file still open, run the following script in ExtendScript Toolkit.
// start script
var thePath = app.activeDocument.path;
alert(thePath);
// end script
Running the same script with a file located on a server volume open in Photoshop correctly returns "/path/to/file.psd" instead of undefined and no error occurs.
This appears to be a bug in Photoshop CS6's JavaScript implementation. This problem did not exist in Photoshop CS3.
A similar issue prevents Photoshop CS6 from saving files to the boot drive using activeDocument.saveAs.
Has anyone else experienced this problem? If so, have you discovered an alternate method to determine the file path or save a file on the boot drive?

Don't know if this will help much but at least you can use it to check a document's filepath without throwing an error. And maybe tell if the problem is with the Photoshop DOM.
function hasFilePath(){// returns true/false
    var ref = new ActionReference();
    ref.putEnumerated( charIDToTypeID("Dcmn"), charIDToTypeID("Ordn"), charIDToTypeID("Trgt") );
    return executeActionGet(ref).hasKey(stringIDToTypeID('fileReference'));
function getFilePath(){// returns path as a string if exists, undefined if not
    var ref = new ActionReference();
    ref.putEnumerated( charIDToTypeID("Dcmn"), charIDToTypeID("Ordn"), charIDToTypeID("Trgt") );
    var desc = executeActionGet(ref);
    if(desc.hasKey(stringIDToTypeID('fileReference'))) return decodeURI(desc.getPath(stringIDToTypeID('fileReference')));

Shortcut-Bug in Bridge CS6 (Mac OS 10.6.8 and 10.7.3)

I noticed a bug in Bridge CS6: the cmd-key doesn't work in the file info panel btw. in the xmp / iptc fields (e.g. cmd+c, cmd+v, ...).
This bug only appears in the file info window (opened via alt+i) in Bridge CS6 - if you edit information or metadata via alt+i in Photoshop CS6, the shortcuts e.g. copy and paste from one field to another works.
The shortcuts also work under Windows (tested under Vista).

I can reproduce this issue in Bridge CS6. Thanks for reporting!
Best Regards,
Bridge QE
Chun Xia

[svn] 4223: Some fixes for bugs found running the TC acceptance tests:

Revision: 4223
Author: [email protected]
Date: 2008-12-03 11:35:03 -0800 (Wed, 03 Dec 2008)
Log Message:
Some fixes for bugs found running the TC acceptance tests:
- Empty try {} throwing NPE while emitting code.
- OP_Callproperty and OP_Callproplex may have a known type but default value.
- Better diagnostic message for CONSTANT_TypeName and preliminary plumbing for CONSTANT_TypeName support.
Modified Paths:
flex/sdk/trunk/modules/asc/src/java/adobe/abc/GlobalOptimizer.java

Re: SB Audigy Series Support Pack 2.5 (08/09/2009)? Important Installation Notes
If any drivers are already installed, you must follow these steps to ensure a proper installation of the new Support Pack.
) Open a Command Prompt window with Admin privileges (right click and select Run as Administrator).
Type the following commands:
takeown /f C:\Windows\*.cdf
cacls C:\Windows\*.cdf /G [color="#ff0000"]Administrators:F
Where [color="#ff0000"]Administrators may?be different if you are running a localized version of Windows or?you can simply use your login name.
2) Unpack the previous Support Pack or Creative official release.
3) Run \Drivers\Setup.exe and choose Driver Uninstallation, select Delete all shared Creative audio driver files. and click OK. Reboot when asked to do so.
4) Make sure the following files were deleted, otherwise delete them manually:
- For Windows 7 / Vista 32-bit open?C:\Windows\System32 and delete UDAAPO32.DLL and?UDAPLD32.DLL.
- For Windows 7 / Vista 64-bit?open?[color="#ff0000"]C:\Windows\System32 and delete[color="#ff0000"] UDAAPO64.DLL and?[color="#ff0000"]UDAPLD64.DLL then? open?C:\Windows\SysWOW64 and delete UDAAPO32.DLL.

Found Bug in PS CS6 While Trying to use the Eraser Tool

I was editing an 8 bit JPEG that I imported from Adobe Lightroom 3. While using the standard eraser tool to erase the background it would stop working and then move the screen around until I released the mouse button. This happend about every 10 - 20 seconds. I'm using a Macbook 2,1 with the OSX 10.6.8.
Recreate Steps:
1) Import 8-bit JPEG from Lightroom 3
2) Select eraser tool on main layer (background)
3) While holding the mouse button down start to erase part of the image
4) About 10 - 20 seconds in the eraser will stop working and then when you move the mouse around image moves
5) To stop the movement you have to release the mouse button and the find the correct part of the image again and start erasing again
6) Most of the time I was viewing the image at >150%
Hope this helps and you can find a fix. It's very annoying to have to stop and find the correct area of your photo to erase.
Anyone else having this issue?

I am trying to reproduce this but as of now, mine is working properly.
Can you copy and paste your system information in this thread for me to take a look at? (Photoshop Help>system info)
Pattie

Warning - gradient fill bug found

I have reported this bug to Adobe. Watch out so it won't bite you.
Short version: gradients can disappear completely when exporting to pdf
Long version:
A. Gradient fill with default settings. First color starts at 0% and second color ends at 100%.
Copy an object with this color to Illustrator or export it as a pdf file. This works fine.
B. Change the start color to 5% and the end color to 90% (anything other than 0/100 will trigger the bug)
Copy and paste an object with this gradient fill to Illustrator. Result: no fill color
Export object to PDF. Result: no fill color
C. Default gradient fill (0% to 100%) + add a third color = works fine
D. Same as C. but change the start and end colors as in B. Triggers the bug again
Bug verified in InDesign CS6 and CC on OS X 10.8.4
Bug verified by Adobe Support.

Hi everyone. I work for a large format printing company. We receive thousands of files every year from many different designers. We started to notice that gradients would drop out of some PDFs when opening them in Illustrator but they would preview fine when opened in Acrobat. I searched high and low for an explanation for this glitch. The only response I received is "Stop opening exported PDFs in Illustrator." This is an unsatisfactory answer for someone that needs to preflight directly in the Illustrator program. I've done a ton of research and have been racking my brain for the last 2 years and have finally found sufficient workarounds for this issue. The downfall with these workarounds: all spot colors located in the gradients will convert to CMYK mixes. I'm still researching to see if there is a way to keep spot colors intact in these areas.
A little back story: InDesign is converting the gradients into something called NChannel. It enables more accurate handling of color blending by including additional dot gain and color mixing info. Both InDesign and Acrobat have the ability to display these elements whereas Illustrator, from what I’m finding, does not. Which is why we’re seeing gradient elements drop out when opened in Illustrator.
Workaround for CMYK Gradients
Open PDF exported from INDD in Acrobat
Go to Tools > Print Production > Convert Colors
Object Type: Smooth Shade (this tells Acrobat to hone in on Gradients only)
Color Type: DeviceCMYK
Check Embed next to Conversion Profile (should be SWOP)
Expand Document Colors on the right and Select DeviceCMYK in Color Spaces then click ok
Save the PDF
Workaround for 1 Spot Color in Gradients (Converts Spot Color located in Gradient to CMYK – all other Spots stay intact)
Open PDF exported from INDD in Acrobat
Go to Tools > Print Production > Convert Colors
Object Type: Smooth Shade (this tells Acrobat to hone in on Gradients only)
Color Type: Spot Color
Check Embed next to Conversion Profile (should be SWOP)
Expand Document Colors on the right and Select the Spot that is located in the Gradient in Color Spaces then click ok
Save the PDF
Workaround for 2 Spot Colors in Gradients (Converts Spot Colors located in Gradient toCMYK – all other Spots stay intact)
Open PDF exported from INDD in Acrobat
Go to Tools > Print Production > Convert Colors
Object Type: Smooth Shade (this tells Acrobat to hone in on Gradients only)
Color Type: Spot Color
Check Embed next to Conversion Profile (should be SWOP)
Expand Document Colors on the right and Select the DeviceN spot color that is located in the Gradient in Color Spaces then click ok
Save the PDF
Please test it and let me know if you run into any issues with these workarounds. I'm always looking for new problems to solve!
- Jenny

Is this a bug in PS CS6?

whenever i try making a 3d object orbit around another, it freaks out : Photoshop Orbit - YouTube
but i asked about it in general discussions and i was pointed to this video : How to Create rotating planets and moons in Photoshop « Photoshop
in which the guy seems to be able to do what i'm trying to do just fine in what looks to be a different ps version.
i was using cs6 but don't know what he is using seeing that i am just getting into ps.

BTW I'm using a Macbook Pro Retina OS X 10.8.5
I uninstalled PS and reinstalled it. Now it works ok. However, when I did the upgrade to PS 14.1.2 it reverted back to it's old way.
It's a bug in the software for me. I've unistalled and reinstalled again and won't do an upgrade untill Adobe addresses the issue.

Shortcut-Bug in Bridge CS6 for Mac / Bridge cant' copy and paste metadata

The cmd-keys / shortcuts doesn't work in the file info panel btw. in the xmp / iptc fields (e.g. cmd+c, cmd+v, ...) of Adobe Bridge CS6 (Mac OS 10.6.8 and 10.7.3). You are not able to cut and paste info from one box to another like previous versions.
This bug only appears in the file info window (opened via alt+i) in Bridge CS6 - if you edit information or metadata in the file info panel in Photoshop CS6, the shortcuts or copy and paste from one field to another works.
The shortcuts also work under Windows (tested under Vista).
I noticed this minor bug already one in the Photoshop CS6 Beta more than one months ago. I hoped that this was corrected in the official test version, but unfortunately it is not. Although it is a minor bug, it is IMHO a basic function and would be very helpful in my daily work. Bridge CS6 and ACR 7 are very good and meet my expect ions or needs - it is too bad, that such a small thing is making working with the application a little bit annoying.
It would be nice, if you could forward this to Adobe engineers that they can fix it.
Thanks so much!

Thanks! If there is a workaround or simple solution, I would be very glad if you could inform me.
Christian
(signature removed by the Admin)
Am 14.05.2012 um 13:49 schrieb FrankBiederich:
Re: Bridge CS6 Mac XMP File Info Panel Bug: can't copy and paste metadata
created by FrankBiederich in XMP SDK - View the full discussion
Thanks for your report; we'll look into it.
Frank
Replies to this message go to everyone subscribed to this thread, not directly to the person who posted the message. To post a reply, either reply to this email or visit the message page: Re: Bridge CS6 Mac XMP File Info Panel Bug: can't copy and paste metadata
To unsubscribe from this thread, please visit the message page at Re: Bridge CS6 Mac XMP File Info Panel Bug: can't copy and paste metadata. In the Actions box on the right, click the Stop Email Notifications link.
Start a new discussion in XMP SDK by email or at Adobe Forums
For more information about maintaining your forum email notifications please go to http://forums.adobe.com/message/2936746#2936746.
Message was edited by: Arpit Kapoor

Bug in Bridge CS6: Orientation tag not always properly interpreted

The Orientation flag in the EXIF metadata can assume eight different integer values with their meanings defined as follows:
1: frame's 1st pixel row = picture's top; frame's 1st pixel col = picture's left
2: frame's 1st pixel row = picture's top; frame's 1st pixel col = picture's right
3: frame's 1st pixel row = picture's bottom; frame's 1st pixel col = picture's right
4: frame's 1st pixel row = picture's bottom; frame's 1st pixel col = picture's left
5: frame's 1st pixel row = picture's left; frame's 1st pixel col = picture's top
6: frame's 1st pixel row = picture's right; frame's 1st pixel col = picture's top
7: frame's 1st pixel row = picture's right; frame's 1st pixel col = picture's bottom
8: frame's 1st pixel row = picture's left; frame's 1st pixel col = picture's bottom
The values in bold typeface (1, 3, 6, 8) are pure rotations only; they are properly interpreted in Bridge CS6 Beta. The values in regular typeface (2, 4, 5, 7) are rotations plus mirrorings; they are properly interpreted in Bridge's Content pane, i. e. where the thumbnails are. In the Preview pane, however, the display is wrong, reflecting the rotations only but not the mirrorings. When opening a mirrored picture in Camera Raw 7.0 or Photoshop CS6 Beta, it will show up correctly again (i. e. with the orientation tag properly applied), so only Bridge's Preview pane is affected, apparently.
By the way, the same bug also is present in Bridge CS5 (and maybe in earlier versions, too, but I didn't check).

Result: In the regular keyword list (dc:subject), the updated keywords appear as expected. In the hierarchical keyword list (lr:hierarchicalSubject), however, the keywords appear as originally imported, ignoring all the subsequent changes. So now dc:subject and lr:hierarchicalSubject are inconsistent.
Not sure I do understand your method correctly but to my knowledge the import and export functions for file info and Keywords are meant for the whole template or the whole keyword list.
If you open a file and start removing and adding you should do so in your keyword list. But how you changed is not very clear to me.
When a keyword is in italic it means it is not persistent and with right click menu you can do so to add it to the list. If you remove a keyword that in your list has a sub keyword it does not automatically change in a parent keyword.

Hue/Saturation Adjustment Layer Bug in Photoshop CS6

I noticed that most of the time I cannot copy a Hue/Saturation adjustment layer in Photoshop CS6. (In about a third of all cases it works, in all others I have to create a new Hue/Saturation adjustment layer).
Hitting Command + J will cause my Mac to make an error sound.
Option + delete also doesn't work half the time.
Also: I cannot do a "Stamp visible" above a Hue/Saturation adjustment layer. Hitting Command + Option + Shift + E will bring another error sound.
I have to creat a new layer, and then create a stamp visible. But half the time this doesn't work, either. Hitting Command + Shift + N will give me another error sound.
I have to create a different adjustment layer, then an empty layer, and only then I can create a "stamp visible".
Only Hue/Saturation adjustment layers are affected by this - but it's a true hold-up.

What Mac? What version of OSX? That aside, your issue sounds too exotic to be a genuine bug. Sounds more like some specific combination of settings is preventing this. could be anything from blending tricks to color profiles...
Mylenium

Possible bug found in Mac Os X Tiger 10.4.11 in conjuction with iPod Touch

Dears,
I think I've found a possible bug in Mac Os X version 10.4.11 in conjunction with iPod Touch.
When the iPod is connected during boot, my Bluetooth hardware fails to be detected. When I restart the portable without the iPod connected, my Bluetooth hardware is recognised & activated again. It is reproduceable.
1. Attach iPod Touch before starting the MacBook Pro
2. Boot the Macbook
3. Bluetooth hardware should be rendered inoperative
Restore functionality:
1. Detach the iPod Touch
2. Reboot the portable
3. Bluetooth hardware is restarted / recognised.
Regards
Cedric

wrong category

FTP BUG in Dreamweaver CS6 after upgrading to build 5861

I just updated Dreamweaver CS6 to 12.0.1 build 5861. Now Dreamwearver fails to put files after several successful puts of the same file. Only symptom is that the background uploader window fails to appear. Only solution is to close and re-open Dreamweaver.
Further testing seems to indicate this condition only happens if I manually save a changed file before attempting the Put. It seems to consistently work correctly if I perform the Put and wait for Dreamweaver to prompt me to save the file.
THIS IS DEFINITELY A BUG THAT SHOULD BE FIXED - Dreamweaver CS6 Perpetual license (Not Cloud)

Ask in the DW forum.
Mylenium

IOS 5.1 Bug Found!

Just updated to ios 5.1 on an iPhone 3GS and found a bug, when removing apps from folders, the second to the last app removed will crash the springboard, and respring... why!? im not sure why but is it comon for iphones to respring? even when they are not jailbroken? ive done a clean restore from ios 5.0.1 to ios 5.1 there should be nothing there to cause a springboard restart.. right? or is this a way of the iphone protecting itself? (like safe mode for example) but thats not fair for me, what of i was in the middle of a serious situation and my iPhone crashes into a respring? im trying to record a number, or a note, or even make a phone call, will i have an issue with resprings all the time or is this a once in a lifetime thing? im actually concerned. tho absolutlly thankfull for the battery fix, it has proved its self worthy. please let me know what you think, will apple release a fix for the crash?

Hi there,
I can't seem to recreate this issue myself, but please report it to Apple here: apple.com/feedback, they are always on the lookout for bugs which they can fix.
Remember to include a detailed description of the error, including a step by step process on how to recreate.
If you have any other questions, do ask, if not, have a great day,
Nathan

Wierd JSFL bug found in CS6

Similar Messages

Maybe you are looking for