Uncompressed AVI crashes to Premiere Pro

Similar Questions

• Cannot display a .avi file in Premiere Pro CS6. We get an error "not supported format or corrupted file.

  I am trying to bring three distinct animations in Premiere Pro, but it won't shoot them in the Source window or timeline of the sequence. The three files are uncompressed .avi files that were returned on in Autodesk Inventor. They are 15 second clips, around 2 GB and 40 fps. I can play them in Windows Media Player without problem. Any ideas on where to start troubleshooting? I can't imagine it's a codec issue, if the files are unzipped?

  Edit: I used MediaInfo to get the info on the video.

  General

  Full name: E:\Videos\13-1011 LAGCOE LED Billboard Video\1250 Drill Pipe elevator Video.avi

  Format                                   : AVI

  Format/Info: Audio Video Interleave

  File size: 2.06 GiB

  Duration: 15s 25ms

  Overall bit rate: 1 180 Mbps

  Video

  ID                                       : 0

  Format                                   : RGB

  Codec ID: 0x00000000

  Identifier of the codec/Info: Basic Windows bitmap format. 1, 4 and 8 bpp versions are palettised. 16, 24 and 32bpp contain raw RGB samples

  Duration: 15s 25ms

  Bit rate: 1 133 Mbps

  Width: 1 280 pixels

  Height: 960 pixels

  Display aspect ratio: 4:3

  Rate: 40,000 fps

  Color depth: 8 bit

  /(pixel*Frame) bits: 23.050

  Stream size: 1.98 Gio (96%)

  > can't imagine it's a codec problem

  Imagine still once your screen printing said they are bitmap files... IE a string of images, not 'really' a video that the Organization recognizes... and a rate of 40 FPS is also "weird".

  Autodesk has other options... to create a file with a 'true' video output codec?

  Because the Assembly is not the same thing as play, you may need to find a codec to be installed to be able to edit (NOT a codec pack!)

  Autodesk has a place where you can download and install 'their' codec to edit files?

• MP4 import crashing of Premiere Pro CS4

  I'm doing a short promo video for my University winter sports club. Just started using first Pro so do not know if it makes a mistake obvious im. I started a project and had imported 2 avi files that come from after effects, an mp3, and sound effects. the first MP4 I imported was fine, its about 400 MB and was filmed on a Gopro headcam. I then tried to import a smaller MP4 in the same project. It crashed the first and every time ive tried. I tried other importers of most MP4 are fine apart from a few much larger files. I also split the file of origanal down in spindles of 50 MB, but it hangs on. I also tried to import into a new empty project with no sucsess. I thought that the file may be corrupted, but they play well and After Effects will load and play them. I have an AMD X 2 4200 Dual, with 2 GB of ram on Windows xp. I also tried transferring the file to different locations, and rename.

  Thank you

  Tom

  This article can be useful...

  http://forums.Adobe.com/thread/668369?TSTART=0

• Import file .mkv of multiplex in Premiere Pro. Error code Timecode.cpp - 1096

  I am trying to edit some .mkv files in Adobe Premiere Pro.  Now, I know that's not possible, but I managed décimalisé the file .mkv with ts muxer and am able to import VIDEO and AUDIO of the original .mkv in Premiere Pro.

  But when I double click on the video to start editing and severed, I get the message:

  [..-.. \src\Timecode.cpp-1096] "crash" Adobe Premiere Pro.

  I am so frustrated, I'm about to pull my hair!  Any help would be appreciated.

  First does not support the mkv.

  You must convert the first to a format with that creation is comfortable.

  Hand brake

• Premiere Pro Crash - Cineform AVI

  Hello

  I use Premiere Pro 2014.2 and I have a problem of crash.  It only crashes with projects that I imported the AVI files I have uncompressed using GoPro studio the cineform codec.  In these projects creation crashed shortly after reading.  I tried to reinstall the first that did not help.  Note that I have not problems to crash if I use MP4 files directly to the output of the camera.

  Grateful if someone could tell me what's wrong.

  Here is the crash error:

  Signature of the problem:

  Problem event name: APPCRASH

  Application name: Adobe first Pro.exe

  Application version: 8.2.0.65

  Application timestamp: 5486db4a

  Fault Module name: ntdll.dll

  Fault Module version: 6.3.9600.17278

  Fault Module Timestamp: 53eebd22

  Exception code: c0000005

  Exception offset: 0000000000038299

  OS version: 6.3.9600.2.0.0.768.101

  Locale ID: 1033

  Additional information 1: 158c

  More information 2: 158c80aea7cf94ac76459cdff23c4c1d

  Additional information 3: 88ad

  Additional information 4: 88ad008462f4eeb30c9bd66127b04103

  Thank you

  Jeremy

  You can be hitting the same problem posted here: Re: Cineform and first 8.2 crashing......

  A collection of customers switching Renderer Software only solved the problem in his case.

