Pre-render (preview) acts crazy and crashes Premiere - QT Bug?
I have a MacBook Pro 17", 2GB RAM, 2.4 GhZ dual core
Looks like some sort of QT Bug:
I have set my sequence preview settings to render with QT Animation codec. When I preview the sequence, it gets stuck at a specific location on a timeline when it reaches a still image. Then I try to cancel the render, but instead it crashes Premiere. Funny thing, that putting the image at some other location on timeline renders perfect. I have tried everything - I've changed the image to another one - same thing. I've deleted all the preview files - nothing changed. Then I've tried to change the codec in the Sequence Preview Settings and I found out, that when it's on DV-PAL, or I-Frame Only, it renders just fine!!! So I suppose that it's some sort of a bug that is in QT native codec probably... (it only happens to a still image on a specific location on timeline)
As a test, try nesting the problem sequence in a new empty sequence then export that new sequence using QuickTime. Let us know whether or not that succeeds.
Cheers
Eddie
PremiereProPedia (RSS feed)
- Over 350 frequently answered questions
- Over 300 free tutorials
- Maintained by editors like you
Forum FAQ
Similar Messages
-
Is there a way i can set all the videos in my library to pre-render at a lower quality. I use a 2009 mac book pro and it really struggles to play the 1080p 60fps on the fly. But when i render the previews it works fine. Is there a way to have them all rendered and stored so i can use them for viewing instead of using the orginal feed ?
Thankyou for the help!
KieranPress Enter instead of the Space Bar and the bar above your timeline will turn green after the render.
-
2010 Mac Pro began acting crazy: FCPX crashes, and now Fan comes on super loud.
Yesterday I was brining in (importing) 1080p24 HD from my Canon 5DmkII CF card via rocketfish card reader, and everything was going well as per normal, and then very quickly, both my monitors went blue and it almost looked like it was back on-line within less than a second, except FCPX was closed, and then Canon Utility for reading my card opened as though I had just inserted my CF card.
It was really weird and kind of scary - especially the speed of how quickly all this happened. Some of you guys know me, but in short, I've been editing in FCP since it was introduced, and I will list all the improtant details below - but please check this out:
This evening, I booted up my Mac Pro and it started with a new twist; the fan(s) came on like a turbine - louder than ever before, as though it was hotwired to 240 volts! Just the noise of the fan freaked me out and I botted down right away. Does anybody out there know what might be going on?
MacPro 5,1 (late 2010)
2.8 GHz Quad Core
OSX 10.6.8
FCPX 10.0.6 (haven't downloaded the most recent update yet)
Please help if you are familliar with any of the issues listed above! Thanks, Stephenso funny how after all these years working on mac's etc., even if we don't know what's up - it just feels better to know someobdy out there (hello.... hello....) hears me - feels my pain. Yup - first round with my dear first personal Mac Pro was a crazy process of diagnostics and multiple phone calls and the case number and the system scan and upload results - but really nobody knew what was wrong!
I was stunned when they dispatched a guy in a van (complete with ladder) all the way out to Summit County from Denver and he comes upstairs to my "studio" and basically tears my Mac Pro down to the shell, replaces the entire motherboard, reassembles it and gives me a new SN! Seriously - I was almost in shock...
"Where did that motherboard come from? Is it new??? Does this guy know what he's doing??? "Can you just lay all these parts on my carpet like that??? I was pretty nervous.
Anyway - yeah, I feel awful that my fan is maxed out again, but yet I'm doing another AE render anyways. I figure it can't hurt that it's screaming - it's definately not gonna get hot! BUT good suggestion to check the sensor readings! I downloaded smcfancontrol 2.4 and it only had minimums in the custom settings and I didn't see where I could set limits for maximum speeds - really seems like there is no controlling this! -
I'm not exactly sure where I should begin on this issue... re-install?
Thx,
DavidYes, of course. And even if I hadn't, that wouldn't explain Premiere freezing
or crashing. Let me ask this. Is there a maximum amount of clips or some kind of RAM use tipping point where Premiere just can't handle anymore references? That is the only thing I can think of that would possibly cause this sudden glitch or some kind of coding error, like the 'replace with clip from bin' command can only handle 'x' file references somehow... I have about 300 AVCHD clips and 200 HD .mov files in the project panel. What do you think? -
.mxf files not importing and crashing premiere
Hello folks
I am editing an event project for a college class. We used three HVX and recorded onto P2 cards. We used about 8 p2 cards total.
Several of the files and entire folder of the video .mxf files will not import into premiere. I get a box stating it is importing them, but the program will state that it is not responding several moments later and I have to force close the entire project.
I have played these .mxf files on VLC player and they play, so I am unsure of how to get adobe premiere cs6 to accept these files without crashing if I can at all.
Thank you,
JamesI am editing on a school PC (a dell) and it is using windows 7.
It is Adobe Premiere Cs6 I am not aware of any updates that have been updating (ex. patches) or what the internal parts are on the computer.
The video files are in MXF format.
I do not believe the proram is running any thrid party effects or codecs.
A handful of the MXF files will not import into premiere, but instead crash the system. -
Interval Since Last Panic Report: 4781267 sec
Panics Since Last Report: 1
Anonymous UUID: B66F7297-3769-4A9D-B364-210E56ED041A
Wed May 29 12:10:04 2013
panic(cpu 0 caller 0xffffff80002c4794): Kernel trap at 0xffffff8000648642, type 13=general protection, registers:
CR0: 0x000000008001003b, CR2: 0x0000000106ffd000, CR3: 0x00000000243f2026, CR4: 0x00000000000606e0
RAX: 0x000d70d1000201f0, RBX: 0xffffff800b79e200, RCX: 0x0000000001510000, RDX: 0xffffff800b83ec08
RSP: 0xffffff807f4535f0, RBP: 0xffffff807f453630, RSI: 0x0000000000000000, RDI: 0xffffff800f9d3b80
R8: 0x0000000000000000, R9: 0x00000000feb6a675, R10: 0x80000000243f2026, R11: 0x0000000000000000
R12: 0xffffff800b79e200, R13: 0x0000000000000000, R14: 0x0000000000000010, R15: 0xffffff800b83ec00
RFL: 0x0000000000010202, RIP: 0xffffff8000648642, CS: 0x0000000000000008, SS: 0x0000000000000010
CR2: 0x0000000106ffd000, Error code: 0x0000000000000000, Faulting CPU: 0x0
Backtrace (CPU 0), Frame : Return Address
0xffffff807f4532a0 : 0xffffff8000220792
0xffffff807f453320 : 0xffffff80002c4794
0xffffff807f4534d0 : 0xffffff80002da55d
0xffffff807f4534f0 : 0xffffff8000648642
0xffffff807f453630 : 0xffffff7f819e9d14
0xffffff807f453670 : 0xffffff7f819e8174
0xffffff807f4536b0 : 0xffffff7f819e82cc
0xffffff807f453700 : 0xffffff800063baeb
0xffffff807f453740 : 0xffffff7f819e5191
0xffffff807f4537a0 : 0xffffff7f819e4d27
0xffffff807f4537c0 : 0xffffff7f81692c18
0xffffff807f453800 : 0xffffff7f816936e3
0xffffff807f453840 : 0xffffff800063baeb
0xffffff807f453880 : 0xffffff7f81692d0c
0xffffff807f4538b0 : 0xffffff7f81693284
0xffffff807f453b00 : 0xffffff800063baeb
0xffffff807f453b40 : 0xffffff7f81692343
0xffffff807f453b60 : 0xffffff7f8169559f
0xffffff807f453b70 : 0xffffff80006564c7
0xffffff807f453be0 : 0xffffff80006567fc
0xffffff807f453c40 : 0xffffff8000656fbb
0xffffff807f453d80 : 0xffffff80002a3f08
0xffffff807f453e80 : 0xffffff8000223096
0xffffff807f453eb0 : 0xffffff80002148a9
0xffffff807f453f10 : 0xffffff800021bbd8
0xffffff807f453f70 : 0xffffff80002aef10
0xffffff807f453fb0 : 0xffffff80002daec3
Kernel Extensions in backtrace:
com.apple.driver.AppleMultitouchDriver(231.4)[59CCF1E6-A8E0-3CFA-919A-9876EF53E 771]@0xffffff7f81691000->0xffffff7f816a2fff
dependency: com.apple.iokit.IOHIDFamily(1.7.1)[675CB4D0-DEAD-379A-AEAC-7719BFE54EEC]@0xffff ff7f80a1f000
com.apple.driver.AppleBluetoothMultitouch(70.12)[FDCED3EF-FA31-3B5B-9DC4-2300E4 839F56]@0xffffff7f819e4000->0xffffff7f819f1fff
dependency: com.apple.iokit.IOBluetoothFamily(4.0.8f17)[78A0DAAA-F28F-3932-8592-25E6F37E4B3 C]@0xffffff7f80da1000
dependency: com.apple.iokit.IOHIDFamily(1.7.1)[675CB4D0-DEAD-379A-AEAC-7719BFE54EEC]@0xffff ff7f80a1f000
dependency: com.apple.driver.AppleMultitouchDriver(231.4)[59CCF1E6-A8E0-3CFA-919A-9876EF53E 771]@0xffffff7f81691000
dependency: com.apple.driver.IOBluetoothHIDDriver(4.0.8f17)[4C497220-8EE1-3FC2-89F5-C37F5C0 19988]@0xffffff7f80e18000
BSD process name corresponding to current thread: hidd
Mac OS version:
11G63
Kernel version:
Darwin Kernel Version 11.4.2: Thu Aug 23 16:25:48 PDT 2012; root:xnu-1699.32.7~1/RELEASE_X86_64
Kernel UUID: FF3BB088-60A4-349C-92EA-CA649C698CE5
System model name: MacBookPro8,1 (Mac-94245B3640C91C81)
System uptime in nanoseconds: 2245056710616
last loaded kext at 56749812389: com.apple.driver.AppleHWSensor 1.9.5d0 (addr 0xffffff7f817d3000, size 28672)
last unloaded kext at 190897619608: com.apple.driver.AppleUSBUHCI 5.1.0 (addr 0xffffff7f80abb000, size 65536)
loaded kexts:
com.apple.driver.AppleHWSensor 1.9.5d0
com.apple.driver.IOBluetoothA2DPAudioDriver 4.0.8f17
com.apple.driver.AppleBluetoothMultitouch 70.12
com.apple.iokit.IOBluetoothSerialManager 4.0.8f17
com.apple.driver.AppleMikeyHIDDriver 122
com.apple.driver.AudioAUUC 1.59
com.apple.driver.AppleUpstreamUserClient 3.5.9
com.apple.driver.AppleMikeyDriver 2.2.5a5
com.apple.driver.AppleHDA 2.2.5a5
com.apple.driver.AGPM 100.12.75
com.apple.driver.SMCMotionSensor 3.0.2d6
com.apple.driver.AppleIntelHD3000Graphics 7.3.2
com.apple.driver.AppleSMCPDRC 5.0.0d8
com.apple.iokit.IOUserEthernet 1.0.0d1
com.apple.driver.AppleSMCLMU 2.0.1d2
com.apple.Dont_Steal_Mac_OS_X 7.0.0
com.apple.filesystems.autofs 3.0
com.apple.driver.AudioIPCDriver 1.2.3
com.apple.driver.ApplePolicyControl 3.1.33
com.apple.driver.ACPI_SMC_PlatformPlugin 5.0.0d8
com.apple.driver.AppleLPC 1.6.0
com.apple.driver.AppleBacklight 170.2.2
com.apple.driver.AppleMCCSControl 1.0.33
com.apple.driver.BroadcomUSBBluetoothHCIController 4.0.8f17
com.apple.driver.AppleUSBTCButtons 227.6
com.apple.driver.AppleUSBTCKeyboard 227.6
com.apple.driver.AppleIRController 312
com.apple.iokit.SCSITaskUserClient 3.2.1
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless 1.0.0d1
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0d1
com.apple.BootCache 33
com.apple.driver.XsanFilter 404
com.apple.iokit.IOAHCISerialATAPI 2.0.3
com.apple.iokit.IOAHCIBlockStorage 2.1.0
com.apple.driver.AppleUSBHub 5.1.0
com.apple.driver.AppleFWOHCI 4.9.0
com.apple.driver.AppleSDXC 1.2.2
com.apple.iokit.AppleBCM5701Ethernet 3.2.4b8
com.apple.driver.AppleSmartBatteryManager 161.0.0
com.apple.driver.AppleEFINVRAM 1.6.1
com.apple.driver.AppleAHCIPort 2.3.1
com.apple.driver.AppleUSBEHCI 5.1.0
com.apple.driver.AppleACPIButtons 1.5
com.apple.driver.AirPort.Brcm4331 561.7.22
com.apple.driver.AppleRTC 1.5
com.apple.driver.AppleHPET 1.7
com.apple.driver.AppleSMBIOS 1.9
com.apple.driver.AppleACPIEC 1.5
com.apple.driver.AppleAPIC 1.6
com.apple.driver.AppleIntelCPUPowerManagementClient 195.0.0
com.apple.nke.applicationfirewall 3.2.30
com.apple.security.quarantine 1.4
com.apple.security.TMSafetyNet 8
com.apple.driver.AppleIntelCPUPowerManagement 195.0.0
com.apple.driver.AppleMultitouchDriver 231.4
com.apple.driver.IOBluetoothHIDDriver 4.0.8f17
com.apple.iokit.IOSerialFamily 10.0.5
com.apple.driver.DspFuncLib 2.2.5a5
com.apple.iokit.IOSurface 80.0.2
com.apple.iokit.IOFireWireIP 2.2.5
com.apple.kext.triggers 1.0
com.apple.driver.AppleHDAController 2.2.5a5
com.apple.iokit.IOHDAFamily 2.2.5a5
com.apple.iokit.IOAudioFamily 1.8.6fc18
com.apple.kext.OSvKernDSPLib 1.3
com.apple.driver.AppleSMC 3.1.3d10
com.apple.driver.IOPlatformPluginLegacy 5.0.0d8
com.apple.driver.AppleSMBusPCI 1.0.10d0
com.apple.driver.IOPlatformPluginFamily 5.1.1d6
com.apple.driver.AppleGraphicsControl 3.1.33
com.apple.driver.AppleBacklightExpert 1.0.4
com.apple.iokit.IONDRVSupport 2.3.4
com.apple.driver.AppleSMBusController 1.0.10d0
com.apple.driver.AppleIntelSNBGraphicsFB 7.3.2
com.apple.iokit.IOGraphicsFamily 2.3.4
com.apple.driver.AppleUSBBluetoothHCIController 4.0.8f17
com.apple.iokit.IOBluetoothFamily 4.0.8f17
com.apple.driver.AppleThunderboltDPInAdapter 1.8.5
com.apple.driver.AppleThunderboltDPAdapterFamily 1.8.5
com.apple.driver.AppleThunderboltPCIDownAdapter 1.2.5
com.apple.driver.AppleUSBMultitouch 230.5
com.apple.iokit.IOUSBHIDDriver 5.0.0
com.apple.driver.AppleUSBMergeNub 5.1.0
com.apple.driver.AppleUSBComposite 5.0.0
com.apple.iokit.IOSCSIMultimediaCommandsDevice 3.2.1
com.apple.iokit.IOBDStorageFamily 1.7
com.apple.iokit.IODVDStorageFamily 1.7.1
com.apple.iokit.IOCDStorageFamily 1.7.1
com.apple.iokit.IOSCSIArchitectureModelFamily 3.2.1
com.apple.driver.AppleThunderboltNHI 1.6.0
com.apple.iokit.IOThunderboltFamily 2.0.3
com.apple.iokit.IOUSBUserClient 5.0.0
com.apple.iokit.IOFireWireFamily 4.4.8
com.apple.iokit.IOEthernetAVBController 1.0.1b1
com.apple.iokit.IOAHCIFamily 2.0.8
com.apple.iokit.IOUSBFamily 5.1.0
com.apple.driver.AppleEFIRuntime 1.6.1
com.apple.iokit.IOHIDFamily 1.7.1
com.apple.iokit.IO80211Family 420.3
com.apple.iokit.IONetworkingFamily 2.1
com.apple.iokit.IOSMBusFamily 1.1
com.apple.security.sandbox 177.9
com.apple.kext.AppleMatch 1.0.0d1
com.apple.driver.DiskImages 331.7
com.apple.iokit.IOStorageFamily 1.7.2
com.apple.driver.AppleKeyStore 28.18
com.apple.driver.AppleACPIPlatform 1.5
com.apple.iokit.IOPCIFamily 2.7
com.apple.iokit.IOACPIFamily 1.4
Model: MacBookPro8,1, BootROM MBP81.0047.B27, 2 processors, Intel Core i7, 2.8 GHz, 4 GB, SMC 1.68f99
Graphics: Intel HD Graphics 3000, Intel HD Graphics 3000, Built-In, 384 MB
Memory Module: BANK 0/DIMM0, 2 GB, DDR3, 1333 MHz, 0x80CE, 0x4D34373142353737334448302D4348392020
Memory Module: BANK 1/DIMM0, 2 GB, DDR3, 1333 MHz, 0x80CE, 0x4D34373142353737334448302D4348392020
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0xD6), Broadcom BCM43xx 1.0 (5.106.198.19.22)
Bluetooth: Version 4.0.8f17, 2 service, 11 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en1
Serial ATA Device: TOSHIBA MK7559GSXF, 750.16 GB
Serial ATA Device: MATSHITADVD-R UJ-898
USB Device: FaceTime HD Camera (Built-in), apple_vendor_id, 0x8509, 0xfa200000 / 3
USB Device: hub_device, 0x0424 (SMSC), 0x2513, 0xfa100000 / 2
USB Device: Apple Internal Keyboard / Trackpad, apple_vendor_id, 0x0252, 0xfa120000 / 5
USB Device: BRCM2070 Hub, 0x0a5c (Broadcom Corp.), 0x4500, 0xfa110000 / 4
USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x821a, 0xfa113000 / 6
USB Device: hub_device, 0x0424 (SMSC), 0x2513, 0xfd100000 / 2
USB Device: IR Receiver, apple_vendor_id, 0x8242, 0xfd110000 / 3Disconnect all other hardware and test one at a time to see if one of them is responsible.
Next run through this list of fixes, I would try the #3 Hardware Test, write anything down it says and take it into Apple for repair.
..Step by Step to fix your Mac
Next I would run through the list, the #8 Reinstall Just OS X will give you a new copy over itself and may fix your corruption problem in OS X if one exists.
If the crash occurs only when you run certain software or connect a device, consider that a possible cause and look for updates or reinstall or uninstall via the developers procedures.
If that doesn't solve the issue, take the machine to Apple as it might be one of those models that is having issues, but doesn't show up in Hardware Test. -
HELP !!! IdeaPad U510 Touchpad is acting crazy and wierd.
I recently got a lenovo U510 and i find the Trackpad acting all wierd. I did update the Elan Trackpad driver to version 11.4.8.1 but dint seem to get rid of the problem. I am regretting having bought this laptop. Need help .
hi akbp,
In addition to what SEAlaa have suggested, have you tried adjust the sensitivity and palm tracking settings by going to the Control Panel (large icon view) > Mouse:
Screenshot:
Regards
Did someone help you today? Press the star on the left to thank them with a Kudo!
If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"! This will help the rest of the Community with similar issues identify the verified solution and benefit from it.
Follow @LenovoForums on Twitter! -
ProRes files act crazy and transcoding to Animation codec gets ugly
So, allegedly, the Animation codec is lossless. However, when I take something encoded with Apple ProRes 422 HQ and transcode to Animation within the Quicktime Pro software, I see noticeable differences. Including: color change and increased aliasing.
The same is true when attempting to export stills from ProRes, even in the highest, most lossless formats. I am wondering if ProRes for PC is actually not quite ready for prime time? When I import a ProRes file into After Effects, I notice the same quality drop associated with trying to transcode it to a lossless format. It seems as though ONLY QT Pro has the capability to display ProRes files properly. If this is the case, this is largely useless, since I can't then USE these ProRes files for anything. What the heck guys? I wouldn't have had clients deliver me ProRes encoded stuff if I knew that it didn't actually maintain its integrity.
Please help out as soon as possible. Clients with deadlines are waiting on a solution that doesn't involve me spending 4000 grand on a new machine and FCP.As a test, try nesting the problem sequence in a new empty sequence then export that new sequence using QuickTime. Let us know whether or not that succeeds.
Cheers
Eddie
PremiereProPedia (RSS feed)
- Over 350 frequently answered questions
- Over 300 free tutorials
- Maintained by editors like you
Forum FAQ -
How do I pre-render only portions of the timeline or selected clips?
I'm switching from Vegas Pro to Premiere Pro. In Vegas, you select a portion of the timeline, then hit control-B and it pre-renders that segment.
In Premiere, you hit enter, but it doesn't pay attention to the selected clips, it just pre-renders the entire sequence.
This wouldn't be such a big problem except I'm managing projects that are fairly long, with 20-30 sequences and 20 or so nested sequences in each project and I'm switching between around 18 different projects for a series of 23 or so videos.
These vids are already taxing my system resources with only a few minutes or so (referencing about 80-120gb of source footage), but my office comp is kinda weak.
The problem is that when I pre-render a nested sequence and bring it back to the main timeline, I have to pre-render it *again* after making the next set of adjustments (ie color correction, transitions etc). Then I have to do it AGAIN when I copy it to another timeline for another similar project.
Every time, it can take as long as 15 or 20 minutes (my video card is an nVidia GTX 560 Ti, it has CUDA, but prem doesn't support it for some reason).
When my main timeline glitched out, forcing me to split into different projects, it took me almost 4 hours just to copy things into place with the additional 20 minutes to load the glitched file.
Then I had to go and pre-render everything again to work my edits back into place.
Even when everything is 90% correctly laid out, I still have to wait for the entire sequence to finish pre-rendering.
As above, in Vegas Pro, I just select a portion of the timeline and the pre-render sticks to that area.
I saw an article that said you could create in and out points and use that for rendering, but it doesn't seem to be a CS6 thing.
I heard that Adobe was trying to keep CS6 up to date as a parallel thing to CC. Surely I don't have to switch to a $600/year subscription just so I can pre-render portions of the timeline like a lower-end competitor program has had for something like 5 years...?
What am I missing? There has to be a way to do this simply.Are you sure?
I have only 3 options on my Sequence menu.
The first is: Render Effects in Work Area (default shortcut - Enter)
Then: Render Entire Work Area
and: Render Audio
No other Render options are available from that menu.
Oddly, those two things are virtually identical. One of them shows 52 clips, the other showed 57 clips. With 26389 frames (approximately...) ETA is around 20-25 mins. That's not very workflow friendly.
It is smart enough that if I pre-render once, making minor changes later makes for much less pre-rendering work, but because I'm working with so many similar projects and sequences, all of them end up needing to be completely re-pre-rendered even if I'm doing a copy-paste and I need to tweak a few little things in one area of the timeline.
This was especially evident recently when in a 3 hour period, I had to go through 4 revisions and needed to keep my original iterations because the person who made the broad, sweeping decisions was making really bad decisions and I knew I would end up going back to my original plan and making a few comparatively simple changes (which is exactly what happened right after the 3 hours).
Out of 3 hours, I could have lost a good hour and a half just waiting around for pre-rendering stuff that hard already been pre-rendered, but because it had been copy-pasted, Prem couldn't see those previous pre-renders.
I actually only lost around 40 mins. But I had to reshoot footage, including setting up lights and camera angles, plus import and do color correction again thanks to no round-tripping to speedgrade and having shot in other areas with those cameras...
If I had been doing it in Vegas, I would have spent only around 10 minutes doing those pre-renders. Oh and Vegas can use my GPU... I'm an Adobe guy mainly, so it's frustrating to see Vegas win on silly niggles like this. -
Can't render preview on some clips
In my timeline I've got a bunch of clips - some have yellow lines above them in the render bar, some red, some green. And then some have no lines at all, it's these that are the problem.
When I tell it to 'render preview' it will make all the clips with yellow and red lines turn to green just fine, but does nothhing with the clips that have no lines above them at all, it's like it thinks 'these clips are so easy to play I dont need to render preview, they dont have effects or anything on them', however it is sorely mistaken because when I play back the preview everything plays fine except those clips, which stutter and skip (because they are uncompressed HD video).
Is there a way to force every clip to 'render preview', not just the ones Premiere thinks need it?Thanks Colin, here is my info:
General
Complete name : K:\final\1 Introductory\3 Tree Run.avi
Format : AVI
Format/Info : Audio Video Interleave
File size : 56.4 MiB
Duration : 7s 567ms
Overall bit rate : 62.5 Mbpsve
Video
ID : 0
Format : JPEG
Codec ID : MJPG
Duration : 7s 567ms
Bit rate : 60.7 Mbps
Width : 1 280 pixels
Height : 720 pixels
Display aspect ratio : 16:9
Frame rate : 60.000 fps
Color space : YUV
Chroma subsampling : 4:2:2
Bit depth : 8 bits
Scan type : Progressive
Compression mode : Lossy
Bits/(Pixel*Frame) : 1.098
Stream size : 54.7 MiB (97%)
Audio
ID : 1
Format : PCM
Format settings, Endianness : Little
Format settings, Sign : Signed
Codec ID : 1
Codec ID/Hint : Microsoft
Duration : 7s 567ms
Bit rate mode : Constant
Bit rate : 1 536 Kbps
Channel(s) : 2 channels
Sampling rate : 48.0 KHz
Bit depth : 16 bits
Stream size : 1.39 MiB (2%)
Interleave, duration : 946 ms (56.75 video frames)
I am editing it off a seperate hard drive, an external harddrive connected via USB. So that could very well cause it.
I'd like to keep editing it there though, if there's some way I could tell premiere to cache the files even though they look like an agreeable format... -
Preview render playback of multicam sequences causes freeze and crash
I have been editing a timeline with several multicam clips that crashes Premiere anytime I try to play back a rendered preview (green bar) area.
First I render the sequence—playback is initially OK. Then after about 10 minutes, often after I have switched back from another program, without fail the playback will stutter and then freeze altogether on certain clips. Gradually more and more clips on the timeline will 'corrupt' until no playback is possible; the program monitor freezes. When I attempt to Delete Render files, I get the beachball cursor and Ppro locks up completely, prompting a force-quit and sometimes a "serious error has occurred" dialog box and then a crash notice of type "I386_GPFLT"
OSX 10.9.4
MacPro5,1
Nvidia GTX 570
I have tried so far:
-deleting preferences
-deleting cache
-deleting preview files
-swapping graphics cards
-switching to software-only playback
-swapping memory modules
-disabling Mavericks' "compressed memory" function
-changing cache and preview locations to another drive
-importing the project into a new one
The problem only occurs on timelines with multicam sequences. Does anyone else have this issue? Any ideas what's going on?Still encountering this problem after latest update.
-
My project gets an error message and crashes everytime I go to render or preview on AE
I have recently starting using AE on my computer, every now and then its struggled to work but I haven't had any major issues until now.
When I try to render or preview my project I've had an error message pop up saying:
"After Effects error: crash occurred while invoking effect plug-in "Shatter".
then followed by a second message
"After Effects error: Crash in progress. Last logged message was <6492> <getdepthpinflags> <5> 32:32 bit
and finally
"After Effects can't continue: sorry, After Effects has crashed. See http://www.adobe.com/support/products/aftereffects.html for known issues. If you still can't resolve this issue, please contact Adobe Technical Support (2).
it then asks me to save and crashes.
I think it may be to do with my computer specs as it does struggle at times in other areas on AE
can someone tell me if i need to buy something like a new graphics card or something?
I don't have any knowledge when it comes to computer specs so heres a link to all the specifications for my computer: HP Support document - HP Support Center
please help me! need to have this project finished so if I need to buy something new for the computer i need to buy it straight away
thanksHow much ram do you have installed? Which OS? Your link to specs provides no details for your system.
What version of AE are you using down to the last decimal point?
We need to know something about your project. The kind of footage used, the size of the comp you are trying to render, the render settings are all critical information. -
Problem with preview and pre-render
hello Ladies and Gentlemen
my problem is after i do any work(write, add, change) the preview is run automatic and after the pre-render come and ask my if i'll save the video
evry day
can you help my for my problem
sorry for any mistake in ortographeCan you provide some info about your system? Graphics card? Screeen resolution? Operating system? What input device (mouse or tablet)? This error has cropped up elsewhere recently, but since the person asking did not provide any details, we were unable to resolve it. If you are having difficulty posting in English, feel free to use your native language. We have English, French,Spanish, German, Russian and even a bit of Japanese covered by people here, so someone might be able to even answer in that language, provided a solution is available.
Mylenium -
Premiere Pro CC: Pre-Render stalls and hangs occassionally
Hi all,
is everyone else experiencing that after hitting enter to do a quick pre-render, the progress bar pops up but then the system just "hangs". The application doesn't really stop working, but there is no progress.
It almost feels that the application can't find the source material. But it only does it occasionally. Its hard to reproduce reliably, The "Rendering" window appears and then nothing happens. When I click cancel, the system locks up and that is it then. Sometimes it comes back to life, but only sometimes...could not find a pattern here either.
I first thought its my hard drive but then it just happens at times, just as like it had forgotten where to look for the source material. Its very annoying ...I've not seen this myself. How long do you wait for it till you decide it's not working?
I have seen things lock up when hitting Cancel, though. Not sure what that's about.
On a side note, there is no pre-render in PP. Hitting Enter is just a render. -
Premiere Elements 8 and crashes
Question: I have tried all the Adobe recommended fixes due to my NVidia graphics card but my project still regularly crashes and now as soon as it starts loading the elements, it crashes with no error message.
System: Windows 7 Professional (x64) (build 7600)
2.80 gighertz Intel Core i7 860
Multi-core (4 total)
Hyper-threaded (8 total)
64-bit ready
32 kb primary memory cache
8192 kb secondary memory cache
999.99 Gig Usable Hard Drive
748.24 Gig free space
Main circuit Board Gigabyte Technology P55M-UD2
Bus Clock: 133 MH
Bios: Award Software International F11 06/23/2010
4 Gig Memory; 2 Gig each in Slot A0 and A2
Single ATA Hard Drive WDC WEd002FAEX-00Z3A0
NVIDIA GeForce 8400 GS Display Adapter with newest 64 bit driver 266.58
Assets: About 300 still images imported from an album in Photoshop elements shot with a Cannon Power Shot a570 IS
Stills are at 3072 x 2304 or vice version, RGB, 180 resolution
27 short video clips from a Kodak Zi6 converted to avi files by AVS Video Converter
Project: I believe the presets are for NTSC DV although I can't get in to check; they've been this way because I usually shoot video with my Sony VX 2100.
Workflow: I imported the stills in chronological order preceding the first video. Then more stills in chronological order before the next relevant video. I am using the timeline. After each import I save, add transitions (mostly the cross dissolve), save, and render. Sometimes after saving rendered files, the system crashes and when I get back in the files haven't been rendered.
Some vertical stills it accepts just fine. For some others, I have to rotate them.
What I have done: I read all the suggestions from Adobe and the forums for dealing with the NVIDIA card. This is what I have done in the approximate order I have done it:
1. Installed the 8.0.1 update
2. Updted the NVIDIA GeForce 8400 GS driver to the newest 64 bit driver 266.58. I tried to do this update a couple of times. The sytem kept telling me the 260 driver was current but the NVIDIA website said to use the 266.58. I finally got it installed but a little later in the process.
3. I could not disable the Hardware Acceleration as the NVIDIA card would not let me...the option was grayed out.
4. I set both the global and the Premiere Elements threaded optimination to off.
5. I turned off "Enable GPU playback" at one time when I could still get into the program.
6. I recreated the adobe premiere elments plugincache.
7. I uninstalled the Nvidia 3D Stereo driver...it was called Stereo not steroscopic. In the NVIDIA control panel I did not install the Stereoscopic functions.
8. I was still crashing frequently. I was getting the low memory message, so I searched the forums and found directions to change the size of the paging file by clicking Start/accessories/run as administrator/enter at the command prompt BCDEDIT/SET INCREASEUSERVA ####. I started with 3072 then gradually increased as it wasn't helping up to 8000.
9. I think I finally upgraded the driver to the 266.58 at this point.
10. This morning I found directions on how to check the size of the paging file by accessing the control panel. It showed my paging file was only 4096 (I guess the former advice didn't work) and it changed it to a virtual memory minimum of 8000 and a maximum of 10000.
Now I can't get into the program at all. It says it has loaded 100%, then there is a 100 second pause. It starts loading the media and crashes.
I love Adobe products and was a former Adobe Premiere 6.5 user. Premiere Elements as described is perfect for me as a video hobbyist. Please help! I would welcome any more suggestions that I can try. Do you think I should just find a replacement for the NVidia board? If so, what would you recommend. I tend to do long projects. I just can't live with all these crashes.
Sincerely,
Tracy Matern
[email protected]Tracy,
Great job with the details - very well done!
This should be a "poster-child" for how to state details, and a problem.
Now, first thing that I see, regarding the crashes are the size of your still images. Overly-large stills require a ton of resources, and can crash the program, and/or the computer. Scaling of the stills to near the Frame Size of the Project will help greatly, and actually improve the quality of the output. This ARTICLE will give you tips.
Next, with a 64-bit OS, like Win7-64, 4GB of RAM is about the minimum for just the OS. Though PrE cannot use more than the 3.5GB of RAM, as it is still a 32-bit app., but the OS and other programs, certainly can. I would bump that up, if at all possible. Your OS and any other programs, will love you for it.
Off the top of my head, it sounds like you have got the video sub-system well handled, and would look beyond it (for now), to other factors.
You might want to see this ARTICLE on setting up a computer for video-editing sessions, and especially the link to Black Viper's Win7 Tune Up Tips Web site.
Also, check that you have the latest version of Apple's QT Player.
If necessary, there are more troubleshooting tips, and I'll be glad to share those, if necessary.
Thanks for the great post, and good luck,
Hunt
Maybe you are looking for
-
How do I transfer pictures from my email account to my desktop
I get several pics in my email account which is yahoo.com I've created a file on my desktop entitled "emails" . How do I move or copy the pics from my email account to my desktop file?
-
I have Photoshop CS6 Extended but my 3D menu is off
I used the 3D features befored and they worked perfectly, but now I am trying to use it and it wont work. The entire 3D menu is disabled. What can I do?? PLEASE HELP
-
Does wcf 4.5 and onwards support evidence based security. Please refer to some useful links on msdn. Thanks in advance.
-
Hi Everyone Need some help from the experts here as I can't seem to work out how to get all the music on an old iPhone onto a new one. Will try and describe the problem as best I can. My husband will be getting a new iPhone 5 next week, this will be
-
My macbook pro will not let me stay on a certain desktop.
I created multiple desktops and was able to put my open application into different desktops. For example, I had Safari open on one desktop and powerpoint on the second. However, when I switched over from my first desktop to the second it switch back