TIFF files and OCR

I previously setup Sharepoint 2013 on Windows Server 2008 R2. In this scenario the TIFF files appeared to be indexed by default and the parser did an OCR on the files (which was very slow).
I have since built a new Sharepoint 2013 farm on Windows Server 2012 and, after some research, it appears the TIFF OCR engine doesn't exist under Windows Server 2012 and TIF files are not indexed by default. As such, I expect OCR of TIFF files under Sharepoint
2013 will no longer work.
Is this correct?
BTW: This isn't bad, it is actually perferred behaviour. However, I just need to confirm the behaviour.

http://technet.microsoft.com/en-us/library/dd744701%28v=ws.10%29.aspx
Forcing optical character recognition of every page of a TIFF image document
This setting bypasses Windows TIFF IFilter performance optimization mechanisms that are designed to skip the OCR processing for images that do not contain text.
To force OCR of every page of a TIFF image document
Open the Local Group Policy Editor as follows: Click Start, type
gpedit.msc in the Start Search text box, and then press ENTER.
Under Computer Configuration, expand Administrative Templates.
Expand Windows Components, expand Search, and then click
OCR.
Double-click Force TIFF IFilter to OCR every page in a TIFF document.
Click Enable, and then select one or more languages.
Click OK.
http://technet.microsoft.com/en-us/library/dd755985%28v=ws.10%29.aspx
If this helped you resolve your issue, please mark it Answered

Similar Messages

I try to save a pdf as a tiff file and get the message the image is to wide to output?

I am trying to save a map I have in PDF format as a Tiff file. When I "save as other - image -tiff I get the message:

If it is a map, you likely already have a bit map. In that case use Export all Images to get the original bitmap back.

Combine Files and OCR

My team here has various files that we combine to make a report which we will then process and disclose. We need the files to be either OCR'ed or optimized to do our job effectively. Some of those files have renderable text and others do not (they are scans). Is there an option where we can combine while also OCRing the scanned docs?

We combine our reports and have the user OCR it before they begin their process. We combine both types of files, renderable and non-renderable, and then the user OCRs the mix. The process will skip the pages that don't need OCRing so I'm not sure where you are getting the idea that you can't.

How do I get PSE 12 to save a TIFF file with file extension ".tiff" instead of ".tif"?

I am using PSE 12 as an external editor for Aperture. When I ask to use an external photo editor, Aperture creates a .tiff file in my Aperture folder, launches PSE 12 and tells it to edit that .tiff file. This all works great. When I am done editing in PSE 12, I ask it to save the file and it saves it back to the original Aperture folder with a .tif extension. I can instead say "save as" and then it suggests the file name with a .tif extension. When I correct the extension to .tiff it warns me that I'm going to overwrite the file (exactly what I want!). I say yes and then I find out that PSE did not overwrite the file, but wrote it as a .tif file anyway. I have to go to the folder, delete the .tiff file and rename the .tif file to .tiff and then everything is fine - but what a hassle. Has anyone solved this problem?

That's not quite where the problem lies, which is good, because you can't change that. The real solution is that you don't ever want to see the save as window in PSE if you are using PSE as external editor for any program. When you see it you aren't creating a version for your asset management program. Go to the PSE preferences>saving files>on first save and choose to save over existing file. That should do what you want.

(CS4) Why is Premiere CS4 modifying TIFF files in a sequence?