• Premiere Pro 2.0 block - deleted Avi

  Hello

  Today, I had to insert a timecode in the film that was part of a project with Premiere Pro 1.5. I installed 2.0 body. I opened the project and I could insert the TC and export it to a Quicktime file. But just after export, Premiere Pro 2.0 crashed. It appeared the message "first found an unexpected error. We will try to save your project. The program stops after a while. I restarted the computer, and when I restarted the program, I discovered that not only my project file had disappear, but also the Avi captured from tape. I got a previous autosave draft but most of the clips are offline. The most surprising thing is that check the working drive, it has the same busy GB he had before "suppression" of the notice. So, I assume that they are always there but one can't read. Is this correct? How can I get back them?

  Thanks in advance for your answers,

  Savarese El Salvador

  Buenos Aires, Argentina

  I'm with Bill because I never saw first delete a project file or real media, even after a mistake like that.  Chances are more than likely that the reported problem is in part due to operator error.

  For example, clips being offline isn't the same as real media being removed from the hard disk.  My strong suspicion is that you have a case of the former, not the last.  If this is the case, then it is also very unlikely that your original project is still on the disk, right where you left it, even though she does not appear in the list of the recent start-up of the first projects.

• Premiere Pro 2015.4 CC once aircraft crashes while after upgrade to 2015.4

  Since the upgrade to first Pro CC 2015.4, I saw repeated application crashes Premiere Pro. In the history of reliability, I see a crash on 8/6, 8/7, 8/8, 8/9, about one per day, each has the same ID of bucket. Seems to be an access violation in GPUFoundation.dll. Here is a copy/paste of the history of reliability of the system that has just occurred. I guess that Adobe brings together the information it automatically, but I'm not 100% sure, so maybe someone knows if the manual reports are needed. Thank you.

  An addendum note: I come to see the accident again... this time I saw what happens right after loading a project and I'm scouring from right to left on a scenario a bit zoomed in. That's all that I have for now but I'll try to get more details.

  Source

  Adobe Premiere Pro 2015.4 CC

  Summary

  Stopped working

  Date

  08/08/2016 11:46

  Status

  Report sent

  Description

  The failing Application path: C:\Program Files\Adobe\Adobe Premiere Pro 2015.3\Adobe first Pro.exe CC

  Signature of the problem

  Problem event name: APPCRASH

  Name of the application: Adobe first Pro.exe

  Application version: 10.4.0.30

  Application timestamp: 579b0be5

  Fault Module name: GPUFoundation.dll

  Fault Module Version: 10.4.0.30

  Timestamp of Module error: 579b 0949

  Exception code: c0000005

  Exception offset: 0000000000006994

  OS version: 10.0.10586.2.0.0.256.48

  Locale ID: 1033

  Information additional 1:5229

  More information 2: 52295558c6c08443a2cf38f99e92bcba

  Additional information 3: 3ccc

  Additional information 4: 3cccd9d61ddac43bb5c86c9492f3469c

  Additional information about the problem

  Bucket ID: 832e8aaf6fbf8e5968300a7c83031636 (120525471915)

  I guess that Adobe is collecting information on this automatically

  You should not.

  Feature request/Bug Report Form

• Premiere Pro crashes on insert or replace edit on 9.2

  Error message:

  

  Description

  The program Adobe first Pro.exe version 9.2.0.41 no longer interact with Windows and was closed. To see if there is more information about the problem, check the history of the problem in the control panel of the center of the Action.

  Process ID: 135 c

  Start time: 01d1dd4cc42368a9

  Time of termination: 4294967295

  Application path: C:\Program Files\Adobe\Adobe Premiere Pro 2015\Adobe first Pro.exe CC

  Report ID: b4f9f7cf-4945-11e6-82a4-5cb901f5a70a

  Faulting full name of the package:

  ID of the failed package-parent application:

  Have HP 2015,2 ZBook core 17 with 16gig Ram version. Randomly, when I try to edit, insert or overwrite, Adobe crashes. Then I edited the same project on a different computer with Adobe 2014, and nothing crashed. I recreated a new project on the original computer edit, import video clips, and it crashed again. Y at - it a bug? I work for a television station in an office more than an hour from the train station. Everything is done remotely. Crashing makes me miss the slot, and that is not acceptable. Need help, is there a better error log that would give you more information?

  Hi bncxlr,

  Yes, there is a bug with dragging clips in the timeline that are longer than the duration set between the points on the 9.2 version and exit. This happens a little when you drag in files longer, as pieces of music. You can remove brands before you drag In/Out or update to the current version, when you have everything ready from new projects.

  Hope that helps,
  Kevin

