TIFF to RAW Conversion

I work with Lightroom 2.5 and DNG (RAW) pictures from my Pentax K20D camera. I am not happy with the Noise Reduction in LR (especially for many slides I have scanned with a Nikon dedicated film scanner). Therefore, I would like to use a better program (perhaps Noise Ninja) to perform noise reduction, before I use Lightroom for further developments and exports. I believe that the noise reduction programs work with only non-RAW files. Would I lose significant image information if I convert my DNGs to 16-bit uncompressed TIFFs for noise reduction in another program, Save As "noise-reduced" 16-bit uncompressed TIFFs, and then convert these TIFFs back to DNG before importing them into LR? What other work-arounds can you suggest if I cannot do Noise Reduction of RAW files in other programs?
Thanks in advance, Paul.

If you hadn't purchased NN yet, I'd compare it first to Topaz, Neat Image and
Noiseware. And yes, it's easy to get noise when trying to open up a slide that has a good amount of contrast.
I'd call noise in scanning rather normal. It is certainly some thing that needs to be looked at. It has the same quality of low exposure on color neg film where there was plenty of color noise in the black of poorly exposed c41. ACR in either LR or PS has not been shared with developers, so that is why the noise reduction can not be applied to RAW files within the pipeline of the non destructive world.
Best may not be the same from shooter to shooter or scan to scan, so while some time the first thing you can do is very basic adjustments in ACR and then export as tif. You really need to run your own tests.

Similar Messages

Exported Raw Conversion Image Resolution and Assigning a Color Profile, etc

In Aperture 1.1, although I set the exported Raw conversion image resolution to 300 dpi in the preferences, it continues to come out at 72 dpi which is something of an inconvenience. Also, is it possible to assign a color profile to the "exported version" so that it is congruent to my PS CS2 color workspace (if that is what its called). Is this program capable of carrying out a conversion as a background operation? Finally, can the layout windows be configured so that they remember how they have been used in the past? Thanks.

Iatrogenic huh! Cool!
Anyway, I'm not real clear on what it is you are trying to accomplish. Despite your obvious vocabulary skills, there seems to be some disconnect relative to what you are trying to accomplish. You are right that "exporting a version" in Aperture is roughly equivalent to what happens in ACR when you "Open" a RAW image into Photoshop. In both cases you have, hopefully, already done the adjusting of parameters you want prior to "exporting", or "opening". When you "open" or "export" you wind up with an "image" composed of pixels, whereas in the RAW adjustment phase you are just working with a temporary thumbnail and a set of mathematical instructions. Big difference, I suppose is that when you "open" and image from ACR into CS2, the resulting image is truly just pixels and has not had a "file type" applied to the file yet, until you "save" it, while in Aperture, if you "export" a file to CS2, or to the desktop, you end up with the file type already applied. Presuming you "export" a 16 bit TIFF or PSD, there is no operational difference.
I could be wrong, but with the new Bayer Demosaicing algorithms in Aperture 1.1, and the Camera RAW adjustments, you should be able to come up with an adjusted image that is VERY close if not identical to one done in ACR, with the possible exception of lens abberation adjustment. I was very critical of the RAW adjustments in 1.0.1, but I am very happy with the capabilites in 1.1. That said, I think there is still some room for improvement in user friendliness of some of the adjustments such as Levels.

Fuji Raw Conversion Software as External Editor in Lightroom

Anyone know whether Fuji's Hyper Utility RAW conversion software (if I remember the name correctly) will work as an External Editor in Lightroom. (Just read an article by a Nikon photographer who uses Capture NX this way in Lightroom and wonder whether the same is possible for Fuji.)

Thanks; I guess my question (which I did not state clearly) is whether if, at the end of processing in HV-S3 and "Save" the saved file (likely a TIFF) will automatically appear in the Lightroom Library associated with the original RAW file; this would be the chief advantage over just opening the folder with the file in HV-S3 to begin with, but it occurs to me that this may be a dumb question (as I've just downloaded and begun to use Lightroom and can't experiment with HV-S3 yet as it has not yet been released, but will be shortly). Thanks again.

Awful canon raw conversion for photos with dramatic (i.e. underwater) non-standard white balance

