Porque Premiere Pro CC 2014 antes si reconocia archivos m2ts y ahora no los reconoce

Tengo Premiere Pro CC 2014 desde hace unos meses. El ultimo trabajo lo hice con el con archivos M2T. Llevo trabajando desde la version CS5 sin problemas con este tipo de archivos.
Por un cambio de disco duro de arranque tuve que formatear. Descargue de nuevo de Creative Cloud, Premiere Pro CC 2014 y mi sorpresa fue que al abrir el mismo archivo creado en
el mismo ordenador y con la misma version de Premiere, me dice "Formato de archivo de compresion no admitido". ¿Que puedo hacer para recuperar la posibilidad de seguir editando
este tipo de archivos en Premiere?

Thanks Kevin.
15 days ago undertake a project where work editing a m2t file with other files in Premiere Pro CC 2014. I finished my work and deliver. Use this 150 times m2t file in this project.
7 days ago change my boot disk by one solid state. I had to reformat my hard drive. Then install Premiere Pro CC 2014 and try to open the same project created with Premiere Pro CC 2014 15 days before and tells me that does not support the compression type of this file and no connection appears in red.
This is my problem: if admitted of 15 days before such m2t file after formatting and reinstalling, no longer supported? I have worked with Premiere Pro CS4 and then since I updated to 2014 CC.
I hope this explanation helps you to help me.