• Premiere Pro CS6 Crash when clicking on the tab "file".

  Hello, recently I ran on an issue that is extremely frustrating and I can't seem to solve.

  Basically, whenever I try to click on the 'file' tab or any reason, i.e. save or export. I'm greeted by the line of serious misconduct and one unexpected on me.
  The main problem is that I am more able to back up or export project and if I try to use the keyboard to save or export shortcut that causes the crash as well.

  This also happens with any project that I opened.

  Any help please?

  

  Ryba,

  Your video, it seems that you are working with OS X 10.10 and 10.11. It only are not supported OS' in our system requirements for CS6. You must be on 10.9 or an earlier version.

  If you are not working with a certified operating system, you will experience that we can simply not to support unexpected behavior. My advice is to reinstall an earlier version of Mac OS X, which is certified for use with CS6. Otherwise, I would advise updating to a newer version of Premiere Pro.

  Thank you
  Kevin

• CC 2015 - Premiere Pro / Media Encoder crash solution | Win10

  OK, so was super frustrated with the Adobe crashing shit in first and SOUL 2015. It would hard lock my system without warnings or error screens

  I could get it for coding, but not using CUDA causing massive export times - 10 hours for 10 minutes of video

  Windows Pro 10 / 64

  Adobe first Pro CC 2015, latest updates

  Adobe Media Encoder CC 2015, latest updates

  AMD FX-9590 4.7 GHz processor

  16 GB of Ram

  Help - Process Explorer

  Click with the right button on creative cloud and select kill process tree. If you are prompted to allow, click OK.

  

  Low and behold, I use CUDA in PP and the SOUL and the apples to apples 10 hours export is not using CUDA just took 30 minutes using CUDA with no crashes.

  I'm down 3 more exports and feeling very hopefull!

  Looking for any other entry as well...

  But apples to apples for the projects, no restart, among others.

  If you think I'm lying all the time encoding...

  -------------------------------------------------------

  30/05/2016 23:52:03: queue has started

  (Source - file: C:\Users\m9590\AppData\Local\Temp\Syd and Jesse Wedding_CC - 6) warp stabilized.prproj

  -File: Z:\MultiCam Sequence.mp4

  -Preset used: Custom

  -Video: 1920 x 1080 (1.0), 23.976 fps, Progressive, 00:11:37:17

  -Audio: AAC, 160 kbps, 48 kHz, stereo

  -Bitrate: VBR, 2 pass, target 2.00 MB/s, Max 10.00 MB/s

  -Encoding Time: 09:40:11

  31/05/2016 09:32:22: file encoded with success

  31/05/2016 16:48:39: suspended queue

  31/05/2016 16:48:46: queue stopped

  (Source - file: C:\Users\m9590\AppData\Local\Temp\Syd and Jesse Wedding_CC - 6) warp stabilized_1.prproj

  -Output File: Z:\MultiCam Sequence - stable and cultures only.mp4

  -Preset used: Custom

  -Video: 1920 x 1080 (1.0), 23.976 fps, Progressive, 00:10:37:05

  -Audio: AAC, 160 kbps, 48 kHz, stereo

  -Bitrate: VBR, 2 pass, target 2.00 MB/s, Max 10.00 MB/s

  -Encoding Time: 07:16:19

  31/05/2016 16:48:46: encoding failed

  -------------------------------------

  The operation was interrupted by the user

  -------------------------------------

  31/05/2016 17:00:29: queue has started

  (Source - file: C:\Users\m9590\AppData\Local\Temp\Syd and Jesse Wedding_CC - 6) warp stabilized_2.prproj

  -File: Z:\MultiCam Sequence_1.mp4

  -Preset used: Custom

  -Video: 1920 x 1080 (1.0), 23.976 fps, Progressive, 00:10:37:05

  -Audio: AAC, 160 kbps, 48 kHz, stereo

  -Bitrate: VBR, 2 pass, target 2.00 MB/s, Max 10.00 MB/s

  -Encoding Time: 00:30:57

  31/05/2016 17:31:31: file encoded with success

  31/05/2016 17:31:32: queue stopped

  31/05/2016 17:44:31: queue has started

  -------------------------------------------------------

  UPDATE #1

  I just had my first breakdown material editing in Premiere Pro, with CC does not.

  Will keep the changes running WITH CC then kill him before you encode.

  Update 2

  No, it was a moment of random when the SOUL is are featured. Now even with CUDA off, I can't get an export at the end.

  GRRRRR

  Bah to all

  After much frustration I seemed to have solved

  Go into the BIOS you and make sure you have AMD Turbo Core CLEARED completely. Not on auto or something else.

  

  I did 3 hours now exports, WITH CUDA and with my CPU pegged at 65 ° c with ZERO problems

  HUZZAH!

  

