Another ACR 4.4 bug?

I noticed this post over on FM. An ACR/PS user encountered a weird issue where an ACR-converted image in PS went completely black when the mode was changed to LAB inside PS. The issue was resolved when he went back to v4.3.
Has anyone else seen this or can they reproduce it if they have 4.4 installed?
The problem may have been related to the way the user installed/de-installed 4.4 and the situation is maybe a bit unique but if this is really a result of 4.4, I think it implies other problems than just EXIF data.
I am holding off on updating but if there is anyone who has already installed 4.4 and would like to try to reproduce the anomaly, it might be helpful for the community.
Link:
http://www.fredmiranda.com/forum/topic/628466

Ah, okay. Whew. I was able to revert to ACR 4.3.1 by doing the following (and it fixed the bug):
- Go to http://www.adobe.com/support/downloads/detail.jsp?ftpID=3822 and download the .8bi file (e.g., download to the desktop)
- Make sure your Bridge and PS programs are closed
- Copy the downloaded .8bi file to:
\Program Files\Common Files\Adobe\Plug-Ins\CS3\File Formats
- Restart bridge, open any file in RAW, and you'll see that the version at the top of the window says 4.3.1. Open the image
- In PS3, Lab color now works properly.
Best of luck to others with this issue.

Similar Messages

Changing Brush size in ACR 7.2 - bug oder feature?

The update to ACR 7.2 changed the way the adjustment of the brush size is behaving. Before one pressed the right mouse button and moved left or right to change the size. Now it's not just left to right but right to left or up and down depending on where the tiny mouse indicatior on the outmost circle is placed. The has as an effect that it's not immediately clear in which direction the mouse has to be moved to change the size. Also the brush circle is move to the side while adjusting and is not congruent with the brushcircle after releasing the mouse botton.
Any ideas if this is a feature or a bug?

The ACR7.3 update did not fix the brush resize problem on my system either - also Win7x64 Ultimate, Ps 13.0.1 (currently I use only the x64 install but the problem exists with ACR hosted in the 32-bit install as well) and ACR 7.3.0.71.
Another annoying thing I've noticed with 7.3 (maybe it was there before 7.3 but I never noticed it) is that even if you set the Feather slider to zero pixels, as soon as you set the brush size to 10 pixels or more, the brush is shown as being feathered. Maybe the 10 pixel cutoff is related to my screen size and resolution: 1920x1200 and 88ppi (NEC MultiSync LCD 2690 WUXi2) but it is still disconcerting at any size.
The unexpected movement of the centre of the brush when you right click reported by the OP, another annoying characteristic, is always towards the centre point of your screen. If you are left of centre, it moves right and vice versa. If you are above centre it moves down and vice versa. Combinations move diagonally towards the centre.
Eric Chan seemed to acknowledge the mouse right-click brush resize and brush centre movement problems with ACR 7.2 in his post #1. Looks like he's forgotten us or has been too busy with other matters. Either way , it would be nice to hear from him again with an update.

ACR 6.3 Bug - Introducing Noise

