LabVIEW 8.2 Image Display bug

Hi all,
Description : Trying to create a constant by right
clicking on an image display (controls palette > vision > image
display) causes labview to crash.
LV
version : 8.20 only, didn’t exist in 8.0.1 and earlier !
Same bugg happens:
with image display (classic),
when trying to create a constant from a
local variable of these indicators,
when trying to create a constant on the
connector of a subVI for these indicators.
Message Edité par TiTou le 10-23-2006 08:38 AM
When my feet touch the ground each morning the devil thinks "bloody hell... He's up again!"
Attachments:
bugg_image_display.png ‏234 KB

Hello,
Thank you for reporting this. A CAR has been filed on the issue - for reference the CAR ID is 4308NMSQ.
Best Regards,
JLS
Standard Response:
This was reported to R&D (4308NMSQ CAR ID) for further investigation. Thanks for the feedback!
Best,
JLS
Sixclear

Similar Messages

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.)

Is this a bug of Outlook 2007 about images displaying in signature?

I've done many tests and researched on website or MS KB. But still got no solution.
My issue is:
I make a signature with images linking from website which can be easily accessed.
I setup this signature in Outlook 2007, when I compose a new mail, and choose the signature I set. It won't show the images with a high percentage rate, meanwhile, I try to get into "Signature"-"Signature...",
Outlook2007 gets stuck, then you can not close Outlook or open Internet Explorer unless you kill the process of OUTLOOK.exe.
1. Test are done under a clean XP system and Office 2007 standard fresh installed. Also there are some other staffs who help me test the signature that report the same issue on Office 2007.
2. Images are rendered in 96dpi. They are all in very small size stored on website, can be easily accessed without network connctivity problem.
3. The signature is made by simple HTML language not by Outlook signature setup wizard. but in this case, you can ignore which method I use to create the signature. The images in signature can be displayed well in Outlook 2003 &
2010. Also I have tried insert images using "link to file" in Outlook signature setup wizard, got same issue.
4. Don't suggest me to store the images locally. These images should be updated after a period. You can not ask the company staffs to update these images manually by themselves. and even if the images are stored locally, the images won't be shown
in Outlook 2007 with a high percentage rate.
5. I've tried setup signature with or without an account profile, got same issue.
6. I 've tried without an accout profile, just copy the signature file to Outlook signature folder, unplug the network cable, and "new mail" then load the signature, of course, the images won't be shown because network connection doesn't exist,
and then when I try to get into "Signature"-"Signature...", the Outlook interface also gets stuck. So I think Outlook 2007 may have some problem on detecting the network connectivity.
7. It is not possible to upgrate the version of Office. Since Office 2007 isn't out of date and is powerful enough for us, no one want to pay more money just to avoid this issue.
I don't know why I cannot upload a screenshot for troubleshooting. If needed. I can send a mail with screenshot attached.
So far to now, I still get no solution, I think this is a bug of Outlook 2007, because the same signature, there is no problem on Outlook 2003 & 2010. Hope someone of MS staff can see this article and report to technical support center.
I would appriciate anyone's kindly help but please consider that you understand what I am talking about. I don't want to waste time for each of us.
thanks in advanced.

What kind of problem about the display image in signature?
How do you add the image into the message body when you send the message?
Does it show correct through Web-based access?
Outlook 2007 doesn't support some of Style Element, you may reference the link as below:
http://www.campaignmonitor.com/css/
Thanks.
Tony Chen
TechNet Community Support
Thanks for your reply, I know that some Style Elements won't be supported in Outlook, but this is not the reason.
Please refer to my post previously, I post it but get no response.
http://social.technet.microsoft.com/Forums/office/en-US/481170b1-f23f-4d46-9914-823326491846/is-this-a-bug-of-outlook-2007-about-images-displaying-in-signature?forum=outlook

Need to get rid of flicker in between image displays--the PC in which LabVIEW 8.2 is installed is routing images via LaVIEW code & 'extended desktop' to typical visual projector and between each image display is a flicker--that we need to remove

