Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Exit
CHCHK
Explorer
CHCHK
Explorer
Activity
‎Jan 24, 2023
04:30 AM
40 Upvotes
In the latest version I'm able to crash Premiere every time I make changes to a sequences setting - e.g. put in a new frame rate, change field order etc.
... View more
‎Jan 20, 2021
07:53 PM
I've tried 14.5 and now 14.8 and I can make Premiere beachball crash everytime I OPT/COMMAND drag a clip to swap it with another in the timeline. Is anyone else having this issue? Cheers, Mike MacOS 10.14.6, nMP 2013 D700, BM Desktop 11.6, NAS and Promise Pegasus drives, Wacom tablet
... View more
‎Dec 03, 2020
11:58 AM
Same experience here (and tried trashing prefs/media cahce etc). Beachballs when moving clips in timeline so I didn't get far beyond that. 14.6 is totally unusable. This was on a current project, not a new one started fresh. nMP 2013, Mac OS 10.14.6.
... View more
‎Dec 03, 2020
11:46 AM
It says 'recommended for all users' so I updated to 14.6 and gave it a go on my current project. It crashed (beachball) when I selected any amount of clips and then moved them in the timeline. Trashed prefs, rebuilt media cache, trashed BM driver, created new workspace and it still crashed when moving a clip. Rolled back to 14.5 which is at least usable. 14.6 is the least stable release I've experienced in 20 years of using Premiere. nMP 2013 D700, Mac OS 10.14.6, media on QNAP shared storage, cache on external drive.
... View more
‎Feb 04, 2020
03:44 PM
1 Upvote
Hi Neil, That's super strange. For me (and Devon I think) when you move/nudge the synced clips the sub-frame audio adjustment reverts back to the nearest video frame point. I've tested and tested and there is no way I can get the sub-frame change to stick, after the linked section has been moved on the timeline. Even 'undo' doesn't bring the subframe adjustment back. Cheers, Mike
... View more
‎Feb 04, 2020
02:17 PM
1 Upvote
Here's the thing - it should work as you describe, i.e. you move or slip the audio waveform by a sub-frame amount to line up perfectly. It appears to have worked. You can link it, snap the synced audio to a frame boundary etc, but when you MOVE the linked clips the waveform goes back to where you started. The sub-frame adjustment doesn't stick! I did a feature doco about 4 years ago syncing sound from an external recorder. I was able to sync the audio a sub-frame amount to match the camera audio perfectly. And it stuck. Then somewhere in the updates since then I haven't been able to get the changes to stick. I've bought it up a few times on forums and with support with no joy - it's nice to know I'm not the only one in the world seeing the issue! Neil, as a test, can you enable audio time units, zoom in and sync 2 waveforms together perfectly, link the clips, disable audio time units, then nudge the clip 1 frame left or right or just move it on the timeline and see what happens to the sync/waveform?
... View more
‎Feb 04, 2020
12:35 PM
I have been having the same issue for a couple of years. I'm sure it used to work properly in the past. It lets you slip or move the audio by sub-frame amounts, so surely that change should stick! Cheers, Mike
... View more
‎Feb 02, 2020
12:33 PM
Hi Sumeet, Tried a few tests - the footage that I'm seeing this bug on is 1080p 25p ProRes 422 from a Ninja2. It doesn't seem to matter what I have as the render codec on the timeline. Toggling between 'max bit depth' on and off shows a big change in the image... darker and duller. FS7, DJI etc footage doesn't show the bug. Here's a clip to test: https://www.dropbox.com/sh/ah08c6z48ct1e80/AABYGH6cuK4i2D9TcKD8RMTHa?dl=0 Thanks, Mike Kelland
... View more
‎Jan 21, 2020
05:25 PM
Awesome post Neil, thank you 🙂 For my rig would you recommend selecting 'max bit depth' in the export dialogue when using ProResHQ as the codec? i.e. does that tick box do anything in that instance? My workflow is to pre-render the timeline and export with 'use previews' selected... Cheers, Mike
... View more
‎Jan 21, 2020
04:32 PM
Noticed a bug with the new 14.0.1 update: the max bit depth selector in sequence settings changes the luma of the timeline - i.e. much duller/darker when selected and normal when deselected. I have ProRes422HQ as the codec for sequence settings when I'm seeing this bug, and Metal acceleration. Anyone else seeing this? Cheers, Mike MacPro2013, D700, MacOS 10.14.3
... View more
‎Dec 02, 2019
05:40 PM
1 Upvote
Yes, having this exact issue too with Mac OS 10.14.3 and a Mac Pro 2013. I can't work out how a bug like this gets past beta testing, when you'd notice it in the first hour of using Pr 2020.
... View more
‎Jan 10, 2018
02:27 PM
Hi Kevin, As you say, this issue is popping up on updated projects and not on new projects (mostly FS7 4K .mxf). I'm tired of keeping 5 or so versions of Premiere on my system (because of issues like this) - we all need to open old projects at some point, it's the nature of our jobs. It would be nice if Premiere could do this reliably. In fact I would say that is THE most important thing a new version should be able to do. Will try a Media cache clean - that seems to be to root of a lot of Premiere's issues... When it's lagging I can see the lights on my raid ticking over furiously... Cheers, Mike
... View more
‎Jan 10, 2018
01:14 PM
I'm also seeing this problem in Pr CC 2018 (was fine in Pr CC 2017). Lag when using keyboard command for insert and overwrite from source monitor - 2 to 10 seconds delay. Drag and drop is instant. Pr 2018 latest version nMP 8 core D700 32GB RAM Mac OS 10.12.5 Pegasus2 raid
... View more
‎Nov 30, 2017
03:56 PM
Extra info: The nMP is 32GB RAM & 8 core, using FS7 25fps 4K .mxf footage in 4K 25fps timelines and 1080P 25fps timeline (issue is non-dependant of sequence setting re. max bit depth/codec etc. Issue: Drag to timeline from source monitor = instant - whereas using keyboard shortcut for insert or overlay edit has lag.
... View more
‎Nov 30, 2017
01:45 PM
My specs are: nMP 2013 D700, Mac OS 10.12.5, Pegasus2 raid, Latest Pr CC, BlackMagic 10.9.3.
... View more
‎Nov 27, 2017
12:33 PM
Have the exact same issue with this new version. Painful!
... View more
‎Jan 25, 2017
04:07 PM
I've had LUT difference problems going back to the switch between CC 2014-2015. Had gamma differences that meant applying a correction filter to all clips over multiple episode that had the LUT applied, or I stick with 2014 forever. This is my number one bug bear with Premiere - updates break multiple fundamental things in old projects, not just LUTs. Sometimes an old project just won't even open. 'Start and finish in one version of Pr' does not work in the real world. I have a subscription and would like to use the new features that come out, but am sick of keeping 2-3 versions of Premiere on my system so that I can open old projects reliably when clients want revisions etc. Do FCPX users and Avid users have to keep multiple versions of their software on their computer too?? I believe this is the biggest problem with Premiere and needs to be top of their priority list, before they lose faith in users with more examples like the poster above. Even after 2 bug fix updates to 2017 I'm still reluctant to download and use it professionally! Cheers, Mike
... View more
‎Mar 21, 2016
01:15 PM
Here's my experience: I had lines (and red frames) for 6 months early on (bought my nMP mid 2014 with D700). Since then I've had a great run without lines for about 14 months. I mounted my tube sideways, but that's about all I did differently. Now in the last month I'm getting many unknown export errors and the lines are back. I haven't changed anything during that time except to update to the latest version of Premiere - which also gives me flashing on long GOP .mxf files and laggy operation (not there in Pr 2014) after a couple of hours. I've switched to software only mode, which is at least reliable, and will contact Apple. If I could go back in time I would have spent my 11K differently, Cheers, Mike
... View more
‎Apr 17, 2015
10:55 AM
Thanks Kevin, good to know you guys are working on a fix for this as well as the lines.
... View more
‎Apr 17, 2015
10:26 AM
Hi WD Vid - Haven't seen the issue for a while... have only been exporting shorter projects lately. Will test in a week or so on a longer edit. I have been getting red frames as well as lines in exports. Like Kevin says, maybe heat is the issue as the times I've seen it are on projects over 20 or so minutes. It's a weird one though - I had a good patch of 3 or so months before the last update where I was issue free.
... View more
‎Mar 11, 2015
04:58 PM
Hi, I'll chime in again and say I'm still seeing the horizontal line issue randomly in exports on my nMP D700 - as well as red frames randomly in exports. I'm forced to using software only mode for exports which takes bloody ages. I'd be better off using my old 2008 Mac Pro with a GTX680 - which is ridiculous when I should be able to use my $11,000 NZD nMP. That's why I paid the big bucks, so I could have faster exports, stay on the Mac platform and get rid of the kernel panics I was having. My colleague has a 12core 2010 Mac Pro with a GTX680 card and is only about 40secs slower than me to export a 23min show...! The difference is his exports are perfect every time. This suggests to me that not only is the nMP having major, random, deal-breaker export glitches but it is also in no way optimised for Premiere Pro. It's enough to make you want to actually try FCPX. Cheers, Mike
... View more
‎Jan 21, 2015
01:45 AM
Just to join in... I took a chance on Premiere Pro over a year ago for broadcast work and I've now just about had it with this software - the lines in my exports are back, after being dormant for about 3 months. Then a few weeks ago I had a few red frames in my exports(wtf!) - deleting the media cache folders fixed that - but tonight my 52min broadcast master .mxf has the thin line glitches for the last 2 minutes of the file. Now I have to re-export (software only this time - about 3.5 hours) and re-watch it through like a hawk - again. It's late and I want to go to bed. Adobe, please fix exports from Premiere Pro CC on the 2013 MacPro. I never had issues like this back on FCP7. I don't care about fancy features, I want fast, rock-solid export of files from the timeline. For non deadline stuff these glitches means less time with the kids - but for deadline stuff it's death. I'm going to have to look for other options. MacPro 2013, D700, 32GB RAM, 512GB, Pegasus2 R6 raid - Mac OS 10.9.4 - latest Pr Pro CC Mike
... View more
‎Oct 10, 2014
12:16 AM
A lot of people are having exactly the same issue on quite a number of new MacPro's - that must mean if it's a hardware fault, then it's very, very specific hardware fault, identical on all machines. Surely software fault is more likely? Any word from Adobe lately on this? Anyway, hopefully your new machine gives you better luck Meanwhile a total Media Cache deletion and disk permissions repair has given me two clean 80min exports.... for now.
... View more
‎Oct 09, 2014
07:58 PM
Damn, just updated to Premiere Pro CC 8.1 and the line are back on ProRes export. Surely this is reproducible by Adobe - MacPro 2013 D700 running 10.9.4 and Premiere. It needs to be fixed ASAP.
... View more
‎Sep 18, 2014
03:01 PM
Just out of interest, do you have FCPX and or the AppleProResCodec.component installed?
... View more
‎Sep 07, 2014
09:06 PM
I'd had some luck since updating to OSX 10.9.4 on a 2013 Mac Pro - the random thin lines on ProRes exports from Pr CC 2014 seemed to have gone away. Today however the problem is back. The only difference is I installed FCPX and the ProApps update a few days ago to get ProRes export from RedCine. Maybe there is a conflict there? Either way, I'm running the latest Pr CC and 10.9.4 and need a fix ASAP. I need ProRes exports to be rock solid for my workflow. Mike
... View more
Copyright © 2024 Adobe. All rights reserved.
AdChoices