I've also been experiencing problems with open captions in 2015.4...The program has crashed a few times when I've been working on it, and I can't seem to keep the captions aligned. I will align all of my captions with the bottom centre of the screen, only to find that when exporting my movie (or returning to it after I've saved everything and quit) the captions have different alignments...This causes some of the captions to stretch beyond the screen. Don't know what to do!
↧
Re: Warning: Captioning in 2015.3 is BROKEN!
↧
Re: Error Compiling Movie GPU/Lumetri with Premiere 2015.3
Hmm... I was just able to "fix" my Lumetri GPU render issue and then reproduce it at will by modifying my project in a particular way. Given the nature of the modification, at least in the instance I'm seeing, this doesn't seem to have anything to do with the GPU. Note, there may be many ways to reproduce this bug so maybe I'm just seeing one instance here, and maybe I was lucky to cross its path, where it may not be the primary instance we've seen.
First, keep in mind I'm still wrapping my head around a lot of info so I don't want to draw any incorrect conclusions... so let's assume the aforementioned is assumptive at this point based on what seems apparent to me as a user (not a Premiere internals expert)... I just can't see this particular instance of repro being a GPU issue but am welcome to hearing otherwise.
Here is the error I just reproduced at will...
...on the surface, pretty much what we've seen I think.
I have multicam footage where only one cam is ultimately currently being used, and it's footage has one single lumetri. For now let's just assume it's a simple sequence with a MOV from Canon footage that has a single Lumetri applied.
Today I noticed that one clip was appearing black in program monitor when scrubbing from the main timeline (which hosts the sequence in question). I disable the one lumetri, the clip becomes visible. I ask myself why?
I noticed the lumetri effect had an input LUT "CANON 7D - SL - PROFILE" ... I set it to NONE and the clip then becomes visible in the Program Monitor. I'm wondering why, but first I had to wrap my head around how I'd originally set that LUT up...
I tried to reselect the LUT in the drop down menu but it was not present. When thinking about this, I vaguely recall having tried a built-in Canon lumetri preset, after which I made my own lumetri preset. I had applied the built-in "SL Neutral Start (Canon 7D)", liked my settings, saved my own preset, and then today I removed/reinstalled Premiere, keeping my settings. I opened my project I'd last used successfully days ago, and it failed to render.
Quick side note... I notice my preset created before reinstalling Premiere has a weird red/white checker icon (on right below), while the newly created one has a nice/picture icon (on left below)...
... not sure if that's important.
Another weird side note thing I notice... if I apply built-in preset "SL Neutral Start (Canon 7D)" that's what the lumetri effect will show for the LUT until I close and reopen the project, at which time it will read as "CANON 7D - SL - PROFILE"... all this just seemed odd to me because I was simply trying to retrace how my Lumetri effect was originally applied in the first place, hopefully to understand what had changed to break things, but in that effort I was totally confused by the odd LUT naming which was different than the original name, and the red/white checker and all that. The overall UX was a bit odd and when trying to troubeshoot another problem (the GPU render failure error) those sorts of things can confuse matters... I guess don't let it confuse matters but FYI in case it helps to know.
Going back to the main topic...
So I basically recreated my Lumetri effects by re-dragging a new one from the built-in preset, then copied/pasted my own settings such as exposure tweaks from the "broken" lumetri effect into the new one. I then saved a new preset with my own name. Now program monitor worked fine, as well as exporting/encoding... great!
An aside, I exported both my old "broken" Lumetri preset, as well as the new one I just created to fix things, and compared the resulting XML files , discovering some differences, but mostly all the name.
Okay, now things were working, so I wanted to try to break things again... so I simply applied back my older preset, the so-called "broken" lumetri effect, and tried to export/encode, and it fails with the so-called GPU error.
So this "broken" lumetri preset applied to my footage causes the same failure we've been seeing... this type of "soft" change causing this failure hardly seems attributable to the GPU.
While this particular flavor of repro may be different from others, we can't really know that from the error alone. The error seems identical. At the very least this means that the error code in question seems easily producible by applying certain settings to the Lumetri effect.
Also, since I had not edited the Lumetri effect since last successfully using this project some days ago, it seems that the Lumetri effect itself and/or its state based on how the software interpreted it, perhaps after having reinstalled Premiere, was somehow changed or different. It makes me wonder if there's cases where these Lumetri effect settings can become fragile based on how one uses the software or perhaps in how one configures/re-installs it. It also makes me wonder if there's some sort of fragility exposed in the underlying rendering engine when the soft configuration of these Lumetri effects is someone modified incorrectly in some way.
There's also nothing to indicate the Lumetri effects were not fine and that the GPU was failing to Premiere based on not being able to handle some operations but I'm less inclined to put more weigh on that avenue given my sense of everything here.
All assumptive and I'm thinking aloud but simply reproducing the same old top-level GPU error message after applying an old Lumetri preset seems to indicate the preset itself and how it affects the settings of the effect can easily induce this error message... which makes the error message seem to me to be, at least in one case, less GPU-related and more Adobe software related... that's assumptive... but hopefully you can see why I wonder this.
What do you all think?
↧
↧
Re: Long Capture unsupported format damaged file
Hi federomano,
I know it's been a while since you did this but would you be able to walk me through this JPEG codec process please? Were you able to recover your corrupt capture?
Thanks!
↧
Re: How do I get Open CL?
HI,
최근 클라우드 CC 업데이트 이후 부터,
에프터 이펙트, 프리미어, 미디어엔코더에서 open cl 선택 창이 활성화 되지 않습니다.
어떻게 조치하면 좋을까요?
비디오카드 정보는 아래를 참고 부탁드립니다.
* intel(R) HD Graphics 5500 1G RAM + AMD Radeon R7 M270 4G RAM
↧
Re: Adobe Premiere Pro CC Glitches Screen & Crashes Computer
First I've got a few questions.
Does your mac have both an integrated and a discreet graphics card? Many of the 2010-2013 models have had a similar issue where the part of the hardware that actually handles the switch causes a kernel panic. That sounds like a similar issue, but maybe not exact to your situation. IF you are suffering from this bug, they'll be very quick to tell you that you're beyond their "free fix" or "warranty". Get tough. Remind them of any "Lemon Laws" in your place of residence, which usually detail procedures for lawsuits and public humiliation for not repairing a problem that was initially part of the hardware. Alternatively, go to system prefs, energy saver, turn off the automatic switching and live with less battery life.
They replaced the mobo? Exact same model? If so, have them check the above issue (two gfx cards, one high power, one run from processor core; switching problem).
Other problems:
Make sure you fully uninstall any cuda driver. It will foul up. In fact, uninstall every external driver you've got besides the apple supplied. If you still have problems, your video codecs may be corrupted and you may have to re-install adobe along with them. Do it in the following order:
Codecs for prores, dnxhd, mxf (if you have any proprietary), and any other x264 or x265's, then adobe software (this will force adobe to search for your installed codecs that match it's set of presets and run them directly, rather than through a connect-server that's 32bit). IF neither of these solves your problem, then your video files may be corrupted. Place them back in the camera, and connect the camera (if possible) directly. Now you will be able to transcode them out using the camera as a go-between, which should handle many issues that arise from working from a card directly or with a corrupted transcode.
↧
↧
Re: CC 2015 .4 - MTS files stall loading, crashes
I have experienced massive crashes and loss of video. When forced to do a hard reset and close the program, the projects never save. I'm running a 16GB iMac with a 3.3 GHz Intel Core i7 processor I purchased this year. I don't think this is a ram issue in my case. My client's projects are behind, I desperately need some help. I was able to load about a 3rd of my clips each time before it crashed. I have no idea what else to do.
↧
Re: 2015.3 Issue, sharpen makes video go black
Wlord, the lumatri sharpen is under the color panel-creative.
Ann, my problem is general, not a sharpen or any other effect problem.
↧
Re: Lag out of the blue
Did you recently update to 2015.4? Do you see Preimiere'a RAM usage spiking?
↧
Re: Could not write XMP data in output file
PrPro doth not do well with blank/empty video track spaces ... it's better to put black video in a sequence than leave a space. Exports with blank spaces will very often have issues ... some very odd ones have been reported here at times that when blank spaces in the sequence were found and "filled", suddenly ... the oddities ceased.
Neil
↧
↧
Re: Is Adobe Premiere Pro Downloadable or cloud based only
Highly recommend the AdobeTV tuturials & such for starters. Then ... I've used a LOT of the lynda.com tutorials. Yea, it's a monthly-fee site, but the training is good, if you pay a bit more you can download the full projects the instructor is using and do the same thing yourself, and they have from how-to-get-started through rather advanced tutorials.
On enough software you can learn all sorts of things ... and amazingly, what I've had to learn over the last fours years keeps expanding.
Neil
↧
Re: Crashing while rebuilding cache after 2015.3 update
There is a noted RAM 'bug' on certain systems/conditions sort of thing. For the most part, people have got 'around' it by going back to the 9.x builds of 2015.0/1/2.
Unfortunately, seeing all this now sounds like your computer is having this issue. You might search through the forum for the threads with RAM/memory-leak issues.
Neil
↧
Re: Lag out of the blue
Nope havnt done a single upgrade since I got the program. Running 2015.0 release and it has been totaly stable up until now.
↧
Re: Error Compiling Movie GPU/Lumetri with Premiere 2015.3
Well ... if I'd heard about the use of the Canon 7D SL Profile Look, at the beginning, I'd a said remove it. That Look preset IS your issue.
There was a whole group of camera-specific "Looks" created for PrPro that were in the 2014 releases. The reason those are all in a 'Legacy' folder in the 10.x builds of 2015.3/4 is because there were a LOT of users that had issues like this with them. So they removed them from the easily-findable ones that people 'browse' though they're still loaded with the program IF ... you insist on using them anyway.
Yea, with a bit of practice, you can make better ones for yourself anyways.
Neil
↧
↧
Re: Lag out of the blue
Check the Help/About dialog box, and note the release and build numbers there. Are you really still on 2015.0? That's over a year old, now.
Neil
↧
Re: Lag out of the blue
Yup just checked. There is no reason it should be doing this though.
↧
Re: Sequence setting for downloaded footage and codecs.
First, you should figure out what the codecs are ... you can get some idea in Finder/Explorer, but MediaInfo (a free download) is a very handy tool to have on your machine anyway. Open it, drag/drop a file from Finder/Explorer onto it, and go to Tree View, and it will show you an amazing amount of info on that file.
Media Info: https://mediaarea.net/en/MediaInfo
You'd be able to get the codecs, frame rate & size, all sorts of useful things.
Once you know frame-sizes say, you can determine what frame-size should be your 'base' frame-size for your project. You can always put 'bigger' files on it, but up-sizing smaller files always shows some degradation.
Neil
↧
Re: Lag out of the blue
Well, there's no reason my back should be sore tonight, but there it is.
This is a complicated program and things DO get out of whack at times, just like my back, and often for seemingly no reason at all. Or not one at least that SEEMS like it should be a reason. So in the real world, we editor types get to puzzle this program through occasionally. Hopefully, not too often.
Are you working only with one project right now? If so ... have you checked to see what it behaves like starting up and using a different or perhaps new project? As sometimes projects get things screwy, and or the project files get corrupted.
Have you tried deleting the media cache and media cache database for PrPro?
Neil
↧
↧
Re: Best Way to Match Shots
Thanks for all the great information!
I used the Premiere/SpeedGrade converter tool and it worked! Thank you very much for this valuable resource. But why the heck did Adobe completely just kill the Dynamic Link functionality? It wasn't a technical reason, because obviously you can get around it with this conversion tool. It is definitely Adobe's way to say, "Surprise, we are getting rid of SpeedGrade!" But rather than just tell us why, they simply try to quietly phrase it out by breaking the connection. They basically did the same thing with Encore. I love what the Adobe Creative Cloud Team has come up with, but how they just kill functionality, without warning, is very frustrating. It makes you not want to upgrade, because you don't know what else they have simply dropped.
In regards to no more SpeedGrade, I can now see a lot of people jumping ship for Blackmagic's DaVinci Resolve. It looks to be an amazing application. And it's free!: Blackmagic Design: DaVinci Resolve 12
Thanks again for the advice and help. I am going to try out the suggestions.
Cheers,
Michael
↧
Re: Lag out of the blue
Ya I'm working with multiple projects and I even started a new one just to test. If I delete the media cache will that mess up my projects?
↧
Re: Lag out of the blue
Yo I cleared the cache and now it'sworking much better. Thanks a ton m8
↧