Preview Image Extract Program for PC

I had an unfortunate hard drive crash where I lost my original Raw images, but left me only with Lightroom Previews. I had read that there was a technique which used a Mac program File Juicer to extract the JPEGs from the Lightroom Catalog Previews.lrdata files; however, I am using a PC. It would be great if someone knows of a similar application for PC or another method of going about this on a PC. Thanks!

http://www.ploki.info/index.php?pagename=Main.LightRoomRecover
I didn't try it myself, so I can't say if it works.
Juergen

Similar Messages

  • Message no. R3009 - error in extraction program for the DSO

    Dear All,
    I get the following error, when I execute the data source object, when I select monitor button in the window the process is in Red.  So I couldn't get the report at the ODS.  Please help me to clear the following error :
    The extraction program does not support object ZSHIPTRACKND
    Message no. R3009
    Diagnosis
    The application program for the extraction of data was called up using the invalid InfoSource/invalid InfoObject ZSHIPTRACKND.
    System Response
    The data extraction is terminated.
    Procedure
    Check the SAP Support Portal for the appropriate Notes and create a customer message if necessary.
    with Regards,
    Jerald

    What release are you at?
    Have you searched SAP Notes and the SDN forums for this. A quick search indicates 9 SAP Notes and 15 SDN posts regarding this error message. Unless we know what release level you are at we are unable to offer viable solutions.

  • Extraction program for EH&S (EH&S to XI scenario)

    Dear Experts,
    I am from the XI background and am new to EH&S. I would like to know whether there exists an extraction program to extract substance data from EH&S(ECC) and send it to XI. If yes then what is it? The EH&S team here doesn't know of any kind. They have only used Change pointers to extract data from one client to the another.
    Please help.
    Thanks,
    Merrilly

    Hello,
    How to set up ALE for substances is described in the IMG / Customizing for EH&S.
    For EH&S 2.7B on R/3 4.6C this is located under:
    Environment, Health & Safety -> Product Safety -> Interfaces -> EH&S Application Link Enabling (ALE) -> ALE for Specification Management.
    All necessary information should be found in 'Set up Distribution of Specification Data':
                                                                                    Set Up Distribution of Specification Data                                                                               
    In this IMG activity you set up the distribution of data on                   
         specifications (see also Information About the Concept in EH&S                
         Application Link Enabling (ALE)).                                                                               
    Requirements                                                                               
    1.  Setting the Active Code Page                                              
             To transfer the data using ALE, you must ensure that the active code      
             pages are the same in the receiving system and sending system as          
             follows:                                                                               
    -   You must select a code page for transfer (for example, SAP(ISO)       
                 code page 1100) that you set up on all SAP Systems that belong        
                 to your ALE distribution model.                                                                               
    -   In Customizing for Product Safety in the IMG activity Specify         
                 Environment Parameters using the environment parameter                
                 ALE_TRANSFER_LANGUAGE, you must specify a language of the             
                 previously selected code page as the transfer language in the         
                 sending system. This language controls which code page is active      
                 in the sending system during data transfer.                                                                               
    -   The RFC destinations of the target systems must be defined with       
                 the logon language that corresponds to the specified code page.                                                                               
    -   If data is to be transferred to different SAP(ISO) code pages,        
                 the operating systems of the sending and receiving systems must       
                 use the same character sets (ASCII or EBCDIC):                                                                               
    Sending system      Receiving system        Transfer possible             
             AS400               AS400                   Yes                           
             UNIX                UNIX                    Yes                           
             NT                  NT                      Yes                           
             NT                  UNIX                    Yes                           
             UNIX                NT                      Yes                           
             AS400               NT                      No                            
             AS400               UNIX                    No                            
             NT                  AS400                   No                            
             UNIX                AS400                   No                                                                               
    For more information, see:                                                                               
    -   The IMG activity Specify Environment Parameters                                                                               
    -   The IMG activity Set Up EH&S Native Language Support                                                                               
    -   The Product Safety documentation in the section EH&S Native           
                 Language Support                                                                               
    2.  Settings in Customizing for Distribution (ALE)                            
             You have made the necessary settings in Customizing for Distribution      
             (ALE).                                                                    
             Also maintain, for example, the sections                                                                               
    -   Basic Settings                                                                               
    -   Communication                                                                               
    3.  Settings in the Product Safety Component                                  
             Make sure that you have fulfilled the following prerequisites:                                                                               
    a)  Maintain the environment variables for serialization                    
                 Serialization collects the IDocs and makes sure that they are           
                 processed in the correct order. For more information, see               
                 section Serialized Distribution in Customizing for Distribution         
                 (ALE).                                                                               
    You specify the serialization number for the sending logical            
                 system in the IMG activity Specify Environment Parameters using         
                 the environment parameter ALE_SERIAL_ID. You specify one unique         
                 channel per logical system.                                                                               
    b)  Specify specifications to be distributed                                
                 If you want to distribute specification data manually, choose           
                 the specification directly from the hit list in specification           
                 management.                                                             
                 For automatic distribution, the specifications must appear in a         
                 set of hits that is assigned to the distribution method. If a           
                 set of hits has not been assigned, all of the specifications are        
                 distributed, providing that you have not defined filters.               
                 Apart from standard filters (see below), you can use the                
                 following customer exits to define further restrictions and             
                 filters:                                                                
                 - Specify Additional Table and Parameter Filter (1)                     
                 - Specify Additional Table and Parameter Filter (2)                                                                               
    c)  Ensure unique identification of specifications                          
                 The specification object must have a unique specification key.          
                 In the standard system, identification is supported by the              
                 specification key.                                                      
                 You can use the customer exit Develop Enhancement for                   
                 Identification to enhance the identification, for example, to           
                 link with one or more identifiers.                                                                               
    d)  Check authorizations                                                    
                 For manual distribution and automatic scheduling, you must have         
                 the read authorization for all the specification data to be             
                 distributed.                                                            
                 You also need the appropriate authorizations for inbound                
                 processing in the target system.                                                                               
    Activities                                                                               
    1.  Maintain the Distribution Model in Distribution (ALE) Customizing           
             In Customizing for Distribution, call the IMG activity Maintain             
             Distribution Model.                                                         
             For more information, see the documentation for the IMG activity.           
             To guarantee communication between systems during distribution, you         
             must make the following entries in the IMG activity Maintain                
             Distribution Model by choosing Add method:                                                                               
    Field             Entry                                                      
            Sender/client:    <Key for EH&S system>                                      
            Receiver/server:  <Key for target system>, for example,                      
                              Sales and Distribution system (SD), on which EH&S          
                              is installed.                                              
            Object name/interface:   Substance (substance(specification),                
         BUS1077)                                                                               
    Method:           SavRepMul (save replicated specifications)                                                                               
    Note:                                                                               
    Message type SUBMAS is supported.                                                                               
    You can set the following filters:                                                                               
    -   Reducing specifications by determining recipients:                               
                 You can reduce the specifications to be distributed by defining                  
                 the following filters:                                                           
                 - Specification type                                                             
                 - Authorization group                                                            
                 - Substance nature                                                               
                 - Set of hits (external key of group object)                                     
                 You can enter several values for a filter field. Individual                      
                 values are linked with OR, whereas the filter groups are linked                  
                 with AND.                                                                               
    If no filters are entered, all specifications are distributed.                                                                               
    -   Reducing specifications using 'IDENTHEADER' filtering                            
                 You define the identification category and identification type                   
                 whose specifications are to be distributed.                                                                               
    -   Reducing data using 'PROPHEADER' filtering                                       
                 You specify the value assignment types for which specification                   
                 data is to be distributed.                                                                               
    -   In Distribution (ALE) Customizing, you can use the IMG activity                  
                 Set Up Segment Filtering to exclude further tables from                          
                 distribution, for example:                                                       
                 - Material assignment                                                            
                 - Regulatory list assignment                                                     
                 - Reference specification assignment                                             
                 - Usage                                                                               
    - Assessment                                                                               
    Then in Distribution (ALE) Customizing, you maintain the IMG                         
             activity Generate Partner Profiles.                                                                               
    2.  Maintain Settings in the Sending and Recipient Systems                               
             The following tables must be maintained in the same way in the                       
             sending and recipient systems:                                                                               
    -   Value assignment type TCG01 and description TCG02 (system                        
                 tables)                                                                               
    -   Table of names for the DDIC objects TCG03 (system table)                                                                               
    -   Table of names for the child DDIC objects TCG04 (system table)                                                                               
    -   Specify Value Assignment Types                                                   
                 Value assignment type TCG11 and description TCG12                                
                 Value assignment type - specification type assignment TCG13                                                                               
    -   Identification category TCG21 and description TCG22 (system                      
                 tables)                                                                               
    -   Check Identification Types                                                       
                 Identification type TCG23 and description TCG24                                                                               
    -   Check Identification Listing                                                     
                 Identification listings TCG26 and description TCG27                              
                 Definition of identification listings TCG28                                                                               
    -   Assign Characteristic-Specific Identification                                    
                 Overriding identification list definitions TCG29                                                                               
    -   Specify Specification Types                                                      
                 Specification type TCG31 and description TCG32                                                                               
    -   Specify Authorization Groups                                                     
                 Authorization object TCG36 and description TCG37                                                                               
    -   Specify Types for User-Defined Texts                                  
                Value assignment text type TCG41 and description TCG42                                                                               
    -   Create Sources                                                        
                Source TCG46                                                                               
    -   Specify Source Types                                                  
                Source type TCG47 and description TCG48                                                                               
    -   Set Up Property Trees                                                 
                Property tree TCG51 and description TCG52                             
                Property tree - value assignment type assignment TCG53                                                                               
    -   Specify Data Origin                                                   
                Data origin TCG56                                                                               
    -   Specify Phrase Libraries and Phrase Groups                            
                Phrase library TCG61 and description TCG62                            
                Phrase group TCG63 and description TCG64                                                                               
    -   Specify Language Selection                                            
                Phrase language (languages supported in phrase library) TCG65                                                                               
    -   Value assignment type class characteristic TCG66                      
                System table, filled using master data matchup                                                                               
    -   Check Value Assignments                                               
                Value assignment assessment TCG71 and description TCG72                                                                               
    -   Specify Component Types for Compositions                              
                Component type TCG76 and description                                                                               
    -   Specify Regulatory Lists                                              
                Regulatory list TCG81 and description TCG82                                                                               
    -   Specify Ratings                                                       
                Value assignment rating TCG86 and description TCG87                                                                               
    -   Specify Validity Areas                                                
                Validity area TCG91 and description TCG92                                                                               
    -   Specify Usage Profiles                                                
                Usage profile TCG96 and description TCG97                             
                Usage profile - rating - validity area assignment TCG98                                                                               
    -   Specify Exchange Profiles                                             
                Exchange profile TCGC3 and description TCGC4                                                                               
    -   Specify Environment Parameters                                        
                General environment parameters TCGENV                                                                               
    -   Protect Characteristics Within Namespace                              
                Namespaces for characteristics TCGK1                                                                               
    -   Manage User Exits                                                     
                User exit parameters from user exit management TCGUEEN                
                User exits from user exit management with function module             
                assignment TCGUEFU                                                    
                Language-dependent user exit names from user exit management          
                TCGUENA                                                               
                User exit categories from user exit management TCGUETY                                                                               
    3.  Check Master Data to Be Distributed                                                                               
    For the ALE process, the following master data must be distributed      
             to all the relevant systems:                                                                               
    -   Phrases                                                                               
    -   Phrase sets (for systems, in which data is created)                                                                               
    -   Classes and characteristics                                                                               
    -   Materials (all material data that is required for                   
                 material-specification assignment)                                                                               
    -   Change numbers                                                      
             Note:                                                                               
    Classes and characteristics are distributed via export and          
                 import. The help texts and phrase sets are also transferred to      
                 other systems along with the classes and characteristics.           
                 Classes and characteristics can also be distributed using ALE.      
             Note:                                                                   
             The required data providers must have been created manually in the      
             Product Safety component under Tools -> Edit addresses -> Data          
             provider before data is distributed in the recipient system. The        
             data providers must be unique with regard to the following three        
             fields:                                                                 
             - Name (NAME1)                                                          
             - City  (CITY1)                                                         
             - Country (COUNTRY)                                                     
             During distribution, the data providers of the specification to be      
             sent are read and also distributed. When writing to the recipient       
             system, the SAP System determines the corresponding address number      
             for the data provider in the recipient system by comparing the three    
             fields Name, City and Country for the address numbers that were         
             sent, and then transfers this address number that was determined to     
             the Data provider field (OWNID).                                                                               
    You can determine the address number of the data provider in            
             Customizing for Product Safety in the IMG activity Specify              
             Authorization Groups.                                                   
             To do this, call the input help for the Data prov. field in the IMG     
             activity. You will find the value you require in the Addr. no.          
             field.                                                                  
             The address number is not displayed in address management in the        
             Product Safety component.                                                                               
    4.  Check Control Data to Be Distributed                                    
             See above: "Maintain Settings in the Sending and Recipient Systems"                                                                               
    5.  Check Consistency                                                       
             A consistency check can be performed for the settings in the            
             distribution model and the partner profiles.                            
             To do this, in Distribution (ALE) Customizing, call the IMG activity    
             Check Partner Profiles and Model Settings.                              
             The distribution model must have been distributed and the partner       
             profiles must have been maintained in all relevant systems.                                                                               
    6.  Error Handling                                                          
             As soon as an error occurs when an IDoc is processed, the whole IDoc    
             is not updated. You can use a workflow to correct errors. IDocs can     
             be modified manually (you can change the identifier, for example)       
             and updated retrospectively.                                                                               
    General Procedure                                                                               
    1.  In a customer reference model you define which data is to be                  
             distributed to which system. You use sets of hits to define the               
             specifications that are to be distributed and specify filters with            
             regard to specifications or specification data as required.                                                                               
    2.  The first time you distribute specifications to the target systems,           
             you do it manually, using the method REPLICATE according to the               
             distribution model. Serialization must be switched off.                                                                               
    3.  You activate serialization and switch on delta distribution as                
             follows:                                                                               
    Activating Serialization                                                                               
    a)  In Customizing for Product Safety, in the IMG activity Specify            
                 Environment Parameters specify the channel for the parameter              
                 ALE_SERIAL_ID through which the ALE data is to be distributed.                                                                               
    b)  In Customizing for Distribution (ALE) choose Set Up Data                  
                 Distribution -> Serialized Distribution -> Serialized                     
                 Distribution Using Object Types -> Activate Inbound Object Types          
                 and specify the inbound object types for which serialization is           
                 to be performed.                                                                               
    c)  Schedule a job (RBDAPP01) that posts the IDocs that arrive in             
                 series in the recipient system.                                                                               
    Switching On Delta Distribution                                                                               
    a)  Activating change pointers for a message type                             
                 Changes to master data objects are logged in the form of change           
                 pointers during master data distribution. To activate the                 
                 writing of change pointers, in Customizing for Distribution               
                 (ALE) choose Set Up Data Distribution -> Master Data                      
                 Distribution -> Activating Change Pointers -> Activate Change             
                 Pointers for Message Types and set the Active indicator for the           
                 message type for which you want to realize delta distribution.                                                                               
    b)  Activating change pointers for each field                                 
                 From the SAP R/3 screen, choose Tools -> Business Framework ->            
                 ALE -> Development -> Master data -> Activate change pointer for          
                 each field and enter the message type for which you want to               
                 determine fields, for which the SAP System writes change                  
                 pointers. All relevant data fields are delivered. If necessary,           
                 adjust the table to your requirements.                                                                               
    c)  Activating change pointers generally                                      
                 To generally activate master data distribution using change               
                 pointers, in Customizing for Distribution (ALE), choose Set Up            
                 Data Distribution -> Master Data Distribution -> Activating               
                 Change Pointers -> Activate Change Pointers (generally) and set           
                 the active indicator.                                                                               
    d)  Scheduling delta distribution as a job                                    
                 You can perform delta distribution manually or schedule it as a           
                 job.                                                                               
    To perform delta distribution manually, from the SAP R/3 screen           
                 choose Tools -> Business Framework -> ALE -> Administration ->            
                 Periodic processing -> Process change pointers and enter the              
                 message type you require and choose Execute.                              
                 To schedule delta distribution as a job, in Customizing for               
                 Distribution (ALE) choose Scheduling Periodic Processing ->               
                 Scheduling Generation of IDocs from Change Pointers -> Define                                                                               
    Variants and create a variant. Then in the IMG activity Schedule       
                 Jobs create a job (RBDMIDOC) for the variant. You can set the          
                 time at which distribution is performed, for example,                  
                 immediately after a change or periodically.                                                                               
    The following applies when transferring data:                                                                               
    o   If a specification is not found in the target system, it is created        
             with the specification key that is transferred.                                                                               
    o   If a specification is available in the target system, its data is          
             updated.                                                                               
    o   When complete specification data is being sent, the specification is       
             locked and no changes can be made to it. If this lock cannot be set,       
             the specification cannot be processed. The IDoc is given the status        
             with error and a work item is created.                                                                               
    Note:                                                                               
    In manual distribution, change pointers are not taken into account.        
             In other words, the entire data record is distributed and delta            
             distribution is not performed.                                                                               
    Note on Executing the Report Program RC1PHDEL:                                 
             You must NOT schedule the report program RC1PHDEL (physical deletion       
             of data) to run in the source system or manually run it between            
             initial distribution and delta distribution, because the keys of           
             logically deleted data records can no longer be read and distributed       
             by delta distribution after the report program has been executed.          
             Before initial distribution you can execute the report in the source       
             system.                                                                    
             In the target system you can execute the report program independent        
             of distribution, as long as the target system does not serve as the        
             source system for further distribution.                                    
             If you want to execute the report program after the first delta            
             distribution, you must first make sure that all change pointers            
             created have been fully processed by the delta distribution and, if        
             possible, that all IDocs (intermediate documents) created were also        
             successfully posted in the target system. Otherwise, there is no           
             guarantee that the source and target systems will be consistent.                                                                               
    Example                                                                    
             The report program RC1PHDEL was executed in the source system so           
             that the deletions of an identifier of the identification category         
             NUM and the identification type CAS and a phrase item were not             
             distributed.                                                               
             Then an identifier of the identification category NUM and                  
             identification type CAS with the identical value that was previously       
             deleted and a phrase item for the same phrase in the previously            
             deleted language are created. The following errors occur in the            
             subsequent delta distribution:                                                                               
    -   The identifier cannot be created because the NUM-CAS value             
                 already exists. The IDoc cannot therefore be posted.                   
                 Notes:                                                                               
    If you attempt to create duplicate identifiers in the dialog,          
                 the same error messages will be displayed as when posting using        
                 ALE.                                                                               
    If the NUM-CAS identifier was not identical to the previously          
                 deleted identifier, the IDoc would be posted successfully and          
                 the identifier would be created in addition.                                                                               
    -   The phrase item cannot be created, because only one phrase item        
                 is permitted for a phrase in each language. The old phrase item                                                                               
    must be deleted first before the IDoc can be posted.                                                                               
    The next section describes the solution for similar error cases. You    
             should, however, try to avoid the need for this procedure by not        
             executing the report program.                                                                               
    e)  In the target system in the dialog, delete the EH&S objects         
                 (specifications, phrases, reports), for which you have already      
                 run delta distribution. These objects are internally marked with    
                 a deletion indicator.                                               
                 Caution:                                                            
                 When you distribute reports, the report bodies are distributed.     
                 To delete these, you simply need to delete all report reference     
                 specifications. Deleting report bodies is not necessary and also    
                 not possible. If you cannot delete objects (such as                 
                 specifications or phrases) owing to their where-used-list, it is    
                 sufficient to delete the 'deleted' detail data in the target        
                 system that has not been distributed. This may require more         
                 processing effort than if you delete all the objects using the      
                 hit list and distribute all the data again in full.                                                                               
    f)  In the target system, set the Set missing deletion indicators       
                 and Delete physically indicators in the RC1PHDEL report program     
                 and execute the report program in the target system.                
                 This triggers the following actions:                                
                 - The deletion indicator is set in the tables that depend on the    
                 header data to be deleted.                                          
                 - All data with deletion indicators is deleted physically.          
                 - The corresponding entries in the table ESTALE (conversion         
                 table for ALE) are deleted physically.                                                                               
    g)  Deactivate the active serialization and the writing of change       
                 pointers and start initial distribution of all objects again.                                                                               
    h)  You can now activate the writing of change pointers and             
                 serialization again and use delta distribution as usual.            
             Note:                                                                   
             If you still have IDocs in the source system or target system that      
             were created before the deletion in your target system, but were not    
             distributed or posted, ignore these IDocs and do not post them. You     
             can do this by changing the channel before repeating the initial        
             distribution by using the environment parameter ALE_SERIAL_ID (for      
             more information on the environment parameter, see the IMG activity     
             Set Up Distribution of Specification Data).                             
    Return ->                                                                       
         Application                                                                               
    Hope this helps
    Mark

  • Set Preview as Default Program for .PDF

    Is there any way to set Preview as the default program for opening .pdf? It currently has Adobe setup as the default and I can't find a way to change it. Any help is appreciated.

    Hello, and welcome to the Apple Discussion Forums!
    Select a PDF file (any PDF file). Then do +File > Get Info+ (or Command-i keyboard shortcut).
    In the Get Info window, where it says "Open With", select Preview. Then click +Change All.+

  • Best free image editing program for mac?

    I am teaching myself Wordpress and need to create a logo to upload into a WP template.  Was informed that I need an image editing program.  Which free program would you recommend that does not have a steep learning curve?  (Enough to be learning Wordpress.)
    Thanks!
    A.

    Not free but check out "GraphicConverter" and "Logoist"...

  • I keep getting the same preview image for multiple photos

    In my iPhoto Library and some of my folders the same preview image is showing for many of my images. When I enlarge or export those images or folders the correct image shows. Any ideas what is messing with the preview?
    Thanks.

    Back Up and try rebuild the library: hold down the command and option (or alt) keys while launching iPhoto. Use the resulting dialogue to rebuild.
    Regards
    TD

  • Setting Preview Image for iMovie

    I just created several tutorial videos using iMovie. The videos are embedded in an online course I'm developing. Does anyone know how to set the preview image that appears for the video?
    Right now, the preview image (i.e. the image that appeard under the "play icon" for the video before the video is clicked on) is just a black image. I believe the player that I'm using defaults to the first frame of the video, which is a black screen. Is there a way to change this? Our tech folks said the preview image is a setting within the video, not the player.
    Thanks for your help.

    Have a look at this tutorial: http://web.archive.org/web/20081012122149/http://www.monkeyflash.com/flash/poster_frame_fo r_flash_video/
    If you still have questions, ask again.

  • Aperture 3: low quality preview images

    I don’t know if it's just a problem with my (new) Aperture Trial library or if it's a Aperture 3 bug:
    The preview images Aperture 3 (trial) creates from raw files (in my case NEFs) are different from the JPEGs exported using the same JPEG settings.
    I get the impression that the preview images don’t use all the adjustments applied to the raw files. They don’t have the moire reduction applied. The preview images of high ISO images have color noise, the exported images don’t have that color noise (the moire and noise settings of raw fine tuning are applied to the exported files but not to the image previews).
    As the preview images are used for the Finder media browser, iLife, iPhone/iPod touch picture sync and other things the lower quality is not acceptable for me.
    The preview images of Aperture 2 are identical to the exported JPEGs from Aperture 2 (using the same settings).
    I use Aperture 3 Trial with a new trial library and a few hundred raw images just to test Aperture 3.
    I already erased all preview images and rebuild the previews. I deselected using the embedded JPEGs from the raw files and I let Aperture rebuild the miniatures.

    It seems that Ap2 syncs the previews to the iPhone... you have to clear the previous cached previews before it will load higher quality previews... anyhow, here is what I did... and photos look better on my iphone (not feeling motivated enough to verify if it is the same quality as iphoto sync)...
    1.) change Ap2 prefs for "limit preview size" to "don't limit"...
    2.) select all the photos in the album(s) you are want to sync, right click (ctrl click), and select delete previews...
    3.) sync your iphone again...
    if that doesn't work directly, you might need to uncheck sync photos to delete all photos on the iphone, but the ultimate goal is to ensure refresh with the higher quality previews...
    Hope that makes sense or gets folks in the right direction... Apple really needs to put a check box in future version of itunes to sync full quality or something...

  • Raw images on iPhoto for iOS?

    Any plans for future versions of iPhoto for iOS to handle raw images?

    Ralph9430 wrote:
    Michael, that is correct. iPhoto for iOS is limited to 19 megapixel images and does not edit RAW files. So if one is shooting with something like a 5D MKII which takes 21 megapixel images one needs to shoot RAW plus a smaller than full size jpeg.
    iPhoto for iOS is not a full fledged image editing program for professional photographer. MacWorld correctly, IMHO, points out in a recent review that iPhoto for iOS is for hobbyists and casual usuers. It does real well with preparing 1-3 megapixel images for sharing on social sites but is not recommended to much more than that.
    Thanks for this info, Ralph.  I had a suspicion that iPhoto for the iPad would be somewhat limited, much the same way Pages, Numbers, and Keynote are relative to their Mac counterparts.  Digital photography is a hobby of mine, and I use Aperture to tweak my RAW photos.  Overall, the I've found the iPad is great for showing photos, emailing them, etc., but not ideal for editing or storing.

  • Extracting JPEG preview image from DNG file

    My company is using the DNG SDK to support raw or DNG files for users of our digital asset management software. We extract a jpeg preview/thumbnail from ALL file types we support.
    My question is: how can we extract a jpeg preview from a DNG file, using the latest version of the DNG SDK?
    Currently, our software uses the SDK to read a DNG file and write a tiff file, and passes the tiff to imagemagick to get a resized jpeg we can use for a preview or thumbnail.
    When we extract the tiff from the customer's file, we get a base version of the image that does not show subsequent colour adjustments made in (eg) CS3; the customer would like to get a preview that shows (especially) the colour adjustments that have been made.
    I know the jpeg preview exists inside the DNG, I used exiftools to extract it,and it does show the colour adjustments made.
    How do I get that preview image out of the DNG file using the DNG SDK? Does the DNG SDK support that operation?
    The SDK has a lot of API, but not much documentation or samples to show usage.
    Thanks for any help anyone can provide.

    Maybe it isn't the smartest way, but this should work:<br /><br />... call info.Parse (host, stream) etc here - the usual stuff<br />{<br />     // find biggest jpeg image for preview<br />     unsigned int subMaxW=0;<br />     int subMaxI=-1;<br />     for(unsigned int i=0;i<info.fIFDCount;i++)<br />     {<br />          dng_ifd* pIFD=info.fIFD[i].Get();<br />          if (ccJPEG==pIFD->fCompression && 1==pIFD->fNewSubFileType)<br />          {<br />               if (pIFD->fImageWidth>subMaxW)<br />               {<br />                    subMaxW=pIFD->fImageWidth;<br />                    subMaxI=i;<br />               }<br />          }<br />     }<br />     if (subMaxI>=0) // load desired jpeg preview<br />     {<br />          unsigned int i=subMaxI;<br /><br />          dng_ifd* pIFD=info.fIFD[i].Get();<br />          if (ccJPEG==pIFD->fCompression && 1==pIFD->fNewSubFileType)<br />          {<br />               // seek to pIFD->fTileOffset[0] and load jpeg<br />          }               <br />     }<br />}

  • Preview freezes when trying to open images - other programs have no trouble

    Preview freezes when trying to open images - other programs have no trouble with the same file. This problem is somewhat intermittent.
    I have replaced the Preview application by moving a copy from another equivalent machine - no luck.
    Did not find any preferences file trash, though I looked.
    Is there one?
    Any suggestions?
    Thanks.

    Edwin,
    The .plist for Preview should be located @ ~/Library/Preferences/com.apple.Preview.plist (where "~" is your Home folder).
    Trash the file, logout/login or reboot your computer and try opening the app and opening the offending file again.
    Let us know if any luck with finding the .plist there and opening your file?
    littleshoulders [:-)

  • When previewing images by clicking on the thumbnail in an Event for example, I've been finding that many images preview in a 'zoomed in' way so only a small part of the photos is previewed in a highly magnified view.

    When previewing images by clicking on the thumbnail in an Event for example, I've been finding that many images preview in a 'zoomed in' way so only a small part of the photos is previewed in a highly magnified view.
    Initially I could find no cause. Then I tried right click - Edit and on the affected images, always get this warning:
    "Image Cannot Be Edited - This photo was previously edited with another application or with an early version of Iphoto. Duplicate this photo to edit it." and a "Duplicate To Edit" Button is displayed. 
    The external Editor defined for iPhoto is Adobe Photoshop Elements.
    Now, I reckon the MUST be others out there affected by this same apparent Preview bug, yet my searches have not revealed any answers.  Also seems impossible to find a contact number for adobe???
    Thanks

    Start '''[https://support.mozilla.org/en-US/kb/troubleshoot-firefox-issues-using-safe-mode Firefox in Safe Mode]''' {web Link} by holding down the '''<Shift ''(Mac Options)'' >''' key, and then starting Firefox. Is the problem still there?

  • Ho to find script and the related print program for print preview of PO

    Hi All,
    We are getting some text output on the print preview of a purchase order.
    How can we determine the driver script and the corresponding print program for this.
    Can you please guide on this.
    Thanks in advance.
    Regards,
    Sanjeet

    U Can check Driver program and form related to that program table is TNAPPR
    Goto NACE t.code
    Selct Application ---> click on output types
    then u wil get one window there select proper output type and
    double click on  processing  routines u wil get form name and related driver program name also
    Plz try this....
    Edited by: Upender Verma on Feb 9, 2009 1:33 PM
    Edited by: Upender Verma on Feb 9, 2009 1:37 PM

  • Looking for some advice regarding an image related program

    Hi fellas, Im looking for some guidance here. I want to write a program that will read an image (image will be an xray image of a square), convert the image to black and white, and measure the length and width of the square. Im looking for the best progamming langauge to make this happen. Anyone have any recommendations? I know c++ has a good imaging library that would be helpful so im looking into that at the moment. And Im pretty sure I can do this with matlab, but Im writing this program for a doctor so I need it to be portable. Thanks in advance for all the help
    Cliffnotes:
    Whats the best programming language to:
    -read an image (of a square)
    -convert image to black and white
    -measure length/width of square
    -GUI would be good but not necessary
    -easy to write

    HashBox wrote:You might want to look in to DPI and what The GIMP does in terms of that, also I found this which might be of use as well: http://en.wikipedia.org/wiki/Pixels_per_inch
    Thanks HashBox, I think Im off to a good start on this. First, I wrote the program (majority of it) using matlab, and now Im trying to convert it to C++. So far I have:
    #include <stdio.h>
    #include "CImg.h"
    using namespace cimg_library;
    //main program
    int main()
    CImg<double> img("xray.jpg");
    //converts the image to black and white
    img.RGBtoYCbCr().channel(0).resize(-100,-100,1,3).RGBtoLUT(CImg<>(2,1,1,3).fill(0.0f,255.0f),false);
    //displays image
    CImgDisplay display(img,"Black and White");
    while (!display.is_closed)
    display.wait();
    return 0;
    So right now, I have the black and white xray image. How do I find out the size of the image using c++? Is there a function for that or do I have to write code to find it manually?
    Heres the original matlab code I wrote that Im trying to write my c++ code after:
    %read the image
    [filename,pathname] = uigetfile('*.*', 'Select an image');
    %assign image to film
    film=imread(filename);
    %threshold the image
    level = graythresh(film);
    %convert image to black&white using the thresholded value
    BW = im2bw(film, level);
    %display image
    imshow(BW);
    SIZE=size(BW);
    counter=zeros(1, SIZE(1));
    for x=1:SIZE(1)
    for y=1:SIZE(2)
    if (BW(x,y)==1)
    counter(1,x)=counter(1,x)+1;
    end
    end
    end
    SUM=0;
    lines=0;
    for counterarray=1:SIZE(1)
    if counter(1,counterarray)>0
    lines=lines+1;
    SUM=counter(1,counterarray)+SUM;
    end
    end
    Last edited by wankel (2009-04-24 21:15:46)

  • Need help for writing extract program

    hi
    i need help for writing extract program to retriew data from legacy system.
    i already developed bdc programs for me31k and me21.
    my requirement is to write extract program s for those t.codes.
    to retriew data from legacy system and stored in flat file.

    i need help with a java program. it is a program that allows the user to enter a student's GPA, number of extracurricular activities, and number of service activities. The user can not enter a gpa above 4.0 or below 0. The user can not enter a negative number for the number of both activities. If the student meets the following criteria: 1) GPA of 3.8 or above and at least one extracurricular activity and one service activity, 2) GPA below 3.8 but at least 3.4 and a total of at least three extracurricular and service activities, 3) GPA below 3.4 but at least 3.0 and at least two extracurricular activities and three service activities, the message "Scholarship candidate" should display. If the student does not meet the criteria above, then the message"not a candidate" should display. Can you help me, please?
    You haven't posted ANY 'java program' for us to help with.
    The forum is NOT a coding service. It is to help you with YOUR code.
    Post the code you have written and SHOW us (don't just tell us) how you compile it and execute it and the results you get. Then we can help you with any problems you are are having.
    If you need help understanding just what the program should be doing you need to ask your instructor to clarify the assignment.

Maybe you are looking for