16 bit to 12 bit image

I have Labview 8.51 full developmental version and it does NOT have IMAQ arraytoimage.vi!
Anyway I have a camera that captures 12 bit images but the card that supports the camera only outputs 16 bit. So I am getting 16 bit tiff files and I am trying to save it as 12 bit image. Is there any other way of doing this w/o using imaq arraytoimage.vi?

Hello sl2obel2ts,
Bad news: The NI-IMAQ VI ArrayToImage.vi is available only
with the NI Vision Development Module (see the Vision Development Module help
for a complete list of included VI’s).
Good news: There is a way
to convert 2D arrays to grayscale pictures without IMAQ VI’s.
Take a look at the linked KnowledgeBase article, and let us
know if it works for you. I hope this helps
David G
Sales Engineer - SE Michigan & N Ohio
National Instruments

Similar Messages

Is possible to Convert a 1 bit B&W Tiff image to a 16 Bit Greyscale Tiff image?

Hi there,
I am trying to convert a 1 bit Black & White Tiff image to a 16 Bit Greyscale Tiff image, Anyone out there know if it is possible and how it may be done? We are using Adobe Acrobat 9 Pro Extended.
Any help would be appreciated.
Cheers, Chris

Almost any graphic editor can do it, but it doesn't make a sense. The picture information remain the same - 1 bit. It has nothing to do with Acrobat.

IMAQdx Grab changing my images from 16 bit to 8 bit?

I have a labview application that I am trying to use with 16 bit images. It is currently running and working with 8 bit images. I though that if I changed the image type from 8 bit to 16 bit and changed the settings on my camera from 8 bit to 1 using MAX that the program would run the same but with 16 bit images instead. However, even when I do this the camera only captures 8 bit images and then the application fails because of an incompatible image type error because all the settings are set to 16 bit images. I set a few probes and realized that very early in my application all my images are 8 bit even when the camera is set to a 16 bit setting. Also the resolution of my images is different than what the camera is set to. I think that the culprit is IMAQdx Grab because I was reading in the help that if the image type does not match the video format of the camera then IMAQdx Grab changes the image type to a suitable format. How can I make it so IMAQdx Grab wont change the image type? I am fairly new with LabView so this might be something simple or not. Thank you.

Hi Optical Intern,
It sound to me that you are having problems with getting the camera file to do what you want. My guess is that you are not saving the attributes in Measurement and Automation (MAX) when you change them. If you are saving them then I would try and set the attributes programmatically in your VI. This should force it to what you want within the program. Let me know how it goes.
Adam H
National Instruments
Applications Engineer

How to view resolution (ppi/dpi) and bit depth of an image

Hello,
how can I check the native resolution (ppi/dpi) and bit depth of my image files (jpeg, dng and pef)?
If it is not possible in lighroom, is there a free app for Mac that makes this possible?
Thank you in advance!

