Unsupported Image Format w/ Photoshop

For the past couple of weeks when I try to edit Canon Raw files (.CR2 from a 5D Mark II camera) using Photoshop CS5, the process is extremely slow and most of the time it does not even work. Here is the error message I receive when it does not work:
"This image cannot be rendered for editing because Aperture does not support the image format."
However, I have had a few shoots where some of the files can be edited in Photoshop and others from the same shoot give me the message above.
My workaround has been to export TIF files, edit them in Photoshop, then import them back into Aperture. Obviously this is a pain. Any suggestions?
Thanks!
Dan

Have you tried the Troubleshooting Basics found here:
http://support.apple.com/kb/HT3805

Similar Messages

  • Unsupported image format after Photoshop

    I recently upgraded to 3.4.5, and now after taking images to Photoshop for editing they come back into Aperture with an "unsupported image format" exclamation mark screen. I need to be able to open images in PS5 and close them without this glitch...I have tried all the typical fixes, so please don't suggest that I rebuild my library, etc. Please help! I have clients who need me to edit their images this week...
    Many thanks!

    Hi Léonie,
    Thanks for your quick response!
    Here are some answers...
    I am on CS5, I have been on iOS 10.7.5 for some time now, and Aperture 3.4.5. I upgraded Aperture from the most recent - I always keep up-to-date on the periodic updates...so I guess that was 3.4.? - I have not skipped any upgrades.
    I am exporting into photoshop as a 16bit PSD. My originals are managed. Not sure what you mean by file export settings in PS...I have chosen maximize PSD and PSB file compatibility as "Always".
    I have tried repairing permissions, repairing the database and rebuilding the database. I have also temporarily trashed my prefs file to see if that would make a difference. None of the above have made any difference. I may try TimeMachine next to go back to the previous version of Aperture...
    When I import a PSD file from my desktop, it brings it into Aperture, and shows a preview properly, but when I then try to open that PSD file from Aperture into Photoshop, it flattens it and none of my layers have been preserved.
    Thanks very much!
    Lori

  • Unsupported Image Format after opening a file in Photoshop.

    As from today,I am getting an unsupported Image Format after opening a file in Photoshop. I have made nothing more than as crop on the image. Why?

    Ernie, I misread your post indeed. I never saw a option to send RAW files to an external editor. All I can see is the option to chose what editor and then specify if PSD or TIFF is used. I always use PSD, usually 16bit and in one other installation in 8bit (due to RAM restrictions there).
    So Aperture creates the PSD version and PS edits that very version and saves it back into aperture. This is where I sometimes () get that "unsupported image" problem.
    I think this also is what Mike does: select a RAW master, use an external editor -> Aperture creates a PSD or TIFF. I haven't tried the TIFF option , though.
    My main point was: it all worked for a very long time and with the latest updates it is broken.
    have a good day.
    Roland

  • "Unsupported Image Format" in Aperture after editing in Photoshop?

    I've had random intermittent problems with some files that I store in Aperture (I'm on 3.4.3) and then edit in Photoshop.  I shoot only in RAW format on a Nikon D300 (.NEF files), and the images import fine.  Some of the images I edit in Photoshop CS6.  Upon saving the image in CS6 and returning to Aperture, I get a black preview image with a silver warning triangle, and it says "Unsupported Image Format".  The info tab shows me that the image is a .tiff file as I expect - and what's odd is when I re-import these images from the folder they're stored in, they display fine as expected.
    What gives?

    All good questions, thank you for asking.
    - Aperture is set up to export to 8-bit TIFF files.
    - Photoshop is set as my external editor.
    - To edit an image, when I'm in Aperture I right click on the image and select "Edit with Adobe Photoshop CS6"
    - I don't use Layers in Photoshop, so when the image is returned to Aperture there's only the background layer.
    - The images are saved in PS using "Save", not "Save As".
    - I verified that the file names are .tiff rather than .tif
    That is exactly what I am doing, when editing my Canon Raws in PS-CS6, and there is no problem with unsupported image formats. that should work!
    and what's odd is when I re-import these images from the folder they're stored in, they display fine as expected.
    Where is this folder? Are the images referenced? And if referenced, are they on an external drive? How is the drive connected and formatted?

  • B&W - Unsupported Image Format

    Aperture continues to misbehave. I scan B&W photos in using VueScan software and a Canon flatbed scanner, import them into Aperture 3.1.1, clean up the photos and sometimes even am allowed to upload to SmugMug and THEN I get the Unsupported Image Format screen and can't do a bloody thing to my photos nor can I even bring them back. This doesn't pass a test of reasonableness.
    Anybody have a workaround? This only happens with B&W photos.

    Hi Vincent,
    Though the following refers to iPhoto, could Aperture have a similar issue as well? When scanning B&W negatives, photos and, documents, then attempting to bring them into iPhoto I had the same issue. iPhoto returned "Unsupported Image Format" or, they appeared as a rectangle filled with black the shape of the imported item. Those scanned items were saved as JPG files.
    Opened them in Photoshop Elements (PSE) I could see them. In PSE I found the item's Mode was Grayscale. Changing Mode > Grayscale to Mode > RGB, saving it iPhoto imported it as it should; life is good.
    Even though the files were B&W images iPhoto wanted the files formatted as RGB. Now when I scan I do check the Mode making sure the file is in RGB even though the image is grayscale.
    Cordially,
    RicD

  • Unsupported Image Format for DNG from GF1?

    I am in the process of trying to switch from Lightroom 3 to Aperture 3 (in case you are wondering why the main reason is increasing integration between iOS and Aperture).
    Most of the images in my Lightroom catalog are from Nikon DSLRs which when I import as DNGs from Lightroom into Aperture show up just fine. However, all of the old DNGs I try to import from Lightroom as DNGs that were shot with my Panasonic GF1 don't render in Aperture and just show up as "Unsupported Image Format."
    Please note that new GF1 images I import from the SD card of my GF1 import just fine. The problem seems limited to GF1 images saved in Lightroom as DNGs that I am importing into Aperture.
    Does anyone have any suggestions as to how to correct this issue?
    Thank you.

    Solved it. Had nothing to do with Photoshop PS4 install, it had to do with moving my home space to a larger external drive. One of the "import" setting changed (I don't remember changing it) such that the images weren't getting imported into Aperture. (Re-?)checked that, and all is well. Will go for the PS4-reinstall tomorrow.

  • Unsupported Image Format After External Editor

    I have Aperture set up with Photoshop Elements 6 for MAC as the external editor. I have PSD(16bit) 300 dpi. I have used this external editor several times in the last two days. The most recent time I had a problem. It started PSE 6 as requested and displayed the picture with a *.pdf filename. I used the filter option I wanted and was satisfied with the result in PSE 6. I saved the file and quit PSE. It came back to Aperture and displayed two images: the original on the left and the edited on the right. After one or two seconds the image on the right (the result of the edit) was replaced by a dark red background with the black text Unsupported Image Format displayed. If I click on the right image, the edited image appears briefly and then reverts back to the error display.
    As I said, I used this only the night before several times with no problems and I have not changed my Aperture preferences since then. The master file is a Canon cr2 file and I did some Aperture corrections before I decided I needed to run a filter in PSE 6.
    Thanks,
    Bruce

    I'm having a similar problem with unsupported images. The problem has occurred when I use an external program to create an image. I've tried creating them as TIFF and JPEG. If I use the Sony Image Data Converter (v2 or v3) I get the unsupported image format.
    Last night I was scanning film with Silverfast, creating TIFF files and using them in Aperture 2 as referenced files. Everything was fine. This morning I did the same thing and got the red Unsupported Image Format screen from the same original image.
    I have found if I import the unsupported image into the Aperture library instead of using it as a referenced file it usually works. I don't like this solution because it messes with my work flow and I'm trying to keep the size of my Aperture Library under control.

  • Unsupported Image Format when inporting from my new Canon 400D (KISS X) CAM

    Could someone please tell me why Apeture is giving me the Unsupported Image Format notice when trying to view and import Raw images from my new Canon 400D camera? I can view the photos on my Canon software. Is it possible that just becase the file is 10.1 MP on my new cam instead of the 8mp that my rebel XT (350D) was that Apeture can not use the format? If in fact this is the case, what can i do to get the 300 plus photos that I just shot at a paid photo shoot into Apertue and still be able to work with them raw?
    I would be grateful for any help I can get.
    Thank you.
    Stan

    Two problems with this workflow:
    1) A 16 bit TIFF file is 52 megabytes. Ouch. Reading them bogs down my little MacBook like you wouldn't believe. I may have to work with JPEG or, god forbid, use Photoshop until Apple's devs can get support for the XTi
    2) Aperture seems unable to figure out the colour balance of the TIFF files. I added a bit of saturation and colour correction (working in the Adobe RGB space) in Canon DPP, but Aperture seems to totally screw up on these files. http://images.dasmegabyte.org/wine_tour/large-37.html almost no detail at all in those bins (plenty in the RAW) and I had to boost the gamma on the web gallery by 1.2x so they didn't look fire engine red.
    MacBook Pro   Mac OS X (10.4.8)  

  • "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

  • Unsupported image format bug

    Hello
    I'm using Aperture 3.4.5 on an iMac, 10.8.4, etc, and importing images from a Canon T3i -- usually but not always RAW. Until this week it worked like a charm.
    Now, each project I import causes the images to be labeled "unsupported image format" with a black field and white triangle with an exclamation point. If I go to light table view the previews look fine, but as soon as I click to bring up an image it's corrupted.
    The Canon DPP utility CAN see the images, as can Photoshop CS6. Older images (same camera, etc) prior to the last couple of imports are fine. So the images aren't corrupted, Aperture is having a problem.
    I've repaired permissions within Aperture and by using Disk Utility. I've repaired the library and then rebuilt it. Each time the problem comes back.
    My iMac has all software updates applied; I don't think I've had a Canon update for RAW formats, and the T3i has been around quite a while.
    Any ideas? Thanks in advance,
    Steve

    hdskullfire2
    Bang! You got it!
    And an apology to leonif DF -- of course when I said I had not installed anything recently, I didn't even think about Apple updates pushed to me. Cheez, I'm a dummy.
    So here's what worked:
    1 -- navigated to /System/Library/CoreServices
    2 -- trashed RawCamera.bundle and RawCameraSupport.bundle
    3 -- restart
    4 -- downloaded RAWCameraUpdate4.07 from Apple
    5 -- installed that
    6 -- launched Aperture
    7 -- opened the Project that had a problem
    Success!
    The munged images in Aperture are now vvvvery interesting.
    If I manipulated them before and got the black box with triangle, they STILL have that displayed. BUT if I duplicate them, the duplicate is fine and can be manipulated without fear.
    If I did NOT manipulate them before, they are fine now.
    By the way, the munged images could be opened and viewed properly by Photoshop CS6, Preview, etc, and displayed their thumbnails properly in Finder when I navigated to my Aperture library.
    Thank you both for your help!
    One more question: how might I report this (politely, of course) to Apple? Seems like the RAW 4.08 has an issue.

  • Canon 10D RAW - Unsupported Image Format??

    I have a folder of 66 Canon 10D RAW (.CRW and .THM) images. After importing to Aperture 1.5 I get 'Unsupported Image Format' for 29 of the images. If I try and open one of these images from the Finder in preview I also get a 'Cannot open' message.
    Strange thing is iView Media Pro, RAW Developer, Canon DPP, Phase One C1, Photoshop CS2 and LightZone can all open and view these files! Only Aperture/OSX (Preview) is having the problem.
    Any ideas how to 'recover' these images to Aperture?

    You are indeed correct .... shame on me for not reading your post carefully.
    Since you have .THM files, are you pulling the images into Canon's ImageBrowser or DP Professional before Aperture vs. importing direct to Aperture? The reason I ask is that iPhoto, Preview and Aperture all failing to read the same image is clearly systemic not application specific. It points to some level of corruption - - - as far as OS X is concerned - - - of the image and is obviously not application centric, save where the application calls on the OS support systems.
    Is it possible for you to generate .DNG's for the "Unsupported" images and try importing these? It may be the CRW wrapper that is somehow unreadable at a myopically detailed level that other imaging tools blythly (and perhapds more appropriately) ignore. The DNG wrapper may allow the RAW content to be then read by Aperture.
    Hopefully this is a more helpful response.
    G.

  • Aperture 2, OS 10.6.4, and Pentax K-x, creates unsupported image format

    Upgraded from 10.6.3 to 10.6.4, and started getting the "Unsupported Image Format" problem in Aperture again for my RAW DNG files from a Pentax K-x.
    The previous fix was to remove the Raw Compatibility Upgrade, and reinstall the 3.0 version. (3.03 was the installed version after 10.6.4).
    Doing this, I was able to view my images, but they show up as only 250 x 170 pixel images in Aperture metadata!
    File size is what it should be (~10MB), but they are dinky little images. What the heck?!!!
    Any ideas what's going on here?
    I would upgrade to Ap 3, but still see tons of people reporting problems with it supporting Pentax, especially color shifting of RAW images after upgrading.
    Suggestions appreciated!
    db

    Hi David-- thanks for your advice. I have been looking into it further and it just gets more confusing. I am able to open all of these DNG files in Photoshop so the problem seems to be with some combination of the K-X, OS 10.6.4 and Aperture 2. I have gone so far as to purchase Aperture 3 but haven't opened the package yet. After hearing about your experience (not to mention the thousands of other complaints about Ap 3 performance I've seen) I think I'll take it back and make the switch to Lightroom 3. Lightroom's features may not be quite as good, but at least it seems to be stable and I imagine it will be able to read the DNGs since Photoshop does. I just don't have the energy to be constantly patrolling the state of my photo management program!
    I'll keep you posted on my experiments with Lightroom.
    Thanks again.
    -Baz

  • Nikon D70 RAW files now get "Unsupported Image Format"

    Prior to March 12th, everything was working fine with my D70 Raw files. I now get the maroon "Unsupported Image Format" (USF) when I select the images that were previously fine. They show up for a fraction of a second before I get the error. I tried rebuilding the database to no avail. I can export the RAW files and open them in Photoshop so they are OK. Also now when I import from my D70 I get the gray box instead of the image and a letterbox maroon USF message, the EXIF data still imports and is associated with the image. Help. I did upgrade to 1.1.1
    Dual 1.8Ghz Powermac G5 2GB RAM Radeon X800 XT   Mac OS X (10.4.6)  

    Well, I can't really put my finger on it. I know for sure it happened post 1.1 upgrade, but it happened with 1.0 as well (I didn't do any troubleshooting when it first happened, just re-imported and it was fine.) The last time it happened it was the last 20 images on the original CF card, mostly in succession, but there were a few images that were still able to be read okay inside of that 20 image string. I reimported from the original card (thank God I had not erased yet!) and it was fine.
    At least I know to keep my originals outside of aperture, what a space wasting bummer! I don't think I have any bad RAM because I've been running for 2 years without any real problems... The minor problems have happened, I believe with very tough weather conditions (humidity) and I experienced problems on all my Macs and even at work on windows. Maybe it was sun flares or static electricity, I don't know. The other issue is that my a/c power dips to low voltage often and my UPS switched to battery. I have a better UPS which always outputs 120v even when things sag or jump.
    The only other thing I can possibly think of is that I have my Aperture library on a new Seagate 300GB drive that has only been used for images and sits dormant in my system except for scratch disk and Aperture. Actually, I did use it for about a month or two mirroring my boot drive with no errors, so I think the drive is good. Grr!
    Troubleshooting rare occurances without have access to trace level data *****! (At work we can take a trace dump from our equipment and the guys can see pretty quickly what happened, and if it is hardware or software issue.)
    To clarify, which Dual 1.8 do you have? The June 2004 one with only 4 RAM slots, or the 2003 one that was added to the original lineup with 8 RAM slots?
    Aaron

  • Unsupported Image Format help! - jpeg

    I have this normal jpeg file 1600 x 1200 that I downloaded and imported into Aperture. The image worked fine in Finder, it didn't generate a preview/thumbnail but sometimes Finder doesn't always do that but I can open it up in Preview.app and view it just fine. The image also opens up in Adobe Photoshop CS 3 fine also, it just doesn't open in Aperture. In Aperture it will say "Unsupported Image Format" in white letters on a burgandy colored background where the image is supposed to be.
    Below is a link one of the images I have this problem with but note that I have this problem with a lot of jpeg files just recently.
    http://www.desktopextreme.com/photos/ToyotaCelica325200561606PM457.jpg
    If you guys want more images that are facing this same problem I could post links to them but I think if we find the problem with one of the images then we would have found the problem with all of them.
    Please any help as to why this is happening or and what I can do to fix it would be greatly appreciated!
    Thanks,
    - Jake

    I've been having this problem with scans off my Hasselblad color slides ever since I started using Aperture at like release 1.5. What I'm hearing here generally agrees with my own experience. I'm scanning in 6x6 color slides at the maximum quality available on my scanner, a Nikon Super Coolscan 9000 ED. The results are very large TIFF files at 16 bit color. One of the really frustrating aspects to all this is the error message isn't exactly truthful. I can get the images to display, I just have to keep shutting down and restarting Aperture every time I want to move on to a different image in a shoot.
    Here's what happens. I open a project containing these image files. The images all display just fine in the browser. The first image selected in the browser begins to load in the viewer. It takes a while, but it gets in there. Nice. Then I click on another image in the browser and almost immediately I get the "Unsupported Image Format" message.
    So I shut down Aperture. Then I restart it. It comes back up on the same project I was just looking at, but before the first image finishes loading in the viewer, I quickly select the other one I wanted to view instead, but had just gotten the "Unsupported Image Format" error on. Lo and behold...it loads into the viewer just fine too. But then when I go to select yet another image, almost immediately I get the "Unsupported Image Format" error.
    Obviously the error isn't because the image format is "unsupported" because the images come up just fine. But having to shut down and restart Aperture every time I want to view a another image isn't...well...very productive.
    I no problems at all...none...with the 35mm scans at the same scanner settings. Well...except the fact that the black and whites don't appear in the import dialog browser, which I understand is yet another issue with 16 bit TIFFs. But I just cannot work easily and quickly with my Hasselblad stuff and it is getting really frustrating. I've been waiting for over a year for Apple to fix this. Does anyone...Anyone at all...have any clue as to a timeframe for a fix for this?
    I can't keep working like this. I really like this software, I love the user interface, I like the convenience of how it nicely generates web galleries and posts them to my iMac account. But the software is getting in my way, and I can't concentrate on what I'm trying to accomplish if I have to keep shutting down and re-starting Aperture just to view my images.

  • Aperture gets "Unsupported Image Format" on some JPG images

    I'm using Aperture 1.5.2 "trial" on PB 15" with OSX 10.4.9. I am getting "Unsupported Image Format" on about half of the 15,000 JPG images that I have on my HDD. But not all of them - even though all images come originally from my D100 camera and are JPEG images. These are all JPEG images with extensions JPG, jpg and jpeg. No RAW or TIFF.
    My images are currently catalogued in iVew MediaPro [IVMP] and I'm interested in switching to Aperture. So I've gotta find a way to import those photos.
    Here's a clue: When I put the CF card from my camera into the computer yesterday and tried to add the images to Aperture it reported that all the images on the CF chip were "Unsupported Image Format." I was not copying the images - just leaving them im place. As a test, I then used IVMP to import from the CF card onto the HDD, into a directory. Afterward, I fired up Aperture and it could properly index and display the files. I noticed that the pre-existing images that are viewable in Aperture all have previews when viewed in the Finder. Also, they've all been imported from CF to HDD using IVMP, so there may be some processing going on there. I also tried reading files into Photoshop and rewriting them with previews, which I verified in the Finder, and those files also can not be viewed in Aperture. So it is not just a question of having a preview - it's something else about the files.
    Another clue - when I shoot more than one CF of photos in a day, I use IVMP to import the first CF batch, and those are always visible in Aperture - but IVMP doesn't let you import two batches on the same date (pretty goofy huh?) - so to import an additional batch I have to (Finder drag-drop) copy from the CF to the HDD into a directory - and those files have no previews, have not been imported thru IVMP, and interestingly are not viewable in Aperture.
    So I'd have to conclude that iView MediaPro is doing something to "tame" the files' format that makes them acceptable to Aperture. But I want to dump IVMP, so there has to be some other way to make these D100 files acceptable to Aperture.
    I either need to "fool" Aperture into reading the files or find a way to tweak 'em and make 'em acceptable to Aperture. Any ideas from other iView/Aperture users out there?
    PB 15"   Mac OS X (10.4.9)  

    Good idea, but I checked it... I mentioned reading right from the card in order to illustrate that the JPG files are "unsupported image format" even *right from the camera*. *In fact* the CF is not the differentiating factor between renderable and non-renderable. The real factor is whether the files went thru iView Media Pro or not. Files that were drag-dropped from the CF into a folder are not renderable by Aperture and files that were imported first (from the CF or from another folder) thru IVMP into a folder are renderable.
    Yesterday I confirmed again that GraphicConverterX does not fix the files if I import and then rewrite with additional options turned on. It also sees the same IPTC data and EXIF on both a "good" file and a "bad" file. Identical. I also fixed the OS9 creator and filetypes so they're <none> and that didn't fix anything - some good files and some bad files have this configuration.
    Ah another COOL THING - I just loaded a CF card into the computer and brought up Aperture - it immediately recognized the card and showed me two previews - one for a NEF (Nikon RAW) and one for a JPG. The previews looked fine. I clicked to have it import the photos. Once imported, the NEF looked OK, but the JPG had a grey preview and then "Unsupported Image Format" on the large version. I think this confirms the file format is a problem, but then why was Aperture able to gen a preview when the file was on the CF chip but not after it was copied to the HDD?
    I double-checked this by copying in Finder drag-drop from the CF card to the HDD and then importing the same two photos (NEF and JPG) from the HDD, and indeed the NEF was renderable and the JPG was not. For me this confirms that there's something about the file format that Aperture can't deal with.
    I then imported the same two files using IVMP (Media Pro) and as expected, both files could then be "imported" and rendered by Aperture. So IVMP is doing something that makes Aperture really happy.
    In case someone can actually compare the two files - I have put up a "bad" and a "good" JPG - it's the same image from a Nikon D100, but one of them (bad) is right from the camera and the other (good) was imported by IVMP and somehow is acceptable to Aperture. Any intelligence that anyone can add based on these files would be useful.
    http://fire.red7.com/aperture-tests/DSC_0070-good.JPG
    http://fire.red7.com/aperture-tests/DSC_0070-bad.JPG
    PB G4 15"   Mac OS X (10.4.9)  

