Raw Conversion

Does Somebody know why my RAW files from a Nikon D7100 and a Canon Rebel T3I do not open in CS5?

You are in the wrong forum. Try this one:
Photoshop General Discussion

Similar Messages

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

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.

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.

Web service call on hosted env fails with hex to raw conversion error

Hi,
I use Enciva to run some hosted Apex applications, and I've had a call open with them for a few days re: setting up a web service call to an e-mail checker, provided by a company called Rolosoft. The e-mail checker runs fine from outside the hosted environment, but I get the following error trying to call from the Apex application:
ORA-06502: PL/SQL: numeric or value error: hex to raw conversion error
Has anyone hit this error before with web services, I've tried manual and RESTful but get the same error message.
Thanks,
Mike

Hello,
We encounter the same issue using manual WebService !
Environnement Settings :
Oracle 11g R2 - Windows W2K3 - NLS_CHARACTERSET : AL32UTF8
Apex 4.1
Any suggestions, helps ?
Thanks,
G.

RAW Conversion between CS2 and Aperture``

Has any one done any sort of comparison of RAW conversation out put from CS vrs; Aperture? Recently I've been using CS2 for my port processing work and really have noticed that the CS2 processing seems to be much clearer, better tones, and detail. Lately I don't seem to be able to get a decent print out of Aperture, I've been using it since it first shipped and I know it fairly well, just feels like I'm in some sort of a slump with it.

If you search this forum for deer.nef you will find a couple of recent threads on that topic.
I have done my own tests, converting several images using both apps. My conclusion is that both deliver a good conversion. Some images may come out better from on or the other but you will probably get the best result from the one you have the most familiarity with.
Note: the current RAW converson in Lightroom is not as up to date as the one in the Photoshop CS3 Public Beta. That will change next Monday. Try your own images in both. You may have a personal style that works better withh one or the other.

RAW conversion in 2 then update to 3 and its RAW conversion

I noticed that when I upgraded from 2 to 3 then 3.1, Aperture notified me that the RAW conversion it did in 2 is not the same as 3 and, would I like the 3 conversion done? When I said yes to one test image, it came out considerably darker.
What have people been doing with that change and, is it happening generally to all RAW conversions to 3 with most camera brands and models?
My preference is to leave them as version 2 as I always like the way Aperture handled RAW. There was a test comparison of RAW converters a year or so ago (I think it was a French site) and Aperture 2 held its own and was my preference.
So now I am wondering, how will new previews be when I import them into version 3? (Have not shot anything lately.) Since I prefer the Aperture 2 RAW to JPEG converter, can I set Aperture 3 to convert more like that?

I don't really want to reimport.
By processor do you mean RAW processor?
It's not that the new RAW in v.3 is bad, it is just darker.
I read up more in Aperture Help. Apple seems to indicate that one might like to keep the earlier RAW processed images and you can. Although, from the sounds of it, they make the v.3 RAW converter sound much better than v.2.
So, still, I just don't know how to "process" this issue myself.
How have others upgrading from 2 to 3 dealt with it and, did you notice the darker image after the conversion? Did anyone keep the v.2 processed images?

Aperture 2 vs Aperture 3 RAW conversion

I am new to Aperture and have been reading up on it. One point I thought was interesting was that v3 RAW conversion was considered improved over v2. I could understand that there could be a variance during the initial release of v3, but at some point v2 conversion would have been updated.
Is there a difference between v2 and v3 RAW conversion?
If so, how big of a difference? Would it be better to use Canon RAW converter instead?
Thanks,
Kenn

You need to eyeball the various conversions using your own typical photos. Each different camera model is a different RAW conversion, and each individual's brain/eyes see them differently. With the Nikon D2x I prefer Nikon's conversion over Aperture's and Aperture's over Adobe's - but Aperture's workflow is superior by a lot so I use Aperture.
If I was selling a thousand dollar large landscape print (I wish) shot on a D2x I would do the RAW conversion using Nikon Capture NX 2 rather than using Aperture, but that is just my personal preference with that particular camera model. And I see the difference as tiny, small enough that for most photography the workflow is more important.
HTH
-Allen

RAW conversion in 16 Bit?

