LV 8.0 PDA Image Depth Error

Attached is an 8-bit image. Why does the PDA Load Image File.vi in LV8.0 PocketPC module give me an image depth of 24 bit when its actually 8 bits?!!
This is a complete shows-stopper

Dear members.
I have tried to use load image file to but I can't load a 10KB JPG witch is expanded a 24bit 400x240 bitmap.
I always get the information that there is not enought memory available (Error code 2). If I try to use bmp
files of 288KB (3x400x240 = 288KB) there is no problem to load them.
Is there another explanation of this error? I am using Win CE 5 on a ARM based 300MHz Board with 32MB
FLASH and 32 MB RAM. The Kernel has a zize of 12MB and with this I have 11..20MB free RAM space.
The main problem is the huge amount for memory I need to load from the FLASH. This costs more than a
secound for such a BMP.
Is there a possibility that there is a missing kernel modul for the JPG uncompress or what does this error mean
exactly?
Yours with kind regards
Martin Kunze
With kind regards
Martin Kunze
KDI Digital Instrumentation.com
e-mail: [email protected]
Tel: +49 (0)441 9490852

Similar Messages

Filter plugin. Problem after change image depth.

Hi All !
I already wrote filter plugin it work fine but only for image depth 8bit, after i change image depth on 16 or 32 bits I getting error msg box from photoshop.
I try change on 'destination.colBits = 8' or 'destination.colBits = pChannel->depth' or ' (pChannel->bounds.bottom - pChannel->bounds.top) * pChannel->depth;' but all the same.
PixelMemoryDesc destination;
destination.data = data; //*pixel
destination.depth = pChannel->depth;
destination.rowBits = (pChannel->bounds.right - pChannel->bounds.left) * pChannel->depth;
destination.colBits = 8;
destination.bitOffset = 0 ;
Please help someone !
Very Thanks in Advance !
All code below:
// Gauss.cpp
// gauss
// Created by Dmitry Volkov on 30.12.14.
// Copyright (c) 2014 Automatic System Metering. All rights reserved.
#include "Gauss.h"
#include "GaussUI.h"
#include "FilterBigDocument.h"
#include <fstream>
using namespace std;
SPBasicSuite* sSPBasic = NULL;
FilterRecord* gFilterRecord = NULL;
PSChannelPortsSuite1* sPSChannelPortsSuite = NULL;
PSBufferSuite2* sPSBufferSuite64 = NULL;
int16* gResult = NULL;
void DoParameters ();
void DoPrepare ();
void DoStart ();
void DoFinish ();
void DoEffect();
void GaussianBlurEffect(ReadChannelDesc* pChannel, char* data);
void ReadLayerData(ReadChannelDesc* pChannel, char* pLayerData);
void WriteLayerData(ReadChannelDesc* pChannel, char* pLayerData);
DLLExport MACPASCAL void PluginMain(const int16 selector,
                                    FilterRecordPtr filterRecord,
                                    intptr_t * data,
                                    int16 * result)
    sSPBasic = filterRecord->sSPBasic;
    gFilterRecord = filterRecord;
    gResult = result;
    try {
            if (sSPBasic->AcquireSuite(kPSChannelPortsSuite,
                                               kPSChannelPortsSuiteVersion3,
                                               (const void **)&sPSChannelPortsSuite))
                *gResult = errPlugInHostInsufficient;
            if (sSPBasic->AcquireSuite( kPSBufferSuite,
                                               kPSBufferSuiteVersion2,
                                               (const void **)&sPSBufferSuite64))
                *gResult = errPlugInHostInsufficient;
            if (sPSChannelPortsSuite == NULL || sPSBufferSuite64 == NULL)
                *result = errPlugInHostInsufficient;
                return;
            switch (selector)
                case filterSelectorParameters:
                    DoParameters();
                    break;
                case filterSelectorPrepare:
                    DoPrepare();
                    break;
                case filterSelectorStart:
                    DoStart();
                    break;
                case filterSelectorFinish:
                    DoFinish();
                    break;
    catch (...)
        if (NULL != result)
            *result = -1;
void DoParameters ()
void DoPrepare ()
void DoStart ()
    if (*gResult == noErr)
        if (doUi())
            DoEffect();
void DoFinish ()
#define defColBits 8
void DoEffect()
    // Start with the first target composite channel
    ReadChannelDesc *pChannel = gFilterRecord->documentInfo->targetCompositeChannels;
    // Calculation width and height our filter window
    int32 width = pChannel->bounds.right - pChannel->bounds.left;
    int32 height = pChannel->bounds.bottom - pChannel->bounds.top;
    fstream logFile ("/Volumes/Macintosh Media/GaussLogFile.txt", ios::out);
    logFile << endl << "top " << pChannel->bounds.top;
    logFile << endl << "bottom " << pChannel->bounds.bottom;
    logFile << endl << "left " << pChannel->bounds.left;
    logFile << endl << "right " << pChannel->bounds.right;
    logFile << endl << "depth " << pChannel->depth;
    logFile << endl << "vRes " << gFilterRecord->documentInfo->vResolution;
    logFile << endl << "hRes " << gFilterRecord->documentInfo->hResolution;
    // Get a buffer to hold each channel as we process. Note we can using standart malloc(size_t) or operator new(size_t)
    // functions, but Adobe recommend sPSBufferSuite64->New() for memory allocation
    char *pLayerData = sPSBufferSuite64->New(NULL, width*height*pChannel->depth/8);
    if (pLayerData == NULL)
        return;
    // we may have a multichannel document
    if (pChannel == NULL)
        pChannel = gFilterRecord->documentInfo->alphaChannels;
    // Loop through each of the channels
    while (pChannel != NULL && *gResult == noErr)
        ReadLayerData(pChannel, pLayerData);
        GaussianBlurEffect(pChannel, pLayerData);
        WriteLayerData(pChannel, pLayerData);
        // off to the next channel
        pChannel = pChannel->next;
    pChannel = gFilterRecord->documentInfo->targetTransparency;
    // Delete pLayerData
    sPSBufferSuite64->Dispose((char**)&pLayerData);
void GaussianBlurEffect(ReadChannelDesc* pChannel, char *data)
    // Make sure Photoshop supports the Gaussian Blur operation
    Boolean supported;
    if (sPSChannelPortsSuite->SupportsOperation(PSChannelPortGaussianBlurFilter,
                                                &supported))
        return;
    if (!supported)
        return;
    // Set up a local rect for the size of our port
    VRect writeRect = pChannel->bounds;
    PIChannelPort inPort, outPort;
    // Photoshop will make us a new port and manage the memory for us
    if (sPSChannelPortsSuite->New(&inPort,
                                  &writeRect,
                                  pChannel->depth,
                                  true))
        return;
    if (sPSChannelPortsSuite->New(&outPort,
                                  &writeRect,
                                  pChannel->depth,
                                  true))
        return;
    // Set up a PixelMemoryDesc to tell how our channel data is layed out
    PixelMemoryDesc destination;
    destination.data = data; //*pixel
    destination.depth = pChannel->depth;
    destination.rowBits = (pChannel->bounds.right - pChannel->bounds.left) * pChannel->depth;
    destination.colBits = defColBits;
    destination.bitOffset = 0 ;
    // Write the current effect we have into this port
    if (sPSChannelPortsSuite->WritePixelsToBaseLevel(inPort,
                                                     &writeRect,
                                                     &destination))
        return;
    // Set up the paramaters for the Gaussian Blur
    PSGaussianBlurParameters gbp;
    int inRadius = 1;
    Fixed what = inRadius << 16;
    gbp.radius = what;
    gbp.padding = -1;
    sPSChannelPortsSuite->ApplyOperation(PSChannelPortGaussianBlurFilter,
                                                             inPort,
                                                             outPort,
                                                             NULL,
                                                             (void*)&gbp,
                                                             &writeRect);
    if (sPSChannelPortsSuite->ReadPixelsFromLevel(outPort,
                                                  0,
                                                  &writeRect,
                                                  &destination))
        return;
    // Delete the temp port in use
    sPSChannelPortsSuite->Dispose(&inPort);
    sPSChannelPortsSuite->Dispose(&outPort);
void ReadLayerData(ReadChannelDesc *pChannel, char *pLayerData)
    // Make sure there is something for me to read from
    Boolean canRead;
    if (pChannel == NULL)
        canRead = false;
    else if (pChannel->port == NULL)
        canRead = false;
    else if (sPSChannelPortsSuite->CanRead(pChannel->port, &canRead))
        // this function should not error, tell the host accordingly
        *gResult = errPlugInHostInsufficient;
        return;
    // if everything is still ok we will continue
    if (!canRead || pLayerData == NULL)
        return;
    // some local variables to play with
    VRect readRect = pChannel->bounds;
    PixelMemoryDesc destination;
    // set up the PixelMemoryDesc
    destination.data = pLayerData;
    destination.depth = pChannel->depth;
    destination.rowBits = pChannel->depth * (readRect.right - readRect.left);
    destination.colBits = defColBits;
    destination.bitOffset = 0 ;
    // Read this data into our buffer, you could check the read_rect to see if
    // you got everything you desired
    if (sPSChannelPortsSuite->ReadPixelsFromLevel(
                                                  pChannel->port,
                                                  0,
                                                  &readRect,
                                                  &destination))
        *gResult = errPlugInHostInsufficient;
        return;
void WriteLayerData(ReadChannelDesc *pChannel, char *pLayerData)
    Boolean canWrite = true;
    if (pChannel == NULL || pLayerData == NULL)
        canWrite = false;
    else if (pChannel->writePort == NULL)
        canWrite = false;
    else if (sPSChannelPortsSuite->CanWrite(pChannel->writePort, &canWrite))
        *gResult = errPlugInHostInsufficient;
        return;
    if (!canWrite)
        return;
    VRect writeRect = pChannel->bounds;
    PixelMemoryDesc destination;
    destination.data = pLayerData;
    destination.depth = pChannel->depth;
    destination.rowBits = pChannel->depth * (writeRect.right - writeRect.left); //HSIZE * pChannel->depth * gXFactor*2;
    destination.colBits = defColBits;
    destination.bitOffset = 0 ;
    if (sPSChannelPortsSuite->WritePixelsToBaseLevel(
                                                     pChannel->writePort,
                                                     &writeRect,
                                                     &destination))
        *gResult = errPlugInHostInsufficient;
        return;

Have you reviewed your code vs the Dissolve example? It is enabled for other bit depths as well.

How to display Image as Error instead of Error Message from Resource Bundle

hi,
I want to display images as error instead of error message from Application Properties in struts1.1
Ex:
I want to prompt a user to type password length min. of 6 char. If failed, need to show simple image as error rather
"Length should be min. 6".
reagrds
parthiban.

BalusC wrote:
RahulSharna wrote:
in the respective resource bundle modify the value by something was below
error.password.length=<img src="/images/password-Length.gif" alt="Password Length Issue" align="center"/>
OK, it apparently allows HTML in error messages.Yes struts allows it :)