I have used several different cameras, which probably have different native bit depths. I assume that Lr converts all RAW files to 16 bits, but the original/native bit depth still affects the quality, right? Therefore, it would be nice to be able to check the native bit depth of an image and e.g. compare it to an image with a different native bit depth.....
I know a little bit of detective work would solve the issue, but it
would be more convenient to be able to view native bit depth in
Lightroom, especially when dealing with multiple cameras, some of which
might have the option to use different bit depths, which would make the
matter significantly harder.
This
issue is certainly not critical and doesn't fit into my actual
workflow. As I stated in a previous post, I am simply curious and wan't
to learn, and I believe that being able to compare images with different
bit depths conveniently would be beneficial to my learning process.
Anyway,
I was simply checking if somebody happened to know a way to view bit
depth in Lr4, but I take it that it is not possible, and I can certainly
live with that.
Check the specifications of your camera to know at what bit depth it writes Raw files. If you have a camera in which the Raw bit depth can be changed the setting will probably be recorded in a section of the metadata called the Maker Notes (I don't believe the EXIF standard includes a field for this information). At any rate, LR displays only a small percentage of the EXIF data (only the most relevant fields) and none of the Maker Notes. To see a fuller elucidation of the metadata you will need a comprehensive EXIF reader like ExifTool.
However, the choices nowadays are usually 12 bit or 14 bit. I can assure you that you cannot visually see any difference between them, because both depths provide a multiplicity of possible tonal levels that is far beyond the limits of human vision - 4,096 levels for 12 bit and 16,384 for 14 bit. Even an 8 bit image with its (seemingly) paltry 256 possible levels is beyond the roughly 200 levels the eye can perceive. And as has been said, LR's internal calculations are done to 16 bit precision no matter what the input depth (although your monitor is probably not displaying the previews at more than 8 bit depth) and at export the RGB image can be written to a tiff or psd in 16 bit notation. The greater depth of 14 bit Raws can possibly (although not necessarily) act as a vehicle for greater DR which might be discerned as less noise in the darkest shadows, but this is not guaranteed and applies to only a few cameras.

Merge to HDR Pro is resulting in a different image, and the 8 bit and 16 - bit sliders don't preview

In Cs6 whenever I touched any of the sliders the image in the preview panel changed quite nicely, now when I start the HDR Pro it comes up with a black image in the preview panel. Thats easy to fix though I switch from 16 bit or 8 bit to 32 bit the preview shows up and I can click on the 16 or 8 bit modes and it shows a preview. Then when I adjust any of the sliders nothing happens. I can play with the sliders as much as I want nothing happens. I have been using the 32 bit mode in cunjunction with the 'tone in ACR' setting which gives great results, but now I wanted to play with the scott5 preset. If I click ok it creates the image beautifully. So not only won't it preview but my image is completely different to what is in the preview panel.

I am looking forward to an anwer concerning the HDR preview-result-difference as well... Since some posts suggest to check out the color profile of the input files, i did so: they are both sRGB. And the immense change of saturation and brightness (in other examples even worse than below) couldn't be explained by a different profile anyway, IMHO.
working parameters:
Adobe Brigde CS6 (Tools/Photoshop/HDR PRO)
Adobe Photoshop CS6
sRGB both input and output...

Best practice for managing a Windows 7 deployment with both 32-bit and 64-bit?

What is the best practice for creating and organizing deployment shares in MDT for a Windows 7 deployment that has mostly 32-bit computers, but a few 64-bit computers as well? Is it better to create a single deployment share for Windows 7 and include both
versions, or is it better to create two separate deployment shares? And what about 32-bit and 64-bit versions of applications?
I'm currently leaning towards creating two separate deployment shares, just so that I don't have to keep typing (x86) and (x64) for every application I import, as well as making it easier when choosing applications in the Lite Touch installation. But I know
each deployment share has the option to create both an x86 and x64 boot image, so that's why I am confused.

Supporting two task sequences is way easier than supporting two shares. Two shares means two boot media, or maintaining a method of directing the user to one or the other. Everything needs to be imported or configured twice. Not to mention doubling storage
space. MDT is designed to have multiple task sequences, why wouldn't you use them?
Supporting multiple task sequences can be a pain, but not bad once you get a system. Supporting app installs intelligently is a large part of that. We have one folder per app install, with a wrapper vbscript that handles OS detection. If there are separate
binaries, they are placed in x86 and x64 subfolders. Everything runs from one folder via the same command, "cscript install.vbs". So, import once, assign once, and forget it. Its the same install package we use for Altiris, and we'll be using a Powershell
version of it when we fully migrate to SCCM.
Others handle x86 and x64 apps separately, and use the MDT app details to select what platform the app is meant for. I've done that, but we have a template for the vbscript wrapper and its a standard process, I believe its easier. YMMV.
Once you get your apps into MDT, create bundles. Core build bundle, core deploy bundle, Laptop deploy bundle, etcetera. Now you don't have to assign twenty apps to both task sequences, just one bundle. When you replace one app in the bundle, all TS'es are
updated automatically. Its kind of the same mentality as active directory. Users, groups and resources = apps, bundles and task sequences.
If you have separate build and deploy shares in your lab, great. If not, separate your apps into build and deploy folders in your lab MDT share. Use a selection profile to upload only your deploy side to production. In fact I separate everything (except
drivers) into Build and deploy folders on my lab server. Don't mix build and deploy, and don't mix Lab/QA and production. I also keep a "Retired" folder. When I replace an app, TS, OS, etcetera, I move it to the retired folder and append "RETIRED - " to the
front of it so I can instantly spot it if it happens to show up somewhere it shouldn't.
To me, the biggest "weakness" of MDT is its flexibility. There's literally a dozen different ways to do everything, and there's no fences to keep you on the path. If you don't create some sort of organization for yourself, its very easy to get lost as things
get complicated. Tossing everything into one giant bucket will have you pulling your hair out.

Change from 16 bit to 32 bit

how do you change 32bit photos to 16 bit

Hi,
Do mean going from 32 bits/channel to 16 bits/channel like under Image>Mode?

Separate GPO for 32-bit and 64-bit machines?

Before I give myself a whole load of work wanted to confirm this either way...
We're imaging both 32-bit and 64-bit Windows 7 this summer (x86 for app compatibility and x64 for Adobe CS6 etc). So far I've made a full working policy for x86 but now need to do x64.
When I created the initial policy on a 32-bit machine the ZCM console automatically seems to add a requirement of Architecture = 32-bit which suggests the policy can only be used on that version of the OS - do I need to create a separate x64 policy from scratch or can the x86 GPO be applied (and work consistently and be supported) on the x64 machines?

Yes unfortunately you have to create your policies with the bit version of
the OS. So you have to do it with a 32bit and 64bit machine.
"gshaw0" wrote in message news:[email protected]..
Before I give myself a whole load of work wanted to confirm this either
way...
We're imaging both 32-bit and 64-bit Windows 7 this summer (x86 for app
compatibility and x64 for Adobe CS6 etc). So far I've made a full
working policy for x86 but now need to do x64.
When I created the initial policy on a 32-bit machine the ZCM console
automatically seems to add a requirement of Architecture = 32-bit which
suggests the policy can only be used on that version of the OS - do I
need to create a separate x64 policy from scratch or can the x86 GPO be
applied (and work consistently and be supported) on the x64 machines?
gshaw0
gshaw0's Profile: http://forums.novell.com/member.php?userid=135427
View this thread: http://forums.novell.com/showthread.php?t=467454

