Metadata Status and Greyscale Images

I have a number of 16 bit DNG grayscale images in my collection. In spite of the fact that I update the metadata files, after a short time, the metadata returns to indicating metadata has been changed and the update arrow appears in the Grid even though the file has not been modified. This seems to be isolated to grayscale images.
Any solution available?

Brent,
I have had this problem with more than just greyscale images. The real difficulty is being able to find them since there is no way to filter for those images which have an update arrow on the grid (i.e., needing metadata updated).
If you can isolate them, I have had great success in updating the DNG Preview, which also updates the metadata. This is not selective so only update those that have the icon. Sometimes I have to do them one at a time but it usually gets rid of the icon.
As a side note, if you have "Automatically write to XMP" turned on, the mysterious icons that won't disappear with the Ctrl-S or by left-clicking the icon also have a memory leak which can freeze LR if you are in a session long enough to use up the available memory.
Give the Update DNG Preview a try on one and see what happens.
Jeff

Similar Messages

How do I paint accurate grey levels between 0-254 in an alpha or a greyscale image? Seems impossible ... Works in 5.5 .. not in CC. Bug?

So here's the thing . I need to be able to assign accurate shades of grey in an alpha channel as our code takes the value (between 0-244) and uses it to do its thing. I assumed this would be easy .. just choose your colour and paint .. but not so.
In an alpha channel, or even in a greyscale image, make a selection and fill it with RGB 6,6,6. Since there doesn't seem to be a way to get a greyscale pallette or input the value for Alpha this is th eonly way I can see to do it.
Now, using the info panel, check that it is indeed RGB 6,6,6. It is.
Now, make another selection and fill it with RGB 7,7,7. Check this with the info panel and ... its 6,6,6.
OK so now use levels or brightness to try to shift that 6,6,6 upto 7,7,7 ... check it with the eyedropper color sampler tool .
What you'll find is that the RGB value will go from 6,6,6 .. to 8,8,8 to 10,10,10 it's impossible to make it 7,7,7 or 9,9,9. Theres a whole bunch of other values that are also impossible.
If you do the above in any of the RGB channels themselves it will work fine .. its just the Alpha and in a greyscale image.
On a similar vein, on a regular layer, fill an area with you RGB 7,7,7, copy it and paste it into your alpha. Looks fine .. until you use levels to increase the contrast and you'll find that what was 7,7,7 is now a noise filled mixture of, I assume, 6,6,6 and 8,8,8.
( NB. As a note the above also happened in CS5 but in an old version of Photoshop 5.5 it works perfectly .. I can give the RGB 7,7,7 and the value thats painted is 7,7,7. Bring it into CC and its fine. So its just the creation of tones in CC that is wrong.
Also, it works fine if you edit the individual RGB channels .. you can get 6,6,6 AND 7,7,7 .. but as soon as you copy and paste it into the alpha . .the 7,7,7 reverts to 6,6,6 )
So
Q1 .. what am I doing wrong?
Q2 .. if 8bit alphas and greyscale images can have values ranging from 0-254 .. then how do I define the value I actually want? I can't use the K value as that's only a percentage so has fewer increments and there isn't a separate input for alpha value.
Q3 .. or put it more simply .. how do I set the grey value to a particular number, eg. 7
Thanks.
Pat
Message was edited by: Patrick Ward

Thanks Herbert. I'll have a good look at Photoline.
I don't know if these have anything to do with it but
the first is the color settings from CS5,
the second is the default from a demo install of CC14. I see the gamma tickbox but it doesn't refer to the alpha.
the thrid are the colour settings of PS 5.5. Note this is the one that gives the correct ( with respect to my expectations ) result

Strange Metadata status ?

Immediately after importing a folder, some Jpeg photos had a 'up to date' metadata status, and others 'has been changed'; same with NEF photos. No processing was done on these photos with LR or other software.
so I don't understand how this status is defined ?
Thanks for your help.
Bernard
Windows 7 , LR 3.2RC