I'm shooting underwater (and white balancing as I shoot using a white disc) with a canon s90, and have noticed that the raw conversions done by aperture are way worse than those from jpegs when I shoot in raw+jpeg and those done by raw processing using the canon digital photo professional software. In particular, reds are pretty much lost. It may be a false lead, but I notice that in aperture, the rgb histogram shows a dramatic spike of the red channel on the far right (possibly clipping?) that doesn't show up in the rgb histogram in the canon software.
I'm not sure whether this is related to the plethora of threads about canon raw processing and overly green output. Has anyone else experienced this or have any ideas? I could batch convert to tiff in the canon software but I'd really rather not do that... For one thing the 16bit tiff files are so much bigger than the raws and it is an annoying extra step. Also, note that I can't just batch fix the white balance because (a) I'm having a hard time getting aperture to do it properly (possibly b/c the red channel is clipped as far as the aperture UI is concerned?) and (b) The white-balance changes from picture to picture as I change depth, which is the whole reason I white-balance as I'm shooting in the first place..
I've attached two versions of a picture, one of which I processed the raw in aperture and one of which I processed the raw (and converted to TIFF to give to aperture) in the canon software. I then exported both as small jpegs from aperture.
Canon Digital Photo Professional (correct):
Aperture RAW processing (very wrong):

>Is MS Picture Viewer a colour managed application? I don't know, but don't think so. Lightroom is however which might be the cause of your problems.
Not in XP. In vista it is color managed. From the sound of it, the problem is a bad monitor profile but you might also have a corrupt Lightroom database. You need to recalibrate the monitor and NEVER use canned profiles from the monitor manufacturer. They are almost always corrupt. As a very last resort, you can use sRGB as the monitor profile (delete any profile found in the windows display properties) but only to hold you over until you can really calibrate it. The other problems with weird errors are pretty worrisome though. Do you also get them when you start a fresh catalog?

RAW conversion, iPhoto vs Aperture

I currently shoot in RAW, save the folder to my desktop, convert files in ACR and import into Photoshop for edits; I then create a master edited TIFF for each saved image a, plus make 3-5 variations (composites, B&W, etc) of every master image . When all that is in the (renamed) desktop folder, I then import that folder into iPhoto where finished files are routed to Smart Folders.
For added security I routinely backup all the RAW files using Export to an external HD.
The ideal workflow (for me) however, would be to use Nikon's free NX2 software to convert the RAW files into TIFF, do basic editing and import both the RAW and TIFF conversions directly into iPhoto. So far, I can't get that to work without going through the extra step of NX2>Desktop>iPhoto.
Am I missing something in iPhoto, or maybe it can't handle that?
Would Aperture allow that direct NX2 > Aperture import? I'm a little unclear on the Aperture RAW conversion process, so could I import RAW files folder into Aperture and then convert those RAW files to TIFF and edit them within Aperture? That way the only time I'd have to go outside Aperture would be to do something in PS that Aperture can't handle.
Brian

No
You simply have to set your editing program as the external editor for iPhoto - in the iPhoto preferences you can choose to send RAW to the external editor or not - if you do then once you edit the photo you must save it to the desktop and import the modified photo into iPhoto creating a new photo - if you do not pass it as RAW then you save in the editor and it is returned to iPhoto and the database properly updated
As to the process iPhoto uses - all originals are saved unmodified - RAW , TIFF or JPEG. as they are imported a small JPEG preview is generated for quick access by iPhoto and other programs - with RAW an additional large JPEG preview is saved -- when you edit in iPhoto the edit steps are saved and applied to the preview and to the thumbnail - future edits steps are also saved so you always start yoru edit with the unedited original and add edits so you never are but one step form the original eliminating the multiple editing losses that cause some people to use TIFF rather than JPEG -- hence my comment
Both can import and convert your RAW photos and both provide lossless editing so using giant TIFFs would not be necessagy
and
Unless you have very unusual requirements your work flow seems uncessary and overly complicated to me
as to
but if I want to see the original RAW file, and the edited versions stored within iPhoto
If you want to see both then they both have to be there - since iPhoto always keeps the original and while editing in iPhoto you can view it at any time by depressing the shift key most people prefer to simply their work flow and save the disk space and let iPhoto handle this
It really sounds like you do not want iPhoto and yoru best choice is to shoose a different photo manager that works like you want - or learn and understand iPhoto (and most if not all Digital Asset managers - DAMs - which work much like iPhoto) and use it the way it works
You can use what you please and do what you please, but if you use iPhoto you are making life very difficult by going against its standard procedures
LN

