Forum Replies Created
-
Dennis Radeke
April 27, 2014 at 11:52 pm in reply to: Closed Captions not retaining colors when exportedHi there,
Here is the help files on closed captioning. There is a lot of good information there. Remember closed captioning is there for the hearing impaired and has to be turned on in order to be viewed on a TV or broadcast. Our format support as well as a variety of helpful tips are there. If you’re doing english, I’d suggest CC1 and 608 subtitles, not 708. You also need to make sure that your source and program monitors are defaulting to the correct display (608 or 708). There are a number of areas where you can get mixed up so again the link is a good one to review. Hope this helps
Adobe Closed Caption Help Link
Dennis – Adobe guy
-
It does sound like a hardware issue, but lets try one thing on the software side: trash your preferences.
Beyond that, I’d have two suggestions. What was the last thing you changed before you had the problem? Software update? Added a hardware piece? If so, undo that and see if that addresses your problem. The other suggestion is a bit of a reach, but I wonder if one of your sticks of RAM went bad? Taking a long time to render might be indicative of a RAM chip going bad. It’s not a high probability but you’ve tried most of the main things.
Oh also if you reinstalled the Adobe apps, did you try the Adobe Cleaner tool first after you uninstalled? Worth a try if you didn’t.
Hope this helps,
Dennis – Adobe guy -
Dennis Radeke
April 21, 2014 at 11:24 am in reply to: adobe premiere render hungry / red line at every moveHi Chuck,
I assume you’re talking about a 4 point garbage matte in which case you would benefit from a supported OpenCL/CUDA graphics card since that effect (among many others) is GPU accelerated. Beyond that, if you’re doing a manual track with this matte, you will find that we have a new masking and tracking feature coming up in the next major release. Here’s one non-Adobe article on it: New Features in Premiere Pro and After Effects
Hope this helps,
Dennis – Adobe guy -
[Justin Crowell] “Al retracted that tweet. I know you can’t REALLY do that…once it’s out there, it’s out there…but he copped to making a big mistake, and regrets it.”
Indeed. Mistake made, apology offered, nothing else to do but move on. To those of you who know Al, he is without doubt, one of the most sensitive people I know. NAB for a vendor is also pretty stressful. That’s not an excuse nor does his retracted statement reflect Adobe’s commitment and passion to our customers. He said something in the heat of the moment and quickly said, “I said something really stupid the other day, and I am really sorry. Thanks for calling me out. Normal service is resumed.”
’nuff said,
Dennis – Adobe guy -
[Charlie Austin] “I’m just a little tired of the high and mighty “FCP is not Professional” bullsh*t. That’s all.”
Oh, the irony…
Charlie, I feel for you…in fact I understand exactly how you feel. As an Adobe employee for over 9 years, I saw where Premiere Pro was headed yet had to endure the perception that Premiere Pro is just for prosumers and hobbyists. Now, that has changed and people recognize Adobe’s commitment to our customers through innovation.
My advice is to not worry about what other people say – if you enjoy FCPX, then rock on and have fun. Time will tell if it sheds its current perception, but that shouldn’t matter to those people who enjoy it.
-
We have identified this as something our users would like us to fix. We plan to…Soon…
-
Dennis Radeke
March 27, 2014 at 1:27 pm in reply to: Software Install Clash? (Avid vs Premiere vs FCP)We cannot comment on when new versions are coming out. Sorry.
-
Dennis Radeke
March 27, 2014 at 12:50 pm in reply to: Software Install Clash? (Avid vs Premiere vs FCP)[Arthur Graham-Maw] “Does the Adobe CC package include the ProRes codec license to decode as well as encode?”
Yes, absolutely.
-
Dennis Radeke
March 26, 2014 at 7:53 pm in reply to: Software Install Clash? (Avid vs Premiere vs FCP)In general there are not any issues from the Adobe side, though I do know of a problem with the latest Apple codecs update ( a post Mavericks update) that will create some problems for us.
As for installing FCPX for ProRes, that is NOT necessary since we licensed ProRes as part of the Creative Cloud release.
HTH,
Dennis -
[Mathieu Ghekiere] “Adobe only really pushed with Premiere development when the FCPX debacle broke out.”
Wow…nothing couldn’t be further from the truth.
Adobe moved to 64-bit at the height of FCP’s popularity – so we weren’t investing or ‘pushing’ the product then? A complete re-write that cost millions of dollars? Only Apple can do that? What about GPU innovation? First to have a usable editor for DSLR footage? This is all CS…5 in 2010!
At the end of the day, the market reacted to FCP X by embracing other editors including Premiere Pro which perhaps is a more accurate description.
Of course you’re entitled to your opinion and I do wish you all success with your choice of FCP X, but Adobe (or any company for that matter) makes a product with purpose and determination.
Dennis – Adobe guy