I think it is a bug related to the way Lr handles metadata.
Please, have a look at http://forums.adobe.com/thread/714432

Antimalware overall status and history no image

Hello,
We are trying to run the report Antimalware overall status and history for EndPoint Protection status, but we are not able to see the graphics in the report:
Anyone have seen that before?
Thanks for your help!

Hi,
Could you see the graphics in the report when you open the report from Report Manager URL in Reporting Services Configuration Manager? Have you checked srsrp.log?
Best Regards,
Joyce
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Lightroom Metadata editing and workflow is tedious nightmare!

I'm new to Lightroom in just the past month, but have used it enough to see that a serious interface problem makes Lightroom version 1x virtually unusable in a deadline-oriented publishing workflow. Lightroom's Metadata editing and workflow is just a terrible nightmare, and far too tedious and slow. It appears to be an afterthought implemented by good-hearted souls who've never had to edit this sort of information under serious deadline pressures. I know Lightroom is marketed as an image database and not a file browser, but we're all looking to simplify our workflow here and with just a few subtle enhancements, Lightroom could be an excellent file browser and file import manager too.
As it is now, the Lightroom v1x handling of File Naming and Renaming, Metadata Editing and Keyword Editing is poorly implemented and in need of an immediate overhaul to help professional photographers expedite this crucial and time-consuming first step in the archiving workflow. While Lightroom is very good at many other tasks, I give it a big fat "F" of a failing grade for these tasks.
First, the Lightroom Library Module needs an even more simple, linear interface that steps users through a precise procedures (and helps them remember them). Arguably, to accomplish this, the Import function may need to become a separate Module that can be selected and used separately before entering the Library. As File Naming and Renaming, Metadata Editing and Keyword Editing currently are implemented, I, for one, am always forgetting to fill out one of these critical sections and can't even seem to remember that some may need to be done before importing while others appear to be conceived to be done after importing. My point is, all these related steps really need to be done together, but the Interface spreads out the functions too much, and it is nearly impossible to build a logical and linear Import workflow, especially when you are first learning Lightroom.
I'd like to see a workflow that walks me through applying and editing (in order), File Naming, Basic and IPTC Metadata, Captioning and Keywords, so that I don't always forget some obscure step in the process (which I keep doing). Here are some specific suggestions, some of which may prove to be valid, some of which may be problems due to my lack of experience with thye software.
1. As currently implemented, Metadata editing requires too much thought, and does not have enough intelligent automation. Eliminate as much typing as possible (See Photo Mechanic!)
2. Lightroom needs better Metadata Presets. A "Quick Edit" view to simplify interface for editing minimal metadata info (File Name, Basic Info, Keywords, Headline, Limited Copyright Info).
3. Separating Keyword Tags, Metadata Browser, Keywording Presets and Metadata Presets confuses the workflow. They should all appear together under one selectable module that organizes a suggested, linear workflowfor these tasks, but allows it to be customized. This is the sort of tasks that need to be learned by rote memory, and having all these panes floating around on both sides of the photo make it impossible to quickly step through these tasks.
- Name (or Rename) files, Edit/Apply Basic and IPTC Metadata, Edit/Apply Keywords, Import or...
- Import, Name (or Rename) files, Edit/Apply Basic and IPTC Metadata, Edit/Apply Keywords, Import
4. Rename should offer the option of renaming the master file names on the disk, not just file names in the database (which I think is what Lightroom does, but again, this is very confusing for new users)! So, it is my belief that this feature needs a checkbox option to rename one, the other or both. But you need to be able to quickly find this dialog box every time you do an import, and it should not be hidden away out of view under the Library menu. Ideally and logically (for workflow), File Renaming should be handled when starting the Import into Lightroom.
This is critically important because many user