Incompatible image size error

Hi,
I had a program that was working, and then made a copy of it to make some changes. The main change was to be able to put a BCG correction on the subtracted image. Now for some strange reason I get an Incompatible image size error. Can anyone help - also, if you could give me a suggestion soon that would be helpful as I have a deadline coming soon.
I suspect that I'm missing something obvious, but can't work out what it is.
Thanks for your help
Sam Whitehead
Attachments:
error.jpg ‏23 KB

Hi casualfanta,
I understand that you are using I-16 type greyscale images, but your screen capture does not include the BCG part. I am assuming you are using the IMAQ ColorBCGLookup VI even though you don't need colour, because the input for the IMAQ BCGLookup (no colour) is of U8 type.
If you are already using IMAQ ColorBCGLookup, then try using the IMAQ Cast Image VI to force a U32 type input and hopefully that'll solve the issue. Let me know if that helps!
Regards,
Imtiaz Chowdhury
Head of Digital Technologies
Brand786

Labview 6.0.2 patch does not remove my "image.cpp" error

I have an industrial PC with the following characteristics:
* Sharp LQ10D367 10.4" TFT screen, running a VGA driver (16 colours only option)
* ROBO 608, Industrial SBC motherboard with onboard video driver, from Chips and Technologies, 69000; 2MB onboard video memory
The standard VGA driver is the most recent driver, and in fact the only one available for this hardware.
Labview 5.1 runs without problem on this machine, but when I loaded Labview 6 (with the 6.0.2 patch) it came up with an "image.cpp error, line 4150" every time I tried adding a graph to the front panel. Changing the screen acceleration properties did not make any difference.
Though I have gone back to version 5.1
for the time being, my application would benefit substantially from the current version.
Are there any fixes for this, or is Labview 6 simply not compatible with VGA screen drivers?
Thanks,
Jo