Similar Messages

  • New (8/14) Macbook Pro Retina - Premiere Pro CC 2014 spinning beach ball

    Help! Seems my shiny new wiz-bang 4-core Macbook Pro with 16 GB of Ram and a 512 solid state drive works just fine with Adobe Premiere Pro CC 2014 until my project reaches a certain size, then it won't open the project and immediately gives me the deadly spinning beach ball. The only way to exit is to force quit whereupon I get the "Sorry, a serious error has occurred...". Aggravating beyond words.
    Saw one forum comment where it was recommended to update to the 6.0 CUDA driver, but not even sure I have a CUDA driver. Plenty of space left on hard drive. In Premiere Pro preferences under the "Memory Tab" it doesn't seem to matter if it's set to "Optimize rendering for.... Memory or Performance." I've reinstalled the Premiere Pro App twice. Doesn't help.
    Some specs:
    Processor  2.5 GHz Intel Core i7
    Memory  16 GB 1600 MHz DDR3
    Graphics  Intel Iris Pro
    NVIDIA GeForce GT 750M GPU PCie
    Intel Iris Pro GPU Built-in
    8 GB DDR# 1600 MHz (x2) = 16 GB RAM
    350 GB of 499 GB left on drive
    Of the 16 GB of RAM I have 11 available for Premiere Pro and the other 5 GB allocated for other apps.
    Any suggestions would be greatly appreciated.

    >NVIDIA GeForce GT 750M GPU PCie
    >Intel Iris Pro GPU Built-in
    Dual graphics adapters are a bane on civilization!!!
    -http://helpx.adobe.com/premiere-pro/kb/error---preludevideo-play-modules.html
    -http://forums.adobe.com/thread/1001579
    -Use BIOS http://forums.adobe.com/thread/1019004?tstart=0
    -link to why http://forums.adobe.com/message/4685328
    -http://www.anandtech.com/show/4839/mobile-gpu-faceoff-amd-dynamic-switchable-graphics-vs-n vidia-optimus-technology/2
    -Mac Utility for dual adapters http://forums.adobe.com/thread/1017891?tstart=0

  • Adobe Premiere Pro CC 2014 Crashing very often! Please Help!

    Hello,
    I am currently editing my first feature on Adobe Premiere Pro CC 2014 and it is currently up to date.
    I am editing on a iMac 27in, late 2013 brand new computer.
    Processor: 3.5 GHz Intel Core i7
    Memory 32GB 1600 MHz DDR3
    Graphics: NVIDIA GeForce GTX 780M 4096MB
    System: OSX Yosemite V 10.10.1
    The project is located on a 8TB G Drive
    7200 RPM
    High Performance ThunderBolt drive.
    Details of the project:
    I am currently working on a fine cut of 5K Red Footage that is being cut in the RAW.
    I work at 1/2 quality settings and have no lag.
    The timeline includes limited stacked video files and various mp3 audio files.
    The Problem:
    Lately, the program will randomly quit or freeze up 4-5 times during an 5-6 hour edit session.
    Many times it is random, however, it seems to happen often if I accidentally click on the end of a clip on the timeline and it goes to switch into trimming mode. 
    Also, it will randomly go into the "pinwheel of death" out of nowhere followed by "Adobe CC is not responding."
    My project file is just about 15MB now.
    What is causing this reoccurring problem?
    How can I make it happen less?  I have scoured the forums and found similar articles but no helpful solutions.
    I have recently turned auto save on to save every 2 minutes because there have been more than one occasion where I lost A LOT of work because of this issue.
    I am about two weeks out from picture lock delivery and this issue is driving me crazy and loosing me a ton of time.
    Please help or let me know if any more additional information can help solve the issue.
    I have sent in well over 25 error reports already.
    Thanks,
    Thomas.

    I think I may have found the solution...
    I completely removed the Premiere Pro folder under User > Documents > Adobe and so far it seems to have solved the problem.
    I of course backed up my projects and than deleted this folder. So far it seems it worked.
    I'll know for sure in a day or two, but after constantly crashing, Premiere hasn't crashed for the last 4-5 hours of work.
    Goran

  • What is the problem with Adobe Creative Cloud Premiere Pro CC 2014, why it freezes often?

    I Purchased the Adobe Creative Productive Premium Suite CS5 in early 2010 and I was very satisfied with it all this time, I can say that I never had a problem while using any of the Production Premium applications. Few weeks ago, I asked Mr. Philip Bloom about a technical issue regarding the best method to use a 50 FPS clip with a 23.976 FPS project, and I got his kind help but he recommended me too that I should upgrade to the latest Adobe Cloud CC 2014 which has many new features added to the different programs. I took his kind advice and downloaded a trial version of all the Adobe Cloud CC programs which I use for my filmmaking business.
    Today is the 20th day of my trial period and I have 10 days left to take the decision of continuing with CC 2014 or not. The past 20 trial days were not very pleasant. I want you to share with me the following details which I'll list them as bullet points and I would appreciate diagnosing the problem if you can and suggest a solution for it  to re-try the Adobe Cloud CC 2014 for the 10 remaining days with no further problems.
    I used to have the Gigabyte graphics card GTX 470 for about 4 years and it malfunctioned last year and I replaced it with a humble Geoforce GT 610 card, but it worked fine with the Adobe Suite CS5 programs.
    My system configuration is Intel Core I7   950@  3.07GHz , installed memory 12 GB. , Windows 7 Ultimate, 64 bit Service pack 1, 3 hard drives 1TB. each (one of them is dedicated for Adobe asset files and the editing work)
    For the first 2 or 3 days I used mainly the Premiere Pro CC 2014 establishing short projects for a max. of 5 minutes each and it was working normal. But, later, as soon as I started to build a project which reached about 24 minutes of length and I began to edit those before I add more clips to the timeline, unfortunately, the PrPro CC 2014 started to freeze on any of the frames every time I try to edit normally as I used to do with the CS5, so, I had to wait for 2 or 3 minutes every time it freezes, then it works for seconds then freezes again!!  and during the 20 days mentioned above it crashed once.
    The movie files of my project are the Nikon's .Mov files and the editing work which I performed included effects such as Color correction (levels) color correction (fast) color correction (Auto) sharpen effect, and stabilizing effect.
    I installed the Magic Bullets Suite trial version, and the Neat Video trial version, aiming to purchase either the DeNoiser or the Neat Video (but I tried their effects without saving them to the project).
    I used to export parts/ or whole project before finalizing the editing process to be able to monitor on a TV screen (mp4 file format) some of the changes I made in PrPro before being freezed.
    Based on my previous 5 years experience using the CS5 Suite I have a strong trust in Adobe, I never thought the problem was in the PrPro application, but rationally I thought it was the graphic card (GT610), and accordingly I purchased yesterday a new Zotac Geoforce GTX 770 (listed by Adobe as an approved card) and I installed it and checked that it is running fine and I checked the processor temperature which was within the normal level.
    Only today, I began to think that it might be something wrong with the Adobe Cloud CC 2014 ( a bug or something) and as a result of searching on the internet I could see lot of users since 2014 who were having freezes and crashes with the CC and the CC 2014 versions. That was a shock for me, could it be that until Feb. 2015 the same severe problem still occurs???
    Sorry for any inconvenience, looking forward to seeing a solution for that serious problem.

    Hello Ashraf,
    Sorry you didn't get any help on this post. In the future, please contact Adobe Support for 1-1 assistance on issues like this: Contact Customer Care
    Thanks,
    Kevin

  • Multi Cam Flicker Issue - Premiere Pro CC 2014

    Multi Cam Flicker Issue - Premiere Pro CC 2014 can any one help me pls

    Hi,
    This might help :
    Go to File > Project Settings > General and change the Video Renderer to Mercury Playback Engine software only. Click OK and select Delete Previews.
    Thanks,
    Rameez

  • How to work on the same project on two machines at the same time and also exchange progress seamlessly using Adobe Premiere Pro CC 2014?

    We are working on a film project on Adobe Premiere Pro CC 2014. Two editors are working on the same film project (same pproj file ) on two machines. As a result the bin structure and the file structure is exactly the same. We even bought two licenses for the respective machines to make matters simple (at least we thought it would).
    Now when we share a sequence between the two machines, every time we have to import and re-link media. Also each sequence import comes with its own set of files, which are actually already present in the project. Basically the new sequences are looking to re-link the media to the original/ source files only and are completely ignoring the file structure present in the project.
    In all editing softwares, timeline/ sequence sharing is a very common practise when working on multiple machines. Why is it so tedious in CC 2014? Every time we share a sequence between the two machines the media gets doubled and tripled in the project. As a result the project file size is increasing perpetually. Already Premiere CC 2014 is extremely laggy and slow, and this stupid bug is making it more difficult for us to finish our work on time.
    Has anybody ever faced this issue? How do we solve it? We are willing to try out any workflow that you can suggest.

    Concurrently working on the same project it requires a specific implementation in all editing programs like Avid's Unity/ ISIS shared storage. That's what you are simply not considering. none of your issues would be any problem if your projects resided on a commonly accessed server or something like that. Check respective hardware solutions.
    Mylenium

  • Flicker footage in Premiere Pro CC 2014.2. Tested on different computers. When waiting for fixes this bug?

    Flicker appears solely the fault of Premiere Pro CC 2014.2. Tested on different computers. Used as nVidia Quadro and GeForce GTX770. Drivers were different. Everywhere equally evident flicker. Incidentally, it defies logic and may occur at different film pieces. If re-render that flicker may occur on another spot in the video.
    It can occur even in the parts without filters !!! But no all time.
    ver 2014.2 - win 7 - intel i7-4770 - gtx 770 - flicker!
    ver 2014.2 - win 7 - intel i7-4770 - Intel HD Graphics 4600 - flicker!
    ver 2014.2 - win 7 - intel i7-2700K - quadro 2000 - flicker!
    MERCURY PLAYBACK ENGINE work fine! But still flickering in preview and render.
    When waiting for fixes this bug?

    Hi Aleksey,
    Flicker appears solely the fault of Premiere Pro CC 2014.2. Tested on different computers. Used as nVidia Quadro and GeForce GTX770. Drivers were different.
    Have you tried with the Mercury Playback Engine set to "Software Only?" More info please: FAQ: What information should I provide when asking a question on this forum?
    Everywhere equally evident flicker. Incidentally, it defies logic and may occur at different film pieces. If re-render that flicker may occur on another spot in the video.
    Is this a brand new project or one you updated from an earlier version? What kind of footage are you exporting? Which preset are you using?
    When waiting for fixes this bug?
    If I can repeat the case here with the same hardware, GPU, and drivers, that would be easier to fix the bug. Currently, I cannot recreate the bug.  If you or anyone else can provide me with steps to recreate the bug, that would help immensely. It sounds like this will be the difficult thing.
    Thanks,
    Kevin

  • Premiere Pro CC 2014 crashes when loading project file

    Hi guys, any help on this is much appreciated as I have a job due in 18 hours and I'm in big trouble if I can't fix this.
    I've been editing a project in Adobe Premiere Pro CC 2014 (updated to the latest version) and when I tried to access the same file today it is giving me the error message:
    'Sorry, a serious error has occurred that requires Adobe Premiere Pro to shut down. We will attempt to save your current project.'
    I had saved other version files and they all seem to be working properly so I know it's not my HD that is corrupt. In fact my suspicion is that it has something to do with a blur effect i'm using. The only problem is, I can't even access the file to delete the effect as the project file won't open.
    Information about my computer:
    I am using a Macbook Pro
    OS X version 10.9.4
    2.6 Ghz Intel Core i5
    Memory 16 GB, 1600 MHz DDR3
    Any suggestions/comments would be appreciated.

    Guys I solved my own problem - thought I'd share with you how in case anyone else is having this problem -
    I came across this thread
    Premiere Pro CC error message and crash
    which had the suggestion -
    "Do tou have after effects installed? If yes, please try to import the main sequence into it and then export it as premier pro project from file/export ootion and then try to open that in premiere pro."
    This didn't work for me too but I did try and import my existing project into a new project and copy all the files over. Works fine now.
    I don't know if I will have the same issue again tomorrow so I'm going to render out a super high res video before I close premiere just in case

  • Why does Premiere Pro CC 2014 renders incredibly slow?

    Dear Premiere Pro experts
    I created a movie with Adobe Premiere Pro CC 2014 and I have serious performance issues when it comes to export the movie.
    The first 10% renders pretty fast and takes 1 hour. Then it takes for every additional 1% about 4 hours! (never rendered it to finish so far, 14% max so far)
    Here are some facts that might help to isolate the problem:
    Project:
    Length: 24 minutes in total, splitted into several sequences (up to 4 minutes) and arranged on a "main-sequence"
    Input: Cineform AVI files, 1080p, 59fps (I converted GoPro 3+ footage (3D!) using GoPro Studio to the Cineform format for further processing)
    Desired Output: Same as input, preserving 3D (Render 3D Intermediate)
    Effects used: Warp-Stabilizer (default settings) and Auto-Color (smoothing 1-2 sec) on almost every clip.
    Hardware / Software:
    i7-3770K @3.5 GHZ (Quadcore)
    16 GB RAM
    NVIDIA Geforce GTX 970 (also tried with a ATI Radeon R9 290X)
    Windows 8.1
    SSD for OS and programs, RAID 0 for media files and project, separate drive for rendering output.
    Then I tried to render using AME using the same settings. The whole video rendered in about 14 hours what is acceptable in my case. There problem here is that the 3D gets lost, even if I selected "Render 3D Intermediate". The picture for the left eye is the same as the one for the right eye. This is not happening when I do a direct export. But the direct export get almost stuck at around 10%.
    There is almost no difference in choosing Software-Rendering and GPU. Also, the GPU has almost no load. Premiere Pro uses the CPU for about 45% (total usage 65%) and takes up 5-9 GB of memory (total usage 65%). Disk usage at around 14b/s.
    I think there are two problems. One is that AME renders differently (no 3D) and the other is that the direct export takes way too long.
    Can someone help me with any of these problems?
    Thank you,
    Martin

    I did some additional research and found out, that the slow rendering happens with this combination:
    - Auto-Color using Temporal Smoothing
    - Render 3D Intermediate
    Without rendering the 3D intermediate, Temporal Smoothing is not a problem. And without temporal smoothing, Rendering 3D Intermediate is not a problem.
    Might this be a problem in the codec or in Premiere?

  • After upgrading to Premiere Pro CC 2014, I can't change the render preview location

    Ever since I downloaded Premiere Pro CC 2014, I cannot re-route my render preview files. I have two internal hard drives and I need the files to go to my secondary one. With CC, it did this just fine, but since I've upgraded to 2014, it will not do it. I've set it the same way I did before in Preferences/Media, then set the Media Cache Files and Media Cache Database to the new hard drive.  It's eating all my hard drive space and I cannot render or export a large sequence. Is there a trick to this I'm missing that has changed?

    Thanks Neil! I'm actually wondering how to change where the preview files go. I've attached two screen grabs. Right now my media cache is going to my SATA drive (my smaller of my two internal hard drives and the drive where Premiere Pro is located.) I want to re-route my render files to go to my Macintosh HD drive which is much larger and gives me more breathing room. I could do that before but since I've upgraded to 2014, even though I have it set in preferences, it STILL goes to my SATA drive. So annoying! I'm wondering if I'm doing something wrong or if it's a bug. I'm still running Mountain Lion (getting ready to finally upgrade, I've just been needing to backup my computer), could this be the reason? Any ideas? Thanks so much for the help!

  • ICanon C100 playback issue premiere pro cc 2014

    I am having playback issues in Premiere Pro CC 2014 with footage shot on my Canon C100 (29.97 fps).  It was happening after doing a straight import and creating a sequence using "new item".  Then, after reading some other threads here and elsewhere,  I interpreted the footage so premiere would see it as progressive (no fields) rather than interlaced, but that doe not seem to help.  It is even doing it when I play at 1/4 resolution.  The only solution seems to be to quit and restart and reopen the project.  Then it works temporarily for a little while but not long enough to actually edit.  I have done projects in Premiere with C100 footage in the past and have not experience this level of difficulty.
    My Media Cache is not going to the startup diskc(it is gong to the right place)
    I am on a Mac 2.66 Ghz Quad-Core Intel Xeon
    OS X 10.8.5
    10GB 1066 MHz DDR3
    NVIDIA GeForce GT 120 512 MB
    Please help - very frustrated.  If the solution is to transcode, it sort of kills the value of premiere in many ways.

    Hi,
    This might help :
    Go to File > Project Settings > General and change the Video Renderer to Mercury Playback Engine software only. Click OK and select Delete Previews.
    Thanks,
    Rameez

  • Hard Drive Setup Recommedation - Premiere Pro CC 2014

    Premiere CC on my old Win 7 64bit hard drive had smooth video previews. Premiere CC 2014 on my new Win 8.1 64bit hard drive is choppy and sluggish. Same ATI Mobility Radeon HD 4650 car which uses WDDM v1.1 as the driver. No other driver available.)
    Would love some expert advice how to setup my new configuration to be optimized for Premiere Pro CC 2014, get rid of choppy video.
    Video is not a huge part of our small 2 person business so
    1. I can't justify a large volume expensive SSD
    2. can't justify another 2+ days to reload Windows 8.1 and all my programs on the small SSD I have (might not even fit.)
    Should I leave programs and OS only on the new WD hard drive... put Premiere project and other data files on the old TOS hard drive and use something like the SDD via eSata as the scratch disk?
    Dell Studio 1747 Laptop - 8GB RAM
    1. NEW - INTERNAL WD7500BPKX new hard drive with Windows 8.1 - (Program files only) 7200 RPM, 750GB, 16 MB Buffer, 6GB/s
    2. OLD - INTERNAL TOSHIBA MK 5056GSY old hard drive w/ Windows 7 (can be wiped and only have data files) 7200 RPM, 500GB, 16 MB Buffer, 3GB/s
    3. SPARE - EXTERNAL Lacie d2Next - (partitioned, can be wiped) 5400 RPM, 500GB, 3GB/s eSata
    4. SPARE/DONATED - EXTERNAL (eSata, Firewire, USB) OCZ-Agility3 SSD (can be wiped) ~100GB
    Thanks. These configurations are an art that we can't specialize in due to our staff size, workload and budget.

    Tweakers Page - Disk Setup but start with increasing RAM to at least 16 GB.

  • Audio-Problem with Adobe Premiere Pro CC 2014 by using long Clips in AVC-Intra Codec (4Gb Border)

    Hello
    We own a Panasonic camera (AJ-PX5000G) and we film in 1080p50 with the AVC-Intra100 Codec. When importing longer clips in Premiere Pro, the video is fully loaded, but the waveform of the sound ends at the Time Code 00:02:28:35.
    Sometimes the sound could be played after this Timecode but otherwise there is no audio. Even if we use the same clip several times we see that it works sometimes and sometimes not. It looks random.
    We also tried to import the Clips with Adobe Prelude directly from the P2-Card but there are the same problems.
    The Clips in 1080p50 AVC-Intra100 have a bitrate of 227Mbps. After 2 Minutes and 28 Seconds 4Gb are written on the P2-Card and the Camera starts a new picture file and 4 sound files..
    It looks like Adobe Premiere Pro has problems with the correct relation of the files that all get together to one clip.
    Is there anybody who can confirm this problem? Can anybody help me with this Premiere Problem?
    Dennis
    (Workstation:  Dell Precision T3600, Intel Xeon E5-1620 @ 3.60 GHz, 16 GB RAM, Windows 7 Professional 64-bit, Service Pack 1, Premiere Pro CC 2014.1 (Build 8.1.0)   )
    Mediainfo of the P2-Cards:
    General
    Complete name                            : \CONTENTS\VIDEO\0068T7.MXF
    Format                                   : MXF
    Format profile                           : OP-Atom
    Format settings                          : Closed / Complete
    File size                                : 3.92 GiB
    Duration                                 : 2mn 28s
    Overall bit rate                         : 227 Mbps
    Encoded date                             : 2014-10-15 13:33:41.000
    Writing application                      : Panasonic P2 2.0
    Writing library                          : Panasonic P2 2.0
    Video
    ID                                       : 2
    Format                                   : AVC
    Format/Info                              : Advanced Video Codec
    Format profile                           : High 4:2:[email protected]
    Format settings, CABAC                   : No
    Format settings, GOP                     : N=1
    Format settings, wrapping mode           : Clip
    Codec ID                                 : 0D01030102106002-0401020201323104
    Duration                                 : 2mn 28s
    Bit rate                                 : 227 Mbps
    Width                                    : 1 920 pixels
    Height                                   : 1 080 pixels
    Display aspect ratio                     : 16:9
    Frame rate                               : 50.000 fps
    Standard                                 : Component
    Color space                              : YUV
    Chroma subsampling                       : 4:2:2
    Bit depth                                : 10 bits
    Scan type                                : Progressive
    Bits/(Pixel*Frame)                       : 2.193
    Stream size                              : 3.92 GiB (100%)
    Color primaries                          : BT.709
    Transfer characteristics                 : BT.709
    Matrix coefficients                      : BT.709
    Mediainfo Audio-Datei P2-Card:
    General
    Complete name                            : \CONTENTS\AUDIO\0068T700.MXF
    Format                                   : MXF
    Format profile                           : OP-Atom
    Format settings                          : Closed / Complete
    File size                                : 13.6 MiB
    Duration                                 : 2mn 28s
    Overall bit rate mode                    : Constant
    Overall bit rate                         : 770 Kbps
    Encoded date                             : 2014-10-15 13:33:41.000
    Writing application                      : Panasonic P2 2.0
    Writing library                          : Panasonic P2 2.0
    Audio
    ID                                       : 3
    Format                                   : PCM
    Format settings, Endianness              : Little
    Format settings, wrapping mode           : Clip (AES)
    Codec ID                                 : 0D01030102060400
    Duration                                 : 2mn 28s
    Bit rate mode                            : Constant
    Bit rate                                 : 768 Kbps
    Channel(s)                               : 1 channel
    Sampling rate                            : 48.0 KHz
    Bit depth                                : 16 bits
    Stream size                              : 13.6 MiB (100%)

    Hi,
    we have the same problem!
    It is not possible to play audio with the AVC-Intra100 Codec fluently.
    Can anybody help?
    Thanks,
    Anja

  • Can't Move Audio Clips in Timeline After Expanding to View Waveforms (Premiere Pro CC 2014.2)

    So, this seems to be a bit of a weird one, and I'd be pretty stoked if it ended up being something silly that I'm doing wrong, but I can't for the life of me figure out what that might be.
    As the title suggests, I can't use the mouse to move some audio clips in a timeline once I expand the track to view the waveforms. This appears to only happen with independent audio clips (WAV. AIFF, MP3, etc), and not with clips attached to video. Also, it's worth noting that I don't have track keyframes turned on. I was hoping that was it, but it wasn't.
    So, what happens is this:
    1) I drag an audio clip down to the timeline (I can drag it onto an existing track, or drag to the bottom of the sequence and create a new track. Neither option seems to get a different result.).
    2) So long as the track isn't expanded and the waveform isn't visible, I can move the clip left, right, or up and down to a different track.
    3) As soon as I expand the track to view the waveform this functionality goes out the window. When this issue happens I can use the keyboard to nudge left and right, but that's about all the movement I have.
    4) It's almost as though the track becomes corrupt. The lanes for the track don't redraw properly, and the track is pretty much unusable. I can't put anything into it, and I can't take anything out. All I can do is delete the track and start again.
    Complicating issues is that this doesn't always happen, but instead is one of those "vast majority of the time" issues. I can't see any rhyme or reason for why it works or doesn't. I seem to do the exact same thing, but occasionally get different results. It doesn't matter what type of file I'm using (WAV, AIFF, etc), and this only happens with independent audio clips.
    Once again, I don't have track keyframing turned on when this happens. Believe me, I wish that was it.
    I have already filed a couple of bug reports about this over the last month or so, but haven't heard anything yet. I was wondering if anyone else was having the same issue, and if so, whether they had any workarounds.
    Mandatory system info:
    Windows 7 Professional SP1 (64-Bit)
    Intel i7-3820
    32GB RAM
    Nvidia GTX 980 (350.12)
    Premiere Pro CC 2014.2

    Update:
    I was just looking to post a screenshot of the timeline when I discovered something interesting. As soon as I use the vertical scroll bar to the right of the sequence, the tracks start to work again. Close off the waveform and the clip goes haywire. Move the scroll bar a tiny bit (or a lot), and suddenly the clip starts working.
    Pretty bizarre.
    The good news is that for the time being that could be a workaround, though it would be great for this to not happen at all.

  • Premiere Pro CC 2014 and Media Encoder CC 2014 not completing encode.

    This is a project that I have been successfully encoding in short segments until now.  Now when encoding, session runs about 10-15 minutes and then ends without error messages. 
    Removing effects and changing to Mercury PB Engine SW did not help. 
    Also tried disabling metadata as suggested in another forum. 
    When CUDA used, logged as "Encoding failed."  When Mercury SW used, logged as "File Successfully Encoded" even though video file is only 6 KB with no content.
    Premiere Pro Build 8.1.0 (81)
    Media Encoder Build 8.1.0.122
    Windows 7 Professional
    Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz
    8 GB RAM
    NVIDIA GeForce GT 610 (9.18.13.3788)

    I am having a similar problem.
    Premiere Pro CC 2014 suddenly decided to crash every time I export to either Adobe Media Encoder or within Premiere itself.
    The encode will usually go for 5-10 minutes before the programs either spits out a "serious error has occurred" window, or it just sits there frozen until I force quit.
    I did find a work-around for the moment. If I open AME and FILE > OPEN, select my project and then the sequence I want, AND put it in Software render mode, it will work.
    My timeline is 2K, 58 minutes in 23.976
    Only effects applied are Lumetri LUTs - no third party.
    I've exported as recently as a week ago without issue.
    Running OSX 9.5 on an X99 board
    3.75 GHz 8-core
    64GB 2400 MHz RAM
    EVGA Titan Black 6GB
    Because I can get my renders out, I am not too concerned. Either there is something wonky with my timeline that screws with any graphics enabled rendering, or there is a bug that is have the same effect. I will try rendering on another of my edit bays that utilizes a GTX 580 that I KNOW works. The Titan is pretty new to my workflow.
    Thanks Adobe, for checking this out.

Maybe you are looking for