RAW conversion comments

I respect a photographers personal opinions regarding their perceptions of differing quality levels in RAW conversions but in the commercial world these perceived differences between Aperture and say ACR are so minimal they certainly do not qualify as a deal breaker.
In the real world of commercial photography, design and printing, photo images are ultimately used as 8 bit CMYK files or when used for Giclee printing as 8 bit RGB files. These files go through so much retouching and manipulation after the RAW conversion that the esoteric quality differences talked about in these posts are irrelevant.
The proper use of any Camera RAW converter is to balance the image before outputting it as a 16 bit TIFF or PSD for refined manipulation in Photoshop. This would include refined levels adjustments sometimes with layer masks and appropriate sharpening at the final output size.
We typically use the RAW converter to:
1- Pull back highlights that appeared to be blown
2- Open shadow detail that appeared to be plugged
3- Correct color casts and saturation
4- In some cases add special effects such as conversion to rich B&W
Very few serious professionals in either the commercial or fine arts world are going to use the RAW conversion as their final image.
We can argue forever about the pros and cons of this or that RAW conversion quality, but in the real world Aperture's solution, while not absolutely perfect, does an excellent job within a program that enhances real world productivity.
Dual 2ghz G5 Mac OS X (10.4.3)

Tom...
With respect, your logic is hard to accept. You state that in the commercial world, images are typically so heavily manipulated that initially quality of RAW conversion is non-issue.
I am surprised that no one has bothered to challenge this idea. So I'll step up.
If my RAW conversion out of ANY program is going to introduce banding artifacts, 'parquet flooring' patterns, or other noisy type data into solidly colored areas, that will need to be fixed in this manipulation of which you speak. Who could justify having to do this sort of thing when there are perfectly good RAW converters out there that don't add this particular headache to the workflow?
Your message states that "Apertures solution, while not absolutely perfect, does an excellent job within a program that enhances real world productivity."
That statement stands as a contradiction when you consider that extra 'fixing' may need to be done to some images coming straight out of Apertures RAW conversion.
I suspect that you (and others) are not seeing problems because evidence is mounting to support the idea that Apertures RAW conversion works better for some flavors of RAW than others. So, perhaps some people are seeing consisten image trashing, and some not. If this is the case, one could easily understand why some are 'satisfied' and some are positively livid.
However, I digress. I still don't agree at all with the idea that in the commercial world a substandard RAW conversion would make an acceptable starting point for any commercial image, regardless of how much manipulation down the track its going to go through. I can't see any art director being satisfied knowing this was going on in their shop.
"Aperture - sure it mangles your images, but it does a heck of a job keeping track of them!"
Jim

Aperture 3 Raw conversion from Nikon D700 - Bad results - Anyone?

I recently upgraded to a Nikon D700 and have noticed I am getting some really bad conversion results from my raw files which involve my having to do a lot of work to get decent images. Most images are too dark and with strong orange cast... Any ideas? I thought it might be the camera, so I tried another computer with photoshop raw converter and images are fine. I have noticed the original import settings are strange on Aperture but cannot seem to change them, they always revert back to maximum hue boost and max boost ect... Any help would be great! thanx!

I have a Nikon D700 and have just tried the Aperture demo- same results as you guys, disappointing RAW conversion. Contrast and sharpness quite poor and blues are 'off'
I currently use Capture NX and was looking for something a little less 'clunky'. Though it may not be as slick as Aperture, its RAW conversion is spot on (as you would expect from a Nikon sponsored app)
It's easy to compare the differences- open an unedited RAW file in Capture NX and save as an uncompressed, 16 bit TIFF. Import this and the original RAW file into Aperture. Prepare for disappointment :-/

A novel idea regarding RAW conversion

