Premiere Pro and MTS File Format

What versions of Adobe Premiere Pro work with MTS Files?

Assuming you're asking about the AVCHD format, this was supported in CS4 and up.

Similar Messages

No sound in Premiere Pro with .mts files

Hello,
when i import .mts files in Adobe Premiere Pro. There is no sound, why? I can import other other video files, like .mp4 and there is sound.
Please Help!
Premiere Pro detects the most settings false, it said 25p but i recorded with 50i and 1080i

There is Audio in my files, the files are produced by an Sony Legria HF S10. I can play the sound with vlc Media Player, but in Premiere Pro CS 5, they said in the file is no sound!
Other files, like .mp4 had a little speaker on the clip, but .mts files not!
I used the Adobe Premiere Pro CS 5 German Trial.

Premiere 9 and .mts files

Does anyone know if Premiere 9 supports the Canon Vixia .mts files. Is it necessary to convert before importing and editing? I've have not been editing in a while. I still have Elements 2 and my mini dv camera just died. Looking at one of the Vixia HF models and upgrading to elements 9. Any suggestions?

If one only has two physical HDD's, I would do a layout such as this:
C:\ OS, programs and Page File (Windows Virtual Memory)
D:\ Assets, Project and Scratch Disks
If I had three HDD's (physical and NOT partitions), then I would split out the Assets and the Projects/Scratch Disks.
The idea is to spread the I/O load over as many physical HDD's, as is possible. In PrPro circles, users spread Exports to another HDD, and also break out Audio from Video and place those on yet another HDD. The more HDD's, the better for total performance.
Good luck, and hope that helps,
Hunt
PS - though I have one 3x HDD setup and then an 8x HDD setup, I often edit to/from FW-800 HDD's, to migrate my Projects between the laptop and the workstation. In that case, I have all Assets, the Project files and the Scratch Disks on the single external HDD. That is less than ideal for pure performance, but allows the migration, so I live with a bit of a slowdown. This ends up being like a 2 HDD setup, except that the FW-800 external is not as fast as an internal SATA. I live with that setup fine, so if you have only two SATA internals, you will still be ahead of me, with those migrating Projects.

Premiere Pro and .mov files

It is clear there is a problem with variable frame rate on Premiere. I'm reading statements all over the net about it. Okay, cool. I have no choice: I'm using Wirecast and for the last two years all of our shows were shot in Quicktime .mov format. Probably more than 100 of them. When I play them, I get audio artifacts and ultimately the audio falls out of sync, resulting in a 1 to 3 MINUTE lag of the audio at the end of the 1 hour show.
I need to go in and watermark all of these shows and put new opening and closing credits on these shows before I archive them.
What is the fastest way to get Premeire to sync up audio on variable frame rate files? I can't tell you how exhausting it would be to discover I need to import each and every one of these videos into something like Sony Vegas, convert it out and THEN begin my work...
Ideas?
Thanks!

Thanks John! That sent me on a rabbit trail which led to the solution!
Oh... man... Adobe... please PLEASE start listening to your user base! Some of us (read: ME) pay $600 a YEAR to have these massive headaches!
So, User base: let me tell you what I've discovered: If there is a variable frame rate (As there often is with things broadcast to the web), Premiere can't handle it. You must convert it using another program (I used "Handbrake" which is a nifty free converter... be sure to click "Constant bitrate"). And then import it into Premiere.
Doing my due diligence, This actually has been a problem since CS4... I guess few people actually record their broadcasts? Or else they are good with it? Or maybe it's just Wirecast that records variable frame rates... I don't know. Either way, I had a workflow repair.
Now I'm off with ANOTHER problem, my newest project won't work in Premiere EITHER, different workflow, different camera and even a different system.. I'm thinking I need to be asking what formats should I record in so I can actually edit in Premiere? *Sigh*

Nikon D7000 .MOV files in Premiere Pro and After Effects CS5.5

