RAW bug

Be gentle, I normally don't post unless I've exhausted all my options. I'm generally very patient but the problem I'm experiencing is incredibly frustrating.
Running CS5, with most recent updates on a late 2009 17" macbook pro (unibody)
As of the last major update (I believe it was 12.0.1) whenever I open a .CR2 I run into 2 issues:
1. When the image is magnified and I hold down spacebar so that I can navigate the image, the image jumps back and forth as I try and move it any direction with a click and drag. The cpu is not stuttering however it appears as if I'm playing tug-a-war with the program.
2. When the image is at anything less than 50% (ie: 33%/fit to screen) some of the changes I've made to the image (ie: noise reduction/spot removal) do not appear on the image - basically it looks like I haven't applied the said change. If you're thinking, "Well at 33% who could see such something like a spot removal," I assure you, this isn't the case.
Has anyone else experienced this? Is there any resolution yet or one on the way?

Story_Lab wrote:
…I never had that problem before the update
If youre referring to the ACR update, try posting in the Adobe Camera Raw forum. The ACR team is pretty active there:
http://forums.adobe.com/community/cameraraw

Similar Messages

Issue w/ OSMF DVRCast w/ use of 'raw:' (bug?)

I am having some issues with his OSMF player and DVRCast. I have started a dvr stream using the raw format prefix. I’m thinking it’s having issues with the “raw:”
These are the errors I’m getting.
DVRCast subscribe failed
Unexpected server response: NetStream.DVRStreamInfo.Failed
or
Error: Unexpected null parameter passed to method
                at DVRCastStreamInfoRetriever()[C:\Documents and Settings\User\My Documents\OSMF\OSMF\org\osmf\net\dvr\DVRCastStreamInfoRetriever.as:61]
                at DVRCastDVRTrait()[C:\Documents and Settings\User\My Documents\OSMF\OSMF\org\osmf\net\dvr\DVRCastDVRTrait.as:68]
                at org.osmf.net.dvr::DVRCastNetLoader/processFinishLoading()[C:\Documents and Settings\User\My Documents\OSMF\OSMF\org\osmf\net\dvr\DVRCastNetLoader.as:113]
                at org.osmf.net::NetLoader/finishLoading()[C:\Documents and Settings\User\My Documents\OSMF\OSMF\org\osmf\net\NetLoader.as:282]
                at org.osmf.net::NetLoader/onCreationComplete()[C:\Documents and Settings\User\My Documents\OSMF\OSMF\org\osmf\net\NetLoader.as:308]
                at flash.events::EventDispatcher/dispatchEventFunction()
                at flash.events::EventDispatcher/dispatchEvent()
                at Function/org.osmf.net.dvr:DVRCastNetConnectionFactory/private:onCreationComplete/org.osmf .net.dvr:onStreamInfoRetrieverComplete()[C:\Documents and Settings\User\My Documents\OSMF\OSMF\org\osmf\net\dvr\DVRCastNetConnectionFactory.as:186]
                at flash.events::EventDispatcher/dispatchEventFunction()
                at flash.events::EventDispatcher/dispatchEvent()
                at DVRCastStreamInfoRetriever/complete()[C:\Documents and Settings\User\My Documents\OSMF\OSMF\org\osmf\net\dvr\DVRCastStreamInfoRetriever.as:163]
                at DVRCastStreamInfoRetriever/onGetStreamInfoResult()[C:\Documents and Settings\User\My Documents\OSMF\OSMF\org\osmf\net\dvr\DVRCastStreamInfoRetriever.as:126]

Bug logged and tracked here - https://bugs.adobe.com/jira/browse/FM-942

Camera Raw Bug: Preview not the same after clicking OK

I am opening a Canon CR2 camera raw file. I dial in the exposure how I would like it in the Camera Raw dialog (8.8), but after I click OK, then image opens in Photoshop (CC 2014) and looks different. It looks more washed out. I took a screen shot of the image after it is opened and the camera raw dialog with the exact image. You can see the difference. I measured the pixel intensity just to make sure my eyes weren't playing tricks on me, and the image after it opens has a different exposure.
I use Spyder color calibration and a GeForce 670 with the latest drivers.
Stuck!!!