With the much debate about Aperture and ACR and RAW conversion, I had this thought: RAW conversion is really part of the image editing process, not part of cataloguing, selection, organization, or required for producing thumbnails.
I'm not exactly sure when the RAW conversion takes place, but I'm guessing on import, so that images can be immediately edited. Why can't thumbnails and organization take place in Aperture without converting from RAW? Adobe Bridge seems to manage this just fine. It would seem like the logical place to put RAW conversion is as a precursor to image editing in Aperture. For example, when you click the adjustment button, the conversion takes place. This would seem like a logical way to incorporate a RAW Converter plugin.
Why does the Aperture RAW conversion have to take place at all (except when a user demands it) ? Seems like this follows workflow more logically...
Brad

Interesting. Well this is confusing then -- why in
the world is Aperture not sending a RAW file to
Photoshop when you configure Aperture to use
Photoshop as its external editor?
It seems from my observations that this was a design choice on the part of Apple. This is going to get a bit technical...
When you choose to open in an external editor, Aperture automatically converts any 'master' file (tagged as 'isExternallyEditable' = false and 'isOriginalFile' = true in the XML file) to a 16-bit TIFF or PSD file, adds that as a new file stacked with the original RAW and opens the new file in the external editor. That new file is not really a 'version' in terms of it just being an adjustment recipe, but is a whole new file which is linked in the database to the RAW, just like a stack.
Once that new file is made, it's 'isExternallyEditable' tag changes to true and from then on Aperture passes the file directly to the editor. This state is shown by the target icon. This repeats until you make image adjustments to that image within Aperture, leading to your earlier problems with repeated editing of the same file in PS. If you DO make adjustments to it within Aperture it then becomes a new 'sub'-master with it's own versions.
Playing devil's advocate, there is actually a valid reason for doing things this way - pass the original RAW file to ACR, and how does PS know where to save the resulting file so that it goes back into Aperture, or which RAW master to associate it with?
A possible solution with Aperture 1.0?
The manual workaround at the moment which would give a reasonable amount of play back-and-forth would be to set up two hot folders using folder actions. One automatically opens any files dropped into it in PS. The other automatically imports any files into Aperture.
So, do all your choice editing until you just have final picks, not bothering with any image adjustments, then:
1) Go through the final picks, Apple-Shift-S (export master), saving them into the PS hot folder. They automatically open up in ACR, probably one at a time.
2) Do your RAW conversion with the superior toolset available.
3) Save into the Aperture hot folder and watch them be automatically imported.
4) Now the more manual bit - drag that converted file into the stack with it's RAW original.
You now have the original and it's converted file linked together in Aperture, although keywords etc. will be separate. Once the hot folders are set up it should be relatively straightforward. Not nearly as straightforward as it could be, but hopefully manageable.
Ian

I have an A77 and see that DxO RAW conversions look different

Several RAW conversion comparisons on the web amongst A77 users are pointing to markedly better conversions and noise handling currently within new DxO 7 eg. http://forums.dpreview.com/forums/readflat.asp?forum=1037&thread=39970661
I know that Sony's RAW have historically taken a while to arrive at optimal conversions from previous experinece with my A350. When Lightroom 3 came along it was like getting new cameras for most Sony Alpha users with from RAW performance at last matching Nikon from effectively the same sensors.
Can you let me know the likely time lag till ACR and Lightroom will have an update to this initial default to really match the DxO performance. Otherwise, to be honest, despite being a Lightroom user since the original Beta stages and a passionate supporter and advocate, I may have to consider jumping ship. Working exclusively in RAW I do need to be using the very best conversions possible to make the best out of my investment in my camera equipment.
I don't know if this lag with ARW conversions is because Sony don't co-operate with Adobe early enough or whether because Sony is only number three in DSLR share it gets less priority within Adobe than Canon and Nikon, but some timeline on a revised version of Lightroom to address this for the new Sony Alphas would be great.
Many thanks from a long time advocate who really hopes I can stick with Lightroom,
Cheers,
Paul

Hi Hal,
Many thanks...I’ll give it a try. Not trying to cause trouble as I genuinely am a fan of LR, but if they always lag on getting to grips with Sony RAWs it’s a major drawback for Sony users.
Cheers,
Paul

Lightroom vs. Photoshop Raw conversion