Lightroom metadata editing Part 2 (see Part 1 at top of thread)...
...This is critically important because many users just do not want to trust their images solely to any database and we want the ability to go look for master files with identical names should something go wrong with the software or we decide to edit the file in Photoshop outside of Lightroom or even switch to another library software program.
My own habit is to rename every file with the date followed by a unique, three-digit file number, as in 20070717_001, 20070717_002...up to 999 etc. (I have never shot more than 999 files in a single day, but this could be a four-digit number). To file these on disk, a folder with a similar naming scheme is created for each day's shoot, although a keyword slug is added to the end instead of file numbers.
5. Metadata Presets (Basic Info, IPTC metadata, EXIF metadata), Keywords need to be able to toggled on or off (promote/demote-expand/contract). Turning Off/On one section at a time via the Metadata Presets popup menu is too tedious...and you can't display IPTC and Large Caption together or leave Large Caption turned on. It also is difficult to remember where the Large Caption default (Preferences) setting is...
6. Please get the EXIF data out of the way entirely when editing captions and visa-versa...And the EXIF data should not separate Basic Info and IPTC Info fields. Please relocate the EXIF to the bottom of the Metadata pane...
7. IPTC Content, IPTC Copyright, IPTC Creator, IPTC Image expand/collapse sections need more automation:
- The Presets fields need Preset lists of entry choices for cities, states, countries, etc.!
- ISO Country Code automatically should be filled in when a country is entered.
- Date created automatically should be filled in from camera EXIF data
- Metadata Presets "Save As" should fill in old name, and allow you to rename it; (When it appears, the new name field should not be empty. This would aid in consistent, alphabetical naming
- Metadata Presets naming should support job names, with actual Presets saved under each job name...
8. IPTC Status EXIF, Contact, etc.
- Caption field MUST display more than one line...(6-8 lines)!
- Caption field MUST support Shift/Return!
- Headline (IPTC Content) should be displayed with (and above) caption. Please present information logically!
- Yellow popups should describe what each field name is for...some are real brain teasers...

Ever Changing Metadata Status

I have LR 2 (on a Windows PC) set up to write all changes to XMP. Normally this works very well, but for some pictures the "Metadata Status" message in the Metadata panel constantly changes from "has been changed" to "..." to "Up to date" then back to "Has been changed" again. This happens in Library view when I am not touching the image.
It seems to happen randomly. If I exit LR and then return it has stopped.
The pictures in question seem to be fine, both to examine in LR, edit and also export.
Is this a known problem? Should I be concerned? It seems like a disk write to the image file or a data update to the catalog must be failing. But I have checked my hard drive and it seems healthy.
I wrote about this on my blog and even made an animated GIF http://bkkphotographer.wordpress.com/2009/09/17/the-case-of-the-ever-changing-status/

I’ve been playing with metadata and sidecar XMP files in order to try and learn the way Lr handles them. I’ve also read quite a bit about this subject and now I believe I understand the significance of these XMP files as an insurance in case anything goes wrong with the database, despite the fact that some relevant data is not included in the XMP file and would be lost in case of catalog (database) corruption.
So, I've done a very simple test:
- created a new catalog;
- imported 10 CR2 RAW files;
- immediately after importing they all displayed (quite obviously) a “Metadata Status: Up to date”;
- applied daylight as white balance to all of them in Quick Develop (“Metadata Status: Has been changed”); option to “automatically write changes to XMP” was off;
- saved the metadata to XMP sidecar files (“Metadata Status: Up to date”);
- closed Lr;
- deleted de XMP files.
When I reopened this catalog, Lr shows the Metadata Status as “Up to date”, even though the XMP files are gone. It’s quite understandable that Lr has no way of knowing that the XMP files no longer exist since they were deleted outside of Lr. But if one tries to recreate the XMP files by saving them again Lr shows briefly a message that it is writing the files but none are actually created. Interesting enough I never get the “sidecar file missing” warning.
I’ve found just two ways of recreating these XMP files after deleting them: either creating empty files with the appropriate names matching the CR2 files or changing some metadata (e.g. adding a caption or title to all photos) before saving the metadata.
OK, some might be asking why deleting the XMP files in the first place? Well, files do get deleted by accident sometimes and could also be lost due to file corruption.
What I would like to understand is if one has a catalog that doesn't use XMP sidecars and at some point they are created (by choice or mistake), is there a way of reverting back and not using them?
Am I missing something or Lr is a little bit weak in handling these XMP sidecar files?
Also, has anyone reproduced this on Lr 3 beta?
Any comments will be appreciated.

Metadata Status Box

I am using Lightroom 4 and its working fine however today for the first time I noticed the following comments in the Metadata Status box which I don't understand and have not been able to find any help in my guidebook.
Metadata Status reads
All (2 Metadata Statuses) 29965
Has been changed 29836
Up to date 129
Is there a problem with my database that I don't know about and should I be concerned?

"Metadata Status" refers - as dj_paige has said - to writing the metadata to file (either true sidecar file or into the header of JPGs, TIFFs, PSDs and DNGs - but not into the image pixels!)
This "writing metadata to file" is a separate and additional saving of the metadata that are already saved in the Lr catalog. Lr saves everything you do in Lr instantly and automatically in its database (= catalog). Since it is not saved in the image pixels - as you probably know - it is called metadata.
In addition to the saving in the catalog there is the option of "writing metadata to file". But this option is not necessary for the function of Lr. It is a feature that enables users to see the Lr edits in Adobe Bridge.
The warning you are referring to means that the data in the catalog and in the file are not identical. Since Lr always uses the catalog (unless you do a "read metadata from file") your photos and the edits are safe and sound.
However, if you want to also save the metadata to file, go to the Catalog panel (just above the Folders panel) and select <All Photographs>. In the Grid View, press Ctrl / Cmd + A (letter A on your keyboard) to select all of your photos. Then press Ctrl / Cmd + S to save the metadata for all selected photos to file. **) This will make the metadata in the catalog and in the file identical - for the moment. As soon as you do further editing in Lr, the metadata in catalog and file will again be different (for the edited photos). Naturally you can repeat the Cmd / Ctrl + S process for the edited photos.
I have this in my workflow: As soon as I have edited a bunch of photos, or at the end of the day, I go to the Grid View, select all newly edited photos and do Ctrl + S.
There is also a feature in Catalog Settings / Metadata tab to <Automatically write changes to XMP>. But I would recommend not to check this box because (a) it causes a constant reloading of TIFFs and PSDs in the Develop Module which is not harmful but annoying; and (b) there is an old bug that causes to send the "metadata warning" message when this box is checked.
**) Depending on the number of photos in your catalog this can take quite a while.