Also:
A lot more information about your hardware and software is needed.
BOILERPLATE TEXT:
If you give complete and detailed information about your setup and the issue at hand,
such as your platform (Mac or Win),
exact versions of your OS, of Photoshop (not just "CC", but something like CC2014.v.2.2) and of Bridge,
your settings in Photoshop > Preference > Performance
the type of file you were working on,
machine specs, such as total installed RAM, scratch file HDs, total available HD space, video card specs, including total VRAM installed,
what troubleshooting steps you have taken so far,
what error message(s) you receive,
if having issues opening raw files also the exact camera make and model that generated them,
if you're having printing issues, indicate the exact make and model of your printer, paper size, image dimensions in pixels (so many pixels wide by so many pixels high). if going through a RIP, specify that too.
a screen shot of your settings or of the image could be very helpful too,
etc.,
someone may be able to help you (not necessarily this poster, who is not a Windows user).
Please read this FAQ for advice on how to ask your questions correctly for quicker and better answers:
http://forums.adobe.com/thread/419981?tstart=0
Thanks!

Camera Raw 6.7/LR4.1 photos corrupted

I have Photoshop 5, LR4.1, Windows 7 64-bit, Camera Raw 6.7 and a Canon 5D Mk3.
When I import photos from the camera into LR4.1 some get corrupted with posterised type artifacting. While I quite like this from a creative aspect, it's not what is on the camera! This example is a bad one...my feeling is that it's a Camera Raw bug as it happens when I import using Bridge direct to my hard disk. Adobe may have rushed this version out a bit too quickly?

