Jon Collins
Forum Replies Created
-
Hi Paul,
Not entirely… by setting a sequence to ProRes, Premiere will only render previews in ProRes. So if for example you stick a bit of a grade on there and some transitions, Premiere will render the necessary media to ProRes with effects on to playback usually on the fly. When you export (unless you enable the “use previews” option which is not recommended), Premiere will use the original linked media, so in this case XAVC-I, for export.
Cheers,
JonJon Collins
Director // Editor // Motion Graphics -
Hi Paul,
Setting the sequence to ProRes 422 is a standard thing with all my sequences. ProRes has always run much more happily on a Mac than Premiere’s MPEG format so I would advise you to do the same thing with all yours. I found this tip out when managing a production team at an agency and we found that this cut our crashes by at least 90%.
Cheers,
JonJon Collins
Director // Editor // Motion Graphics -
Interesting to hear. I hit a brick wall last week. The Adobe guys spent 2 days going over my setup with 4 screen shares, phone calls and support threads. Shooting on FS7 editing on IMac 5K. They couldn’t work out the problem. I eventually figured out PluralEyes was rearing it’s ugly head again and despite being years since corruption issue were first spotted, PluralEyes had somehow corrupted not just the project but also all the media caches too so no other projects would play back.
The senior engineer I talked to at Adobe said there was 99% chance that what I was suggesting couldn’t happen, but after deleting the media cache, all was good in the other projects. The corrupt project is all but a write off.
Anyway, might be worth deleting the media cache files if you keep encountering issues.
Cheers,
Jon -
A little late to the party on this one but… The Media Browser import sequence feature is great, but sometimes you don’t want to bog down a project by importing an entire sequence into it. I’ve just written a quick tutorial on how to run multiple Premiere Pro projects at one time, from one click on the dock.
Jon Collins
Director // Editor // Motion Graphics -
I’m a bit late to the party on this, but this has been an issue that annoyed me as well. I however found a work around which I’ve written a quick tutorial on over here: Opening second instance of Premiere Pro.
Jon
Jon Collins
Director // Editor // Motion Graphics -
For this, 3D camera tracking would definitely be the quickest option I think. It’s not obvious what the current problem is but I suspect the area to track is too small and the search area too big.
Hope that helps!
Jon Collins
Director // Editor // Motion Graphics -
Hi Esther,
It sounds like you may be doing something wrong if it’s taking a long time (more than 5 secs) per frame with that amount of RAM. It’s possible that you’ve not set the tracking point reference area to the correct size. This is the area that the tracker analyses to see where you’re reference has moved to in that particular frame.
You have to analyse all the footage you want to track before applying to a NULL.
On the frame before your tracking point disappears, you can reset the tracking point by holding down ALT and moving the the tracker. This will keep the tracking crosshairs in the same place whilst moving the tracker.
Jon Collins
Director // Editor // Motion Graphics/ -
Hi there,
There tends to be a lot of frustration when you first start with AE… but stick with it!
It’s not entirely clear what you’re trying to do, but I think you might find the 3D Camera Tracker tool more useful for this. Check out the tutorial from Adobe: https://tv.adobe.com/watch/learn-after-effects-cs6/3d-camera-tracker/
Cheers,
Jon