I just upgrading from CS4 to CS5 the other day for PS, including 6.3 of ACR. I've had something happen in the workflow of the images I'm working on, but you can duplicate it below (or tell me if you can't).
In PS, create a 200x200 pixel image. Fill with white. Save as a .tiff . Close the file.
Open Bridge. Find file. Open in Camera Raw. No adjustments. Click open, to open it in PS.
Back in PS, make a levels adjustment layer. Drag the black point all the way to the right. Check out the random grey noise like pixels that have suddenly appeared everywhere. Try it with default settings in ACR, change anything you want. I can't get them not to appear.
I don't think this is just me. Anyone else want to verify?

function(){return A.apply(null,[this].concat($A(arguments)))}
sjlocke215 wrote:
I would prefer not to add another two steps to my workflow by processing this or that way to get around it.
I agree that the dithering regardless of settings is a bug - the Camera Raw color transform should respect the Color Settings choice you have made in the Color Settings preferences panel of Photoshop, and it does not:
Are you opening your images into Photoshop?
If you set the converter to output 16 bit data, then just work in Photoshop with the 16 bit data, then Save As or Save For Web & Devices there aren't really extra steps... And all your processing will be in the more accurate 16 bits/channel color depth, which yields better quality images overall.
I would also suggest converting to the ProPhoto RGB color space to avoid channel clipping due to gamut issues.
It's pretty clear that because of quirks in Camera Raw, extra steps may be warranted to get the best possible image quality.
-Noel
P.S., There was another thread where this was discussed extensively, mid to late last year.

Another Edit in Photoshop bug

When I highlight an image and select "Edit in Photoshop" the image opens in Photoshop just fine.
The problem arrises when I am finished editing and click "Save" in photoshop. The edited image does not appear in my Lightroom Library. Instead, I only see the original image. The really quirky thing is that the original now has bars on each side of it indicating a stack and the little white square appears at the top left displaying "1 of 2". If you hover over it with the mouse a pop-up says "This image is part of a stack" But if you double click it or choose "Expand stack" it still only shows the one image.
What gives? Both 2.0 & 2.1 have this issue. I never experienced this in 1.X so the bug is new.

Jao,
Nope. Everything is just as it was when I used LR 1.X together with CS3. I upgraded to LR 2.0 and CS4 about the same time so it could be an issue with either but I suspect it is in LR.
Here is another quirk I just discovered...
If I double click on the white square indicating the number of photos in the stack, both images (the PS edited & the original) show up in LRs compare view on my second monitor. The edited image still does not show in my Library screen even though it's on the second monitor in compare view. Strange.

Yet Another 8.0.2 bug

With 8.0.2 (at least with PHP/MySQL) you can no longer use a
variable in your custom SQL more than once. You must specify
"duplicate" variables. For example - I want to find all records
where either SCORE is equal to a passed URL parameter or PLACE is
equal to the same URL parameter. This will NOT work anymore:
SELECT * FROM mytable
WHERE score =
varTheParam OR place =
varTheParam
Define your varTheParam, try to test the results and you get
yelled at because varTheParam is undefined. Your SQL must be like
this:
SELECT * FROM mytable
WHERE score =
varTheParam OR place =
varTheSameParamAgain
Now, define your varTheParam and varTheSameParamAgain -
setting them both equal to the same thing. A waste of resources
here.

Come on 8.0.3 update....or just reinstall 8 and not the
latest update. :-)
"Tom Muck" <[email protected]> wrote in
message
news:e7eida$bcf$[email protected]..
>
> "abtech123" <[email protected]> wrote
in message
> news:e7ei9g$b3s$[email protected]..
>> With 8.0.2 (at least with PHP/MySQL) you can no
longer use a variable in
>> your
>> custom SQL more than once. You must specify
"duplicate" variables. For
>> example
>> - I want to find all records where either SCORE is
equal to a passed URL
>> parameter or PLACE is equal to the same URL
parameter. This will NOT work
>> anymore:
>
> Good catch. Just another in the long list of severe
recordset bugs in the
> 8.0.2 updater.
>
> Tom
>

ACR 7.3 Bug on Adjustment Brush tool - changing brush size problem.

I update photoshop and using ACR 7.3 and now having big problem when I use Adjustment Brush took. Phe problem is when try to change brush size with holding right mouse button and moving the mouse. Behavior completely changed and its impossible to predict if I move mouse right what will happen.
Please check solution for it. old behaviour was great. I think this is not new feature, its bug.
Thanks in advance.

No need.
Already bugged and acknowledged: http://feedback.photoshop.com/photoshop_family/topics/bug_crash_adjustment_brush.

Another serious AI SDK bug!

Yes, I found another one. This time it is the:
AIAPI AIErr(* CopyArtToEntry )(AIDictionaryRef dictionary, AIDictKey key, AIArtHandle art)
AIAPI AIErr(* CopyEntryToArt )(AIDictionaryRef dictionary, AIDictKey key, short paintOrder, AIArtHandle prep, AIArtHandle *art)
the art is a placed art. These 2 APIs work only during the working session, it acts crazy when you save the file and reopen it.
Instead of getting the image of the placed object, you will get its bounding box only. Just letting you know to not wasting much time on this bug.
There is a work around for it, though, but quite nasty!

I think I'm still a bit confused about the different uses of AIUIDRef vs. AIUIDREFRef.
AIUIDREFRef seems to be an unnecessary extra layer on top AIUIDRef. I have been up until now using AIUIDREFRef for everything, though at this point I can't remember why I arrived at that solution. What is the purpose of using one vs the other?
And also, is it necessary to release the reference here? Doesn't this get cleaned up automatically when the variable loses scope?
I'm not clear on the use of AIUIDREFRef either, except for how what you mention and its similar use in dictionary code. That said, I can pretty much guarantee it doesn't clean itself up because its not a class with no destructor; its just a typedef to a struct, so I don't see how it could release itself.
I have to admit my main use has been in refereing to layers -- I find that's a much safer way to hang on to a layer than its layer handle. Sometimes I get nasty results & crashes when I talk to layers that are deleted, and sitting somewhere in the undo stack. The AIUIDRefs seem pretty safe. That said, for me they're either stored in dictionaries or refer to layers so maybe that's why they work for me. I can say in those two cases I don't see any of this undo problem.

