Strange Artefacts in CRW Files

Hello everybody,
I made some raw images for texturing a 3D Model on a film set. As soon as I opened them in Photoshop or Bridge (tried MAc and windows) the images turned into strange looking colored ones with craaazy artefacts.Have a look... http://sebi.multimediaart.at/CRW_0005.CRW or  http://sebi.multimediaart.at/CRW_0020.CRW
Canon eos 300d
thanks
sebi

Sebi, that depends on when the raw files became corrupted.
Do you still have the raw files on the memory card? If so, it is possible
they are intact on the card, but somehow became corrupted during the
transfer process to your computer (or afterwards, after the copies were
already on your hard drive). You can try re-transferring them, e.g., using a
different cable and/or card reader, and re-opening the copies in Camera Raw.
If you already tossed the data on the memory card ... Do you have other
copies of these raw files (i.e., backups)? If so, try opening the backups in
Camera Raw and see if they're intact.
If this is the only copy of the raw data you have, then I'm afraid you're
out of luck.
I would suggest doing some tests with your camera, card, card reader, cable,
and computer to see where the corruption is coming from. That's the only way
to minimize the chances of it occurring again.
Eric
thanks for the fast answer.
that's right. irfanview is opening the image just in half of the solution and
just in 8bit.
Do you have any solution to fix those images? (i have about 70 of them)

