Aperture support for AVCHD?

I imagine aperture supports video as well as photo files.  But for some reason I cannot get Aperture to recognise my video files from my Sony 5n shot in AVCHD.  Is there a particular way to import these files?
Thanks

AVCHD is a very compressed HD quality video format. It's designed for creating material to be edited and then the edited version to be exported to a more usable format.
In Video it's common to think in terms of Production and Delivery formats. Production Formats are massive because video creates huge amounts of data. (For instance, an hour of miniDV - a compressed standard def format - will use about 13 gigs of disk space.)  But Production formats are editable at high quality. So the practise is to shoot in production format, then edit, then export the edit to a compressed format like mov, mp4, avi etc. These Delivery formats are excellent quality for viewing, have (relatively) small file sizes but are not good for editing as they are lossy and heavily compressed..
So, if you're not shooting to edit use the other video format on your camera - mov, avi - and if you are shooting to edit, bring the material into your editor - FCP, iMovie - and add the finished product to Aperture.
It's broadly analagous to shooting in Raw, processing and then outputting to Jpeg...
Regards
TD

Similar Messages

  • Where is Aperture support for raw files from Leica X Vario?

    Where is Aperture support for raw files from Leica X Vario?

    It doesn't appear to exist, at this time:
    http://www.apple.com/aperture/specs/raw.html

  • Aperture support for Nikon 1 AW 1

    Is there Aperture # support for Nikon 1 AW 1 .nef file format??

    Frank
    The AW 1 became available about the first of November.
    I'm running Aperture 3.5, OS X Mavericks 10.9, and Digital Camera RAW Compatibility Update 5.01
    What is surprising is that I understood that the AW 1 contained the same sensor etc of the V2. It was the waterproof shockproof body that was the big change.
    Thanks for the quick response.
    Bill

  • Aperture support for unsupported raw formats

    I was doing some tests with Aperture to see if it could fit my workflow. My concern was support of old files from a Nikon Coolpix 5400, raw (thanks to firmware update at the time) as well as a recent Nikon DSLR. No problem with the DSLR. 5400 was not supported. After some internet research I found out there is a pref file (Raw.plist in /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources) that has info about all supported cameras. This add raw support for the cameras listed in the file for Preview, iPhoto, Aperture (system-wide). Same list that Apple provides as camera compatibility list.
    In that list I chose to duplicate the NIKON-E8400 array and renamed it NIKON-E5400. Didn't change any value in the array. To my surprise, even without rebooting, this added support for the Nikon Coolpix 5400 images. The image looks pretty much the same with these default settings (when opened in Preview for example) than it does in ACR in CS2. The only odd difference is the image size loosing 10 vertical pixels (from 2592x1944 opened in ACR CS2 to 2592x1934). I have no idea why it does this but it is no big deal really as it is no scaling, just loss of pixels.
    I am a bit concerned of course about the possibility to carry on this tweak in the next OS updates.
    I guess any raw from any camera could have support this way.
    Just need to name the array in Raw.plist properly. For mine I just opened a raw in text edit and saw first line the name of camera, was "NIKONE5400". I compared the format of this name to other names in the array and decided to add the "-" to look like others so "NIKON-E5400", and that was it. Now I was lucky the default setting for the 8400 I used as a base worked for the 5400, apparently. It could have not been the case and then I would have had to play with the values in the array. Quite a few so a long process I am afraid, but possible.
    The deal would be to release a little utility software that would let us play with these values easily and see a result live on a sample image, and once satisfied it would modify this Raw.plist file. This way people could add support to their own raws.
    If anyone in the know sees a big issue in doing what I did please tell.
    Of course playing with this Raw.plist file is at your own risks so keep backup and bee careful.
    The tweaking of this raw.plist file had been talked about in different forum in the past concerning the support of Canon 3xxD that had a different US name Rebel something. The change of name of the corresponding array added support before an OS update did it for everyone.

    I also modified my Raw.plist file to import RAW files from my Olympus C-5050Z. But that doesn't make Aperture import a type of RAW file it didn't support before. It just turns out that your Nikon 5400 RAW files are the same format as the Nikon 8400 files except for size, just as my Olympus C-5050 files are substantially similar to the Olympus C-7070 files. I think the Raw.plist file used by ImageIO contains hints on how to treat the data and color in the images and as long as the cameras don't behave too differently, substituting one model with another will work.
    The RAW.plist file is a standard plist file that can be examined and modified with the Property List Editor. What I would like to see is documentation of the parameters so that we can more easily add support for cameras that aren't supported out of the box.
    MacBook Pro   Mac OS X (10.4.7)   2.16GHz 2GB RAM 256VRAM

  • Aperture support for Nikon D7100?

    Lightroom now has support for Nikon D7100. Does anybody have any suggestions when Aperture will provid support?

    There has always been, and likely always will be a bit of leap frog, one upsmanship with the timetables for competing developers when adding RAW support for new cameras.  None of the developers who offer solutions for RAW processing have the market cornered in this respect.
    While I too have concerns ... it should be pointed out that the view across the fence is not as attractive as one might think.
    On Oct. 23, 2012, Apple added RAW support and tether support for the Nikon D600 ... while Lightroom did add RAW support for the D600 about the same time, Adobe has yet to offer tether support for the D600.  In fact, Lightroom only supports a small select few cameras for tethering.
    Of course this may not be of interest for Aperture users who do not rely upon the tethering feature ... I simply point out this situation in order to illustrate that Lightroom is not a panacea of perfection ... and don't get me started on how horrid the Lightroom Slideshow and Book modules are compared to what Aperture offers.
    Likely, Apple will offer an update sooner rather than later.

  • Window 7 has native support for AVCHD after the update today

    "21. Improved playback support for video content from digital camcorders and cameras
    Customers loved the increased range of formats natively supported by the Windows 7 Beta, but noticed areas where they wanted broader support. For example, one was unable to seek to a specific spot in the video in Windows Media Player or Windows Media Center for AVCHD content that was imported from a digital camcorder. Weve addressed this. Also, while the support for video from some digital cameras worked great, we also got feedback about supporting a broader set of devices out of the box. Weve since added support for Windows Media Player to natively support the .MOV files used to capture video for many common digital cameras. "
    http://blogs.msdn.com/e7/archive/2009/02/26/some-changes-since-beta.aspx

    Windows media player 11 can play AVCHD very well on windows vista already. And the .MOV native support actually worries me. If that happens, would apple still be making quicktime for windows? will quicktime pro still be on windows? because as far as i know there was no more windows media player on the mac as soon as flip4mac(well, it was made by microsoft..) came out.

  • Aperture support for fuji X-T1 raw files

    How quickly does aperture update for raw files for a recently released camera?

    Thanks for the link, William.  However, from the Aperture site, they don't seem to be in any hurry.  The X-E2 isn't even listed there.  It's hard to know which direction to go with Adobe costing so much more than it used to.  Since I use layers and masks quite a bit, I need to update my raw converter, since I use CS5.

  • Native FCP support for AVCHD

    Hi,
    Does anyone know if Apple has indicated that it plans to eventually support the AVCHD codec natively? If so, could someone point me to where that information might be posted?
    Thanks,

    There was a FCP Supermeet at IBC in Amsterdam last September.
    Apple representatives were at the meet, and indicated somewhat vaguely that native editing would be supported.
    Whether that will be done or not remains to be seen, as well as when and if the revised version of FCS will be released.
    There is a video of the presentations at LAFCPUG.org that you can view.
    http://www.lafcpug.org/ibc08_podcast.html
    Actually, I prefer working in pro res HQ due to its 10-bit and better color space capabilities.
    HDD space is cheap.
    But it's your call, and remember that if it is supported, expect to get the fast CPU you can. It just won't work on anything but.

  • Aperture support for Nikon Coolpix A ?

    Is there any hope of Aperture supporting Nikon Coolpix A NEF in the near future ?

    Nobody here knows.
    Here's the current listing of supported cameras:
    http://www.apple.com/aperture/specs/raw.html

  • Aperture support for RAW Nikon D600.

    Just bought the latest Nikon D600 and when loading RAW images, I'm getting a "Format not supported" error.  It reads the JPEG just fine but not the RAW.  I also have a Nikon D3S and it reads the RAW images just fine.  I'm currently on Aperture V3.2.
    Thanks

    Danl1,
    This is the way it works with every new camera that comes out.
    Untill Apple and Adobe and PhaseOne get a final production sample in their hands, they cannot write the code neccessary to process the RAW files from any manufacturer.
    Some camera makers provide this information pre-release, but most tend to be pretty secretive right up to the end.
    So the solution is to shoot JPG or convert RAW in Nikon's software for the next 2 weeks or so, and by then Aperture and Lightroom and CaptureOne will be up to speed.
    Enjoy your new camera... it looks great!

  • No support for AVCHD video

    Currently Lightroom 4 does not seem to support .m2ts format video, will that change going forward?
    I'd like to be able to get the most out of my Sony A77, or at least be able to down sample it for use.
    Thanks!

    For those of you have trouble on Win 7 64. Please run this test:
    Launch your Windows Task Manager and go to the Processes tab. Is Adobe QT32 Server.exe running?
    If not, go to C:\Program Files\Adobe\Adobe Photoshop Lightroom 4\Support\DynamicLinkMediaServer\dynamiclinkmediaserver\1.0 and execute it from Explorer.
    Verify it is running in the Processes tab of Windows Task Manager
    If it is, attempt an import of a video.
    Please report back what you find.
    thanks.

  • Missing thumbnail images for AVCHD files

    I never had this problem before.
    In the past I would import AVCHD (*.mt2s) video files to the oganizer using Premiere Elements 7.
    Then I would open Photoshop Elements 7 and the video files I just imported in Premiere Elements 7 would display their thumbnails just fine.
    NOW, these thumbnails do not display.
    AVCHD files that I had previously imported still display their thumbnail, but any NEW AVCHD files do not display their thumbnail images; it just displays a default video thubmbnail graphic.
    Furthermore, if I select "Update thumbnail" from the context menu of a previously imported AVCHD file with a thumbnail, then the thumbnail image goes away and siaplays the default graphic.
    (PLEASE NOTE: when I click the default thumbnail image, it opens the video previewer successfully. So the answer is not that the video file is missing and therefore needs to be reconnected to regenerate the thumbnail image. So else is wrong here.)
    How can I get the thumbnail feature to work properly? It works fine in Premiere Elements; the thumbnails images for both new and old imported files display just fine in that program, which is what I used to be able to see in Photoshop Elements. Why is PSE7 not displaying these video thumbnail images?

    I have solved this issue myself a month or two ago and forgot to report my findings.
    I alspo have a Canon HD camcorder so this was a major issue for me.
    The way to resolve this issue (at least in my case) was to download a  codec pack like k-lite. Do a google search for the codec pack or follow this link:
    http://www.codecguide.com/download_kl.htm
    When I installed the codec pack, I think I had to make sure M2TS files were selected within the installation wizard so just be aware of that.
    Another way to resolve this issue is to upgrade to Windows 7. After I upgraded to Windows 7, I did not have to re-install the codec. I think Windows 7 has native support for AVCHD files.
    I hope this helps. If it does, please report here if you encounter anything of note worthy since the details of this process are no longer fresh on my mind.

  • Final Cut Pro Settings For AVCHD Canon HFS100

    Hi friends,
    I am new to Final cut pro and digital video. I just purchased a Canon HFS 100 and am shooting in 30p and am going to be editing on FCP 6.0.1. From Easy Setup on FCP I have changed the FORMAT to HD, RATE to 29.97 and USE to DVCPRO HD -1080p30. Will this be the most favorable settings if I want to make high quality HD videos for the web. Or should I leave it on FCP Easy Setup default which is FORMAT: all formats, RATE: all rates and USE: Custom Setup.
    Thanks.

    Hi Khorsani,
    welcome to the arena.
    Your version of FCP was the [first one|http://www.apple.com/support/releasenotes/en/FinalCut_Pro_6.0_rn/index.html#appleref%3Adoc%3Auid%3ATempBookID-ReplacedWhenAssociatingWithMessierRevision-CH1-SW59 ] to offer some support for AVCHD.
    You want to use Log&Transfer (FCP main menu>File or ShiftCommand8)to convert your footage to ProRes or AIC, which are editable formats that FCP likes.
    http://www.apple.com/support/releasenotes/en/FinalCut_Pro_6.0rn/
    Also [Read this|http://documentation.apple.com/en/finalcutpro/professionalformatsandworkfl ows/index.html#chapter=6%26section=2%26tasks=true] for more general info.
    Connect your camera to your machine, then try to Log&Transfer.
    Please note that AVCHD support was improved with following FCP 6.0.x versions so you may want to update your current version if something does not work.
    To update just click on the Blue Apple of the OS top menu and look for software updates.

  • Intel 960 vs dual Xeon E5520 for AVCHD editing

    Like many people on this forum I am trying to determine the best hardware to purchase for my use of Premiere Pro. For the last several years I have been using Liquid Edition but decided to move over to Premiere because of its support for AVCHD editing.
    I have narrowed my system choice between a single processor i7-960 and a dual processor xeon E5520. From the PPBM4 benchmarks it appears that a 960 system is sligthly ahead of the xeon system which surprises me. However, the results does vary based on task. An added benefit is that the 960 system is cheaper to build. On the other hand, Adobe seems to recommend a dual processor system for HD editing.
    My question is which system is better at AVCHD editing? For the tasks that you routinely do in Premiere which configuration would better suit me?
    Thanks for any help.

    There are a number of things to consider:
    1. Price/performance
    2. Number of CPU's and cores
    3. Clock speed
    4. Memory slots
    5. Overclock ability
    What are the factors in favor of the i7-960 in comparison to dual E5520:
    1. Price/performance
    3. Clock speed
    5. Overclock ability
    so that means that dual E5520 have in in their favor:
    2. Double CPU's and double the number of cores
    4. Twice the memory slots (12 or even 18 versus 6)
    When looking at the PPBM results, the i7-960 @ 3.2 performs around equal to dual E5520 @ 2.26. So effectively double the cores and lower the clock speed gives around the same performance. However, overclocking can have a significant impact as you see in the top results and that is where dual Xeons have a problem. Servertype mobo's are very difficult to overclock if at all (the same applies to Dell XPS BTW, because of their crippled BIOS). But the servertype mobo's have double or triple the memory slots of an X58 mobo and with CS5 around the corner, that may be a distinct advantage, because you can at reasonable prices go for 24 or even 36 GB memory.
    However you remain limited to the standard clock speed and E5520 are not very fast. On the other hand if you were to build the system yourself, you could get an i7-930 at half the price of a i7-960 and overclock it to let's say 3.6 and it will be faster than both a single i7-960 and a dual E5520 at stock speeds.
    Unfortunately, there are no tests specifically for AVCHD (there may be in the future for CS5) so a definite answer can not be given to your question, but keep in mind that all the top scores were achieved with raid configurations, so that is an aspect that should not be forgotten.
    My advise: Depending on your budget, calculate between 30 - 50% of your budget for disks and raid controller. That will probably limit your choices.
    If you have indefinite means available, I would go for dual W5590 or the new Gulftown hexacores, at least 24 GB RAM and an Areca 1880iX-24 with 24 Seagate Cheetah 15K.7 600 GB disks in raid30 and 4 SSD's in raid10 for boot disk. Add a nice nVidia card and a Tesla C2000 co-processor and you are equipped for the next coming years.

  • Yosemite/Aperture 3.6 No Support for Nikon D810/ Raw-S Files ?

    I am thoroughly confused.  I only recently began "drinking the Apple Kool-Aid" and am quite disturbed to learn (after upgrading to Yosemite & Aperture 3.6) that Nikon d810 Raw-S files are NOT supported....
    What gives ?  I mean you pay premium dollars for what is allegedly a premium product (MacBook Pro - Retina latest edition) you have the latest/ greatest software (Yosemite & Aperture 3.6) and the latest/greatest camera (Nikon D810) and one of the file formats is simply "Not supported ?"  Seriously ?? 
    I have had more compatibility issues with Apple and its software since being convinced by all the marketing hype to "drink the Kool-Aid" than I ever had with my ancient Dell XP PC laptop.... 
    Getting back to the point.  Why no Raw-S Support for Nikon d810 ? 
    Will there be support for the Nikon d-810 Raw-S files at some point ? If so, when ? 
    If not, WHY ? 
    What should I do with the 400 photos I took of a high school hockey game in Raw-S format given I am now drinking only the "Apple Kool-Aid?"
    Signed....
    Disgruntled Customer

    Apple can't release it until Nikon supplies them with the required information.
    Apple doesn’t routinely monitor the discussions. These are mostly user to user discussions.
    Send Apple feedback. They won't answer, but at least will know there is a problem. If enough people send feedback, it may get the problem solved sooner.
    Feedback

Maybe you are looking for