Hello,
decided to post here, because I didn't find any old postings of this subject anywhere.
I'm composing 2-d drawn animation on AE and editing in Premiere, then importing to
Avid media composer for exporting to Sony Digital Beta tape via SDI. When working in
CS3 and earlier, everything was nice, AE made about 1730 kB TIFF files and Premiere
kept them the same size, you just needed to select export -> movie... Tiff sequence,
deselect recompress, select best quality and optimize stills. File sizes were the same,
and I could rest assured that the original AE image quality was still there.
Now in CS4, something fundamental has changed. AE CS4 still makes perfect TIFF
animation frames (at 1024x576 same as CS3, about 1730kB and at 1050x576 about
1770kB).
So far, so good.
In Premiere 2.0 and 3.0, you could select a preselection 720*576 pal widescreen
composition and when exporting the edited animation would get the same pixel-level
IQ as from a custom Desktop: 1024*576 square pixel composition, when using the
Export movie described above. This to me looks like Premiere uses the original
TIFF material.
But in Premiere 4.0, something weird happens. If I use a 720*576 pal widescreen
preset (with AE CS4 1050*576 animation sequences) and export 1050*576 pal
widescreen square pixel image sequences, Adobe Media Encoder chops off 330
square pixels and stretches the image horizontally for blurred, sad results.
EXPORT MOVIE never did this!
Having found that out, I use only custom-> desktop: 1024 or 1050 projects now,
but here again something weird happens: Adobe Media encoder adds about 600kB
to every TIFF frame, and I'm almost unable to notice the difference, but I would say
that the images certainly don't look any better than the ones that were imported to
Premiere, more on the opposite. So, in every option but when exporting one TIFF at
a time Media Encoder alters the superb AE TIFFs.
Why on earth does Adobe want to add a huge amount of useless bits, in animation
the disk space required increases very significantly. What was wrong with the
EXPORT MOVIE option?
I'm asking should I just edit in Premiere 3 if I want unchanged, superb AE quality
TIFF sequences? Premiere gives it when I export only 1 frame, but as soon as I tick
"Export as sequence" it starts Adobe Media encoder which affects all frames, even
those with no Premiere effects on them. Premiere 3 preserved original IQ even in
PAL editing mode (export movie uncompressed) but Encoder in CS4 either
loses 30% of the pixels or adds about 600kB more air!?!?!
1050*576 is not a must for me because I want web movies to be 16:9 sqpix and
the Avid where I work in prefers 1024*576 over 1050*576 in Digital Betacam tape
exporting for uncompromised broadcasting results.
This issue is affecting many animatiors here in Finland, in CS3 and earlier there
were no problems because Premiere respected AE quality work, but now this Media
Encoder has messed things up, not selecting Custom-desktop-1024/1050 will ruin any
animation movie image sequence and selecting it makes files A LOT bigger without any
improvement in IQ.
I hope someone from Adobe could explain what on earth is going on in Premiere
development? Many animation professionals in Finland are awaiting your kind reply.
Anyone with a clue what's going on in the altering can give a hand!
Olli Laamanen, Finland

I did additional testing by comparing exported frames from Premiere
to the AE frames. Only when I delete all render files before export, do I get
the same image pixel-wise. But then there's the extra ~600kB of data.
Does anyone know what that is, a colleague suggested it might be the color
profile or some metadata added by adobe media encoder. I'd really like
to know what it is! Someone who knows something about this Adobe
Media Encoder might have the answer.
So if you are using AE and Premiere to make animation and want to
keep your master footage unchanged, the equivalent for CS3 export ->
movie -> TIFF uncompressed is to
-work only in desktop mode
-delete all render files before exporting media through the encoder
otherwise CS4 will change your images.
Like this it doesn't change the images but adds over 30% additional
data (somekind of tags/metadata)?
Anyone with a guess what it is, please help!

Photoshop CS6 can't/won't open TIFF file created in photoshop CS3

