Dennis Radeke
Forum Replies Created
-
Hi Gabriel,
I would clear the media cache and also possibly trash your Premiere Pro preferences. Maybe AME too honestly. Those things should help you out.
If not, then you could turn off the GPU acceleration and try it again. Finally, I agree that updating drivers needlessly sometimes gives not so great results, but generally I am completely comfortable with updating NVIDIA drivers.
Dennis – Adobe guy
-
Did you try to reinstall the CUDA driver from the nvidia site? I would think that would do the trick.
-
Well, IMO the camera shoot definitely has a lot to do with it. The black background with strong lighting on all sides (of his head) could allow the editor to do a chroma on black and still maintain definition. I would think that the blend mode can help accentuate it a bit or a lot depending on the the shots you have. The contrast of light too might indicate a small glow effect, but I don’t think that it would make the shot per se.
-
Sorry guys, we don’t (and I can’t) comment on what we are working on. Any inferences you might make are entirely your own.
Thanks,
Dennis – Suddenly corporate Adobe sounding guy! 😉 -
[Richard Herd] “I tried to use the metadata stuff in Prelude, by recipe name and corresponding script. And then I’d have all these nifty subclips. It really did not work at all, because the information I typed into Prelude did not show up in the clips unless I opened the clips and looked at the markers, the GUI problem. (CS6, fyi).
I am basically committed to Adobe (although I love X too) (and will continue to argue with accounting for CC). Having said that, I hope Prelude can include a true metatagging/keywording interface.”
Hi Richard. With CC2014, we now have access to the comment markers of Prelude searchable in Premiere Pro. In addition, we have the search bin feature which creates a bin based on your criteria. So, if you wanted to create a bin for “Tomatoes” you could enter in “Tomatoes” and “Tomato” and it would create a bin for that. We also have a tag panel in Prelude that allows you to create custom tags (also searchable) that would hopefully allow you to easily log footage as a pre-production process.
[Richard Herd] “One more thing: Audio from Premiere to Audition is lame lame lame because when the audio goes from Premiere to Audition, the media is transcoded and the timecode is re-written to where ever it is in the Premiere time line. This means conforming any picture changes is virtually impossible, and I literally have to use old-school metadata: paper and pen. This hopefully has been fixed in CC.”
I think we’ve addressed this with later releases. Let me know if not.
[Richard Herd] “And changing audio output settings (ergo omf) is simply ridiculous: new sequence, change audio settings, copypasta. Roles win for this every time. There is no reason this cannot be done in Premiere via the mixer interface: I need a little button [export stems], and then whatever name they are is what they are named. When someone else (say in ProTools) opens it up, they see exactly what my mixer is. … and now I’m writing that as feature request”
We agree 100% 😉
-
We are identifying this as a bug and logging it. If you have a company name you want to put next to it, please respond and we’ll enter it next to the bug.
Dennis – Adobe guy
-
I would imagine this is so because of the absolute nature of frames and its history in film.
I’m curious as to why you would want it at 1 as opposed to zero. I’d just like to understand.
As for fixing it – file a feature request or bug report here: https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform
-
Two that I didn’t see on your list were:
Trash preferences
and this: https://helpx.adobe.com/creative-suite/kb/cs5-cleaner-tool-installation-problems.html
I would stick with latest NVIDIA drivers and certainly Premiere Pro 8.2.
HTH,
Dennis – Adobe guy -
The 5200 provides much of the same horsepower for less money.
https://www.nvidia.com/object/compare-quadro-gpus.html
-
Why don’t we get connected on LinkedIn? Probably easier that way anyway…