Thanks, Mo. We're using 2017.2 (14.2.1.34), so this is a non-issue. After Effects is definitely not changing the cache location; unless the external cache is removed when the program starts up, it stays pointed to the external SSD drive. ... View more

I know I'm just reviving a necro post here, but figured I'd post in the hopes of saving some other poor soul from this hassle. The redefinery scripts have a ShapesToMask script that works like a charm. I'm not going to name names, here, but some people might even say that it handles the conversion exactly the way After Effects should have been doing it for the past, say, decade or so. The rd: scripts are free for everyone, though they encourage an in-kind donation to charity, if you feel so inclined. link: redefinery.com: rd: scripts ... View more

We rarely work with QT formats any more, so this tip might be hopelessly out of date; have you tried exporting h264 MP4s and just changing the file extension to .mov? We used to do that all the time, and rarely (if ever) had a problem. ... View more

Thanks for the reply, ProDesignTools​. That's some straight-up —, right there. If I were a betting man, I'd say that the likelihood of Adobe actually listening to any sort of customer feedback is pretty much nil...  😕 If anyone happens to have the installer kicking around, please shoot me a DM! Moderator Warning: Do not use profanity, even if only implied, misspelled, etc. We have minors reading this forum, so keep that in mind. ... View more

I thought this had been solved...? It's been MONTHS. WATF, Adobe. I need to install Premiere 2017.1.2 for OSX; Creative Cloud will only let me do 9.0 or 11.1.4? STILL?!? Man, get your stuff together, Adobe... This juvenile — match with Dolby is ridiculous. Does anyone have an installer for 11.1.2? Moderator Warning: Please do not use profanity. It is against community guidelines. Keep in mind that minors are reading this forum, so please consider their well being when posting. ... View more

Hi Victor, As TaranVH mentioned, Match Frame has nothing to do with framerates; it matches the frame that your sequence panel playhead is on back to the identical frame on the original source clip. Match Frame won't actually change any of your clip or sequence settings. Think of it like telling Premiere "hey, show me where this frame came from". The only way I know of changing the framerate of your clips is by interpreting the footage (explained by TaranVH above). I think I might know what issue you're having, but I'm not totally clear on what's happening in your project, based on your description. So, I'm working on a project right now using footage shot at 59.94. When I imported the footage into Premiere (dragging from the Media Browser panel), Premiere assumes that the framerate is 23.976, and plays the clip back in slow motion (I have no idea why it chose 23.976; maybe someone else can shed some light on that?). I'm cutting in 29.97, so I right-click on all of the footage in my bin and choose Modify > Interpret Footage; in there, I tell the footage to assume the frame rate 29.97. The clips play back at 50% speed (as 29.97 is exactly half of 59.94). Someone can correct me here, but if you shot at 50fps and Pr is playing the clips back at 25fps, they should be playing back at 50% speed, which would be really obvious when you're trying to edit. By the same token, if you change the interpretation of your 25fps footage to 50fps, it should play back at double speed (which is, I assume, totally not what you want). If everything is playing back at normal speed at 25fps, are you sure you shot it at 50p? The simplest explanation would be that you shot it in 50i, and Premiere is playing it back progressive (merging the two fields into a single frame). If your cut works properly in the 50fps sequence that Meg helped you create, I'd just export a 50fps file from it. I'm worried that if you start futzing around with interpreting the footage to a different framerate, you edit could wind up getting completely borked. ... View more

BOOM. Done. It totally works with sequence timecode set. Thanks for the help! ... View more

