Michael Tate jones
Forum Replies Created
-
Michael Tate jones
April 22, 2010 at 4:17 pm in reply to: Final Cut Pro crash due to use of BCC 6 pluginI’ll give it a try. Will I be able to easily revert back to my licensed copy of BCC 5?
-
Michael Tate jones
April 22, 2010 at 4:12 pm in reply to: Final Cut Pro crash due to use of BCC 6 pluginYes, running FCP 7.02, but I haven’t upgraded to BCC 6 yet. Still running the latest version of BCC 5.
-
Michael Tate jones
April 22, 2010 at 3:16 pm in reply to: Final Cut Pro crash due to use of BCC 6 pluginI’m still seeing that bug pop up either during a render or occasionally when the CTI is over a clip with a Boris effect.
Don’t have 2 video cards, but we do have a Black Magic card in the machine which technically may be considered a second video source I guess.
Just yesterday I was trying to render a clip with the 3D extruded shatter effect and it would crash with that same NRTAll bug. Strangely enough it would render ok if my frame size was 1280×1080 30P with a pixel aspect ratio of HD 1280×1080. But if I switched to 1920×1080 60i with a square aspect ratio it would crash during the render.
Hope this helps.
-
Michael Tate jones
March 25, 2010 at 2:50 pm in reply to: Final Cut Pro crash due to use of BCC 6 pluginGreat! Just installed it. I’ll let you know how it goes. Hopefully that NRTAll bug is squashed.
-
Michael Tate jones
March 15, 2010 at 8:24 pm in reply to: Final Cut Pro crash due to use of BCC 6 pluginHere’s my crash code if it helps…
Path: /Applications/Final Cut Pro.app/Contents/MacOS/Final Cut Pro
Identifier: com.apple.FinalCutPro
Version: 7.0.1 (7.0.1)
Build Info: FCPApp-910141802~4
Code Type: X86 (Native)
Parent Process: launchd [102]PlugIn Path: /Library/Plug-Ins/FxPlug/BCC NRTAll.fxplug/Contents/MacOS/BCC NRTAll
PlugIn Identifier: com.BorisFX.BCC NRTAll
PlugIn Version: 5 . 0 . 5, 8 bit (76)Date/Time: 2010-03-15 15:12:36.493 -0500
OS Version: Mac OS X 10.6.2 (10C540)
Report Version: 6Interval Since Last Report: 187339 sec
Crashes Since Last Report: 6
Per-App Interval Since Last Report: 139726 sec
Per-App Crashes Since Last Report: 6
Anonymous UUID: 815A6A6B-1305-4397-AAA0-40197853791DException Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000020
Crashed Thread: 0 Dispatch queue: com.apple.main-thread -
Michael Tate jones
March 15, 2010 at 8:23 pm in reply to: Final Cut Pro crash due to use of BCC 6 pluginHi Matt, it’s been a few months since the original post on this issue. Any updates for us? Would REALLY appreciate getting this bug squashed ASAP 🙂
-
Michael Tate jones
March 10, 2010 at 6:20 pm in reply to: Final Cut Pro crash due to use of BCC 6 pluginI have the same issue as well, however, I’m still using BCC5 with FCP Studio 3. This is discouraging as I was hoping the eventual upgrade to BCC 6 would solve the problem.
-
Michael Tate jones
June 2, 2009 at 4:40 pm in reply to: Query about merits of Firestore tapeless Vs Decklink Tape CaptureI’ve been using a Firestore for over a year now. It has saved me tons of time pouring through countless tapes and logging and capturing footage. The Firestore creates an individual Quicktime movie every time you start and stop recording. When you’re done shooting, you just connect it like any other Firewire Hard Drive and copy the individual files to your computer and start editing.
As the previous poster stated. You’ll only need the Decklink card if you plan on capturing or outputting video to/from broadcast quality tape decks (Incredibly expensive pieces of equipment) or to view the output of your video editor to a broadcast quality monitor.
-
I’ve updated as well with no ill side effects. Running 2 x 2.8 Quad Core Mac Pro, OS X 10.5.3, Quicktime 7.5, BM Multibridge 6.7, 10GB of Ram. This is much better than my Pinnacle Cinewave days where each successive update from Apple would break the Cinewave software.