I have LV6.0.2 running on an Arcom SBC with the Chips and Technology 69000
HiQVideo 2MB display chip. This chip is not capable of rendering 3D graphics.
I have noticed the CPU will go to 100% usage if I open a sub-VI panel with lots
of the new 3D graphics on it, as the display chip passes rendering off to the
main processor.
Perhaps you could try replacing the LV6 3D graphics with the older versions
that are available on the Controls pallet. At 16 colors the new graphics look
terrible anyway.
I am running the chip at 1024 X 768 screen resolution and 65K colors with
no other problems.
Regards,
Alan Brause
"Jo" wrote in message news:[email protected]..
> I have an industrial PC with the following characteristics:
>
> * Sharp LQ10D367 10.4" TFT screen, running a VGA driver (16 colours
> only option)
>
> * ROBO 608, Industrial SBC motherboard with onboard video driver,
> from Chips and Technologies, 69000; 2MB onboard video memory
>
> The standard VGA driver is the most recent driver, and in fact the
> only one available for this hardware.
>
> Labview 5.1 runs without problem on this machine, but when I loaded
> Labview 6 (with the 6.0.2 patch) it came up with an "image.cpp error,
> line 4150" every time I tried adding a graph to the front panel.
> Changing the screen acceleration properties did not make any
> difference.
>
> Though I have gone back to version 5.1 for the time being, my
> application would benefit substantially from the current version.
>
> Are there any fixes for this, or is Labview 6 simply not compatible
> with VGA screen drivers?
>
> Thanks,
> Jo