It's likely to be a hardware issue - Lr doesn't directly touch your files, but it does stress the kit.
Every other example like this (there have been many such posts, and I've had it myself) has been traced to hardware: either failing RAM, or - as in my case - a dying hard drive.
The Bridge dimension's unusal though - let's see what others have to offer about that - but from an Lr perspective this is hardware all the way.
How are you importing the files, incidentally? Card reader? Or USB straight from camera to computer? If it's the latter, please try the former.

CS6 Bridge caching bug

In this thread we discussed a problem with CS6 Bridge constantly re-caching layered Tif files:
http://forums.adobe.com/message/4473274#4473274
Since then a new related problem has been reported and discussed on other forums.
Sometimes Photoshop refuses to save a file, claiming the file is already open or in use by another program, even though no other programs are running.
Turns out that problem is caused by Bridge caching. If you have Tif support disabled in Camera Raw prefs, the save problem does not occur. If you go to Bridge and navigate to a different folder, the save does not occur or goes away.
I've tried to report this as a bug in the photoshop.com site, but that bug reporting process is confusing and I have no confidence is works. Anybody know a better way to report bugs?

Hab das mal auch versucht bei CS6 Bridge/Camera RAW: Bug with exposure sync zu melden...

Canon 5d Mk II - Repair Highlights issue

I recognized that in ACR 5.2 the Canon 5d Mark II has some
serious problems with Highlight recovery:
Yellows turn Red and Blues get desaturated.
It really keeps me from using it, thoug it usually is
an incredibly powerful adjust slider....
Anyone same problem?
Maybe an adobe camera raw bug.....
Nikolaus

> maybe a canon problem???
It is a combination of errors, none of them of Canon's (they do maintain their fare share, but not in this case).
1. The shot is overexposed: see the raw histogram:
http://www.panopeeper.com/Demo/NikolausMacheck_Adobe_0405_Hist.GIF
The overexposure affects much of the colored fluorescent tubes over the shop, but it does NOT affect the "fetons ...whatever" under "REPLAY" between the two doors.
2. ACR interprets the 5D2 raw data incorrectly. It sets the saturation level at 15600, while it is in fact 15760. This increases the apparent clipping, though the direct effect is limited to the sky.
3. ACR adds 0.4 EV to the exposure without telling it to you.
The above effects *together* push the "fetons whatever" tubes into clipping. This needs to be corrected by -0.6 EV "exposure", not by "Recovery".
However, all this won't help on the problem of color gamut: some of the resulting colors are simply not in sRGB. You need to reduce the brightness even more if you want to keep the colors inside sRGB.
Important note: if you switch in ACR to ProPhoto, you seem to have caught the proper colors. This is eye-wash. As your monitor is certainly incapable of displaying ProPhoto colors, what you see may be more pleasing than what you get with sRGB, but that is NOT the color, which can not be reproduced. You have to go back and take another look in order to see the "true" colors, for no printer and no monitor can reproduce that. Your only alternative is reducing the brightness.

Extending the beta! How to compose and post defect reports.

There is no such thing as bug-free software, and LR is no exception to that. Even more, v1.0 releases, even those with long beta programs, can be more brittle than expected. We've already seen a few things that look like real defects which could be addressed in a future release. This is normal and expected, and now a team at Adobe will be dedicated to maintaining the LR release into the future.
This posting is sort of asking the question "how can we help", with a fair bit of opinionated ranting of my own on the subject. Take my comments with a grain of salt, of course, but I'm not sure I say anything that hasn't already been said a million times before.
Firstly, is there a place where bug reports should be posted that Adobe will see? Is there a document that describes how Adobe would prefer such reports to come in, perhaps with suggestions for supplemental material they'd like to see passed along with the defect report? Not only does this provide a place where Adobe can track raw bug reports, it can make perturbed users feel better, since they've been able to do something specific and active.
Full disclosure: I am a software developer by trade, and I maintain shipped releases of code for a living. I know how I like to see problem reports and it drives me *crazy* when a we get a vague report formatted with no punctuation, in all lower-case, containing no specific details. Usually these come with bizarre screen-shots embedded into a Microsoft Word file. Not helpful.
It drives me crazy because I know there is a bug in there somewhere, it just isn't necessarily the bug seen by the end-user or understood at first blush by the developer. I call this the "real bug", and it can be hard to suss out, sometimes.
I assume that the following basics are /probably/ helpful when reporting defects against LR v1.0:
- System details. At least the exact platform version and release. Possibly with a short run-down on CPU speed, amount of RAM. Mac users should probably be sure to clarify what CPU they are running.
- Clear steps to reproduce, if possible. Describe the problem exactly as you see it, being sure to use the language and nomenclature that the application uses. Capitalize app-specific controls exactly as you see them in the app, to make it clear what you are doing.
Try to reduce the problem to the barest set of operations.
- For things like "hangs" and "crashes", I'm guessing that most supported platforms have a way of capturing these details. I cannot and will not speak for Adobe. But! if I was looking at a crash or hang, I'd want any and all crash logs (OS X) or Dr. Watson (Win32) that were related to the former and the sample output (OS X) or Process Explorer dump (Win32) for the latter.
Details on how and where to post defect reports would be nice. Sounds like a FAQ item, at the least!
Finally, here are some things that drive me crazier and I feel are *not* helpful:
- Defect reports that intersperse observed behaviour with guesses about what the problem really is. No one knows better the potential places where symptoms could stem from except those people maintaining that codebase. I'm a smart guy and code for a living. I would never presume to know the precise inner-workings of Lightroom without access to the source and probably a run at it in a development environment.
- Arguing for how terrible or disastrous a particular "bug" is, and how it needs to be addressed as critical for immediate correction. Everyone, including me, finds their own bugs most critical. The problem is that software maintenance requires putting everything into perspective, evaluating each defect on its own merit, as well as how risky a fix for the defect might be. This last part cannot be minimized. Changing code incurs risk. The idea is to carefully shepherd a new release into each new version while maintaining integrity and stability. No matter how bad a bug is, introducing a fix that simply

I agree with how you think bugs should be reported. For now, I'd suggest posting them here, in detail. Some of us can relay them to the appropriate places, at least until we hear from Adobe personnel about an official location or method for the average end user.
Lee Jay

5508 WLC - VPN disconnects from Wlan guest

Strange issue that our support staff is seeing on our guest WLAN.
I have 2 wlans, 1 is production and authenticates our Domain controllers, this is working fine.
The other is a wlan that has restricted access internally, I allow http, https and VPN access out only.
It appears that on the guest wlan, after random amount of time an established VPN connection using Cisco VPN client disconnects.
Wireless connectivity doesnt appear to go down, just the vpn connection.
On this guest wlan, I have configured QOS bronze and I read a link where this may be affecting the UDP conversation between VPN client and end point.
Can anyone shed light on this ?
I just upgraded to latest and greatest code and I am still seeing same issue.
Cheers
Dave

Soemthing I want to make you aware of is another guest bug we hit... After fixing the VPN problem by moving to 7.0.220.0 we hit this bug!
The fix ... Reboot your WLC weekly. We have a call with Cisco BU on Monday to talk about this...
http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCtx00942
Webauth stops redirecting after some time
Symptom:
It is seen on 7.0.220 4404 WLC that users in the webauth SSID are not redirected to the login page anymore after 1 week or so.This message appears :
sshglue.c:7009 WebAuth HTTP Redirect rule creation failed for peer 192.168.1.8
Conditions:
webauth, 4404 running 7.0.116/220
Workaround:A reboot solves the problem for another week or so
Status
Open
Severity
2 - severe
Last Modified
In Last 7 Days
Product
Cisco 5500 Series Wireless Controllers
Technology
1st Found-In
7.0(116.0)
7.0(220.0)
Interpreting This Bug
Bug Toolkit provides access to the latest raw bug data so you have the earliest possible knowledge of bugs that may affect your network, avoiding un-necessary downtime or inconvenience. Because you are viewing a live database, sometimes the information provided is not yet complete or adequately documented. To help you interpret this bug data, we suggest the following:
This bug has a Severe severity level 2 designation. Important functions are unusable but the router's other functions and the rest of the network is operating normally.
Severity levels are designated by the engineering teams working on the bug. Severity is not an indication of customer priority which is another value used by engineering teams to determine overall customer impact.
Bug documentation often assumes intermediate to advanced troubleshooting and diagnosis knowledge. Novice users are encouraged to seek fully documented support documents and/or utilize other support options available.

LR 1.1 - Bug with Camera Raw resolutions?

I don't know that this is necessary, but in case this is a bug, I am posting it here, as well as in the help forum. Is it my imagination or am I missing some obscure Lightroom Preferences setting?
When selecting Edit in Photoshop, Lightroom 1.1 seeems to ignore the Camera Raw resolution settings for Nikon .nef files. While I have Nikon's recommended D1x natve resolution set for Photoshop's Camera Raw Plug-in (5.9MP - 3008x1960 @300ppi at 8-bits per pixel), when a selected .nef file is opened through Lightroom, it comes into Photoshop using all the D1x pixels (10.5MP - 4011x2613 @240ppi at 16-bits per pixel).
Is this yet another Lightroom resolution bug?
Did the same problem occur with the beta and 1.0 versions of Lightroom?
Why are all these Preference Settings hidden away in so many different places, and then not communicating with one another? If they must be set up in different dialog boxes for each application, you should be able to get to all related Preferences for Lightroom, Camera Raw and Photoshop in one place -- ideally the Photoshop Preferences dialog boxes.

No need to double post one forum section is enough.
Don
Don Ricklin, MacBook 1.83Ghz Duo 2 Core running 10.4.10 & Win XP, Pentax *ist D
http://donricklin.blogspot.com/

Is this a bug in APEX 3.0.1 Installation RAC database with RAW device???

Hello,
I am getting the following error when I try to complete approval process.
ORA-20001: Unable to create tablespace. ORA-01
119: error in creating database file '//./FLOW_1.dbf' ORA-27040: skgfrcre: creat
e error, unable to create file OSD-04002: unable to open file O/S-Error: (OS 2)
The system cannot find the file specified.
I checked the alert log for error here is the error in the alert log file.
ORA-1119 signalled during: CREATE TABLESPACE FLOW_1 DATAFILE '//./FLOW_1.dbf'..
and i found the syntax for create tablespace was wrong.
To create a tablespace in RAC with RAW device environment under windows.
it should have forward black slash instead of backward slash "/" without .dbf extension.
so, I changed the syntax i was able to create tablespace through sqlplus.
When APEX tool try to create this tablespace it throws this error..
Old: CREATE TABLESPACE FLOW_1 DATAFILE
'\\.\FLOW_1.dbf' SIZE 10304 K REUSE AUTOEXTEND OFF
EXTENT MANAGEMENT LOCAL AUTOALLOCATE SEGMENT SPACE MANAGEMENT AUTO
error : ORA-01119: error in creating database file '\\.\FLOW_1.dbf'
New:
CREATE TABLESPACE FLOW_1 DATAFILE
'\\.\FLOW_1' SIZE 10304 K REUSE AUTOEXTEND OFF
EXTENT MANAGEMENT LOCAL AUTOALLOCATE SEGMENT SPACE MANAGEMENT AUTO
Tablespace created.
Is it a bug in APEX 3.0.1.??
Is anyone installed APEX in RAC ??
James

Hi,
One observation, Apex is switching the Session ID after one got killed ? I was working on Apex page with browse Item to test open cursor count,
after killing the SID (227) on which the open cursor count was getting increase, it APEX automatically switches to new SID(149) for that session.
Now the problem is even if I have two SID's and one hits the maximum open cursor count, It is not switching to other SID instead the whole application becomes unavailable.
STATNAME SID VALUE USER
opened cursors current 20 14 APEX_PUBLIC_USER
opened cursors current 149 74 APEX_PUBLIC_USER
opened cursors current 194 71 APEX_PUBLIC_USER
opened cursors current 211 5 APEX_PUBLIC_USER
opened cursors current 227 325 APEX_PUBLIC_USER Killed
opened cursors current 244 15 APEX_PUBLIC_USER
opened cursors current 20 14 APEX_PUBLIC_USER
opened cursors current 149 76 APEX_PUBLIC_USER
opened cursors current 194 71 APEX_PUBLIC_USER
opened cursors current 211 5 APEX_PUBLIC_USER
opened cursors current 244 15 APEX_PUBLIC_USER
Please kindly help in this.
Thanks in Advance
Thanks & Regards
Sanjay
Edited by: user11204334 on Dec 8, 2010 1:02 AM

Bug? Camera Raw Smart Object Can't Be Edited

I have a problem where a raw file placed as a smart object can't be re-edited in CS3. Here's how to replicate the problem:
1. Open a JPEG or TIFF as a Smart Object (may happen with other file types).
2. Go to Layer > Smart Objects > New Smart Object via Copy.
3. Double-click the top smart object and make changes in Adobe Camera Raw.
You should now be able to hide/show the top layer (the final)
to see the bottom layer (the original.)
4. Double-click the top smart object layer to see that it properly opens Camera Raw allowing you to make edits (this works for now but will stop working when we encounter the bug in a moment).
5. Save the file and close it.
6. Re-open the file and double-click either of the smart object layers to edit them. Instead of Camera Raw dialog opening, the image in the window changes to the original unedited version. This is a bug and doesn't happen on every image, but it always happens on at least some of my images.
There have been times when it works, but the next time I open the file it stops working. Some of my files allow editing later without problems. Truly weird. Has anyone else had this problem? Is there a workaround?
I have applied all updaters, so that means I am using Photoshop CS3 10.0.1 with Camera 4.4.1 on Mac OS 10.5.2. I have also trashed preferences for Photoshop and Adobe Bridge. I've also Purged the Adobe Camera Raw Cache in the Bridge. This happens on both my Mac Pro (3GB RAM) and MacBook Pro (4GB RAM) so it's not just one machine.
Thanks in advance,
Dan

Hi Daniel,
Stumbled on your post while searching on a similar issue. I'm not sure if I precisely understand yuour problem, but here's my experience when dealing with TIFFs and JPEGs embedded as Smart Objects in CS3...
If the Smart Object layer contains a TIFF or JPEG that has already been edited and saved in Camera Raw (i.e., the embedded file has Camera Raw XMP metadata in its header), then Photoshop will open the Smart Object's contents in Camera Raw... with one provision. You have to make sure that in your Camera Raw preferences, under "JPEG and TIFF Handling", that both boxes are checked for "Always open JPEG/TIFF files with settings using Camera Raw".
If those boxes aren't checked, when you try to edit the contents of a Smart Object layer containing a TIFF or JPEG with Camera Raw settings in its header, instead of opening the embedded file for editing, Photoshop seems to simply revert to displaying the layer without the settings applied. I'm unsure whether this is a bug or intended behavior, but it seems to be one of the symptoms you describe.
On the other hand, if you make a Smart Object layer from a JPEG or TIFF that does not already have Camera Raw settings in its header, Photoshop CS3 will never open that layer's contents in Camera Raw, regardless of what preferences you have checked. Instead, the contents are opened in a separate window as a temporary .psb file. The only way I've found to do Camera Raw editing in these cases is to export the layer, edit the exported file in Raw, and then re-import it via Replace Contents.

Bridge CS6 open file bug with Hasselblad RAW file

There is a bug in Bridge CS6 (or RAW editor?) with (some) Hasselblad RAW files. I have a set of FFF files that I can use and open without problems in Bridge CS6 (5.0.0.399 x64). But one file of them does not show a preview icon and when I try to open it in PS6 or RAW editor, I get an errormessage "unexpected end of file...". When I open the same file in Hasselblad "Phocus" software there is no problem. I can see the preview thumb and I can play around with the file and even export to TIF or DNG without any trouble. I can even open the exported DNG in PS or Bridge/RAW editor then.
Well, you might say I should not care for a single file but it leaves a bad taste, when the Hasselblad software can handle the file without problems...
If some developer want to take a look at this I could provide original files.

Curt Y wrote:
Also, be sure to use a card reader for file transfer as a camera transfer can introduce errors.
I work with a Hasselblad medium format camera. I do not have a CF card in use. And I can tell that this worked absolutely flawless for many years. I NEVER had corrupted files caused by transfer. Many photographers using pro medium format cameras work the same way (Phase One, Leaf, etc.). They do not use CF cards but firewire cable. the problem arised when I started using the CS6 Bridge software. And it turned out that I get more and more corrupted files which appeared to be fine before. So from one shooting i.e. 1 file of 100 was corrupted first. Since I started using Bridge and changed RAW settings and worked with the same files after some days I have 5 corrupted files of 100 now. And NO it is not my system. It works fine with other camera RAWs where I have absolutely no problems. It is only the Hasselblad files. Though I still can open the Hasselblad RAW files with the Hasselblad software. The problems are only with the Bridge (respectively the raw editor) in combination with the Hasselblad files.
To me it looks like CS is corrupting the files since they worked fine at first - even in CS and after some days playing around in CS the appear to be corrupted. Funny that I can open the same files without problems using a different software - isn't it? ;-)
thanks for the link I will try it.... :-)