8 bit vs 16 bit

I started creating photo books, and I've been running into some confusing territory. So far my procedure has been to edit RAW photos in Lightroom, then export 16 bit PSDs to InDesign. I layout the whole book in Indesign. Then I have to make PDFs of the book and convert everything to JPGs.
My confusion centers around 8 bit vs 16 bit. If I am converting to final JPGS, should I export as 8 bit right out of Lightroom? Or is it better to stay away from 8 bit as long as possible?

Nice suggestion, but it will generate BIG files though of you use Smart Objects.
For 99% of most publishing needs you won't need 16 bit files. certainly not if you are placing them directly into Indesign, and then exporting them anyway as 8 bit jpegs for print.
16 bit files are for EDITING. They are useful for many color corrections back and forth, for pushing and pulling with 10 retouchers all arsing with the file, to avoid DAMAGE and posterisation. For most printing needs you have to do A LOT of damage to an 8 bit file before that damage registers on the print. Like the ******** I worked with for 3 years who would pile 50 adjustment layers on top of an 8 bit image and wonder why the resulting injet looked like a rainbow - thats what you would be trying to avoid.

16 bit to 8 bit in CS5

Can any body tell me how I change a document mode from 16 bit to 8 bit as it appears some filters can`t handle documents in 16 bit.

Image menu > Mode > 8 Bits/Channel

64 bits or 32 bits

Good evening
On my desktop I have the two 64-bit versions and 32 bit Adobe Indesign, Photoshop, Illustrator.
Could you tell me the advantages and disadvantages between these two versions.
Thanking you
Ulysses

To give you the 10,000 ft view of the advantages and disadvantages of the 32-bit versus the 64-bit versions of these products …
The real difference between the 32-bit and 64-bit versions of these products is the ability to use much larger address spaces with the 64-bit version. Generally speaking, for most documents and images, you will absolutely not see any performance advantage with the 64-bit versions of the applications (and in fact, there could be a very minor but measurable performance degradation with 64-bit). The advantage of the 64-bit versions is that they can directly access orders of magnitude larger virtual memory space. Typical 32-bit applications can only access a 2 GB virtual memory space, regardless of how much physical memory you have installed on your computer. This may sound quite ample, but when you are dealing with very long and/or very graphically-rich InDesign documents, for example, that 2GB memory is chopped up into temporary document storage, screen buffers, placed imagery temporary storage, and work spaces for a myriad of internal functions including layout, color management, content placement, PDF (and DPS and other format) export, printing, etc. Prior to InDesign 9, it was not uncommon to need to regularly exit InDesign and restart the program to reclaim these workspaces to avoid out of memory messages – these were not messages about being out of physical memory, but rather virtual memory. With the new 64-bit version of InDesign, these issues are of the past. Illustrator documents may be complex, but with rare exception contain only one artboard and typically don't have the same virtual memory issues. On the other hand, if you are a user that runs Photoshop with large number of layered, large, high resolution images open, the additional address space of the 64-bit version may be necessary for you as well.
Disadvantages of 64-bit are relatively few. If you use plug-ins for which there are not yet or might never be 64-bit versions, you might be stuck using the 32-bit versions for the time being. An example of this under Windows would be availability of a TWAIN scanner plug-in for Photoshop 64-bit – it doesn't exist.
All this being said, unless you have plug-in compatiblity issues, the 64-bit versions of Illustrator, Photoshop, and InDesign are mature and very stable and thus recommended. (Personally, I've hidden the Windows Start Menu items for both 32-bit Illustrator and 32-bit InDesign and have suffered no problems.)
Be aware that going forward, the 32-bit versions of these applications will eventually be dropped.
- Dov

How do you switch between 64 bit and 32 bit? (Win 7)

I have searched here, Adobe Support, read the User Manual, and can not find any information on how one changes from 64 bit to 32 bit. I am trying to create Time Lapse sequences and CS 5 tells me I have to be in 32 bit mode. How do I get there? I am running an HP Pavilion dv7t-3300 i7 QuadCore with 4gb RAM and Windows 7 Pro 64 bit.

Similar concern here. No 64 bit version. I purchased the Photoshop CS5 downloadable upgrade. I have installed the program but only see the 32 bit version. Image / Mode shows 8, 16 and 32 bit versions and no 64 bit.
Start Programs offers only a single version of Photoshop which based on the splash screen is 32 bits. Did I miss something during the install?
Bob

Filter / Sort by Bit Depth? (16 bit vs 8 bit)

I am looking for a way to use the Filter panel to sort/filter results by bit depth (16 bit vs 8 bit images) - is there a way to do this Bridge CS4? I have looked in every part of the sorting mechnisms and can't find a way. Am I missing something?

Unfortunately there is no such way in the filter panel, it might be a good
feature request, maybe you can add that using the link at the main page on
this forum.
In the meantime there are 2 possible workarounds. Regarding the fact that a
16 bit is twice the size of an 8 bit you might want to use the sort by size
criterion in the Path Bar but when having different source files or layered
files that might not always be sufficient.
If you use the find command (cmd+F / or menu Edit-Find) you can select the
find by bit depth option. Also select the option to equal and use either the
number 8 or 16.
I am looking for a way to use the Filter panel to sort/filter results by bit
depth (16 bit vs 8 bit images) - is there a way to do this Bridge CS4? I have
looked in every part of the sorting mechnisms and can't find a way. Am I
missing something?

Lenovo G580 20157 32 bit or 64 bit?

Hello everybody!
I just bought a Lenovo G580 vith no operating system on it. The problem is that since i don't know if my Lenovo is 32 bit or 64 bit , i don't know if the operating system i'm going to buy should be a 32 bit or a 64 bit. Here are some specifications of the processor: Intel Celeron dual core B830, 1.8 GHz, L3 cache 2MB. Can anyone help?
Thank you in advance guys.

Good day.
This --> Intel link should help you out. The bottom section reads as your CPU is 64-bit.
Hope this helps.
English Community Deutsche Community Comunidad en Español Русскоязычное Сообщество
Community Resources: Participation Rules • Images in posts • Search (Advanced) • Private Messaging
PM requests for individual support are not answered. If a post solves your issue, please mark it so.
X1C3 Helix X220 X301 X200T T61p T60p Y3P • T520 T420 T510 T400 R400 T61 Y2P Y13
I am not a Lenovo employee.

Should I install Windows 7 as 32-bit or 64-bit?

I just purchased a mid 2011 MacBook Air. (11" 1.6GHz Core i5, 4 GB RAM, Lion 10.7.1.)
My ultimate goal is to run PowerPoint and an TurningPoint audience response system that plugs into PowerPoint. TurningPoint says it runs as either 32-bit or 64-bit. That's the only Windows program I will likely use. Otherwise I'm a Mac guy.
My installation disks for both Windows 7 and Office 2010 both included 32-bit or 64-bit.
So is there any reason for installing Windows 7 and Office 2010 as 32-bit or 64-bit?
I plan to use Boot Camp 4.0.1 and have limited tech skills "under the hood."

I'll take you up on your kind offer, Stefan.
I've been reading the Apple info on the install before I get started. I checked out the Boot Camp 4.0.1 interface and see that will be asked to select the tasks. Here's a few questions:
1. It defaults to "checked" on all 3 tasks - should I do the same?
2. My MBA did not ship with any Lion install discs - can I complete the project without one? Does the second task take care of that?
3. What's a "WIndows 7 ISO image"? How do I get one? - or is it created in the Boot Camp process?
Danke,
Peter

10 bit vs 8 bit uncompressed

Would anyone care to explain to me the difference between these 2 forms of compression. I always use 8 bit, never had issues but just want to know the difference. thanks.

The end user will almost always be seeing 8-bit, and your video sources are
probably 8-bit as well, unless you have a very nice camera. 10-bit video
offers more detailed shades of color. For example, if there is a very dark
area in your image, 8-bit might just show black, whereas 10-bit could show
some detail. Of course, if you deliver your final result in 8-bit, then you'll
need to somehow brighten those areas to bring them into the 8-bit range.
It's about the amount of data you have available to represent your image.
Let me try a metaphor. Bit depth is like image size. So, for example, let's
say you shoot a video at 1080 and you are delivering it at 720. It makes
sense to stay in 1080 until the very end, because all your details will be clearer,
and the approximations more accurate as you process. Then, at the final
output stage you can make the compromises inherent in reducing the size.
If you have 10-bit footage (i.e. DigiBeta), and/or you're planning to do a lot of color correction,
effects, and gradients go with 10-bit. You'll get better results.
On the other hand, if you're a beginner working with basic 8-bit footage,
stick to 8-bit. It will work just fine for now.

16 bit to 12 bit image

Similar Messages

Maybe you are looking for