Adobe DNG Converter - command-line parameters for new 1.4 features

Adobe DNG Converter - I need to know what the command-line parameters are for the new DNG-1.4 options (e.g. lossy compression).
Last I checked, there was no updated documentation released - would somebody please help?
Rob

By inspecting strings in the exe file using ProcessExplorer (MS SysInternals), I found these command-line switches for controlling lossy compression:
-lossy
-size
-count
A D O B E
Adobe: please take a moment and update the command-line documentation - thanks.
http://wwwimages.adobe.com/www.adobe.com/content/dam/Adobe/en/products/photoshop/pdfs/dng_ commandline.pdf
or, if there is another that is updated - do tell...
Rob

Similar Messages

  • Command line parameters for automator?

    I'm trying to setup a cron job to so that every morning at 8 am "New Mail.workflow" will open and run. I'm able to get it to open but I was wondering if there were command line parameters for Automator that could open AND run a workflow file? Ideally I'd like it to close after running, but I'll worry about that later. Thanks in advance.

    The preferred way is to save your workflow as an application and then call usr/bin/open on it. If for some reason you must have the workflow run inside of Automator (not self-contained) then you're looking at some quality time with man osascript. As it happens Apple has removed even the need for Cron for most users. A click to File -> Save As Plug-In -> for iCal handles it from start to finish.
    Edit: I forgot to mention that Automator has its own simple command line utility for running *.workflow files. Check out man automator

  • Command line parameters for al_engine.exe

    If you go to a command line window on a DS server and type al_engine.exe with no parameters it prints "Usage" information.  Some of the parameters it mentions are known to the community (like -XX, -XI, etc).  However there are some which sound pretty interesting, but I can't find any information or examples how it should be used.  Examples:
    -L<list of value> : List of Object Labels from UI (separated by , or ; or space) to filter.
    -Je<XML file> Execute the Installation scenario defined in XML file.
    -jd"datastore delta file in quotes>" : Modify datastore values using "file"
    -Jf, -Ja, -We,  and many more.
    I am particularily interested in -Je functiohnality - it sounds like it can be used to automate deployment.  I am using import/export options to do some automation, but real automation would include deletion of some objects, adding jobs to projects, etc.
    Can anybody help with the documentation/examples?

    The preferred way is to save your workflow as an application and then call usr/bin/open on it. If for some reason you must have the workflow run inside of Automator (not self-contained) then you're looking at some quality time with man osascript. As it happens Apple has removed even the need for Cron for most users. A click to File -> Save As Plug-In -> for iCal handles it from start to finish.
    Edit: I forgot to mention that Automator has its own simple command line utility for running *.workflow files. Check out man automator

  • Command line parameters for OMBPlus?

    Hi,
    Is it possible to pass command line parameters to TCL scripts running in OMBPlus.sh, and if so, can someone provide an example?
    I'm able to use the argv0 variable to get the script name itself but not sure how to get any other additional parms...
    Thanks,
    Jim

    Jim,
    If you are building command-line scripts to automate OMB+ commands, there is another factor you should be aware of. If your script errors out cleanly, the OMBPlus.sh does NOT pass this back to the shell. The return code is evaluated within OMBPlus as the return from a "source" command and then OMBPlus exits normally.
    For example:
    #file test.tcl
    return -code error
    Unix/shell> OMBPlus.sh test.tcl
    Unix/shell> echo $?
    0What I do to pass an error state back to the shell is to create a flag file in my script if exiting due to error. My shell script deletes this file prior to running the script and then tests for it after the run as part of the conditional logic
    Function in tcl file:
    #Get location where this script installed
    #This variable is set at the top of the script.
    set theScriptDir  [ file dirname [info script]]
    #If we want to bail in the script at any point we call exit_failure with an appropriate error message
    proc exit_failure { msg } {
       global theScriptDir 
       set ERRFLAGFILE "$theScriptDir/ers_owb_import.error"
    #rollback any uncommitted work
       OMBROLLBACK
    #Log the error and exit
       set fout [open "$ERRFLAGFILE" a+]     
       puts $fout "Error:-> $msg"
       close $fout
       # return and also bail from calling function
       return -code error
    }And my shell script does something like:
    cd ${JOB_DIR}
    rm -f ers_owb_import.error 2>/dev/null
    echo \\nBegining Uninstall of OWB Project
    ./OMBPlus.sh ${JOB_DIR}/my_tcl_Script.tcl
    if [ -f ${JOB_DIR}/ers_owb_import.error ] ; then
          echo \\nERROR - SCRIPT FAILED
    else
         echo \\nScript Succeeded.
         # script logic continues....
    fiCheers,
    Mike

  • Command Line Parameters for spotify.exe? (Windows 7)

    I've been trying to use Windows Speech Recognition to open music. The problem is, the WSR Macros only open the executable then ask you if you want to run the program with command-line parameters. What I want to do is say the album or the artist then have Spotify open and play that artist/album; I can't do that until I figure out how to open spotify with parameters, if there are even any. Thanks for your help. (I also know how Spotify has had multiple suggestions for this to be integrated in the application itself, but I'm trying to just use Windows Speech Recog)

    Hi,
    I found the Script at the Task schedulder /libary/ Microsoft/defrag
    There was some discussion of this topic here:
    https://social.technet.microsoft.com/Forums/windows/en-US/7fc46461-daf5-4004-b1a7-ca645e370ee5/defrag-on-ssd-the-volume-system-reserved-was-not-optimized-because-an-error-was-encountered-the?forum=w8itprogeneral
    Don
    (Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
    This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

  • Command Line Parameters for Run Application.vi in the LVWUtil

    I am trying to use the "Run Application.vi" located in the LVWUtil.llb.  I am sending a command line similiar to this:
    "C:\WINXP\system32\msiexec.exe" /i "C:\qc data\ZVMS Program Updates\Application Installer\install.msi"
    this command line works from the Start>Run dialog but the Run Application.vi only sees the beginning of the line "C:\WINXP\system32\msiexec.exe" so it opens the windows installler but does not go to the install.msi file and run it.  Does anyone know the correct command line formats for the Run Application.vi to run the entire command line?
    Thanks,
    BethV

    Hello BethV,
    I downloaded the LVWUtil32.zip file from the Windows API Function Utilities (32-bit) for LabVIEW example program.  In that zip file, is a library entitled Winevent.lib, which includes the Run Application.vi.  When you used this VI, I believe the string you passed in as a input had too many quotation marks.  Namely, you do not need quotes around the msiexec.exe call.  I passed the following string into the Run Application.vi and got the expected results:
    C:\WINDOWS\system32\msiexec.exe /i "C:\mymsi.msi"
    Please let me know if it helps.
    Message Edited by Wendy L on 10-21-2005 02:34 PM
    Wendy L
    LabWindows/CVI Developer Newsletter - ni.com/cvinews
    Attachments:
    RunApplication.GIF ‏2 KB

  • Command Line Parameters for Silent Install with Status for BI4.0 Products

    For the XI3.1 product installations, which clearly leveraged MSIEXEC installation files, it was possible to use the /qb+ command line parameter to trigger a silent install which showed the progress of the installation with a final prompt to acknowledge the completion of the installation.
    For the new BI4.0 installation package, it's not clear how to trigger a silent installation which also shows the installation progress.  The installation guide describes using -q in the command line to run a silent installation, or leveraging a response.ini file to trigger a silent install, but in neither case does it show how to modify the silent installation command to enable a display of the installation progress.
    Does anyone know the syntax, either command line or embedded in a response.ini file, to trigger a silent installation for the BI4.0 products which ALSO shows the progress of the installations?
    Thanks,
    Josh

    Yes, I've tried the same switch that I used for the XI3.1 installations, namely "/qb".  In XI3.1 I was able to use this switch either directly in the MSIEXEC command line or in the Response.ini file as "QUIET=/qb".  In either case, this switch resulted in a silent install that showed a progress bar window for the installation, completing with a confirmation prompt indicating that the installation had completed.
    Neither approach works with the BI4.0 installation packages.  My suspicion is that SAP has switched to a different installation engine as I can't find the typical .msi installation files that would indicate this is a MSIEXEC installation.  I'm hoping someone knows what type of installation engine is being used and what the switching syntax is for silent installs. But it can't be a completely transparent silent install (I know how to do this); it must provide an option to show an installation progress bar.
    Thanks,
    Josh

  • New Command-Line Parameters for defrag.exe?

    Hi,
    what means the Dollar sign
    at Task-Scheduler, under Scheduler/Library/Microsoft/defrag/ 
    %windir%\system32\defrag.exe -c -h -o -$
    Is it a new parameter? Which function has it?
    Thanks in advance.

    Hi,
    I found the Script at the Task schedulder /libary/ Microsoft/defrag
    There was some discussion of this topic here:
    https://social.technet.microsoft.com/Forums/windows/en-US/7fc46461-daf5-4004-b1a7-ca645e370ee5/defrag-on-ssd-the-volume-system-reserved-was-not-optimized-because-an-error-was-encountered-the?forum=w8itprogeneral
    Don
    (Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
    This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

  • Bug in Adobe DNG Converter 7.2 RC

    Adobe DNG Converter 7.2 RC (for Windows) keeps missing files. When pointing it at a folder containing many raw image files to convert (and providing a different folder as the destination for the converted files) then it won't always find all the raw files. There are no files besides the raw image files in the folder ... umm, with the possible exception of the hidden Bridge cache files, .BridgeCache and .BridgeCacheT. The destination folder initially is empty.
    When this happens then I have to re-do the conversion, with the same source and destination folders selected and the Skip source file if destination file exists check-box ticked. Then DNG Converter will collect and convert the raw image files it missed in the first run. So far, I never had to perform a third run, but I frequently have to do two runs to get a folder's raw files converted. For example, in my most recent attempt there where 966 raw image files in the source folder (of the type Sony ARW, along with XMP sidecar files), and DNG Converter found 954 files in the first run and the remaining 12 in the second. The bug also occurs when the folder contains mixed types (Sony ARW and Leica DNG in my case). There is no error message or any other kind of hint that something is going wrong, so you have to check the result manually. The status line at the top of the Conversion Status window teling the number of files to convert will report the number found; if that's less than the number of raw image files available then you'll have to start a second run when the first is finished. It's easy to miss the problem, and then you may end up with some files not converted!
    So far, the bug inevitably occurs when there are many raw image files in the source folder—i. e. more than 400 (and up to 1,200). When doing several attempts on the same source folder then the set of missed files will vary, i. e. it's not always the same files that get missed. It is not even always the same number; the number of missing files varies between, say, 5 and 20, i. e. approx. 0.5 - 5 % of the number of files in the folder. It seems that if the number of raw image files in the source folder is small (say, less than 300) then the bug does not happen. In my last successful attempt, I converted 263 files of type Leica DNG, and DNG Converter found them all on the first attempt.

    ssprengel wrote:
    Does it matter what hard-drives the files are on, whether they are missed?
    No, it doesn't. There are two physical SATA hard-disk drives installed in my machine, and the error occurs no matter where the source files are. It also does not matter where the destination folder is. Usually it's on an external 3.5" drive connected via USB 2.0, but I also tried the internal drives, to no avail.
    ssprengel wrote:
    Does an older DNG Converter also miss files?
    Gosh! To my surprise, yes it does! I just tried DNG Converter 7.1, 6.7, and 6.6, and they miss files just like 7.2 RC does. They didn't back when they were current ... or at least, I never noticed.
    This seems to indicate that the culprit is not DNG Converter 7.2 RC but my machine. But then, my machine and the hard-disk drives (including the external 2 TB 3.5" USB drive) are the very same I am using for years now. I didn't change the operating system; it still is Windows XP SP3. I am also still using the same cameras as I always did for years now. The only significant things that changed recently (besides DNG Converter) are Photoshop 13.0.1 and Bridge 5.0.1.

  • Is there any Compatibility issues between Yosemite 10.10.2 and Adobe Elements 12 editor 12.0 or adobe DNG converter 8.1 ?

    Is there any Compatibility issues between Yosemite 10.10.2 and Adobe Elements 12 editor 12.0 or adobe DNG converter 8.1

    A Reminder for Mac Folks upgrading to Yosemite | Barbara's Sort-of-Tech Blog

  • Adobe DNG Converter

    Need advice on which Adobe DNG converter to use with my new Nikon Coolpix P7800. I'm a MAC user with Lightroom 4. I found the camera listed on 8.3, but it is a Window format. Help much appreciated. PS. I tried Adobe DNG 8.4 but my raw photos wouldn't load.

    Always use the latest version of the DNG converter that will run in your OS.
    As SS says, the DNG works on folders only, not on individuals files.  THe files are not supposed to "load".  They will remain untouched and the DNG Converter will generate raw DNG files (copies) from each and every raw file.
    You can then open the DNG files with any relatively recent version of ARC.

  • How can I get the updates for Photoshop CS5 to download to my new Macbook Pro where I have already installed CS5 from my original disk? I have tried many times over 2 days. I was able to successfully download the current version of Adobe DNG converter.

    How can I get updates for Photoshop CS5 to download to my new Mac book pro where CS5 is already installed from my original disk? I have tried many times over 2 days. I get the same error messages re downloading error. I successfully downloaded the current version of Adobe DNG Converter & it installed perfectly. Help please!

    The Adobe auto updater is highly unreliable.
    You need to look for and download the update yourself and then manually apply it as per the detailed instructions on the download page:
    Adobe - Photoshop : For Macintosh
    ~~~~~~~~~~~~~~~~~~~~~~
    Please note that the Adobe Camera Raw plug-in must be updated separately, after you have updated Photoshop:
    Adobe - Adobe Camera Raw and DNG Converter : For Macintosh

  • What is  Adobe DNG Converter for?

    Could someone kindly explain to a novice the purpose of Adobe DNG Converter. I'm shooting Raw images on a Nikon D80 (only) and opening them using PE4.0.1 (Mac) and ACR4.1. Am I right in thinking Adobe DNG Converter is of no relevance in this setup?

    Hi, Anthony. For right now, the main purpose of the DNG converter is to save your camera's raw files in a format that will hopefully be more standard and preserved for longer against the day when raw formats and cameras have moved on and your particular camer model is no longer supported.
    It can also be used to for cameras that are too recent for certain applications to have support for their raw formats. Make a DNG and sometimes you can work with your files in a program that doesn't support them.
    EDIT A fair number of people with newer models were doing the latter for aperture till the last OS X update.

  • I just purchased the new Canon SX60 camera. Despite downloading and installing the latest version of Adobe DNG converter, I receive an error message saying that Photoshop CS4 can't open up/convert raw files (.CR2). This is the same file format as used by

    I just purchased the new Canon SX60 camera. Despite downloading and installing the latest version of Adobe DNG converter, I receive an error message saying that Photoshop CS4 can't open up/convert raw files (.CR2). This is the same file format as used by the SX50, with which I never had any problem. Does anyone have a suggestion on how to fix this problem? Thanks.

    Camera Raw plug-in | Supported cameras  I do not see that SX60 as supported. Just how new is the SX60 when was it announces. Its support is not even listed in ACR 8.7 RC

  • Adobe DNG Converter For Panasonic LX3?

    The recent Apple update still does not recognize Panasonic's LX3 camera. I believed I could still get a Raw image into Aperture by doing the following:
    Using Adobe DNG Converter, and looking at Aperture's requirement that the linear compression option be turned off. I converted the Raw format file to DNG and then tried to import it into Aperture. Aperture seems to "digest" the image, but then states the format is unsupported. Am I doing something wrong? Why doesn't this seem to work?

    I think the problem is, for the LX3, Adobe demands that Linear conversion be on for the LX3. Given Aperture doesn't support this... I think you may be at loggerheads.

Maybe you are looking for