Well...ANOTHER FLASH 8 BIG BUG...!

Hi!
Another Flash 8 Bug...this must be bug number (N! n=3000)
:rolleyes:
A simple tween animation which won't work if these 2 frames
are together side-by-side. The solution: Add a blank frame between
them...& voilà! It works like it should..
I've attached both simple examples
HERE.
One with the bug and the other one without it (with the drive
through to the solution).
Just see it for yourselves and tell me if I'm wrong or what.
However, this is the 2nd time I've faced this bug in 2
different flas of mine.
Perhaps it's Flash 8 Spanish version? This is why I've
attached the swf aswell.
This is really annoying. It took me a couple of hours to get
this silly solution due to this bug (once again).
I've also noted that depending on the Player version
(specially the newest version) some guided shape tweens on
previously released swf files, stop from working properly.
Is there a Macromedia place where you can inform about these
bugs and attach a self-explainatory fla file?
I'm really looking forward to v9...
Please, after downloading this example, confirm if this is
also happening to you (just to discard a bug from the Spanish
version and extend it to any other version).
Thank you very much!
Cheers!

weird! the playhead actually does play the rest of the
timeline in your movie clip - yet the tween
wont play - i copied/pasted the tween to a new doc and it
plays fine when tested - so it is
sosmething else that is causing it - you have a lot of code
in various places setting alpha for
stuff - but i dont think thast is the issue. just not sure
why this is - the text is not a font so
it is not a case of embedding it - weird. test just the movie
clip (Ctrl + Alt + Enter) and click
button - you will see playhead play but tween not work.
--> **Adobe Certified Expert**
--> www.mudbubble.com
--> www.keyframer.com
Manare wrote:
> Hi!
> Another Flash 8 Bug...this must be bug number (N!
n=3000) :rolleyes:
>
> A simple tween animation which won't work if these 2
frames are together
> side-by-side. The solution: Add a blank frame between
them...& voil?! It works
> like it should..
>
> I've attached both simple examples
>
http://personales.ya.com/pruebas2005/Another_BUG_&_Drive_through.rar.
One with
> the bug and the other one without it (with the drive
through to the solution).
> Just see it for yourselves and tell me if I'm wrong or
what.
> However, this is the 2nd time I've faced this bug in 2
different flas of mine.
> Perhaps it's Flash 8 Spanish version? This is why I've
attached the swf aswell.
>
> This is really annoying. It took me a couple of hours to
get this silly
> solution due to this bug (once again).
>
> I've also noted that depending on the Player version
(specially the newest
> version) some guided shape tweens on previously released
swf files, stop from
> working properly.
>
> Is there a Macromedia place where you can inform about
these bugs and attach a
> self-explainatory fla file?
> I'm really looking forward to v9...
>
> Please, after downloading this example, confirm if this
is also happening to
> you (just to discard a bug from the Spanish version and
extend it to any other
> version).
>
> Thank you very much!
> Cheers!
>

Another behaviuor of the Bug 272219

Hi.
Maybe you know the following bug:
Bug 272219 (Oracle 7.3 to 10.1 and all versions in-between), and Metalink forum discussion 149572.999.
You cannot create a trigger on a table if the table has a column named the same as the column 's data type.
Today I found another very unpleasant behaviour of the same bug - when executing DML from PL/SQL block. Consider the following example:
CREATE TABLE t1("DATE" DATE);OK.
INSERT INTO TABLE t1 ("DATE") VALUES (Sysdate)OK.
BEGIN INSERT INTO TABLE t1 ("DATE") VALUES (Sysdate); END;PL/SQL: Compilation unit analysis terminated
PLS-320: the declaration of the type of this expression is incomplete or malformed
Best regards, Beroetz

Just today I had a problem with a VI with a diagram disable structure that would compile but the FP of the executable was mallformed and cause the whole app to crash.
So I stay away from diagram disable structures in execution code.
Ton
Free Code Capture Tool! Version 2.1.3 with comments, web-upload, back-save and snippets!
Nederlandse LabVIEW user groep www.lvug.nl
My LabVIEW Ideas
LabVIEW, programming like it should be!

ANOTHER Java NIO Socket Bug??