Hi to all!
I'm using Aperture for quiet some time now, and i like the way i can select and organize all my files, and doing and adjusting my projects and albums.
But since I'm starting shooting Nef files I seem to be more and more in a dilemma. I also like the way I'm working with CS4 now, and all the options I have in Camera Raw, and I'm still trying to figure out, whether there is a way in working with both apps inter-active.
My library is now a referenced, external one. So all editing of my Raw files is stored in the Aperture library internally. My 14 Bit Nef files are converted into 16 Bit in the moment Aperture is opening or converting it? As soon I open them with External Editor they are a 16 Bit (if I want so) but they are no more Raw.
Most of my files are not getting extensively edited, so it's fine with me doing my conversion and a few tweaks, and leave them so. Now I tried to open the same Nef files in Adobe Camera Raw, and as long I let Adobe store the edit files separate from the Raw files, it seems Aperture is not disturbed, and I can even open and adjust them again. So far it seems to be no problems.
But I noticed now 2 problems.
The first is that all given keywords and description are only inside Aperture library (and they would only accompanied if I export the files as Tif)
And secondly that Adobe Raw seems NOT to convert my Nef files into 16 Bit.
If someone sees somehow a workaround pls give me ideas. Also how important is this 16 Bit question at all during this RAW conversion? Would it make sense to Raw-convert a 8 Bit file, and open it after to 16 Bit to make than more layer-work or clean-up?
I'm sorry if my questions sound a bit confusing.

mogli365 wrote:
I also like the way I'm working with CS4 now, and all the options I have in Camera Raw, and I'm still trying to figure out, whether there is a way in working with both apps inter-active.
You can use both but not interactively, and it's probably not a good idea unless you really know what you're doing because you could lose track of some images that way. Many will say that there's no reason to do this, but there are some things I do starting in Bridge/ACR. I keep these images in a folder called "NOTinA2", and I browse that folder with Bridge.
My library is now a referenced, external one. So all editing of my Raw files is stored in the Aperture library internally. My 14 Bit Nef files are converted into 16 Bit in the moment Aperture is opening or converting it? As soon I open them with External Editor they are a 16 Bit (if I want so) but they are no more Raw.
Neither program is affecting the actual RAW file: Bridge/ACR are storing instructions in a sidecar file, and Aperture is storing instructions in the Library. When you export or open in Photoshop, a new file is created. There's no need to open either in Photoshop unless you need to do Photoshop work.
Most of my files are not getting extensively edited, so it's fine with me doing my conversion and a few tweaks, and leave them so. Now I tried to open the same Nef files in Adobe Camera Raw, and as long I let Adobe store the edit files separate from the Raw files, it seems Aperture is not disturbed, and I can even open and adjust them again. So far it seems to be no problems.
The two programs are both referencing the same files, and one doesn't even know the other is there. If you open a file in Photoshop from either program a new file will be created. However, if you open it from ACR, Aperture will not know it's there.
The first is that all given keywords and description are only inside Aperture library (and they would only accompanied if I export the files as Tif)
You can not share Keywords from Aperture with Bridge.
And secondly that Adobe Raw seems NOT to convert my Nef files into 16 Bit.
At the bottom of the Adobe Camera RAW window, you'll see what looks like a web link. Click it to open the workflow options dialog box. There you can change it from 8bit to 16bit, set your print resolution and tell it if you want to open them in Photoshop as Smart Objects. (that last option will "embed" a copy of the RAW file in your Photoshop document and allow you to revisit you RAW conversion settings.)
DLS

Aperture RAW conversion and noise

