I'm working on a project that is starting to make me think maybe it wasnt worth buying PP CS5.5 The most Important project of my life and it keeps crashing. I shall explain more.
Im working with footage taken on a ProHD camera Info below:
Type: QuickTime Movie
File Size: 3.5 GB
Image Size: 1920 x 1080
Frame Rate: 25.00
Source Audio Format: 48000 Hz - 16 bit - Stereo
Project Audio Format: 48000 Hz - 32 bit floating point - Stereo
Total Duration: 00:13:53:19
Average Data Rate: 4.2 MB / second
Pixel Aspect Ratio: 1.0
QuickTime Details:
Movie contains 1 video track(s), 1 audio track(s) and 1 timecode track(s).
Video:
There are 20844 frames with a duration of 1/25th.
Video track 1:
Duration is 0:13:53:19
Average frame rate is 25.00 fps
Video track 1 contains 1 type(s) of video data:
Video data block #1:
Frame Size = 1920 x 1080
Compressor = XDCAM EX 1080i50 (35 Mb/s VBR)
Quality = Normal (3.00)
Temporal = Normal (3.00)
Audio:
Audio track 1 contains 1 type(s) of audio data:
Audio data block #1:
Format = 16 bit - Stereo
Rate = 48000 Hz
Compressor = 16-bit Big EndianC
Timecode:
Timecode track 1 contains 1 type(s) of data:
Timecode data block #1:
Start Time = 09:37:17:07
Reel name =
When playing back this footage on VLC it works fine and there are no obvious errors or anything strange going on. Playing back in PP was fine when I started the project however once I had aligned 3 cameras, nested them and made a new sequence, dragged the nest across so I could use MultiCam I got my first crash; So I decided to restart the project and just import the one video file which you see above. I cannot play back this file without PP crashing. It crashes generally around the same time code each time. Crash details below:
Faulting application name: Adobe Premiere Pro.exe, version: 5.5.2.0, time stamp: 0x4e960e56
Faulting module name: ImageRenderer.dll, version: 5.5.2.0, time stamp: 0x4e95f50d
Exception code: 0xc0000005
Fault offset: 0x000000000014c59d
Faulting process id: 0x1918
Faulting application start time: 0x01cd094fe9a5fad9
Faulting application path: C:\Program Files\Adobe\Adobe Premiere Pro CS5.5\Adobe Premiere Pro.exe
Faulting module path: C:\Program Files\Adobe\Adobe Premiere Pro CS5.5\ImageRenderer.dll
Report Id: 38e19277-7545-11e1-8746-bcaec52105c2
Fault bucket 48268580, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0
Problem signature:
P1: Adobe Premiere Pro.exe
P2: 5.5.2.0
P3: 4e960e56
P4: ImageRenderer.dll
P5: 5.5.2.0
P6: 4e95f50d
P7: c0000005
P8: 000000000014c59d
P9:
P10:
Now, I have other footage shot with the same camera, same memory card in the same location and this footage works fine in PP.
I cannot even scrub through the video slowlty as this also causes a crash. The only way I have found to solve the issue is to cut out the video at that time stamp and the video seems to play past the affected part. This obviously will not do as my entire project will have to be shot again and considering the fact that the people I was shooting will probably never return to the Uk means I cannot re shoot the video.
There is nothing wrong with the footage. So if anyone knows how tofix this or if you need more information pease let me know
PC Specs:
ACPI X64
Processor: Intel(R) Core(TM) i7 960 @ 3.20GHz 3.60GHz (Watercooled)
RAM: Corsair i7 DDR3 2GB PC12800 1600MHz (x3 or 6GB)
HDD: Samsung 1TB 32MB Spinpoint F3 HD103SJ ATA
GPU: Nvidia GeForce GTX 580 (Watercooled)
Motherboard: ASUS P6X58D-E X58 DDR3 LGA1366
Audio Nvidia HD
1-only way I have found to solve the issue is to cut out the video at that time stamp and the video seems to play past the affected part
2-There is nothing wrong with the footage
1 and 2 contradict each other... if there was nothing wrong with the footage, you would not have to cut the video to get it to play
Have you done this (below) to be sure your sequence matches your video?
The easy way to insure that your video and your project match
See 2nd post for picture of NEW ITEM process http://forums.adobe.com/thread/872666
I know that there is contradiction by saying there is nothing wrong with the footage and then having to cut part of it out to make PP work.
The video files play back perfectly well on other programs and it used to play back perfectly well on PP. Its PP thats causing the issue because PP is the only program that has an issue with the footage. If all other programs play it then it certainly would suggest there is actually nothing wrong with the footage.
I know how to set up a sequence so thats not the issue.
Im sorry if youre looking to the footage or me for a mistake or error but there isnt any, this is a Premiere error not a footage or user error.
More information on the file. I have just downloaded MediaInfo and taken a look at the file. I hope this helps in the quest for a crash free PP.
General
Complete name : F:\Burp.MOV
Format : MPEG-4
Commercial name : XDCAM EX 35
Format profile : QuickTime
Codec ID : qt
File size : 3.45 GiB
Duration : 13mn 53s
Overall bit rate mode : Variable
Overall bit rate : 35.6 Mbps
Encoded date : UTC 2012-03-22 22:50:56
Tagged date : UTC 2012-03-24 01:11:43
©TSC : 2500
©TSZ : 100
Video
ID : 1
Format : MPEG Video
Commercial name : XDCAM EX 35
Format version : Version 2
Format profile : Main@High
Format settings, BVOP : Yes
Format settings, Matrix : Custom
Format settings, GOP : M=3, N=12
Codec ID : xdvc
Duration : 13mn 53s
Bit rate mode : Variable
Bit rate : 34.0 Mbps
Maximum bit rate : 35.0 Mbps
Width : 1 888 pixels
Original width : 1 920 pixels
Height : 1 062 pixels
Original height : 1 080 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 25.000 fps
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Interlaced
Scan order : Top Field First
Compression mode : Lossy
Bits/(Pixel*Frame) : 0.678
Stream size : 3.30 GiB (96%)
Language : English
Encoded date : UTC 2012-03-22 22:50:56
Tagged date : UTC 2012-03-22 22:50:56
Color primaries : BT.709
Transfer characteristics : BT.709
Matrix coefficients : BT.709
Audio
ID : 2
Format : PCM
Format settings, Endianness : Big
Format settings, Sign : Signed
Codec ID : twos
Duration : 13mn 53s
Bit rate mode : Constant
Bit rate : 1 536 Kbps
Channel(s) : 2 channels
Sampling rate : 48.0 KHz
Bit depth : 16 bits
Stream size : 153 MiB (4%)
Language : English
Encoded date : UTC 2012-03-22 22:50:56
Tagged date : UTC 2012-03-22 22:50:56
Menu
ID : 3
Language : English
Encoded date : UTC 2012-03-22 22:50:56
Tagged date : UTC 2012-03-22 22:50:56
Bit rate mode : CBR
I have found a work around for this issue but its not ideal in the slightest. It masively increases file sizes but makes the footage workable.
I downloaded Prism Video File Converter (Free) and converted the videos to .mp4 using a H264 compressor at High quality. Its turned my 3.45 Gb file in to a 15Gb file but PP no longer crashed when playing back the new file.
I'm still very much interested to fond out why PP was crashing in the first place though!
I've been dealing with this for literally about a year. I had it in CS5 all the way till CS5.5.2. Most people experience this when using some sort of still images or graphics, but for me it went to the extent of exporting h.264 files with no effects on them at all.
It finally got so bad that it was crashing as the program was opening.
So I did what any normal person should have done a while ago. Troubleshoot. I figured that not a lot of people were experiencing this issue, so what did I have that was probably differant than other people and that would be my custom built PC.
I ran stress tests on my memory, cpu, and gpu. It turns out that I wasn't letting Prime95 run long enough as it eventually threw some errors. So I went back into my bios and started fresh, as I am overclocking my cpu. After several hrs of tweaking I ran Prime 95 successfully for quite sometime.
I opened up a PP project that had been crashing constantly because I was using heavy graphics, effects, and timelapse stills. After several hrs of editing, rendering, and tweaking effects I am error free.
So long story short I don't know what anybody else's set up is, but check your memory and make sure it is stable. Don't use memtest as it will most likely come back as fine. Run Prime95 for a few hrs and if there is a problem at all it will either throw an error, freeze, BSOD, or restart. If you guys are on Mac's then I don't know what to tell you other than Mac's fail too so make sure you check your hardware components, that is the likely cuplrit.
North America
Europe, Middle East and Africa
Asia Pacific