Question About Time Remapping - Premiere Pro CC 2014

I have a question in regards the the Time Remapping feature. When I use it to gradually speed a clip up, the audio obviously doesn't change with the video. I was looking to see if there is a way to do the same change to the audio, within Pr Pro or Audition. I spent some time looking in the programs and also Googling yesterday, but didn't find much. Does anyone know a way to do this? I did try using Audacity (Sliding time Scale/Pitch Shift), but the way Audacity processes the audio is quite a bit different than Pr Pro/Au.
Thank you,
Benjamin
P.S.
O.S. Windows 7 Professional 64-bit
Version: 6.1 Service Pack 1
System architecture: Intel CPU Family:6, Model:10, Stepping:9 with MMX, SSE Integer, SSE FP, SSE2, SSE3, SSE4.1, SSE4.2, AVX, HyperThreading
Physical processor count: 4
Logical processor count: 8
Processor speed: 3492 MHz
Built-in memory: 32738 MB
Display: 1
Display Bounds: top=0, left=0, bottom=1080, right=1920
OpenGL Drawing: Enabled.
OpenGL Allow Old GPUs: Not Detected.
OpenGL Drawing Mode: Advanced
OpenGL Allow Normal Mode: True.
OpenGL Allow Advanced Mode: True.
AIFCoreInitialized=1
AIFOGLInitialized=1
OGLContextCreated=1
NumGLGPUs=1
NumCLGPUs=1
glgpu[0].GLVersion="3.0"
glgpu[0].GLMemoryMB=2048
glgpu[0].GLName="GeForce GT 640/PCIe/SSE2"
glgpu[0].GLVendor="NVIDIA Corporation"
glgpu[0].GLVendorID=4318
glgpu[0].GLDriverVersion="9.18.13.5012"
glgpu[0].GLRectTextureSize=16384
glgpu[0].GLRenderer="GeForce GT 640/PCIe/SSE2"
glgpu[0].GLRendererID=4033
glgpu[0].HasGLNPOTSupport=1
glgpu[0].GLDriver="nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um"
glgpu[0].GLDriverDate="20150408000000.000000-000"
glgpu[0].CanCompileProgramGLSL=1
glgpu[0].GLFrameBufferOK=1
glgpu[0].glGetString[GL_SHADING_LANGUAGE_VERSION]="4.50 NVIDIA"
glgpu[0].glGetProgramivARB[GL_FRAGMENT_PROGRAM_ARB][GL_MAX_PROGRAM_INSTRUCTIONS_ARB]=[1638 4]
glgpu[0].glGetIntegerv[GL_MAX_TEXTURE_UNITS]=[4]
glgpu[0].glGetIntegerv[GL_MAX_COMBINED_TEXTURE_IMAGE_UNITS]=[192]
glgpu[0].glGetIntegerv[GL_MAX_VERTEX_TEXTURE_IMAGE_UNITS]=[32]
glgpu[0].glGetIntegerv[GL_MAX_TEXTURE_IMAGE_UNITS]=[32]
glgpu[0].glGetIntegerv[GL_MAX_DRAW_BUFFERS]=[8]
glgpu[0].glGetIntegerv[GL_MAX_VERTEX_UNIFORM_COMPONENTS]=[4096]
glgpu[0].glGetIntegerv[GL_MAX_FRAGMENT_UNIFORM_COMPONENTS]=[2048]
glgpu[0].glGetIntegerv[GL_MAX_VARYING_FLOATS]=[124]
glgpu[0].glGetIntegerv[GL_MAX_VERTEX_ATTRIBS]=[16]
glgpu[0].extension[AIF::OGL::GL_ARB_VERTEX_PROGRAM]=1
glgpu[0].extension[AIF::OGL::GL_ARB_FRAGMENT_PROGRAM]=1
glgpu[0].extension[AIF::OGL::GL_ARB_VERTEX_SHADER]=1
glgpu[0].extension[AIF::OGL::GL_ARB_FRAGMENT_SHADER]=1
glgpu[0].extension[AIF::OGL::GL_EXT_FRAMEBUFFER_OBJECT]=1
glgpu[0].extension[AIF::OGL::GL_ARB_TEXTURE_RECTANGLE]=1
glgpu[0].extension[AIF::OGL::GL_ARB_TEXTURE_FLOAT]=1
glgpu[0].extension[AIF::OGL::GL_ARB_OCCLUSION_QUERY]=1
glgpu[0].extension[AIF::OGL::GL_ARB_VERTEX_BUFFER_OBJECT]=1
glgpu[0].extension[AIF::OGL::GL_ARB_SHADER_TEXTURE_LOD]=1
clgpu[0].CLPlatformVersion="1.2"
clgpu[0].CLDeviceVersion="1.2 CUDA"
clgpu[0].CLMemoryMB=2048
clgpu[0].CLName="GeForce GT 640"
clgpu[0].CLVendor="NVIDIA Corporation"
clgpu[0].CLVendorID=4318
clgpu[0].CLDriverVersion="350.12"
clgpu[0].CUDASupported=1
clgpu[0].CUDAVersion="7.0.0"
clgpu[0].CLBandwidth=2.58495e+010
clgpu[0].CLCompute=181.438
I'm sure this information is somewhat unnecessary for this question, but thought I'd add it anyway.

