Ben G unguren
Forum Replies Created
-
Ben G unguren
August 27, 2014 at 2:38 pm in reply to: Name of FIRST VISIBLE LAYER beneath text layer?Thanks for the “break”, Kevin & Dan — very very helpful!
Ben Unguren
Motion Graphics & Editing
http://www.mostlydocumentary.comSome contents or functionalities here are not available due to your cookie preferences!This happens because the functionality/content marked as “Vimeo framework” uses cookies that you choosed to keep disabled. In order to view this content or use this functionality, please enable cookies: click here to open your cookie preferences.
-
Ben G unguren
August 26, 2014 at 4:40 pm in reply to: Name of FIRST VISIBLE LAYER beneath text layer?Clarification: By “bottommost” layer, I mean the bottommost VISIBLE layer. So it’s working, but after it finds the first visible layer, it checks all the layers beneath it. I want it to stop checking at that point!
Ben Unguren
Motion Graphics & Editing
http://www.mostlydocumentary.comSome contents or functionalities here are not available due to your cookie preferences!This happens because the functionality/content marked as “Vimeo framework” uses cookies that you choosed to keep disabled. In order to view this content or use this functionality, please enable cookies: click here to open your cookie preferences.
-
Try Liquefy. It’s a bit more organic than you might like, but you can do some pretty cool stuff with it.
Ben Unguren
Motion Graphics & Editing
http://www.mostlydocumentary.comSome contents or functionalities here are not available due to your cookie preferences!This happens because the functionality/content marked as “Vimeo framework” uses cookies that you choosed to keep disabled. In order to view this content or use this functionality, please enable cookies: click here to open your cookie preferences.
-
Interesting dilemma.
While not perfect, this got me pretty close: New Comp, New Layer — I created a mask/path, then applied the Stroke effect. I set it the effect to Paint on Transparent, Hardness to 100%, Brush Size around 1.6 (this is the critical setting, which you’ll want to adjust to taste). Then I created an Adjustment Layer with a Levels effect. Set the Level’s filter Channel to “Alpha”, then slide the Alpha Gamma to 0.00. This gave me a nice, nasty jagged line, with most parts (but not all) exactly one pixel wide (you’ll have to precomp it if you want to put it on top of anything else). Adjust the Stroke Brush Size until you get the width you like best.
The only thing that comes to mind to get EXACTLY what you want it is to create the final pixelated line in photoshop, pixel for pixel. Then use your preferred method to reveal the line in AE (masking, painted mask, animated stroke, etc).
Keep in mind that often a single-pixel line isn’t single pixel in the end, but aliased, with softened edges. Most people can’t tell the difference; in fact, they will see an aliased line as single pixel more readily than a non-aliased one. Especially when it’s a part of a motion graphics piece.
Ben Unguren
Motion Graphics & Editing
http://www.mostlydocumentary.comSome contents or functionalities here are not available due to your cookie preferences!This happens because the functionality/content marked as “Vimeo framework” uses cookies that you choosed to keep disabled. In order to view this content or use this functionality, please enable cookies: click here to open your cookie preferences.
-
This isn’t the most elegant solution, but I’ve found that you can COPY / PASTE from one PPRO project to another, and it will use existing clips where possible. Here’s my process (again, not the most elegant — I use CS6):
1 (USE THE RIGHT FORMAT): Use FCP XMLs for all file transfers. (This makes it easier in case you have someone on your team who prefers FCP. Also it allows you to work between CC, CS6, and the occasional CS5.)
2 (PREPARE YOUR MAIN PROJECT): Make sure ALL CLIPS are loaded in your main PPRO project. SAVE.
3 (PROCESS THE TRANSFERRED FILE): Make a NEW PPRO PROJECT (I usually call it “TRANSFER” and put it in the same directory — I use it a lot on multi-user projects). IMPORT the new FCP XML into the project. Select only the desired SEQUENCE in your project window and COPY (Cmd+C). SAVE.
4 (THE IMPORTING TRICK): OPEN your Main PPRO project and PASTE (Cmd+V). At this point I’ve had a couple things happen:
A. The sequence alone shows up in your Project Window; everything is linked to your original footage. You’re done!
B. The sequence shows up with all assocated clips — it’s a big mess. In this case, do the following:5 (B ONLY): If you get B, drag everything that was pasted (all the items will be selected) over the “Bin” icon to put the mess into a bin.
6 (B ONLY): Take the new sequence any new items that aren’t in your current project (usually music, graphics) and move them out of the bin. Select everything else in the bin and DELETE.
Even though PPRO gives me a warning (“If you continue, these clips will be deleted from your sequences”, etc), It still seems to give me the desired result — the sequence’s clips were linked to the ORIGINAL clips from the project file, and not the pasted clips.
Again, I realize this is more of a hack than a feature, so it can’t necessarily be counted on for future releases, but it has been a reliable hack for me so far. Happy editing!
Ben Unguren
Motion Graphics & Editing
http://www.mostlydocumentary.comSome contents or functionalities here are not available due to your cookie preferences!This happens because the functionality/content marked as “Vimeo framework” uses cookies that you choosed to keep disabled. In order to view this content or use this functionality, please enable cookies: click here to open your cookie preferences.
-
Ben G unguren
February 18, 2013 at 7:13 pm in reply to: Final Cut Pro XML issue when imported in to PProBe sure to check the source files — open them in some other player (QT, MPEG Streamclip, VLC, etc) to verify that they are indeed HD clips. Maybe they were transcoded to DV-esque footage as part of the XML export. Or something.
If they are HD, try making a new sequence with the HD settings as you like them, then copy/paste the entire edit from the bogus sequence to the good one. And then rescale the clips to fit the HD sequence.
Ben Unguren
Motion Graphics & Editing
http://www.mostlydocumentary.comSome contents or functionalities here are not available due to your cookie preferences!This happens because the functionality/content marked as “Vimeo framework” uses cookies that you choosed to keep disabled. In order to view this content or use this functionality, please enable cookies: click here to open your cookie preferences.
-
Ben G unguren
December 28, 2012 at 5:00 pm in reply to: TIP: Keep your FCP Studio 2 *QT* License on 10.7+Rafael: It worked! Here’s what I did:
– Locate the old 10.6 installer.
– Open “Optional Installs.mpkg” located in the “Optional Installs” folder of the install disc
(Incidentally, this installer runs fine, while the main FCP installer doesn’t)
– Deselect all apps except for “Rosetta”
– Run the installerFrom there, installing FCP was a snap!
10.8 + 10.6/Rosetta + FCP 6 = goodness
Now to find my 6.0.6 update….
Ben Unguren
Motion Graphics & Editing
http://www.mostlydocumentary.comSome contents or functionalities here are not available due to your cookie preferences!This happens because the functionality/content marked as “Vimeo framework” uses cookies that you choosed to keep disabled. In order to view this content or use this functionality, please enable cookies: click here to open your cookie preferences.
-
Ben G unguren
December 28, 2012 at 3:17 pm in reply to: TIP: Keep your FCP Studio 2 *QT* License on 10.7+You’re right, Steve — QT 7 is easily downloaded from Apple, where it is installed in the Utilities folder. But I am talking about registering QT Pro using the license for Studio 2. I did a clean install of Mountain Lion, thus can’t install Studio 2, and leaves me hanging with QT 7.
Raphael, thanks for the tip with Rosetta — I’ll give that a try today! I don’t use FCP much these days; operating under the assumption that in 2 or 3 years Studio 3 will only run on legacy machines…. But I loooooove how FCP combines and exports quicktime movies, especially for syncing DSLR footage with external audio. (But I do that so infrequently I’m not sure it justifies buying a copy of Studio 3.)
Thanks for your input guys.
Ben Unguren
Motion Graphics & Editing
http://www.mostlydocumentary.comSome contents or functionalities here are not available due to your cookie preferences!This happens because the functionality/content marked as “Vimeo framework” uses cookies that you choosed to keep disabled. In order to view this content or use this functionality, please enable cookies: click here to open your cookie preferences.
-
Thanks for the information in this thread everybody. I’m on 10.6.8, and if the GUI starts to slow down (particularly dragging clips around in the timeline) I now resize the window. In most cases I can make it about half-size for a minute, then go back to full-size and everything keeps working great!
This doesn’t happen all that often to me, but it’s good to know how to work around it when it does! (I’m perpetually afraid of upgrading the OS….)
Ben Unguren
Motion Graphics & Editing
http://www.mostlydocumentary.comSome contents or functionalities here are not available due to your cookie preferences!This happens because the functionality/content marked as “Vimeo framework” uses cookies that you choosed to keep disabled. In order to view this content or use this functionality, please enable cookies: click here to open your cookie preferences.
-
Check your parenting hierarchy. Also, make sure you select the layers in the correct order (hand->lowerArm->upperArm->handController). I’ve gotten that message and in most cases redoing the parenting and/or selecting seems to do the trick.
Ben Unguren
Motion Graphics & Editing
http://www.mostlydocumentary.comSome contents or functionalities here are not available due to your cookie preferences!This happens because the functionality/content marked as “Vimeo framework” uses cookies that you choosed to keep disabled. In order to view this content or use this functionality, please enable cookies: click here to open your cookie preferences.