Brandon Kraemer
Forum Replies Created
-
Yes, the audio out on the Blackmagic card does seem to contribute to the problem. However, problem just changes, I get video out with out dropped frames but now my audio is out of sync!
-
Has anyone found a solution to this? I recently tried isolating my NVidia cards from the system and disabled the NVidia drivers with no luck. The only thing that solved it was to disable the driver for the Blackmagic DeckLink, but then I have no video output. This wasn’t an issue under Mountain Lion with my Kona 3 card, but that card is incompatible with Resolve.
-
What PCI slot are people’s Decklink cards installed in? Mine is in slot4, only other option for me is slot3. Haven’t tested swapping yet.
-
I am having this same issue. Just changed my system from a Kona 3 to the BMD Decklink 3D+ card and upgraded to Mountain Lion and now it’s drop frame city.
I was running FCP 7 for about 4 days in Mountain Lion prior to swapping cards with out drop frames so it looks like it’s the Decklink.
-
exactly. if you are using a managed volume(s) share via the server itself over say SMB then you do not need to establish a storage area network with metadata controllers.
I would guess that what you propose will work with a limited number of clients with this scenario, but if you go beyond a few clients a SAN will give you a lot better performance but will also require primary and redundant MDCs.
-
I do not recommend sharing the storage from the file server via SMB over the Gbit connections. It’s best to turn your file server into a master meta-data controller and turn the client workstations into redundant MDCs with something like metaSAN.
You can’t just plug in everyone into the switch and directly mount your shared storage to all client machines unless that volume is a managed share from the file server or the network is running under some kind of SAN.
-
the OP’s mindset stems from…
1. everything else in the industry being available in some kind of cheap dumbed down prosumer form, so why not a SAN?
2. lack of experience with the real world business side of this industry.
3. operational costs and profit margins shrinking in this industry for 10 years +.
4. sense of entitlement, “why can’t I have everything I want for next to nothing” rubbing off from clients to post-production community.
-
short answer… a LAN setup uses a server that shares a disk over network protocol (SMB/AFP) but that volume is owned by the server which controls it.
A SAN is a volume that is mounted to multiple users directly, not via a server’s share… but a server class machine typically governs the metadata, so clients have a metadata and a data connection to the SAN.
-
Thank you, we of course suspected our workflow was sound. So this begs the question, what is up with the nasty lines of chatter and buzzing on areas of fine detail? Has anyone else seen this?
It’s to the point that I’m almost recommending to my director to never shoot over-cranked with this camera. The only way to salvage a shot is to add vertical blur and the image is softer than standard speed footage to begin with so it’s not really a solution.
I can’t be the only one seeing this?
-
that is exactly what we are doing… only difference is the 7D 720p 50 fps footage is being converted in Cinema Tools to 25 fps instead of 50 fps… still plays as slo-mo.
I have seen this before on clips not converted to 25 from 50. The fact that it has this nasty look but irregardless of movement (not a field issue) and is on any fine lines makes me suspicious that it’s something the camera is doing when it windows down on the sensor.