Failure: "image.cpp", error 11602

I'm developing an application in LabView and with the Web publishing tool I can visualizethe results in Internet. The problem is that I open the explorer (Netscape or Internet Explorer) the following message appears in the screen: "Failure, "image.cpp", error 11602, please contact with NI" and the explorer is close... It's labview 6.1

eddie wrote:
>
> I'm developing an application in LabView and with the Web publishing
> tool I can visualizethe results in Internet. The problem is that I
> open the explorer (Netscape or Internet Explorer) the following
> message appears in the screen: "Failure, "image.cpp", error 11602,
> please contact with NI" and the explorer is close... It's labview 6.1
A good general starting point is www.ni.com/failure . Worth looking at
the specific tips (if any) for this error, and the general tips.
Mark

Bad Image Data Error!

Hi,
I'm doing a project for a my class doing a simple sunrise/sunset program. I've noticed that if I either create simple images in fireworks and import them, or even images form the web, I get an error message saying "Bad Image Data Error!" and all the images turn to red squares.
Any ideas of how to fix this? I don't want to have create images in flash.
Thanks,
Avi

Oh and I forgot to add....I've experience this problem on both CS3 & CS4. Tried it on my desktop and laptop, both are Windows 7 64bit.

40D raw .CR2 files still causing 'Unsupported Image File' error