I recently upgraded from Production Premium CS5 to CS5.5. Initially Nikon D7000 .MOV files used in previous CS5 Premiere Pro project would not play well in CS5.5. Now .MOV files do work in both PP and AE CS5.5. Here are the steps I followed. Not recommending you follow my steps exactly, just providing info for those that are interested.
1.       Launch Premiere Pro CS5.5 and open previous PP CS5 project, convert project to CS5.5 and rename project file as not to replace previous CS5 project file.
a.       At this point .MOV files do not play in new project or in AE CS5.5
b.      Close Premiere Pro and After Effect if still running.
2.       Using Adobe Bridge CS5.5, batch rename;
a.       Make copies of original files to new folder location while renaming file extension from .MOV to .mpg
b.      Let Adobe Bridge finish creating all new thumbnail previews.
c.       Leave Bridge running in background.
3.       Launch Premiere Pro CS5.5, let Premiere finish recreating thumbnail previews if needed.
a.       Attempt to preview existing .MOV file in project. It worked for me.
b.      Attempt to play sequence containing .MOV files. It worked for me.
c.       Attempt to play or modify sequence .MOV files in AE CS5.5 via Dynamic Link within Premiere. It worked for me.
d.      Close Premiere Pro project and AE projects if open.
4.       Create new Premiere Pro project and sequence
a.       Import a different Nikon D7000 .MOV file not previously used or renamed.
b.      Attempt to play this newly imported .MOV file. This worked for me as well.
c.       The new, previously un-renamed .MOV file also worked in AE CS5.5 for me.
I will perform additional tests but at the moment Nikon D7000 .MOV files are working for me in CS5.5 after initially performing a batch rename in Bridge CS5.5 from .MOV to .mpg and letting Bridge create preview files. Even .MOV files not renamed now work.
An example of Nikon D7000 footage edited with Adobe Premiere Pro CS5.5, After Effects CS5.5, and Sound Booth CS5 can be seen on my blog, http://stevelandonsmyth.typepad.com/steve-landon-smyths-blog/2011/07/my-first-hd -video-shoot-with-nikon-d7000.html
My system: MacBook Pro 17" 2.3 GHz i7 quad core, 8GB RAM, 500MB SSD
Message was edited by: Steve Landon-Smyth

Hello,
I see 2 post in this thread from Todd that say they are working on a fix and it should be out soon. One is from July, the other from August. It is now Sept 7th and I still see no patches or fixes for any bugs. I spent 400 dollars on an upgrade, but is this upgrade going to be supported?
This is making me rethink upgrading to the .5's in the future.
It is a minor bug to most, but in that sense it should be an easy quick fix. Am I wrong? Is this really a complicated issue?
I apologize if this comes off like a rant, but thats kinda what it is. It is not hard to batch rename files, but its a pain to have to relink all those files in PP.

Premiere Pro and Adobe Media Encoder running slow

Hello everyone,
I'm having trouble with CS4, which is running significantly slower than CS3 did on a older machine. The CS4 suite is installed on a Dell Precision M6400:
Windows Vista 64-Bit
Intel Core 2 Duo CPU T9400 @ 2.53 GHz
8 GB RAM
NVIDIA Quadro FX 2700M Graphics with 512MB dedicated memory
The OS is running on a 57.5 GB HD (C:) and the Adobe suite is installed on a 298 GB Solid State HD (D:), except for Adobe Media Encoder, which is installed on the C: drive.
My project has 4 15-16 minute sequences. The sequences are in DV NTSC, 29.97 fps, My scratch disks are set to a folder on the C: drive. Media Cache Files and the Media Cache Database points to a folder on the D: drive.
These are some of the problems I'm having:
- Premiere Pro CS4 generates peak files every time I open a project
- It then takes 3-5 minutes to render before I can preview a 16-minute sequence
- Adobe Media Encoder takes 5 hours to render a 16-minute sequence (as flv) that has been previously rendered
- AME takes 1 hour to render every 15 minute sequence that has never been rendered before
Are my settings affecting their performance? Is there any way to improve it? Thanks.
(Premiere Pro is the only app that is slow)

