Matthew Small
Forum Replies Created
-
It does fit in the box. Blackmagic has always been very good at keeping their packaging to a minimum. I really like this because it requires less resources to created boxes and doesn’t produce useless empty space.
I really hate software boxes that are 9x12x4 that only have an install disk and a half-size manual inside.
Matt Small
Pair of Hands
Sherman Oaks, CA“If it was easy, everyone would do it.”
-
When we “accidentally” upgraded to 10.3.9, we started getting snyc hits on output in video. I don’t know if you’re hooked up to a sync generator, but we downgraded back to 10.3.8 and that’s minimized our problems. I would STRONGLY recommend NOT upgrading to QuickTime 7 as your Pro Key will not work. Granted, it’s only another $25, but it adds one more variable to the problem. My recommendation is download the 10.3.8 combo update from apple’s site along with the Quicktime 6.5.2 re-installer that gets rid of QT7 and rolls back to 6.5.2, get your install disks and do an archieve and install of 10.3 and reload the 4.8 drivers from BMD. My 2
-
Here’s a nifty unit by Gefen with a remote control:
https://www.gefen.com/kvm/product.jsp?prod_id=2964
Matt Small
Pair of Hands
Sherman Oaks, CA“If it was easy, everyone would do it.”
-
Mathieu,
Yes, you are doing the right thing- if you need a continuous cadence (pulldown, 3:2) in your master. You are also saving 20% of your disk space by working in 23.98 since you’re essentially throwing out 1 of every 5 frames upon capture and removal of pulldown. Even if you don’t need constant cadence, you’re still helping yourself out by editing in 23.98
A lot of the time, dropped frames occur when the hard disk has material that is actually written farther apart on the disk. I would try to render for mixdown before you playback or output a QuickTime in 23.98 and bring it into a new sequence. If you have one continuous file, the likelyhood of dropped frames is less.
Matt Small
Pair of Hands
Sherman Oaks, CA“If it was easy, everyone would do it.”
-
You need to copy (drag & drop) the application itself onto the hard drive you wish to test and run (double-click) it from there.
Matt Small
Pair of Hands
Sherman Oaks, CA“If it was easy, everyone would do it.”
-
We had the same issue, but when we captured bars from the SRW deck, they were fine. I think it’s a problem within Final Cut where the bars and black generated in final cut were incorrect.
Matt Small
Pair of Hands
Sherman Oaks, CA“If it was easy, everyone would do it.”
-
Steve,
Good to hear that you’re making progress with the problems. I guess if I would have waited two minutes, I would have seen your previous post. Good luck with your troubleshooting!
Matt Small
Pair of Hands
Sherman Oaks, CA“If it was easy, everyone would do it.”
-
Another FCP gotcha is if the Canvas window is set to anything other than “Fit to Window”
Matt Small
Pair of Hands
Sherman Oaks, CA“If it was easy, everyone would do it.”
-
10.3.9 hosed our sync input to the card. We had to downgrade our OS to 10.3.5 and the shipping drivers with our Decklink HD Pro 4:4:4 to get back to a stable environment. Don’t upgrade to 10.3.9 if you don’t have to. If your system is stable, make sure it stays that way.
Matt Small
Pair of Hands
Sherman Oaks, CA“If it was easy, everyone would do it.”
-
Matthew Small
May 5, 2005 at 12:32 am in reply to: Wrong frame rate reported by Quick Time and other applications using Blackmagic codecI had this same problem capturing 1080 23.98. I went back into FCP and the frame rate was correct. I exported the file via File->Export->Quicktime Movie and created a new source clip that came up with the correct frame rate flag in QuickTime player and After Effects.
Matt Small
Pair of Hands
Sherman Oaks, CA“If it was easy, everyone would do it.”