Matching dng and jpeg workflow

Hi all. I searched high and low for the answer and can't seem to find what I am looking for...so here it is.
I am moving to Lightroom from Aperture. There was a really cool feature that I used and want to do or hope to do the same in LR.
Sometimes I shoot jpeg and raw on my camera and when I import, I only import jpegs. I rate and reject the ones I don't want and then I import again using a "match jpeg" feature. Could I do that in LR, if so how?
Also, for one folder I seperated the two, and if I wanted to do the same "matching dng to jpeg" could I?
thanks for any help
jg

There is no such feature in LR, as far as I know.
The best you could do is import everything (first setting the preferences so that you "Treat JPG next to RAW as separate photos"), then adjust the thumbnail size in the grid so that there are an even number of photos in each row, thus ensuring that the JPG will be next to the RAW, and then reject in pairs.
There is no benefit in Lightroom to putting these photos into different folders.

Similar Messages

  • "There was not enough memory" error message when saving DNG and Jpeg

    PC/Windows XP Pro. Pentium 4/2Gb RAM.
    I am constantly getting memory errors when trying to save batches of images from ACR4 either as Jpegs or DNGs.
    A couple of images in to the batch a small window appears with a list of the files and next to each of them is the line: "There was not enough memory."
    These are 220Mb TIFF files that are processed in Hasselblad's Flexcolor on the same computer. I can process an entire folder full (sometimes 50 images) without a hitch in Flexcolor, but Bridge/ACR4 and CS3 can't handle any reasonable number of images.
    Could it be something in my settings? For the record, they are:
    In Bridge, under Edit/Preferences/Camera RAW preferences, Camera Raw Cache is set to 10Gb. Jpeg and Tiff handling boxes are both ticked.
    Under Edit/Preferences/Cache, Cache Size slider is slightly over half way to the right.
    In addition, I have CS3 pointed to a formatted 500GB scratch disk all to itself.
    And CS3's RAM is set to 80%.
    Finally, this computer is used for nothing else except image editing.
    Any ideas?
    Thanks.
    D.

    Thomas,
    Thanks for the reply.
    If you mean by "Public Beta", did I download the 10.4Mb plug-in (as per John Cornicello's link above) and install it at Program Files\Common Files\Adobe\Plug-Ins\CS3\File Formats in place of the old plug-in, then yes.
    I always run ACR4 via Bridge, never via CS3. CS3 always comes after conversion in my workflow. Also, I like to give Bridge/ACR a free run of available resources. Nothing else is ever open when I'm running them.
    In CS3 under Edit/Preferences/File Handling, under Image Previews I selected 'Never Save'. Not sure if this affects ACR though.
    Also, as per the suggestion in the article referred to in my last post, I removed the tilde ~ to activate the Bigger Tiles plug-in. CS3's memory % is now set @ 90%.
    The only thing I haven't done is to activate the Microsoft 3Gb switch. I can't find instructions that are clear enough. Also, it may be that it makes no difference when running Vista 64bit, as I am.
    For what it's worth, with these fine tunings, CS3 now executes the Retouch Artist's Speedtest in 20 seconds, a shade faster than before. This is extremely fast, so my setup should not be the problem here. I hope! ;-)
    Finally, is there any point in trying LR? Or is its file saving/cache setup the same as ACR's?
    Thanks for taking an interest in my case. I'm very happy to be a guinea pig since I will constantly have to process large numbers of files and I'd like to overcome this problem
    Many thanks.
    D.

  • Viewing dng and jpg files

    How do you get LR4 to display both dng and jpegs seperately instead of as dng + jpg with the same file name.

    Disclaimer:  The following applies to WINDOWS EXPLORER.  I don't use Bridge so I don't know if it's applicable at all to Bridge.
    Adobe does not provide a codec for viewing Canon raw files as thumbnails.  Canon has one for free but it only works on a 32 bit Windows system.
    Early this year I found a free download for displaying raw file thumbnails that works on an x64 Windows system.  Since that time the author realized there's a real demand for this software and has started charging for it.  In any case, I find it works very well.
    http://www.fastpictureviewer.com/codecs/
    -Noel

  • In PSE 13, when I open a folder, jpeg files have a preview image, but PSD, DNG and CR2 files don't. Also, no thumbnail below the file list.

    Working in PSE 13, when I open a folder, jpeg files have a preview image, but psd files just have white sheet of paper as preview.  I have to open the file to be able to see it.  Also, there is no thumbnail of the file below the file list.Surely, there's a setting that needs to be changed. I did not have this problem with Elements 12. This is a real bother because I have to use Lightroom to see all the file types. It seems as if Elements is using the standard Windows file loader that can't show previews of file types it doesn't know including .PSD, DNG and CR2. Is that a bug or did I do something wrong? Thanks for any help.

    I am using Windows 7 64 bits. Working in the editor, I never use the organizer. The screen above is not the same at all that I got in Elements 12, it was completely different and showed me a thumbnail below the listing when I single clicked on one of the files. In Elements 12, I also could see  a thumbnail of all the file types, not only the jpegs. It is as if the loader is the regular Windows used anywhere, not the right one for Elements. I hope someone understands my problem.. Thanks.
    Mike

  • Move RAW and JPEG / JPG together

    Ok, here's one thing that I find *really* annoying.
    I often shoot raw + jpeg so that I can give smaller files to models or stylists without having to do a tonne of post-processing.
    However, it looks like LR doesn't handle this situation very well. If I have a raw + jpeg pair in a folder and drag that image to another folder in LR, it looks like only the raw will be moved. The jpeg stays in the folder it was originally in.
    This kills my workflow, as I have to either delete my jpeg's or move them by hand. It would be very nice if LR could recognize that the images were linked and move them both if I put the RAW file into a different directory, even if it is only applying edits to the RAW.
    Thomas Park

    I would like to see two parts to this:
    * the ability to import (or not) raw & jpg of the same root name. In other words, if I turn it on, I want "foo.dng" and "foo.jpg" both imported. If off, then import "foo.dng", and do not import "foo.jpg".
    * Once imported, I would like to be able have Lr let me separately manipulate the two files, or manipulate one while the other lurks in the shadow. For example:
    ** When treating separately, I should see "foo.dng" and "foo.jpg" as two separate images
    ** When manipulating just one, I would like to be able to see only one slide in the library, and have edits to metadata apply to both. I'm not sure about during develop: I think I would want to develop the raw, and have no processing applied to the jpg. But it seems like I'm asking for something inconsistent and maybe confusing to people: metadata edits apply to both images, processing applies to one.

  • DNG/raw+XMP workflow comparison

    [ Note: this discussion has been branched from an existing one (link on top ^) and deals about DNG-raw+XMP -PECourtejoie ]
    Omke Oudeman wrote:
    What Disk based XMP data file you are referring to and you think Camera Raw get's involved in this while writing metadata? Could you specify your thoughts about that, I thought it only reads the new thumbnail after saving metadata to the newly saved filed after a keyword has been added.
    And an other thought, you have to set the Camera Raw general section to save image settings to either side car XMP files or Camera Raw Database. Might this be of importance to set to either of the two for testing. That said, default is sidecar files and I don't see any benefit with saving in a central data base instead of having the settings traveling in (DNG) or beside (XMP sidecar)
    I deal primarily with image files, specifically NEF, PSD, and JPG. All Camera Raw 'edits' are stored to the XMP sidecar files (in the case of NEF files), or as embedded metadata (in the case of the other formats). Of course, they aren't really edits, and are more like conversion instructions for Camera Raw.
    Whenever I keyword raw files, their XMP sidecars are modified to include the keywords. If you inspect one of these XMP sidecars, you will see that they contain Camera Raw settings, keywords, and camera EXIF data--anything you might need to know about the image, stored externally to the image file. I don't know for sure, but I guess that some or all of this information is also stored in the Bridge database. I would never dream of trusting XMP data to a single database, as it constitutes many hundreds/thousands of hours' work. As it stands, I like that I can keep the XMP with my raw files, where I can see them!
    It's important not to get confused between the Bridge database and the Bridge cache, and the equivalent database/cache belonging to Camera Raw. I haven't found much information on the Bridge database--I guess it's central to the operation of Bridge and the way it handles files and its cache. The Bridge cache appears quite straightforward, being a hierarchy of jpegs designed to allow Bridge to display images quickly.
    Bridge uses Camera Raw in order to generate 'High Quality' thumbnails and previews of supported image types, based on XMP data, optionally including TIFF and JPEG. Camera Raw has its own mysterious database and cache, but this internal working is irrelevant to this subject (AFAIK) as Bridge only uses Camera Raw as an API for generating previews for the cache, and keeps an eye on any file updates made externally in order to keep its own records up-to-date. This is presumably why Bridge is always reading the disk.

    I deal primarily with image files, specifically NEF, PSD, and JPG. All Camera Raw 'edits' are stored to the XMP sidecar files (in the case of NEF files), or as embedded metadata (in the case of the other formats). Of course, they aren't really edits, and are more like conversion instructions for Camera Raw.
    Same here although my NEF's are CR2 form Canon and always converted to DNG, so no worry about sidecar files that can be lost
    Whenever I keyword raw files, their XMP sidecars are modified to include the keywords. If you inspect one of these XMP sidecars, you will see that they contain Camera Raw settings, keywords, and camera EXIF data--anything you might need to know about the image, stored externally to the image file. I don't know for sure, but I guess that some or all of this information is also stored in the Bridge database. I would never dream of trusting XMP data to a single database, as it constitutes many hundreds/thousands of hours' work. As it stands, I like that I can keep the XMP with my raw files, where I can see them!
    Here is where I got a little lost, as earlier stated I was not aware of keywords, labels and rating stored in sidecar XMP, I always thought those files only contained the ACR settings. Using DNG one of the many pro's (sorry Mike, don't want to start again ) is that all info is stored in the file itself and no sidecar files.
    And to be honest, I won't have many problems with lost ACR settings, they can be easily recreated for my workflow and in the analog days you were also not able to recreate a negative in the same way after a few days or more due to different chemicals/temperature, enlarger light source strength, other box of paper and not to forget your own moods....
    But losing other IPTC settings like copyright and keywords is a problem. When having converted ('developed') the raw files there is no problem for this info, it is stored in the file info and according to IPTC standards visible by most applications.
    I have decided to not provide vital info on raw files (CR2 or DNG) other then rating/labeling and changing the filename to yyyymmdd and sequence number. My keywords and description etc are only added to the keepers. They are renamed too but with the same yyyymmdd and a more relevant name and sequence number. I also include the original filename option while batch renaming. The DNG files are just stored on a HD with a proper year and date folder structure, there are also far to much raw files to put all those effort for keywording in.
    The keepers are going in my central archive and I use Canto Cumulus single user as DAM. When needed I can find the originals very easy, even don't use Bridge to look for the right one, just glance at the original filename, use the Finder (windows explorer?) to find the files on the external HD and copy the wanted file with some others from same series and these are cached in Bridge to look at and work on. I do so because Bridge takes to long to cache (even with only thumbs) from external sources and the above mentioned method is much faster
    It's important not to get confused between the Bridge database and the Bridge cache, and the equivalent database/cache belonging to Camera Raw. I haven't found much information on the Bridge database--I guess it's central to the operation of Bridge and the way it handles files and its cache. The Bridge cache appears quite straightforward, being a hierarchy of jpegs designed to allow Bridge to display images quickly.
    For me there is no confusion between Bridge cache and ACR cache, they are both easy to find and I regularly dump the whole Cache file for Bridge after it has grown over 30 GB in size. I can't rely on Bridge for use of DAM and it gives a fresh start and the cache rebuilding is not that time consuming when it can do its work and you don't need the computer yourself. I also don't worry about the ACR cache, it does not grow above 1GB and replaces the oldest with the newest so don't have to clean it myself.
    just wondering where to find the Bridge Database, can't find it and according to the activity it should have huge sizes??
    It is still a mystery to me.

  • Copy original TIFF to DNG and import?

    Does Lightroom support the option "Copy as dng and import" when the source files are tiff?
    The reason is that I would like to be able to copy my original tiff files as dng and then import into Lightroom. The tiffs are 16 bit tiffs generated from Nikon Capture.
    The menu system allows me to choose this option, but all the files get copied as tiffs and imported as tiffs even though I have chosen the "copy as dng" option.
    This is a major setback as the tiffs are about 60MB each, whereas the dngs Lightroom generates from a Nikon NEF raw image are under 10MB each.
    I can't seem to figure out a way to convert all tiffs to dng on import into Lightroom.
    Thanks.

    Caine-
    You're definitely deriving good insight from all of this!
    As far as your color and tone, others have seen similar things with Canon's DPP software. The answer to these discrepancies has been that Canon and Nikon understand their RAW files better than Adobe can understand them because they don't share their "secrets" with Adobe. But, what we can do is take one of a few approaches in LR: one is to find some presets that other users have developed for your camera and import them into LR, see what works, and apply them. Another is to develop presets yourself: you can save a Develop Preset, set a preset at import, or set a "Default Preset" for your camera. There is also a method that gets used a lot to calibrate your camera in Camera Raw using a GretagMacBeth color card, then open the image in Photoshop and running a script that analyzes the captured colors and puts out a calibration preset for your camera.
    As far as high ISO settings, others have complained about LR's noise reduction for higher ISO's, so you're not alone. I noticed something interesting, though, in the past couple of days. I was testing my daughter's Canon Rebel, which she has capturing RAW+JPEG, as I was setting up LR on her computer. I decided to check out her high ISO quality (it goes up to 1600) and found that Canon's in-camera noise reduction, which it applies to the jpegs, was quite good. At first glimpse it seems better than what I could do in LR.
    I guess, Caine, that if I was in your position, I would import all of my RAW into LR, and just use the Nikon tiff approach for the images I needed to edit for use. I know what you mean about huge files. Fortunately, hard drives are cheap compared to earlier days, but still...so, I would approach my workflow like import into LR, do whatever I could with LR, but for output go to Nikon first to create a tiff before, say, editing in Photoshop or whatever.
    Tony

  • RAW+JPEG workflow solution needed

    Question to any pro's out there-nitpicky. Aperture 3. I have imported 1000's of files via seperate RAW and JPEG import option into projects, then created a RAW album and a JPG album within each project via a file type filter. I have done this because I want to have the ability to choose to save space by deleting some unwanted RAW files that I know I will never edit, but keep some of those JPEGs. For some I might want to keep RAW and not have the JPEGs. Sounds funny, but the space adds up when shooting 7fps, thousands of 6 MB JPG add up. Here is my question. I have been rating a bunch of the RAW in my RAW album within a project. I have lots of files that I have rejected. Is there a way to automatically match the associated JPEGs of these already rated rejected files that I don't want either RAW or JPEG without doing so manually in the project "parent" folder. HELP! I didn't see this hiccup and I have manually seperated all my projects this way. Is there a better way to do this workflow in the future once I have found a way to straighten this mess out?

    Sorry - how thoughtless - here are the steps (pretty much off the top of my head)
    -Autostack the RAW JPEG pairs
    -Make album of RAWs and album of JPEGS with corresponding file types as album picks
    -Go through RAW album w/ stacks closed and label all RAWs to be rejected.
    -Go to JPEG album and open all stacks filter by label to pick up the image stacks with JPEGs to keep select all and create new album called KEEP JPEG
    -Go to JPEG album filter by label select everything, get rid of filter, invert selection
    -Create new album called KEEP RAW
    -Go to KEEP RAW album open all stacks filter by file type JPEG, select all, delete images
    -Go to KEEP JPEG album open all stacks filter by file type RAW, select all, delete images
    I just did that off the top of my head without being in front of Aperture so it might a little wrong but you get the idea. With short cut keys it isn't a huge deal but still too much for me to do on a regular basis to save a couple megabytes.
    RB

  • The raw portion of a referenced master got separated from its jpeg pair when I was relocating originals.  Can I recombine the raw and jpeg pair?

    Hi, I'm a fairly new Aperture user and have just started storing my photos on an external hard drive. An error message appeared when I was relocating originals of a project. It stopped relocating at one image, saying that the jpeg file did not exist. I found the raw file name under the new project folder that I was relocating it to, but it's jpeg pair did not move. The file names look identical except one ends in .JPG and the other as .NEF. I tried to combine originals, but I got the same error message and when I looked at the files the raw now had (1) attached to it, whereas the jped didn't. The Aperture window started to close unexpectedly many times. I tried Repair Permissions and Repair Database and that seemed to stop Aperture from closing unexpectedly, but the raw and jpeg  pair are still in separate folders. How can I get them paired up again or does it matter? I'm using Mac OS X and Aperture version 3.4.5.
    Thanks,
    sophie

    If you don't take care when choosing the location for referenced images, you can create some problems for yourself.
    From an operational perspective 'Managed' images means Aperture will take care of the image file storage for you, 'Referenced' means you will take care of it yourself.
    There are a number of things that may have happened but this is what I think is most likely:
    If you shoot a lot of photos with the same brand of camera, eventually you'll end up with duplicate file names, for example two different files called DSC_1234.NEF. If you attempt to store these in the same folder yourself, worse case scenario is you may inadvertently overwite one of the files. If you use Aperture to relocate, you'll get one of the files with a new name of DSC_1234 (1).NEF.
    So your first step is to figure out what these files really are. Are they duplicates, or are they different files with the same name, and do they each have a matching .JPG
    Aperture has the tools to fix up the problem, but you need to confirm what the problem is first.
    If you don't have many of the (1) files, it may be worth continuing your 'relocate' to subfolders - making sure your subfolder hierarchy doesn't cause duplicate names to be stored together. Then when everything else is stored correctly, address the problem images by moving them to where they should be, with the right name and the JPG/NEF pairs together.
    You can then search for missing files in Aperture and use the 'Locate Referenced Images' to reconnect them with Aperture.
    Andy

  • Matching Raster and Vector RGB color in InDesign CS3.

    We print on a Durst Lambda RGB imaging device to photographic paper. All color management is done as an early bind (raster files are converted to the printer's color space and vector colors are chosen from a palette database). So basically the files must go through InDesign without any color change in raster or vector information. We have clients that require specific RGB builds for logo colors the are present in both their raster and vector files.
    Color Management is set to "North American General Purpose 2" with "RGB: Preserve Embedded Profiles" selected.
    1) The file is exported as a PDF 1.4, High Quality, PDF/X_None.
    2) The PDF was ripped on a Cheetah RIP (Jaws level 3) with no color management on.
    3) Solid raster colors such as 0-255-0 will reproduce as 0-255-1.
    4) The color differences between the raster and vector are usually 1-4 points.
    5) The vector is consistent as was input in the programit's only the raster that changes. When you are trying to match raster and vectors logo colors it is a killer.
    However, I can go into the InDesign (or Illustrator) color settings and turn color management off (This is our current workflow). In doing this the RGB working space uses the monitor profile and "color management policies" are set to OFF. With these settings the RGB raster and vector match. The problem with this work flow is two fold:
    1) We have other devices than our RGB Durst Lambda that can use the InDesign color managementVutek flat bed 3200 and grand format 3360.
    2) We have had many occurrences where the custom "color management off" settings have reverted back to the default "North American General Purpose 2"without any intervention.
    I have tried this with different RIP's with the same results.
    Does anyone have an idea to create a simple PDF workflow and keep the color information consistent?
    Program: InDesign CS3 5.0.2
    Platform: Mac OS 10.5.2
    Computer: G5 tower with 4 gigs of RAM

    I believe that setting is an old Illustrator setting that has been saved to effectively turn the color management off. The monitor profile effects the image displayedit doesn't effect the color transform.
    Anyway, the color management I want to use is the "North American General Purpose 2".
    To reiterate:
    The procedure:
    1) The file is exported as a PDF 1.4, High Quality, PDF/X_None.
    2) The PDF was ripped on a Cheetah RIP (Jaws level 3) with no color management on.
    The Problem:
    3) Solid raster colors such as 0-255-0 will reproduce as 0-255-1It changes from the original raster color placed in InDesign.
    4) The color differences between the raster and vector are usually 1-4 points.
    5) The vector is consistent as was input in the programit's only the raster that changes. When you are trying to match raster and vectors logo colors it is a killer.
    To summarize, the color of the raster file will change from the original that was place into the documenteven though nothing was selected in InDesign that would change the color (i.e. profile conversion to an output profile or a transparency effect used). The change is slightbut there.

  • Windows 8 Elements 11 Problem with DNG and CR2 files

    Have a Windows 8 machine with Elements 11 which has Camera Raw 7.4 installed and showing correctly in the editor. The Browser shows thumbnails of the DNG and CR2 files, but when an attempt is made to edit them, the editor opens but does not open the file. Same thing happens if I try to open the file using the File Open from the menu.
    Also I have been through the help and forums and found an article about opening jpeg files as Camera Raw files (http://blogs.adobe.com/pselements/open-jpeg-files-in-adobe-camera-raw-in-photoshop-element s/) and this does not work either.
    Help please !

    Disclaimer:  The following applies to WINDOWS EXPLORER.  I don't use Bridge so I don't know if it's applicable at all to Bridge.
    Adobe does not provide a codec for viewing Canon raw files as thumbnails.  Canon has one for free but it only works on a 32 bit Windows system.
    Early this year I found a free download for displaying raw file thumbnails that works on an x64 Windows system.  Since that time the author realized there's a real demand for this software and has started charging for it.  In any case, I find it works very well.
    http://www.fastpictureviewer.com/codecs/
    -Noel

  • "Save PDF to folder as JPEG.workflow"

    ...is now missing from my library/PDF services folder.
    I use Aperture to design my books, which I have printed by Asuka and other vendors. I set up workflows to export the books at the appropriate DPI (271 for Asuka, 300 for the flush mount albums I do).
    When the the JPEG's weren't showing up in the folder I tried to save to I checked my Library/PDF services folder to find the "Save PDF to folder as JPEG.workflow" missing.
    Should I re-install Aperture from the disk? If I do so how will it affect my library?
    Thanks

    Installing Aperture again will not affect your library, so there is no risk doing that.
    Regards
    Paul K

  • Import from HD folder with NEF and JPEG files-Can't see JPEG files

    I am using Aperture 2 and I am trying to import from an external HD folder of images, with both NEF and JPEG files of the same photo. Using the import function, the import pane only shows the NEF file, not the JPEG file. Is there a setting somewhere that will allow me to see the JPEG file also, so I can import only the JPEG. (note: if I move the JPEG to a different folder away from the NEF file, then the JPEG appears and I can import it.)
    PS I am importing only the JPEG because I have a Nikon D60, which is still un-supported.

    You could import both, select all images afterwards, select 'Create version from master jpeg'(alt-J), unstack all (shift-cmd-K while everything is still selected), sort by file size to separate the raws from the jpegs, and delete the raws.
    Or run the raws through Adobe's DNG converter (which in its newest version, 4.4, supports the D60) and use the DNG baseline support until Apple (or rather Aperture) supports the D60.

  • DNG and Color Negatives

    This may seem to be out in left field but here goes...
    I've been using custom camera profiles in LR to help get better color when scanning color negative film using Vuescan from my Nikon scanner. Vuescan can output a DNG file that contains the metadata tags for Make and Model so I can shoot a color chart, scan it and run it through profiling software (either DNG profile editor or Colorchecker Passport) then use the profile in LR's Camera Calibration to help zero in the color. It works fairly well.
    Now I'm scanning larger negatives on an old Imacon Flextight, which is producing great scans as far as dynamic range and sharpness are concerned but doesn't have profiles for the new film I'm using. I figured I could use the same strategy as with Vuescan if I could get the metadata tags set in the tiff files then convert to DNG and make a profile. I've been using Exiftool to set every Make and Model tag I can write to, and it shows up in LR's metadata pane as being set, but the profiles aren't matching up with the file (i.e. they don't show up as options in the Camera Calibration drop down).
    What am I missing to get these to match up?
    Thanks.

    Can you please send me two examples:
    1.  One of your old DNGs (for the case where the profile shows up correctly in Lr).  Please also send me the profile that works with this DNG.
    2.  One of your new DNGs (which doesn't work).  Please also send me the profile that you're trying to use with this DNG (which isn't showing up).
    With these 4 pieces, I can figure out what's going wrong.
    [email protected] (yousendit.com, dropbox, etc.)
    Thanks.
    Eric

  • Stacking of DNG and CR2 files

    When creating DNG files, I prefer to leave the CR2 files in the same directory and not embedded in the DNG files.
    This prevents the DNG files from doubling in size and thus prevents them from taking twice as long to open/read/write/etc.
    However, LR does not recognise IMG_1234.DNG and IMG_1234.CR2 as being the same like it does IMG_1234.CR2 and IMG_1234.JPG.
    It would be nice for it to automatically stack photos like this:
    DNG
    CR2 (or other native raw)
    JPG

    I doubt many use the same schema for both DNGs and RAWs in the same folder. For one, it'd be too easy to in some cases edit the RAW, and others editing the DNG. One reason I never shoot RAW + JPEG; having all three would be unworkable for me.

Maybe you are looking for