TCP Socket connection in CLOSE_WAIT status and not getting closed

I am facing an issue with the TCP socket connections not getting closed and they are in CLOSE_WAIT status for ever.
As a part of batch process in our application, emails are sent with 4 embedded images. These images are downloaded from 3rd party site with IP say "UUU.XXX.YYY.ZZZ"
The images are embedded to email as follows
1. An URL object is created with the site url.
URL urlPhoto = new
URL("http://UUU.XXX.YYY.ZZZ/email/photos.jpg");
2.     The image cid is created with the URL object and the image name
HtmlEmail htmlEmail = new HtmlEmail();
String cid1 = htmlEmail.embed(urlPhoto,
"photo.jpg");
3.     The image cid is added to the email template by replacing the ${cid1} and the email is sent.
<td valign="top">
               <img src="cid:${cid1}" width="279" height="274">
          </td>
When a mail is sent, 4 new TCP connections are opened and are put in CLOSE_WAIT status for ever. For every mail sent 4 new connections are opened. In UNIX there is an upper limit on the number of open file handles (defaults to 1024) at any point of time. The open TCP connection has the underlying socket in CLOSE_WAIT status and is not getting closed at all. When the upper limit (1024) is reached the batch process is throwing the following exception and terminates.
Caused by: com.inet.tds.ap: java.net.SocketExceptionjava.net.SocketException: Too many open files
at com.inet.tds.am.a(Unknown Source)
at com.inet.tds.TdsDriver.a(Unknown Source)
at com.inet.tds.TdsDriver.connect(Unknown Source)
at java.sql.DriverManager.getConnection(DriverManager.java:525)
at java.sql.DriverManager.getConnection(DriverManager.java:171)
at com.hcomemea.batchprocess.dataaccess.database.BaseJdbcDao.openConnection(BaseJdbcDao.java:106)
... 12 more
When I run the command lsof in UNIX which list the open file handles in the system
$ /usr/sbin/lsof -p 22933 -i | grep CLOSE_WAIT
java 22933 build_master 297u IPv6 129841943 TCP integration.com:47929->UUU.XXX.YYY.ZZZ:http (CLOSE_WAIT)
java 22933 build_master 298u IPv6 129841947 TCP integration.com:47933->UUU.XXX.YYY.ZZZ:http (CLOSE_WAIT)
java 22933 build_master 299u IPv6 129841950 TCP integration.com:47936->UUU.XXX.YYY.ZZZ:http (CLOSE_WAIT)
java 22933 build_master 300u IPv6 129841970 TCP integration.com:47952->UUU.XXX.YYY.ZZZ:http (CLOSE_WAIT)
��list of 935 connections similarly�
I tried 2 solutions
1. Got the HttpURLConnection from the URL object and invoked disconnect method on the same. But it doesn�t work.
2. Ran the batch process java program with the parameter �Dhttp.keepAlive=false to close the underlying connection but didn�t help.
I need the underlying sockets to be closed and not put in CLOSE_WAIT status after sending the mail.
Is it the problem with the embed method of HtmlEmail object not closing the underlying socket connection.
If anyone has faced this issue before, kindly let me know the possible solutions for the same ASAP.
Thank you,
Ramesh G