I have noticed that the Lightroom RAW conversion looks about 1/3 to 1/2 stop brighter compared to Photoshop on the same image with the same settings (I'm using LR 2.4 and Photoshop CS4). Anybody else notice this or have any thoughts? I'm assuming they use the same RAW conversion engine.

Thanks for the response. Well, when I export from LR to a JPEG and do the same from Photoshop (viewing them in photoshop), I get two slightly different toned images (I mistakenly said the LR images are brighter...they're actually darker). Viewing them this way should remove any monitor discrepencies (I'm working on a calibrated Lacie 724 monitor with 120% Adobe 1998 gamut so that should not be an issue).

Panasonic Lumex DMC-LX1 raw conversion for Aperture doesn't work.

I've seen many people having raw conversion problems. Direct import of Lumex raw files to Aperture does not work.
Adobe DNG conversion of raw to dng does not work.
I'm running on Photoshop CS.
Perhaps my DNG conversion settings aren't right? Tell me what they should be.
Do I have to go as far as changing the raw.plist or whatever it's called.
Would CS2 with the Raw conversion Plug-in work instead?
Remember that..."If all the woman lived across the sea, what a great swimmer Yellowman would be"!
2.0 Duelly G5 4gigs ram. 23" Flat Cinema Mac OS X (10.4.6)

Joe,
good to see that you are reading these posts. I am sure that many users whose cameras' raw files are currently not supported by Aperture would love to help out in any way they can.
However, as we are living in a converging world, why doesn't Apple talk with Adobe and share some of the information used for RAW conversion? I'm thinking dcraw which (according to a note in its source code*) is using data provided by Adobe... and that same data is also contained in the Raw.plist.
Thus, if Adobe knows something and shares it with dcraw, and Apple uses some of the dcraw code (at least the m2 matrices found in Raw.plist are equal to the dcraw ones), why can't you guys all share the same information, and thus speed up RAW support for all cameras?
Just a thought.
Kindest regards,
Karl
* This is the bit:
Thanks to Adobe for providing these excellent CAM -> XYZ matrices!
void CLASS adobe_coeff (char *make, char *model)
powerbook G4 17 1.33 GHz Mac OS X (10.4.6)

"Unable to save the raw conversion settings. There was a write permission error."

I just built a new workstation for processing photos using PS CS5. I use external drives to store my images as I find it easier for backing up as well as for when I want use my laptop for sorting, etc.. I copied over all my old "Collection" files, and of course, had to "fix" them once on the new machine. Once pointed in the right direction, the collections all fill out correctly.
When I go to process a collection though, I encounter an odd problem I can't seem to sort out. I can delete files, rename files, copy/paste to the external drives, etc.. What I can't seem to do is add Labels, Ratings, or modify RAW settings. I mean, I can use ACR to make adjustments, I just can't seem to save them.
The system just ignores label, rating commands completely. When I try to save an ACR adjustment I get this error. "Unable to save the raw conversion settings. There was a write permission error."
The files are NOT write protected. I'm set up as the owner of my workstation, with complete control of the system. I can't seem to find any useful information about this error because the "write permission error" seems to only be happening on installs, so that's all I can find help for.
My system:
Intel Core i7 970@ 3.20GHZ
24.0 GB RAM
64-bit OS - Windows 7 Pro
DX58S02 Motherboard
NVIDIA GeForce GTX 580

Thanks for replying. I've been going crazy trying to fix this.
To answer your first question; I use sidecar XMP files. If everything from my archive was shot in RAW I'd try converting to DNG and see if embedding the changes directly in a file worked. Unfortunately, a lot of my old stuff was shot in JPG, so sidecars seems to be the best choice.
When I add labels, ratings, as well as change RAW settings on files I place on my workstations HD everything works. It's only when I try to do these things with the same files on removable drives that I run into trouble. The drives I use are Transcend 640GB StoreJet 25ms connected via USB.
I don't think it's a UAC problem. At least, to my understanding, doesn't that control how your machine alerts you to program changes? I looked into how to change ownership, and did so, but that didn't work. Here's a link to what I mean: http://www.addictivetips.com/windows-tips/windows-7-access-denied-permission-ownership/
I'm stumped. I also hate the idea that I'll have to go through various folders to find images from already created collections, copy them to a new folder on my HD and then work on them. Then I'll have to put them all back... ugghhhh

Numeric or value error: hex to raw conversion error , pls help

I am having problem with a sproc which accepts a Raw parameter.
I have a table called Profile:
CREATE TABLE PROFILES
PROFILEID INTEGER NOT NULL,
USERID INTEGER NOT NULL,
PROFILE RAW(255)
and a sproc named addprofile
CREATE OR REPLACE PROCEDURE addprofile
profile IN RAW,
userName IN VARCHAR2
AS
userId INT;
BEGIN
GetUserIdByName( userName, userId);
INSERT INTO Profiles
( ProfileID,userId , profile )
VALUES ( Profiles_ProfileID_SEQ.NEXTVAL,AddProfile.userId ,
AddProfile.profile );
END;
I am calling the Ent Library's Insert profile method which is part of DbProfileProvider.cs (Security App block). It is trying to persist a serialized profile object into the database.
private void InsertProfile(string userName, byte[] serializedProfile,
Data.Database securityDb, IDbTransaction transaction)
DBCommandWrapper cmd = securityDb.GetStoredProcCommandWrapper
(SPAddProfile);
cmd.AddInParameter("userName", DbType.String, userName);
cmd.AddInParameter("profile", DbType.Binary, serializedProfile);
securityDb.ExecuteNonQuery(cmd, transaction);
I get the following error:
Any suggestion on what needs to be changed to get this working? thanks!
Exception Details: Oracle.DataAccess.Client.OracleException: ORA-06502: PL/SQL: numeric or value error: hex to raw conversion error ORA-06512: at line 1
Stack trace:
[OracleException: ORA-06502: PL/SQL: numeric or value error: hex to raw conversion error
ORA-06512: at line 1]
Oracle.DataAccess.Client.OracleException.HandleErrorHelper(Int32 errCode, OracleConnection conn, IntPtr opsErrCtx, OpoSqlValCtx* pOpoSqlValCtx, Object src, String procedure)
Oracle.DataAccess.Client.OracleException.HandleError(Int32 errCode, OracleConnection conn, String procedure, IntPtr opsErrCtx, OpoSqlValCtx* pOpoSqlValCtx, Object src)
Oracle.DataAccess.Client.OracleCommand.ExecuteNonQuery()
Microsoft.Practices.EnterpriseLibrary.Data.Database.DoExecuteNonQuery(DBCommandWrapper command)
Microsoft.Practices.EnterpriseLibrary.Data.Database.ExecuteNonQuery(DBCommandWrapper command, IDbTransaction transaction)
Microsoft.Practices.EnterpriseLibrary.Security.Database.DbProfileProvider.InsertProfile(String userName, Byte[] serializedProfile, Database securityDb, IDbTransaction transaction)
Microsoft.Practices.EnterpriseLibrary.Security.Database.DbProfileProvider.SetProfile(IIdentity identity, Object profile)
[InvalidOperationException: Error saving the profile for the following user 'test'.]
Microsoft.Practices.EnterpriseLibrary.Security.Database.DbProfileProvider.SetProfile(IIdentity identity, Object profile)
EntLibSecuritySample.DFO.Security.SecurityHelper.SetUserProfile(IIdentity identity, Object Profile) in C:\DFO\Sample\Security\EntLibSecuritySample\SecurityHelper.vb:285
[ApplicationException: An error has occurred saving profile object to Datastore. See stack trace for further information]
EntLibSecuritySample.DFO.Security.SecurityHelper.SetUserProfile(IIdentity identity, Object Profile) in C:\DFO\Sample\Security\EntLibSecuritySample\SecurityHelper.vb:287
EntLibSecuritySample.ProfilePage.cmdSaveProfile_Click(Object sender, EventArgs e) in C:\DFO\Sample\Security\EntLibSecuritySample\profile.aspx.vb:59
System.Web.UI.WebControls.Button.OnClick(EventArgs e)
System.Web.UI.WebControls.Button.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument)
System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument)
System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData)
System.Web.UI.Page.ProcessRequestMain() +1292

