Skip navigation
austinlingerfelt
austinlingerfelt Calculating status...
Currently Being Moderated

JPGs Dramatically Slow Performance Down on Mac

May 20, 2012 9:00 AM

I've been working with sequences that have jpgs in the new CS6 that come to a crawl when working on them and rendering them.  I'm using a brand new 17" Powerbook with the 2.5 i7 and 16 gb of memory.  The same sequences in CS 5.5 render lightning fast and when I work on them there are no speed or performance issues.

 

When I work on the same sequences in CS6, my computer comes to a crawl.  Rendering is incredibly slow.  If I'm rendering, I can literally hardly do anything else--like visit web sites in Safari or send an e-mail.  I can do it but it's incredibly slow.

 

These are reasonable size jpgs that caused no issues in 5.5.

 

I tried uninstalling CS6 and reinstalling and that didn't help.

2110 Views   23 Replies   Latest reply: vrvince, Jul 23, 2012 6:34 PM
 
Replies
  • Bill Hunt
    Currently Being Moderated
    1. Bill Hunt,
    May 19, 2012 9:54 AM   in reply to austinlingerfelt
    Report

    What are the pixel x pixel dimensions of those JPEG's?

     

    Though PrPro, as of CS 5, has better Scaling algorithms, than before, processing a bunch of unused pixels can require major processing power, and require overhead to handle.

     

    Hunt

     
    |
    Mark as:
  • austinlingerfelt
    Currently Being Moderated
    2. austinlingerfelt,
    May 19, 2012 11:38 AM   in reply to Bill Hunt
    Report

    common size 1986x1324 300dpi

     

    CS 5.5 had no problem shredding through rendering jpg images that size.  CS 5.5. also had no problem manipulating and scaling those jpgs.

     

    Open the same sequences in CS 6 and rendering (plus everything else) comes to a crawl.

     

    When I export a 2-minute sequence that has like 1 jpg, everything goes great until it gets to the jpg; then it slows way down for 10-20 minutes, then speeds back up and finishes.

     

    The issue is definitely with PR CS6.  I have no trouble with 5.5.

     
    |
    Mark as:
  • Jim Simon
    Currently Being Moderated
    3. Jim Simon,
    May 19, 2012 11:40 AM   in reply to austinlingerfelt
    Report

    Have you only tried sequences created in a previous version?  Do you get the same behavior with a new sequence specifically created in CS6?

     
    |
    Mark as:
  • austinlingerfelt
    Currently Being Moderated
    4. austinlingerfelt,
    May 19, 2012 11:45 AM   in reply to Jim Simon
    Report

    Same behavior with fresh new sequence and work from scratch.

     

    Created a new two minute video yesterday (new project, new sequence, fresh work) with 1 layer video, psd title overlay, than use of jpgs in two spots (5 seconds each).  Premiere acted like I was working on a machine 10 years old.

     

    Seems like it renders normally until it gets to the jpgs.

     
    |
    Mark as:
  • Jim Simon
    Currently Being Moderated
    5. Jim Simon,
    May 19, 2012 11:47 AM   in reply to austinlingerfelt
    Report

    OK.

     

    And what exactly is the resolution of those JPEGs?

     
    |
    Mark as:
  • austinlingerfelt
    Currently Being Moderated
    6. austinlingerfelt,
    May 19, 2012 12:02 PM   in reply to Jim Simon
    Report

    The biggest are 1986x1324 300dpi. 

     
    |
    Mark as:
  • Jim Simon
    Currently Being Moderated
    7. Jim Simon,
    May 19, 2012 12:03 PM   in reply to austinlingerfelt
    Report

    Yeah it should handle those fine.  I tested using 3 JPEGs around 5000 x 3000 and they exported just fine and very fast.

     
    |
    Mark as:
  • austinlingerfelt
    Currently Being Moderated
    8. austinlingerfelt,
    May 19, 2012 12:08 PM   in reply to Jim Simon
    Report

    What if you add motion to those jpgs and zoom in/zoom out on them?  Still fast?

     

    What are your specs?

     

    Mine: OSX 10.7.4, 2.5 quad i7, 16 gb of memory, 400 gb free interal drive, 1 tb external fw 800 drive

     

    I made sure there are no updates for my CS6 install.  I'm using the cloud?  Are you using the cloud or the retail, packaged version of CS6?  Trying to figure out what the differences are.

     
    |
    Mark as:
  • Bill Hunt
    Currently Being Moderated
    9. Bill Hunt,
    May 19, 2012 12:52 PM   in reply to austinlingerfelt
    Report

    Thank you for that info.

     

    As Jim says, the sizes, themselves, should not cause any sort of slowdown, as you have very few unused pixels to be processed.

     

    Even with Pan & Zoom (using the Fixed Effects>Motion>Scale and Motion>Position), should not cause any major slowdowns.

     

    Though I do similar, with SD material (NTSC 720 x 480), even using Pans & Zooms, I have had Projects with over 3000 stills, most with some form of animation, that edit smoothly.

     

    Other than the SD vs HD nature, I seldom am working with an Image Sequence, just due to the nature of what I am working with. That could be a variable, but I do not recall reading of major slowdowns, with folk doing Time Lapse, or Stop Motion work WITH Image Sequences. That does not mean that they do not exist, but just that I cannot recall reading of the issues.

     

    Wish that I had more to offer, but good luck,

     

    Hunt

     
    |
    Mark as:
  • Jim Simon
    Currently Being Moderated
    10. Jim Simon,
    May 19, 2012 1:21 PM   in reply to austinlingerfelt
    Report
    What are your specs?

     

    Win 7 64

    i7 2500

    8GB RAM

    1TB hard drive for everything

    Still running the trial

     
    |
    Mark as:
  • austinlingerfelt
    Currently Being Moderated
    11. austinlingerfelt,
    May 19, 2012 2:04 PM   in reply to Jim Simon
    Report

    Make me think this is a Mac specific issue. Bummer.

     
    |
    Mark as:
  • austinlingerfelt
    Currently Being Moderated
    12. austinlingerfelt,
    May 19, 2012 2:37 PM   in reply to austinlingerfelt
    Report

    Going to try uninstalling ALL Adobe sw on my laptop and then reinstall CS6 from the Cloud.

     
    |
    Mark as:
  • austinlingerfelt
    Currently Being Moderated
    13. austinlingerfelt,
    May 19, 2012 6:51 PM   in reply to austinlingerfelt
    Report

    Reinstalled.  No improvement.  Total waste of time.

     

    Trying to work and render.  My computer is now constantly crashing.  Only the Adobe SW is causing problems.  This is the report on the last crash.

     

    Interval Since Last Panic Report:  130775 sec

    Panics Since Last Report:          4

    Anonymous UUID:                    58102DB3-3A0B-4A97-8457-F8393C1CCC1D

     

     

    Sat May 19 19:57:08 2012

    panic(cpu 6 caller 0xffffff80002c473a): Kernel trap at 0xffffff7f8166aa82, type 14=page fault, registers:

    CR0: 0x000000008001003b, CR2: 0x0000000000000014, CR3: 0x000000008468b047, CR4: 0x00000000000606e0

    RAX: 0x0000000000000000, RBX: 0xffffff82069e9890, RCX: 0x0000000000000000, RDX: 0x0000000000000020

    RSP: 0xffffff81d182b400, RBP: 0xffffff81d182b420, RSI: 0xffffff82069e9890, RDI: 0xffffff8033876c00

    R8:  0xffffff80208fe800, R9:  0xffffff80337eaa00, R10: 0x800000008468b047, R11: 0xffffff80002da800

    R12: 0x00000000fffffffe, R13: 0x0000000000000001, R14: 0x0000000000000000, R15: 0xffffff8033876c00

    RFL: 0x0000000000010282, RIP: 0xffffff7f8166aa82, CS:  0x0000000000000008, SS:  0x0000000000000010

    CR2: 0x0000000000000014, Error code: 0x0000000000000000, Faulting CPU: 0x6

     

     

    Backtrace (CPU 6), Frame : Return Address

    0xffffff81d182b0b0 : 0xffffff8000220792

    0xffffff81d182b130 : 0xffffff80002c473a

    0xffffff81d182b2e0 : 0xffffff80002da0cd

    0xffffff81d182b300 : 0xffffff7f8166aa82

    0xffffff81d182b420 : 0xffffff7f8167a0ae

    0xffffff81d182b460 : 0xffffff7f8167a15c

    0xffffff81d182b480 : 0xffffff7f816a3ee6

    0xffffff81d182b4c0 : 0xffffff7f8167959a

    0xffffff81d182b4f0 : 0xffffff7f81679612

    0xffffff81d182b510 : 0xffffff7f8167bc88

    0xffffff81d182b570 : 0xffffff7f8167bfd2

    0xffffff81d182b5c0 : 0xffffff7f8169b24a

    0xffffff81d182bcc0 : 0xffffff7f81699f69

    0xffffff81d182bd20 : 0xffffff7f8165f8a5

    0xffffff81d182bde0 : 0xffffff8000659a78

    0xffffff81d182be40 : 0xffffff80002a3a38

    0xffffff81d182be80 : 0xffffff8000223096

    0xffffff81d182beb0 : 0xffffff80002148a9

    0xffffff81d182bf10 : 0xffffff800021bbd8

    0xffffff81d182bf70 : 0xffffff80002aef20

    0xffffff81d182bfb0 : 0xffffff80002daa33

          Kernel Extensions in backtrace:

             com.apple.ATIRadeonX3000(7.1.8)[BB62D2AF-725C-3D33-8009-C51F397EBB72] @0xffffff7f8164c000->0xffffff7f818e6fff

                dependency: com.apple.iokit.IOPCIFamily(2.6.8)[06C77CAA-586C-3AA7-94B7-A544F47002 5E]@0xffffff7f80883000

                dependency: com.apple.iokit.IONDRVSupport(2.3.2)[D05CFB53-FB72-3613-8162-2D188DB0 4738]@0xffffff7f80cf2000

                dependency: com.apple.iokit.IOGraphicsFamily(2.3.2)[2D2A4A31-EB4F-3730-BE3A-76C06 1685FC5]@0xffffff7f80cba000

     

     

    BSD process name corresponding to current thread: Adobe Premiere P

     

     

    Mac OS version:

    11E53

     

     

    Kernel version:

    Darwin Kernel Version 11.4.0: Mon Apr  9 19:32:15 PDT 2012; root:xnu-1699.26.8~1/RELEASE_X86_64

    Kernel UUID: A8ED611D-FB0F-3729-8392-E7A32C5E7D74

    System model name: MacBookPro8,3 (Mac-942459F5819B171B)

     
    |
    Mark as:
  • austinlingerfelt
    Currently Being Moderated
    14. austinlingerfelt,
    May 19, 2012 6:10 PM   in reply to austinlingerfelt
    Report

    I just changed the video rendering and playback option to software only and that really sped things up on the same sequences I've been having issues with.  Can anyone explain why that would make such a difference?  Does it have something to do with the Macbook Pro?

     
    |
    Mark as:
  • Jeff Bellune
    Currently Being Moderated
    15. Jeff Bellune,
    May 19, 2012 6:57 PM   in reply to austinlingerfelt
    Report

    Please don't post the contents of crash logs beyond the first few lines.  The information it contains is useless to almost anyone who reads the topic, and the extra clutter makes the whole thread difficult to read and navigate.  And if the entire log is requested, please send it via PM instead of posting it in a topic.  Thanks.

     

    Jeff

     
    |
    Mark as:
  • Jeff Bellune
    Currently Being Moderated
    16. Jeff Bellune,
    May 19, 2012 7:01 PM   in reply to austinlingerfelt
    Report

    And please don't double-post.  I deleted your other topic.

     

    Jeff

     
    |
    Mark as:
  • austinlingerfelt
    Currently Being Moderated
    17. austinlingerfelt,
    May 19, 2012 7:24 PM   in reply to Jeff Bellune
    Report

    Jeff,

     

    I am getting complete computer crashes just trying to do basic tasks in Premiere, so that is why I posted a separate topic.  This topic had to do with a specific issue in rendering.  The other topic had to do with Premiere simply crashing in general, giving both a serious error message (subsequently closing down the program) and giving the more fatal error on OSX Lion where the computer locks up and you have to power the entire computer down.

     

    I posted the above error message here, because that's the error message that was generated when Premiere crashed trying to render the sequence I am referring to here.

     

    I came here for help because I am simply trying to get work done.

     
    |
    Mark as:
  • austinlingerfelt
    Currently Being Moderated
    18. austinlingerfelt,
    May 19, 2012 7:30 PM   in reply to austinlingerfelt
    Report

    And Jeff to further reaffirm my point.  I just finished a project, saved it, and quit Premiere and it crashed on quit.  So it is a separate issue.

     

    Process:         Adobe Premiere Pro CS6 [267]

    Path:            /Applications/Adobe Premiere Pro CS6/Adobe Premiere Pro CS6.app/Contents/MacOS/Adobe Premiere Pro CS6

    Identifier:      com.adobe.AdobePremierePro

    Version:         6.0.0 (6.0.0)

    Code Type:       X86-64 (Native)

    Parent Process:  launchd [123]

     

     

    Date/Time:       2012-05-19 21:29:28.252 -0500

    OS Version:      Mac OS X 10.7.4 (11E53)

    Report Version:  9

     

     

    Interval Since Last Report:          136116 sec

    Crashes Since Last Report:           9

    Per-App Interval Since Last Report:  35474 sec

    Per-App Crashes Since Last Report:   8

    Anonymous UUID:                      58102DB3-3A0B-4A97-8457-F8393C1CCC1D

     

     

    Crashed Thread:  0  Dispatch queue: com.apple.main-thread

     

     

    Exception Type:  EXC_BAD_ACCESS (SIGABRT)

    Exception Codes: 0x000000000000000d, 0x0000000000000000

     
    |
    Mark as:
  • Jeff Bellune
    Currently Being Moderated
    19. Jeff Bellune,
    May 19, 2012 7:37 PM   in reply to austinlingerfelt
    Report

    It sounds like you have serious hardware/driver issues.  It's likely that Pr is exposing the problems because other software won't tax your system like Pr does.

     

    I'll give you the choice -- do you want to start a general crashing topic?  If so, I'll delete the crash report posts from here and you can start that topic again (minus the gory crash report details).  If you want to leave the crashing issue in this thread, then keep all of the info and any future responses here.  You can have one or the other, but not both.  If you post the same problem in more than one thread, things get messy very quickly.

     

    Jeff

     
    |
    Mark as:
  • austinlingerfelt
    Currently Being Moderated
    20. austinlingerfelt,
    May 19, 2012 7:39 PM   in reply to Jeff Bellune
    Report

    Just leave it here.

     

    This is a brand new Mac with 10.7.4, all software updates installed.  All Adobe updates installed.  Only other software installed is Office for Mac.  Haven't installed anything else besides Firefox.

     

    I have already tried uninstalling and reinstalling all of the Adobe sw.

     
    |
    Mark as:
  • Jason Van Patten
    Currently Being Moderated
    21. Jason Van Patten,
    May 19, 2012 10:11 PM   in reply to austinlingerfelt
    Report

    austinlingerfelt wrote:

     

    I have already tried uninstalling and reinstalling all of the Adobe sw.

    I have, through recent trials and tribulations of my own, found it nearly impossible to completely clean a Mac of all of Adobe's software so that I could reinstall.  None of the cleaners available can find everything that Adobe writes into various places in the OS.  I actually formatted my Mac Pro and re-installed from scratch, that's how bad it got.

     

    I've left feedback for the developers at Adobe suggesting they clean that garbage up.  CS6 on a Mac is a mess with all of the ancillary applicatons that are needed for it.

     

    As for your OP: it sounds like there's still some work to do on the OpenCL code in Premiere.

     

    jas

     
    |
    Mark as:
  • austinlingerfelt
    Currently Being Moderated
    22. austinlingerfelt,
    May 24, 2012 11:15 AM   in reply to Jason Van Patten
    Report

    I think you're totally right.  Once I set Premiere to do software rendering that solved the issue and the performance became similar to CS 5.5.  It is a disappointment.

     
    |
    Mark as:
  • vrvince
    Currently Being Moderated
    23. vrvince,
    Jul 23, 2012 6:34 PM   in reply to austinlingerfelt
    Report

    I too just upgraded to CS6, and my still-based "videos" with dissolves, pans and scans seem slower. I have late 2011 Macbook Pro 17", using OpenCL via it's AMD Radeon 6770m. I was hoping it would be faster, and not need preview rendering. Regular DLSR video is indeed faster to preview w/o rendering. It's the 12-36MP stills that slow it down (these are way below the 256MP theoretical max.)  Switching to ProjectSettings/General/Renderer: ... Software Only did "help" though we are back to having to render previews.

    Another anomaly: when using OpenCL, and most areas have Yellow bar, hitting Return does not render the Work Area to Green. It just plays it (I guess it is has convinced itself that it should preview fine ;-)

     
    |
    Mark as:
Actions

More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points