I have the most recent version of Leopard 10.5.1 and the newest version of Aperture 1.5.6 (2J2). Often times I open a RAW image shot with a Canon 40D (.cr2 file), I get the red screen "unsupported Image File" error message. Color mode is RGB. These were shot with RAW plus JPEG (not SRAW). It doesn't happen on every image shot at the same time in the same way, just some of the images. Can anyone advise why I would still be having this issue so long after Apple is offering 40D support? I've tried rebuilding my library data base to no success. I've tried reinstalling aperture. What next? Getting very frustrated, thanks!

hi, sazer01
sazer01 wrote:
I have the most recent version of Leopard 10.5.1 and the newest version of Aperture 1.5.6 (2J2). Often times I open a RAW image shot with a Canon 40D (.cr2 file), I get the red screen "unsupported Image File" error message. Color mode is RGB. These were shot with RAW plus JPEG (not SRAW).
I use Nikons and sometimes get a message like that. This might not be Aperture causing this. Blow out the connector holes on your memory cards and pins inside the cameras where the card connects. If the error is on the same frames all the time reformat your card a couple of times before using and make sure the card is seated properly. Don't turn off the camera immediately after taking the shot but let the camera finish the process of writing the photo frame onto the card.
Have you opened the frames in Preview to check if it see it?
victor

"Bad image format" error when displaying an image on Nokia 6600

I get a "bad image format" error when I try and display an image on a Nokia 6600 cellphone. The image displays correctly when I run it on the J2ME 2.1 Emulator, but gives an error on the phone. Plz help!!

More info please... what kind of an image are you trying to display?

What's with the occasional "Unsupported image format" errors?

I get this error randomly -- suddenly Aperture can't show me anything but a brief flash of the image, and then I get the maroon screen "Unsupported image format" error. Restarting Aperture returns things to normal. I've seen this in both version 1.5.6 and 2.
I can count on this occurring about every hour or so. This is quite frustrating. I use CR2 files almost exclusively, written from a Canon 5D.
Any ideas or workarounds for this behavior?

I was getting this all the time with 1.5, I have not seen it yet with 2. I think it's a memory thing, it happens more quickly if I am running Safari and other stuff. Sometimes quitting Aperture then starting again does the trick, more often shutting the machine down and rebooting clears it. I also have some very large tiff's in the library, Aperture can't (I've not tried it in 2 yet) cope with them, always the unsupported error message. These files are between 300mb to 1gig, sometimes it justs hangs on to the 300mb but mostly not. By the end of the day it was a real problem, I could only export images 2-3 at a time, if I tried to email 10 low res I would get either an out of memory warning or unsupported etc.
Something holds onto the memory somewhere either in Ap or Safari or all things running.
Kevin.

Unsupported image format error

Hey folks,
I've read several older threads on this topic and have not seen any new information. I am hoping there is a fix and someone out there knows it.
When I fired up aperture today I discovered that all of my images display with the dreaded unsupported image format error.
Thinking that my 215gb library had gotten too large, I tried to create a new library. Same result. When I import new images from my Canon 40D they show as a tiny preview and then quickly turn to the red message. It appears the raw files are not even imported into the library.... which made me think permissions. I repaired permissions and went so far as to set my ~/Photos/ to 777 ... still no dice.
I tried rebuilding my library - did not help
I have tried restoring from TimeMachine backup - no help
I deleted the plist and ~/Library/Application Support/Apreture - no help
I'm getting really worried that I have lost my library. I understand that the files are still there, but what about my edits and metadata. Seeing that this is a wide-spread issue is not helping my situation.
Any suggestions? Thanks in advance!

