Unsupported image format with Leaf Aptus 65

Hello all,
even after the latest Aperture update to 1.5.6, Aperture gives an error message with Leaf Aptus 65 RAW files. I can see the image for a second. Anyone here with this digital back but not having this problem?
Thanks.

Maria, the raw support for the Nikon D800E requires Aperture 3, see the technical specifications for the raw support in Aperture:    D800E**,   ** Requires Aperture 3 or later.
Apple - Aperture - Technical Specifications - RAW Support
You will have to upgrade to Aperture 3, to use the raw images with Aperture or shoot jpeg or use the software that came with your camera to develope the raw.
Regards
Léonie

Similar Messages

  • Unsupported image format with 3:2 or 16:9 aspect for Leica Digilux 3

    I can import RAW files just fine with my Leica Digilux 3 dslr, but when I import RAW images using 3:2 or 16:9 aspect formats, aperture comes up with unsupported image format. appreciate any feedback.
    as an fyi, it does it on a macbook pro and an imac

    Allen,
    there have been several threads with similar problems of broken references to raw images; in some cases even with managed raw images, that cannot be reconnected, for example:
    Raw images all blank
    One more reason to avoid managed libraries.
    The "lsregister" command must exist on your machine.  It may move around a bit, because there are many links in the path to current versions.
    After the last update I found this direct path (MacOS X 10.8.2):
    /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchSe rvices.framework/Support/lsregister -R /System/Library/CoreServices/CoreTypes.bundle/Contents/Library
    To search the "lsregister" command in your system, try to open the "/System/Library/Frameworks/CoreServices.framework" in the Finder and to navigate from there:
    Typing "open /System/Library/Frameworks/CoreServices.framework" into the Terminal will open a Finder window in the directory (as you probably will know )
    Added: If newly imported raws are recognized without problems it is unlikely to be a problem of missing raw conversion registration. I am just concerned about the error message you get.
    Regards
    Léonie

  • "Unsupported image format" with my new Nikon D800E - please help.

    I get this message: "unsupported image format" when I try to load photos from my new Nikon D800E. Aperture 2.1.4. Worked fine with old Nikon D300. I can get a thumbnail image in Projects, but that's it. Suggestions, please?!

    Maria, the raw support for the Nikon D800E requires Aperture 3, see the technical specifications for the raw support in Aperture:    D800E**,   ** Requires Aperture 3 or later.
    Apple - Aperture - Technical Specifications - RAW Support
    You will have to upgrade to Aperture 3, to use the raw images with Aperture or shoot jpeg or use the software that came with your camera to develope the raw.
    Regards
    Léonie

  • Suddenly "Unsupported Image Format" with previously good image files

    Aperture 3.3.2 under OS 10.7.4 on a 2011 MBP with 8 GB RAM and no overfilled drives.
    Nikon D2x NEF + JPEG files, RAW as Master. Has been working fine for weeks, no change in setup of any kind. No crashes until hours after this problem presented today. As recently as yesterday I was round-tripping to Photoshop and exporting from Aperture smooth as silk.
    Suddenly today most images will not open in Photoshop via Aperture but they open fine in PS from the referenced originals. Aperture will not export NEf files or most PSD files. JPEGs as Masters work normally.
    Aperture apparently sees the referenced files fine, including displaying and zooming. Most of the time. This is not an issue of unconnected originals.
    I have tried rebuilding the database, repairing permissions, deleting plist, etc. About half the time Aperture ends up stuck and reqs a force quit. Tested with multiple Libraries. New image files imported tday for testing work normally with any Library.
    I tried Terminal mode and Léonie's string
    /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchSe rvices.framework/Versions/A/Support/Isregister -R /System/Library/CoreServices/CoreTypes.bundle/Contents/Library
    multiple tries always came back with "no such file or directory."
    This was a very stable setup so I am very _not_ desirous of starting to upgrade things just because. I have an upgrade plan for 10.8 but for good reasons do not want to do it just yet. Also I do not want to back up or upgrade from anything broken. 100% of originals are readily available, but there are many tens of thousands...
    Any ideas would be appreciated.
    TIA
    -Allen   

    Allen,
    there have been several threads with similar problems of broken references to raw images; in some cases even with managed raw images, that cannot be reconnected, for example:
    Raw images all blank
    One more reason to avoid managed libraries.
    The "lsregister" command must exist on your machine.  It may move around a bit, because there are many links in the path to current versions.
    After the last update I found this direct path (MacOS X 10.8.2):
    /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchSe rvices.framework/Support/lsregister -R /System/Library/CoreServices/CoreTypes.bundle/Contents/Library
    To search the "lsregister" command in your system, try to open the "/System/Library/Frameworks/CoreServices.framework" in the Finder and to navigate from there:
    Typing "open /System/Library/Frameworks/CoreServices.framework" into the Terminal will open a Finder window in the directory (as you probably will know )
    Added: If newly imported raws are recognized without problems it is unlikely to be a problem of missing raw conversion registration. I am just concerned about the error message you get.
    Regards
    Léonie

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

  • Twist on Unsupported Image Format message

    I have Aperture on my G5 tower as well as my Macbook Pro. A year ago I copied a project from the G5 to my Macbook Pro. The project was fine on both computers. Two days ago I was in Aperture on my G5 and I noticed that not all but some of the pictures in that project threw up the magenta screen with the Unsupported Image Format message. Interestingly, those very same pictures on the Macbook Pro also come up with that message.
    Now, understand that these files have been separated for a year. Both Aperture programs are up to date, both computers are up to date. Both have Adobe CS3 products installed, all up to date.
    To me this has nothing to do with file corruption or anything to do with editing time or memory as suggested in a number of places in various posts. An update from Apple has caused this. No way two computers could corrupt the same files at the very same time.
    If anyone has any advice or insight beyond restarting Aperture or the computer I would be quite happy to hear it. So far my searches have revealed nothing.

    I also had the Unsupported image format with the maroon background today. I have a Nikon D80 but all of my images are .jpg and I don't use raw .nef format. Working on a project all afternoon an early evening and SUDDENLY started getting 'unsupported image format' messages on the red background. I know the files are not corrupted because I had been in and out o many of them all day long. Had a similar problem with 1.5 and phoned Apple support and was told to restart Aperture holding down the Option - Command keys. A message appears to rebuild the library. Took about an hr for 40,000 images (24"3.0 iMac with 4 GB) and all is fine again.
    If I remember correctly, Aperture keeps track of everything in a database of some sort and sometimes it gets corrupted. The uif messages start to appear and quickly get more frequent. Rebuilding the database resolves the problem.
    Worked for me today, hope it works for others.
    Cheers,
    Dave
    PS. How come someone from the Aperture support team doesn't post this???
    Also, searching for "unsupported image format" in the help menu or the aperture support page doesn't immediately display this solution. Instead you have to hunt through the forums?

  • "Unsupported Image Format" all of a sudden, with previously workable files

    Folks,
    I've got an issue that seems very strange indeed.
    Months ago, I bought a Pentax K20D. I also bought a 17" MacBook Pro and Aperture. Camera and Aperture played well together.
    I encountered the known issue with white spots on the image when using the 2-second timer for long exposures. I read about how the Pentax firmware update 1.01 changed the EXIF Make information, causing Aperture to be unable to read the K20D PEF RAWs. So I waited.
    When Aperture 2.1.1 was released (and I think the Apple RAW update), I installed both of those. When I heard through this forum that the updates fixed the problem, I also updated my camera's firmware and confirmed that it worked.
    So smooth sailing for a few months on Aperture 2.1.1, OS 10.5.3 (or .4, I forget), and K20D firmware 1.01.
    Then I bought a Mac Pro 8-Core with 10.5.4 on it. I sold the 17" MacBook Pro. I used the Migration Wizard to move my user account from one machine to the other, but did a fresh install of all applications. (I've been an Apple tech for the past 7 years, and have various certifications. I know the user transfer process isn't perfect, but it should have the following results... read on)
    Now, in Aperture 2.1.1 on 10.5.4 with all updates, PEF RAWs taken with K20D firmware 1.01 that were previously edited, manipulated, etc just fine on my MacBook Pro say "Unsupported Image Format" in a big reddish-black box when I try to view the master. If I switch to Quick Preview, it displays just fine, but is un-adjustable. Additionally, any NEW images I copy from my K20D show in the Import window as being 0x0 pixels (or occasionally 160x120 pixels) and will only show a tiny preview or "Unsupported Image Format." All PEF RAWs taken with K20D firmware 1.0 are just fine.
    So here's what I've done:
    1) Tested a fresh install of 10.5.4 on another HD in the Mac Pro. Installed Aperture 2.1, updated to 2.1.1. This should be perfectly clean. It gives the "Unsupported Image Format" error with any new images from my K20D. Copying the library from my other partition gives the same problems as described earlier.
    2) Tested a fresh install of 10.5.3 on another partition in a Macbook Pro. Installed Aperture 2.1, updated to 2.1.1. Applied the Apple RAW update and iLife enhancements. It gives the same errors as before.
    3) Tested a fresh install of 10.4.11 on another partition in a Macbook Pro. Installed Aperture 2.1, updated to 2.1.1. This worked perfectly for all PEFs and DNGs.
    4) Took a month-old backup (from when everything was working just fine) of my Aperture Library and loaded it into all of the above configurations. Same results!
    So what is the deal here? Aperture all of a sudden can't read images that it itself was able to edit a month ago? How come it works just fine in 10.4.11? This seems really messy. I have essentially lost a lot of the work I've put in.
    I can use DNGs moving forward, but my past work is now messed up, and the DNGs are almost 75% bigger than the PEFs!
    Anyone have any ideas for resolution or should I just call Apple?
    Message was edited by: MonsieurBon

    If it's any consolation, I had the EXACT same problem today; just opened Aperture 2 and my entire library of images shows "unsupported image format' -- the thumbnails are still intact but clicking on any image suddenly shows the red screen.
    Same situation, these images were previously editable and accessible. We had a power outage an hour ago and initially I thought my library had crashed, but I was not actually using Aperture 2 at the time of the outage so I don't think that's the case.
    Given the relatively sparse attention Apple gives to these forums, I don't expect there will be a quick response.
    I have Leopard 10.5.4 installed, I don't have access to another version of the OS to see if I can get it work. If I'm not mistaken, wasn't there a series of Software Updates recently? I click on these without really checking the apps that are affected; could Aperture have been one of the apps 'revised' by the recent update?

  • Raw Files Appear Deleted or Corrupted Suddenly in Aperture with Unsupported Image Format Error

    I have been using Aperture 3, latest update, for the past year. Today, I tried to import new raw files from my new Sony RX1r and, as far as I can see, all raw files in Aperture give the "Unsupported Image Format" and alert symbol in the library where not only new files should be, but also ALL PREVIOUS RAW FILES. These files do no even show up as existing in the iPhoto Library.
    This is, needless to say, distressing, as hundreds and hundreds of photos seem lost. Also, the files show a reduced pixel size and file sizes all go to .5 Mb. Some of the photos seemed to show up initially and look fine until I tried to open them, then they all either disappear or show the Unsupported Image Format instead of the opened file. I have tried rebuilding the iPhoto library, but no help.
    I have looked in these discussions and see similar problems with Aperture. Perhaps, Apple has not made an update for the RX1r from the RX1 for raw files, but why should all older raw files now be corrupted, especially those recently made with my Olympus OM-D? Had no problem with Aperture until this disaster.
    Please help.
    William

    Just an update. Restarted computer and attempted rebuilds of iPhoto library a couple more times and finally files and photos mostly recovered, except for those I had tried to open. Aperture seems to have a problem, or a host of them, dealing with RAW files, and there is no update yet for the Sony RX1R for Aperture or iPhoto. Lightroom 5, on the other hand, seems to work great with these files directly, so that will be where all photos go for now. Will iPhoto and Aperture just become old archives? It is so infuriating that Apple does not allow for simple importing and exporting compatibility with such an excellent program as Lightroom 5 just to protect their somewhat poorly supported Aperture. I've been a staunch Apple supporter and user since the 80's, but having more doubts about the direction this company is taking.

  • After loading Lion I cannot open some pictures. I get Unsupported Image Format. It tells me picture was taken with Canon EOS Rebel with unknown lens

    After loading Lion I cannot open open some pictures in Aperture. I get Unsupported Image Format, all files even the ones I can open are .JPG. Also it tells me picture was made using Canon EOS Rebel with unknown lens.

    You mention that 'most' of your files are DNG. Try
    running the effected files through Adobe DNG
    converter again and then import your reprocessed
    files to Aperture and see if the problem persists.
    I had a problem with a batch of D2x files converted
    to DNG which had been metadata tagged by
    PhotoMechanic (the evil app).
    B.T.W. You mention that you had been using Bridge.
    Are you getting any of the embedded XMP metadata
    coming into Aperture during the import process?
    Already tried that multiple times...no luck. I'm wondering though if it might be related to metadata as you suggest. I'm still trying different things to see what happens.
    I was able to alleviate the problem on one set of images by painstakingly searching my external drive for the oldest backups I could find - CR2 files from before DNG conversion. I then ran those through DNG Converter and tried importing them again (this time, I embedded NO thumbnail, but I'm not sure if that made the difference - I think it was more likely a fluke in the original conversion that caused the problem). This time, it worked.
    Now, the big problem is that I still have a couple hundred images for which I can't seem to locate the original CR2 files. I don't typically keep them after conversion, as I don't have the space for both.

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

  • Intermittent "Unsupported image format" message with either CR2 or DNG

    I am seeing "Unsupported image format" messages once files created by a Canon EOS 1Ds Mark iii (+stored in Canon's CR2 file format or when the same file is converted to Adobe's DNG file format+) have been imported into Aperture.
    Some files will import and be viewable. However, most of the time the files are not viewable. This occurs even after updating Aperture to 1.5.6.
    Is anyone else seeing problems with CR2 or DNG files created by Canon EOS 1Ds Mark iii?
    Has anyone see a solution?

    I think Support is confused with the Canon camera models.
    10.5.1 supports 1D Mk III, but only 1Ds Mk II.
    (http://docs.info.apple.com/article.html?artnum=306835
    http://www.apple.com/aperture/raw/cameras.html)
    I don't believe that 10.4.11 supports anything that 10.5.1 doesn't support. In fact, the docs at http://docs.info.apple.com/article.html?artnum=306297 say "Adds RAW image decoding support for the following cameras: Panasonic Lumix DMC-FZ50, Leica V-Lux 1, Olympus E-400, Olympus EVOLT E410, Olympus EVOLT E510, Canon EOS 40D" (the 1D Mk III came in the 10.4.10 update.)

  • "Unsupported image format"- Has nothing to do with RAW images-

    I have a very weird problem with one of my Aperture 3 libraries. This only seems to apply to one library, all the others I tested seem to work just fine.
    This library was created on my MBA and transfered to my iMac when I returned from my trip. It worked fine until yesterday.
    When I open an image (thumbnail looks just fine) the photo briefly shows the large view with the "Loading" indicator at the top. When the loading indicator goes away the photo is replaced with the "Unsupported image  format" display. After that the thumbnail is gone too. This happens for most, but not all images in this gallery. I can restore the thumbnail and other previews from the raw NEF photos by choosing "Reprocess Original".
    I have already tried all the options the Aperture debug menu offers (start with Option-Command), this didn't help…
    When I open the library in the Finder (Show package contents) I can drill down to the "Previews" folder and see the photos that Aperture wont display. They seem jsut fine and all file permissions seem to be set correctly…
    Has anyone ever experienced this problem? I really don't know what else i could try, short of deleting this library and importing all the images into a new one, losing all my edits, of course… Super annoying…
    Thanks and kind regards, Hans
    Edit: The raw photos are from my Nikon D700, which has been supported by the RAW importer since forever. i dont think that has anything to do with the original files, especially since Aperture can recreate the previews from the raws…

    There has been problems with the last Raw update released a few days ago especially with Nikon cameras.
    Have you updated your system software in the last day or so? Is it possible you updated on one system but not another.
    And for what its worth norbertmuc's question was  valid from a troubleshooting standpoint. If something worked at one point and stop working at a second point it is fair to ask what happened between those two points. He might have been a bit brusque but I don;t think he was accusing you of anything.
    And of course there are many things you can do to a library to break it.

  • Canon G7x and unsupported image format icon with RAW files.

    When RAW files downloaded from Canon G7x get "Unsupported Image Format" message. Using iMac with 10.9.5  and Aperture 3.5.1.  This is a new camera and is not on the supported list.  Is there a way around this?  Now that Aperture is static will new cameras continue to be added to supported list?

    The only way 'around' it is to upgrade to the required Aperture and/or OS version.  So you will need to wait for that to happen. In the meantime you could shoot Raw+JPG, use the JPGs now and when (and if) the camera is supported (or you move to a different program) you will have the Raw files.
    As for camera updates in Aperture, no one here can say what Apple intends, we;re just users here like yourself and even discussing this is technically against the TOU of these forums.
    But I think it is safe to assume, as Apple will continue to support Raw processing and that the Raw processing is done at the OS level and they have said they will support Aperture at least through Yosemite's life cycle that any new Raw format added to OS X will reusable by Aperture. But that's only a guess.

  • Canon EOS 350D .CR2 pics still 'unsupported image format'?

    I was releaved to see updates in Mac OS X (10.4.8) and Aperture 1.5 the other week, hoping it would solve my problem, being able to finally work with my RAW files (.cr2) from the Canon EOS 350D (yes, being in Europe these days).
    I followed the posts on the forum throughout the summer, which recommended waiting for the next OS X update (which should support the camera in that raw definition file) and I didn't want to use the workaround, which clearly had problems with the colors on the pics.
    After all the updates the other week, nothing has changed on my MBP. Still the 'Unsupported Image Format' on my RAW files. On the other hand, I don't see any posts on problems with the 350D camera anymore as well (only on CR2 files in general).
    Am I missing something really basic here (tried rebuild library)? Or, have all the CR2 formats gone down the drain on Aperture 1.5?
    Any help is appreciated, as I have already looked into Adobe Lightroom Beta and although I don't want to switch, the files seem to work there...

    Yes, the import thumbnail is as you describe, the low res. JPG that is embedded in the RAW wrapper.
    10.4.8 needs to be installed prior to Aperture 1.5 .... from a functionality point of view. I am not aware of a dependence that says AP 1.5 has to be uninstalled before a 10.4.8 upgrade or any such, not that AP 1.5 should need re-installing after a 10.4.8 upgrade .... assuming it was working correctly beforehand.
    But to this last point, since you have an issue which may be related to AP or OS X, it is likely worthwhile updating both and in order.
    Final thought. do you import directly from the CF card / camera vs. using an intermediary tool such as ImageBrowser or DP Professional? I am wondering if Aperture is very OCD aboout the image format wrapper and chokes at the least excuse that other apps. and tools ignore.
    G.

  • Unsupported image format after moving from one project to another

    I scanned several thousands of images to my Aperture library. Went thru all of them providing adjustments to many of them, keywords to all of them and adjust date/time to all of them. All of the pics were visible, format is jpeg.
    This is a managed library (all pics within Aperture db).
    This morning started to restructure the project files (had three of them). After moving couple of hundred images to newly created project file I started seeing "unsupported image format" red screen after clicking the jpeg. 20-30% of the pictures clicked showed on viewer "unsupported image format".
    Tried regenerating the previews. Tried command-option start with first fix the preferences option. Then with rebuild option.
    Tried moving the pictures back to their original project file.
    No joy... Still 20-30% of the pictures show the "unsupported image format".
    Aperture 2.1.
    Amy other tricks I could try?
    Reported this to Apple aperture feedback of course.
    --h

    Link the two Macs together: there are several ways to do this: Wireless Network, Firewire Target Disk Mode, Ethernet, or even just copy the Library to an external HD and then on to the new machine...
    But however you do choose to link the two machines...
    Simply copy the iPhoto Library from the Pictures Folder on the old Machine to the Pictures Folder on the new Machine.
    Then launch iPhoto. That's it.
    This moves photos, events, albums, books, keywords, slideshows and everything else.
    +Note: there is no importing involved+
    The thumbs appear, but the images are added 2 or 3 times each and the events are all messed up.
    This happens when you import one Library to another, which you've done by drag and drop:
    Creating a black library and over writing the new with the old.
    Your problem is arising because of the Network Share. iPhoto needs to have the Library sitting on disk formatted Mac OS Extended (Journaled). Users with the Library sitting on disks otherwise formatted regularly report issues including, but not limited to, importing, saving edits and sharing the photos.
    Regards
    TD

Maybe you are looking for

  • How to use the implementation class in propetty pallete

    Hi, I am using forms 10g....I have to insert horizontal scroll bar in text item.. I have only class files instead of jar files ...how cani place the class file instead of jar file... How to use the implementation class in property palette to display

  • Can't set web photo as desktop background

    Hi everyone, I've had my pro for 4 years now, and I used to be able to use any web engine (normally I use google chrome and firefox) and click on a photo on the web and have the option to make it my desktop background. For whatever reason, that optio

  • Variable Input Selection in WAD is not displaying

    Hi  Experts,                    I created a query with one input selection screen. when I use the same query in WAD and execute the template it is not showing any input selection screen, directly showing result. This is supposed to show Hierarchy Inp

  • Reading Texts from Infotype

    Hi, How can we read texts from the Infotype. There is this function module HR_ECM_READ_TEXT_INFOTYPE, but we need the Employee Number, Begin date and End Date as inputs. I just want to check if a field with a particular value exists or not. just like

  • Open an iFS document in Java

    hi, I have two questions: 1) I have a document in folder /public/docs and i want to read its contents from a jsp file. The only method i found in the javadoc is getDocumentContent that returns an InputStream. Still, it requires as a parameter a Docum