• Adobe Premiere Pro cc 2015.2 crashes when exporting

  From one day to the other, Premiere Pro has crashed during editing, but worse: it crashes when exporting.

  Things usually never did not, all of a sudden fool you.

  I've updated my graphics driver, I cleaned my Cache of media, I did a complete reboot and still it crashes. It's a fairly simple change, not even a true documentary, but I can't seem to export

  What is the problem?

  Using Windows 10, i5, Radeon AMD R9 - 270 2GB16GB DDR3

  everything worked great until this week

  Try to create a new project, import the old one in.

• Importing files AVI H.264 in Premiere Pro on Mac

  I work with files from a mobile DVR. The DVR uses H.264 compression and AVI files. Files can be opened and discovered very well on my PC, but cannot be opened on a Mac. To view the files, I have been using a program called Elmedia Player. Files can also be imported into Premiere Pro CS5 or CC. I don't have a first on the PC to be able to try to import here unfortunately.  I've been converting files using Total Video Converter MPEG 4 Pro and then import it in first. It worked, but it seems to drop frames during conversion. Any suggestions on what I can install to be able to import the files into first without making a conversion? If this is not the case, no matter what other converters that people recommend? Any additional info, I missed it would help me?

  Thanks in advance.

  I'm not sure that it will actually work, but try to replace the name extension of AVI to MOV file to 100%.

  Also, I found Flip4Mac (play on your Mac - Telestream Flip4Mac Windows media) very helpful for etc. ASF, ASX, WMV, AVI.

• Premiere Pro constantly crashing

  Video editing on Adobe Premiere Pro CS7. Have a Windows 8.1, Intel Core i7, Geforce 860, 1 TB, 24 GB of RAM.

  Affected by the constant program crashing when you transfer a piece of a clip to a new sequence, crashes every time.

  Never had any problems until I upgraded to windows 10, after upgrade, that I couldn't run the program without crashing, later downgraded to 8.1 & once again I have the same questions.

  Can someone help me? Do I have a hardware problem? What's happening... ?

  Event Viewer says: "error of Application."

  Name of the failing application: Adobe first Pro.exe, version: 6.0.0.0, time stamp: 0x4f7177ec
  Name of the failed module: MSVCR100.dll, version: 10.0.40219.325, time stamp: 0x4df2bcac
  Exception code: 0 x 40000015
  Offset: 0x00000000000761c9
  ID of the process failed: 0 x 1270
  Start time of application vulnerabilities: 0x01d17428c42919f6
  The failing application path: C:\Program Files\Adobe\Adobe Premiere Pro CS6\Adobe first Pro.exe
  Path of the failing module: C:\Windows\SYSTEM32\MSVCR100.dll
  Report ID: 4b0a5180-e01c-11e5-8262-54271e6b9acc
  Faulting full name of the package:
  ID of the failed package-parent application:

  Once again

  Name of the failing application: Adobe first Pro.exe, version: 6.0.0.0, time stamp: 0x4f7177ec
  Name of the failed module: MSVCR100.dll, version: 10.0.40219.325, time stamp: 0x4df2bcac
  Exception code: 0 x 40000015
  Offset: 0x00000000000761c9
  ID of the process failed: 0 x 1048
  Start time of application vulnerabilities: 0x01d17423a1cd01d7
  The failing application path: C:\Program Files\Adobe\Adobe Premiere Pro CS6\Adobe first Pro.exe
  Path of the failing module: C:\Windows\SYSTEM32\MSVCR100.dll
  Report ID: 900f382d-e01b-11e5-8262-54271e6b9acc
  Faulting full name of the package:
  ID of the failed package-parent application:

  Once again

  Name of the failing application: Adobe first Pro.exe, version: 6.0.0.0, time stamp: 0x4f7177ec
  Name of the failed module: MSVCR100.dll, version: 10.0.40219.325, time stamp: 0x4df2bcac
  Exception code: 0 x 40000015
  Offset: 0x00000000000761c9
  ID of the process failed: 0 x 1220
  Start time of application vulnerabilities: 0x01d17423182e0876
  The failing application path: C:\Program Files\Adobe\Adobe Premiere Pro CS6\Adobe first Pro.exe
  Path of the failing module: C:\Windows\SYSTEM32\MSVCR100.dll
  Report ID: c8e80b59-e016-11e5-8262-54271e6b9acc
  Faulting full name of the package:
  ID of the failed package-parent application:

  Help, please!

  OK... to be clear

  You have a version 6.0 of the PProCS6

  Is there a reason any you have not installed the CS6 bug fixes?

  Updates

  Everything has worked with Win8.1 and stopped working with Win10

  Did you clean your drive and do a fresh install of Win8.1?

  Msvcr100.dll is the problem that is listed

  Have you checked Microsoft for more information about C run-time library?

  http://helpx.Adobe.com/x-productkb/global/troubleshoot-c-runtime-errors-products.html

  Also http://www.microsoft.com/en-us/download/details.aspx?id=14632 for a download from Microsoft

  I don't think you have a hardware problem... I think you have a failed upgrade of Win10, and then you did not erase your drive and start over