Similar Messages

  • IMAQ spline interpolation shows strange artefacts

    Can someone explain the strange artefacts I see when using the IMAQ spline interpolation routine to resample an image? (See the 2 small attached files)
    Some pixels get very wrong colors. Is this due to the spline routine itself or is it maybe a bug?
    Certified LabVIEW Developer (CLD)
    Attachments:
    original.jpg ‏9 KB
    resampled.jpg ‏28 KB

    Thanks for the answer,
    Manu
    Certified LabVIEW Developer (CLD)

  • Canon PowerShot A2300 .CRW files are not recognised by CS6, Bridge, ACR7 - Workaround??

    I have enabled raw files on my Canon A2300 by loading up SDM (stereo data maker) scripting on the memory card, for the purpose of aerial photography (via kites and my small quadcopter). I now have nice big 16MP raw files that I cannot access on any software. Can anyone offer a workaround so that I can edit in ACR?
    I have tried renaming the extension to .CR2 and .jpg but that didn't work.
    Thanks

    I have just checked my .CRW files and realise that the display problem is not random, all .CRW images shot in portrait mode are displayed as landscape. This appears to be an Adobe issue and means that the helpdesk was right - PS CS6 does not fully support this type of Raw file.

  • Cannot Import .CRW Files from Canon S70

    I have imported thousands of RAW format photographs from my Canon 20D (.CR2) and 1Ds (TIF); however, none of the .CRW files from my Canon S70 will import. There is nothing wrong with the files themselves, as I can open them in Photoshop CS2 and Bridge. Specifically, I am using the option to import a copy and convert to .DNG. I have not tried any of the other import options. Has anyone experienced this or know how to get past this stumbling block.

    On a lark, I checked for updates in Adobe Bridge. It indicated that there was a RAW update available, so I installed it. Lo and behold, I was then able to import the .CRW files from my Canon S70.
    Can anyone explain this? Since I had CS2 installed well before ever installing Lightroom, is it possible that the presence of the RAW libraries that were already installed with CS2, prevented the installation of the newer RAW libraries when I installed Lightroom 1.0? And even so, what would be different - I was able to manipulate .CRW raw files in Bridge and CS2 before installing the latest raw update.

  • Problem with CRW files

    I just installed Aperture, changing from Photoshop Elements 4. But I have a problem with my .CRW files from my Canon Powershot S45 (RAW format). If I click on them, I get a glimps of a low resolution picture, but that is immediately replaced by the words "Unsupported Image Format" on a Mauve background. Fashionable color, no doubt, but not what I want to see at that moment.
    I can open the files in Adobe Elements 4.
    Aperture has no problems with the RAW .CR2 files from my Canon 350D.
    I ran the memory test program Rember and repaired file permissions, but all seems well.
    My system is an 2.1 GHz PowerPC G5 with 1.5 GB of RAM.
    Any ideas?
    Joop

    Thanks for the quick response people, most appreciated.
    I might indeed be out of luck: the S45 is not supported
    Re-importing the files did not work: managed or referenced.
    So I tried to export the file in different formats from PE, and I can use the .PSD format.
    So I am looking forward to an evening of converting....

  • A strange thing about saving files in Mac OS X

    I've noticed a strange thing about saving files in Mac OS X.
    In the save dialog, you click a folder to save into that folder.
    Well, if you accidentally click a file instead of a folder, the name of the document you're saving is changed to the name of that file! Then you have to retype the name, or cancel out of the process and start over.
    I don't see why you would want to change the name of the file you're saving to the name of a file that already exists, unless you want to overwrite the existing file (unlikely), but maybe there's a reason for this I'm overlooking.

    The Mac OS didn't used to do that. There must have been a lot of requests for it though. Especially from Windows switchers I would imagine, since you've always been able to do that in Windows.
    Sometimes I like being able to pick up the a name I do want to replace right from the Save dialogue. Most of the time though, I think it's a dangerous option. I don't know if there's a way to turn that behavior off.

  • Strange artefacts on 2nd monitor in kdm and while logging in

    Hello there,
    since about 2 weeks during a upgrade I've got  strange artefacts like it's shown in the attachet image when starting kdm and during login.
    I have have got nvidia geforce 8600 gt  with 2 monitors (17 & 22") configured as twinview and use latest stable kde 4.2.2.
    I have not looked excatly which package was updated when this problem appears but can it have sth to do with the updated  xorg server 1.6? For anny suggestions I would be galde how I can solve this problem or what the problem excat is... because this looks really ugly.
    Thanks for your help!
    Frank
    http://yfrog.com/76dsc00884j

    I have the same problem. The most strange thing is that when I logged to another installation where I'm using slim for login and when I come back to main installation with kdm, I saw scratched slim background. I think that is some problem with graphic card buffor or something like that because when I turn off the computer and turn on I don't see slim background when I'm logging using KDM. Unfortunetly I saw another artefacts
    I have only one monitor and I have nvidia gf 8800gt.

  • CRW file won't convert to DNG

    I added a CRW file shot in 2010 to the catalog, but the convert to DNG command is grayed out.  Why is LR refusing to convert?  Is there some other way to get it to convert?  Must i first export is as a tiff and then add that to the catalog and convert that to a DNG?

    I agree. I don't experience enough file size savings to be concerned. Also remember that any adjustments you make in Lightroom to any image regardless of whether it's the original raw file, the DNG, JPEG, or whatever, the underlying master image remains untouched. There's no need to create DNG just to preserve the integrity of the raw file. I think if you want to do different renderings of the same image you would do just as well to simply create a virtual copy of the original raw file and work on it. But that is your choice.
    Those who are in favor of the DNG format argue that it is an open format that will always be supported (at least by Adobe). There is some integrity checking that can be done. And, of course there is the reduced file size. There are other arguments as well, but I haven't really paid a lot of attention to them. Those who are strongly in favor of converting to DNG may suggest that I'm foolish. That may be true. But I'm content working with my original raw files.

  • Aperture stripping 8 pixels from Canon Digital Rebel CRW files?

    hi,
    I just wanted to see if anyone else was having the issue I am. I'm using Aperture with CRW files from a Digital Rebel, which are 3072x2048 in resolution. However, upon import into Aperture, images are listed as 3072x2040 in resolution. Exporting JPGs confirms that the images are only 2040 pixels in height. Converting the same RAW files in Photoshop results in images that are 2048 pixels in height.
    What happened to those 8 pixels? It is kind of a pain because the 3072x2040 files are now not exactly a 3:2 aspect ratio...

    yeah, I recognize that it's a very small "loss" of information, but it's just a little bit annoying because of the loss of the 3:2 aspect ratio. I just sent some of the 2040 images out for printing so hopefully there won't be an issue there.
    I noticed that the crop tool, when you tell it to use a 3:2 aspect ratio, will generate crops that aren't exactly 3:2 pixel-wise. Again, it's very close, but I just feel like there's no reason why it shouldn't be exact.
    Thanks for everyone's help! I guess I should start thinking about this as more of a "feature" than anything else...

  • Importing crw files to iphoto

    I've got some canon crw files on my pc - iphoto doesn't seem to recognise them - what's the best way to get the images into iphoto at as hi res as possible?

    sure there are tons of free and paid programs which let you convert them to other formats
    https://www.google.dk/search?q=file+extension&oq=file+extension&aqs=chrome..69i5 7j69i65j0l4.3196j0j7&sourceid=chrome&espv=210&es_sm=93&ie=UTF-8#es_sm=93&espv=21 0&q=convert%20crw%20to%20jpg

  • CS6: Strange Artefacts in 3D renders - what is causing this and how to fix it?

    Hi all
    I am creating 3D renders in PS CS6, and I am getting strange blocky artefacts in the renders. These appear on first pass and persist throughout the render. This has happened in the last 2 renders I have tried - I haven't used 3D for a while before this and I don't remember these before.
    By blocky artefacts I don't mean the JPG artefacts created by the forum's degrading of the uploaded image, but the light coloured rectangular blocks around the "s",
    On Win7x64 with latest PS CS6 update; NVidia 650M\2GB on a Core i7\8GB.
    The attached example follows a YouTube tutorial on creating long shadow icons.
    Any advice appreciated!
    Thanks
    Richard

    By the way, it might be helpful for you to show the steps that you followed to get to where you are. 
    What you're showing doesn't really look like a typical 3D rendering.  I'm assuming you sheared an extrusion to get that effect, because the type still looks face-on.  You must be viewing the object in Orthographic projection, because the diagonals don't converge.  Have you disabled all your light sources?
    Could you put the .psd file online somewhere for others to take a look at?
    This is what I'd expect a 3D extrusion to look like...
    I didn't use Photoshop 3D before Photoshop CS6, so I can't speak to the level of reorganization made, though I've read the same comments from others.
    -Noel

  • View Master mode strange behaviour with jpg files

    Hy all,
    I'm using Aperture, and I'm tweakin a lot the SW to discover all secrets ....
    I'm really concerned about a strange behaviour of the SW in view mode.
    If I open a jpg file, do not apply ANY modification, and apply the "show master" command (pressing M), there's a subtle behaviour :
    *the images get sharper !!!!*
    It behaves as if an "edge sharpening" was applied !!!!!!
    With _RAW files this thing doesn't happen at all._
    Even stranger, if I zoom to full definition (by pressing Z), and toggle between normal view and "show master" view, the immage remains the same !
    The effect is not so evident with all images, but sometimes it is !!
    Anyway, I expect not to have such kind of things with a professional SW.
    With professional cameras and good quality files it's really annoying not to beeing sure what's the REAL content of the jpg image.
    Has anyone noted this thing ? Is there a reasonable explanation ?
    The only one I tried to figure out is the following : may be Aperture applies some kind of resampling algorithm with jpg files (bicubic, bilinear, etc).
    May be this resampling is not applied with 100% magnification, as weel as with raw files.
    But it's only my guessing. Now, I'm tweaking other viewers and other SW to understand what's the real jpg image stored in the file : the blurer one form normal view or the sharper one with "show master" mode.
    I stress once again : of course, the jpg file I'm talking about have no settings at all, just imported and toggled with M button.
    Thanks in advance.
    Regards,
    Enzo

    Hy,
    I'm afraid I'm not been clear.
    The problem is this :
    1) jpg image opened in normal view mode, no zoom, (no quick preview, of course) : image with a certain amount of blour
    2) jpg image opened in show master mode, no zoom, (no quick previre, of course) : image SHARPER with respect with the previous.
    No edit applied from import, so "show master" command shouln't apply any change in rendering, should it ?
    The only thing I said on 100% view is that such difference (between normal mode e show mastermode) is not present with 100% magnification.
    That was the issue.
    Enzo

  • Strange Problem.. File to Idoc... RCVPOR is missing in control Records.

    Hi All,
    File to Idoc:
    Sender :
    Party : PT_ABC
    Business Service : BS_ABC
    Note : I provided the LS name(PARTABC) for BS_ABC Under Adapter Specific identifiers.
    Receiver :
    Business system (Without party) : BS_DEV_R/3
    In the IDOC receiver communication channel, I enabled the options
    -Apply COntrol records from Payload
    -Take sender from Payload
    -Take Receiver from Payload.
    Note : When i won't enable the above three options in IDoc RCV channel... Message is not processing and showing error as "Unable to convert the sender service BS_ABC to an ALE logical system..!"..
    File is picked and message processed and when i checked in SXMB_MONI,Idoc control records are showing clearly like below.
    - <EDI_DC40 SEGMENT="1">
      <TABNAM>EDI_DC40</TABNAM>
      <DIRECT>2</DIRECT>
      <IDOCTYP>ORDERS05</IDOCTYP>
      <CIMTYP>ORDERS05</CIMTYP>
      <MESTYP>ORDERS</MESTYP>
      <STDMES />
      <SNDPOR>SAPDPI</SNDPOR>
      <SNDPRT>LS</SNDPRT>
      <SNDPRN>PARTABC</SNDPRN>
      <RCVPOR>SAPDL1</RCVPOR>
      <RCVPRT>LS</RCVPRT>
      <RCVPRN>DEVSAP</RCVPRN>
      </EDI_DC40>
    But the Idoc is reached to R/3 with status '56' .And in the control records.. the receiver port (SAPDPI) is missing.
    I dunno what happened.When i cross checked, the remaining interfaces are working perfectly.
    Any idea whats going wrong?
    Regards
    Deepthi.

    As a matter of fact it is not strange at all:)
    It means you need to check the partner profile in the receiving r/3 system. This type of problem occurs because you need to define the partner profile PARTABC to the IDOC ORDERS05. If this association is missing you would always see the RCVPOR missing in the destination system.
    Also you have mentioned that "Note : When i won't enable the above three options in IDoc RCV channel... Message is not processing and showing error as "Unable to convert the sender service BS_ABC to an ALE logical system..!"..
    This is because for the BS_ABC sender service you must have a logical system associated; you can check the same by looking at the adapter specific identifiers. In your case I believe it is empty so the system can't find the logical system for it.
    Thanks
    Abinash

  • Strange characters when writing files

    I've made a program using a FileWriter. The program is coded and compiled on a Linux PC. I'm using the filewriter to dynamically write HTML-lines. I use "\r" to write returns. On my Linux PC and on my Windows XP sp2 laptop it works fine. On the PC of a friend it does not work correctly. It sees the "\r" as an unknown character. The browser also comments on that (illegal character). She also has Windows XP sp 2 installed running explorer 6. What could be the solution for this problem? Should I recompile on my friends PC? It is strange though. We use the same Java version (1.5).

    I don't know why you aren't using a print writer (with a println) method.
    Regardless with text files you will always find that they will render correctly on one system and not another because different systems have different line seperators and some software is pretty crappy when it comes to display and gets it's knickers in a knot when it sees line seperators it doesn't like. i.e. Notepad.

  • View of PDF file changes or looks strange when opening a file.

    Hi all,
    I have strange problem, that is haunting me.
    A PDF file is created from Microsoft Dynamics AX 2009 system. I guess that Microsoft have their own pdf-writer-engine.
    From time to time, we have seen that the PDF files, on some computers looks correct, on others gibberish.
    One user has a Win7 machine, 32-bit system. 4gb of memory. Today he opened a PDF file from the AX system. When He opened the file on his desktop., it looked fine. After 5 seconds. The entire view changed to strange signs and letters. I opened the same file on a Win-7, 64 bit machine. Everything looks allrigt.  Both of us have Adobe Reader 11.04 installed. one-two houes after the first error, he opened another PDF file. That started to look like gibberish, and after 5 seconds it looked allright.
    In general we only see these types of errors something like 1 out of a hundred times. Most common is that the view is gibberish from the beginning, and never changes.
    Any idea to solve this, will be much appriciated
    /Hector

    I think this is done by the browser when it is saving a temporary file and there's already a file with that exact name in the temp folder.

Maybe you are looking for