Dennis Radeke
Forum Replies Created
-
[Scott Witthaus] “I will keep a log when I start my trial. Might be an interesting post we can debate in the future!”
Sounds like a plan and an interesting conversation. will look forward to it!
Dennis – Adobe guy
-
[Scott Witthaus] “The 30 days starts from the time you install the software not the download date, correct?”
Yes, correct Scott.
[Scott Witthaus] “I am actually looking forward to seeing what the improvements are in CC versus CS6.”
I find the Wikipedia article to give a fairly good sense of the changes from one version to another. I’m pretty sure it’s an Adobe employee who keeps the article up to date.
https://en.wikipedia.org/wiki/Adobe_Premiere_Pro
[Scott Witthaus] “Like it or not, Premier is something that freelancers need to know these days.”
Clearly, I like it, but you’d be surprised if I said otherwise, no?
Also, just my pet peeve, but my yearly New Year’s hope is that folks in the business will spell Premiere Pro correctly. Yup, I know – small pet peeve…
-
[Michael Hancock] “Unless they changed it recently, you don’t need a credit card to try the trial. You just download the software you want to try, hit “Trial”, and for 30 days you’re good to go. After that, you’re locked out unless you subscribe.
It’s not like Netflix where you basically sign up for their service and they give you 2 weeks for free as a “trial”, and it’s your responsibility to cancel before those two weeks are up. Adobe is 100% free (unless it’s changed recently).”
Yes, that is correct. You create an Adobe ID (like your AppleID, Microsoft ID, Amazon ID, etc…sigh – too many passwords…) and any and all products you download will work from 30 days of signing up.
-
[James Ewart] “I’m sure I read here some time back that Adobe’s Mercury Playback engine was the thing that made them throw in the towel.”
That’s flattering for Adobe to be sure, but I would imagine (officially my guess only) that the effort to move the existing code base to 64-bit cocoa was a bigger effort than just starting over. They were likely bit by their own decision to drop ‘carbon’ – the effort to allow existing 32-bit apps to move over to 64-bit.
-
I’m sure many others will chime in here, but the big thing that sticks out to me is your lack of RAM. If you’re cutting a feature, you absolutely need to max the RAM on the system. 64GB of RAM isn’t anything crazy and borderline not enough for 64-bit NLE applications and raw footage.
If you are choosing between NLE’s, I’m sure you’ll get lots of good opinions.
As for proxy vs native media, I think native media is preferable but many times not practical based on storage, turnaround time, demand on the systems, the production workflow of the overall editing team, etc. Ultimately, you have to make that decision, but if you’re not completely sure about native media, than transcoding to a proxy style format is probably a good choice. In another few years though, I think native media will be even with proxy workflows if not the standard.
Good luck!
Dennis – Adobe guy -
Well, in general, you have an OS and version of software that are several years removed from one another, so it’s quite possible that your problem lies there somewhere.
If you’re having display issues, then the best thing to try is to see if there are any graphics drivers that you can update. Specifically, if you have a Macbook that has a NVIDIA graphics card, make sure you install the CUDA drivers from the NVIDIA website. If you’ve updated to Mavericks, then make sure you’re on the latest version which is currently 10.9.5. Also, make sure you have the latest version of CS4 which I think is 4.2.1 – Premiere Pro product updates
Finally, you can try Creative Cloud for free for 30 days. The latest version definitely will give you the support you need as well as all the features from 5 subsequent versions.
Good luck,
Dennis – Adobe guy -
Always tough to say on things like this. What I see mostly is RGB separation.
There is this: https://aescripts.com/separate-rgb/
If you’re looking for an internal effect, you might look at Channel Mixer to see if that gives you what you’re looking for. If the lens distortion is added, there is an effect for that as well.
HTH,
Dennis -
It’s because you didn’t spell Premiere Pro correctly….
If what Ryan said doesn’t set you straight, let us know. Perhaps one easier thing to do is quit and relaunch the Creative Cloud application which will ping the server on reboot for any updates.
Dennis – Adobe guy
-
Hi Mitch,
Here’s something you could try. With Premiere Pro CC 2014, you can use the Media Browser to look at Premiere Pro projects. In fact you can have as many Premiere Pro projects open at one time by using multiple media browsers and loading any sequences into the source view.
Using that idea, you can create a template project that has all of your clips, title slugs, bumpers, etc. and be able to grab the parts that you want easily and use them in a new project.
Other things to consider would be to update your graphics drivers, increase the RAM and delete your prefs as well as your media cache. I generally recommend at least 16GB of RAM and 32 or 64GB is not too much. If you’re looking for more information, please post some specifics about the system that you’re using.
Hope this helps and Merry Christmas,
Dennis -
Chip,
If it begins to infect the OS operations, then most likely, the problem is not located with Premiere Pro. It clearly sounds like a hardware problem. By chance do you have a new MacPro?
In addition to troubleshooting Premiere Pro and your OS, I would highly recommend you get in touch with Apple or take your box down to the Apple store to get it looked at and explain your problem.
Dennis – Adobe guy
Merry Christmas