Opening 16-bit TIFF in LabVIEW Pro

16-bit images are captured from a PerkinElmer digital panel in an x-ray system. LabVIEW will not open these saved TIFF images directly. If images are first opened using ImageJ and then re-saved as a TIFF image LabVIEW can then open them. The images however have the same file size but are slightly modified at the high intensity values which currently are not an issue.
How can these TIFF images be opened without having to go through this second step; has anyone written LabVIEW software to take images directly from the panel - free or for purchase as a vi for use in a larger program?

Would it be possible to post one these images. I have tried to duplicate the issue using a stock Tiff image, but I cannot get the error you are reporting. I would check and make sure that all of your image types match up, such as in IMAQ Create and IMAQ ImageToArray. If you are reserving a memory location for an image other than 16 Bit, then that could cause an error. Also, if you don't have the correct indicator wired to the output of the IMAQ ImageToArray VI, that could cause an error too. It sounds like the error is occuring at IMAQ ReadFile though. Are you using the default file options, or are you setting them through a control or constant? If so, what inputs are you changing? If the inputs don't match up, that could lead to an error also.
Regards,
Chris L
Applications Engineer
National Instruments
Certified LabVIEW Associate Developer

Similar Messages

Opening 32 bit TIFF in camera raw (or not...)

I have been following tutorials on creating HDR images in photoshop using the 32 bit function.
Once I have created the 32 bit image, and saved it as a Tiff file. I then go into bridge and made sure the preferences for camera raw are set to enable suppoprted TIFFs. However I cannot open this image through camera raw, it just opens up in photoshop...
In the turorials I have seen this does not seem to be a problem for others, why won't this work for me?

Sudarshan,
Thankyou for your reply.
I have managed to resolve this problem now. I have recently downloaded photoshop and therefore assumed it was the most up to date version. This was not however the case, as I had camera raw 7.0 installed. I have updated this to the latest version and this problem has resolved itself, I can now edit the 32-bit TIFFs in camera raw.

ACR 4.4.1 opening 8-bit TIFFs as 16-bit TIFFs

I have a number of 8-bit sRGB TIFFs produced from scans of 35mm colour slides by the Epson Perfection 4990 Photo scanner. Am using Win XP Pro SP3.
If I open these images from Bridge 2.1.1.9 directly in Ps CS3 10.0.1 they are correctly shown in File Info and at the top of the Ps file view window as being 8-bit sRGB TIFFs.
However, if I open these from Bridge into ACR 4.4.1 (using either CTRL+R or File/Open in Camera Raw) they are shown (in the blue text at the bottom of the view window) as being 16-bit sRGB TIFFs.
Further, if, whilst in ACR, I choose Open Image to open any one of these images in Ps, Ps then says that the image is 16-bit - that is, it now agrees with ACR. If I then save the image as a TIFF (whether or not any adjustments were made in ACR), Ps saves it as 16-bit which nearly trebles the file size (18 to 47 MB).
Anyone have any idea as to why this might be happening?

Andrew,
You are severely confused.
>Seems like ACR should be able to tell the bit depth of a file
RAW files are neither 8-bit nor 16-bit by themselves. It is the conversion in ACR that produces a non-raw (cooked) file in whatever bit depth you define in ACR.
>and the image is then opened in Ps from ACR, and you then choose immediately to close the image without making any edits in Ps, Ps still asks you if you want to save the changes to the document be
The instant you click on Open in the ACR dialog box, a brand new image is
created in RAM with whatever parameters you define in ACR. You no longer are looking at your raw image {or TIFF] but at a converted image that exists only in RAM. If you do not save it, that image is lost forever --meaning that you need to go back and open the raw image {or TIFF] in ACR all over again.
You need to do your homework, Andrew. Read the white papers linked in the FAQs of this forum to understand what a raw image is (essentially a very, very dark linear grayscale image) and read Jeff Schewe's book on ACR to learn how to use it.

HT3989 Open 32-bit AU at logic pro 10

I updated from snow leopard to mountain lion and from logic pro 9 to 10. I can't change it to 32-bit even if I follow the instructions above. what can I do?

LPX is 64-bit exclusively and so is the OS ML! Therefore you're out of luck if you plan to use 32-bit plugins. There are possibilities to bypass this rule with assistance of third party apps. At the moment I'm testing Plogue Bidule
http://youtu.be/7KAifzef5uk
I'm still testing all possibilities, but it looks promising.
Another app which seems to be capable of offering a platform for this purpose is Vienna Symphonic Library. I did not have the chance to test so I will not comment.
Hope that helps.
Have a nice day!

Import 16 bit tiff files in premiere pro cs5 ?

When i try to import a 16 bit tiff sequence I get an error message "The video bit depth of this file is unsupported.".
I could not find how to set bit depth in project, however I understand from the help files that 16 bit workflow is supported.
What I am doing wrong?