Good questions and thinking! I was vague about the chronology.
I first noticed the issue when I intended to import some images on my iMac which is home to my main 200+gb library. I never even got to the importing stage b/c I saw red, literally, when I launched the app.
I then created a new library and tried to import.
My final stage was to import onto the MBP, different machine, different library.
As for updates, I had applied the Dec. updates to the iMac but not the MBP.
While I know this will destroy my crediability as a troubleshooter (if you saw my images you'd know I have none as a photog ) I have realized that my Canon 40D somehow got switched into a custom mode during a few of the shots causing it to go into Canon's sRAW. I think that accounts for the behavior of the imported images on the MBP. It does not, however, account for my entire library turning red on the iMac.

Image.cpp error

When I try to print the labview panel & diagram on my new canpn pixma iP1000 printer I get the following message. I am using LV6.0
"image.cpp error" in line 11035. Please contact ni.com. Anyone can help!

hi labview 1958,
please look here:
Failure: image.cpp, line 11035 in LabVIEW 6.0
Greets!

Image Verification Error

My client has been reportng issues to me about when some people try to submit an application on their site that they recieve the error message "Image Verification Error". I had submitted a ticket to BC about this and was informed that there was some javascript causing this issue. I have gone through this page and removed any javascript that is not essential for that page hoping to fix the problem, but I was informed yesterday that they recieved some emails saying the same thing. So I am hoping someone else who has had this issue may have an answer.
Here is a link:
http://www.americanavc.com/Apply-Online?RefNumber=H-PHX1008&Position=IMMEDIATE%20-%20Hotel %20Audio%20Visual%20Technical%20Coordinator%20%28Phoenix%29
Any help you can provide would be appreciated.
Thank You

I found when testing the image capture, if you mis-enter the image verification details and submit; you correctly receive an "incorrect verification error".
However, when you hit the back button and re-enter the characters correctly, it still shows the same "incorrect verification error".
I'd be interested too if there's a known issue and a fix?
I am aware there is a new image captcha coming soon.
http://forums.adobe.com/message/4811786#4811786
Regards
Mike

Image file error

i get a 'image file error' when i connect my n8 to my pc. what is the problem?

Then the file is corrupted. Can you open the file on the N8? Change fileformat to .jpg.
‡Thank you for hitting the Blue/Green Star button‡
N8-00 RM 596 V:111.030.0609; E71-1(05) RM 346 V: 500.21.009

"Unsupported Image Format" error ONLY on exposures longer than 4 minutes

When importing my photos to Aperture, I get an "Unsupported Image Format" error, but ONLY on images where my shutter was open for longer than 3 minutes or so. I'm looking at Aperture right now, and I've got one shot that was 184 seconds long - no problem. Next shot, 240 seconds - ERROR. I shoot everything in RAW and have no trouble with any of my "normal" exposure shots - thousands of them. Error shows up only with the shots where I've locked the shutter open for more than 4 minutes.
What the heck is up? I'm *assuming* it's a problem with Digital Camera RAW in OSX, as Preview.app is also unable to display the image. Photoshop CS6 and Lightroom 4 have no trouble with these images. Even in Aperture, I see a low-res preview of these "error" images for about two seconds before the error message replaces it.
Aperture 3.4.5
Digital Camera RAW 4.07
Nikon D600 (latest firmware) shooting .NEF RAW files, all images imported directly into Aperture from SD card in computer's slot
OSX 10.8.4

This problem, unsupported image format for long exposures, has been reported on and off for some time now.
Its not an easy search to phrase but for example I found this Aperture 3 will not recognize RAW files obtained from long ... at dpreview from a while back.
Sorry to say there are no resolutions that I can find. You might want to try and get in touch with Apple. They don;t make it easy to get software support even on there 'pro apps' but if you start with the normal Mac support number you might get to someone who can help.
Additionally you can leave feedback by going to Aperture->Provide Aperture Feedback. There is a setting to report bugs.
Sorry I don;t have anything better to report.
good luck, post back if you find out anything
regards

LV 8.0 PDA Image Depth Error

Similar Messages

Maybe you are looking for