Harsh,
I am not a user of the Enterprise Library so I can not speak to the specifics of that. However, here is a short sample that is based on the information you've provided. Perhaps it will be useful.
Database:
create table profiles
profileid integer not null,
userid    integer not null,
profile   raw(255)
create or replace procedure addprofile
p_profileid in integer,
p_userid    in integer,
p_profile   in raw
as
begin
insert into
    profiles (profileid, userid, profile)
    values (p_profileid, p_userid, p_profile);
end;
/C# code:
using System;
using System.Data;
using System.Text;
using Oracle.DataAccess.Client;
using Oracle.DataAccess.Types;
namespace HarshTest
/// <summary>
/// Summary description for Class1.
/// </summary>
class Class1
    /// <summary>
    /// The main entry point for the application.
    /// </summary>
    [STAThread]
    static void Main(string[] args)
      // connect to local db using o/s authentication
      OracleConnection con = new OracleConnection("User ID=/; Pooling=False");
      con.Open();
      // create command object and set properties
      OracleCommand cmd = new OracleCommand();
      cmd.Connection = con;
      cmd.CommandText = "ADDPROFILE";
      cmd.CommandType = CommandType.StoredProcedure;
      // parameter object for profileid
      OracleParameter p_profileid = new OracleParameter();
      p_profileid.OracleDbType = OracleDbType.Int32;
      p_profileid.Value = 1;
      p_profileid.Direction = ParameterDirection.Input;
      // parameter object for userid
      OracleParameter p_userid = new OracleParameter();
      p_userid.OracleDbType = OracleDbType.Int32;
      p_userid.Value = 1;
      p_userid.Direction = ParameterDirection.Input;
      // create a byte array for the raw value
      ASCIIEncoding encoder = new ASCIIEncoding();
      byte[] byteArray = encoder.GetBytes("TestProfile");
      // parameter object for profile
      OracleParameter p_profile = new OracleParameter();
      p_profile.OracleDbType = OracleDbType.Raw;
      p_profile.Value = byteArray;
      p_profile.Direction = ParameterDirection.Input;
      // add parameters to collection
      cmd.Parameters.Add(p_profileid);
      cmd.Parameters.Add(p_userid);
      cmd.Parameters.Add(p_profile);
      // execute the stored procedure
      try
        cmd.ExecuteNonQuery();
      catch (OracleException ex)
        Console.WriteLine(ex.Message);
      // clean up objects
      p_profile.Dispose();
      p_userid.Dispose();
      p_profileid.Dispose();
      cmd.Dispose();
      con.Dispose();
}Maybe the part about creating the byte array is what you are missing...
- Mark