Need to get rid of flicker in between image displays--the PC on which LabVIEW 8.2 is installed is routing images via LabVIEW code & 'extended desktop' to a typical visual projector and between each image display is a flicker--that we need to remove
Attachments:
Get JPEG Files in the folder.vi ‏13 KB
Display image on the screen.vi ‏34 KB
Create image file path.vi ‏12 KB

In response to below------Thank you Lynn-----Yes, there is a main panel--I will attach----and if you have any further suggestions please let me know--Thanks again
How are you running this program? Is there a top level vi which calls the ones you posted? The Display image on screen.vi will display two images in succession, but according to the note on the block diagram the second image is blank. It seems as though this would intentionally create a flicker.
The sequence structure is unnecessary. Dataflow will determine the order of execution. The only exception is the time delay in the third frame. Since it has no data dependency, a single frame sequence may be useful to assure that the delay occurs before the picture is updated. A simple state machine might be a more versatile architecture for what you may be trying to do.
It is not necessary to write the FR.PanelBounds property immediately after reading it, nor is it necessary to read it a second time in the second frame. Just wire from the first read.
Lynn
Attachments:
Main Front Panel with Rendv Final Nov 6 with pause.vi ‏755 KB

Is there a way to turn the pattern matching example in Labview to instead of loading a rectangle around what you want the template to be you can use an image display , I've be trying and can get no where with it

What I want to do is , have two images on image displays and the pass them through the same setup as the pattern matching example to get the number of matches , I have attached what I have done and also given the pattern matching example program as well.
Hope to get answers back soon,
Thanks Alan
Attachments:
screenshot.docx ‏48 KB
Pattern Matching Example.vi ‏100 KB

Hi there!
The example used can be adapted for comparing two images, however the algorithm and coding for finding the differences is more specific to your actual problem. In terms of the loading and displaying of the images, this can be done in the same way.
Once you have some sort of algorithm, then you can automate the learning and matching by simply wiring them in order. (in the example, these are put in case structures as they are waiting on response from the front panel)
I hope that this helps,
Liam A.
National Instruments
Applications Engineer

Using Data Socket with LabView 7 Image Display

I want to to connect the Image Display over the Data Socket, but its not working?

Please be more specific. How are you trying to connect to the datasocket. is it over a network. same PC.
Joe.
"NOTHING IS EVER EASY"

Image display control scrolling does not work properly when zoomed in

I am using a ROI on an image in the image display control. When zooming into the image to fine-adjust the positioning of the ROI, the image scrolling does not work properly. As far as I understand, the image should scroll automatically when the ROI is leaving the visible area. However, the scrolling behaviour seems to depend on the origin of the Labview panel, not the origin of the image display control, which might require to move the ROI way out of the visible area before the scrolling takes place. In other words: the coordinate system of the image display control is shifted with respect to the true visible image area, depending on where you place it on the front panel. As a consequence, when clicking on a ROI which is in the visible area, but is outside of what Labview thinks is the visible area, it might immediately jump to the left border of the image, making the positioning of the ROI really difficult.
Has anyone noticed this behaviour, and what would be a reliable solution to avoid this?
Dirk

Hello,
no, I am not talking about the tools palette. Just place an image control with some image in it on a new VI front panel. Then, use the rectangle from the tools and select a ROI in the image. If you zoom in (using the magnification glass), and then grab the ROI and move it around, the image scroll with the ROI. So far, so good. If you now place the image control elsewhere on the panel, or add new control above it, resize the panel, etc. , this scrolling when moving the ROI will not work correctly if the origin (0,0) of the panel is far away from the image control.
I have attached a VI for simplicity (although there is hardly any code in it).
If you make a ROI and try to move it down, you will notice that scrolling starts if you move the mouse out to about 10cms below the image (depens on your screen, of course). After that, if you click on the ROI, the scroll bars and ROI might jump up to the upper end of the image. Imagine how annoying this is if you try to finely adjust the ROI position.
I think it is a bug in the implementation of the image display control.
Thanks,
Dirk
Attachments:
scrolling.vi ‏818 KB

Image Display got rotten (really: the Indicator, not the Image!)

