Old Raw processing bug returns.

Since upgrading to 10.6.5, I have now found that the default camera Raw setting is no longer staying set. I have reprocessed a batch of images in a project, and started re-applying the Raw Fine Tuning settings, as I've found the default Apple one is much better than the custom one I had created (the previous default being far too aggressive).
However, when I set it the 'Apple - Camera Default' shows a tick, and all is OK. If I quit Aperture and reload, the setting is un-ticked. I remember this happening in a previous version, but can't remember the fix (was there a workaround, or did it need an update?)

ednsb wrote:
Maybe a bit off topic but when you run the disk utility program to repair permissions it is a very good idea to boot from the OSX disk and run it from there rather than from the root disk.
Sorry but not the right thing to do. While repair disk HAS to be run from other then the volume you are repairing Repair Permissions should be run from the volume which has the current OS X.
See:[About Disk Utility's Repair Disk Permissions feature|http://support.apple.com/kb/HT1452]
*Should I start up from a Mac OS X install disc to repair disk permissions?*
When possible, disk permissions should be repaired while started up from a Mac OS X volume (hard disk) that contains Mac OS X, instead of a Mac OS X installation disc. Mac OS X software updates may change permissions on some files to improve security. When this occurs, the version of Disk Utility on the Mac OS X volume is updated to account for the new permissions. Running Disk Utility while started from the Mac OS X volume ensures that the changes made by software updates are preserved.

Similar Messages

ACR vs Aperture for Raw Processing

I have been using Lightroom for over a year (including beta versions on my old PC), but have grown tired of it's lack of worthwhile output options. I have a trial version of Aperture and think that it is a far superior product on the management and output side of things, but I am having problems getting my raw files to look good to me.
I could process all the files in Bridge first, then create tiffs or PSDs to import into Aperture, but that would negate have the purpose of Aperture. I need help with an Aperture workflow and probably with raw processing controls in Aperture.
Specs: 17" MBP with 10.5.1, Aperture 1.5.6
Camera: Pentax K10D ver 1.3
I typically convert my PEF files to DNG due to better compression in DNG, but have tried using the original PEF with identical results. Any help is appreciated.

I too came back to Aperture after a year of Lightroom's "workflow". It really is possible to match or surpass LR's output. There's a good guide to the adjustment tools here:
http://www.insideaperture.com/Site/AdjustmentToolGuide.html
Also lots of tips about workflow, etc. here:
http://www.bagelturf.com/
You probably won't want to spend too much money if you're just using the trial, but Ben Long's book
Aperture Pro training Series: Aperture 1.5 is very good.

RAW Processing Change?

Today, I believe after installing the version 5.01 Digital RAW Compatibility Update, all of the pictures in my library produced by my Nikon D2x and D3 cameras are listed as being adjusted using an "earlier version of Apple's RAW processing." And clicking on the button to reprocess the RAW images does result in very minor changes.
These cameras are pretty old models. Did Apple really sneak in some changes to RAW processing engine for older models along with the added models listed in the RAW Compatibility update? Nothing was said about this in the update page, and this happened before only with a major Aperture version introduction. Did this happen for anyone else?

I'm seeing changes for many, perhaps all, my Sony camera bodies. But first, note that the Images aren't -- iirc -- marked as "needing" to be re-converted -- they are simply marked as having been converted by a superannuated version of Digital Camera RAW. I create my own RAW tuning settings, and save them as the default. With DCRAW 5.x, I had to create new ones and save them again as the default. But I didn't have to change any Images that had been converted with any of the older DCRAW versions.
I think the notice I got was very similar to the one that shows up when you use the old "Highlights & Shadows (sic)" adjustment brick.

Using old raw converter - why?

Aperture 3.2.3 has started importing images and processing them with an old raw converter for some reason. When I look at the image the first brick of the Adjustments tab contains a warning that the raw file was convertered using an old raw converter and giving me the option to update the processing. This has just happened all of a sudden, and I can't find any preferences to change the processing engine to the proper converter. Any ideas? Thanks.

I just noticed that there's an update to 3.2.4 anf to the raw converter. I applied those updates and the problem has gone away. Not sure why it happened in the first place 'though. One of those things...

Strange RAW processing problem

I've just jumped into the Mac world recently with a Mac Pro (which I absolutely love). I've been watching Aperture since it was announced. A friend of mine has been using it for a while. He has Cannon cameras and so he is golden. However, I was playing with it the other day to get a feel before I decided to purchase. I loaded up a set of RAW files from my Olympus E-500 and was ready to play. Unfortunately several of my shots ended up looking like this on screen:
http://PhilU.smugmug.com/photos/103737186-M.jpg
Lightroom (Adobe's RAW processing has always been excellent) shows the same problem images just fine:
http://PhilU.smugmug.com/photos/103737163-M.jpg
This is on Aperture 1.5 on 10.4.8.
This seems to be an issue with long exposures that have the "Noise Reduction" (dark fram subtraction) turned on. I had a few long exposures with it turned off that looked fine and also some shorter exposures with it turned on that looked fine. That's just speculation though.
Has anyone else run into this? Is there anything I can do to make it work?

Yea, same for me in all apps using the core RAW functionality (Preview, iPhoto, Aperture, etc.)
I had thought this thread was dead long ago. I did get it submitted as a bug on http://bugreport.apple.com back then - it is still in "Open" status. Hope they get a chance to take a look at it.
The upside is that the workaround I mentioned before is still in effect. I also noticed that the last RAW update included a DNG fix so that files converted with the newer versions of the DNG converter are read properly. Would still be nice to have native ORF working properly (it does work fine most of the time, just not with images of the particular combination listed above).

Canon 6D RAWs processed awfully bad?!

Hi,
I previously owned a Canon 400D and loved Aperture for the entire workflow, it was just a breeze. Now got a new Canon 6D and also took some test photos with the 5D mk3, and every Raw that I import just looks awfully dark and contrasty.
That is, for a moment they look nice, and then, when they're fully loaded, they turn dark and contrasty.
I thought something would be wrong with the cameras, but opened up some of the pictures in lightroom or in Photoshop, using the adobe raw processor, and there, everything looks nice.
I never knew that the aperture raw processing was so bad, not just with colors, but also with noise reduction for example. Am I doing anything wrong, maybe with some secret color space setting or so (cam is set to sRGB), or are the raw profiles in aperture for these new cameras just not implemented properly yet?
Example Images:
Aperture:
http://chfilm.de/download/foto/IMG_0324A.jpg
Adobe Raw Conversion (nothing done, except hit auto adjust and increased the luma denoise a bit)
http://chfilm.de/download/foto/IMG_0324LR.jpg
what is going on?? I seriously what have never expected such an enormous impact on image quality by the software, especially since I thought Aperture was a Pro-tool. Look at the sharpness of the images!!

I have been fortunate enough to recently upgrade myself to a Canon EOS 6D. After my first shoot, I was heartbroken to see the poor quality of the images--dark, low contrast, etc. This was fixable in Aperture with some effort, but then I started noticing serious blue and orange color artifacts around high-contrast edges, and a near total loss of detail in deeper shadows. I was about to return the 6D as defective but then tried a couple images in Canon's RAW processing software. And I was blown away by the results--gorgeous images, perfect contrast and loads of shadow detail that could be extracted with the right adjustments. I also grabbed a trial of Lightroom, which produced results similart to Canon's software.
So there's nothing wrong with the camera. Apple's RAW converter for the 6D is just flat busted. How could something this bad have actually made it out the door?
I've been a long-term Aperture user--since version 2.0, and have grown to love the interface and the effortless workflow for organizing images. But the issues with the 6D RAW converter have pretty much forced me to abandon Aperture over night. Hello Lightroom.
As with previous comments, I suspect this is really just part of the thin end of the wedge with Aperture and that it may be headed for extinction. Sad.
Here is an example that shows the shadow issues. Both are 100% views of he same RAW file loaded without any additional adjustments--except that I've cranked up the shadow level to illustrate the Aperture RAW converter's failure:

Process for return of Components after sales

Dear Gurus,
Plz inform regarding the following process:
We require a process for return of the components ( part of the Finished goods that is sent to the customer) after the same is being returned by the customer and then that needs to be replaced by a new part. Please inform how to take the material back in our stock and send a replacement in respect of the same.
regards
PUB

Hi,
Are you trying to say that first you sell material to the customer.
Then your customer returns that material and then you do the modification to the material.
And again send that material to the same customer.
Is this what you are trying to say.
But what about the price where you want to accommodate your pricing.
The material which you are sending after rework is it free of charge delivery or you are charging some amount.
You can do the process as follow
Sales order u2013 delivery u2013 billing document u2013 return order wrt billing document u2013 done the PGR.
Now create new sales order for the newly created material after rework.
You have to create the sales and distribution BOM for your new sales order.
In that you can give the details about the return material also.
So that BOM will be exploded in the newly created order.
And the pricing you can do as per you want.
If its not working then please explain us the whole scenario for the better reply.
Regards
Raj.

My student has been using Lightroom 4 with Photoshop CS5 on her Mac for well over a year. Because of the difference between the Camera raw version available to her in Photoshop CS5 and the raw process in Lightroom 4, she has been exporting her raw images

Any ideas?

My student has been using Lightroom 4 with Photoshop CS5 on her Mac for well over a year. Because of the difference between the Camera raw version available to her in Photoshop CS5 and the raw process in Lightroom 4, she has been exporting her raw images from Lightroom and choosing the "Render using Lightroom option when it popped up in the dialogue box. She has been doing this for over a year and a half without any problem. Today when she hit Command E no dialogue box appeared and the image just opened in Photoshop. I'm concerned that all of her Lightroom edits are not being rendered to Photoshop. Anyone have an idea as to how we can get the "Render using Lightroom" dialogue back?

How do I update a folder of DNGs to the new 2010 (Current) Raw Process?

Is there an efficient method to update an entire folder of DNG images to the newer RAW process in Camera Raw 6.1 - to "2010 (Current)"?
And as an added bonus, it would also be great to simultaneously update the Camera Profile - to "Adobe Standard".
I have lots of folders of DNGs that were processed in ACR 5.7 or Lightroom 2.7, and so they were processed in the older, 2003, process version.
I see that when I update a single DNG in Lightroom 3's Develop Module that I am asked if I want to update all of the photos shown in the Filmstrip at the bottom of the window. This is very convenient!
My father does not yet have Lightroom 3, but does have Photoshop CS5 and ACR 6.1 installed and he wants an efficient method to do the same using those tools. We found that if we open the folder in Bridge, select all the DNG images, open the multiple images in Camera Raw, click on the "Select All" button in the upper left corner of the window, that we can then go to the Camera Calibration panel and make these two changes to all of the images simultaneously.
It seems like there should be some method of doing this from within Bridge. When we go to Edit -> Develop Settings -> Copy Camera Raw Settings and then select all of the other DNGs in the folder and go to Edit -> Develop Settings -> Paste Camera Raw Settings.... and choose only the Camera Calibration checkbox, that only one of the two settings actually gets changed; the Camera Profile setting does - the Process version does not.

austinmirage wrote:
Is there an efficient method to update an entire folder of DNG images to the newer RAW process in Camera Raw 6.1 - to "2010 (Current)"?
And as an added bonus, it would also be great to simultaneously update the Camera Profile - to "Adobe Standard".
You CAN easily make a Camera Raw preset or use Copy/Paste develop settings to change a folder's worth of files to "Adobe Standard"...that's simple. However, currently the Process version is not captured in a preset not copy/paste settings...the only current method is to actually open images inside of Camera Raw, select all and change the Process version to what you want...note, even Sync won't sync the Process version...only select all and then change the setting.
It's hoped in the future this will be somehow addressed...it will require that the subsetting for Process version be a separate item in the Camera Calibration settings.

Why my raw looks different in lightroom and camera's raw processing software

Hi, I am using a Sony A-100 and just start using Lightroom to process my raw file. I quite like lightroom's interface and its workflow, however, a a problem disturbing me is the image look quite different in sony's raw processing software and in lightroom (just import without any editing). In sony's software, the WB and exposure is correct and I don't need to adjust so much. But in lightroom, the color always looks warm and image is underexposure.
Is it a common problem or it is just a special case as to sony's dslr camera.

The main reason is that each different software is interpreting image and color data in its own way due, I guess, to different processing methods.
In that way, digital is not different than film : no film render colors and contrast the same way.
You have to choose what fits the best for you.
As an example, I think ACR / LR handle Canon files pretty well ( quite close to Canon's propietary raw converter - neutral settings - ). On the other hand, Nikon owners have more troubles and seem to prefer Capture 4 or NX renderings.
Gilles.

This photo was adjusted using an earlier version of Apple's RAW processing

It is May 16 2012. A couple of days ago there was an update to OSX. I am now at 10.7.4. My Aperture version is 3.2.3. Digital Camera Raw 3.12.0 build 615 and a bunch of zeros.
Last night when I imported a slew of photos, everything seemed to go well, but when all processing was complete all of the photos changed to a deep green hue. I finally found the message in the title line: "This photo was adjusted using an earlier version of Apple's RAW processing" and somewhat resolved the problem by individually reprocessing each master.
Does anyone know what has caused Aperture to act this way and how the problem can be fixed? From a timing perspective, I feel that it was the OSX update, but I cannot be sure.
Thanks in advance for any assistance.

I am on a MacBook Air (mid 2011) running Lion 10.7.4 and Aperture 3.2.3 with Digital Camera Raw 3.12.0. I have the exact same green photo import problem described above. I have a Panasonic Lumix DMC-GF3 and I shoot RAW. Sometimes (I can't seem to determine what triggers this), when I click on the photo and Aperture brings it up in the Split View, Aperture briefly re-processes the photo and displays it without the green tint, but now the photo is over exposed. If I right click->remove all adjustments, then the photo finally displays correctly.
Sometimes, Aperture tells me "This photo was adjusted using an earlier version of Apple's RAW processing".
The fix suggested by Snoop Dogg at https://discussions.apple.com/thread/3942768?start=30&tstart=0 took away the green tint. But now the recently imported photo is still over exposed. By default, I turn on "Auto Enhance" on on my imports into Aperture. I still have to right click->remove all adjustments, then the reapply the "Auto Enhance" quick fix before my photo finally displays correctly.
Any thoughts on this would be appreciated. Thanks.

Automatic Row Processing (DML) - Return Key Into Item

Hello,
This question is on Apex 4.2:
I'm Displaying the [UNIKEY] column value after the record is inserted into the table using :
page process > process row table_name > Source: Automatic Row Processing (DML) > Return Key Into Item > "Item Name"
This works fine while inserting records, my question is why this does not respond on update / delete ?
ϯ LT

LT
Check your branches.
What might be happening is that on insert and update an other branch is followed.
Where the branch of the insert either isn't clearing the cache of the page or is setting the item with it's own value.
The branch on the update on the other hand is clearing the cache of the page and not setting the item.
With a delete there is a clear cache process generate by the wizard. Check if this process is only running on the delete and not on the update.
From memory the process is called something with reset.
If the above doesn't help try to replicate the problem on apex.oracle.com and give access with a guest developer account so we can have a look.
Nicolette

Reversal process of return excise document

Dear all,
My user has created and posted a return excise invoice.
On posting it has created an excise invoice number and an accounting number.
Now it is noticed that while processing the return excise he had manually inputed some wrong values manually.
So he cancelled the internal document number through J1IS.
But the return excise invoice is not reversed.
So can anyone let me know in details how to reverse the return excise so that he can create another return excise invoice???
Its urgent so please help.
Regards,
Indranil

Hi,
in ECC6.0 Excise Invoice created in j1is is reversed / cancelled in J1IS only ( Shift+f6) , ask your FI consultant to check the Acc Document entry once is canceled / reversed thru J1IS.
Rgds,
Vikas

Leica D-LUX 4 (LX3) RAW Processing

Hi all,
Just wanted to report some interesting behavior regarding the long-awaited RAW processing ability for the D-LUX 4 and Panasonic LX3. I did not see this happen on the first library I coverted, because I let Aperture do the image processing, so the files were already converted when the Library upgrade process finihed.
Anyway, this time I did not process images when doing the upgrade of my personal library, because I wanted it to finish the task quickly. It did about 3 hours for some 40K photos.
I had been shooting RAW + jpg since I got my Leica D-LUX 4 in the hopes that Aperture would support it some day...and that day came!
Anyway, the .RWL RAW files show up in the browser view as black boxes with the warning triangle. They convert when you select them individually, and that was pretty much as expected.
What was cool though, was when I had opened an .RWL image into Split View, and then arrow key selected the next unprocessed image. Aperture displayed "Unsupported Picture Format" on top of a low res image that had really severe lens distortion for an instant in what appeared to be a 16:9 or longer aspect ratio image, then displayed the properly converted 4:3 RAW file.
This is obviously the lens correction processing that is part of the way the camera operates, and that A2 was incapable of converting correctly. I thought it worth mentioning that you can sort of see it at work in A3.
It is so great to have A3 do such a good job on these files, and be so responsive. Really enjoying getting to work with my Leica RAW files finally.
THANKS APERTURE TEAM!
Sincerely,
K.J. Doyle

Tonys264 wrote:
I have been waiting for over a year for RAW support for the Leica D-Lux 4 using Aperture 2. It seems that this support is only going to be offered for Aperture 3 users. I have asked at my local Apple Store for an explanation without any success. Is it really just a marketing ploy for A3, or was there a technical reason why A2 could not have support for this camera??
Hi Tony,
Now I am not sure if this conversion works on a machine without Aperture 3 on it, because all of the machines here have A3 on them...
BUT...
I just dragged a .RWL file into iPhoto and it opened, no problem.
I have no control over the conversion, of course, and the better control system for RAW is what you are paying for in A3.
I shot over 30K images with my DL4, storing RAW + JPG hoping for this, and seeing them come up in A3, and be so workable (better that Phase one) was a very happy day for me.
Sincerely,
K.J. Doyle

Problem with leave to list-processing and return to screen

Hi all,
I am designing a screen in which I have provided a pushbutton which will allow the user to upload (via BDC) the price list to VK11 transaction. And consequently, after upload the BDC message will be captured and displayed as an ALV list. for this, I am using leave to list-processing and return to screen 100 statement.
My problem is, when I return from the alv list screen by pressing back/any button the called screen 100 is displayed as a dialog window. but actually the screen 100 is a normal screen.
How can I rectify this problem?
Thanks,
Rajan

rajan,
i think the below link will clear your problem.
[http://help.sap.com/saphelp_nw04/helpdata/en/9f/db9d2f35c111d1829f0000e829fbfe/frameset.htm]
Regards,
Venkat

Old Raw processing bug returns.

Similar Messages

Maybe you are looking for