This sounds more like a problem due to connection pooling at middle tier/application server.
If that has been ruled out, then you might to enable DCD or set expiry time on the server.

How can I minimise the file size of a greyscale image ?

Hi,
What methods are there for making as small as possible the file size of a greyscale image. I need to keep the resolution at 200pixels per inch. The image is going to be big, 5835mm wide and 1780mm tall ! Some of them have some fine soft detail so I need to keep an eye on how that degrades. Others are better.
Can the same work for colour images or are there different approaches for those ?
Thanks
Envirographics

My need is to enlarge up a plan for placement in, then tracing over in a CAD program, retaining the fine detail prior to tracing. I have some at 1/10th the full size item at 200ppi, others still as digital slr raw files. I have found that less than 200ppi the detail starts to go. considering this, if I am now working full size item surely I would need 200ppi also ? I could try simply enlarging it up 'as is' but would imagine when I am zoomed in that the ability to work closer in would be lost as I would be seeing great big pixels. Certainly taking an image currently raw and making it 200ppi and 5800 wide would give me better detail retention.
I had hoped for some suggestions on how to save at lesser colour or grey numbers than 256. Some scanning of large plans can for storage purposes use 17 colours for example. Do I need 256 shades of grey, can I save as 64 shades perhaps ? Certainly LZW is the right direction here, retaining detail but using compression. JPG compression starts to frogspawn the edges below quality 6, so losing detail again. What about png or gif, thats what I had hoped for. Does anyone know how to reduce colour palette numbers to 64 or 32 shades ?
Envirographics

Greyscale image not displaying properly.

This is my first post here, so greetings!
I am working in LabView 11, and all updates are current.
I am trying to display a greyscale image with five shades varying from black to white. (The shade corresponds to a voltage, this is used to control a piece of optical equipment.)
The image is incorrectly displaying only the black shade and the next shade up (on an 8-bit color scale, it is showing only 0 and 63). I am using "draw unflattened pixmap", and I'm passing to it a 2D array of 8-bit numbers (0, 63, 127, 191, 255) and a Greyscal color table that I created. Each value in the 2-D array that is 63 or greater is drawn on the picture as a shade of 63. I've checked to make sure that the input array does have values that range up to 255.
The mysterious part is that I am using the exact same process in another step of my VI, and it is working perfectly. Same color table, same type of array, and I'm doing it several hundred times in a loop. It has never failed even once to produce the correct image.
I've attached my code, and two of the sub-VI's that I call from it. The main code is "Adaptive Optics Experiment". You won't be able to run it, as it requires a software development kit for a company called Andor for some of the sub-VI's, but maybe just by looking you can detect an issue. I've noted on the block diagram where the problem occurs, and where the same process seems to work fine. It's in the large stacked sequence structure; the working part is in frame 1, non-working in frame 2.
I've also attached an image of the final picture that shows only two shades.
Any suggestions would be greatly appreciated!
Attachments:
Adaptive Optics Experiment.vi ‏88 KB
OptimumPhase.vi ‏14 KB
BuildPhaseMap.vi ‏18 KB