I'd like to hear comments on the following VI, containing just a single Image Display Indicator, which, for some reason got corrupted during porting across LV versions and resizing. By divide and conquer I found that it was the origin of pretty odd problems that I was observing in a complex VI: absence of front panel updates, pull down menues not displayed, actions needing a double press of buttons, and so on.
The VI is saved from LV2012 windows, also attached as saved for 8.5. Just opening it, on 2 installation of Labview, I turn labview into something responding oddily. (try to pull down a menu, e.g.). Linux LV seems not to suffer from it, maybe because it places a nonfunctional FP placeholder for this control, without trying to cope with its nonfunctionality.
The question is perhaps, why LV doesn't detect the problem and behaves so weirdly with it -- bug?
Enrico
Attachments:
BadImage.vi ‏34 KB
BadImage85.vi ‏36 KB

Yes, I was able to see this trouble as well. Checked in different versions (2010 and 2012 x86/x64). But was unable to re-create this VI from scratch. It seems to be that Vision Control was broken in customization attempt where cluster with buttons was rearranged from vertical to horizontal position (may be in combination with saving for previous LabVIEW version).
Time to time I do the same (for example save VI with vision controls from v. 8.6 to 7.1) and I've got lot of situations when "downgraded" VI cannot be opened or caused just crash, or broken. Something is wrong.
Quick and dirty analysis of the given "BadImage.vi" shows that the problem with refreshing is present. LabVIEW tries to refresh this control continuously.
In Process Explorer we can see one thread with 100% CPU load (overall 20-25 percent, because I have 4 CPUs):
In Call Stack we may see DrawImageControl function which is called from niviswnd.dll.
Well, load this stuff into debugger, set breakpoint and see - this function called continuously:
called somewhere from SetPIClusterPartSize from LabVIEW.
I don't want to go deeper into call chain analysis (anyway makes no sense without source), but short walking in debugger shows that messages continuously fired:
Check it with Spy:
There are thousands WM_PAINT messages which continuously sent to the Window with this weird control. Looks like attempts for update, but due some internals errors this called again and again.
The messages queue is full with WM_PAINT - therefore LabVIEW is "unresponsive" - context menus cannot be shown, dialogs cannot be closed, slow reaction, etc.
Sorry for slightly off-topic above, but may be this will be helpful for NI's engineers for further investigation.
Andrey.

Image display reference control still not working

Has anyone looked at the Image Display referece control bug? I still can't pass an image display reference to a sub VI since the front panel control in the subVI generates this error:
"The control requires an external library for its operation. This library is not installed, is not installed to the correct location, or is not loadable, or the library's version is not high enough."
I know there's some cludgy ways around it (passing panel reference, demoting reference class to 'control' and back), but it seems like such a simple thing to fix that would already have been fixed unless no one's working on it.
Attachments:
ImageRefError.vi ‏37 KB