So I tried this out on a couple of different machines yesterday, and still have the same result (i.e. nothing...). It's got to be a workflow issue, but I'm not sure what I'm doing wrong. Here's my process in as much detail as possible: I'm in my Timeline panel, working with basic multi-cammed interview clips -- 2 cameras, video nested -- on V1 with a separate, offboard audio track from location sound on A1. As I'm playing through the interview, I'll select the video track and add a marker (usually with a KB shortcut, but sometime with the Add Marker button on the top L of the Timeline panel). The result is a marker added to the video clip only. It shows up in the Marker panel, where I double-click on the thumbnail to change the marker colour, exit from the dialogue box, then enter a comment in the text box in the Marker panel -- something like "My name is Frankie P. Cheesewinkle, and I moved here in 1997 to join the outlaw biker gang 'All's Gouda'". I continue playing the clip and adding markers using that same process, effectively giving us a super rough, basic transcription in the Marker panel. In editing, we sort the clips by colour to find different interview subjects. Clicking anywhere in the Marker panel doesn't move the playhead at all; I can edit the in/out times for each marker and edit the text, but nothing else happens when I click on the marker. Are you guys running Premiere 11.1.1, or an older version? This feels like a total n00b question, but what workflow do you guys use in order to get the markers to work properly? ... View more

I don't know if it's a settings issue on this end or what, but clicking on a marker in the Marker Panel absolutely does not cue the playhead on this machine. +1 on the functionality, though. Those would be super helpful features. I'd be happy with having the existing features actually work properly, for the time being... ETorr  wrote A single-click on a marker in the Markers Panel cues the playhead. Would be great to add functionality to the Markers Panel: - Ability to sort by Marker Name, Marker Comment, In point, Out Point - Additional headers, sortable by those headers: Marker Duration (if any), Marker Color, Marker Type, and Any additional Custom-Defined Headers - Filterability of markers based on any of the above. - Ability to see markers across multiple bin items to increase power navigability ... View more

Thanks, Meg. I've marked your answer as correct; it's obviously an issue with our setup, somehow. I'll mess around with our Windows machines and see if I can narrow it down. ... View more

WAT What are your system specs? It absolutely does NOT work that way on this machine... Clicking on markers in the Marker panel does literally nothing... Late-2013 (Trashcan) MacPro OSX 10.11.6 PProCC2017 (spring 2017 release) I'll have to try this out on one of our Windows boxes...! ... View more

Thanks, Meg. This is kind of a roundabout way of doing what I'm looking for, and depends on all of the markers having unique keywords -- finding a specific clip about "cheese" in a feature-length documentary about, say, Fondue might be a little cumbersome. Ideally, what I'm looking for is something like this: Producer says, like, "why don't we try that clip where the outlaw biker talks about how much he likes eating cheese?" *sort markers by colour > red (the colour denoting that this is a clip from the biker) *3rd marker on the list is a comment marker: "i really like eating cheese" *click on marker or alt-click on marker or right-click on marker, select "Go to Marker" *Playhead jumps to clip on timeline, I grab it and drag it into its new place If you're familiar with the order and layout of the markers in your Marker panel, it's super quick to find a particular clip (marker) ... View more

I don't really have an answer, but to wonder aloud: Didn't Apple finally get around to modernizing ProRes a few months ago? Could this have anything to do with that? Or maybe the ProRes isn't "true" Apple ProRes, but was encoded on a PC using FFmpeg? I haven't worked with ProRes in ages... I'd be curious as well to hear if anyone else is experiencing issues w/ ProRes ... View more

BOOM. Done. Thanks for the tip! ... View more

Bizarre... What platform are you on? This machine is running OSX 10.11 I've tried resetting the workspaces, but that doesn't seem to help. Is there a hidden toggle for it somewhere...? **edit** If you right-click on the image pop-up and select "open image in new tab" or "view image", you can see the full-rez version ... View more

There are a bunch of different ways you could do it. One super basic, quick-and-dirty way would be to key yourself out of the greenscreen, duplicate that layer, place it in front of your fog layers, and KF the opacity as you walk "through" the fog. So, your keyed FG layer starts as totally transparent, then becomes more visible as you move towards the camera. if you want to get super fancy with it, you can generate some really great looking fog layers in C4D using a plugin called TurbulenceFD from Jawset. You can create fog that reacts to a solid body passing through it, then composite that into your live action footage. ... View more