• Premiere Pro CRASH - always DNxHR Bug 2015.1

  After the last update PP 2015.1 was DNxHR in PP. But now I can't even start PP. It instantly crashes after that I have started with the following information.

  Problemsignatur:

  Problemereignisname: APPCRASH

  Anwendungsname: Adobe Premiere Pro.exe

  Anwendungsversion: 9.1.0.174

  Anwendungszeitstempel: 564dce25

  Fehlermodulname: DNxHR.dll

  Fehlermodulversion: 2.1.0.9

  Fehlermodulzeitstempel: 55352343

  Ausnahmecode: c000001d

  Ausnahmeoffset: 000000000000f4c9

  Betriebsystemversion: 6.1.7601.2.1.0.256.48

  Gebietsschema-ID: 1031

  Zusatzinformation 1: b14f

  Zusatzinformation 2: b14f0bb255ff1fda75b2218f14e23e1b

  Zusatzinformation 3: 1a8d

  Zusatzinformation 4: 1a8d695bd80513a1d5d2f39f3606178d

  System
  Teacher of Win7 64 bit

  AMD Phenom II X 4 965
  XFX AMD R9 380 (Crimson latest driver)

  16 GB DDR3-1333 RAM

  I had weeks of bug before with my old HD 5850 and I thought it was because old graphics card. Now, I've updated the R9 380 and re - install Win7. But ALWAYS the same bug. Come on Adobe, say anything, give us a fix now!

  I read another Thread in this Forum about the same bug, but no Support from Adobe responded. Its ridiculous. I can't use my paid im software. And the worst. This update was one month away, still no correction.

  Any1 has found a solution?

  Hi Matze Ed,

  For a fix, update for first Pro CC 2015 (9.2).

  Thank you

  Kevin

• Premiere Pro CC 2015 crashes when I export the complete sequence

  Hi, I have installed Premiere Pro 2015/Media Enconder 2015 (by selecting delete do not CC 2014 in advanced options) yesterday. Everything seemed to go smooth import, bringing a project from 2014 CC, editing and ranking. But now that I export the sequence, no matter what it crashes. Always! Unless I export fragments of minutes 10 or less of the sequence. Which is a pain because that its a sequence of 65 minutes, which then I import these parts, synchronization and attempt to re-export to see if it works. It takes a good 1-2 hours for each fragment.

  CC 2014 ran smooth, and I waited all this time to update to the CC 2015 to avoid the bugs and problems!

  IM OSX 10.9.6 latest first Pro CC 2015 (updated October 2, 2015). 32 GB of RAM and a RACK of 12 HD mini SAS to.

  Yet once, everything worked smoothly in CC2014.

  I would greatly appreciate any information, solution, entry on that.

  Thank you very much!

  Problem solved! I copied the complete timeline on a new sequence. I also did the digital rebellion of troubleshooting household help and quick fix. Rebooted the system and before, first just crashed and disappeared. Now, he has stopped exporting without crashing and an error message appeared this time highlight the reason: a red giant plugin I was using several plug-ins. I removed the plug-in and everything is fine, in addition to taking 1/4 of the exporting time. The plug ins that I used were the CC version 2015, so there must be a bug. I have this post in case anyone else runs into a problem or similar.