Forum Replies Created

Page 1 of 3
  • Tj Ingrassia

    November 10, 2019 at 4:36 am in reply to: Quicktime Playback – Green Screen of Death

    No, I’m using X. And the issue normally happens in the Finder, not when I am playing in QuickTime

  • Tj Ingrassia

    November 10, 2019 at 4:31 am in reply to: 2 Stereo Pair ProRes to single stereo H.264

    Did you ever solve this issue? I’m having the same problem right now.

  • Tj Ingrassia

    May 30, 2018 at 3:01 pm in reply to: Waveforms not matching audio – redraw?

    Same issue here. I’m on Premiere version 12.1.1 (Build 10).

    Short clips behave normally. It’s only on this longer project that I’m having the issue (2 video files recorded at a conference, each file around 8 hours long).

  • Same issue here. Premiere 2017.1.2. Brand new 5K iMac with every spec turned up to 11, running OS 10.12.2.

    I’m assuming this is an Adobe issue. Everything was running fine until I updated to the latest version of Premiere. That’s when the beach balls started happening.

  • Tj Ingrassia

    September 1, 2015 at 4:02 pm in reply to: “Pan Behind” equivalent?

    For lack of a better solution, I created one myself, called “Pan Behind”.

    https://bit.ly/1L11qPe

    Install the “Pan Behind” folder into the “/Motion Templates/Effects” folder.

    To use Pan Behind, create a layer mask just like you normally would, using any of the built in FCPX masks. Then, add Pan Behind to the clip. VERY IMPORTANT…Pan Behind must be moved *ABOVE* the mask in the effects hierarchy, or else it won’t work. With the Pan Behind effect selected, you’ll see a white box appear in the viewer, which you can grab and move around. Voila, you’re moving the clip underneath the mask.

  • Tj Ingrassia

    August 31, 2015 at 3:58 pm in reply to: Audio Hard Limiter

    [Oliver Peters] “That’s correct. The volume control for the clip occurs after the application of the audio effect in the hierarchy of effects in FCPX. Therefore, adding a filter has no affect on the volume levels that you set.”

    Just wanted to follow up. This little nugget is huge for me and explains so much about my frustrations with limiters up to this point. I’ve thus far been doing my mixing in the timeline, then throwing a limiter on the clip and wondering why no Limiting is taking place. I now know to add any gain that I need from within the Limiter filter *first*, and then make further adjustments in the timeline.

    Awesome tip!

  • Tj Ingrassia

    August 29, 2015 at 5:30 pm in reply to: Audio Hard Limiter

    [I think the guy just wanted to get his brick-wall compression in place and get the damn job done.]

    That’s exactly what I wanted.

    “Taint”… that’s classy.

  • Tj Ingrassia

    August 28, 2015 at 9:46 pm in reply to: Audio Hard Limiter

    This is very helpful and has gotten closer than anything I’ve yet found. A couple follow-up questions…

    1. It looks like if I use the “Gain” feature within the Compressor filter, it raises the level of the clip, but still obeys the “Limiter Threshold” that I set. However, if I raise the level of the clip in the Timeline/Inspector, the Limiter doesn’t seem to work…like it will only clip the levels that it recognizes from within the effect itself. Does that make sense? Am I doing something wrong or is this just the way it works?

    2. You mentioned saving my settings as a “unique effect”. I do this all the time with video effects (then use Motion to setup Rigs for custom controls within FCPX). However, it won’t let me right click an “Open a Copy in Motion.” Is there some other way to save my custom settings as it’s own separate effect, or does it only save my settings within the Compressor effect itself?

  • I’m assuming this is the case for the others who have QT7…my QuickLook (pressing the spacebar to preview a file) still does not work, even though I can open and play in QT7 without converting.

    This is very annoying for my workflow. I’ve used QuickLook for years and it’s maddening that it stopped working. I haven’t done a software update recently, so I can’t figure out why.

  • Tj Ingrassia

    July 14, 2014 at 1:21 pm in reply to: FCPX Pulldown from Canon C100 HDMI

    Correct, almost all capture and monitoring devices will accept 24p. The issue is with the signal being sent to those devices. My understanding is that most cameras (including the C100) do not output true 24p over HDMI, but rather they wrap the 24p stream into a 60i wrapper.

    Some “smart” devices, like the Atomos Ninja 2, are able to recognize the wrapper and extract the original 24p stream. Other devices, like the BlackMagic Ultrastudio Mini Recorder, are “dumb” in the sense that they only pass along the signal that they receive. So when the Mini Recorder sees the 60i wrapper from my C100, it isn’t smart enough to extract the 24p.

    The Mini Recorder is basically just a stripped down version of the Ultrastudio Express. If I plugged in my C100 to the Express, it would do the same thing as the Mini…pass along with 60i without unwrapping it.

Page 1 of 3

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy