Forum Replies Created

Page 2 of 34
  • Jeff Markgraf

    May 1, 2018 at 6:55 pm in reply to: Reconsidering FCPX in Hollywood

    [Simon Ubsdell] ” But can we really, at this very late stage, attribute all the blame exclusively to intransigent editors who refuse to see the light?”

    Speaking to FCPX in “Hollywood”:

    “all,” “exclusively” – of course not. But substitute “most” and “primarily” – a resounding YES. After 7 years, the level hostility and misinformation is breathtaking.

  • Here’s a page that looks at several remote controllers using iPad. Not sure which ones use Bluetooth vs. WiFi.

    – I’ve briefly played with Ctl+Console a while back, and it works as advertised.

    – Lots of people seem to have used the ProCutX as well. (I seem to recall some controversy surrounding some Pixel Film Studios plugins a while ago, so maybe do some research here.)

    Most any of these would seem to do what you want.

  • Jeff Markgraf

    November 22, 2017 at 8:24 pm in reply to: Head scratcher: unable to export (share) a project

    Hi Sam.

    I didn’t put in a support ticket with you guys because it didn’t seem like a Jellyfish problem. I could export his sequences just fine from my system. Same with the other user.

    Today one of the problem systems saw the problems disappear. Go figure!

    After Googling the issue, it seems bad renders and/or corrupt files may be at play. I’m going to keep an eye on this and I’ll submit a support ticket if it crops up again. Thanks for the quick response.

    Enjoy your turkey & trimmings.

  • Jeff Markgraf

    November 21, 2017 at 10:41 pm in reply to: FCPX monitoring cam audio issues

    Yep. It’s a known bug. I think it was introduced with Mavericks OS. FWIW, it seems only to affect files that have the pan mode set to “none” – which, of course, would be any file with mono audio.

    I thought it was just with AJA I/O hardware. Sorry to hear it affects BMD as well. But at least it’s an easy fix once you know what to do. But I agree – kinda shoddy coming from Apple.

  • Jeff Markgraf

    October 12, 2017 at 8:03 pm in reply to: Yesterday’s Emmys & FCP X.

    Oliver-

    Sorry about the misspelling. Haven’t used a Teranex in years (last used one to convert SD PAL to SD NTSC).

    Do you know if Teranex’s basic technology has changed since Black Magic bought the company? Any change to their “secret sauce” algorithms?

  • Jeff Markgraf

    October 12, 2017 at 7:58 pm in reply to: Yesterday’s Emmys & FCP X.

    Andy –

    You stepped into a thread about research and winning an Emmy, and what role FCPX may or may not have played, with this nonsense:

    “And everyone says FCPX allows you to edit in ways not possible in any other NLE : )”

    As the thread became more about hardware vs. software methods to upscale SD to 4k, and threatened to derail over confused terminology, you added nothing to the discussion except to call out FCPX for its inability to do things it wasn’t designed to do.

    You presented no new information, solved no problem, provided no insights, cleared up no confusion, saved no new or potential users from hours of confusion or frustration.

    Your incessant trolling is tiresome. Please stop. Please contribute meaningfully to the conversation and the community.

  • Jeff Markgraf

    October 11, 2017 at 12:04 am in reply to: Yesterday’s Emmys & FCP X.

    [Shane Ross] “how do you directly capture video into FCP-X? What capture DEVICE can you use, within the FCP-X interface, to capture video?”

    Per the FCPX help document:
    “Final Cut Pro supports tape-based import of the DV (including DVCAM, DVCPRO, and DVCPRO50), DVCPRO HD, and HDV formats”.

    So the only “direct” capture is from DV based tape formats. If you have a new MacPro, you would need a DV to Thunderbolt cable to connect the tape deck. An older Mac Pro with a Firewire port would be able to connect directly.

    (Of course DV is a compressed format and doesn’t allow for the best upscaling of SD video. Obviously, DVDPRO50 and DVCPRO HD would be the least compressed, but still not uncompressed. And the reduced color sampling is always going to be an issue.)

    Other “direct” capture is via Thunderbolt, Firewire or USB from modern file-based cameras

    Isn’t this a bit of a tempest in a teapot? FCPX wasn’t really made with tape capture in mind. It’s built for file based import and export. We all know that. So use the AJA capture utility or the Black Magic device of your choice and move on.

    This is silly. I don’t think anyone is trying to be insulting. I think it’s more of a terminology misunderstanding. No need for yet another video “tutorial.”

    The Terranex vs. software upscaling discussion, on the other hand, is interesting. Terranex used to be the gold standard. I’m curious if the choices (softening vs sharpening, for instances) are different for stills vs. motion when upscaling. Does one method work better for interlaced vs. progressive, etc.

  • Duncan & Jesse –

    See the reply to Ben above (or below) this thread and try the MIDI configuration fix. Hope it helps.

  • It’s a bug that’s been around for a while when monitoring audio with an external device, like an AJA T-Tap. Not sure which other devices have this problem. Shouldn’t happen when monitoring through the headphone/line out or through the monitor speaker.

    Here’s the fix:

    1. Open Audio MIDI Setup from the utility menu. Switch “Speaker Configuration” from Stereo to 2 Channel Surround. Apply the setting.

    2. Reselect Stereo and apply it. Close the MIDI setup.

    This should fix the problem.

    Otherwise, change the audio pan setting of the clip in the browser from “none” to “Stereo” with the pan set to center, and that will also fix the issue, although as a workaround.

Page 2 of 34

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