I think I'm being really dense here but for the life of me, I can't get this code to work properly. I am trying to build a NIO socket server using JDK 1.4.1-b21. I know about how the selector OP_WRITE functionality has changed and that isn't my problem. My problem is that when I run this code:
if (key.isAcceptable()) {
     System.out.println("accept at " + System.currentTimeMillis());
     socket = server.accept();
     socket.configureBlocking(false);
     socket.register(selector, SelectionKey.OP_READ | SelectionKey.OP_WRITE);
if (key.isWritable()) {
     SocketChannel client = (SocketChannel)key.channel();
     System.out.println("write at " + System.currentTimeMillis());
if (key.isReadable()) {
     SocketChannel client = (SocketChannel)key.channel();
     readBuffer.clear();
     client.read(readBuffer);
     System.out.println("read at " + System.currentTimeMillis());
}the isWritable if statement will always return (which is fine) and the isReadable if statement will NEVER return (which is most certainly NOT FINE!!). The readBuffer code is there just to clear out the read buffer so isReadable is only called once per data sent.
This SEEMS to be a bug in how the selector works? I would expect to see isReadable return true whenever data is sent, but that is not the case. Now here is the real kicker ;) Go ahead and change this line:
socket.register(selector, SelectionKey.OP_READ | SelectionKey.OP_WRITE);to this:socket.register(selector, SelectionKey.OP_READ);And now it appears that isReadable is running as expected?! To let people run this code on their own, I have uploaded a copy of the entire java file here:
http://www.electrotank.com/lab/personal/mike/NioTest.java
Please forgive the code, it's just the smallest test harness I could make and much of it is lifted from other posts on this forum. You can test this by using Telnet and connecting to 127.0.0.1:8080. You can test the isReadable piece by just typing in the Telnet window.
Someone else has listed something as a bug in the Bug Parade, but the test case is flawed:
http://developer.java.sun.com/developer/bugParade/bugs/4755720.html
If this does prove to be a bug, has someone listed this already? Is there a nice clean workaround? I'm getting really desperate here. This bug makes the NIO socket stuff pretty unusable. Thanks in advance for the help!!
Mike Grundvig
[email protected]
Electrotank, Inc.

Yeah, isReadable crashed for me too.
My solution was to not call it. I set up two selectors for the two operations I wanted notifying (accept and read) and used them independently in different threads. The accept thread passes them over to the read thread when they're accepted.
This way I don't need to call isReadable since it is bound to be readable otherwise it wouldn't have returned, as read is the only operation I'm being notified about.
--sam

Another WRT600N storage link bug with Vista

Yet another annoyance with the WRT600N and Vista. Files made by the vista box on storage link (or made by xp, mixed system) suddenly become "write protected" but not really. Upon trying to delete files on this storage linked media, I get this error message:
An unexpected error is preventing the operation. Make a note of this error code, which might be useful if you get additional help to resove this problem: Error 0x8007045D: The request could not be performed because of an I/O device error.
This seems to be a permissions snafu between the linked storage and Vista. The XP box can usually delete this stuff. Checking properties shows it to be completely free of read only or other flags that would prevent the deletion.
Any idea?

I'm getting the same problem only with the Linksys WRT650N router. I have a 1TB Cavalry USB drive connected, formatted NTFS (by Vista). I have Vista Business x64. 4gig RAM, AMD Athalon x2 6400 @ 3.4Ghz.
If I repair the LAN connection I can delete two files and then it goes back to saying I don't have the permissions.
Micorsoft says it's Linksys' problem. I haven't talked with Linksys because I just know they are going to say it's MS' problem.
Anyway, anybody have any ideas or solutions to this problem?

Colour Labels being reset when changing from one to another. Possibly a bug?

For some time I have suspected that I was "loosing " images that I had filtered based on their colour label. I have narrowed it down to changing the colour label of an image in just one particular way.
I think that the errors occured in in Lightroom 3 but they it always occurs in version 4
Using Develop mode
I label several images to one colour eg blue
In the filmstrip using the colour label filter select for example blue and purple which will still show all the images labelled as above
Using the colour buttons on the toolbar under the image, change the colour label of an image to purple, Since the filter is set to blue and purple the image should still be present in the filmstrip but it is missing
Searching for the image via other means eg filename I find that the colour label has been reset to none instead of changing to purple
This only happens if the colour change is done using the toolbar buttons, using any of the text menus that access the colour labels the problem doesn't occur.
The error is not limited to blue and purple labels
Am I missing something? Can anyone replicate this ?
regards
Wes

I can replicate this when using toolbars.
This doesn't seem to happen when I use the keyboard.
I can remember more older bug reports related to using the toolbar in conjuction filters. Somehow the codepath and behaviour is different the when using keyboard shortcuts. Go figure...

Another Spectral View Tool Bug

If I change the Tool type in Spectral Frequency Display the on screen mouse pointer changes to reflect the new tool type but the operation doesn't actually change until I have clicked on the screen once with the new tool.
Example: Have been using the Marquee tool to select an area, say, between 1K and 5K and processed an effect on that area. If I then change to the Time Selection tool the mouse pointer changes to the "I" bar. If I then double click in the marker area to select a Range it selects that region correctly by time but only the 1K to 5K frequency range. I have to click in the audio display area to make the Time Selection tool work correctly before I can select the Range in the Marker bar. In AA 1.5 this worked OK without the extra clicking.
Also with AA 1.5 if you had an area selected with the Marquee tool and then changed to the Time Selection tool the selected area would instantly reflect that change by keeping the same time selection but making it full bandwidth. In AA 3 I have to click away from the original selection to make the Time Selection tool active and then try to reselect the same time range again with the mouse.
Sorry this is so long but trying to give all the facts about these annoying bugs takes a lot of explanation.

Hello Ryclark.
I can confirm that the behaviour of both versions of the program under the given circumstances are as you describe.
I've had an extremely brief play around with some options in the Preferences box, and I've been unable to alter the selection behaviour.
Regards,
Steve.

Switching between Acrobat DC / XI window and another application - cursor selection bug (video and test files attached)

Hi,
When I have Acrobat XI or DC open along side InDesign (or other programs like Acrobat or Word), I run into a bug where upon switching from InDesign to Acrobat, the mouse cursor automatically selects a bunch of text in the Acrobat PDF with a spinning beach ball, and I have to click around multiple times to release it from whatever text it has selected. It is annoyance I noticed in a few versions of Acrobat now, and I had hoped the bug would be fixed in DC. The only way to prevent this from happening is to click anywhere else on the Acrobat window (eg the menu bar or the side tools panel, but not the PDF itself).
Video describing the problem: https://imgur.com/dXurXcB
Note that no clicking is taking place when switching windows from InDesign to Acrobat - the text in the Acrobat window is being selected automatically by the bug.
If you watch the video carefully, you will also notice that the Acrobat window does not look like it is taking focus during the selection bug - it only takes the focus after clicking around multiple times.
Test documents used to record the video:
http://s000.tinyupload.com/?file_id=14619964329420357364
InDesign CC File
http://s000.tinyupload.com/?file_id=18294837115907237178
PDF File
Computer:
Model Name: MacBook Air 2013
Model Identifier: MacBookAir6,2
Processor Name: Intel Core i7
Processor Speed: 1.7 GHz
Number of Processors: 1
Total Number of Cores: 2
L2 Cache (per Core): 256 KB
L3 Cache: 4 MB
Memory: 8 GB
OS: Yosemite 10.10.1

Thanks for the reply. I think the issue is just confined to Mac machines + Adobe products (this issue doesn't occur when I switch from Word Preview 2016, or Office 2011). I can confirm this issue occurs on more than one Mac as well.
Here is a slightly larger GIF if the first was too hard to make out
https://i.imgur.com/CNKnkC0.gif
It's almost as if the text manipulation / selection from InDesign is carrying over to the Acrobat window, interrupting the normal focus it should get on first click...
Edit: It just occurred with Spotify - Switched from Spotify to Acrobat, with a scanned image PDF. The rectangular selection tool tries to grab a region of the image several times before focus returns to the Acrobat window. It also just happened after manipulating images and text in Word 2016 Preview and Word 2011.

Another 7.6.1 bug...

Yup!
My internet connection always been fine and quite fast...
Since 10 days or so I updated my Time Capsule to the new
7.6.1 Firmware and now my result on Speednet is...
0.60 Mps in download and 0.95 in upload
This is brutal?!?
When I plug the modem straight into my laptop I
get my usual good signal back...
What's going? Why everyone's having similar problem with the time capsule?

Hi Elias -- I'm also in Brazil, will keep the subject in English so other may find it later.
I'm in São José dos Campos, SP -- we had 35-38 degrees C last week (for me if feels like eight hundred degrees :-), the heat may be one reason.
Since I had work to do I've bypassed the TC connection and plugged the ethernet cable directly on the MBPro. Connection was 5mbps via ethernet. My TC was left on for a day, her blinking amber led pleading for love or at least attention, but I am an unforgiving *******.
The next day I've plugged everything back and got my 5mbps wireless connection. It may be because the TC was "cooling off" for a night, it may be because she felt rejected and decided to mend her ways, I am not sure, but anyway I will try this approach next time instead of wasting hours fiddling with the airport settings.
thanks for the tip!
Rafael

Another ACR 4.4 bug?

Similar Messages

Maybe you are looking for