Hi again Salazaroo....
Thanx for your answer...
I am working in a project shot with RedOne and the output will be 35mm and DCP.... we´ll made the prints with Cinevator system as well... same as yours...
What I did is open the Pr project in After effects and from there export the R3d as DPX to work in the compositings... I am trying different ways to do this... change the R3D settings to RedLog and RedSpace before to export as DPX OverRange, or PDLog985 and RedSpace before to export as DPX Standard (as Mark Christiansen says in THIS SITE) ...
Once I do it, I import the DPX to start the composition... so I change the Cineon Settings to OverRange or Standard (depending of the settings at export) and apply the Cineon Converter LogToLin... but then everything looks too overbright to work... I am working with the DPX and .psd and tiffs together so it is like crazy to match everything together...
I tried to export as PDLog985, RedSpace and OverRange Cineon Settings (instead of Standard) and it looks much better... I check the picture looking at the Info panel and everything is Ok, or close the 'Iris simulator' and detail appear in the image, ...but when I check different elements coming from matte painters and 3d artist, whites clip at 1... how can i match everything together in the same space color to work and then apply the Cineon Converter LintoLog before export???
This is the first time I work with DPX and I am reading a lot about it, but I could´t find a step by step explanation... and it is like there are many ways to deal with it... some people says to use a general Working Space, some people says don´t (See this Article) ...
Thank you man.... I really appreciate your help....

How to open a 16-bit dll in Labview

Hi,
I would like to open a vi for a spectrometer (Jobin Yvon 270M), but I get the following error message: "A CIN tried to load a 16-bit dll. This operation is not supported under Labview for Windows 95 or Windows NT. The CIN and DLL must be recompiled". Is there any way how I can open the 16-bit dll in Labview? I´ve read that it could be possible by writing a Thunk DLL(???). Do you have some advise how to solve this problem?
Thanks a lot,
Markus.

This isn't a LabVIEW issue, but a Windows issue. To call 16-bit code from a 32-bit OS you need a bridge. That's what the thunk is. You can read more from this MS KB article. There's also this NI article. Not for the faint of heart.

16 Bit Tiff Images Display Bug?

Question 1:
Is there a problem with Aperture 2.0 displaying 100 + mb 16 bit tiff images generated by a film scanner (nikon coolscan 4000 ed)? I am having trouble with my library that I migrated from Aperture 1.5. All of my images were working fine in Aperture 1.5 (and previously in iPhoto as far back as 2003). In Aperture 2.0 I am getting scrambled images and some images that read unsupported file format. The problem is sporadic. It effects some images and not others. Sometime images display correctly and sometime they become scrambled and unsupported, and then back again.
There is no trouble with the images themselves. I export them to CS3 with no distortion or trouble. The problem seems to be in Aperture 2.0.
I have re-built the library, tried migrating images, changed the color profile.... I think I have exhausted every trick I can manage from a user vantage point. The images work fine when converted to 8 bit files. This is not the solution for me - I need to keep these images 16 bit.
Question: Is this this just my version (I purchased downloaded upgrade), that is having trouble, or is this a wider problem that Apple aware of and is looking into?
Please advise. I have 1000's of scanned pictures that I have been working with for years that were fine and now are not. I purchased a new Mac Pro 2.8 so as to work more productively with these large images - and now it seems that the very software I rely on has failed me.
I have not been able to find any comments from Apple regarding this issue.

I've had this problem with images saved as 8-bit scans.
Are you using any compression in the TIFs? I scanned using Nikon Scan 4, cleaned up a bit in Photoshop 7, reduced the bit depth to 8-bit, and saved at TIFs with embedded colour profile using ZIP compression, Macintosh byte order.
This used to work with Aperture 1.5.6, but with Aperture 2.0 I see a kind of offset pattern, so a vertical line looks like this:
If export the master TIF, open it in Photoshop (where it looks normal) and save it with no compression Aperture displays it properly.
(I'm still using Tiger, so I don't think this is an OS issue.)

ACR with 32-bit tiffs?

I ran a set of HDR images through Merge to HDR Pro. Saved the result as a 32-bit tiff. Back to Bridge 6.0.1.6 where I can see the tiff.
I now want to do the RAW processing on the HDR file in ACR. I have no "Open in camera RAW".
I can open .NEF, .jpg, and other tiffs. Does ACR not support 32-bit tif files? And if it is supported, what do I need to do so I CAN get into ACR with a 32-bit tif?

Check this thread:
http://forums.adobe.com/message/4514579

Save as a 16 bit TIFF file for Enlarging?

Question, a local photo developer told me that if I wanted to develop my photos at something like 16 x 20 or larger I should save my photos as a 16 bit TIFF file. Elements 4.0 does not seem to allow me to set the bits at 16, just 8. Is there any truth to what they are saying?
Also isn't the file size going to be massive when doing this. Most likely prohibiting an upload to their site?
I am shooting with a Nikon D50 in RAW format. Obvioulsy I have to open it in Elements from Camera Raw as an 8 bit photo to save it in either TIFF or JPEG format.
Any comments are appreciated.

