Larry Asbell
Forum Replies Created
-
In Premiere Pro, you can activate what FCP calls wireframe mode, by either single-clicking on the word “Motion” in the Effects Controls or by double-clicking the picture in the program monitor.
-
There has been no update to Premiere Pro since 7.1.2 which was made available 27 days ago.
I would speculate that the fix to your problem was more due to quitting restarting the program rather than the update. For some reason PPro seems to develop random faulty behaviors, solvable by restarting, more than a lot of other software.
-
Sorry but I don’t see your email to ping you directly. Would you be interested in a Mac Pro 4,1 3.32 GHz with 8 gigs? Could include a Sonnet 2 port SATA card and a firewire card.
Larry at LAEditing dot com
-
Should be Alt/Drag.
-
In Premiere, making a series of unique titles based on the first one is possible but is so error prone it is awful. Several ways that ought to work, don’t or are extremely convoluted.
However you seem to be saying option-drag is not working at all and I can’t say why that is. When I option drag to copy an existing title in the timeline, the copy has “Copy 01” added to the name. That tells me that the copy is unlinked and can be edited without affecting the original. Maybe you should skip trying to renaming the copy. In the timeline, just option-drag to copy, position the playhead over the copy, the double click on the copy, modify the text, and close the Text Tool.
-
This is, believe it or not, the way it is supposed to work. If you want the next title to be different, you option drag the first title to the next location and that will break the link. Or you can use the New Title button in the upper left of the Text Tool to make a title that is not linked. I can’t imagine what someone was thinking but Premiere’s been this way for many version, probably since the beginning. Why would the very rare case of wanting duped titles to mirror changes in the other be the default behavior?
-
[Morten Ranmar] “Also I cannot see how and where you can enter timecode IN and OUT points numerically in Avid.”
Click on monitor, type number, press IN.
-
Can’t speak for Adobe, but I can tell you that a GTX 760 2GB is working well in my MacPro 4,1. using Premier CC 7.1.
Setting Mercury Playback to use CUDA GPU performs much better than MPE in software. Rendering is much quicker too. I don’t how one measures degrees of improvement or what other details to check out that would tell if the acceleration is equal to other approved GPUs. Perhaps knowing how to interpret a utility like atMonitor to track GPU usage would help.
I will add that SpeedGrade now crashes on boot. Earlier, when it did not crash, it was unacceptably sluggish, but I gather that’s a pretty widespread experience with this SG version on Mac, and not necessarily related to which GPU. I’m keeping a eye out for a release that improves SpeadGrade.
-
On re-reading your orig post it occurs to me that your overall system performance could be the issue. I had an ATI 6870 1GB card in a MacPro running PPro CC and it played very stuttery. I changed to a different card and now get better playback.
But to your original bottom line question — no your exports should not be affected, as long as they are a codec and data rate that you Mac can handle.
-
Your original footage is on your Thunderbolt external drive so that plays fine. But after you rendered the effects, the preview files that were created are located where? It’s the performance of playing back those files that matters now. You say you changed the location of of the scratch disk. I wonder if that only affects the location of newly created preview files? Are there still preview files on your system drive? Look inside the folder at this location:
users/your user/documents/Adobe/Premiere Pro/premiere version number/Adobe Premiere Pro Preview Files/your project name
If preview files remained there you could delete them and re-render the sequence so they will be on your media drive (alternatively you could move them but I can’t tell you for sure whether they will relink).
I suppose another possible cause of poor playback of rendered files could be an inefficient codec for preview files, which you set in sequence settings.