Raw Conversion: Colors not accurate. Correction with profile?

Hi,
When I create JPGs from my Raw files, the results don't look natural. Some colors have more saturation, some less. For example, the colors of the KoMi A series look somehow dirty; the reds of the Maxxum 5D seem to be oversaturated (dark reds are to bright, brown faces look rather pinkish).
This is in comparison to the orignal objects, to the JPGs generated from the KoMi Raw converter and to the in-camera JPGs.
Since Lightroom has tremendous color tuning options (under HSL and Color), I wonder whether a camera-specific profile can make the colors more natural. Has anybody tried for the KoMi cameras? Can anybody share a profile?
I don't have a color checker, so this would be a tough one for me. I tried a bit, but whenever one color seemed right, another color had become worse.
Here is my equipment:
Cameras: Konica Minolta A2, Minolta A1, Konica Minolta Maxxum 5D.
Other: My room has fluorescent tubes of type 950 (5000K, highest quality, Philips Graphica Pro) or of course daylight from outside. My screen is calibrated using ColorPlus hardware. I used a grey card for most of my photos. JPGs viewed with IMatch (color-profile aware).
Regards,
Martin

Hallo Uli,
there are two aspects of the color deviation:
1. Displaying colors in LR
This is what you are addressing in the other thread. I can confirm this behavior, but let's not touch this matter here.
2. Raw conversion
This is what I am talking about in this post. The effect is actually larger than the display deviation.
Regards,
Martin

ORA-22835: Buffer too small for CLOB to CHAR or BLOB to RAW conversion