The data rate for replay is one thing, the data rate from disk to memory then from memory to CPU and back the other way are different matters and ought not to be confused. It is well-established that for a computer to edit AVCHD you need top end components, and note that I said there were three tasks to distinquish with increasing hardware requirements, namely merely replaying the video, specifying edits in the editor and then the rendering. It is commonly accepted by all the industry vendors that to do remotely commercial AVCHD rendering you need a minimum Quadcore CPU then that eats data fast, in order to not let it go to waste you need a fast motherboard bus fast memory and in order for none of those to go to waste you need the fastest disk set-up you can manage. I in fact have a 4-disk RAID0 volume using SATA (I think the disk model is SATAII but I have to await return from the repair center before I can confirm). For this RAID0 volume I have run speed test software from BlackMagic because I have one of their HDTV capture cards. It recorded that this volume which remember is doing parallelised IO is just fast enough to receive a encoded HDTV stream from the BlackMagic card but too slow to receive an uncompressed HDTV stream, indeed when I tried both I found the volume did keep up with compressed but fell behind with uncompressed. Remember that with a RAID0 volume of 4 SATAII disks a given file gets spread over the four disks and hence IO is spread over those 4 3G/s data lanes. Also remember with these disks 3G/s is just a burst speed, for AVCHD we are interested in sustained serial IO which is much less.
Before my machine broke down, I found that it took 5 hours to render 33 minutes of HDTV albeit as it went along it transcoded from AVCHD to a Microsoft HD format for Vista-only. Another interesting thing is that I found that the longer this render ran the slower it became, the estimated time started at 3 hours but the actual was five and the last one third took maybe 3 hours. Because the machine broke after that run I couldn't figure the bottleneck. For my machine bear in mind that at the repair shop we found that the Quadcore had only half the necessary electrical power plugged in, the monitor software showed however that it constantly ran around 90% of whatever capacity that reduced power supply permitted. Now then we can puzzle over why it got slower and slower and yet CPU consumption remained consistent and near to full capacity, memory was not the bottleneck because that was constant at 6.4G. But you can say that this was maybe performing like a Dualcore and was hitting some sort of wall, if you had a 1 hour render with that rate of degeneration of performance factored in what would happen to the render time, and for 3 hours you could be running indefinitely. I hope when the machine comes back the correct power supply will make it behave like a Quadcore should for this type of application. Anyway I have two theories for the degradation. First is just that PrProCS4 was getting its knickers in a twist and thereby just doing more computation per minute of video to be rendered as time went by, maybe internal resource management related to OO-type programming maybe, or related to disk IO falling behind, both these theories have problems, for the latter the CPU usage should then have dropped also.
Anyways, you need really a Quadcore system and blazing fast disk to work fully with AVCHD commercially, we found an external SATAII disk so if I were you I would just go get one and move on with your life.
Message du 03/06/09 16:08
De : "Jim Simon"
A : "JONES Peter"
Copie à :
Objet : Premiere Pro and Adobe Media Encoder running slow
For AVCHD you MUST have FAST disks.
AVCHD actually has a lower data date than DV. You need lots of CPU muscle, but disk speed is really not a factor specific to AVCHD. Anything that works for DV will work just as well for AVCHD (and HDV as well).
>

Premiere Pro and OWC Qx2 Raid

Hi all,
Wanted to post an issue I am having with Premiere Pro and my newly purchased OWC Raid. I formatted the Raid using OWCs provided software and it seems as though Premiere has not taken kindly to that. I copied some project folders to the OWC and when I opened premiere to relink the files it cannot seem to see or access any of the files on the OWC.
Other users in other forums have stated that the problem can be fixed by reformatting the OWC using Mac's disk utility instead of OWCs. I am currently in the middle of copying files over to other drives so I can do this, but I was wondering if anyone on here had any other solutions.