Thank you for your comment.
When I save the 16 bit file in ACR it saves it as a .dng file. When I open the .dng file in Elements again the raw editor opens it as a 8 bit file automatically. This may be all well and good if I can have enlargements made with this file type but not good if what the developer is telling me is true. ???????

PSE 10 as external editor for Aperture 3 - 8-bit TIFF and what color space?

Hi all,
I'm taking the plunge and trying PSE 10 as my external editor for Aperture 3. I understand that I need to export as 8-bit TIFF files (not 16) because PSE can't do certain things with 16-bit files. Is that right? Should I specify a color space in Aperture or leave it as "no profile selected"? (I don't know much about color spaces; I'm not a pro.) I print on an Epson RX580 Stylus Photo printer, if that matters.
I'll be grateful for any help and advice. Thanks.

Can I suggest you buy Philip Andrews book, Advanced Photoshop Elements 10. he explains colour spaces and much much more very clearly and exactly what can be done with 16 bit files and what you then have to change to 8 bit to accomplish. He's written basic and advanced guides for Elements since day one. Usually available from Amazon for under £20.

Please a solution against crashes when opening a file with Acrobat XI pro?

Hello,
Am a member of Adobe Creative Cloud.
Am also constantly having crashes when opening a file with Acrobat XI pro.
Am running on Windows 7 Home Premium, Service Pack 1, 64 bit - RAM 20 GB -
The crash happens systematically after the installation of the update. Within one day I uninstalled and reinstalled the program 4x! It takes of a lot of my time.... Thank you for providing a definitive solution!
Best regards

I've been having the same issue! I try to open it and it crashes - says re-open, it crashes... I re-installed it yesterday and it opened and worked fine. Closed it out at the end of the day thinking everything was finally fine but this morning the same crashes it had yesterday... HELP!!!

Save U32 bit image as 16 bit tiff

Right now I am using IMAQ to grab a RGB(U32) color image in real-time. I am then trying to save the image as a 16 bit tiff file. However, the images only save as 8 bit tiff files. How can I fix this problem?
Thanks,
David

Hi David,
The simple VI that I attached reads an image from file and writes it as a TIFF. If you would like to test it, you can open up one of the images in the Vision >> Images folder (for example, candy.png which is U32) and you will see that it should save it as a U32 TIFF file. If the image you are reading in is I16 (i.e. IMAQ Create has type I16 wired in as a constant) then you should get an appropriate image out. If you are successful with this VI, I would recommend migrating it into your application. I hope this helps give you a good start.
Vu
Attachments:
Write TIF.vi ‏55 KB

16-bit TIFFs seem to have a blue hue

I modified the original images (usually RAW) with photoshop, and saved them as 16-bit TIFF files so as to retain as much quality as possible.
(I am using a collection in photoshop elements to manage the pictures, and itunes syncs them from there.)
Yet, when they sync to my ipod/color 60g, they have a blue-ish hue to them.

open system preferences (either from dock or click on the apple pic top left of screen and select from drop down) or from a finder window: applications, and then click on displays>color then> calibrate and you can play with colors there... and yes, you can click to get it to factory settings..

Even though I have checked "Automatically open all supported TIFF's" in Camera RAw Preferences - My tiff files do not open up in camera RAW

Even though I have checked "Automatically open all supported TIFF's" in Camera RAw Preferences - My tiff files do not open up in camera RAW - PS 6

Sorry I'm taking to along, but I checked a few things using ACR 8.6
Saved a png as an 8 bit tiff, then to 16 bit. Changed the background layer into a floating layer, all opened in ACR.
It was when I added an adjustment layer, that it no longer opened in ACR.
Now what can I recommend? If you have Lightroom, you can Import and work on your layered tiffs that way. I hope this is a viable alternative for you, because I think ACR does have a problem with layered tiffs and I don't really know of any workaround, but you are free to explore.
Gene

Re-edit 32 bit tiff in PS doesn't work?

Hi,
When I generate a 32 bit tiff (HDR) in PS CS5 from bracketed pictures within lightroom 4.1, import the tiff back into lightroom, adjust it in lightroom, and then send it back to PS (option "Edit a Copy with Lightroom Adjustments" selected) for further editing, the file won't open in PS. Opening the file directly in PS works, but without the adjustments made in lightroom.
I have tried the same with a 32 bit tiff from Photomatix. Same behaviour.
Has anyone else noticed this behaviour?
Haya.

Yep, same issue here. You can Export using 16 bit depth and ProPhoto RGB to create a copy, which is what you are actually working with in LR anyhow. It would be nice if 'Edit In' would give you a warning that "LR can only create a 16bit copy with adjustments applied, do you want to proceed," instead of simply failing. Perhaps log this a 4.1 bug?

Opening 16-bit TIFF in LabVIEW Pro

Similar Messages

Maybe you are looking for