I've been using Aperture for many years and have recently learned something useful about how to tweak the RAW conversion settings. Until recently I just left them at the default settings for my camera, a Panasonic GH2.
Anyhow I've not been entirely happy with shadow noise (otherwise I reckon it's a great camera). Many web sites say that a degree of shadow noise is normal for this camera, so I didn't figure mine was any different. I tried a variety of noise reduction approaches but none really made a worthwhile improvement.
Until a few days ago when I tried tweaking the 'Raw Fine Tuning' settings - and I found a way to make things *much* better.
Please note that the following comments may only be relevant to Panasonic RAW files, and maybe only for the GH2. I don't know if they apply to other cameras (though I think they may.
It turns out that for the GH2, the default 'Raw Fine Tuning' setting includes 'Sharpening' of 0.78 and 'Edges' of 0.79. This is fairly aggressive sharpening, but I didn't really realise what it was doing to noise until I discovered that was significantly increasing shadow noise -even at base ISO!
If I set these both the sharpening sliders in the Raw Fine Tuning section to '0', the 'grain' in the shadows is much smoother - a massive improvement.
But, of course, the image is a bit less 'sharp'. Well, this isn't much of a problem with 16+ megapixel cameras. Unless you are making huge enlargements from originals, and really look closely at the finest details at 100%, it makes very little difference if you give up this 'sharpness'. But the reduction in noise is actually very obvious indeed. It's much better!
Most of the sharpness I need on these less noisy images can easily be added by including the 'Edge Sharpen' adjustment, either at the defailt settings, or marginally toned down a bit. I'm currently using Intensity 0.7, Edges 0.3 and Falloff 0.4. This leaves most smooth areas untouched, so the 'noise' or 'grain' in smooth areas is as it comes from the sensor. By toggling the Edge Sharpen on and off, I can easily confirm no change in 100% or 200% loupe views.
That level of edge sharpening is a bit subtle, but actually achieves most of what I got from the Raw Fine Tuning sharpening sliders. It will be applied only to in-focus contrasty things like eyelashes or hairs or other defined edges, and very nicely.
So I'm sharing this in case other people also find it helpful. I strongly suggest removing the default sharpening entirely, and only using the Edge Sharpening slider in a cautious manner if you want to enhance sharpness.
Some related web pages:
http://www.jonroemer.com/blog/2011/01/aperture-3-too-sharp-tweak-the-default/
http://www.twin-pixels.com/raw-processors-review-aperture-bibble-capture-one-dxo -lightroom/
PS - there is a different issue with the default Raw Fine Tuning 'Boost' and 'Hue Boost' sliders, both of which are set to 1' by default. It turns out that these introduce a very large amount of contrast and exposure gain - turn them down to zero and the image goes quite dark and flat! The Aperture user guide says something about Hue Boost changing colours when Boost is set to '1' and this is the case. So I've experimented with turning them both to zero, and instead using a custom curves adjustment to achieve a similar level of exposure and contrast to the default conversion and the camera's default JPG image. By fine-tweaking the curves one can get better control of blown highlights and the overall contrast. I'm not sure if the colours are 'better', but I think so. I am fairly sure that I get smoother transitions in the mid-tonal ranges with this approach rather than just using Apple's default settings. Maybe they are a but strong for my liking. Certainly I can make curves that rarely require the 'Recovery' slider to fix over-boosted highlights. Anyhow, you may also find that this tweak helps a bit. Interestingly on a Canon RAW file the effect is not nearly as great in exposure terms, but there is also a definite colour change.
PSS - the end result is that I have set my camera preset for RAW fine tuning to zero settings for boost, hue boost, sharpening and edges. I then add contrast as needed using curves, and sharpen only with a little edge sharpening. I've then saved a few Presets with slightly different contrast curves and all with a little edge sharpening. I can very quickly select the level of contrast needed, and I am very confident that my results are quite a bit better, with better tonal gradations and much less noise.
Hope this helps
Chris.

Nice observations, Chris. I think the RAW Fine Tuning is often overlooked, even though it's a vital first step in RAW processing, and really the whole point of shooting RAW in the first place. Too much boost yields horrible skin tones in my experience. I have a default of .50 Boost and Hue Boost, Sharpening and Edges at .25, Moire .50, Radius 12.0 and Denoise .25. I've found these are "mid range" settings for the Canon 5Dii, and first make small adjustments to the Fine Tuning brick before moving on to exposure adjustments.

RAW conversion bug with Noise Reduction

Hello,
I have found a serious bug in the RAW conversion when noise reduction is applied. When converting from two types of Canon RAW files (a CRW from a Powershot G6 and a CR2 from a 20d) I found that if you apply Noise Reduction to a RAW file on very low settings (the default setting in the NR function will produce this reliably) single-pixel lines appear at regular intervals throughout the image. Here is an example:
You can see several lines in this image:
http://farm1.static.flickr.com/140/3821480263171e76604b.jpg
A 100% detail of which is here:
http://farm1.static.flickr.com/179/382148021af6586d27eo.jpg
Has anyone else had this problem? Can someone from the Aperture dev team fix this?
-Steve G

Well I find this filter is quite good in 'masking' block artifact that codec like xvid, or other low compression codec have. I only apply it if I find the block artifact is too much and I find this filter is less offending to my eyes than the block artifact.
In manual it said that if you have noisy video and want to lower the size then you can use this filter. It also blur the video a bit. But I suspect it is more than blur as I try gaussian blur in time line and the result is not as good. You can see the result as well. There is the tab between source and target and you can compare the result by togling between source and target tab.
BTW, anyone with 1 core, dual, or quad core, can you tried to encode with it? Just cancel it after few minutes as I want to see what is your processor utilization with this filter on. Also you can see how long does it take to process this video from the 'estimation time left'.

Raw Conversion

Similar Messages

Maybe you are looking for