Erik Lundmark
Forum Replies Created
-
Yes I did and it didn’t make any difference. I conformed it back and forth between 24 and 23.98. The frame rate did reflect the changes but not the Media Start and End.
Erik -
Here’s the next test I did.
I set the deck to true 24 frames, set up my capture settings to trues 24 frames, created a new compressor setup all in true 24 f/s with a watermark.
Now it works. the Media Start and End stay consistent.
So Compressor doesn’t know how to deal with 23.976 is my only conclusion.
-
I have both a burn-in window on the source material and I’m also looking at the Media Start Media End fields in the FCP Browser.
the burn-in window doesn’t change of course since it’s embedded, but the Media Start and Media End fields change. The problem is that we can’t rely on those new numbers for frame accuracy relating to the original high-res material. -
[Barry Green] “I don’t know quite what’s happening, but we think it’s related to how a Mac will write files to any new volume the first time that volume gets mounted (it writes at least a “trashes” and “recycled” directory to the card, and who knows what all else?) Perhaps somehow in that process, it does something or conflicts with something which introduces an instability in the handshaking? I don’t know.”
Thanks for claryfying it for me, much appreciated.
Erik -
[Barry Green] “That’s the infamous mac “glitch” that occasionally happens. We think that it’s related to putting a card in a Mac (or connecting the camera as a card reader to the Mac) while the cards are not write-protected. *Never* allow a P2 card near a Mac without being write-protected.
The footage on your cards is good, it’s the Mac transferring the footage that glitches it. You can try re-importing if you still have the footage on the cards.”
The more I think about this the more confusing it gets. If the computer (Macs only, or even PCs?) is able to corrupt the data becasue the card is not write protected it sounds as if the data on the card is altered once put into a computer, or when a file transfer is happening. Maybe some kind of handshaking protocol? If that’s so, how can the files on the card still be good if the computer did something to them? And how can making the card in read-only mode not negotiate the same corruption?
You must understand that this is not a consistent behavior. It popped up after a few months of using the camera, and it’s still not always there, but often enough to know that something is not working right. -
Thanks for the info.
I’ll keep that in mind for the future, to always write protect the cards before I use them in the computer.
Do you have technicals ideas what’s going on? Why would some frames have corrupt pixels without giving me any error messages in the file transfer?
Thanks,
Erik -
I hear you. My old box started doing it too.
And I thought it only was an issue with new boxes. Those were the ones I was installing at a post facility. My only thought is that the DA converter loses sync suddenly for some to me unknown reason. And since the old boxes are acting up as well as the new ones it must be some updated (changed) software that is causing the noise.
Needless to say, my clients are very dissapointed. I need to find another view-out solution as this one is too hard to trust. -
[Luke Maslen] “switch your easy setup to Blackmagic HDTV 1080 23.98 -> 59.94 and then your TV should be able to play out the 1080i59.94 signal.”
OK, I’ll try that tomorrow.
But we did get a picture by changing the video out (1080p 23.98 -> 29.97) under the “View” menu. My guess was that this is essentially the same output as using the Easy Setup 1080p 23.98 -> 59.94.Thanks,
Erik -
OK, got it, thanks!
Erik
-
[walter biscardi] “Something sounds very wrong there. With my Kona 3 card, I can select anywhere from 1 – 16 channels during ingest and they are never greyed out. You might want to check with BlackMagic on that one, I’d be shocked if you can’t deselect audio channels on there”
Yeah, I’m taking this to the BMD forum instead since it’s not a FCP issue.
Thanks for your quick responses.
Erik