Hi mjpur,
Suggestion: Please check this link for better coding in LabVIEW
http://www.ni.com/newsletter/51735/en/
-Coming to problem:you said in sequence:1 it is working and it's not in 2nd sequence and you mentioned the color tables are also same.
-Now the only terminal looks connected is with data terminal which is coming from BuildPhaseMap.vi
-Please check if the data coming from Build Phase Map is proper or not.
Thanks
uday,
Please Mark the solution as accepted if your problem is solved and help author by clicking on kudoes
Certified LabVIEW Associate Developer (CLAD) Using LV13

Converting greyscale images to single spot colour

Hi there.
I’m trying to convert a greyscale image into a single spot colour image. The spot colour is PMS425C, a grey version but as I’m only printing 2 colours I need to convert these images into one spot colour.
Can somebody please assist?
Thanks

Did you see the monotone separated into cmyk? If so, you may not be making the PDF correctly and the spot is being converted. It can still have cmyk channels but they are empty and will not end up as plates. Check your output to PDF settings and make sure in the ink manager that spots are retained. Also, there is more than one way to view in output preview which can be confusing at first.
You should be exporting as PDF X/1a and if your settings are correct, when you view in output preview (separations) in Acrobat, you should see the spot as spot.
Try saving your monotone as .psd too many other formats will not support the monotone. If you view separations in ID, you will be able to see if your file actually supports spot colour.

Backups of raw and Jpeg images

I currently backup my iphoto library via time machine and keep a second copy of another USB HD. However the backup is the iphoto library, how do I back up the raw and jpeg images so that they are not within the library so that I could access them from a non apple pc?
I just would like the added security.
Thanks
Peter

You'll need to export them from the Library.
Select an Event or Album in the iPhoto Window and go File -> Export
In the resulting dialogue you have a number of options:
From the dropdown you can select the Kind to export:
Originals will get you exactly that: the original files. These will be the contents of the Event as per the iPhoto Window.
Current will get you the most recent versions of the files: a mix of edited and unedited pics. Again, the contents as per the iPhoto Window.
Tiff and Jpeg options allow you to export the current versions in those formats and you can the metadata - tiles, keywords, descriptions and locations - to the files on export.
PnG does not have the option to write the metadata as that format has very limited support for it.
There are other options for file size and naming and so on.
Regards
TD

Embedded Metadata Preservation and publication

Will Muse allow me to publish web pages in html5 that expose my metadata currently embedded in photographs cataloged Adobe LR?
We have populated the IPTC and IPTC Extension fields for our images with important metadata and do NOT want it stripped upon web publication.