Camera raw 6.3 "Clarity Bug"

Hi, I am using Photoshop CS5 (64bit) + Camera raw 6.3 + win 7 x64 on both of my computers and having some problems with Camera raw 6.3 "clarity" settings. When I open Nikon D700 raw files and do some "Adjustment brush (K)" every settings which I apply is saving execpt "clarity" value not saving. It hapens so often. So I have to re open raw+xml files to re check if clarity value is saved correctly.
I am having this problem on both of my computers. So it seems there is a bug. Please check it.

Hi,
I just sent the video link to you via private message. Please let me know if you couldn't manage to download the video.
All the best wishes...

Bug in Camera Raw

I think this was introduced with ACR 6.6 RC ... but I'm not entirely sure, as the bug seems to be transient.
The problem basically is, when adjusting an image in Camera Raw and hitting Ctrl+Z while the preview is zoomed in to 100 % view or larger then the enlargement will snap back to "Fit in View". However this will happen only sometimes, not always. I have not yet found out which preconditions must be met in order for the bug to happen. The last thing I tried was a DNG 1.0 file from a Leica M9 camera, portrait orientation, cropped to 4:3 aspect ratio, some capture sharpening added (including Mask), preview enlarged to 400 % view. Upon trying to decide whether I want Colour Noise Reduction 10 or 20, I wanted to toggle between the two settings via Ctrl+Z but the preview kept switching back to "Fit in View" every time I hit Ctrl+Z.
The behaviour can sometimes be reproduced with other images from the same camera, and sometimes not. I wasn't able to reproduce it with images from other cameras ... not yet.
Operating system: MS Windows XP SP3 (32 bit)
CPU: AMD Athlon 64 X2 Dual Core 6000+
RAM: 4 GB installed, 3 GB used
Graphics card: ATI Radeon HD 2600 Pro

