Skip navigation
Replies 1 2 3 4 Previous Next
  • Currently Being Moderated
    Jun 29, 2012 8:32 AM   in reply to J.Y. Design

    Just noticed that people that were formerly identified as "Adobe Employee" are now merely called "Staff".

    This seems to have been applied retroactively. (unless this is just one of the seemingly endless ongoing adjustments to the Jive forum software)

     

    Hopefully this doesn't portend the withdrawful of the very useful contributions of Adobe employees to these fora. (Yes, they may not always give you the answer you want, but generally they are helpful and are very knowledgeable about the software)

     

    If Marketing/Legal seems to think that the only solution is to limit/forbid employee contributors they are making a big mistake!

     
    |
    Mark as:
  • Noel Carboni
    23,514 posts
    Dec 23, 2006
    Currently Being Moderated
    Jun 29, 2012 8:35 AM   in reply to Bo LeBeau

    Bo LeBeau wrote:

     

    unless this is just one of the seemingly endless ongoing adjustments to the Jive forum software

     

    This is just one of those.  See this thread:

     

    http://forums.adobe.com/message/4525942#4525942

     

    -Noel

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 29, 2012 9:40 AM   in reply to Noel Carboni

    Noel, thanks for the info.

     

    Now if they could just get the forum software to correctly display the correct chronological order of questions.

    It's most disconcerting to see a question that was posted and most recent reply was 10 months ago suddenly appearing between questions that were just posting within the last few minutes or hours.

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 29, 2012 10:47 AM   in reply to Bo LeBeau

    That happens when someone moves a post from another forum, or when we have to delete SPAM that was added to an older topic.

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 29, 2012 12:34 PM   in reply to Bo LeBeau

    Bo LeBeau wrote:

     

    Just noticed that people that were formerly identified as "Adobe Employee" are now merely called "Staff"…

     

    Staff seems a bit more dignified than employee to me.  No need to read much into it.

     

    staff 1 |staf|

    noun

    1 [treated as sing. or pl. ] all the people employed by a particular organization: a staff of 600 | hospital staff were not to blame.

    • the teachers in a school or college : [as adj. ] a staff meeting.

    2 [treated as sing. or pl. ] a group of officers assisting an officer in command of an army formation or administration headquarters.

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 6, 2012 1:37 PM   in reply to D.Estabrook

    I've been having the same issue, i thought it was related to Extensis Suitcase Fusion 3, so I upgraded to find out that didn't work either.. Having the same issue on my iMac or Macbook Pro... changes text randomly to other text and style within the same document

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 6, 2012 2:13 PM   in reply to guilloa

    There are 4 or more other topics about this.

    We know about the bug and are working on it.

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 27, 2012 9:45 AM   in reply to Chris Cox

    Any updates on this bug?

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 27, 2012 10:25 AM   in reply to sumosays001

    I've had another website comp with many text layers corrupted last week and have seen no update in the interim. I avoid using CS PS6 for editing files with text layers, especially complex files where reconstructing corrupted layers takes lots of time. I recommend using another tool for website comps and similar text layer intensive use.

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 30, 2012 7:47 PM   in reply to Chris Cox

    This is a MAJOR, MAJOR bug! A month later, still not fixed!!

     

    Adobe knew about this back in April, during the beta phase -- http://forums.adobe.com/message/4308699 -- but they still rolled it out without it being fixed.

     

    When can we expect this to be fixed??

     
    |
    Mark as:
  • Noel Carboni
    23,514 posts
    Dec 23, 2006
    Currently Being Moderated
    Jul 31, 2012 9:00 AM   in reply to jaspman

    jaspman wrote:

     

     

    When can we expect this to be fixed??

     

    As stated above, we cannot reasonably expect any answer to that from Adobe.  We can only hope a 13.0.1 update is just around the corner.

     

    See post 42 in the following thread for some thoughts I've had on the subject...

     

    http://forums.adobe.com/message/4575278

     

    -Noel

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 31, 2012 11:12 AM   in reply to Noel Carboni

    Hi everyone,

     

    I just wanted to update you all on the status of this text corruption bug. Engineering has finally identified the source of the bug, which relates to changes that were made to implement the background save feature in CS6. It was a very hard problem to identify (scripting is also a factor), and is related to issues in other parts of the Photoshop code (Acrobat TouchUp workflow, for example) that we have encountered since CS6 was released. I think it's fair to say the background save changes either exposed for the first time, or otherwise exacerbated problems that have been lurking in the Photoshop code base for some time. Such is life in software development.

     

    But getting back to the text corruption issue, unfortunately, just turning off background save will not prevent the problem, which is consistent with what users have reported around this bug. And once the corruption has occurred, the problem is in the PSD file, and the lost text is not salvageable. At this point, we have no workaround to offer that will prevent these problems from occuring.

     

    I know this is not good news, and I again apologize for the problems this has caused many of you.

     

    We are working hard to get a fix ready, although as I indicated before, I can't comment in detail about when or how this will be made available. We are working first on a very specific, very targetted fix for this text corruption problem, while we also continue to investigate what other parts of the application may be affected by the underlying bug. As I have further information, I will share it with you, in the meantime, we greatly appreciate your patience and help in resolving this.

     

    Paul

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 31, 2012 12:51 PM   in reply to PDFerguson

    Thanks for the detailed update. What's most disconcerting is not just the very serious nature of the bug but that Adobe knew about it BEFORE releasing CS6 for sale and didn't inform buyers about it. Because it is such a major bug, that would have been the most customer friendly tack to take. It seems that the rush to release and bring in the bucks was more urgent than to prevent expensive problems for a lot of unwitting buyers.

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 31, 2012 12:58 PM   in reply to jaspman

    i hope they arent saying we'll never be able to restore those files sounded a bit ambigous as to the future.

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 31, 2012 3:09 PM   in reply to ubernaut

    ubernaut_4 wrote:

     

    i hope they arent saying we'll never be able to restore those files sounded a bit ambigous as to the future.

    PDFerguson said: "And once the corruption has occured, the problem is in the PSD file, and the lost text is not salvageable."

     

    Doesn't sound in the least bit ambiguous to me.

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 31, 2012 3:25 PM   in reply to pf22

    yeah but in the next sentence Paul did sort of hedge it a bit and "At this point, we have no workaround to offer that will prevent these problems from occuring." Seems to me there should a way to salvage since some of the data for those layers obviously exists but is just reassigned.

     

    i did say "a bit" and "hope" also…

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 31, 2012 3:26 PM   in reply to pf22

    I salvaged a damaged file, but it wasn't easy. The text itself is preserved, but it moves to a different layer and inherits different coordinates and properties as each text block "switches seats". I saved a copy and screen capture of the file so I could see the original design and then worked on reformatting and repositioning the messed up text layers. I did the rework in PS CS5 and the file seemed to be okay after rework, but perhaps it's a ticking time bomb now?

     
    |
    Mark as:
  • Noel Carboni
    23,514 posts
    Dec 23, 2006
    Currently Being Moderated
    Jul 31, 2012 3:30 PM   in reply to ubernaut

    As a software engineer (I speak geek) I read that to mean:

     

    There's no hope of gettin' your corrupted data back and there's no known way to keep Photoshop 13.0.0 from doin' it again without a patch from us, which we're workin' our butts off to get to you without breakin' anythin' else.

     

    If the data truly is still in the file - even most of it - it would be Really Cool if someone with knowledge of PSD file structure could code up a dandy little fixer-upper program.  Adobe has done stuff like that in the past...  C'mon, Adobe.  Wow us on this one.

     

    -Noel

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 31, 2012 3:28 PM   in reply to BJN3

    ive been doing somethign similar but i have noticed even new layers also inherit the issue perhaps ocne the fix is out the new layers will stick, we can always hope.

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 31, 2012 3:39 PM   in reply to jaspman

    jaspman wrote:

     

    Thanks for the detailed update. What's most disconcerting is not just the very serious nature of the bug but that Adobe knew about it BEFORE releasing CS6 for sale and didn't inform buyers about it. Because it is such a major bug, that would have been the most customer friendly tack to take. It seems that the rush to release and bring in the bucks was more urgent than to prevent expensive problems for a lot of unwitting buyers.

     

    We had one or two reports, but were not able to discern a pattern of problems, nor did we have a reproducible case to look at until after CS6 had been released, so to say we knew the extent and seriousness of this bug before releasing CS6 is not accurate. During our beta cycle, we deal with literally thousands of bug reports, crash logs, and miscellaneous problems that our users report. Many of these turn out to be unreproducible, edge-case, or one-time occurences, or are caused by extraneous, external hardware or software problems (e.g. video drivers). We try our best to identify and fix serious problems before release, but to expect perfection in that process is not realistic.

     

    I am sorry this one slipped through, but all I can do is assure you that we are giving this the serious attention it deserves and are working hard to resolve it.

     

    Paul

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 31, 2012 5:11 PM   in reply to PDFerguson

    Someone at Adobe deleted part of my post above. I provided a link to a forum discussion -- http://forums.adobe.com/message/4308699 -- in which, on April 3, 2012, Pattie Foxhoven reported the following:

     

    ---------------------------------

     

     

    Hi all-

     

    I can reproduce this and I have logged a bug on this one. Thanks for all the feedback. You guys are great!

     

    Pattie

     

    --------------------------------

     

    Release date was May 7. So Adobe did have reproducible cases well BEFORE release.

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 31, 2012 5:52 PM   in reply to jaspman

    Someone at Adobe deleted part of my post above. I provided a link to a forum discussion --

    jaspman,

    To my knowledge the text bug you reference, which Pattie is acknowledges, is a different bug from the thread topic. 

     

    Your bug  has to do with transforming (scaling) text layers.. then the incorrect font size is shown when the multiple layers are targeted. It is easily reproducible. 

    The thread topic is about whole text layers being permanently replaced with other text layers from the same document. A much more troublesome issue, and MUCH more difficult to reproduce.  That may be why your post was edited.

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 31, 2012 6:05 PM   in reply to jaspman

    We didn't get a reproduceable case for THIS bug until mid-June (and we'd been trying since the beta).

    It took the right files and the right steps to reproduce the problem, and those weren't easy to get.

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 31, 2012 6:37 PM   in reply to Chris Cox

    I see. My confusion on the other issue.

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 6, 2012 11:35 PM   in reply to jaspman

    Hi everybody, I've have the same problem, I was editing bigger PSD of website one morning and suddenly every txt layer went crazy. After re-install photoshop with no effect I've found this thread. The work with corrupted PSD is also slower. Each click at layer pallete takes 2-3s Thanks for solving this in future, I know you are doing great job. I'm fan of Photoshop from the version 3 from mid 90s.

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 13, 2012 2:35 PM   in reply to DusanKonecny

    Just checking in on the status of this issue...

    I'm still using CS6 - mainly becuase I don't own an earlier version (I subscribe to Creative Cloud--greatest thing ever). I wonder if Adobe would be willing to give me CS5 to use until this bug is fixed? I haven't lost anything major yet - most of my work isn't too text heavy, but I've had a few instances where I was forced to rebuild parts of my files. What worries me is what if some text is corrupted and isn't noticed in the proofing stages and it goes to print - I'll be liable for any damages. We all know how often things are missed on proofs.

     

    (I fell in love with Photoshop in September of 1992 and there hasn't been very many days that I haven't used it since! I compare Adobe products to Apple products - far superior to all of their competitors)

     
    |
    Mark as:
  • Noel Carboni
    23,514 posts
    Dec 23, 2006
    Currently Being Moderated
    Aug 13, 2012 4:20 PM   in reply to SabienSJ

    13.0.0 is still exactly as functional as it ever was, and 13.0.1 hasn't been seen yet.  We're all waiting anxiously for it.

     

    Honestly, if I had a lot of critical text work and I'd seen evidence that my copy of Photoshop CS6 was experiencing this text bug I might well consider using an older version of Photoshop.  No one wants corrupted files!  Adobe has mentioned it being a timing glitch uncovered by Photoshop's new "save in the background" changes, so it's not a given that everyone will experience it I suppose.

     

    I admire the positive tone of your closing comment, but Adobe doesn't really have competition, and Apple is far superior to...  what exactly?  There's no equal to an iPad, but as far as computers go I have a Dell Precision Workstation that's every bit as good as my chief engineer's Apple Mac Pro - both systems are simply excellent.

     

    Based on the traffic here on the forum, it seems there are more Photoshop CS6 glitches overall being reported by Mac users.

     

    -Noel

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 13, 2012 4:53 PM   in reply to Noel Carboni

    AFAIK this particular text bug is cross-platform.

    And I would question Noel's anecdotally based assumptions about PsCS6 "glitches" and Macs.

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 13, 2012 5:36 PM   in reply to charles badland

    not to add fuel to the fire and start a pc/mac flame war but am i the only one whos finds it ironic that Noel's engineer is using a mac and she as either a designer or someone who is involved enough in design to be involved in this thread is using a pc?

     

    sorry i had to

     
    |
    Mark as:
  • Noel Carboni
    23,514 posts
    Dec 23, 2006
    Currently Being Moderated
    Aug 13, 2012 6:29 PM   in reply to ubernaut

    Actually I'm a career software engineer myself.  I just happen to own my own software company.  My chief engineer and I share about the same number of decades experience in software engineering (about 70 years between us), and have worked together for nearly 30 years.  We both go back to times well before there was a Microsoft or Apple, when computers took up whole rooms, and both have experience with both Mac and PC platforms.

     

    I'm actually about as platform-neutral as anyone you'll find.  I like all computers. 

     

    The plain and simple fact is that Windows and OSX are both solid modern operating systems.  When well setup and managed, both can deliver a good user experience, and professional level results.  Whether one is "better" for a particular individual or another is entirely up to that individual.  Given that Apple does not license OSX for use in a virtual machine, a Mac has a slight advantage as a development system, since a PC, while technically quite capable of running a virtualized OSX system, can't legally be used to do so.

     

    And I'm a "he", by the way.  Click on my avatar some time.

     

    -Noel

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 13, 2012 6:33 PM   in reply to Noel Carboni

    sorry about the confusion regarding your sex.

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 13, 2012 7:37 PM   in reply to ubernaut

    You should apologize for apparently not reading the thread before posting or you'd have picked up on Noel's software engineering background. And you seem to have some platform stereotypes that you might want to revisit since there are professionals in many fields who post here and who use either one or both platforms. It's not ironic to design on a PC nor develop on a Mac, and no...you didn't have to.

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 13, 2012 8:00 PM   in reply to BJN3

    settle down now

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 21, 2012 10:55 AM   in reply to ubernaut

    so there is some hope for these files i have one file which i have continued to use while wating for the fix and it has gotten somewhat better then it was at one point. at it's worst any new text layers would also catch the currpution but now in this file new layers are no longer corrupted even after saving and re-opening. the older layers still go haywire upon editing.

     
    |
    Mark as:
  • Noel Carboni
    23,514 posts
    Dec 23, 2006
    Currently Being Moderated
    Aug 21, 2012 11:04 AM   in reply to ubernaut

    I can almost imagine random rearrangement of layer data occasionally causing data that was moved to be put back, but I wouldn't think that would be particularly encouraging.

     

    I'd love to find out that when they release the fix Adobe also makes available a handy utility that can straighten out (or minimize) the damage in a saved PSD files.  I have no idea whether that's even possible, but it sure would be a nice gesture from them if they could do so.

     

    -Noel

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 21, 2012 11:24 AM   in reply to Noel Carboni

    well in my case i have a file which i use to create title graphics for slider images. many of the layers are re-used and most of them would never need editing but not being able to add new savavble layers is certainly worse then then just not being to edit old ones, granted obviously both still suck. i agree completey with your comments regarding Adobe addressing what is at this point a wide spread customer support issue in addition to being a technical one.

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 27, 2012 2:12 PM   in reply to D.Estabrook

    Just wanted to add another (very) unhappy purchaser of CS6 .. this "bug" has now affected two projects and has cost me both time and money not to mention some client relation problems due to a missed deadline.

     

    Photoshop is the tool of choice for our detailed web comps and unfortunally for us these usually have many text blocks. Unacceptable.

     

    Please keep us updated on the progress of a fix or at least a workaround. And I agree with some of the other posters here .. this should really be told to any new purchasers of Photoshop CS6.

     

    Brian.

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 27, 2012 11:55 PM   in reply to jointmedias

    The same happened to me....
    "Clicking on any text layer it is replaced by text from another layer in my document".. in my file the new text frame has moved a bit left from the original position

     

     

    I do agree with 81.jointmedias: "this should really be told to any new purchasers of Photoshop CS6." The bug was causing me a major panic while I was editing a huge website presentation for a customer... the whole project with corrupted text layers was gone one morning. Fortunately I was able to recover the files from the backup files, but it took me a lot of time to figure it out what was causing the problem.. So, I'm back with Photoshop CS5 and the rest of our designers until CS6 update..

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 28, 2012 9:19 AM   in reply to D.Estabrook

    I appreciate your frustration with how long this is taking to resolve. There's not a lot more I can offer about the status of this issue; as I've already indicated, this is a top priority bug, and has received considerable engineering and test resources over the past weeks. We continue to monitor the forums for posts about this issue, and as soon as I can share more information about how and when this will be resolved, I will do so. Sorry I don't have more at this time, but please don't mistake the lack of information for a lack of concern or a lack of committment to fix this problem.

     

    Paul

     
    |
    Mark as:
Actions

More Like This

  • Retrieving data ...

Bookmarked By (1)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points