Hi all,
the following query select to_char(nvl(round(pc.target_cost*xx_primavera.geteurtolvrate,2),amount),'FM999G999G999G999G990D00') detail_amount,
nvl(ct.cost_type, description) detail_description,
tm_desc.memo_id,
primavera_prj_name detail_prj_name,
hp.party_number detail_party_number,
xpid.interface_line_attribute1,
utl_i18n.unescape_reference(replace(regexp_replace(utl_raw.cast_to_varchar2(tm_desc.task_memo), '<[^>]*>'), chr(13)||chr(10))) document_description,
REPLACE(regexp_replace(utl_raw.cast_to_varchar2(tm_id.task_memo), '<[^>]*>'), chr(13)||chr(10)) prim_memo_client_id
from XX_PRIMAVERA_INVOICES_DETAIL xpid
join admuser.xx_ar_hz_parties xahp on xahp.orig_system_bill_customer_id = xpid.orig_system_bill_customer_id
join hz_parties hp on hp.party_id = xahp.party_id
left join admuser.projcost pc on pc.proj_id = xpid.primavera_prj_id and pc.cost_type_id != 29 and xpid.service_code = 8 and pc.task_id = xx_primavera.getTaskId(xpid.primavera_prj_id,'A1020', 'Изготвяне на оферта') and delete_session_id is null
left join admuser.costtype ct on ct.cost_type_id = pc.cost_type_id
left join admuser.taskmemo tm_id on tm_id.proj_id = xpid.primavera_prj_id and tm_id.memo_type_id = 53 and tm_id.task_id = xx_primavera.getTaskId(xpid.primavera_prj_id,'A1020', 'Изготвяне на оферта')
left join admuser.taskmemo tm_desc on tm_desc.proj_id = xpid.primavera_prj_id and tm_desc.memo_type_id = 55 and tm_desc.task_id = xx_primavera.getTaskId(xpid.primavera_prj_id,'A1020', 'Изготвяне на оферта')
where amount != 0
and xpid.interface_line_attribute1 = :ra_ctp_attribute1
ORDER BY xpid.primavera_prj_name, xpid.description;returns error:
ORA-22835: Buffer too small for CLOB to CHAR or BLOB to RAW conversion (actual: 2371, maximum: 2000) I found that the error occurs in the row : utl_i18n.unescape_reference(replace(regexp_replace(utl_raw.cast_to_varchar2(tm_desc.task_memo), '<[^>]*>'), chr(13)||chr(10))) document_description,and tried to change it to: utl_i18n.unescape_reference(replace(regexp_replace(utl_raw.cast_to_varchar2(dbms_lob.substr(tm_desc.task_memo,1,2000)), '<[^>]*>'), chr(13)||chr(10))) document_description,....but it returns not value for that field... am i using dbms_lob.substr at the wrong place? The column 'tm_desc.task_memo' is BLOB type.
Any ideas how to cheat it ?
Version: Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - Production
PL/SQL Release 11.1.0.7.0 - Production
"CORE     11.1.0.7.0     Production"
TNS for Linux: Version 11.1.0.7.0 - Production
NLSRTL Version 11.1.0.7.0 - ProductionThanks in advance,
Bahchevanov.

Your second example has the parameters reversed. The amount (length) comes first and then the offset:
DBMS_LOB.SUBSTR (
   lob_loc     IN    BLOB,
   amount      IN    INTEGER := 32767,
   offset      IN    INTEGER := 1)
RETURN RAW;
DBMS_LOB.SUBSTR (
   lob_loc     IN    CLOB   CHARACTER SET ANY_CS,
   amount      IN    INTEGER := 32767,
   offset      IN    INTEGER := 1)
RETURN VARCHAR2 CHARACTER SET lob_loc%CHARSET;
DBMS_LOB.SUBSTR (
   file_loc     IN    BFILE,
   amount      IN    INTEGER := 32767,
   offset      IN    INTEGER := 1)
RETURN RAW;Also, remember that # of bytes is not necessarily the same as the # of characters depending on your character set. So 2000 bytes might become 4000 characters. And you have to make sure the BLOB is actually character data and not arbitrary binary data.
Post the results of reversing the parameters and using a smaller chunk size.

TIFF to RAW Conversion

Similar Messages

Maybe you are looking for