Forum Replies Created

Page 1 of 29
  • Successful ETT operation using the same file, over thunderbolt with a Caldigit T3 (older model, not RAID5 capable). This is pointing more to a firmware issue with T4.

  • OK, this is getting a bit more perplexing. Just hooked the t4 array to a Macbook Pro, did a print to video without the MXO2 hooked up, and it choked again. FCP issues, or Caldigit firmware?

  • All right, it’s Tuesday morning, and as promised, I’ve run the self contained QT.

    So, about that five dollars you owe me….

    Here’s what console reports. I cleared the console as I opened FCP….The ETT crashed around 9:52 (4.5 minutes into the program).

    5/26/15 9:41:24.570 AM Final Cut Pro[1849]: ProKit’s NSWindow addition -setActiveAppearanceDuringRestore: has been deprecated and does nothing on SnowLeopard for apps linked on ProKit 5.x or later. Please remove this method call.
    5/26/15 9:41:44.000 AM kernel[0]: Sandbox: sandboxd(1953) deny mach-lookup com.apple.coresymbolicationd
    5/26/15 9:41:45.559 AM coreaudiod[163]: Disabled automatic stack shots because audio IO is active
    5/26/15 9:41:45.755 AM sandboxd[1953]: ([163]) coreaudiod(163) deny file-read-data /Library/Audio/Plug-Ins/Components/AppleAES3Audio.component
    5/26/15 9:41:45.758 AM sandboxd[1953]: ([163]) coreaudiod(163) deny file-read-metadata /Library/Audio/Plug-Ins/Components/AppleAES3Audio.component/Contents
    5/26/15 9:41:45.761 AM sandboxd[1953]: ([163]) coreaudiod(163) deny file-read-metadata /Library/Audio/Plug-Ins/Components/AppleAES3Audio.component
    5/26/15 9:41:45.787 AM sandboxd[1953]: ([163]) coreaudiod(163) deny file-read-data /Library/Audio/Plug-Ins/Components/Flip4Mac WMA Import.component
    5/26/15 9:41:45.790 AM sandboxd[1953]: ([163]) coreaudiod(163) deny file-read-metadata /Library/Audio/Plug-Ins/Components/Flip4Mac WMA Import.component/Contents
    5/26/15 9:41:45.793 AM sandboxd[1953]: ([163]) coreaudiod(163) deny file-read-metadata /Library/Audio/Plug-Ins/Components/Flip4Mac WMA Import.component
    5/26/15 9:41:46.271 AM coreaudiod[163]: Enabled automatic stack shots because audio IO is inactive
    5/26/15 9:41:46.277 AM coreaudiod[163]: Disabled automatic stack shots because audio IO is active
    5/26/15 9:41:47.074 AM coreaudiod[163]: Enabled automatic stack shots because audio IO is inactive
    5/26/15 9:41:47.080 AM coreaudiod[163]: Disabled automatic stack shots because audio IO is active
    5/26/15 9:41:47.860 AM coreaudiod[163]: Enabled automatic stack shots because audio IO is inactive
    5/26/15 9:42:04.718 AM coreaudiod[163]: Disabled automatic stack shots because audio IO is active
    5/26/15 9:42:04.846 AM coreaudiod[163]: Enabled automatic stack shots because audio IO is inactive
    5/26/15 9:42:24.171 AM WindowServer[86]: CGXDisableUpdate: UI updates were forcibly disabled by application “Final Cut Pro” for over 1.00 seconds. Server has re-enabled them.
    5/26/15 9:42:25.852 AM WindowServer[86]: reenable_update_for_connection: UI updates were finally reenabled by application “Final Cut Pro” after 2.68 seconds (server forcibly re-enabled them after 1.00 seconds)
    5/26/15 9:42:25.891 AM coreaudiod[163]: Disabled automatic stack shots because audio IO is active
    5/26/15 9:42:25.913 AM coreaudiod[163]: Enabled automatic stack shots because audio IO is inactive
    5/26/15 9:42:47.691 AM coreaudiod[163]: Disabled automatic stack shots because audio IO is active
    5/26/15 9:46:57.388 AM mDNSResponder[36]: Double NAT (external NAT gateway address 192.168.0.10 is also a private RFC 1918 address)
    5/26/15 9:46:58.968 AM SubmitDiagInfo[2279]: Launched to submit Diagnostics and Usage
    5/26/15 9:47:47.005 AM coreaudiod[163]: Enabled automatic stack shots because audio IO is inactive
    5/26/15 9:47:48.883 AM WindowServer[86]: CGXDisableUpdate: UI updates were forcibly disabled by application “Final Cut Pro” for over 1.00 seconds. Server has re-enabled them.
    5/26/15 9:47:58.517 AM WindowServer[86]: reenable_update_for_connection: UI updates were finally reenabled by application “Final Cut Pro” after 10.63 seconds (server forcibly re-enabled them after 1.00 seconds)
    5/26/15 9:47:58.561 AM coreaudiod[163]: Disabled automatic stack shots because audio IO is active
    5/26/15 9:47:58.593 AM coreaudiod[163]: Enabled automatic stack shots because audio IO is inactive
    5/26/15 9:51:56.000 AM kernel[0]: 0xffffff8149202000::rc_scsi_cmd_START_STOP_UNIT: Disable disk cache flush
    5/26/15 9:52:23.291 AM WindowServer[86]: CGXDisableUpdate: UI updates were forcibly disabled by application “Final Cut Pro” for over 1.00 seconds. Server has re-enabled them.
    5/26/15 9:52:32.982 AM WindowServer[86]: reenable_update_for_connection: UI updates were finally reenabled by application “Final Cut Pro” after 10.69 seconds (server forcibly re-enabled them after 1.00 seconds)
    5/26/15 9:52:33.040 AM coreaudiod[163]: Disabled automatic stack shots because audio IO is active
    5/26/15 9:52:33.712 AM coreaudiod[163]: Enabled automatic stack shots because audio IO is inactive
    5/26/15 9:52:37.289 AM coreaudiod[163]: Disabled automatic stack shots because audio IO is active
    5/26/15 9:52:37.311 AM coreaudiod[163]: Enabled automatic stack shots because audio IO is inactive
    5/26/15 9:52:40.805 AM coreaudiod[163]: Disabled automatic stack shots because audio IO is active
    5/26/15 9:52:41.190 AM coreaudiod[163]: Enabled automatic stack shots because audio IO is inactive
    5/26/15 9:52:54.464 AM WindowServer[86]: CGXDisableUpdate: UI updates were forcibly disabled by application “Final Cut Pro” for over 1.00 seconds. Server has re-enabled them.
    5/26/15 9:52:56.042 AM WindowServer[86]: reenable_update_for_connection: UI updates were finally reenabled by application “Final Cut Pro” after 2.58 seconds (server forcibly re-enabled them after 1.00 seconds)
    5/26/15 9:52:56.078 AM coreaudiod[163]: Disabled automatic stack shots because audio IO is active
    5/26/15 9:52:56.195 AM coreaudiod[163]: Enabled automatic stack shots because audio IO is inactive

  • The program I’m laying off is a syndicated 30 minute fishing show. Content is the same, edited and closed captioned previously, and imported as its own self contained file, but the commercial package is different for each market. That’s 4 commercial breaks, each 2 minutes long. For 25-32 different markets, depending on time of year. We send a new show out every week. 52 episodes a year. For the last 30 years. That’s 1528 episodes to date. 3 markets get an hour long version. Of those markets, about half are still requiring physical media. Speed is a factor. Exporting the self contained file is another step, that we’ve never had to do before, in the 11 years we’ve been on FCP.

    Again, I am going to try your suggestion, just can’t do it till the office is open on Tuesday. But I’m still trying to understand why the new hotness (caldigit t4 raids thunderbolt) is choking, when we had no issues with the old drive (Caldigit VR raid1 firewire 800).

    I don’t want to frustrate you any further, so I’m going to table this till after Memorial day, when I can try your suggestion.

  • Don’t think that I’m discounting anything you have to offer… I am fully aware of the contributions you and others have provided to this site, and the industry in general (and thank you for it). I myself was fairly active helping others a few years ago mostly in the basics forum… Fell off as more people migrated to premiere or avid. I’m trying to understand the problem, and the root cause of it.

    But back to the subject at hand. This is all academic until I get back to the office; there are no disabled clips, everything is the same codec (prores lt) except for lower thirds. The problem persists on multiple timelines, multiple projects with mostly different media, I’ve rerendered , switched to sa RT, reconfigured the raid as 1 and 0, tried different cables, different wiring schemes, updating from mountain lion to Maverick (and then using a beta version of the Matrox driver… FCP was nearly unresponsive, which may be a clue, so had to restore). And of course, I trashed final cut preferences. If I pick up the ETT from where it choked, it again works 5-7minutes before choking again.

    Interestingly, if I print to video, it works for a bit, then playback freezes for a couple seconds, then continues on with no audio.

    I’ve checked console logs to try and determine if something in the background is affecting performance, but nothing stands out. The only program installed on this system not necessary for the job is istat menus for resource monitoring.

    The only thing that comes to mind is possibly bad Ram, but apple hardware test shows it as good. Going to run Remembr on Tuesday to be sure. AFTER I export and try self contained QT. Also currently transferring user profile to a different (lower spec, same manufacture year) Imac as my nuclear option.

    Any further thoughts?

  • That’s probably the only troubleshooting step I haven’t tried, because (1)doing that wouldn’t be practical for our workflow, for reasons I won’t get into here, (2) the failure has never happened at an edit point, nor anywhere near more than 1 layer of prores LT. (3)its been working for years with a smaller, slower raid, on a slower connection.

    But, I will try as you say bright and early Tuesday morning. However, if your solution Does work, what would be the reason? Raid1 via firewire is superior to raid 5 via thunderbolt?

  • Dennis Leppell

    May 22, 2015 at 9:02 pm in reply to: FCPtoAE Popcorn Island. Where can I get it?

    Holy crap, is it your lucky day….I happen to still have this stashed away. don’t remember if it was any good or not.

    https://www.dropbox.com/s/4hhoi9lnry3vrm3/PI_FCP2AE.jsxbin?dl=0

    INSTALLATION
    Copy the “PI_FCP2AE.jsx” file into your “Adobe AfterEffects –> Scripts” Folder.

    USAGE
    Save an XML file from Final Cut.
    Open After Effects
    Choose File –> Scripts –> PI_FCP2AE.jsxbin
    Browse to the Final Cut XML File.

  • Dennis Leppell

    August 9, 2013 at 9:00 pm in reply to: Moving on from Graid Drives

    I’m using CalDigit gear, and am pretty happy with them. Customer support, the one time I needed it, was incredibly responsive.

  • I use this camera daily, along with FCP 6. Here’s the deal.

    When capturing from tape, you use Batch Capture, and connect the computer directly to the camera via firewire.

    When capturing from card, you have options. First and foremost, you should backup the entire card onto a hard drive. Create a folder on the drive, and drag/drop ALL of the disk contents into that folder. Very important, so you can maintain file structure. You can use either a card reader, or mount the HVR-MRC1 (the video recording unit you are referring to) onto its docking unit (with battery), and connect that to the computer via firewire.

    Now you are ready to import footage into FCP. Open log and transfer. mount the footage by clicking the add folder button in the upper left of the window, and select the Video folder that’s inside the other folder you created.

    Now here’s the catch, and the root of your problems. FCP doesn’t have adequate support of the MTS file type, particularly with those created by a Z7. Thus, you cannot preview the footage, nor set in/out points for each file. You MUST transfer the whole file. BUT, you do not have to transfer all the footage that was on the card. Pick and choose the files you will need, that closest correspond with your shot list, and add these to the queue. Since each shot has a unique name, you should be able to figure it out (the format is (reel_shot#_Year_Day_Time)

    VERY IMPORTANTWhen you are done, you must eject the footage/volume. Select all and hit the eject button in the upper left corner. Hitting delete on your keyboard will delete all your original footage from your hard drive.

    Good luck, and get cutting!

  • Ok, fired things up today, but without the Lacie HDD in place. Everything seems fine. Maybe my bootup order? Started the deck first, then the Caldigit, then the iMac.

    I’m so confused.

Page 1 of 29

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