Aperture sometimes slow import slow reaction on highligts and shadows

1. Aperture sometimes, one out of three times perform a slow import from a compactflash card. Normally 10 images (nikon d-200 10 mb) in less than a minute. Sometimes the same ammount takes more than 5 minutes. Reconnecting the cardreader on the front usb connection solves the problem.
2. Using the sliders on highlights and shadows, the adjustment of image takes a little time, no instant reaction.
3. Aperture is installed on a 250 gb hd (first) (standard installation version 1.5.2). The data is installed on a second 500 gb internal drive. Drives never go to sleep. 4GB internal ram. Video card 7300 GT.
I have talked to different people about this performance issue and got different answers, which range from:
a. This is the best performance with aperture with the current system. If you want more buy a better video card.
b. Your video card is bad, mainly the vram. Replace the video card (warrenty still applicable).
Any views and advice from this forum?
Regards
iemke

Mac OS X 10.4.9 to boost image import speeds
By Prince McLean
Published: 09:35 AM EST
Apple this week dropped yet another pair of pre-release Mac OS X 10.4.9 builds on its developer crowd, inching the software closer to a public release.
The diligence with which the Cupertino-based company has been refining the software may signal that Mac OS X 10.4.9 will be the final maintenance update to Mac OS X 10.4 Tiger before attention is drawn solely to Leopard.
As was the case with prior seeds, developer notes accompanying the latest builds -- 8P2132 (Intel) and 8P132 (PowerPC) -- are said to reflect no known issues with the software.
People familiar with the latest pre-release say Apple notes just one significant change since builds 8P2130 and 8P130 were issued last week, specifically a bug fix to ImageIO that was affecting image import speeds.
This is from Apple Insider.
Jeff

