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.
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.
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.
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,
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:
dependency: com.apple.iokit.IOPCIFamily(2.6.8)[06C77CAA-586C-3AA7-94B7-A544F470025E]@0xffffff7f808830 00
dependency: com.apple.iokit.IONDRVSupport(2.3.2)[D05CFB53-FB72-3613-8162-2D188DB04738]@0xffffff7f80cf 2000
dependency: com.apple.iokit.IOGraphicsFamily(2.3.2)[2D2A4A31-EB4F-3730-BE3A-76C061685FC5]@0xffffff7f8 0cba000
BSD process name corresponding to current thread: Adobe Premiere P
Mac OS 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)
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.
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.
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 
Path: /Applications/Adobe Premiere Pro CS6/Adobe Premiere Pro CS6.app/Contents/MacOS/Adobe Premiere Pro CS6
Version: 6.0.0 (6.0.0)
Code Type: X86-64 (Native)
Parent Process: launchd 
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
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.
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.
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 ;-)