johnkwon9 wrote:
Have you been able to reproduce this issue on images before/without applying a crop?
No, I haven't. In fact, currently I am unable to reproduce the issue at all. I deleted the .8bi file of ACR 6.6RC and replaced it with a backup copy of the .8bi file of ACR 6.5, to check if the issue would appear with that version also (it didn't). Then I deleted the .8bi file again, to replace it with a backup copy of the .8bi file of ACR 6.6RC (I did not re-run the ACR setup procedure but just copied the .8bi files manually). Since then, the issue didn't appear anymore. It seems my original .8bi working file somehow was corrupted, and deleting and replacing it with a backup copy apparently solved the issue.
If the issue re-appears then I will report it here immediately.
EDIT: Umm ... I just found out what the "issue" actually is. It's just me. Hitting the Z key (without the Ctrl modifier) will select the Crop tool and zoom to "Fit in View" when a crop has been applied. So the issue appeared whenever I wanted to press Ctrl+Z but actually hit just Z inadventently (pressing the Ctrl key too late or not fully). So the issue is solved. Sorry for the flurry!

BC4J/Jedeveloper 3.2 BUG with SetAttribute on LONG RAW

Hi,
I'm using Jdeveloper 3.2, a BC4J/JSP application and a Oracle Thin connection to Oracle 8.0.4.
I think I found a bug in BC4J:
I have a table with a LONG RAW column that is also used by other (non BC4J)
applications to store binary data (including, but not limited to JPG's)
I'm able to retrieve data of any size using GetAttribute().
When I use the following code from a WebBean, it fails on commit
when the file is bigger than 4K.
The error is:
Error Message: JBO-26041: Failed to post data to database during "Update":
SQL Statement " UPDATE BDATA Bdata SET LRDATA=:1 WHERE ID_CARD=:2 AND CODE_REGISTRATION=:3".
Error Message: ORA-01461: can bind a LONG value only for insert into a LONG column
public void setData(java.io.File f) throws Exception
long len = f.length();
InputStream in = new FileInputStream(f);
Row myRow = qView.getCurrentRow();
byte[] buffer = new byte[(int)len];
in.read(buffer, 0, (int) len);
in.close();
Raw myval = new Raw(buffer);
myRow.setAttribute("Lrdata", myval);
Please help, I need this to work !
null

Raw domain is limited to the oracle-JDBC limitations of 4K length for such-streaming data types unless a Stream is used to update the data. We plan to support such streaming for Raw domain in the next major-release.
However, you should be able to work with Raw domain and if your data size is bigger than 4K, override the doDML() method in EntityImpl (that contains the Raw attribute) and perform a custom update for the Raw data. Basically the logic will be something like:
doDML()
1. save the raw attribute value
2. Populate 'null' or a single byte-bytearray for raw attribute value so that super.doDML() won't fail.
3. prepare an update statement with just the raw column and where clause for this entity's primary key.
4. fill in the raw data using an in-memory stream over the bytes from the Raw domain instance held in step 1. Use Statement.setBinaryStream() method.
5. execute the statement (to post the stream).
6. re-populate the entity data-structure with the valid Raw domain instance.
null

RAW bug

Similar Messages

Maybe you are looking for