Maybe you are looking for

  • Performance tuning in EP6 SP14

    Hi, We just migrated our development EP5 SP6 portal to NW04 EP6 SP14 and are seeing some performance problems with a limited number of users (about 3).  Please point me to some good clear documentation related to performance tuning.  Better yet, plea

  • Can Anyone Help Me Configure My Verizon (D-Link) DSL-2750B "Traffic Shaping" (QoS)?

    Well ... I just spent a wonderful hour and a half (not) bouncing around VZ technical support, etc. trying to get assistance regarding configuring my DSL router.* Between the low-quality Skype connection to India and my lack of success, I'm a little b

  • How to use position hierarchy for approval in custom workflow ?

    Dear All, I have created a custom workflow which fires when ever a new supplier site is created. Now I want to add approval hierarchy in this flow. For that I want to use Position Hierarchy. I have not find useful resources for doing that. Can you pl

  • Video stretched when exported even when "letterbox" is checked

    Hi, I'm trying to export a lower quality version of one of my HD movies. I've previously been able to do this when I export using Quicktime Conversion at 640x480 with the "letterbox to preserve aspect ratio" option checked. However, I just did exactl

  • Where clause with In

    Hi I have a simple query in the stored Procedure below. create or replace package vr_DEPT as TYPE dname_rec is record (dname dept.dname%type); type dname_ref_cur is ref cursor return dname_rec; Procedure dept1(dno Number, dname2 in out dname_ref_cur)