I'm not aware of any way to perform a speed ramp for audio using Adobe software.  Would be a great new feature, though.
Adobe - Feature Request/Bug Report Form

Similar Messages

  • Dramatically slower encode/render times from Premiere Pro CC 2014 via both AME 2014 and direct export via PP

    My recent update to Adobe CC 2014 apps has been an unmitigated disaster.  Was running the 2013 version until last week and everything was just dandy.  Very good performance and excellent render/encode times even for stuff with lots of filters and fx. 
    Since update 1-2 min videos with no fx or filters (or even transitions) have gone from exporting in under two minutes to well over 25 minutes.  These exports are with the same presets I regularly use (Vimeo 720HD H.264). 
    I've been poking around the forums here for two days looking for answers and can't find anything that works.  Tried the whole "App Nap" toggle as well as a few other tips.  Didn't do squat.  Looking for any hints/answers.  Thanks.
    Mac Pro Mid 2012
    2 x 2.4 GHz 6-Core Intel Xeon
    32 GB 1333 MHz DDR3 ECC
    ATI Radeon HD 5870 1024 MB
    OS X 10.9.5 (13F34)
    System SSD 500GB
    Cache SSD 500GB
    Media HD 1TB

    Hi MXSw,
    MXSw wrote:
    All right.  More experimentation has been done.  Seems like the renaming of Adobe folders fix prescribed in the link below might have helped a bit.
    Premiere Pro CC 2014 renders are painfully slow.
    You can rename folders, but I prefer to do it this way: Premiere Pro CC freezing on startup or crashing while working (Mac OS X 10.9, and later)
    MXSw wrote:
    Kicked out a 1 minute edit with some color/fx in under 10 minutes.  Not as fast as in the past but at least the CPU seemed to be cranking at 500% and above per Activity Monitor.  Its barely gone over 250% in previous attempts.
    That sounds a lot better.
    MXSw wrote:
    Same 1 minute edit took 35 minutes however when I exported from a PP timeline using MXF clips instead of QTs.  I assumed the QTs would speed up the process but in the past I've gotten great performance on big old RED raw files so still a bit of mystery why I can't approach the speeds I had prior to most recent CC update.
    Maybe updating your project file has something to do with it. I'll keep my eye on this issue. Thanks for reporting.
    Regards,
    Kevin

  • Newbie question re: upgrading to Premiere Pro CC 2014.1

    Apologies in advance for having to ask such a basic question... I have recently upgraded my edit suites to PP CC 7.2.1 (4) from Apple FCP. The suite is connected to the Internet, yet when I open the Adobe Application Manager, and open the Premiere Pro drop down it doesn't mention 2014.1 ?, How/where do I upgrade?
    Thanks in advance

    You may need to "force" the updater by...
    Log out of your Cloud account... Restart your computer... Log in to your paid Cloud account
    -Sign in help http://helpx.adobe.com/x-productkb/policy-pricing/account-password-sign-faq.html

  • Question about benchmarking with Premiere Pro

    Hi all:
    I am a writer for a website that focuses a lot on benchmarking PC hardware and am in the process of refreshing our CPU test suite. I'd like to implement Premiere Pro into our testing, but as a new architecture launch is due in a couple of weeks, I am working on this with some haste. I'm a novice with this tool, so it's my hope that I can get the "a-OK" from experienced users who know whether we're testing with the tool in a reasonable way. This is important because we implement real-world benchmarks for the sake of showing users of such tools how one CPU can compare to another in terms of raw performance. Other tools we benchmark with include 3ds Max, Maya, Handbrake and Lightroom (which I desperately wish supported more than a couple of threads).
    That all said, the project I've created is not conventional, as it's more of a worst-case scenario. I recorded about 18 minutes from a new PC game using Fraps, resulting in 35GB worth of source files. These are not "lossless", but are close to it (300~370Mbit/s). I take these files, crop most of them, add in cross dissolves and then encode it to MPEG 2 Blu-ray using almost default settings. In order to stress the CPU better, I enable the "Use Maximum Render Quality" (is that often used in production encodes?) option, and also change to a VBR 2-pass.
    Here are some quick results from the benchmarking I did this afternoon:
    Intel Core i7-975 (4 core, 8 thread, 3.33GHz) - 46m 40s
    Intel Core i7-975 (4 core, 8 thread, 4.00GHz) - 38m 45s
    Intel Core i7-980 (6 core, 12 thread, 3.33GHz) - 30m 36s
    As seen there, in an equal-clock 4 core vs 6 core battle, we saw the latter encode finish about 50% faster (the scaling is rather amazing). But the question remains - can I feel confident in benchmarking this as a project? Would it ultimately prove useful to you guys?
    Thanks much for any help!
    PS: As an added question, does Premiere Pro take advantage of SSE4 (or beyond) instructions, and will it support AVX in the future?

    Hi Jim:
    Thanks for the response!
    I don't own a video camera (boy, do I ever feel like a reject, now). Would it be an inaccurate way of doing things if I took the same project I have as mentioned above, export it to AVCHD 1080p/24 and then use that as the source file to encode to MPEG-DVD? It'd still be game footage, but essentially the codec is what really matters (I could be wrong; perhaps the codec would work better with real images).
    Sorry if that comes off as a ridiculous question. If that's not a good solution I will see about getting such a source from somewhere.
    Thanks a ton!
    Edit: Would it be sufficient to use a Blu-ray .m2ts file specced at 1080p/24 AVC MPEG-4 as a source? I assume it's AVCHD given it's 1080p.

  • Premiere Pro CC 2014 renders are painfully slow.

    Running CC 2014 on a brand new iMac: 3.5 GHz Intel Core i7, 32 GB RAM, NVIDIA GeForce GTX 780M 4096 MB.
    I have a 2.5 minute timeline with many dynamic link clips back to simple After Effects CC 2014 comps. Rendering in this timeline is MIND-BOGGLINGLY slow. 
    Video Rendering and Playback Renderer is set to Mercury Playback Engine GPU Accelerated (CUDA)
    And in Preferences > Memory> I have optimized rendering for "Performance".
    My Sequence is using Apple Pro Res 422 as my video preview codec with Maximum Bit Depth and Render Quality selected.
    Renders should be screaming.
    Is anyone else experiencing this? Have I done something stupid in my set up?

    Hi Kevin.  Thanks for response.  Yes, acceleration is enabled.  Not CUDA as I'm running on a ATI Radeon HD 5870.  See screenshot below. 
    Also have a thread specific to my issue here: Dramatically slower encode/render times from Premiere Pro CC 2014 via both AME 2014 and direct export via PP
    If you get a chance to look through it, I'd appreciate it very much.
    Thanks!
    Martin

  • 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

  • Premiere Pro CC 2014 freezes frequently and crashes

    Since upgrading from Premiere Pro CC to Premiere Pro CC 2014 my projects crash in regular intervals, which didn't happen before.
    All my settings and presets have been pulled across fine, but suddenly relatively slim projects get stuck during editing, rendering or exporting. The progress bar stops, the preview screen freezes and that's it. I can only radically crash the sucker. I did delete all preview files and it improved marginally... only that the time until it froze took a few minutes longer.
    I'm on 64bit high-end Windows 7 machine and have never had this problem with previous versions of Premiere Pro.
    Very frustrated.

    @bendubb37: I'm not the least bit defensive about complaints regarding the stability and general quality of the program. As a quality engineer on the Premiere Pro development team (not a member of the technical support team), I'm quite familiar with many if not most of the problems--both those that are legitimate bugs in our code and those that result from conflicts with OSes, hardware, codecs, other programs, etc. I genuinely appreciate having customers come to this forum to report issues they're having. Such reports sometimes help us identify bugs that we weren't aware of, and they always help us to prioritize bugs to fix based on which issues are biting the most customers and having the greatest impact on their productivity and satisfaction. And naturally I understand the frustration and anger of customers who are wrestling with one problem or another in the program.
    What I took issue with was cutco's derision of a perfectly valid troubleshooting step recommended by a technical support agent and his assertions that a) "This community is kind of useless" and b) "Adobe is absent." Cutco graciously acknowledged that he had let his frustration get the best of him.
    As to the oft-repeated claim that CC2014 is buggier and less stable than prior versions, I submit that it's a problematic claim to substantiate, at least based on anecdotal personal experience or taking the pulse of this forum & others. There's no question that some customers who enjoyed smooth sailing with an earlier version are experiencing problems with CC2014. But I know for a fact that this release included fixes for a significant number of bugs, including crashers, so many other customers who were having problems with earlier versions are now cruising along without a hitch (or at least without those old, fixed hitches). Alas, those people are not frequenting the forum to sing the praises of CC2014.
    My point here is simply that claims about the relative quality of one release versus others can be a distraction from the more important--and much more concrete--fact: a certain number of customers using CC2014 are having Problem X, which didn't happen in CC7.x. The more we can learn about Problem X--and the more clearly we can differentiate X from Y and Z, which may manifest similarly--the sooner we can nail down the cause.
    Don't get me wrong: there is an objective trajectory of a product's quality. Unfortunately, even when you have a large pool of data in front of you, the trajectory doesn't lend itself to quantification. You can't simply count the number of deferred bugs, for instance, because not all bugs are equal. You can't even go by the number of known crashers because some are extreme edge cases while others lurk in the path of mainstream workflows. That said, for people like me who spend our working lives trying to deliver the highest quality possible, the trajectory our program's quality is a common topic of discussion.

  • Where is a link to the Premiere Pro CC 2014.1 (8.1) update? - Can I get help with the ticktime.cpp-290 error?

    Ola to precisando do premiere versao 8.1 caravan consegue o link?
    Message was edited by: Kevin Monahan
    Reason: needed better title

    Hi Kevin,
    I posted about the same problem (TickTime.cpp-290 error) in another thread, but since you're asking here specific questions to resolve it, I'm answering it here.
    Re: Debug Event: [...\ ...\src\TickTime.cpp-290]
    What were you doing when this error started to occur?
              Nothing special I remember. The only thing I do recall, is:
              I was working with Premiere Pro (where the main project is), After Effects but rendering some PNG sequence, and Adobe Media Encoder. I sent from AE to AME a project to render. Configured 2 outputs (PNG & MP4). The same way I sent from PP a project to render and one error occured. Unfortunately I didn't write down the error, but it was like a path C://AME_64/something. But the AME queue updated and everything seemed OK. I close AME to be sure that the error wouldn't be the source of future error during rendering, and relaunched it. And at that time I couldn't open it. I got the error "Adobe Media Encoder has encountered an unexpected error and cannot continue". The only way I found to resolve this is to remove the directory /Users/%USERNAME%/My Documents/Adobe/Adobe Media Encoder/8.0/". The problem seems to appear when I save the queue. And since that time, Premiere do the TickTime.cpp-290 error.
              Another thing I noticed, don't know if it was there before, is, the AEP file in AME queue setttings displayed framerate as "25 / 29.97 / 30 / ...", a 2 digits number for the framerate. But suddenly (I thought first it was because of the Premiere Pro file being added to the queue, but no because it appended after without it), it was displayed as "25 000 / 29 970 / 30 000", a 5 digit number.
              After that, the TickTime.cpp-290 appeared. Sometimes when opening project, sometimes and resetting or changing the workspace (because it was messed up), sometimes when closing.
    Do you have iCloud installed?
              No.
    Is this a Premiere Pro CC 2014.0 or Premiere Pro CC 2014.1 project that was updated to Premiere Pro CC 2014.2? If so:
              It started long time ago a draft in CS6, but since I reopen the project, I saved new versions in Premiere Pro CC 2014.2 (not sure if I have other version like 2014.1 or 2014.0). Is there a way to know which 2014 version are my files? If I look into the XML I only saw Version="28"
    Do you have a copy that can be opened in an earlier version?
                  An old draft version in CS6. But that version has footage in different framerate and not all be interpreted at the timeline framerate.
    Do you get the same error in that earlier version?
                   No error here, the file opens properly.
                  Additional info: I tried to open the 2014.2 file on another computer (where PP 2014.2 is installed) and same problem (this computer is on Win7 64-bit)
    Did you use any unusual footage types in your project?
         I used MOV (Animation), MP4 (H264), and PNG sequence. The framerates of the footages are 24,25,30 and 60fps (but everything has been interpreted in 30fps)
    If you remove them, do you still get an error?
                  When I had the error, but not when I open the project file, I resave the file removing anything not interpreted in 30fps (because at that time I still had footage interpreted in their original framerate). I was able to work for some time, but now I can't open it anymore despite that.
    Was the fps interpretation changed in any of the clips?
         Since the error appeared, and because I saw in another thread that it could be related to footage of different framerate, my timeline is now in 30fps and all the footage have been interpreted in 30fps. Footage are MP4, MOV, PNG sequence in 24, 25, 30 & 60fps.
    If so, restore them to their original fps and see if you still get the error.
                  Unfortunately, since I can't open the project anymore, I can't test that.
    Did you use Warp Stabilizer?
              No.
    Do you have any browser plug-ins?
              What do you call browser plug-in in Premiere?
    Are there any third party plug-ins used?
              I have Magic Bullet Looks 2, and I'm using it on this project.
    If so, remove the effect from those clips and see if it improves the situation.
                  Unfortunately, since I can't open the project anymore, I can't test that.
    Some additional infos on my computer.
    I use Windows 8.1 (64-bit),  all Adobe softwares installed have the last update (for video apps, it's 2014.2)
    The language settings are configured in French, but Windows and CC apps are in English.
    If needed the 2014.2 project file is here:
    https://dl.dropboxusercontent.com/u/68413846/showreel19_30fps.prproj
    Thanks in advance to help us to resolve this weird bug.
    Christophe.

  • 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

  • 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

  • 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.

  • Premiere Pro CC 2014.2 crashes when "locating media"

    The problem;
    Premiere Pro CC 2014.2 crashes when "locating media".  I am working on a project that has not given me any problems for the last 200 hours.   About a week ago I notice that the .proj file size was 276mb and found this odd because my largest project to date was never larger than 80mbs.  I thought that the premiere was running slow because of the project size. As luck would have, when my client made their their final changes 2 days ago, I opened the project and premiere would hang on the locating media window and then would crash. I called Adobe and spent an hour on the phone with them to no avail. 
    Project workflow
    - 700gb of 5d footage
    - 20 sequences under 5 minutes
    - Dynamically linked files with AE
    - Warp Stabilized about a dozen clips of under 5 sec
    - On every sequence color correction adjustment layer with  RGB Curves, Three way color corrector and sharpen filter
    - I kept old versions of the sequences (I was in version 5 before the crash)
    What I have tried;
    - Unsuccessfully tried to open auto-save files for this project.
    - Successfully opened other older non relevant project
    - Removed Mercury playback engine in the project settings
    - Cleaned out media cache database through pp in media Preferences
    - Manually deleted cache files in /Common/Media Cache Files and /Common/Media Cache
    - Tried importing sequences into new .proj file; it would crash as a result.
    What "worked".
    I was able to open it on another computer. save it under another file name. bring it back to my original computer and open it without problem. I lost about 3 days working through this problem, I missed my deadline. and angered the client.  I was able to use a friends IMAC to "fix" the problem, however I can't always count on him being there if it happens again.
    Questions.
    - What the hell happened? Why could I open it on one computer and not on the other?
    - Is there a way to fix a corrupted .proj files on a PC?
    - What should the average file size be, before it becomes unstable? (I'm pretty that my file size was bloated by all the previous versions of the sequences)
    Windows 8.1  64bit
    Premiere 2014.2
    Intel Quadcore i7-4770    3.40GHz
    16gb Ram

    Hi,
    I would suggest the following steps:
    http://blogs.adobe.com/kevinmonahan/2014/09/10/premiere-pro-cc-freezing-on-startup-or-cras hing-while-working-mac-os-x-10-9-and-later/
    Run a disk permission repair on your boot drive, and
    Reset Home Folder permissions and ACLs Error | Apple Support Communities
    Thanks,
    Rameez

  • Exporting to Media Encoder crashes Premiere Pro CC 2014

    Greetings,
    I am experiencing a problem with premiere off and on. Right now it is an on problem. When I am exporting from Premiere Pro CC (and CC 2014) it will intermittently crash Premiere. I have tried this with several different audio and video formats (AVI [Lagarith and uncompressed], WAV, H.264, MPG2, AAC, etc). At the moment, every time I go to export to queue it locks up and hangs on the "Preparing data for export..." Media Encoder Launches and then it just freezes. I get "Problem Even Name: AppHangB1" over and over. Sometimes a full restart will fix this temporarily and sometimes it goes away for a long while. I managed to get a few sequences exported and then it just kept freezing on every PP CC restart.
    Here are my system specs:
    Premiere Pro CC (up to date)
    Win 7 64bit (up to date)
    i7 970
    24GB Ram
    NVIDIA 470GTX (driver up to date)
    3 x 1.5TB internal
    4TB internal
    3TB internal
    12TB RAID 5 via USB 3.0
    USB 2.0 and 3.0 drives
    FireWire audio device (M-AUDIO FireWire1814)... although, I am not using it for playback. It is connected.
    Footage is from C100 H.264 .MTS, H.264.mov from 7D, and H.264 .MOV from iPhone.
    All stock video plugins with a few third party audio plugs.
    This problem happens with and without third party plugs, but it happens that this project uses them.
    I have chatted with Adobe help twice about the matter and nothing has come of it. Log out, log in = same. Restart = same (sometimes), create new user account = same, and so on. The only thing I haven't done is completely re-install premiere, which seems a bit overkill. One of the reps said he would get back to me in a few days after he watched the issue via screen share. Never heard back.
    I get the sense that this has something to do with PProHeadless.exe not launching or not running properly. When the crash happens on a fresh restart of PP CC 2014 PProHeadless is not running. I can start PProHeadless and it will send sequence to media encoder. When I try to export another sequence from the same project it crashes and I see another instance of PProHeadless launched.
    Also, once the projects are exported to Media Encoder, I can encode them to any format with no problem. The problem is getting the sequences there!
    Is there anything that I am overlooking here?
    Thanks for the help!

    Hi
    Premiere pro cc 2014  8.0.1 (21) build
    Encoder CC 2014 8.0.1.48
    I use CC for Teams so it updates all the time.
    Again when I tried to use it today by letting premiere open it by sending an output into Queue it crashed both Encoder and Premiere.
    In order to shut down Encoder and Premiere I had to go into Task Manager and "End Process Tree" on everything adobe I could find because just ending Encoder did not work it would not close. I remembered that years ago when Premiere would crash we had to end a photoshop process. I found photoshop open even though it was not "alive" on my task bar. I had used it yesterday but had closed it. I also had to close dynamiclinkmanager.exe *32 as well as one of the three Adobe CDF Helper.exe*32. They popped back on but Encode closed and then I got a message that Premiere needed to close and did when I clicked the button to let it close.
    After all this I re-opened Encoder by itself and checked the Preferences finding that Import Sequences Natively option was again checked.
    By the way for me, "Launch AME manually, then drag the sequence from PPro's Project panel to AME's Queue (or to a preset in the Preset Browser). That uses a different code path than the File>Export>Media workflow." won't work most of the time because I do live events of panel interviews that may run 2 or more hours. I need to break them down to chapters for the web
    Also I know this isn't part of this problem but I and many others would still love dynamiclink to work to Encore because the DVD is not dead yet. The current work path is a drag.
    Looks like some programers and engineers have some work to do.
    Thanks
    Dennis
    My computer:
    Self built PC windows 7 Professional 64 bit Build 7601 SP 1 I use auto update so it is up to date.
    ASUS P6x58D Premium Motherboard
    Intel (R) Core i7 930 @ 2.80 Ghz
    Installed Memory  12 GB
    NVIDIA GeForce 9500 GT
    NVIDIA GeForce GTX 580
    2 Apple Monitors and a HP full HD Monitor
    With a BlackMagic Intensity Pro Capture Card

Maybe you are looking for