Earlier this year, I was still using CS3. I created a bunch of original TIFF files, and modified files which had been created in CS1. When I am having to go back and reference these CS3 TIFFs, some of them are giving me an error message and refusing to open. Evidently, they are not compatible with CS6?! Seriously?!
I have since uninstalled CS3, but the box is sitting on the shelf if I need it (which I am hoping I don't). Any suggestions for a workaround - preferably one which will not destroy my layers.
Thanks!

Well, carp. Just like when you take your car in to the mechanic: I can't find any of the offending TIFF files. Not surprising considering that I have just north of 1,000 on my drive. Yikes.
For the record, the error message basically just said that the file I was trying to open was incompatibile with this version of Photoshop. And just now I successfully opened a file from April 2005, originally created in CS, and it is completely intact. My novice-ness shows through , but it's perfectly intact.
Sorry to bother to Board; I'll come back when (if?) the message comes back.
Thanks.

Batch merging two TIFF files into one

I have a lot of portrait B5-size TIFF files that were scanned from paper documents and I plan to scan more.
I want to merge every two of these files into landscape B4-size TIFF files.
I want to do this by a batch job.
What is the best way?
Are there any command-line tools to do this job?
I do not have Adobe package software. Instead I installed MacGimp.
Although I have some experience with shellscript and Applescript,
I'm new to Script-Fu.
I made a GUI script for the application Preview that reads a multi-page TIFF file and saves as a PDF file with 2-UP layout. This method has two flaws:
(1) Preview aborts for large files.
(2) Resulting PDF file is more than five times as large as original TIFF file.
Namely, 40-page, g4-compressed, 400KB TIFF file results in 2.5 MB PDF file.
Maybe, the Preview does not make inheritance of TIFF compression.
So I decided to make multi-page TIFF files of 2-UP layout.
Thank you for reading.
iMac G4 Mac OS X (10.3.9)

Self-solved.
convert file1.tif file2.tif +append result.tif
The command-line tool `convert' can be installed by Fink
as a part of ImageMagick.
iMac G4 Mac OS X (10.3.9)

Automatically Slicing Large TIFF Files with Photoshop 5.1

I am trying to automatically slice a very large TIFF file (800 MB) into 28 equally-sized rectangles using Actions (it is a scanned image of 28 scientific slides and reducing the resolution is not an option). My goal is to start with the TIFF file and end up with a folder that contains 28 separate files. I'll do this on many such TIFF files, so it needs to be coded into an action.
So far I have an action that creates guides in a grid pattern and then converts the guides to 28 individual rectangular user slices that together cover the entire screen. Unfortunately the file is far too large to use with the "Save for Web & Devices" tool and I also can't export to TIFF from that tool. So I made an action that individually selects each slice (using the slice select tool), copies it, creates a new file, pastes the image, saves it as a flattened, non-compressed TIFF into a new folder, then closes the file. When I try to run this I get the following error:
The command "Select" is not currently available
          -- Continue --       -- Stop --
If I press Continue the action is not carried out. If I press Stop and select the slice manually there is no problem (but then my action will not be fully automated). The image is in 8-bit RGB mode, and I've also tried converting the locked Background layer into a standard layer. I don't see any reason why the select command shouldn't be available! There is only one layer and there are user slices available for selection. I tried separating the slicing and select/import jobs into 2 different actions but it still didn't work.
Any help you can give me would be greatly appreciated! Thank you!
Photoshop CS 5.1 Extended, v. 12.1 x64 - I have installed the recent update
Windows 7 64-bit
6 GB RAM

This might do it...
It will save the individual files in a folder called filechop off the files path.
#target photoshop
function main(){
if(!documents.length) return;
var dlg=
"dialog{text:'Script Interface',bounds:[100,100,380,290],"+
"panel0:Panel{bounds:[10,10,270,180] , text:'' ,properties:{borderStyle:'etched',su1PanelCoordinates:true},"+
"title:StaticText{bounds:[60,10,220,40] , text:'File Chop' ,properties:{scrolling:undefined,multiline:undefined}},"+
"panel1:Panel{bounds:[10,40,250,130] , text:'' ,properties:{borderStyle:'etched',su1PanelCoordinates:true},"+
"statictext1:StaticText{bounds:[10,10,111,30] , text:'Accross' ,properties:{scrolling:undefined,multiline:undefined}},"+
"statictext2:StaticText{bounds:[140,10,230,27] , text:'Down' ,properties:{scrolling:undefined,multiline:undefined}},"+
"across:DropDownList{bounds:[10,30,100,50]},"+
"down:DropDownList{bounds:[140,30,230,50]},"+
"saveFiles:Checkbox{bounds:[10,60,230,80] , text:'Save and Close new files?'}},"+
"button0:Button{bounds:[10,140,110,160] , text:'Ok' },"+
"button1:Button{bounds:[150,140,250,160] , text:'Cancel' }}};"
var win = new Window(dlg,'File Chop');
if(version.substr(0,version.indexOf('.'))>9){
win.panel0.title.graphics.font = ScriptUI.newFont("Georgia","BOLD",20);
g = win.graphics;
var myBrush = g.newBrush(g.BrushType.SOLID_COLOR, [1.00, 1.00, 1.00, 1]);
g.backgroundColor = myBrush;
var myPen =g.newPen (g.PenType.SOLID_COLOR, [1.00, 0.00, 0.00, 1],lineWidth=1);
win.center();
for(var i=1;i<31;i++){
   win.panel0.panel1.across.add ('item', i);
   win.panel0.panel1.down.add ('item', i);
win.panel0.panel1.across.selection=0;
win.panel0.panel1.down.selection=0;
var done = false;
    while (!done) {
      var x = win.show();
      if (x == 0 || x == 2) {
        win.canceled = true;
        done = true;
      } else if (x == 1) {
        done = true;
if(!documents.length)return;
var startRulerUnits = preferences.rulerUnits;
preferences.rulerUnits = Units.PIXELS;
doc = app.activeDocument;
app.displayDialogs = DialogModes.NO;
doc.flatten();
var tilesAcross = parseInt(win.panel0.panel1.across.selection.index)+1;
var tilesDown =parseInt(win.panel0.panel1.down.selection.index)+1;
var tileWidth = parseInt(doc.width/tilesAcross);
var tileHeight = parseInt(doc.height/tilesDown);
var SaveFiles = win.panel0.panel1.saveFiles.value;
ProcessFiles(tilesDown,tilesAcross,tileWidth,tileHeight,SaveFiles);
app.preferences.rulerUnits = startRulerUnits;
main();
function ProcessFiles(Down,Across,offsetX,offsetY,SaveFiles){
try{
var newName = activeDocument.name.match(/(.*)\.[^\.]+$/)[1];
}catch(e){var newName="UntitledChop"}
var Path='';
try{
Path = activeDocument.path;
}catch(e){Path = "~/Desktop";}
if(SaveFiles){
Path = Folder(decodeURI(Path) +"/FileChop");
if(!Path.exists) Path.create();
TLX = 0; TLY = 0; TRX = offsetX; TRY = 0;
BRX = offsetX; BRY = offsetY; BLX = 0; BLY = offsetY;
for(var a = 0; a < Down; a++){
for(var i = 0;i <Across; i++){
            var NewFileName = newName +"#"+a+"-"+i;
   app.activeDocument.duplicate (NewFileName, true);
    activeDocument.selection.select([[TLX,TLY],[TRX,TRY],[BRX,BRY],[BLX,BLY]], SelectionType.REPLACE, 0, false);
    executeAction( charIDToTypeID( "Crop" ), undefined, DialogModes.NO );
    app.activeDocument.selection.deselect();
if(SaveFiles){
var saveFile = File(decodeURI(Path+"/"+NewFileName+".jpg"));
SaveJPEG(saveFile, 10);
app.activeDocument.close(SaveOptions.DONOTSAVECHANGES);
    activeDocument = documents[0];
TLX = offsetX * (i+1) ; TRX = TLX + offsetX; BRX = TRX; BLX = TLX;
TLX = 0; TLY = offsetY * (a +1); TRX = offsetX; TRY = offsetY * (a +1);
BRX = offsetX; BRY = TRY + offsetY; BLX = 0; BLY = (offsetY * (a +1)+offsetY);
if(SaveFiles){
Path.execute()
function SaveJPEG(saveFile, jpegQuality){
jpgSaveOptions = new JPEGSaveOptions();
jpgSaveOptions.embedColorProfile = true;
jpgSaveOptions.formatOptions = FormatOptions.STANDARDBASELINE;
jpgSaveOptions.matte = MatteType.NONE;
jpgSaveOptions.quality = jpegQuality;
activeDocument.saveAs(saveFile, jpgSaveOptions, true,Extension.LOWERCASE);

Photoshop Opens 8bit TIFF files as Camera Raw

My normal workflow consists of opening RAW files in ACR, making adjustments, then moving on to Photoshop where I apply retouching and build clipping paths. I then save the file as an 8bit TIFF. I rarely reopen these 8bit TIFFs again, but when I did so recently what I encountered was not what I expected.
My Photoshop (CS6) is opening 8bit TIFF files as Camera Raw when selected by "right click" followed by "Open with Photoshop CS6". I remember being able to open 8bit TIFF files directly in Photoshop, but I think this change has occurred since installing CS6.
Again, files in question began as 16bit Raw files, but were worked on in Photoshop CS6 (retouching) and saved with clipping paths. This would reduce them to 8bit files. When placed in page layout, clipping paths work properly, confirming that paths are intact.
When I want to open the files again - say from Bridge or a Finder window - by the method "right click - Open with Photoshop CS6", the file is opened first in Camera Raw, and then in Photoshop, and the path(s) is missing.
I can open these TIFF files and access Paths but only if I locate and select the file from within Photoshop (File/ Open.../). The Open window gives "Format" as Camera Raw (which it isn't, having been saved as 8bit file). If I override format to "TIFF", the file opens with clipping path shown.
What might be going on here and how can I correct it?

DaleH wrote:
I set the preference to automatically open JPEGs and TIFFs with settings.
That's the reason for Adobe Camera Raw being automatically used to open TIFFs which were previously sent from ACR to Photoshop. The TIFFs have ACR settings because they originated as images generated from raw files by ACR. If you don't want ACR to be invoked when opening such files by a right-click then set the preference to "Disable TIFF support".
DaleH wrote:
I didn't manually set the bit depth.
When I saved the file with a clipping path it automatically dropped down to 8bit.
That's not happening here with CS6. 16 bits per channel are maintained when saving TIFF from Ps, regardless of there being a clipping path. Are you certain that the ACR workflow options definitely said 16-bit, as shown below, when ACR initially generated the images from raw and passed them to Ps?

Extension for tiff files - tif vs tiff

I have encountered some (for me) confusing behavior. I have been working with both aperature and photoshop cs4. When I take a file from aperture to cs4, aperture creates a file with the extension.tiff. when I then save the file after working on it in photoshop it saves with the extension .tif. that is to say, Aperture uses 2 'f's and photoshop uses 1 'f' which results in two files. Is this related to option choice in the Tiff save panel or something anomalous with aperture.
Thanks for any suggestions.

I have played with this a little more and this is what I found. The file created by aperture has the tiff extension. If photoshop is set up to open all tiff files using camera raw, then when editing is complete and the file is saved it will be saved using the save as dialog even if save is selected, and the tiff file saves with a single f by default. The second f can be added in the save dialog box in which case it asks if you want to save the file that already exists. Save over the original tiff file and the edits will be visible in aperture.
On the other hand if camera raw only opens tiff files with adjustments, the the save command saves directly in which case the two f extension is maintained.
Apparently use of camera raw causes the save as dialog box to come up the first time the file is saved. Thus one can either add the second f in the dialog or forgo the use of camera raw for tiff files being brought in from aperture.

Minilab won't read .tiff file from Aperture

When Aperture exports a TIFF file it gives it the .tiff (rather than .tif) extension. Our local professional minilab uses an Agfa D-Lab 2 machine, and apparently this will not read files with a .tiff extension. The lab had to rename all the files on their PC first to give them a .tif extension.
Is there a way of getting Aperture to export files with .tif extension? Or do we have to rename all the files after export before submitting to the minilab? Thanks for any advice!

The .tiff extension is something Apple has needed to fix ASAP for a long time. It gets in the way of a proper workflow. When clients receive .tiff files and they work on them in Photoshop they'll end often end up with .tiff.tif files after they are saved. Very annoying and it probably makes the photographer look sloppy in the clients' eyes.
I've tried the automator route and it doesn't work because it will not rename the extension. You can batch the files in Photoshop, save them as tif's, they'll then be ".tiff.tif" and then use a program like iView to extract the ".tiff" and replace it with nothing so that you end up with the the file_name and the .tif extension. IOW, a tiff named as it should be.
I haven't tried it yet but I may pick up this software, A Better Finder Rename. http://www.publicspace.net/ABetterFinderRename/index.html It says it will rename the file extension and it will do it as a batch. Could be a lifesaver until Aperture fixes the .tiff issue.

Premiere Pro CS6 won't recognize alpha channel in .tiff file from photoshop

Hey Everyone,
I'm new to Premiere Pro, but I have used Final Cut Pro 6-7. Anyway, I created a 3D text design in Photoshop to use on top of another photo in a video in Premiere. In Photoshop, the alpha channel appears fine. In Premiere Pro it is not recognized. Instead, a white background appears where the alpha channel should be. When I layered the 3D text on top of a photo (in Premiere Pro), the white still appears around the 3D text design. After I imported the file, I did click on the .tiff file and clicked on modify---->interpret footage----->alpha channel (where I deselected ignore alpha channel). Premiere Pro still does not recognize the alpha channel. Should I convert the Photoshop file to another format or is there something I'm not doing? I'm spending more time trying to figure this out than I am on putting this short video/photo slide show together. I would greatly appreciate any help anyone can offer.

Thanks Ann!!! Seriously, you just saved me hours of aggravation. I didn't know I had to select that in Photoshop. I was under the impression that Adobe product files were seamless.

Raw file settings missing from smart objects in tiff files after upgrade to CS6

Yesterday I was using Photoshop CS5 and RAW 6.4 (?) in a Windows environment.
When editing photographs, I generally open the photo in Camera Raw, make development changes (ie exposure, contrast, etc) and then open the developed image as Smart Object in Photoshop. I then clone, add layers, masks, etc. and then save the final image as a tiff.
Yesterday, I upgraded to Photoshop CS6 and RAW 7.0. Now, when I open my tiff files and Smart Objects in the RAW editor, my exposure, contrast, and black settings are missing (reset to zero). My graduated filter settings are also missing.
It seems to me that the embedded sidecar data in the tiff / Smart Object is not being read correctly.
How can I update my old tiff / Smart Objects? Re-developing thousands of photos is impractical.
NOTE: As a side note, I opened a RAW file with xmp data (not stored as a tiff/Smart Object) and had no problems.
Many thanks.

You need to set the ACR engine to the 2010 version in the prefs.
Mylenium

.Tiff files show as RAW files

I have an Olympus C-770 Ultra Zoom and have just shot some .Tiff files and loaded them into my 5th G. iPod via the Apple camera connector. They have shown up as RAW files for some unknown reason so I can't view them on the iPod. What is going on and what is the solution?

Thank you for replying. That is right, I am quite suspicious of memory - my laptop is full to the brim and I suspect that this may affect available memory and cause some problems in LR. Unfortunately, I don't know enough about computers to be certain.
The card reader - quite simple: the card reader is the same, whether I save the files to the internal or external drives. I put the SD card in it, then copy the files and paste them where I want them. When done, I then open the LR and synchronize the folder. When I copy and paste files to the internal drive, the images look fine in LR; when I copy and paste them into the external drive, 80% of them come up visually corrupted in LR. Since the same card reader is used in both cases, and the files are OK when saved internally, I am assuming it is not the card reader.
So, basically, when I became aware of the problem, I tried copying and saving the same file both internally and externally from the card reader, in order to verify what was going on. That is how the same file (more than one, actually) ended up on three different drives.
Right now, my instinct is to copy everything to an external drive and clear some space on the internal one. I am very apprehensive though - what if something is causing file corruption on the external drives - in that case I will be corrupting everything when I migrate the files. Hence my previous question - are the files actually corrupted, or do they simply appear corrupted in LR because of memory issues? As I said, I don't know enough about this to be certain and do not know what to do.

Not able to open TIFF files

Photoshop is not able to open few TIFF files and I am not able to understand what's making these files different from the other TIFFs
Attached the error box that's popping when trying to open the file in Photoshop.
Here is the link of the TIFF file which is throwing the above error - https://www.dropbox.com/l/IDZfh8TSHAWgS8mP0oWeFn
Please help

Your file is corrupted.
Some applications are able to open the embedded, flattened, JPEG preview only.

TIFF files and OCR

Similar Messages

Maybe you are looking for