Similar Messages

  • Downloading Aperture has slowed down photo editing on my iMac.  Should I delete iPhoto?

    Downloading Aperture has slowed down photo editing on my iMac.  Should I delete iPhoto? 

    So it was only the initial preprocessing after an import of a complete library. If your system drive is nearly full, you should expect performance problems. Try to free at least 20% of your drive.
    I would try to keep your iPhoto Application - it is only 1.1 GB and you may need it later; but you can safely delete the iPhoto Library once you are sure, you imported it successfully. iPhoto can do some things Aperture cannot - e.g. greeting cards, calendars. And it is always nice to have a second application for testing purposes, if something should go wrong.
    But make a backup copy of the iPhoto Library, just in case. Sometimes you will notice years later that a single image not imported correctly, and then you will be glad you still have a backup of the original iPhoto library.
    Regards
    Léonie

  • Why is aperture so slow

    for me aperture is slow to start, slow to operate and slow to shut down?  Am about ready to go back to iPhoto.

    In addition to the reasons Corky02 listed (how much RAM and what kind of processor do you have,BTW?) Aperture may become slow, if your hard drive fills up - keep more then 20% of your hard drive free.
    How long have you been using Aperture? If you are just starting to use Aperture and doing the initial setup of a large library, Aperture still may be busy with the initial processing of thousands of images. It will be much more responsive when this initial processing and indexing has been done.
    You may wish to turn on Aperture's  "Activity" viewer while you observing an an natural slowness - so you can see what tasks are performed and watch the progress. You also may pause tasks (indexing Faces, creation of previews), that you want to postpone and rather run over night. The Activity viewer can be started from Aperture's main Applications Window:
         Window -> Show Activity
    Two more diagnostic utilities (from Applications -> Utitilities) are useful: the "Console" and the "Activity Monitor". These will show you if any processes are crashing or logging diagnostic messages, and also how much processsing time Aperture  is using, or if other processes are competing with Aperture for processing time.
    Apart from the initial import of a large library Aperture may show slowness if you have a serious problem with your library:
    You may have imported a corrupted, incompatibable image
    or your library got corrupted (maybe by using a drive not formatted MAcOS X Extended, or by Force Quitting Aperture).
    Then the Aperture First Aid Tools may be able to fix this: Try to repair the permissions and to repair the library, as describe here:
         Aperture 3: Troubleshooting Basics: http://support.apple.com/kb/HT3805
    Report back, if this does not help.
    Regards
    Léonie

  • Aperture horribly slow on retina 16gb

    Since a few days i am using my new macbook pro retina i7 2.3 16gb ssd. and i am surprised how slow aperture is.
    i used it on a ssd macbookpro 13" i5 with 8gb for 2 years and always was ligtning fast.
    its not useable at all right now. when i scroll to photos (without preview mode) each photo takes up to 1/2 seconds which is just to slow. when i dodge and burn cursor gets choppy, and when i adjust levels it takes 2/3 sec to take any effect.
    Just noticed that when i only browse the cpu goes up to 113%+
    Since i just used it as temp library (later i will import that in my full archive) the library is only a 2.000 to 4.000 images large.
    Here some other information
    Macbook Pro 2.3 i7 16gb ram and 265GB SSD.
    Clean new install mountain lion (only adobe suite, chrome, aperture, dropbox and skype are installed)
    Turned off faces, and geo location in aperture, and also set previews to quality 6 and half size. no other apps running.
    by the way not only aperture gets slow, but when i just did some changes to a image and i command tab into a other app. its slow as well..
    getting crazy
    current activity monitor stats
    ram 12.7 gb used 3.2 free
    1.8 gb swap used
    disk activity small peaks of around 900kb so nothing exciting here
    network almost not used. (so no backup or anything is on
    for cpu with a idle aperture in the background is just normal
    93% idle
    skype uses some 3%
    chrome 2%
    photoshop 1.2%
    my other system is a i5 8gb macbook pro 13" with 8gb of ram and also a SSD and a lot of **** on it, and harddisk for 95% full and that one is lightning fast.
    so im really stuck here :-(

    I did a couple of things to resolve this issue and it was very succesful for me from what I can tell so far.I would like to share this information with everyone. For the record, I recently bought a standard MBP with the i7 2.6GHz CPU, discrete GT650M GPU with DDR5 1GB, and the Hi-Res AG screen. I dropped in 16GB RAM from Crucial and a Samsung 830 512GB SSD. So technically, my MBP with the exception of the retina screen should be pretty identical to the tech inside the rMBP. The SSD I installed also uses the same ATA controller as the Apple OEM NAND in the rMBP.
    Thanks to Linc Davis I used his suggestion to look for memory leaks within the Aperture application and my findings so far seem to dictate that he's probably right. I did some comparison with other editing software that I use and none of those exhibited the same behavior. The leaks detected with the "Aperture" process were exponentially higher than say "Photoshop" or "Elements." I think Apple has some code repair to do with Aperture. They rushed 64-bit and Retina support and somewhere the code got sloppy. As Linc also stated, it's tough to track a memory leak, but I find it strange that Aperture reports more leaks than other similar applications?
    After doing quite a bit of research, because I do like Aperture a lot as a workflow engine, I had to try my best to fix this. Personally, I don't think this has anything to do with our hardware. Everyone on this thread has the maximum amount of memory supported by their MBP's, so there's not much more that can be done here. Also, the rest of the tech is high-quality IMO. The problem I believe is the order that things have flowed with OSX updates, released, the most recent Aperture update, and the move to 64-bit forced by Mountain Lion. That said, here's what I suggest:
    Make sue that you have all of your updates for OSX, Aperture, and iPhoto if you're using a shared library.
    Backup your machine with TM. When this is done, moved on to #3.
    Download "Rember" and test your RAM just to make sure it passes all the checks.
    Check SMART status and make sure your SSD is not reporting any I/O errors. If all is good, continue.
    Download and install the latest version of ONYX 2.6.7.
    Using ONYX, go to the "Cleaning" tab and do a generic cleanup of all the crap on your machine.
    Using ONYX, go the "Maintenance" tab and repair permissions, run all the Scripts, and most important - rebuild Launch Services and the DYLD shared cache.
    Reboot your machine.
    Start Aperture holding down the OPTION and COMMAND keys. You will get prompted to REBUILD the database. Do this, not REPAIR (that does't really help). After the rebuild is complete, launch Aperture.
    Within Aperture, go into PREVIEWS tab, and set "Share previews with iLife and iWork" to NEVER.
    Go ahead and try... what do you think? For me, it runs much better, more reliable for sure.
    Now for the last and most controversial topic that has to do with TRIM. Problem is, people with an rMBP can't disable TRIM support on their SSD from what I can tell. Maybe I'm wrong? However, call me crazy, but when I had the TRIM hack enabled for my SSD, I saw some screwy things happening with I/O during Aperture use. According to everything I read from extremely knowledgeable people of the subject, TRIM is one of those uncertain grey areas. In theory the tech sounds logical, but in reality, I'm not sure if it's impacting I/O by making it unreliable? After all, those commands between the OS and the ATA controller have to be perfect in every way possible - otherwise it will create problems. In the case of Apple usage with there OEM NAND, it seems to be engineered. Can't say the same for Trim Enabler?? Just use caution IMO. Like I said, for me, I saw some weirdness, mainly beachballs. As soon as I disabled the TRIM patch, they went away. If you have a quality SSD like a Samsung or Intel, just rely on the firmware's GC. Do what I do, just let your system sit at the login prompt idle once a week.
    Another suggestion; use the PMSET command and change the default values for 'standbydelay" from 1600 to 86400 (24 hours). This will tell your MBP to stay in standby mode longer and only after 24 hours will it execute 'Standby' mode (which will write memory contents to the SSD - this just burns NAND P/E cycles unnecessarily). Don't know about you, but who the **** leaves their MBP in stanby mode for 30 days (based on Apple's logic)? I use it daily, so 24 hours fof sleep for me is fine. And, the MBP battery is great and can easily stay in sleep mode for at least 7 days untouched. Point is, less hibernation is better. The command is >>
    > sudo pmset -a standbydelay 86400
    Good luck!

  • HT4007 Aperture is Slow - What do I do?

    Almost everything I do in Aperture is slow and it's gotten worse over time.  This doesn't happen with other applications it's specific to Aperture.
    Clicking the import tab takes several seconds.
    Clicking to a project causes a beach ball
    My library is huge. 35,000 pictures
    The Vault requires 178GB.
    I'm running Aperature 3.5.1 on an imac 2011 with 8GB of RAM. Everything is updated.
    What should I do to improve performance?
    Will breaking down the library in to parts help? How do I do that?
    Thank you for your help!
    Bob D. in Huntington Beach.

    My library is huge. 35,000 pictures
    The Vault requires 178GB.
    Is your library on an external or the internal drive? How full is the internal drive? Do you have at least 20GB free on your System drive?
    Do you use plug-ins? If yes, have you checked, if they are compatible?
    When did the slowness start? After updating software or installing new software? After importing new images?
    Will breaking down the library in to parts help? How do I do that?
    The library size alone cannot cause the slowness, so spliting it will probably not help.
    Try to narrow down the problem;
    You may have imported media, that cannot be processed;
    Your library may need fixing,
    your user account may have wrong settings,
    or you may have a system wide problem.
    To check for corrupted media in your Aperture library, launch Aperture, while holding down the Shift key. Is Aperture still slow?
    To check if the library is causing the problem create a small test library - just use the command "File > Switch to Library > Other/new" and create a new library; import a few images and test.  Do you see the same slowness?
    If even a new library does not help, repeat the experiment, but while working in a different user account. Is Aperture more responsive, if you are using a different account?
    Then post back, with the results of your experiment.
    Léonie

  • Impdp over network: sometimes slow

    Hello,
    I've just made an experience, that impdp over network is sometimes slow and sometimes fast:
    My configuration:
    I have a "source" database (lets say A), with version 11.2.0.1, and two "destination" databases B (11.2.0.1) and C (11.2.0.3).
    The data size is about 100 GB. Import from A into B needes about 4.5 hours, and import from A into C takes about 1.5 hours.
    The data which is moved are identical. I've also checked the wait states, and we have found out, that database B makes a lot of log switches
    during import, which is the reason, why database B is such slow. On database C there are almost no log switches.
    B has log switches frequency about one in 2 seconds. C has aprox. 6 log switches in the first 30 minutes (during DATA load).
    That database B has logswitches, and C not let me think about Direct Load versus External Table Load, which is described in the documentation.
    But this seems different when using network_link: the trace of the DW process does not support this information (but should, as described in 552424.1).
    I think, there are some bugs/features fixed/changed between 11.2.0.1 and 11.2.0.3 regarding load strategy over network_link.
    There might be also a chance, that a initial parameter is different between B and C causing to different behavior, but
    Does anyone have a similar observation? Does anyone know about this "change"?
    Additionals:
    The users have all the same grants, the data are exact equal (by FLASHBACK_TIME), remap_schema and remap_tablespace are used at both.
    Ulrich

    Hello,
    Database A is in archive mode, B and C not.
    The problem is in the data transfer, not at index generation.
    For C, the data transfer is 30 min, Index generation is about 1h.
    For B, the data transfer is about 200 min, Index generation in about 1h.
    I have one new information: We have switched back after this to dumpfile transfer, and interesting: With dumpfile, the import is done with Direct Path.

  • Transcoding - sometimes slow, sometimes fast and sometimes not at all?

    This is odd...Sometimes Encore CS5.5 will transcode fast, sometimes slow and sometimes it would't transcode at all. (No errors. Seems like the program stop and go to sleep) And this is on the same project without any changes. I just tried to restart my PC, restart Encore several times, and everytime It wil behave differently. Why?

    These may, or may not, help... but free to read...
    Odd Errors http://forums.adobe.com/thread/670174
    Long File Names or odd characters cause problems
    Read http://forums.adobe.com/thread/588273
    And #4 http://forums.adobe.com/thread/666558
    And This Message Thread http://forums.adobe.com/thread/665641
    Also, make sure you do not have even a 1 frame gap between video files

  • Aperture - Too slow to be really efficient?

    I have been thinking about whether Aperture might be a way to go for me as far as working with my photographs. The ads etc. seemed like it offered some great features and I don't like the Nikon software that has come with my cameras. iPhoto is OK for my family snapshots, but I want more capabilities for my more serious stuff.
    So I when i got an email mentioning the 30 day trial I figured that was a great opportunity to check it out. I was hoping I'd be pleased enough over that 30 days that spending the $300 dollars to buy it would be justified despite the fact that I have Photoshop CS2 and a few other way to organize my photos. Thus far $300 seemed way too steep simply to duplicate capabilities I already have and doesn't come close to offering the capabilities of a full blown image editing app like PS.
    So my question is this. Is this thing really supposed to be as slow as it is? The app is running so slow on my Mac G5 dual 2.5 with Radeon 9600 with 2gb of Apple installed RAM that I can't see suffering through using it long enough to even see if it does some of the things I hope it does. I certainly couldn't see using it rountinely as an app for PRODUCTIVITY. There's nothing productive about an app that takes a good 5 seconds merely to remove a master from the library. Even clicking on an image to look at it takes way too long as the preview refines it's resolution.
    I did a quick search on this issue and saw lots of stuff out there. I have waded through some of it and some of it is enlightening and some just adds to the confusion. Apparently there may be an issue when running dual monitors. Am I understanding that correctly? Seems to me that most Pros and heavy duty amateurs run 2 monitors (and for good reason - most of the apps these days need to screens to display all the neccessary palattes etc.) So if 2 displays hurt performance, I can't see how this is an app that is going to work for me. I certainly don't want to go reconfiguring my Mac simply to go through the latest batch of pics. It also seems to me that a large library could also be an issue - while I don't have huge numbers of images, I do have a couple of thousand that I keep active on my machine (and a ton more on backup DVD).
    So anyway, I'd like to hear from people with a similar setup to mine . . . from your experience is trying to use this app on such a system (which is by no means a slow and incapable Mac at all - I push heavy pixels doing HD work in After Effects and Final Cut all day long and never feel like the apps are too slow to even use)? I am not going to run out and buy a new system simply to run Aperture since. Even if all the bells and whistles are what they seem, they aren't enough to justify it. I also don't want to waste any time using this trial version and learning it's ins and outs if going In know the app won't run efficiently enough.
    So am I crazy? Is this thing really as slow as it seems? Are there really as many speed issues as a search of the forum reveals? Is there something I am missing?

    So am I crazy?
    I have no such evidence.
    Well, give it time.
    In my personal experience, for all practical purposes
    it's unusable on my configuration. A Mac user since
    1986, I purchased my Mac Pro configured specifically
    for Aperture, including an upgraded video card. The
    outcome has been underwhelming.
    As I can't buy a faster computer, I can only assume
    Aperture is suited to hardware yet to be released.
    Aperture is the lowest point in my experience as a
    Mac user.
    I am actually hearing that sentiment more than I would like to as I ask around. Too bad. On the surface it looks quite good. I findit odd that the company that has taken on such great things as it has in the video world can't make this a more efficient piece of software. Perhaps they see much bigger money in the volume that comes from focusing on phones with video and computers for your TV and thus don't really care about an app like Aperature which would really just appeal to dedicated photographers at it's current pricing and probably doesn't rpresent enough revenue - even amongst photogs with cash to burn.
    I'm evaluating Aperture (which I have purchased at
    full retail price) alongside the beta of another
    professional photo app which is yet to be released.
    The jury is still out, but growing restless.
    Yeah, I have played with the Beta from one of the "Others". It was interesting. It was a while ago and that version didn't seem as potentially "robust" as aperture did. But I think it may be time to go back and take another look.

  • Updated to LR 5.4, images now importing extremely slow. After importing and rendering images are still very slow to go through and develop. No issues in LR 5.3 which was very fast.

    After importing and rendering images are still very slow to go through and develop. No issues in LR 5.3 which was very fast. Canon,Nikon, Leica and Fuji files all rendering slow. iMac 2.9 ghz 16gb RAM OSX 10.8.5. Catalogs and images are kept on external drives. Drives running fine. Really need a fix on this since I'm norally imported and processing at least 4,000 images per LR Catalog. Is there way to revert back to 5.3? I can't use 5.4 is its current state. Thanks.

    Download LR 5.3 and install it
    By the way, lots of people have this complaint about LR 5.4, and the advice I give is to use LR 5.3 unless you need one of the new camera models supported by LR 5.4

  • I have an Iphone 4 with IOS 6 and my emails have disappeared.  I also have a very slow reaction time to my touch screen.

    I have an Iphone 4 with IOS 6 and my emails have disappeared.  I also have a very slow reaction time to my touch screen. Help!

    Hello there, parihargs1.
    To troubleshoot display brightness issues the following article provides 2 key steps:
    iPhone: Hardware troubleshooting
    http://support.apple.com/kb/TS2802
    Of note is the following:
    Display has no backlight or dark screen
    Toggle the ringer switch to see if the unit vibrates. If it does, it could be that iPhone is getting power, but is not displaying any image.
    Try turning iPhone off and then on again.
    While connected to the iPhone charger, try to reset the iPhone.
    If the low-battery screen appears, charge the iPhone.
    Display does not adjust brightness automatically
    The ambient light sensor brightens the display when using the iPhone in brightly lit environments, and dims the display in low light. To test this sensor, do the following:
    If the iPhone is in a protective case, remove it from the case. If there is a protective film on the display, remove the film.
    Verify that the Auto-Brightness setting (Settings > Brightness and Wallpaper) is set to ON, and that the Brightness level is set near the middle of the slider.
    Press the Home button to return to the Home screen and then press the Sleep/Wake button to lock the iPhone.
    In a bright environment, cover the top third of the iPhone to block the light, then press the Sleep/Wake button or the Home button to wake the phone. Slide the slider to unlock the phone.
    Notice the brightness of the screen and application icons; they should be somewhat dimmed.
    Remove the cover from the top of the display and in a few moments the display should get brighter.
    If these steps do not resolve your issue please refer to the "Issue not resolved" section for your next step.
    Thansk for reaching out to Apple Support Communities.
    Cheers,
    Pedro D.

  • I have ios5 on iphone 4, but it makes iphone too much slower, release update to improve phone speed, when i touch home button, it have slower reaction, too while i scroll in menu and shuting down the applications, infinity blade is frozing

    i have ios5 on iphone 4, but it makes iphone too much slower, release update to improve phone speed, when i touch home button, it have slower reaction, too while i scroll in menu and shuting down the applications, infinity blade is frozing during video game parts and during playing its 3 or 4x slower reactions, make update for ios5 please,
    - reminders are ok
    - camera- perfect
    - newstand - perfect
    - icloud too

    Hi
    I have a iPhone 4S this is not siri it is actally something to help those who have some sort of disability by reading the screen you can disable this by going to general then go to the bottom to accessability
    Hope this helps you

  • Ever since upgrading to Yosemite, Aperture is slow and basically unusable. Every click results in spinning wheel.

    Ever since the upgrade to Yosemite, my Aperture application will not let me perform any tasks. I have let it run over night and many times to do database repairs etc... and nothing seems to work. Any recommendations on what I can do to help get the application back to a better state?

    and many times to do database repairs etc...
    Have you also rebuild the Aperture Library?
    Have you opened the "Activity" window to check, which tasks Aperture is running? (Window > Show Activity)
    Sometimes Aperture may be trying to process a corrupted image or video over and over again. Then it will help to identify the problematic item and to delete it from the library.
    If you cannot find anything suspicious in the Activity window, try to find out, if your aperture library has a problem by testing with a new, empty Aperture library. Just add a few photos and check, if Aperture is more responsive.
    If Aperture does not even work with a new library, check in a different user account, for example the Guest user.

  • Aperture very slow on mac pro 8 core

    I have a very new mac pro that can't seem to run aperture at a usable speed at all. My 4 year old G5 was able to run it faster, using the same library. When I move between pictures, or even try and change rating, the whole computer comes to a halt and I can't do or click on anything. After about 10 - 30 seconds I can start working again. This is the same with just about any feature in aperture. I have checked the task list and it is empty. This is running with the library on the boot drive and on a secondary drive. The performance is the same. Any ideas??

    Library size does matter, and Aperture doesn't handle big libraries well when it comes to speed. It shouldn't matter but it does.
    My own library is around 65k images and growing rapidly. If I was to have all these images on one drive, or a RAID, and perform a search of an image with spotlight, I would get results in only a few seconds, with Aperture it's like pulling your hair out and is very painful to perform a search.
    If I wanted to search my entire album I must be prepared to watch the spinning beach ball for quite a few minutes, and every click or keyboard type takes another few minutes. I don't know why this is, or why the finder runs rings around Aperture, even iView can perform a whole library search in a matter of seconds.
    I think it is because Aperture is trying to show you all the thumbnails or present a graphical view of all the images when you choose library or all images. All I am doing is asking Aperture to consider all the data in all images before I perform my search, but Aperture wants to do everything.
    I really hope that the engineers work on this issue for version 2, and also come up with a better captioning window than is currently in use. I use PhotoMechanic to caption everything before it even touched Aperture, which makes Apple's programme by post-event workflow rather than my live workflow. An IPTC window such as PhotoMechanic's would be very welcome. If anyone else agrees please add it to the feedback page.
    Anyway, back to the performance. Certain operations, even with plenty of RAM and a good graphics card, can lead to almost snail like performance with large Aperture libraries. I doubt an Octo-Mac (as I like to call them), or even a 50-core Mac with 60Gb RAM and a 20GB video card would make any difference. The application needs updating in that respect.

  • Itunes sometimes slow to launch with Windows XP

    Sometimes itunes opens in about 4 seconds, and sometimes it takes between 10 to 12 seconds before I even see the itunes screen. Is this delay normal? Can anyone explain why this delay only occurs sometimes?
    Thanks in advance for your help.

    I have noticed this too. When using Itunes (without an Ipod) in the past few months, my PC has taken over a minute to boot up Itunes. I often have several other applications open at the same time. I also notice that music that I play in Itunes "jitters" from time to time. Other MP3 playing software (e.g Winamp, Napster, Rhapsody) never lag or "jitter". Is Itunes very RAM demanding versus other programs?
    Today, when connecting a new Ipod Nano for the first two times, it took amost 3 minutes for Itunes to actually appear on the screen! We have not connected a third time yet.
    4G Nano   Windows XP  

  • Running Slow When Viewing Events and Transcoding (and gets hot!)

    Hello community,
    Before you read, please read my specs down below to rule that out.
    So I'm running FCPX version 10.1.1. I just imported a lot of video (almost 1TB). All of it is in 1080p. I did not copy anything in and left it in its original folders. So I am having two problems:
    1. I wanted to transcode all of the video to work better with FCPX. Part of the original media is ProRes 422, but part of it was AVCHD. So after converting the AVCHD to Quicktime (.MOV) files, I went to transcode all of the footage to optimized media during import, but it was painfully slow. It would take 15 minutes to transcode a 10 second clip. My computer would also get very hot during this process (90*C). After multiple attempts, I decided to forgo that and just transcode when I export. If anyone has an answer as to why that is, that would be great.
    Now problem #2.
    2. I am just viewing the media in the events browser to put keywords on the videos. All I am doing is viewing the videos. I have not even created a project or anything. When I'm viewing it, a lot of the clips won't load or play back, and my computer gets really hot (90*C). I can't even scrub over the videos in the event browser because they will be blacked out or blank and won't load. And this fluctuates. Sometimes I will be able to view the media, sometimes I won't and it'll get really hot. It is really slowing down my workflow and it would be great if anyone had an answer. I have reset the PRAM and the SMC and neither of those have worked.
    Thank you!
    System Specifications:
    Mavericks OSX 10.9.3
    Macbook Pro Retina, 15-inch, Late 2013
    16 GB of Ram
    Intel i7 Quad Core - 2.6 GHz
    Intel Iris Pro with Nvidia GeForce GT 750M
    500 GB SSD - 202.44 Free
    Secondary Drive (with all of my video files):
    WD My Passport Ultra HD 2TB - 1.1TB Free

    Your setup should be more than capable of handling that workload.
    There are a few things you did not mention.
    How is the drive connected?
    The most likely explanation for the slowness would be a slow drive. If the drive is only USB2, that would be a bottleneck.
    You can easily test that by running Blackmagic Disk Speed Test. I do this with every drive to see what performance I can expect.
    You mentioned converting AVCHD to mov. You should know you really don't need this. FCP X can import these files directly. It is best to keep the whole AVCHD structure by copying the whole folder or, better yet, use FCP X to create a camera archive. These will be used just as a camera card would, except much faster to import from, being in a hard drive instead of an actual SD card.
    My suspicion is on whichever software you are using to do this conversion. There are a number of low quality converters out there, and if these files have problems they can easily cause FCP X to sweat (pun intended).

Maybe you are looking for

  • EA4500 Open DNS RESOLVER

    Since 2 month now, my ISP (internet service provider) close my internet conenction and say that i have an opendns resolver isue with my router they cant help me with it so i called linksys support line and my router have 1 year old and i need to pay

  • Want to BootCamp, add external HD and go to OS 10.6. Questions

    I've got a MacBook Pro that I bought off Ebay while in Afghanistan, so I'm trying to plan this out and do this all at one time. The MacBook Pro is 2.16 GhZ, 15", 2 Gigs of RAM and 250 G of HD. What I want to do is: dual boot, add external hard drive

  • [Amarok] Problem + pacman thing

    Step by step [root@localhost custompkg]# pacman -R amarok-base error: /var/lib/pacman/local/amarok-base-1.4.5-4/files: No such file or directory error: could not find amarok-base in database [root@localhost custompkg]# pacman -S amarok-base :: amarok

  • HT1338 My download / install is gone from my doc. how do I get it back

    My download / install is gone from my doc. how do I get it back

  • REORG and RUNSTATS: any order of precedence?

    Hi. Is there any documentation on Reorg and Runstats? I am confused about what role each of these play on what table (ex. P, Q, X, Y etc). It all began with ST04 where I tried to manully run the REORG and Runstats (as the ACR was not running OK) and