Hello eaolson,
Unfortunately, this bug (CAR# 3R1F8KRJ) has not been fixed in LabVIEW 8.5. The attached VIs, however, do provide a workaround. The main VI contains an Image control. The sub VI has a Generic Control Reference Input to which the Image Control Reference is wired. In the sub VI, a "to more specific class" function is used to get the full properties list for an Imagecontrol.
Please note that, according to R&D, this workaround is ineffective when built into an executable.
I apologize for the inconvenience this bug may cause. We are aware of the issue and working to resolve the problem.
Best Regards,
T. McCarty
Attachments:
Main.vi ‏40 KB
sub.vi ‏10 KB

Photoshop CS4 Menu toolbar display bug and fullscreen slowness...

http://img384.imageshack.us/img384/8202/menutoolsbugee3.gif
I'm having a display bug with the menu toolbar in Photoshop CS4 Extended. Notice the area of tools is gone and replaced by random pixels? This happens whenever I enter the fullscreen mode that hides the interface. And when I exit that fullscreen mode, that bug appears and doesn't fix itself until I restart Photoshop. Can this be fixed?
Image view rotation also happens much slower than normal in that fullscreen mode when interface is hidden. But performs normally after I bring back the interface.
I'm on WinXP, Athlon 64 4000+, 3GB ram, GeForce 6800 GT video card [driver 169.21]. I'm not sure if this is a video driver bug or CS4 bug.

Yeah, Dave, I can understand how that can happen. I've seen that sort of weirdness when I've seriously overtaxed my hardware.
 
 Had way too much running all at once yesterday, switched over to Firefox, and clicking on folders in the Bookmarks bar, I had 4 bookmark/folder menus dropped simultaneously.
 
 I managed to grab a screenshot with 2 of them showing, but man! You shoulda seen it with 4!
 
 I ESC'ed out, quit GarageBand (had a song project of several hundred MB going) and all was fixed.
 
 
<a href="http://www.pixentral.com/show.php?picture=1oV3eLGID1UYwZ4L5Y0n44ThA0Ab0" /></a>
<img alt="Picture hosted by Pixentral" src="http://www.pixentral.com/hosted/1oV3eLGID1UYwZ4L5Y0n44ThA0Ab0_thumb.png" border="0" />

Why does moving the mouse over an IMAQ image display slow the GUI down so much?

I have a large application with several vi's running simultaneously under labview 8.6.1. When I mouse over an image display control in one of the vi's, everything slows down a shocking amount in all the other vi's. The windows task manager does not show a large increase in CPU use. My pc is has a quad cpu with 4GB of RAM, and the CPU and memory loads do not appear to be terribly taxing to the system. However, many of my vi's apparently come almost to a standstill if I just move the mouse in a circle around my image control.
This looks like it is largely a GUI display issue. If I make a new vi and put a while loop in it that only displays the iteration loop number to an indicator, I can see the iterating occurring, then stopping totally when I mouse inside the image display control. When I stop moving the mouse inside the control, or when I move it outside the control, the interation loop number jumps up, as if it had been incrementing behind the scenes the whole time. So only display of the interating was halted.
This problem occurs even if the vi with the image control is not executing. If the vi with the image control is open but not running, and I mouse over the image on it, the other guis all come to a screeching halt.
Does mousing in the image display control really utterly crush all other guis in all other labview windows? Is this an issue inherent to the image display control? If so, is there anything I can do about this?
Also, this issue is not entirely limited to display. I started looking at it in greater detail because this issue also exposed what I think is a race condition in my code. I have a vi that acquires an image from a ccd and puts it into an IMAQ image.ctl. This image then gets passed up to a vi up the call chain, and is put on a queue and sent over to be de-queued by a vi that has the image display control. Here's the kicker: when I mouse over the image display control, the image successfully gets acquired inside the subvi, and if I probe the wire leading to the output IMAQ image display.ctl, I see the image. If I simultaneously probe the wire coming out of the subvi one level up the call chain, the image gets lost about half the time. This only happens if I am mousing in the image display control IN A TOTALLY DIFFERENT AND SEPARATE VI. If I bump up the priority of the ccd image acquisition vi to 'highest priority', the problem only happens about 1% of the time, and I really have to mouse around to make it happen. Still, it's disturbing that mousing in the GUI in one window results in a failure of a separate subvi to simply pass an image up the call chain. I understand that IMAQ images are referenced rather than passed by value, but I don't see why there should be a failure to pass the image up the call chain. I've looked for a race condition, but can't find one.
Eric

I have finally been able to replicate the behavior that you are seeing on another computer once the image was large enough. Here are a few notes about this behavior:
First. The UI only slows down when the images are large, 16 bit images. The reason why this is unique to 16 bit images is that they can only be displayed on the front panel as 8 bit images. The workaround that Weiyuan suggested to change the 16 bit display mapping hints towards the root of the problem...that any time a mouse runs over the indicator, Windows asks the entire image to re-draw (having a separate indicator overlapping the image will create the same behavior). With a 16 bit image, not only does the image have to re-draw on the screen but the 16 bit pixels need to be mapped to 8 bits. When setting the 16 bit display mapping to Full Dynamic, this requires mor computation/pixel than 90% dynamic or one of the other mapping schemes.
This is expected behavior if your program is running and you're trying to display a large 16 bit image. To fix this behavior there are a couple options:
Change the 16 bit display mapping to something other than full dynamic. You can choose which 8 bits to display or if you want to map the bits.
Resize the image just for viewing purposes on your front panel (since you aren't going to view every single pixel of you image on the screen). You can use the IMAQ Resample.vi to do this. This will allow you to take your 1500x1500 pixel image and only display a 500x500 pixel version.
If you are interested in viewing small details of the large image, consider just displaying a smaller region of interest at a time.
Let me know if any of these solutions work for you. Good luck on your application.
Zach C.
Field Engineer
Greater Los Angeles

Flickering problem with live viewing with IMAQ Image Display

Hi everyone,
I am trying to write a program to do live imaging with Andor camera. I am using some examples from Andor. The images are acquired in sequence and send into IMAQ Image Display and also Intensity Graph. There is minimal flickering issue in the Intensity Graph but there is very bad flickering problem in IMAQ Image Display. Perhaps I misunderstand how to optimize the vision tools. Does anyone know how to overcome this issue? I have attached the code that I am testing. Thanks in advance.
Best regards,
Han Yen
Solved!
Go to Solution.
Attachments:
iXonRTA_live_0.0.1.vi ‏70 KB

You can use Vision Assistant to test our vision functions. Vision Assistant is really meant to prototype - it does not have all teh functionality of Vision Development Module and is not as flexible as we don't allow you access to all the settings for every function.
I recommend starting in Vision Assistant and then porting over to LabVIEW or C (whatever you are most comfortable with)...this is built-in functionality. There is nothing wrong with using Vision Assistant to do live imaging, just that you run into limitations and you will only be able to use this code on computers that have Vision Assistant.
Hope this helps.
--Michelle
Instrument Control R&D
National Instruments
Instrument Control
Machine Vision

Image display scroll bar

Hi All,
I am using two "Image displays" in my IMAQ vision system. One is for the original image and the other is for the image after it has been manipulated. I would like to connect the scroll bars from each display to move as one. Anyone have any idea how to do this?
Don

Here is a present from Santa. It is in LV 8.0. Enjoy
Matthew Fitzsimons
Certified LabVIEW Architect
LabVIEW 6.1 ... 2013, LVOOP, GOOP, TestStand, DAQ, and Vison
Attachments:
IMAQtrackImages.vi ‏62 KB

When I buid an application, the vision image display is black.

Hello !
I have made an application using "vision image display". I have labview 7 express and vision builder 6.0. On labview, my application run very well and my image is displayed.
I create an application with application builder 7 and I run it on a client computer with labview runtime engine 7.0 and IMAQ Vision 6.0 run-time engine. And my image is never displayed but stay black.
Why ?

Hello,
I have a few questions concerning the problem. Where does the image come from, is it read in or is it from the harddisk. When the image is read in, which hardware do you use? I think you taked off the lens aperture and checked the contrast!? Check if the "vision image display" is correct licensed. Which Version is used from the "vision image display"? You can also check, when there is used any hardware if the drivers are the same on both systems. The current version is 2.6. With your answers, we should get a solution for the problem.
ThomasD

Multiple image displays

Hi,
I plugged 2 USB3.0 cameras in LabVIEW, and displayed the images from both in the front panel seperately. One image display corresponds to one camera source. When I run the codes, the display windows are supposed to show separate image grabbed by the corresonding camera. However, the displays windows sometimes show the same image source from one camera and they are not stable. I guess the signals from both cameras are mixed sometimes. I have no idea how to solve this problem.Has anyone met with the same problem before?
Also, I'd like to confirm my calcultion of bandwidth. I want to plug 6 USB3.0 cameras in total eventually. They will all be set the same with resolution 1024x1280, mono8. The bandwidth of USB3.0 is 625 MB/s. Thus, the calculatin of maximum frame rate for each camera the setup could handle should be:
maximum frame rate = 625M / (1280 x 1024 x 6) = 79.4 fps. Is this right?
Thanks,
Olivia
Solved!
Go to Solution.

Hi,
I attached my vi. file here.
Thanks,
Olivia
Attachments:
double_camera.vi ‏85 KB

LabVIEW 8.2 Image Display bug

Similar Messages

Maybe you are looking for