This is maybe not the most elegant (or cheapest) solution, but we run our projects off of fast internal drives; any primary assets, like footage, sit on SSDs, while the project files are on a fast HDD. Those drives are synced to a NAS, with the "Program Files" drive syncing twice a day (at lunchtime and in the evening), and the "Assets" syncing once per day (the cache files are never synced); "Program Files" are backed up to a cloud service once a day. The NAS is mirrored onto a JBOD array twice a week; every two weeks, the JBOD is backed up offsite onto a RAID5 array. If the internal drives fail, we're losing at most a few hours worth of work; the assets don't typically update super frequently, so the likelihood of losing those are pretty slim. If our computers all died, and the NAS hardware went down or somehow lost 3+ drives at the same time, it'd be a pretty big hassle, but the JBOD array could be used to get things up and running again on a single machine. If the place burned to the ground, we'd lose some assets, but could recover most of the work. I try to make sure there are 3 copies of everything, including an offsite backup. The easiest thing for you might be to pick up a couple of RAID-capable enclosures, and throw some big HDDs in them. Set your work computer up to sync to one of the enclosures once a day, and make a periodic duplicate of that that you can store at, like, a friend's house. ... View more

Media files deleted after 2017.1 upgrade ... View more

11.1.1 was an emergency patch to fix the serious bug in 11.1.0 where Premiere was permanently deleting project media, no? It's not an actual bugfix patch? IIRC, the media deletion bug had to do with Premiere 11.1's new auto cache deletion function, and had something to do with the location of the cache --- i.e. if the cache files were stored next to your media, Premiere would just delete everything in the folder, rather than differentiating between the cache files and your media. I think that's what the issue is, anyway...? It's entirely possible that instead of actually fixing the problem, the 11.1.1 patch just disabled the ability to have your cache files saved next to your original footage. If Adobe can actually figure out the bug, maybe they'll restore the functionality in a later version? Dunno for sure; that's just a guess. Frankly, it's probably safer and easier just to stick with 11.0.2 for a few more months... ... View more

I'm not totally clear on what you're talking about, but from what I can make of your post, I think we're having the same problem (?). Dual monitor setup (1440p, not 4k), OSX, Trashcan (D500). When I launch an Adobe app, the mouse position is registered improperly by the app, if I'm trying to drag an item into a bin, the item will often end up in the wrong bin, as the app thinks the mouse is around 75-80 pix lower than it's appearing on screen. Same thing happens when dragging footage around in the timeline --- the clip will end up on the wrong track. FWIW, this only happens on our Trashcan; the Windows computers and iMacs are fine. After beating my head against the wall, my best guess is that it's an OSX issue; I first started seeing it after updating to, I think, El Capitan (??? who can keep track of these stupid OS names any more...?); no issues with 10.9 (OSX Zip Zorpo or whatever it's called). The problem occurs with all versions of Premiere, AE and Audition installed on the machine, as well as one or two other apps -- basically anything that runs in a dual-monitor workspace spanning both screens (workspaces with undocked, floating panels don't exhibit the same problem). The problem occurs in versions of CC that had been installed (and working just fine) before the OSX update, so I don't see how it can possibly be an Adobe bug. I'm not exactly holding my breath for a fix from Apple; I've found that the simplest workaround is just to slightly re-size the program window -- grab the bottom right corner of the program window, drag it up a little, then back down to where it was. It takes about 2 seconds, and lasts until you close the program. When you re-open, you'll have to repeat the process. That seems to force OSX to re-adjust where it thinks elements of the UI are, and everything functions as normal again. ... View more

This is probably more of an After Effects question... I'm not sure what part of the "zoom effect" you're talking about, but the shots themselves were done with a steadycam (or, more likely, with a DSLR-style camera mounted on a smaller gimbal rig), smoothing them out; The post person threw a keyframed Optics Compensation filter on top, which bows the edges of the footage towards the camera; the scale property (or potentially the z-position) of the footage is keyframed with an ease, and there's possibly a soft cut (really short dissolve) in between the footage. There's also some SepRGB action going on, for flavour, and what looks like some faked-out digital noise overlaid on top. To get the footage zoom in AE, keyframe the scale of the top layer so that it zooms in, then parent the back layer to the first, and KF the opacity of the top layer from 100% to 0% over the course of, like, 3f. That's a starting point that should get you close. ... View more

NOT INTERESTED, but thanks! We'll give Adobe a few more patches to iron things out, first... ... View more