Overclocking is safe as long as you make sure the temps do not get too high, so it requires good cooling. But if that is OK, there is no negative to overclocking. Look at PPBM5 Benchmark and see how many have overclocked their system, they are all in the top range of performers, example nrs. #8, 13 and 23 with the same generation of your CPU. Even my old system at rank # 48 is still pretty decent for a 920 @ 3.7 MHz.
See Overclocking the i7, a beginners guide.

Premiere pro and media encoder CC problem

Hi guys,
I hope some of you can help me, I installed new version of premiere pro and media encoder CC and now none of them works, I can edit in premiere but as soon as I press export message apears ''sorry a serious error has occurred that requires adobe premiere to shut down'' when I try to open encoder it shut down on startup.
I'm using old IMac 2.4ghz intel core duo, 2gb 667 mhz ddr2 sdram, ATI Radeon HD 2600 Pro 256 MB, OS X 10.8.5.
This is the error report, please help:
Process:
Adobe Media Encoder CC [946]
Path:
/Applications/Adobe Media Encoder CC/Adobe Media Encoder CC.app/Contents/MacOS/Adobe Media Encoder CC
Identifier:
com.adobe.ame.application
Version:
7.2.0.43 (7.2.0)
Code Type:
X86-64 (Native)
Parent Process: launchd [136]
User ID:
501
Date/Time:
2014-02-10 08:44:28.001 +0100
OS Version:
Mac OS X 10.8.5 (12F45)
Report Version: 10
Interval Since Last Report:
1264 sec
Crashes Since Last Report:
1
Per-App Interval Since Last Report: 24 sec
Per-App Crashes Since Last Report:   1
Anonymous UUID:
7E711766-8C55-00D3-811F-852F73421407
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Application Specific Information:
terminate called throwing an exception
abort() called
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib
0x00007fff9483c212 __pthread_kill + 10
1   libsystem_c.dylib
0x00007fff8d74ab24 pthread_kill + 90
2   libsystem_c.dylib
0x00007fff8d78ef61 abort + 143
3   libc++abi.dylib
0x00007fff96ff79eb abort_message + 257
4   libc++abi.dylib
0x00007fff96ff539a default_terminate() + 28
5   libobjc.A.dylib
0x00007fff8f49d887 _objc_terminate() + 111
6   libc++abi.dylib
0x00007fff96ff53c9 safe_handler_caller(void (*)()) + 8
7   libc++abi.dylib
0x00007fff96ff5424 std::terminate() + 16
8   libc++abi.dylib
0x00007fff96ff658b __cxa_throw + 111
9   com.adobe.dvacore.framework
0x000000010022814d dvacore::filesupport::DirHelper::Create() + 813
10 com.adobe.AMEAppFoundation.framework
0x0000000104f285e9 AME::foundation::AppUtils::GetUserPresetDir(bool) + 425
11 com.adobe.Batch.framework
0x0000000105c0a842 AMEBatch::Initialize() + 2194
12 com.adobe.ame.application
0x00000001000273cb AME::app::AMEAppInitializer::AMEAppInitializer(exo::app::AppInitArgs&, std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> >&) + 811
13 com.adobe.ame.application
0x000000010000ad6a AME::app::AMEApp::InitApplication(exo::app::AppInitArgs&) + 2426
14 com.adobe.exo.framework
0x000000010513e77a exo::app::AppBase::Initialize(exo::app::AppInitArgs&) + 1066
15 com.adobe.ame.application
0x00000001000141a8 AME::RunTheApp(exo::app::AppInitArgs&, std::vector<std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> >, std::allocator<std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > > >&) + 1576
16 com.adobe.ame.application
0x0000000100056a38 main + 424
17 com.adobe.ame.application
0x0000000100003f74 start + 52
==========================
Edited by moderator to trim the crash report down to the essentials. Since these forums do not support attaching file (due to legal and security issues), we recommend uploading files using Acrobat.com’s Sendnow (https://sendnow.acrobat.com) or similar services (YouSendit.com, etc.)

Hi mawe81,
Thanks for posting on Adobe forums,
Please follow this document http://adobe.ly/1f2EHCg
and let us know if this fix your issue or not.
Regards,
Sandeep

Premiere Pro and Media Encoder crash while rendering H.264

Very recently, a problem's popped up where Premiere Pro and Media Encoder (CC) will crash while rendering H.264.
It's only while rendering H.264 - other formats seem to work fine.
And I don't mean that it returns an error, I mean it hard crashes with a Windows "Adobe Premiere Pro CC has stopped working" popup.
It doesn't crash at a consistent time during the render, even on the same project. Occasionally, it won't crash at all, but this is usually not the case.
I've tried disabling CUDA and my overclock to no avail. Please help!

On the topic of opening a project on the exact same version of Premiere Pro CC 2014 (yes it is definitely up to date, and the 2014 version), to overcome this export crash problem that ZachHinchy has brought up - you can't. Technically speaking, one should easily be able to open a Premiere Pro CC 2014 project from one system on another system running the exact same up to date, legitimate version of Premiere Pro CC 2014 without any kind of error. But for some reason, this has been disallowed(?) by Adobe. It has facepalm written all over it. Does anyone agree that this is at least a little bit silly?
I have tried exporting a Final Cut Pro XML from my project to try and open the sequence at uni on a Mac, so I can render my project when I finish my edit. It half works - the clips are there, but the sequence is gone - i.e. 12 hours of painstaking sequencing and micro-edits that had me at several points in time wanting to insert my hand through my monitor with enough force to make a large hole. I really cannot afford redo this sequence, as my assignment is due tomorrow, and I have to work at 6 oclock in the morning, so I also cannot afford to stay up till the early hours of tomorrow morning. Wish me luck that some miraculous event has taken place overnight that will somehow allow me to just open my project, on the same version of Premiere, on a Mac, without hassle. (Apple OS is not friendly to anything but its own selfish nature, so I am having doubts).
Adobe please, if you can do anything at all to help, you will save my assignment, and my faith will be restored. Otherwise, I'll just get my money back and buy Final Cut instead.
I cant even
If I find a way to fix either of these problems, I will post straight away.

How much does Premiere Pro and After Effects rely on the hard drive it's installed on?

This may be a really dumb question, but how much does Premiere Pro and After Effects rely on the hard drive it's installed on if all your video files, assets, disk cache, etc are on different drives than the one the program itself is installed on?
The reason I am asking is that I currently have a "relatively" slow Sata II SSD for my C drive that has just my OS (windows 7 64bit) and programs (adobe editing programs, no games) installed on it and nothing else. All of the files used in my projects are saved on either a very fast Sata III SSD or a slower HDD depending on what the files are. For example, disk cache on the Sata III, stills on the HDD.
Being cyber monday I have the opportunity to buy another very fast Sata III SSD to replace my current Sata II SSD C Drive (just OS and programs). Both synthetic and real world benchmarks show a near double in performance. I just want to know if anyone thinks the upgrade is even worth it because for all I know there won't be any increase in performance since no videos, still, cach, etc will be stored on the C Drive.
The alternative is to get a second monitor because I currently only use one 21" monitor.
I suppose another alternative would be to not buy anything on the cyber monday deals and just save money for something else.
Any advice or input would be greatly appreciated. Thanks!

Thanks Alex! I think you are right about not being able to notice the difference between the SSDs. I ended up finding a deal to get about $80 off a great monitor that I've been looking at for a while and decided to pull the trigger on it. I thought about it and realized that there have already been a bunch of times where I want to watch a tutorial on youtube and follow allong in AE or PrePro, but have to keep switching windows. I also frequently want to have my video preview on a separate monitor so I can have a taller timeline window. This monitor will help a lot with that. Thanks again for your help!

I have the Creative suite 6 premium teacher edition installed on a mac and I want to install Premiere Pro and Photoshop ONLY on a separate macbook. How do i do this?

I have the Creative suite 6 premium teacher edition installed on a mac and I want to install Premiere Pro and Photoshop ONLY on a separate macbook. How do i do this?

Get the CS6 installation file and when you run it on the separate machine choose to install only the programs you wish it to have.
CS6 - http://helpx.adobe.com/x-productkb/policy-pricing/cs6-product-downloads.html

I have .MPG and .MTS files on my computer. Can I convert at high quality?

I received .MPG and .MTS files from a friend who shot the video clips on a Sony HDR-CX150, and are now on my computer.
Log and Transfer sadly doesn't work because of the disassembled file structure... Total Bummer.
Will these AVCHD camcorders allow me to throw the footage back on the camera, and THEN perform a log and transfer?
(I don't know if my friend still has the manual)
Side note: I bought Aimersoft Total Video Converter and it seemed to work great, but the quality of the video output is AWFUL. I'm so disappointed.

Try MPEG Streamclip for the MPG files. Lots and Lots of posts explaining its use can be found here on the forum.
Did ClipWrap work on the mts files?
iirc, AVCHD seems to be a one way format. It may be worth reading through the camera manual or going to one a website for the camera to see just to see if going backwards is possible.
Good luck,
x

Why is "edit in Audition" greyed out in Premiere Pro and After Effects?

Since the CC 2014 launch, the option in in Premiere Pro and After Effects to "edit in Audition" is greyed out. Right-clicking a clip in Premiere Pro doesn't have an option for Audition. I cannot send my compositions, sequences or clips to Audition for audio editing. I contacted an Adobe Support personnel earlier this evening. They suggested to go into my Mac's System Preferences and enable a root user, log out of my account, log into the root user, shut down and boot up into safe mode. None of these scenarios worked. It is still greyed out, in both user accounts.
Is this a known issue? I even uninstalled and reinstalled Audition. Still nothing. All my Adobe apps are updated. My Mac is updated. Again, never had this issue before.
I'd appreciate any assistance!
Thank you!
Cheers,
Evan Lockhart

I may have an answer for you, but not sure if my resolution will work for Macs.
First, here's my system and initial info. I'm using a work computer, operating system is Windows 7. I just upgraded to Adobe CC 2014 about a week ago, and I also uninstalled the previous versions of all my Creative Cloud programs after installing the new versions (CC 2014 doesn't just update the previous version, it installs a new program and doesn't automatically uninstall the previous CC programs). Not sure if the uninstall is necessary, for this resolution to work.
Anyway, after I installed Premiere Pro CC 2014 and Audition CC 2014, the Edit Clip in Adobe Audition command was available from the Edit menu in the Menu bar, but was disabled in the right-click menu for the sequence (for the right-click menu, it was visible, but greyed out and disabled). When I tried to use the command from the Edit menu in the Menu bar, it gave me a dialog box to fill out and it created a new folder (titled "Adobe Audition Interchange"). So, the command, when selected from the "Edit menu" obviously uses a different process than the command from the right-click menu. Anyway, I didn't want a new folder created or to fill out a dialog box, I just wanted it to behave like it used to. Basically, when I right-click the sequence and select Edit Clip in Adobe Audition from the right-click menu, it just opens Audition and the audio waveform is visible.
I was able to resolve this and get the right-click command working by reading a couple of articles on this same issue from Adobe CC (not CC 2014) and using those to figure out how to fix this in Adobe CC 2014.
Here's what I did:
I had to locate my .sesx files in my system. They are NOT in the same location as they were for the previous version of CC (at least, they weren't for me). I had to use the Search command and look for .sesx extensions to locate them.
Found them under the path C:>Users>Public>Public Documents>Adobe>Audition>7.0>Session Templates. Note that (for me), there was a folder titled 6.0 on the same level as the 7.0 folder. I selected the 7.0 folder as that folder contained the most recent set of .sesx files. I checked the 6.0 folder and those were the .sesx files from the previous version, so I deleted that folder just as a clean-up step.
I right-clicked on one of the .sesx files in the Session Templates folder and then selected Open with from the right-click menu. The Open with dialog box displays and provides a list of programs.
I selected Adobe Audition CC 2014 from the list of programs (you may have to browse to find it) and then selected Always use the selected program to open this kind of file. I then clicked OK to submit the configuration command and close the Open with dialog box.
I restarted Premiere Pro CC 2014 and the Edit Clip In Adobe Audition command was now enabled on the right-click menu and was working properly.
I wept with joy..... OK, not really, but I'm always irritated at ridiculous regression errors and a lack of thorough testing of new software versions, so I am happy to resolve frustrating issues.
Don't know if this will help you, or if you already resolved your issue. Either way, good luck!
~ Jim

I just installed Adobe CC Premiere Pro and it continuously crashes!

I just installed Adobe CC Premiere Pro and it keeps crashing. I've tried creating a new project, opening an existing project -- nothing works. I can start a new project and get as far as to import clips into the project window but the moment I try to play a clip or create a sequence from it, it crashes. I'm running off a brand new laptop (Lenovo X1 carbon 3rd gen) 8Gb Ram, i5 processor, best of anything I could get on this specific machine. Any thoughts??
The files I'm opening with a new project are MP4 files from a gopro camera. The existing project was a CS5.5 file that it attempted to update to CC -- it actually located all of the files fine and as soon as it gets to the workspace with everything laid out, it crashes. Let me know if I can supply any more information.

I just posted Im having the same issue.
Premiere Pro 2014.2 is crashing
I love PPRO 2014 very much but, wrote an nasty gram to Adobe because each update seems to have issues.
I have set my autosave to 5 min saves and each time I see it say AUTO SAVING I use it as a reminder to do a real save.
I have a super system and it didn't use to crash like this every hour.
Why not try it out for a year and do a major update vs little updates that have issues the last 3 times.
I can't render either with the hardware setting, which did work for a year then, the latest update screwed that up.
The Adobe Tech blamed it on Apple but, hey - it worked for a year until Adobes update.

"The project was saved in a newer version of premiere pro and cannot be opened in this version." - Except it wasn't!

Last night I saved a project I've been working on for a couple of days. It's been fine all along. Today, when I went to open it, it's no longer listed in the recently opened files on startup and i get this message:
"The project was saved in a newer version of premiere pro and cannot be opened in this version."
Except it wasn't! I use Premiere CC and it's been fine all along. I can no longer open it at all...
Any thoughts? Very frustrating!

One more item. In using PP CC2014 for the first time with this project, I have run into multiple issues making this project very frustrating. When adding a sequence to the master sequence, I have to render the audio each time in order to see all of the audio waves. You have to keep doing this over and over, even though you've already rendered a sequence already.
I am getting error messages when rendering the project saying there are issues compiling the movie. Getting same type error message if I try to export. I narrowed it down to two sequences keeping the program from rendering without the error messages. They each had a tiff file. I deleted them and they rendered. Not sure what this issue was with these particular files since I have other tiff files in the project. Once the rendering of all sequences was done, all the individual sequences were closed and the master was the only one open. I didn't close them. So now to edit any of the sequences I have to go back and open them.
The only thing this project has in it are titles created in PP, a few graphics, mostly tiff tiles and some jpeg and the dissolve effect. That's it. Seems like they should have done more with this version before putting it out there. Maybe that's why there are two separate applications for PP? Who knows. I will be uninstalling PP CC2014 when this project is complete.

Premiere Pro and MTS File Format

Similar Messages

Maybe you are looking for