DMXzone Smart Image Processor .tif file issue

I'm using the DMXzone ASPupload & smart image processor.
I'm having an issue creating thumbnails from .tif files. All other
formats work well. I've tried using the the server component that
came with the product, the .net component, and ASPupload component.
None seem to work.
I REALLY NEED HELP!

You are correct. The DMXzone smart image processor will
upload the .tif, then resize it and convert it to a .jpg file. The
.tif file is stored so that you can download it by clicking a link.
The app I've built is an image gallery. JPG thumbnails with
links to hi-res graphic files.
The smart image processor automatically creates the display
thumbnails, except in the case of .tifs. Which the software claims
can process.

Similar Messages

  • Image processor keeping files open in PS CC - not saving

    I am trying to use my watermark action with image processor to "process/batch my high resolution for print files to be for web png" my files all at once [saving as PNG]
    Photoshop is keeping the files open with out saving them.
    my action consists of-
    placing an image
    fit image [makes low res for web]
    set selection
    align
    flatten
    i used this action in my previous version of PS with no issues.
    tried re-making the action- same thing happened.
    Please help
    Thank you!!

    I haven't experienced that problem. But a related annoying problem with batch actions in CS4 is that if I minimize Photoshop while a batch action is running, the program interface minimizes, but the images open and close on the desktop still. In prior versions of PS, I could minimize the program and the batch action would go on in the background, invisible to me, while I could do other tasks. But now, when I run a batch to convert over 1000 files, each one pops open on the desktop, in front of any other open app's windows. It then closes and the next one opens, etc. Which means my computer is unusableduring any batch command.
    Very annoying! How could the QA and beta testers have not noticed this?

  • Image Processor Jpg Files Cause LR to Stop Working

    Photoshop CS3 and Lightroom 1.4.1
    Vista Ultimate 64 / 8 Gig Ram / Lots of Hard Drive space on Scratch Drive
    nVidia 8800 GTS w/640 MB Ram
    Image files processed in Photoshop
    Exported via: File > Scripts > Image Processor (IP)
    IP settings are default except the jpg output is set to 12/max
    From the same PSD file, no modifications in PS
    One file will cause LR to crash ("A problem caused the program to stop working correctly) the next does not.
    Both jpg files open and display without a problem in...
    - Photoshop
    - Adobe Camera Raw
    - Microsoft Office Picture Viewer
    - Apple Quicktime Picture Viewer
    - Windows Explorer (thumbnails)
    I have saved two otherwise identical files, one crashes LR every time, the other opens in LR fine, every time.
    This has been occurring in about 3 out of every 100 files saved via IP.
    The next time LR is opened it crashes again if the 'bad' file is not renamed or deleted due to the automatic file updating process.
    Trying to import 100 files requires importing them one at a time when this happens because there is nothing to indicate which file cause LR to break during the batch import.
    If Adobe Tech Support would like the two 'identical' files they can email me and I'll send them along.

    *push*

  • Image Processor Pro xml issue:

    When I download the script Image Processor Pro.xml to my window 7 computer with CS6,  the File Type reads "Safari Document"  When I select my images in bridge and try to run IPP the only thing that happens is a blank white window opens and sometime PS will crash.
    I just upgraded from XP with CS5 to Win7 with CS6.  I had no problems running IPP in XP/CS5

    Thank you very much, xbytor2. 

  • Batch Action through Image Processor Leaves Files Open in CS4

    I am not sure if this is a change in CS4 or something that I am doing incorrectly. But when I run Bridge CS4 < Photoshop < Image Processor (running an action that I have been running since CS2) the files do not close in photoshop after running the action. In all prior versions of PSCS#, photoshop closed the file after finishing the action. The files all save properly. But having hundreds of files opened inside of photoshop causes the scratch disk to go low and slows everything down.
    What am I doing wrong?

    I haven't experienced that problem. But a related annoying problem with batch actions in CS4 is that if I minimize Photoshop while a batch action is running, the program interface minimizes, but the images open and close on the desktop still. In prior versions of PS, I could minimize the program and the batch action would go on in the background, invisible to me, while I could do other tasks. But now, when I run a batch to convert over 1000 files, each one pops open on the desktop, in front of any other open app's windows. It then closes and the next one opens, etc. Which means my computer is unusableduring any batch command.
    Very annoying! How could the QA and beta testers have not noticed this?

  • Bridge Image Processor always creates JPEG or TIFF folder, how do I change that behavior?

    I have searched the web, Bridge forums, and Photoshop forums, and come up empty-handed. (The strange thing is, I know there used to be a post that answered this question a few years ago.) Anyway, I use Image Processor quite a bit, and it works great except for the annoying behavior of always creating a new folder to store the newly-created images.
    I remember the solution is to change some line in a (XML?) file from "JPEG" to "". For the life of me, I can't find which file that is! I think it used to located down inside Application Support. I think.
    Thanks for help on this, it's driving me crazy!
    Jeff

    Thanks for replying! I'm running CS 5.1. Oh, now I see...I've never run Image Processor from within Photoshop, just from Bridge. You're right, it does offer different options than Bridge.
    Anyway, I found it what I was looking for.
    Open up (don't run!) the Image Processor.jsx file. I opened it up in ExtendScript Toolkit. The path is /Applications/Adobe Photoshop CS5.1/Presets/Scripts/Image Processor.jsx
    I'm on line 1574 (in other versions, the line number may vary)
    This is what the line says:
    var subFolderText = inFolderLocation + "/JPEG/";
    Change to:
    var subFolderText = inFolderLocation + "//";
    Problem solved. Repeat as necessary for other folders you don't want created (TIFF, PSD)
    Back to work!

  • Buglet in Image Processor.jsx

    I'm not sure how to report this, but there's a bug in the Image Processor script that was driving me nuts so I figured out how to patch it. This may be a Windows-only bug (I'm not sure).
    The problem is that the when you bring up either of the directory pickers for changing the directories in the Image Processor dialog, they both default to the Windows desktop rather than the path that the dialog shows. Since the Windows desktop is a long ways away from where I keep my images, tihs is a lot of mouse clicks to set this directory everytime I want to use it. There is an attempt to pass the directory picker a starting directory, but that code is just wrong. This occurs in two places in the Image Processor. To fix it, I replace this line:
    var selFolder = Folder.selectDialog( strPickDest, this.parent.parent.destLongText );
    with this line:
    var selFolder = Folder.selectDialog( strPickDest, d.destLongText);
    and now the directory picker starts out where it's supposed to and it's a lot quicker to set it to what I want.
    If this has been bugging you, you can patch your own Image Processor.jsx file. Just find the two lines that look like the first line and replace them with the second line.
    And Robert, do you have any idea how to get the real one fixed at Adobe?
    I wonder if this actually works on the Mac. On windows, it takes a chain of 5 parents up (this.parent.parent.parent.parent.parent.destLongText) to make the original way work, but I could imagine that this would be difference on Windows/Mac. Since the real parent has already been resolved with FindWindow right in this same function, I found a safer way to accomplish the goal.
    --John

    >>>I'm not sure how to report this, but there's a bug in the Image Processor script that was driving me nuts so I figured out how to patch it. This may be a Windows-only bug (I'm not sure).
    var selFolder = Folder.selectDialog( strPickDest, this.parent.parent.destLongText );
    with this line:
    var selFolder = Folder.selectDialog( strPickDest, d.destLongText); <<<<br />
    John I did your bugfix, but it did not work in my CS2. I'm still taken to the Desktop. Have you done any further work on this "bug"?
    Thanks,
    Dennis Jacobsen

  • Wish Image Processor always came up.

    Not most innovative request, but gotta let you know. Lot of times I select the image processor (from within Bridge) and it just does not come up. So far----thankfully, it comes up after a quit and relaunch. But hoping not have to do that down the road. appreciate it.

    Thanks for replying! I'm running CS 5.1. Oh, now I see...I've never run Image Processor from within Photoshop, just from Bridge. You're right, it does offer different options than Bridge.
    Anyway, I found it what I was looking for.
    Open up (don't run!) the Image Processor.jsx file. I opened it up in ExtendScript Toolkit. The path is /Applications/Adobe Photoshop CS5.1/Presets/Scripts/Image Processor.jsx
    I'm on line 1574 (in other versions, the line number may vary)
    This is what the line says:
    var subFolderText = inFolderLocation + "/JPEG/";
    Change to:
    var subFolderText = inFolderLocation + "//";
    Problem solved. Repeat as necessary for other folders you don't want created (TIFF, PSD)
    Back to work!

  • Help needed to enhance Image Processor Pro Script to save transparency in TIF

    Hi everyone,
    this is my first post in this community.
    We have a droplet which reduces the resolution of tif images to 72dpi and save the tif image with transparency. This works fine, but it took to long for the whole process of many picture in different folders. That's the reason why we searched for another script which can preserve the folder structure and set the resolution of every tif image to 72dpi.
    We found Image Processor Pro, which does exactly what we needed. The script works perfectly in CS5 and CS5.5 as it saves the tif with the transparency. Those saved tif images could be used in InDesign with the transparency.
    BUT Image Processor Pro script works not so perfectly in CS6 as it seems that this option to save a tif with transparency is not implemented or does not work in the script. The result is that those converted tif images are w/o transparency in InDesign. That's a huge problem for us.
    This is the point where I need your help. Neither I have experience yet with jsx-files nor with the right syntax of it.
    Is there a way for anybody of you to implement / enhance Image Processor Pro so it will save tif with transparency?
    We used the latest German Version of Image Processor Pro: 2.3.1 (link: http://www.russellbrown.com/scripts.html)
    (The German version contains only german on screen texts!)
    I am very thankful for every help you can give.
    Thanks in advance for your help.

    Possible causes:
    1) It probably has nothing to do with your image files, but you won't know until someone else tests one of them. You could create a small 50% gray TIFF file with transparency and post it, assuming you know it exhibits the issue with IPP.
    2) At the download link you provided:
    http://www.russellbrown.com/scripts.html
    There are two installers for Image Processor (CS5 and CS6). Did you download and install the CS6 Version Installer?
    3) Another possible solution other than modifying the script is to reset the PS Preferences file. When strange things happen in PS with no explanation this usually fixes them. My PS CS6 was inflating  all new files by 1.4MB. After examining one of the files it turned out PS was inserting a Costco printer profile into every new file. So don't automatically assume your PS image files are not somehow being corrupted and causing loss of transparency in IPP. Creating a new Preferences file resolved my issue:
    http://forums.adobe.com/thread/375776
    You may want to record your old Preferences settings prior to creating a new one, but test it first with the default settings.

  • Connectivity issues - Bridge CC to Photoshop CC - Image Processor issues.

    Hi guys.
    I'm having issues with Image Processor between Bridge CC and Photoshop CC. I can see in the forums that others are having issues that are close to mine but not the same. I can still see my image processor tab in my Tools menu.
    The problem is that I can click the Image Processor tab and it will bring Photoshop CC to the front of all windows, act like its loading, and then nothing happens from there. The run script box doesn't come up, nothing opens.
    I was wondering if anyone else has come across this and if so how you fixed it.
    Thank you

    I'm having the same result when I run image processor from Bridge. Image processor looks like it's about to open, the wait cursor displays (Photoshop CC will open if it's closed), but then when focus switches to Photoshop, nothing happens.
    A few months ago when I tried to upgrade to PS CC 2014 I had the same problem, which was only fixed when I removed all Adobe apps and re-installed CC and Bridge with no PS CC 2014. This might fix your problem if you re-install and only use a single version.
    Currently I have both versions of Photoshop installed again as I need the linked smart object functionality of 2014 but I also need my library of extensions in Photoshop CC. (Really frustrating switch to HTML5 only, by the way Adobe)
    Does anyone know if there is any way to have both versions of Photoshop installed AND have scripts fire off from Bridge?

  • Date of creation problem after making Bridge create TIFs with PS Image Processor.

    I went through about 100 files and did what I wanted in Camera RAW (started out with NEFs). Thereafter I had Bridge make TIFs of all the files in the folder using the PS Image Processor.
    Now, looking at the TIF folder in Bridge, I find that about 80 of them has a wrong creation date (I checked the Preferences and I have asked for the date of creation - and not the date of modification). As I watch (several minutes) Bridge changes some of the dates to the ones known to me to be correct - but not all. If I close Bridge, restart Bridge and open the folder again the same happens, i.e. it starts all over. Even stranger is that the Windows Pathfinder have problems with the same files - i.e. does not show the date of creation at all.
    The date of these 80 files are all the same - and they have been edited over several days!
    I have done a lot of work on those files and would hate to start all over. I checked and of course the dates are the original in the RAW folder that I started out with.
    I am sure that I do not have any bugs in my PC.
    Can I remedy this i any way? I hate to have wrong dates on my files.
    What can I have done to cause this? Can anyone help me? Thanking You in advance.
    Git

    Thank You again.
    Yes, I have also purged the cache. More than once and again this morning. It does not change the result. Bridge still goes from the date January 13th 2013 to the correct date of creation when I look at the separate thumbnails - and back again when I scroll down the page and subsequently scroll up again!
    Thus it seems that Bridge knows the date that the camera set but somehow this foolish January date keeps coming back.
    All the folders with NEFs have correct dates - also the ones where I have imported the files from camera to pc in 2013! Only my TIFFs have this problem.
    Rigth now I am having Norton 360 run a complete system scan. When that is done I will inactivate Norton (I know that I cannot have 2 antivirus softwares and firewalls run simultaneously on the PC) and instead run a complete scan with Lavasoft Adaware Pro. I have also used Norton Utilities and found no problems. Plus Malwarebytes Antimalware and Superantispyware. No problems.
    If "date file created" is the date that the file was modified, it would not help me much. I often go back to a file and play with it again and if I have understood correctly, then this date would change again. I want to see the date of capture ("date created"). Also, by now the problem afflicts at least 1000 files. It would be impossible to do single file manual corrections of dates on so many files.
    Update: While I have been writing this, an opened folder with only 36 files has changed the dates to the correct date of capture. I could also scroll up and down without the dates changíng in this small folder. But when I closed Bridge, restarted it and looked at the folder again Bridge again did need minutes to get all the dates rigth. Maybe I have a pc capacity problem instead of a software problem? But why on earth would this specific wrong date result from a too weak pc.?
    Maybe I should just give up and reinstall PS?
    Sorry if I trouble You with a ridiculous problem.
    Git

  • Image processor: "No source files could be opened by Photoshop."

    I am also getting a "There were no source files that could be opened by Photoshop" warning when trying to save jpegs of open images (opened from a PDF) using the image processor.
    Here is what I'm doing:
    1. Open multiple pages of a PDF into Photoshop
    2. Run the Image Processor with settings:
    - Use open images
    - Save to "select folder location" (choose a valid location)
    - Save as jpegs
    3. Run
    And it gives me the warning. How can the files not be opened by Photoshop. They already are?!?

    JJ, thanks for the response, and my guess is you are correct. It would be nice if Adobe would change this. My whole intention of using the Image Processor in this case was to "batch save" all the open files. As far as I know, there isn't another way to do that without creating an action or other such nonsense. ; )
    At any rate, thanks for your input and explanation. At this point, I suppose the issue is as good as solved.

  • Wrong image resolution for TIF file

    Under OSX 10.6.2, the image resolution using Preview application is wrong for FAX MultiPages TIFF files.
    If I open up a file with this resolution:
    Image size: 1728 x 1081 pixels
    Image DPI: 204 x 98 pixels/inch
    Color Model: Gray.
    The image always show up all squeezed vertically which tells me the Preview application is not processing the DPI properly. When using the size menu from tools, it assumes the resolution is the same for vertical and horizontal which is wrong.
    I'm unable to use the Preview application to read FAX TIFF files with the standard FAX resolution.
    How do I open up a trouble ticket with Apple developers to fix this issue? I believe it's a software design issue assuming that all TIFF files use the same resolution for both horizontal and vertical DPI. The Preview application should be able to handle different DPI for horizontal and vertical resolution.
    We're a small business and we are running the whole office with Mac Minis and iMac with a Mac Mini Server of course. We love it, but we have this annoying bug which I don't have any way to fix it.
    Thank you,
    Stephan Monette
    Unlimitel Inc.

    Here's a sample of the tif file from our fax machine you can download:
    http://www.hmnet.net/warp2/fax-standard.tif
    Download the file on your desktop and try opening it. You will see the square at the bottom will look like a rectangle. With the right resolution, it should look like a square, not a rectangle.
    If I open the file with Windows picture and fax viewer, the resolution is fine and the square looks like a square. But the same file on Windows with Quicktime fails to open and it complains about a corrupted file.
    On my MAC, the file opens with Preview, but the resolution is wrong.
    Maybe the FAX server is not formatting the TIFF file properly, but we can't fix that since there's no more support for it. But the Windows app is able to open it up with the right resolution. So maybe it's just some code change to do in the Preview app.
    Thanks,
    Stephan Monette
    Unlimitel Inc.

  • Thumbnails for TIF files are not latest image-CS3

    When I save a (flattened) image in TIF, I get only a partial thumbnail--often a previous layer or selection or something from the clipboard. This is in CS3 (on XP) but also used to happen in PS7.

    Since you mentioned XP I am assuming your issue is Windows Explorer.
    Right click on the file and select refresh thumbnail. I am thinking this is a database issue and is not updating. If that does not do it, then delete thumbs.db.
    If both of those don't work, then I would assume trashing the preference file for photoshop would be next.
    Thats about all I can think of for now.

  • Image processor [in Script menu] not recognizing PSD files?

    I've been using PS since CS.  I still keep a copy of CS2 on a computer simply for the Script -> Image Processor.  Since CS5, the processor no longer recognizes many files.  These same files will batch process with no problem in CS2.  Anybody figure out why the processor has recognition issues?  Thanks for any help.

    File names are visible using the "select folder" button, directing the script to locate the files to be batched.  When selecting the folder, you will see the files within the folder in the adjacent tab [windows or mac].  CS5 put a limit of 8 [if I remember correctly] characters on the processing script.  Additionally, some symbols which are permissible in other file naming protocols, no longer worked. 
    The experience is wide spread among heavy users of this batch tool.  I have seen many "google" searches on the subject...which is how I identified the naming issue in CS5.  The issue exists with JPG and PSD files; Adobe RGG and, sRGB; each processed from RAW or other JPG/PSD files.  I simply cannot determine why one set of files work, and  another will not, yet all will work on older versions of PS.
    Once again, these same files causing issue, will process without issue on a CS2 version I keep for just such occurrences.  I've been using the batch image processor since CS to apply actions to folders of files.

Maybe you are looking for