Andrew:
What you describe is much like how Google Picasa Web Albums and Flickr "used to" do this. The original was stored "as-is" and the images that were downsized for preview and thumbnail were stripped of all metadata. After a number of users complained about this issue, they now preserve at least some of the embedded metadata for the previews and other derivative files. If I recall correctly, Flickr only preserves those values that are part of the older IPTC schema known as IIM or Information Interchange Model -- but this would mean that at minimum the owners copyright notice would remain intact (as well as caption/description, basic location information, credit and keywords).
While better than nothing, that's still going against principle five of the Embedded Metadata Manifesto, "Other metadata should only be removed from files by agreement with their copyright holders." (http://www.embeddedmetadata.org/embedded-metatdata-manifesto.php). Muse seems to ignore principals one through five in regards to all images except for the original!
Does the Muse system give any warning to users that the application is removing all the metadata from these derivative images? I would consider that to be the least that could be done. Then those that don't care about having additional potential "Orphan Works" floating out in public can continue. Those that do care about protecting their intellectual property can opt not to continue (until or if this is fixed).
Why doesn't Muse operate like the Save for Web & Devices (SFW&D) save option in Photoshop? It is part of the Adobe family right? The default with SFW&D will at least retain the creator and copyright notice, though the user can use the pull down menu to choose several other options including ALL. Talk to Alan Lilich (one of your Adobe Engineers) about how much overhead this really takes with most files. He and Dennis Walker from Camera Bits (makers of Photo Mechanic) both backed me up on this point when I presented findings from the SAA Survey of Stock Images at the Microsoft Pro Photo Summit in 2007 (Video summary of that presentation). Even for smaller files it's really not that exhorbitant. See point three in the "Metadata Myths" article at (http://www.controlledvocabulary.com/blog/top-metadata-myths.html) for details.
It's a real shame that you don't at least give the user the option of leveraging that embedded metadata already in the image by inserting it into an area around the image on the page. While having all embedded metadata appear automatically is an option, I'm sure that for some this would be annoying as they would have to then cut that copy from the page. However, is there a reason why there could not be a check book that the user can check to load this info into the Page text when the image is loaded? That would save a lot of opening the image in another application to gain access to the metadata (or going to Photoshop or Bridge and using File Info) -- then Copying and going back to the page to Paste in the info would take.
Many page layout programs for news operations automatically load the Contents of the Caption (Description) and Credit fields below an image when it's place into a layout. I don't see any reason why Muse couldn't adopt the same approach. Or at least have this as an "option" in the preferences for a user.
Should I log this as a "feature request"?
David

Why do 16 bit greyscale images look significantly worse than 32 bit?

Howdy,
I am trying to display a greyscale image from a camera. Parts of the program are written by someone else, and the image comes in as a U16 array. I am using IMAQ create and IMAQ arraytoimage. The image displays perfectly if I use the 'float' inputs on the above to sub vi's, but if I use 16 bit or 8 bit, the image quality is terrible. I would like to be able to display the image as 16bit.
If I save the 16 bit image, and reopen it with another program, it's still just as bad. I have also tried converting the array to I16, and U8, but it makes no difference to the image quality.
From what I understand, there should be very little visible difference between 8, 16 and 32 bit greyscale images. Does anyone have any ideas where the problem might be? my next guess is the camera settings, but I'd love it to be something in my code..
Cheers,
Andy

Andy,
Thank you for contacting National Instruments. The key thing to note is that the image data type that LabVIEW uses is a signed interpretation so you need to do some more conversion to get an Unsigned 16-bit array to display properly as an NI-IMAQ image. Refer to the Knowledge Base: 16-bit Images in NI-Vision for more information on how to do this. Thanks and have a great day.
Regards,
Mark T
Applications Engineering | National Instruments

Smart-Collection (metadata status) not updated immediately

Hi
I created a smart-collection that matches photos where their metadata status has changed on file system. So I changed the date with ExifToolGui (*click*). Closed the ExifTool and waited in LR 5.6 to see the smart-collection populated. But nothing happens. Photos only were added to this collection if I navigated to them in the library. Only the visible ones were added, so if I scrolled down, more photos were added. That's not really useful. And now, not even with navigating to them will put them in to that collection.
Other smart-collection for metadata changes in LR works like a charme.
Restarting LR doesn't help.
Windows 8.1 64bit
Does someone have an idea or can reproduce that behavior?

Try this:
- In the left-hand Catalog pane, select All Photographs.
- Do Edit > Select All to select all photos.
- Do Library > Find All Missing Photos.
When I had somewhat related issue with slow update of metadata status, that command seemed to sometimes speed it up.

Metadata Status and Greyscale Images

Similar Messages

Maybe you are looking for